×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

 
Return to Search

Reference Domain Analysis Model (RDAM)

Return to Search

Basics

Reference Domain Analysis Model (RDAM)

1380
Ballot - STU to Normative


Education Services; Guidance (e.g. Companion Guide, Cookbook, etc); Logical Model; - New/Modified HL7 Policy/Procedure/Process -

Create New Standard

Details

Technical Perspective: The CIC sponsored HL7 Reference Domain Analysis Model (RDAM) project scope is to integrate EHR System Functional Model (EHR-S FM), CIMI Clinical/Common Logical Information Model CLIM (SOLOR, FHIM, CIMI, CQF); where, the EHRS FM will be refactored to remove legacy data-conformance criteria and the EHR-S FM will be integrated with the CIMI harmonized FHIM, CQI/CDS/CQF domain Logical Information Models (LIMs). The RDAM domain LIMs and Domain Functional Models will be Sparx Enterprise Architect resident, within the HL7 Cloud and use open-source model to model transformation tools to constrain the RDAM to specify HL7 WG DAMs, the CIMI Basic Meta Model (BMM) archetypes and patterns, Detailed Clinical Models (DCMs), FHIR Structure Definitions (FSDs). HSPC SOLOR tools will manage context-specific common data elements, value and code sets across profiles and extensions, e.g., FHIR, CDA, C-CDA, NIEM, etc.

- The value proposition is that RDAM MDD tools can produce clear, complete, concise, correct, consistent and requirements-traceable CDA/C-CDA, FHIR, etc. implementation profiles, extensions, guides and reference-implementation artefacts to enable efficient-and-effective clinical decision support, knowledge-based-reasoning and population-based analytics. The requirements-traceable and consistent common Data Elements (CDEs), CIMI-BMM, DCMs, etc. increase patient-value (lower cost, increase quality and safety) as CDA/C-CDA, FHIR. etc. consistent implementation artefacts.

- As an example, the methodology might start with pre-coordinated, forms-based Structured Data Capture (SDC) Clinical Input Form (CIF), which are consumed by objects, components, and services. SDC depends on clear, complete, concise, correct, consistent and traceable common data elements (CDEs) which are structured from use-case/scenario requirements-traceable consistent CIMI-CLIM with SOLOR-semantics. As we walk up the DIKW model-of-meaning ladder, CIMI prefers to follow the post-coordinated, Detailed Clinical Model (DCM) Analysis Normal Form (ANF) path to knowledge based systems, population based analytics and business intelligence capabilities.

- Roles and Responsibilities: EHR WG will curate clinical functions. CIMI WG will curate Information model content. CIC WG will facilitate clinical ballot verification and validation of the RDAM content.


Technical Perspective: The HL7 RDAM reference domain analysis model project need is to integrate EHRS-FM system functional model, CIMI CLIM (SOLOR, FHIM, CIMI, CQF) common logical information model; where, the EHRS FM will be refactored and aligned with the CIMI harmonized FHIM, CQI/CDS/CQF domain LIMs logical information models. The RDAM domain LIMs and Domain FMs functional models will be Sparx Enterprise Architect resident, within the “HL7 Cloud” and use open-source model to model transformation tools to constrain the RDAM to specify HL7 WG DAMs, the CIMI BMM basic meta model archetypes and patterns, DCMs detailed clinical models, FHIR FSDs structure definitions. HSPC SOLOR SNOMED extension for LOINC and RxNorm tools will manage context-specific CDEs common data elements, value and code sets across profiles and extensions, e.g., FHIR, CDA, C-CDA.

- The value proposition is that RDAM instantiated MDD model driven development tools can produce clear, complete, concise, correct, consistent and requirements-traceable implementation profiles, extensions, guides, APIs and reference-implementation artefacts to enable efficient-and-effective clinical decision support, knowledge-based-reasoning and population-based analytics. The requirements-traceable and consistent CDEs, CIMI-BMM, DCMs, etc. increase patient-value (lower cost, increase quality and safety) as consistent implementation artefacts, e.g., CDA, C-CDA, FHIR.

- As an example, the methodology might start with pre-coordinated, SDC structured data capture CIF clinical input form, which are consumed by objects, components, and services platforms. SDC depends on clear, complete, concise, correct, consistent and traceable CDEs, which are structured in accordance with use-case/scenario requirements-traceable consistent CIMI-FHIM-CQF with SOLOR-semantics. As we walk up the DIKW model-of-meaning ladder, CIMI prefers to follow the post-coordinated, DCM ANF analysis normal form path to knowledge based systems, population based analytics and business intelligence capabilities.



pilot-study comments-only HL7 ballot, including immunization, allergies and intolerances using model driven development tools producing FHIR profiles. - Target: 2018 Sep WGM reconciliation HL7-STU Ballot, including procedures, allergies, medications, problems, immunizations, results and vital signs with associated model driven development tools producing US Core FHIR, CDA, C-CDA and federal NIEM artefacts, suitable for patient-managed longitudinal electronic medical records mandated by the 21st Century Cures Act. - Target: 2019 Sep WGM reconciliation Normative Ballot complete FHIM-EHRS FM domains - Target: 2020 Sep WGM reconciliation HL7-ISO Ballot - Target: 2021 Sep WGM reconciliation Project End Date - Target: 2022


RDAM.HL7.Org

Federal Health Architecture (FHA) Federal Health Information Model (FHIM) Apache 2 license How much content for this project is already developed? >90% Was the content externally developed (Y/N)? Yes, Federal Agencies developed FHIM Is this a hosted (externally funded) project? Yes

#1316 IIM and T, #1276 HL7 EHRS-FM Release 2: Immunization Functional Profile, Release 1

Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs), Payors,Clinical and Public Health Laboratories; Emergency Services; Local and State Departments of Health; Medical Imaging Service; Healthcare Institutions (hospitals, long term care, home care, mental health),Pharmaceutical; EHR, PHR; Equipment; Health Care IT; Clinical Decision Support Systems; Lab; HIS

HHS (FHA, ONC, CDC, FDA, SAMHSA, CMS, AHRQ, NLM), DoD, VA, IPO


Healthcare Reference Domain Analysis Model (RDAM)

EHR System Functional Model and CIMI Common/Clinical Logical Information Model (IIM and T Project)

Yes


No

External vocabularies: SNOMED CT, LOINC, RxNorm for US Realm Exemplars New Product: Reference Domain Analysis Model (RDAM) Other stakeholders, vendors or providers: US Federal Agencies
Organization & Realm

Realm Specific - Enter "U.S." or name of HL7 Affiliate below

Universal, with US Realm exemplars.
People

Steve Hufnagel & Nona Hall



Clinical Interoperability Council Work Group

Clinical Information Modeling Initiative Work Group; Electronic Health Records Work Group; Modeling and Methodology Work Group; Structured Documents Work Group

Status & Dates

Active

On Hold

11/10/2017

01/01/2021

2021 Jan WGM/Ballot

01/01/2021

2021 Jan WGM/Ballot

Approvals



Pending






System Info



View Ballot Items (with NIBs)




Return to Search