Agile Data Models
Flexible Data Models – Paired with Point-and-Click ETL Management Tools – Keep Data Agile, Adaptable, and Always Up-to-Date.
Why does it take other vendors up to two years to implement their EDW and start delivering actionable insights? They spend too much time mapping portions of the metadata, relying mostly on manual processes and hand-customized ETL scripting. Manual mapping is not only time consuming but also must be redone again and again as data models shift.
Pre-Built Data Models
Health Catalyst arrives with a box of preconfigured loading scripts based on commonly available source systems, including clinical, financial, and ancillary sources from well-known healthcare software vendors.
This extensive, ever-growing library – developed by Health Catalyst team members who have mapped hundreds, maybe thousands, of Source Mart tables using traditional, manual methods – expedites extraction and automatically transforms metadata to load scripts. That means the platform can be installed and configured in as few as three months with a real ROI in as few as six.
Source Mart Library
Browse Health Catalyst’s catalog of Source Marts based on commonly available, well-known source systems.
Data Mapping Made Easy
Developing, testing, and deploying custom Source Marts is painless with Source Mart Designer, which captures source system metadata to automatically map tables and columns in a source system to tables and columns in a Source Mart.
Demystifying Table and Column Names
The Health Catalyst team uses its extensive knowledge of a source system, supplemented by the knowledge base in Source Mart Designer, to change cryptic source system names into ones that reflect the way humans think.
For example, a column in an EHR source system labeled Pat_ID may make sense to someone who’s worked with healthcare IT software a long time – and it’s only one of many names that could be used. But it’s not the way a person unfamiliar with that code would search for that information. The Health Catalyst team changes that column heading to the more intuitive PatientID so that when users search the metadata repository, they’re far more likely to find what they’re looking for.
Optimized for Late Binding
Data loaded from the source system to a Source Mart undergoes minimal transformation in the process – just enough to link it to core naming standards like patient ID and provider ID, encounter date and time, facility ID, etc.
Data stays in its raw, undiluted form and isn’t bound until a use case requires it, which saves healthcare systems from hammering out their entire data model up front.