cimi/ihtsdo dcm tooling ecosystem thoughts thomas beale openehr foundation stan huff, md...
TRANSCRIPT
CIMI/IHTSDO DCM tooling ecosystem thoughts
Thomas BealeopenEHR Foundation
Stan Huff, MDIntermountain Healthcare
Introduction
• These slides describe a possible semantic health modelling environment for CIMI / IHTSDO, featuring:– Next generation archetype / template tools– Integrated terminology subset authoring– Model management tool - CKM– AML-enabled UML tooling– With underlying IHTSDO terminologies, including
SNOMED CT and LOINC
Introduction
• They also describe the possible technical relationships between central CIMI artefacts and downstream environments.
• Getting to this or a similar tooling environment will require investment and commitment of multiple organisations.
• These slides try to provide a basis for thinking about the work tasks and scale.
Introduction
• The core formalism for archetypes and templates is the Archetype formalism. Specifications:– Archetype Definition Language 2– Archetype Object Model 2– Artefact Identification
Introduction
• CIMI archetypes are based on the CIMI reference model
• Currently available CIMI archetypes here on Github
CIMI-based
XSDs
CIMI Tooling ecosystem (summary)
CKM
CIMI Editors,Reviewers
TerminologyService
CIMI archetypes
Export
IHTSDO releases
SNOMED, LOINC etc
Valuesets
IHC CEMs
ADL Workbench (AWB)
CIMI Modellers
CIMI/IHTSDO modelling environment
FHIR
openEHR/13606 sites / vendors
(current tools)
e.g. FHIM (VHA)
Import
IntermountainLegacy environment
(current tools)
Other sites / users
Clinical Modellers Workbench (CMW)
proprietary
Other sites / usersConcrete format-based sites
AM
L Bridge
CIMI archetypes
(XMI)
CEML CEMs
openEHR /13606
Other DCMs
openEHR / 13606
archetypes
CDA tpls /v3 msgs
Modelling DevelopmentTransformation
UML/AML-tool based environment(future)
Terminology
CIMI extension
POTENTIAL PROJECT PHASES
Notes
• The following slides mention broad possible phases, each 3-6 months in duration
• Could be broken down differently / more finely
• Order is not significant here, i.e. some development can occur in parallel
Notes
• ‘CKM’ represents ‘Clinical Knowledge Manager’, a tool in use by openEHR.org, and various e-health programmes:– openEHR CKM– Nehta (Australia)– Norway MoH– Brazil National Health Terminology Centre– Slovenia MoH– Scottish NHS and UK clinical groups
• It supports team-based online development and lifecycle management of archetypes, templates and terminology subsets
AWB++, CKM, some exports
CKM
Review GovernancePublication
CIMI Editors,Reviewers
TerminologyService
Querying,Subsets,
etc
CIMI archetypes
ExportIHTSDO releases
SNOMED, LOINC etc
Valuesets
RM Manager
IHC CEMs
openEHR /13606
Technical Transform
ADL Workbench (AWB)
CIMI Modellers
CIMI/IHTSDO modelling environment
Basic bridge
XSDs, FHIR, other
openEHR/13606 sites / vendors
(current tools)
archetype
Import
CEMconv
conv IntermountainLegacy environment
(current tools)
Concrete format-based sites
openEHR / 13606
archetypes
CEML CEMs
Ref-set builder
Ref-set building
CIMI extension
XSDs
CMW core tool platform
CKM
Review GovernancePublication
CIMI Editors,Reviewers
TerminologyService
CTS2
Querying,Subsets,
etc
CIMI archetypes
ExportIHTSDO releases
SNOMED, LOINC etc
Valuesets
RM Manager
IHC CEMs
openEHR /13606
Other DCMs
Technical Transform
AWB
CIMI ModellersCIMI/IHTSDO modelling environment
FHIR
openEHR/13606 sites / vendors
(current tools)
e.g. FHIM (VHA)
archetype
Import
CEMother conv
conv
conv
IntermountainLegacy environment
(current tools)
Other sites / users
CMW
ADL/AOM tool platform
Archetype Editor
Template Editor
Terminology Query-builder
Terminology Binding
Clinical Modeller UI
proprietaryOther sites / usersConcrete format-
based sites
openEHR / 13606
archetypes
CEML CEMs
CDA tpls / v3 msgs
Ref-set builder
Ref-set building
CIMI extension
XSDs
CMW Clinical Modeller UI & ref-set builder
CKM
Review GovernancePublication
CIMI Editors,Reviewers
TerminologyService
CTS2
Querying,Subsets,
etc
CIMI archetypes
ExportIHTSDO releases
SNOMED, LOINC etc
Valuesets
RM Manager
IHC CEMs
openEHR /13606
Other DCMs
Technical Transform
AWB
CIMI ModellersCIMI/IHTSDO modelling environment
FHIR
openEHR/13606 sites / vendors
(current tools)
e.g. FHIM (VHA)
archetype
Import
CEMother conv
conv
conv
IntermountainLegacy environment
(current tools)
Other sites / users
CMW
ADL/AOM tool platform
Archetype Editor
Template Editor
Terminology Query-builder
Terminology Binding
Clinical Modeller UI
proprietaryOther sites / usersConcrete format-
based sites
IHTSDO tools
Integration?
openEHR / 13606
archetypes
CEML CEMs
CDA tpls /V3 msgs
CIMI extension
Notes
• ‘AML’ = Archetype Modelling Language, a new OMG RfP which will become a standard in ~18 months.
• AML is a UML profile based on the openEHR Archetype Object Model (AOM 2) specification.– Note that it is reference model independent and
has no technical relationship or specificity to any openEHR information model.
• AML, implemented in a UML tool will enable archetype modelling – i.e. it will bring archetype modelling to the IT mainstream
XSDs
AML bridge
CKM
Review GovernancePublication
CIMI Editors,Reviewers
TerminologyService
CTS2
Querying,Subsets,
etc
CIMI archetypes
ExportIHTSDO releases
SNOMED, LOINC etc
Valuesets
RM Manager
IHC CEMs
openEHR /13606
Other DCMs
Technical Transform
AWB
CIMI ModellersCIMI/IHTSDO modelling environment
FHIR
openEHR/13606 sites / vendors
(current tools)
e.g. FHIM (VHA)
archetype
Import
CEMother conv
conv
conv
IntermountainLegacy environment
(current tools)
Other sites / users
CMW
ADL/AOM tool platform
Archetype Editor
Template Editor
Terminology Query-builder
Terminology Binding
Clinical Modeller UI
proprietaryOther sites / usersConcrete format-
based sites
IHTSDO tools
Integration?
AM
L Bridge
UML/AML-tool based environment
AML-enabled UML tool
Generation toolsSoftware
components
S/W devs
CIMI archetypes
(XMI)
openEHR / 13606
archetypes
CEML CEMs
CDA tpls /V3 msgs
CIMI extension
REPRESENTATIVE DOWNSTREAM ENVIRONMENTS
Notes
• Here we try to show some details of how CIMI archetypes, templates and subsets could be used by downstream environments, each of which have their own reference model(s), and potentially content modelling formalisms.
Intermountain Legacy environment
CKM
TerminologyService
CTS2
CIMI archetypes
IHTSDO releases
SNOMED, LOINC etc
Valuesets
AWB
CIMI/IHTSDO modelling environment
archetype
CEMother
CMW
Developmenttools
Deploy
S/W devsXSD
Technical TransformsCEML CEMs
Intermountain legacy environment
Local customisation
ceType??
Dev’t artefacts
conv
Model-based system
app app
HIS
FHIRWS
??
CIMI extension
Archetype-based sites / vendors
CKM
TerminologyService
CTS2
CIMI archetypes
IHTSDO releases
SNOMED, LOINC etc
Valuesets
AWB
CIMI/IHTSDO modelling environment
archetype
CEMotherconv
CMWDevelopment
tools
Deploy
S/W devsXSD
Technical Transforms
Specialised archetypes
& templates
openEHR/13606 product / project environment
Local archetypes &
templating
Model-based system
app app
openEHREHR/HIS
FHIR& IHE
WS
openEHR / 13606
archetypes
API
FHIR UI
Dev’t artefacts
Runtime OPTS
openEHR.org CKM
openEHR community
Review
Nehta CKM
Moscow CKM
Norway CKM Brasil
CKM
Slovenia CKM
CIMI extension
Other environment – e.g. FHIM/MDHT/CDA
CKM
TerminologyService
CTS2
CIMI archetypes
IHTSDO releases
SNOMED, LOINC etc
Valuesets
AWB
CIMI/IHTSDO modelling environment
archetype
CEMother
CMW
MDHT
Deploy
S/W devs
MDHT/FHIM/CDA
conv
app app
HIS
CDA template
Dev tools
app
CIMI extension
Other environment – HL7v3 messages
CKM
TerminologyService
CTS2
CIMI archetypes
IHTSDO releases
SNOMED, LOINC etc
Valuesets
AWB
CIMI/IHTSDO modelling environment
archetype
CEMother
CMW
Modeller
Deploy
S/W devs
MDHT/FHIM/CDA
conv
app app
HIS
HL7 v3 RMIM
Dev tools
app
CIMI extension
CIMI FHIR environment
CKM
TerminologyService
CTS2
CIMI archetypes
IHTSDO releases
SNOMED, LOINC etc
Valuesets
AWB
CIMI/IHTSDO modelling environment
CMW
Deploy
S/W devs
FHIR artefact dev environment
FHIRconv
FHIR WS
FHIR profiles Dev tools
HIS
CIMI extension