Deeper Dive for HL 7 AB 4242018 SOA

Deeper Dive for HL 7 AB 4/24/2018

SOA Cross Paradigm Interoperability PSS • • Our objective is to provide set of knowledge artifacts about mapping between different HL 7 Products and versions of HL 7 Products that will help in implementing interoperability solutions. We are not trying to create a standard. Implementation Guide - Use Case Driven – Interested Party Use Cases – VA, SAMHSA, ONC / Massachusetts ACO / e. LTSS program – Co-sponsor WG Use Cases – SD (CCDA on FHIR), CIMI • We will use same approach as the previous HL 7 SOA Cross-Paradigm Implementation Guide. VETERANS HEALTH ADMINISTRATION

MDA Tooling – Objective is no Risk to HL 7 • The tooling we use is open and transparent. – All software and content is in open source. – The “secret sauce” of the tooling, the Interoperability Model specification and the Semantic Element Exchange Repository (SEER) specification are OMG Standards. • The Project Team will work with HL 7 to ensure correct snapshots are identified and archived as part of the IG. – What is produced: (Maps, Reports) – What was used to produce them: (Software, Content) • Besides the previous HL 7 SOA IG, the tooling has been used in – – – The SAMHSA IEx. HUB and OCP The VA Standards Incubator The US IPO JET FHIR Proving Ground Argonaut Phase II Project The ONC e. LTSS project / Massachusetts Behavioral Healthcare ACO project and others VETERANS HEALTH ADMINISTRATION

Beginning of Dive: Tooling uses a Model Driven Approach • We create a Map for a format using the MDMI meta-Model. – MDMI is a component of the HSSP Roadmap. • Developing a MAP for a format is not difficult – Need to know the syntax and the meaning of the data elements – Need to associate the data element with data elements in the Semantic Element Exchange Repository (Part of the Standard). – Tooling exists to support map development and maintenance, including automation. – Tooling exists support an iterative development process: testing and SME reports. • ANY MAP works with ANY MAP. – Re-use any Map with any Map: A CCDA MAP to/from a FHIR Map, a VLER Map to/from CCDA, FHIR to/from VLER – Versioning: FHIR STU 2 to/from FHIR STU 4 VETERANS HEALTH ADMINISTRATION Point to Point Versus Any to Any

Next Level: Map Development 3 b Information models/formats: CDA/: C-CDA, FHIR, HL 7 V 2, CIMI, DAMs. Nex 2 1 MAP Repository Map Design Environment 4 a Runtime / Testing Tooling 4 b VETERANS HEALTH ADMINISTRATION Tooling for SME Reporting 3 a

Next Level: Components Map Design Environment Map Editing Tooling Model Map Automation Tooling Interoperability Model Generation of Computable Map SEER (Semantic Element Exchange Repository) Tooling to Administration of SEER The SEER provides the missing link between Formats: Semantic Understanding between different models VETERANS HEALTH ADMINISTRATION MAP Repository

Interoperability Model • • Separates Syntax from Semantics Syntax Component of the Model is used to decompose a message into its Semantic Elements or construct a message / document from its Semantic Elements There is a logical Semantic Component of the Model. The mapping is to map Semantic Elements in the format to the Business Elements in the SEER. VETERANS HEALTH ADMINISTRATION

SEER (Semantic Element Exchange Repository) • Provides Semantic Understanding between Information Models • Have extended the SEER to have a 11179 Classification System • Descriptions not enough to insure quality mappings • “Domain of Discourse” for Repository is exchange of information between different exchange formats VETERANS HEALTH ADMINISTRATION

Runtime Testing Tool Source Map Source Message Syntax Processing VETERANS HEALTH ADMINISTRATION Target Map Construct and Populate Source Logical Semantic Model Construct and Populate Target Logical Semantic Model Target Message Generation Target Message

Demonstration DEMONSTRATION VETERANS HEALTH ADMINISTRATION