CIMI Practitioners' Guide

<<<CIMI Practitioners' Guide, May 2017-Draft, is under construction>>>

Introduction

• Facilitators: Nona Hall and Steve Hufnagel
• Objective: Maintain and communicate current information with CIMI members, partners and stakeholders.
• CIMI Co-chairs: Stan Huff, Linda Bird, Galen Mulrooney, Richard Esmond
• Practitioners' Guide URL: http://wiki.hl7.org/index.php?title=Clinical_Information_Modeling_Initiative_Work_Group
• CIMI WIKI URL: http://wiki.hl7.org/index.php?title=Clinical_Information_Modeling_Initiative_Work_Group
• CIMI Web Site: http://opencimi.org/

Acknowledgement

Collaboration that Grows with a Strong SME Base

• the contents of this Guide came from
  • CIMI Co-Chairs
  • Linda Bird BIT, IHTSDO
  • Galen Mulrooney, FHA and VA contractor
  • Richard Esmond, PenRad LLC
  • Stanley Huff, Intermountain Healthcare
• Members of the following SDOs
  • IHTSDO, POC: Linda Bird BIT
  • HL7 Work Groups (PC, CDS, CIC, EHR, SOA, Vocab)
  • The Open Group Healthcare Forum, Jason Lee POC
  • ISO/CEN, POCs: Gerard Freriks, William Goossen, Gary Dickinson
• Federal Agency staff and contractors
  • Department of Defense
  • Veterans Administration
  • Interagency Program Office
  • ONC OST and Federal Health Architecture
  • MITRE
• Members of the following Healthcare Organizations** Intermountain Healthcare
  • PenRad, Inc., Results4Care
  • HSPC and other interested parties
• Faculty, Staff and Students
  • The University of Utah

Our IT objective is to make the appropriate data available when it is needed, where it needed and how it is needed. We plan to integrate existing models, with semantically-consistent computable-data, including provenance data (who, what, when, where, why, how) across different platforms, e.g., population health, Clinical Decision support, EHR patient documentation systems, etc. using tooling to generate various implementation styles, including HL7 Fast Healthcare Interoperable Resources (FHIR).

Problem: Skyscraper Analogy

• BLUF (Bottom Line Up Front): As is: no shared terminology content (floor 1), no shared information models (floor 2), then they are building from the 3rd floor up. No shared value from the 3rd floor up. 
• Future State: shared terminology content (floor 1), shared information models (floor 2), sharable value built on floors above. 
• In a perfect world the following would be done concurrently and with close collaboration
  • Recommended Solution Part 1: We integrate SOLOR into FHIM, Concurrently, resolving SOLAR gaps
  • Recommended Solution Part 2: We integrate CIMI, FHIM and CQF 
  • Recommended Solution Part 3: We follow Agile refinement cycles through pilots and implementations
  • Recommended Solution Part 4: We develop adequate documentation, test cases, fixtures and supporting resources
• In the real world, we are asking:
  • the Federal Partners to provide resources to make efficient and effective progress in the near, mid and long term.
  • the Federal Partners to work together to deliver—in an ongoing way—a single integrated terminology system (SOLOR), that meets all US regulatory equirements, while simplifying implementation for developers.
  • the FHA to facilitate Federal Partner governance and configuration management of this work
  • The ONC OTS to endorse this initiative and facility resources
  • We are asking the IPO to provide coordination and facilitation
  • We are asking HL7 to facilitate
    • international, commercial and academic peer review and
    • ballot governance and configuration management.
    • Coordination of an ISO ballot (this will be several years from now)
• Analogy of the Challenge: Today’s efforts occur as if we’re always trying to build the ultimate skyscraper, starting on the 3rd Floor.
  • Inconsistencies exist/become extended producing transformational (mapping) efforts = models, models everywhere
  • The problem is that today’s healthcare systems do not capture information and its context consistently, and consequently, they cannot easily share-or-merge information from different sources to create a computable operational-picture (aka longitudinal patient-records, care plans, clinical knowledge and other shared healthcare information across time, multiple care locations and differing contexts).
  • If continued and unchecked, even the best of implementation accelerators, like FHIR with its extensions and profiles, allow far too much implementation variation; where, each project often creates, from scratch, yet, another information model, e.g. through a mapping exercise.
  • The missed opportunity is to leverage a shared logical Reference Information Model minimizing the duplicative-work, avoiding inconsistencies and avoiding the necessity to engage these SMEs, these resources and our larger community. This is the “models, models everywhere phenomenon ”.
  • As an example, Standards, in general, use different formats and rules for ‘simple’ things like: name, address, dates. Resulting in EHR-systems that after decades cannot uniformly exchange this ‘simple’ ubiquitous data; let alone ‘complex’ clinical health data.
    • the HL7 EHR Interoperability workgroup, in its analysis “Record Entry Lifecycle Event Metadata using FHIR,” found substantial provenance (who, what, when, where and how) inconsistencies among FHIR resources .
      • http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG
    • The SOLOR/LEGO team found FHIR tries to define things such as attributes for anatomy, that are not based on a particular model of anatomy, and thus you get semantic overlap, with the burden of reconciliation, which may not even be possible, if left to the end user.

SOLOR Standardizes Terminology

• Gentamicin is an example of the non-consistant terminologies
• Why we can simplify now?
  • Licensing models have changed so we can implement native standards
  • LOINC and SNOMED are integrating content via a shared logical model
  • RxNorm can be extracted into a shared logical model
  • SNOMED + LOINC + RxNorm + post-coordination provides comprehensive coverage for typical clinical data representation requirements 
• In distinguishing terminology and model capability: Concrete Example
  • In SOLOR / RxNorm = description of dosage of penicillin and what it means;
  • With the use of the FHIM it will tell you if its part of substance administration and/or adverse event.
  • RxNorm doesn’t do that
• CIMI can offer a DCM that providers can use in the detailed execution of a particular domain

Federated Information Model Development

Consistent FHIR extensions-and-Profiles can be achieved by:

• Following CIMI Principles and Reference Architecture (see principles and Architectural Framework sections)
• Using Model Driven Development tools, such as SIGG (MDHR, MDMI) (see tools section)
• Governance and Configuration Management of artefacts. (see Governance section)

Federated Software Development

• Ideally, implementers can meet Project Needs by reusing FHIR Extensions and Profiles, from a FHIR Artefact repository
• Alternately,
  • CLIM models can be refined to meet requirements,
  • Tools (e.g., SIGG) can use CLIM models to create needed implementation FHIR artefacts.

Federated FHIR Extensions-and-Profiles Development-Lifecycle

Scope

CIMI considers its work in the "Universal Realm”; where, current work might be considered "US Realm".

1. CIMI uses International Standards, when available.
2. CIMI is using a SNOMED extension including LOINC and RxNorm (SOLOR).
   1. SNOMED and LOINC are used beyond the US, such as Canada and UK.
   2. RxNorm is the most international medication terminology available
   3. RxNorm includes chemical ingredients, which are international; where, US pharmaceutical units, packaging and manufacturers can be replaced by foreign equivalents
3. Technically, CIMI's SOLOR semantic-bindings are completely defined; where,
   1. SOLOR follows the SNOMED observation model with explicit context expressions (e.g., body site)
   2. CIMI's SOLOR terminology bindings are exemplars; where, incomplete exemplars lead to inconsistent implementation artefacts, such as FHIR or CDA profiles and extensions.

Situation

• CIMI's Goal is to help people live the healthiest lives possible,
  • by enabling a “Learning Health System” supporting areas such as, but not limited to, Precision Medicine, CDS, Genomic/Omic, EHR and Ancillary systems; where,
• CIMI's Approach capitalizes on the inroads made with the exchange of data, standards and standards adoption, and,
  • brings back a focus on data in order to make additional and necessary advancements and
  • requires data that is computable, usable, extensible, and interpretable across disparate systems - a state that currently does not exist.
• CIMI's IT Objective is to make computable healthcare-data efficiently-and-effectively available when it is needed, where it needed and how it is needed to
  • integrate existing healthcare-related information models, with semantically-consistent data,
    • including appropriate provenance data (who, what, when, where, why, how)
    • to support development (implementation and test) projects
  • support Model Driven Development pilot-projects across healthcare related platforms,
    • using seamless model-instantiated tooling to generate implementation profiles and extension (e.g., FHIR, CDA, etc.)
  • promote the development and use of free and open models, that are foundational to computable-interoperability
  • maintain a clean separation of clinical model semantics using a SNOMED extension including LOINC and RxNorm (SOLOR)
  • build upon and improve existing work; in particular US Core and FHIR core
  • establish the Integration of SOLOR+FHIM+CIMI+CQF+US Core as the enabling foundation for
    • Detailed Clinical Models (DCMs) for semantic-interoperability and
    • Knowledge Artifacts (KNARTs) for analytics and reasoning
  • align models and tooling to seamlessly extend the usability of these assets
  • use model-instantiated tools to generate consistent-and-traceable standards-and-implementation artifacts
  • advance in constructive steps through pilots and agile development-cycles of build, test, learn, plan and deploy cycles
  • support pilot projects with appropriate Communications and Governance strategies

Charter

CIMI will coordinate activities with other workgroups to establish aligned logical models and standards that support computable data-sharing in support of consistent health processes and achievement of improved patient outcomes. This coordination will encourage harmonized standards to manage data capture, clinical workflow and interoperability.

Products, Benefits and Contributions

The CIMI workgroup will coordinate with relevant groups related to

1. Harmonized healthcare logical models, resulting in consistent computable implementation standards, profiles, extensions and guides to enable improvement in health care processes and patient health outcomes.
2. CIMI curated Architecture (Principles, Reference Archetypes, Semantic-Anchor Patterns, Processes), documentation and training.
3. Model driven development methodologies and tools related to HL7 standards and artifacts.

Projects

Plans

Principles

<<< work in progress >>>

ASSERTION vs. EVALUATION_RESULT criteria

1. 'Reasoning' vs. 'Finding', 'Subjective' vs. 'Objective', 'Fact-ish' vs. 'Judgement-ish' categories work > 80% of the time; but, they are not reliable criteria for a small set of "edge cases'.
   1. In most cases it is obvious, when to use ASSERTION (e.g., 'Reasoning', 'Subjective', 'Judgement-ish' things, such as DIAGNOSIS, PROBLEM, COMPLAINT, FAMILY_HISTORY)
      1. The Patient DISCHARGE_DIAGNOSIS is ... (implying the set of findings defining the DISCHARGE_DIAGNOSIS)
      2. John has blue eyes
   2. In the small number of cases, where it is not obvious when to use ASSERTION, CIMI prefers
      1. ASSERTIONS be used when the answer to an EVALUATION_RESULT is 'Present' or 'Absent', 'Yes' or 'No', 'True' or 'False', etc.
   3. Although theoretically possible; but for practical implementation reasons, CIMI does not support round-trip conversion between EVALUATION_RESULT and ASSERTION structures, as shown by the set of ATTRIBUTE vs. EVALUATION_RESULT attributes shown above.

Legends

• UML models are being used for CIMI BMM; where, UML relationships are shown above:
• Many figures were done in the FreeMind open-source Mind Maps; where, the legend, download information and basic structure are given below.

Architectural Framework

• Reference: Jan 2017 CIMI Architecture, Methodology and Style Guide from Ballot

The CIMI Architecture consists of the three Basic Meta Model (BMM) Reference Model layers and two Archetype layers shown here.

The CIMI Reference Model is expressed using the OpenEHR Basic Metamodel (BMM) Language. The archetype layers are expressed using the OpenEHR Archetype Definition Language (ADL). While reference model modules define classes, attributes, and class hierarchies, the archetype layers only specify progressive constraints on the reference model but do not introduce new classes, attributes, and class-class relationships.

1. The CIMI Core BMM Reference Model provides the core granularity of the CIMI model and introduces its top-level classes such as the DATA_VALUE class and the LOCATABLE class. This reference layer module defines the CIMI primitive types and core data types.
2. The CIMI Foundational BMM Reference Model is closely aligned to ISO13606 and the OpenEHR Core Reference Model. It defines foundational CIMI clinical documents and clinical record patterns. It also introduces the PARTY, ROLE, and PARTY_RELATIONSHIP patterns and defines the top-level CLUSTER class for complex CIMI type hierarchies. CQI Knowledge Artifacts may also leverage this layer.
3. The CIMI Clinical BMM Reference Model consists of the classes derived from existing CIMI archetypes, the FHIM, QUICK, vMR, and QDM. This layer defines the set of 'schematic anchors' (to borrow Richard Esmond's term) or core reference model patterns from which all CIMI archetype hierarchies and ultimately Detailed Clinical Models (DCMs) derive. Requirements for this layer come from FHIM, vMR, QDM, QUICK, FHIR US Core, SDC, etc...
   1. The 'goal' is to define the reference models with low FHIR transformation costs where feasible noting that we will inherently have some divergence due to the different requirements underlying both models.
   2. Galen points out that, FHIM’s expressivity will not carry over to CIMI DCMs given the models' different requirements (e.g., FHIM includes finance and accounting).
4. The CIMI Foundational Archetype Patterns define the top-level constraints on the CIMI Reference Model. These typically consist of attribute formal documentation and high level attribute semantic and value set bindings. Archetypes at this layer will provide the foundational requirements for future US Core and QI Core profiles. Future pilots will explore the generation of US Core and QI Core archetypes from these CIMI archetypes.
5. The CIMI Detailed Clinical Model Layer represents the set of leaf-level constraining profiles on the foundational archetypes to create families of archetypes that only vary in their finest terminology bindings and cardinality constraints. This layer is intended to support clinical interoperability through an unambiguous specification of model constraints for information exchange, information retrieval, and data processing.

From layers 1-5, we define the set of transformations (e.g., SIGG (MDHT, MDMI)) to generate the corresponding FHIR profiles including the US Core and QI Core profile sets. Note that FHIR profiles can be generated from the various levels of the archetype hierarchy depending on requirements. The lower down in the hierarchy, the more prescriptive the profile is in terms of constraints. Much like ADL Archetypes, FHIR profiles can be layered.

It is important to note that some FHIR profiles may be derived from the Foundational Archetype Layer (e.g., US Core, some QI Core profiles, some CQIF profiles on PlanDefinition, Questionnaire and ActivityDefinition, etc...) and others from the DCM Layer (e.g., bilirubin, HgA1c, etc...). In other words, the arrow for FHIR Profiles stems out of the outer box rather than the last of the inner boxes (the DCM box).

BMM Hierarchy

The CIMI Reference Model is done in UML and contains three Basic Meta-Model (BMM) hierarchical layers of Pattern structures aka Clinical Pattern structures:

1. Each Pattern contains a single class or group of related classes that can be constrained by ADM or AML archetypes in order to define a family of related and consistent Detailed Clinical Models (DCMs), such as types of
   1. Lab Orders,
   2. Procedures,
   3. Skin Wounds, etc.
2. The three layer CIMI Reference Model contains modular sets of (Clinical) Patterns, which can be used to create leaf-level DCMs:
   1. Core BMM Reference Model Level-1 defines core types and two root classes:
      1. Data Types
      2. Data Value Types
      3. LOCATABLE class, from which the majority of CIMI domain classes derive and
      4. ASSOCIATION_CLASS from which we derive
   2. Foundational BMM Reference Model Level-2 defines the foundational underpinnings of the CIMI model.
      1. This structure aligns with the ISO 13606 EHR and the OpenEHR Reference Models.
      2. The Foundation Reference Model defines the top-level hierarchies to derive lower-level classes and clinical patterns:
      3. CLUSTER,
      4. COMPOSITION,
      5. CONTENT,
      6. PARTY,
      7. ACTOR,
      8. ROLE,
      9. PARTICIPATION, and
      10. PARTY_RELATIONSHIP.
   3. Clinical BMM Reference Model Level-3 builds upon the Level-1 Core and Level-2 Foundation to specify the Level-4 CIMI Preferred Archetypes aka Semantic Anchors for DCMs.
3. The CIMI Core and Foundational reference modules provide the core semantics, structure, and granularity of the CIMI model.
4. the CIMI Clinical Reference Model module provides an intuitive domain semantic-anchor view for DCMs.
5. This modular approach allows for
   1. additional, domain-specific Level-3 Reference Archetypes and Level-4 Patterns
   2. alternate iso-semantic patterns to be introduced at the appropriate level in the model.
   3. Over time, it can be expected that the layers will hierarchically become more stable
      1. Level-1 Core BMM purposely being most stable.
      2. Level-2 Foundation BMM might change, such as when new underlying taxonomy-structures are added.
      3. Level-3 Clinical BMM might change, such as when new clinical disciplines and data-structures are added.
      4. Level-4 Reference Archetypes changing, such as when new domains are added.
      5. Level-5 DCMs under a constant-state of flux, such as when new information-exchange requirements are added.
   4. If change occurs, it should be backward-compatible with-respect-to lower layers and legacy-DCMs.

Archetype Hierarchy

The CIMI archetype hierarchies form the second part of the CIMI model. These hierarchies serve two primary purposes:

1. They enable the progressive application of constraints on reference clinical patterns including the specification of terminology constraints that assign formal meanings to both model attributes and their range.
2. They allow for the definition of sets of models whose members vary solely based on the constraints they apply to a common underlying reference model pattern. Archetypes can specialize more general archetypes in ADL. They do so by progressively constraining the underlying reference model pattern in a manner that is consistent with and not contradictory to the constraints specified in archetypes higher up in the hierarchy. Examples of constraint refinements are listed below:
   1. A top-level archetype restricts the range of Ingredient.substanceCode to the set of all concepts subsumed by the SNOMED CT concept ‘Pharmaceutical/biologic product’. A downstream specialization of this archetype restricts the Ingredient.substanceCode to ‘Metoprolol’.
   2. A top-level archetype assigns the SNOMED CT concept ‘Procedure site (attribute)’ as the semantic binding of the attribute Procedure.site. A downstream specialization of this Detailed Clinical Models (DCMs), highly specific models that enable the interoperable exchange of clinical information, typically reside at the leaf-level of CIMI archetype hierarchies. The cumulative constraints applied on a DCM are intended to be precise enough to allow for the unambiguous exchange of interoperable clinical information and thus constitute highly specific constraints on the underlying reference model pattern.

Introduction

Core Modeling Principles

The following principles guide CIMI’s modeling approach:

1. CIMI favors a design by specialization over a design by constraint approach. This approach is summarized as follows:
   1. if a class has a number of specializations, each requiring a different set of attributes, common attributes are represented in the parent class while child attributes are added to the appropriate specializations. An alternative approach may be to include the union of all attributes in a single class and constrain attributes out at the archetype level.
      1. The former approach is preferred over the latter except in certain cases.
      2. For instance, if a specialization differs from its parent by a single attribute, the inclusion of the attribute in the parent class may be preferred over the creation of a new class.
2. CIMI generally favors the definition of explicit attributes in the reference model over the slicing of lists in archetype definitions. The attribute subset pattern is achieved by defining a multi-cardinality attribute in the reference model and specifying subsets of the list elements in archetypes.
   1. For instance, one may specify that the LOCATABLE class, the supertype of all CIMI classes, has an attribute called participation of type PARTICIPATION and whose cardinality is 0..*.
   2. In an archetype, one may then constrain the participation attribute in the following manner.
      1. The first element of the list represents the author.
      2. The second element represents the data enterer.
      3. The third element represents the location where the authoring activity took place.
      4. The fourth element of the list represents the system where the information was recorded.
      5. While such subsets are allowed in both UML and ADL, CIMI generally avoids their use and favors the explicit representations of such subsets as full-fledged attributes in the model. For instance, CIMI explicitly adds an attribute for the
         1. agent of an activity,
         2. the location of an activity,
         3. the entity involved in the performance of the activity, and so on.
   3. The motivation for this approach stems from the fact that CIMI is a logical model rather than a physical model and favors greater reference model expressivity over physical patterns that enable better economies of structure.
3. CIMI may offer a number of variants for a given attribute.
   1. For instance, CIMI defines bodyLocation: AnatomicalLocation and bodyLocationPrecoord:
      1. CODED_TEXT to support both a coded and a post-coordinated anatomical location.
   2. Similarly, Assertion.dueToCode:CODED_TEXT and Assertion.dueTo:
      1. ClinicalStatement allow users to link an assertion to another clinical statement or simply define its type to be CODED_TEXT.
   3. Archetypes will need to specify a single property in such cases in order to avoid semantic collision.

Terminology Alignment

Information models are often developed independently of clinical ontologies. As a result, many information models align poorly with the terminologies or ontologies upon which they ultimately depend for their formal semantics. Moreover, by not explicitly specifying the model’s semantics, the meaning of the model is left open for interpretation during implementation further hindering interoperability. In an effort to better align models of use with models of meaning, the Clinical Information Model is designed to align closely with the SNOMED CT Concept Model wherever such an overlap exists. In CIMI, the model’s formal semantics are specified through terminology bindings defined at the archetype level. These terminology bindings occur at three levels:

1. To define the relationship between the attribute and its class. CIMI model attributes are aligned with their corresponding SNOMED CT concept model attributes when such a correspondence exists.
   1. An example in the CIMI Finding Assertion Model, the body site data element aligns with the SNOMED CT concept 363698007|Finding site (attribute)|from the SNOMED CT Clinical finding concept model.
2. To define the semantics that the attribute can contain. CIMI model attribute ranges are aligned with the ranges specified for their corresponding SNOMED CT concept model attribute when such a correspondence exists. Using the example above, the range for the Body Site is the range defined in the SNOMED CT technical guide for Finding Site Anatomical or acquired body structure | 442083009 (<<)
3. To define the post-coordinated representation of some of the semantics of the archetype using the SNOMED CT concept model. CIMI preferred models favor post-coordination in the model rather than in the terminology.
   1. In some cases, CIMI archetypes may be associated with SNOMED CT expressions, provided that the expression conforms to the constraints specified for the flattened archetype.
   2. For instance, a CIMI Clinical Statement may be associated with a SNOMED CT Situation with Explicit Context expression or a pre-coordinated code.
   3. We are currently investigating the use of SNOMED CT Templates for such bindings

Core BMM

The CIMI Core BMM Reference Model provides the core granularity of the CIMI model and introduces its top-level classes such as the DATA_VALUE class and the LOCATABLE class. This reference layer module defines the CIMI primitive types and core data types.

Foundation BMM

The CIMI Foundational BMM Reference Model is closely aligned to ISO13606 and the OpenEHR Core Reference Model. It defines foundational CIMI clinical documents and clinical record patterns. It also introduces the PARTY, ROLE, and PARTY_RELATIONSHIP patterns and defines the top-level CLUSTER class for complex CIMI type hierarchies. CQI Knowledge Artifacts may also leverage this layer.

Clinical BMM

• The CIMI Clinical BMM Reference Model consists of the classes derived from existing CIMI archetypes, the FHIM, QUICK, vMR, and QDM. This layer defines the set of 'schematic anchors' (to borrow Richard Esmond's term) or core reference model patterns from which all CIMI archetype hierarchies and ultimately Detailed Clinical Models (DCMs) derive. Requirements for this layer come from FHIM, vMR, QDM, QUICK, FHIR US Core, SDC, etc...
  • The 'goal' is to define the reference models with low FHIR transformation costs where feasible noting that we will inherently have some divergence due to the different requirements underlying both models.
  • Galen points out that, FHIM’s expressivity will not carry over to CIMI DCMs given the models' different requirements (e.g., FHIM includes finance and accounting).

Clinical_Statement Overview

Clinical_Statement (Top View)

Clinical_Statement-Topic

Clinical_Statement-Association

Clinical_Statement-Context

Clinical_Statement-Data_Packages

Foundation Archetypes

CIMI_Foundational_Architype_Patterns_Mind_Map.jpg

• The CIMI Foundational Archetypes Patterns define the top-level constraints on the CIMI Reference Model. These typically consist of attribute formal documentation and high level attribute semantic and value set bindings. Archetypes at this layer will provide the foundational requirements for future US Core and QI Core profiles. Future pilots will explore the generation of US Core and QI Core archetypes from these CIMI archetypes.

Detailed Clinical Models (DCMs)

• The CIMI Detailed Clinical Model Layer represents the set of leaf-level constraining profiles on the foundational archetypes to create families of archetypes that only vary in their finest terminology bindings and cardinality constraints. This layer is intended to support clinical interoperability through an unambiguous specification of model constraints for information exchange, information retrieval, and data processing.

Skin-Wound DCM

• 2917-02-09-1000 ET Patient Care Workgroup Telecom
• Attendees: Jay, Susan, Richard, Claude, Steve

1. Skin Wound content & scope
   1. Braden
   2. Skin Assessment
   3. Wound Assessment, with Pressure Ulcer specialization
   4. No Skin Risk Assessment (out of scope)
2. Schedule
   1. Feb 13: Requirements UML and Terminology spreadsheet finished
   2. Feb 13 to Mar 3 - VA verification and validation of spreadsheet
      1. Diagram
      2. Data-Element and Value-Set Spreadsheet
   3. Mar 8: Presented at LOINC conference by Susan

UML

Mind Map

Tools

FHA sponsored FHIM and SIGG (MDHT and MDMI) have the capability for generating FHIR implementation models. With the adoption of CIMI information requirements (informed by FHIM), SIGG can generate CIMI archetypes and FHIR Structure Definitions (FSDs) and compare them to their source archetypes to confirm the process.

• FHIM & MDHT could then serve as one of the “translator” tools.
• MDMI can serve as one of the "mapping" tool.
• Part of the tool authoring activity is to add new SOLOR terminology content as necessary to meet requirements derived from existing specifications; where,
  • there is a versioning and publication step between the SOLOR box/layer and the CLIM box/layer. 
  • there is a versioning and publication step between the CLIM box/layer and MDHT/MDMI; where, the arrows metaphor conveys the publication step. 
• IHTSDO workbench with ISAAC plugin authoring tools are in the SOLOR box/layer. 
• ADL workbench, enterprise architect UML tool, etc. need to be able to import SOLOR content, so they can build the profiles using the SOLOR terminology foundation…

• SOLOR (SnOmed LOinc, Rxnorm) terminology authoring project can provide the terminology foundation for FHIM, CQF, DCMs and FHIR profile and extension development. SOLOR creates Lightweight Expression of Granular Objects (LEGOs) with description-logic semantics aka SNOMED expressions; where, SOLOR can be treated as a single, coherent terminology systems that covers essential healthcare domains.
• FHIM is FHA's Federal Healthcare Information Model, which is a high-level logical healthcare model, which covers approximately 36 clinical domains and has been vetted by Federal Agency SMEs and clinicians. Details are available at www.FHIMS.org
• CIMI is Clinical Information Model Initiative which defines Terms-of-Reference AKA Principles, modeling style guidelines, a CIMI Core Reference Model, Reference Archetypes, Patterns and Detailed Clinical Models (DCMs); where, a CIMI Model is a clear, complete, concise, correct and consistent logical semantic-and-syntactic description of a healthcare concept, which can be instantiated as a computable implementation object that is interoperable among systems.
• CQF is Clinical Quality Framework to support Continuous Quality Improvement (CQI) with a Quality Improvement and Clinical Knowledge or QUICK data model, Clinical Quality Language (CQL) supporting clinical decision support (CDS) and clinical quality measures (CQM).
• FHIR defines a set of "Resources" that represent granular clinical concepts; where, CIMI's CLIM and tooling can be used to create consistent FHIR and other implementation paradig profiles and extensions. SIGG creates FHIR Structure Definitions (FSDs); where, FHIR tools can convert FSDs into FHIR Resource extensions and profiles. FHIR Core Resources, Profiles and Extensions can be managed in isolation, or aggregated into complex documents.

The following is a list of authoring tools that might be pertinent to investigate as we develop CIMI tooling:

• Terminology Browsers
  • IHTSDO browser
• Value Set Editors
  • art-decor
  • Apelon
  • National Library of Medicine Value Set Authority (VSAC)
• CIMI Model Authoring Tool
  • ADL 2.0 web based archetype and template editors
  • Results 4 Care tool for online authoring of clinical content for Detailed Clinical Models
  • Results 4 Care UML template and Model creation / validation tool for Detailed Clinical Models
  • [Spanish ADL Authoring Tool from Spain (Gerard Freriks to provide info)]
• FHIR Profile Editors
  • Furore Forge FHIR profile editor
  • Model Driven Health Tools (MDHT)
• CIMI to FHIR Profile Conversion
  • Model Driven Message Interoperability
  • FHIR "logical model" work
• CIMI (mini)RM UML
  • Sparx Enterprise Architect Project 3.0.5 EAP
  • BMM Extension

References

• Jan 2017 CIMI Architecture, Methodology and Style Guide from Ballot
• Clinical Element Models (CEMs)
  • CEM Browser
  • ClinicalElement CIMI Browser Models published in a web browser, processed by ADL workbench and available as ADL, XML, JSON, graphical tree, etc
  • GitHub CIMI Models managed in Git version control repository: GitHub
  • Browser pubs periodically refreshed from GitHub & may be out of synch
• CIMI Overview Slides by Stan, 5/19/16
• CIMI Reference model requirements
• CIMI Artefacts on GitHub
• CIMI Wiki@Mayo (2010-2015)
• CDS WG Wiki
• CDS Standards Wiki
• CQI wiki
• Clinical Observation Modelling by Walter Sujansky Jan 31, 2017
• EHR WG Wiki
  • EHR Immunization Profile with mapping to FHIM, CIMI, FHIR
• FHIM website
• HSPC website
• FHIR Website
• FHIR Infrastructure Wiki
• ISO 13606 Information architecture for communicating EHRs
  • Part 1: Reference Model and Data types
  • Part 2: Archetype Object Model v2.0
  • Part 3: Terminologies
  • Part 4: Information security
  • Part 5: Messaging
• ISO 13940 ConSys, ISO 13967 HISA, SIAMM
• ISO 13972 Detailed Clinical Models(DCMs)
  • Detailed Clinical Models: A Review, 2010
  • Detailed Clinical Models: Representing Knowledge, Data and Semantics in Healthcare Information Technology
• MDHT website
• MDMI website
• MAX Artefacts
  • MAX Video
• Open Group Healthcare Forum
• OpenEHR and ADL language and tools
  • OpenEHR Reference Model (RM)
  • OpenEHR ADLWorkbench tool
  • OpenEHR Clinical Knowledge Management (CKM) repository
• Patient Care Wiki
• SNOMED Training Materials
• STAMP Overview, 1/15/17
• VOCAB Wiki

Jan - Sept CIMI Investigative Study / Task Force Supporting documents

• HL7 Project Scope Statement
• Briefing Slides
• Briefing Slides Notes Pages
• Aug 2016 Preliminary Report
• Aug 2016 Technical Forum Summary
• Sep 2016 Final Report
• Work Breakdown MPP
• Work Breakdown PDF
• Work Breakdown XLSD
• CIMI Practitioners’ Guide