Skip to main content

About Common Data Model

The Health Chain Common Data Model (CDM) that sits on the SQL on FHIR platform serves as a standardized framework for organizing healthcare data in a unified format that facilitates interoperability and analytics. By using FHIR as the foundational canonical model, Health Chain can seamlessly integrate with various healthcare systems.

Enhance Data Integration and Insights with Health Chain’s CDM and Data Mart Seamless Data Integration and Interoperability

Leverage FHIR's capabilities to integrate data from multiple healthcare systems, ensuring seamless data exchange and interoperability. This feature can support the aggregation of diverse data sources into a unified view, enhancing the comprehensiveness of the data analysis.

Improved Data Insights

By leveraging FHIR-based data marts, healthcare organizations can perform advanced analytics and reporting, gaining valuable insights into patient care and operational efficiency.

###Targeted Analytics Data marts built on top of the Common Data Model allow for the creation of specialized subsets of data tailored to specific business needs, such as Risk Adjustment, Quality Analytics and More!.

Comprehensive Data Models and Specialized Marts at a Glance Common Data Model

Unlocking the Power of FHIR Data

Navigating the complexities of FHIR data to derive actionable insights can be a daunting task. The vast array of FHIR resources, each with its own structure, cardinality, and relationships, creates a steep learning curve when trying to extract meaningful information.

To address this, SQL on FHIR and the Common Data Model (CDM) part of the SQL on FHIR Platform offers a comprehensive solution that bridges the gap between the intricate structure of FHIR and the familiar framework of relational databases, enabling organizations to maximize the value of their data. By transforming FHIR resources into well-organized, flattened tables, Health Chain CDM empowers users to:

  • Easily query and analyze FHIR data: Complex FHIR structures are flattened into intuitive, queryable tables, simplifying the process of retrieving and analyzing data without losing its clinical richness.
  • Build data marts and generate analytical reports: With FHIR resources structured into relational tables, creating data marts and generating custom reports becomes seamless, helping organizations gain actionable insights faster and more effectively.
  • Seamlessly integrate FHIR data with downstream applications: The CDM facilitates the smooth integration of FHIR data into existing relational systems, improving interoperability and supporting a wide array of downstream use cases such as business intelligence, decision support, and analytics-driven care management.

Moreover, the Health Chain CDM is built on the solid foundation of HL7 FHIR R4 fundamentals, meticulously handling cardinality, resource references, and complex data types. This ensures that the integrity of the data is preserved, while also enhancing its accessibility for non-technical stakeholders. By accurately reflecting the richness of FHIR data, the CDM ensures consistency, scalability, and compliance with evolving data standards.

Health Chain CDM is designed with performance and scalability in mind, capable of handling large volumes of healthcare data without compromising speed or accuracy. Whether deployed in cloud environments or on-premises, it offers flexible configuration options to fit the unique needs of each organization. By leveraging the Health Chain Common Data Model, organizations can unlock the full potential of their healthcare data, transforming it into a valuable asset for operational efficiencies, clinical decision-making, and enhanced patient care.

Health Chain CDM by the numbers Create as many data marts as possible and reports based on business requirements.

21 FHIR R4 and R5 Resources

21 Resource Core Tables

  • Account
  • Patient
  • Claim
  • Encounter
47 Resource Supporting Tables
  • Account_guarantor
  • Claim_insurance
  • Claim_payee
  • Encounter_diagnosis
  • Encounter_statushistory
  • Patient_contact
12 Data Type Supporting Tables
  • Codeableconcept
  • Reference
  • Contactpoint
  • Address
  • Humanname