Download presentation
Presentation is loading. Please wait.
Published byGeorgia Harrell Modified over 8 years ago
1
Transforming CIMI into SNOMED expressions Source model Target model Model mapping Source file Target file XSLT Issues
2
Source Model Systolic Blood Pressure ADL Workbench Domain view Showing exclusions from hierarchy
3
Target Model SNOMED CT Observables as of December 2014
4
Target Model Protégé view of OWL Concepts are children of SNOMED CT Concept model nodes; can be imported & classified
5
Classified (SCT imported into expression)
6
Model Mapping Observable model implicit nodes
7
Source File XML transform by openEHR Names are not pretty Concepts are provided
8
Target File Header Mostly boilerplate Namespace invented IRI is constructed Import useful for testing
9
Target File Body Legible names for sample They won’t be legible in transform Nicely grouped here Protégé OWL XML output doesn’t do that
10
Target File Terminology Binding The Range of the property is a concept We might point at a refset concept But only if the refset concept could be asserted to subsume its members
11
XSLT Header Namespace (in process) Observable model concepts for testing whether to display Key values for the model Flags for displaying inferred nodes Concept lookup Testing output
12
XSLT Header Output Header metadata Test output of key variables Namespaces
13
XSLT Root concept Use identified root ID as name in OWL Look up parent concept in Terminology section to support classification Output:
14
XSLT Inferred Concept Test for model property To be parameterized Test for whether this property’s inferred parent is already in output Write inferred parent Use generic names CIMI_SBP_specified_by CIMI_SBP_Taking One calculated field
15
XSLT Inferred Concept Output Only one calculated value “systolic_blood_pressure” White space Namespace
16
XSLT Observable Property Genericize names Design binding solution Range binding should be to CIMI URI. Current string is ac0.0.0.201
17
To Do Add terminology binding statement Add balance of observable properties Align Namespace & XML base Genericize names Complete header; resolve Protégé tagging discrepancy Inferred node is Observation procedure, not Technique Whitespace
18
Issues CIMI model properties not mature Yes they are Need to firm up observation properties, largely based on Intermountain CEM (based on several contributing standards & specifications) Keeping SNOMED CT concept model on the front burner (Really a governance question to make sure bindings are agreed & easy to know) CIMI alignment with model not mature It is; just not governed Is observable a root “about” relationship? A “code” property? SCT Observable model is not mature (New version shared in context of LOINC update) CIMI terminology binding syntax not mature Yes it is; need service Current examples are in-line Designing for URI specification; no examples yet Assume a URI is a URI Unclear how URI for refset terminology binding would work in OWL Need to assert subsumption, not membership; perhaps a terminology service can return members for closure axiom Protégé has issues with chaining inclusions (archetype, terms, SCT) Protégé or Perl conversion has issues with Foundation Metadata Concept This is intentional Perl conversion does not yet work on US edition XML transform of CIMI ADL is not normative Notes from presentation in CIMI 5/9/16
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.