1 / 43

HL7 version 3

HL7 version 3. HL7 v3 Implementation – an introduction. Covers HL7 v3 modeling principles, MIF, ITSs and the structure of XML instances, the RIMBAA technology matrix. Slide contents published under the Creative Commons / Attribute-Share Alike license

halle
Download Presentation

HL7 version 3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HL7 version 3 HL7 v3 Implementation – an introduction Covers HL7 v3 modeling principles, MIF, ITSs and the structure of XML instances, the RIMBAA technology matrix. Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/HL7v3_implementation.zip

  2. Agenda • HL7 v3 modeling/HDF – bottom up • MIF and the origins of schema • Conformance/validation principles • RIMBAA Technology Matrix • HL7 v3 documentation • From an implementers standpoint

  3. An introduction HL7 v3 modeling / HDF -bottom up- Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt

  4. XML example XML ITS DT R1

  5. Constrained R-MIM (a SIM)

  6. HL7 v3: Model Refinement ITS (serialization format of instances) R-MIM / SIM Serializable Model Refinement of Clinical Documents D-MIM / DIM Domain Model Pharmacy Refinement of RIM Stable model, Domain agnostic RIM

  7. Full R-MIM (a SIM)

  8. D-MIM (a DIM)

  9. RIM – Abstract Data Model

  10. RoleRelationship ActRelationship Role Participation RIM Backbone Classes Entity Act

  11. Notes • Core of all information models: Data Type specification • Dynamic model: • Interactions, message/response exchanges between 2 applications • Service layer, contractual issues, -work in progress- currently not covered by HL7 v3

  12. An introduction MIF – Model Interchange Format Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt

  13. MIF • The Model Interchange Format (MIF) • a set of XML formats used to support the storage and exchange of HL7 version 3 artefacts • the pre-publication format of HL7 v3 artefacts used by tooling. • the formal definition of the HL7 metamodel. • MIF can be transformed into derived forms such as UML/XMI or OWL.

  14. MIF documents: • Requirements-analysis related structures. • Static model related structures. • Dynamic model related structures. • Infrastructure related structures: • including data types, and vocabulary • Structures related to testing • Conformance-related HL7 structures • Publication related structures

  15. Derived forms

  16. MIF: How Is It Defined? (1) A set of XML schemas (+ Schematron):

  17. MIF: How Is It Defined? (2) • The XML schemas define the MIF language constructs as types, with the meaning of the types explained informally in annotations:

  18. A MIF model browser

  19. MIF versions • The meta-model format used for HL7 v3 models is subject to changes. • Versions: MIF 1.0 , MIF 2.1.x • Latest MIF version is generated by the latest version of the ‘v3Generator’ tool • XSLTs between MIF 2.1.x versions are shipped with the Generator tool.

  20. MIF Diff Determine differences between models

  21. An introduction ITSs and the origins of HL7 Schema Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt

  22. ITS – Implementable Technology Specification • An ITS specifies how instances of HL7 SIMs should be ‘transmitted’ • Serialization, deserialization, encoding syntax • The most commonly used ITS is the “XML ITS” • Alternatives: RIM serialization ITS (“RIM ITS”), Green CDA

  23. MIF transform toXML based ITS schemas Repository MIF MIF MIF XSLT XSLT R-MIM Pubs XML Schemas

  24. MIF Example: E_NonPersonLivingSubject Other attributes

  25. MIF Header

  26. MIF classes/associations (snippet)

  27. MIF v. XML-based ITS • XML provides a syntax only • An XML based ITS defines the set of valid XML instances for a given message type • no schema can do this • Download informative schemas with the v3 Ballot Package • Normative Edition schemas as a reference

  28. Generated XML-Schema for BirthPlace (snippet, XML ITS 1.1) XML ITS

  29. An introduction Conformance and Validation Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt

  30. A “Valid” v3 instance.. • Complies with the requirements as defined by the HL7 v3 information model • Conformance indicator, cardinality, vocabulary • Complies with additional (“contractual”) requirements • Template definitions, business rules

  31. Attribute/AssociationConformance Levels • Conformance indicator: • Optional: MAY be present, MAY be processed • Required: SHOULD be present, SHALL be supported by sender/receiver, SHALL be sent if known • Mandatory yes/no: • Mandatory*: SHALL be present, SHALL be processed/supported by sender/receiver

  32. Vocabulary: Value Sets Person name: EN [0..*] administrativeGenderCode: CE CWE <= AdministrativeGender … • Attribute is linked to Concept Domain • The concept domain is (UV Realm) represented by a value set. • The value set is based on a coding system.

  33. R-MIM (SIM).. and a Template (LIM) • Notes: • Template model must be a valid constraint on the R-MIM • -- An instance would not be able to conform to both if the above doesn’t hold true • Reminder: Clone names of classes carry no semantics (they are irrelevant)

  34. Constraint Language • To express additional constraints • OCL, ADL, Gello • No solution has been formally adopted • Typical (OCL) example: • The Person object should have either an id or a name • context Person • inv: id.hasContent or name.hasContent

  35. Example: „Valid“ CDA Document • Validates against the published XML Schema • XML Schema based validation tool • Validates against the abstract CDA model specification • Use a MIF (specification of the abstract model) based validation tool, includes conformance and vocabulary validation • Validates against requirements as specified in implementation guides • Mostly: a XML Schematron based validation tool • Validates against templates as specified in a document instance • MIF or Schema based validation tools

  36. An introduction RIMBAA Technology Matrix Slide contents published under the Creative Commons / Attribute-Share Alike license Source: www.ringholm.de/download/implementation_mechanics.ppt

  37. RIM - Abstract Data Model

  38. The RIM is “abstract” The same “instance” of information can be shared via different information interoperability paradigms • E.g. lab results can be shared • via (electronic) documents (v3 Clinical Document Architecture) • via V3 lab messages • via Web Services with v3 payloads • ..or they can be imported • In a RIM Based Application (RIMBAA)

  39. Use of V3 artefacts RIMBAA

  40. RIMBAA Technology Matrix (1/2) Persistent Representation Object Representation Serialized Representation RIM (generic) Model RIM Constrained Information Model Application specific Model

  41. UI PL RIMBAA Technology Matrix (2/2) (at a 90 ̊ angle to the matrix on the previous slide) Processing Logic Object Representation User Interface

  42. Consistentency of Models • It is beneficial to use one and the same semantic (reference) model for messaging, in-memory application objects as well as at the persistence layer. • This ensures the lowest degree of semantic loss due to mappings between data models. • Mapping of application internal data models to message models is possible if one only has to support a couple of messages

  43. Any Questions ? • Or: post your question/suggestions via • HL7 Wiki: http://bit.ly/d7tSsL • E-mail v3impl@ringholm.com

More Related