CRM Taskforce Meeting Minutes - 15 March 2012

From CIMI
Jump to: navigation, search

Attendees

  • Linda Bird (Ministry of Health Holdings, Singapore)
  • Michael van der Zel (Results4Care)
  • Josh Mandel (SMArt)
  • Gerard Freriks (EN13606 Association)
  • Grahame Grieve (Health Intersections)
  • Richard Kavanagh (NHS Connecting for Health)
  • Galen Mulrooney, ONC, U.S.A.

Apologies

  • Thomas Beale (Ocean Informatics)
  • Stan Huff (Intermountain Healthcare)

Agenda

  • Criteria for consideration of starting point reference model
  • Candidate reference model consideration, against criteria
  • CIMI meeting update (presentation)
  • CIMI San Francisco meeting
  • Actions

Brief Summary

  • Criteria for consideration of starting point reference model
    • Captures the required information patterns and semantics
    • Demonstrable Computability/ Implementability/ Transformability (into ISO13606, HL7, openEHR,...)
    • Existing Tooling & Infrastructure
    • Existing Library of Clinical Models and Community
    • Simplicity
    • IP Considerations
    • Can support all use cases
  • Candidate reference model consideration, against criteria
Candidate Model /
Consideration
ISO13606 (or profile) openEHR Reference Model openEHR / ISO13606-1 Harmonisation DCM2010 (ISO13972 conformant) en13606 Association Proposal
Captures Required Information Patterns & Semantics
  • Review example models & data
  • The profile for the CIMI RM consists of: Composition, Section, Entry, Cluster, Element and indications of Data-Types
  • Review example models & data
  • Review example models & data
  • Review example models & data
  • The profile for the CIMI RM consists of: container, data, qualifier, state, context and indications of Data-Types
  • Review example models & data
  • The profile for the CIMI RM consists of: Composition, Section, Entry, Cluster, Element and indications of Data-Types
Demonstrable Computability/ Implementability/ Transformability
  • All apply
  • All apply
  • N/A
  • All apply
  • All apply
    One predefined semantic structure is used in all CIM’s, facilitating standard transformations
Existing Tooling & Infrastructure
  • Achetype/ Template Editor (RM-independ)
  • Ontological Archetype Library Manager (RM-independ)
  • Content creator community and discussion platform
  • Export to ADL, OWL, Mindmap
  • Archetype/ Template Editor (RM-depend)
  • Clincal Knowledge Manager (RM-depend/ could be adapted)
  • ADL Workbench (RM-independ)
  • Being transformed to HL7 v2, HL7 CDA, ISO13606-1
  • Adaptations of either column to the left
  • At this time EA + MDG (Model Driven Generation) (UML profile, data type) (RM-independ) + extension(validator/transformer
  • Content Creator (CC)
  • Import from openEHR, IMH CEML , CC
  • Export to openEHR ADL, HL7 CareStatement
  • Stand alone not dependent on any existing CEN/ISO or other standard.
  • Achetype/ Template/CIM Editor (RM-independ)
  • Ontological Archetype Library Manager (RM-independ)
  • Content creator community and discussion platform
  • Export to ADL, OWL, Mindmap
Existing Library of Clinical Models and Community
  • Yes
  • own collection
  • all archetypes in CKM’s
  • all Clinical Models from Intermountain/GE
  • Yes
  • No
  • Yes
  • OpenEHR and CEML models can be imported
  • Yes
  • to be produced after finalisation of this proposal and acceptance of semantic patterns
I.P. Considerations
  • Need to pay for printed material, only. Free for use
  • The RM and AOM are public open standards.
  • There are IP-rights on the paper format
  • The XML-Schema is under CC BY SA license, carrying forward the public IP of the 13606 Standard.
  • Freely available specificiations.
  • Need to consider copyright and licenses.
  •  ?
  • manual on wiki
  • templates on gforce(see MDG link some rows back)
  • models up to creators
  • The agreement is: that it will be submitted to CEN/ISO.
  • At present the IP is owned by the ERS but published according to the EN13606 Association rules.
  • Artefacts produced are licensed under CIMI control.
Simplicity (size?)/ Learnability
  • Profile will contain the minimal number of classes.
  • ±18 or 16 classes
  • 34 classes in structures,19 in ehr,21 in primitives,50 in basic
  •  ?
  • 12 classes
  • CIMI RM: 9 Classes plus 6-8 Primitives called Leaf-nodeTypes
Can Support All Use Cases
  • Yes
  • Yes
  •  ?
  • Yes
  • Yes
Other Considerations
  • This choice does not give any vendor, that is using a full standard or proprietary solution, a competitive advantage, thereby giving a perfect match to CIMI's goals
  • It is a neutral stand-alone set of components with the scope to produce CIM’s only. That can be transformed.

Summary

Candidate Model
Summary
ISO13606-1 (or variation) openEHR Reference Model openEHR/ ISO13606-1 Harmonisation DCM2010 (ISO13972 conformant) EN13606 Association Proposal
Strengths
  • Simplicity
  • Public open international standard
  • Tooling support
  • Tooling chain
  • Freely available specifications
  • Existing library of models
  • Multiple implementations
  • Harmonisation of communities.
  • Simplicity
  • Conceptual
  • Tooling support
  • Simplicity
  • Tooling support
  • CIMI meeting update (presentation)
    • Feedback requested

Actions

  • Linda Bird to:
    • Distribute minutes
  • All to:
    • Distribute examples of each approach to consider expressivity of reference model
    • Contribute to summary of approaches