Cross-Paradigm Interoperability Implementation Guide for Immunizations (“X Paradigm”)

1. Cross-Paradigm Interoperability Implementation Guide for Immunizations(“X Paradigm”) Service Oriented Architecture May 2013 update

2. Overview • The X Paradigm project is meant to provide guidance in creating deployments where many systems, new and legacy, speaking different standard protocols, must interoperate to satisfy one healthcare domain. • The immunizations domain was chosen due to its relative simplicity, existing infrastructure, and the background of some authors. The HL7 Service-Aware Interoperability Framework (SAIF) provides the theoretical and standards framework for approaching the project. • The X Paradigm Informative Ballot is an early draft released for HL7 ballot for purposes of collecting broad review and comment. The project is not complete; it is informative at this early stage.

3. Service-Aware Interoperability Framework • Next draft will likely follow a straightforward crosswalk of the SAIF Enterprise Conformance and Compliance Framework

4. Enterprise Dimension • Previous draft worked from the Immunization DAM • No reason to change that chapter (yet)

5. Information Dimension • Use of Object Management Group’s (OMG’s) Model-Driven Message Interoperability (MDMI) standard fleshed out • Presentations: • Tues Q2 PHER • Tues Q3 SOA • Wed Q4 SAIF Architecture Program

6. HL7 SAIF: Information View Use Case: Immunizations Paradigm A “Brute force” approach Paradigm B • Conceptual Perspective C-CDA Model Clinical Referent Index? • Logical Perspective • Implementable Perspective Immunization Model C-CDA Spreadsheet HL7 V2 IZ field list Implementation Instance of Immunization HL7 V2 Message • Service Instance of Immunization C-CDA Doc. Runtime Service

7. Applying Model Driven Message Interoperability standard to the Immunization Use Case – SAIF Information View only Paradigm A MDMI artifacts Paradigm B • Conceptual Perspective Immunization DAM (not yet traceable) MDMI Metamodel Referent Index Metamodel MDMI Metamodel • Logical Perspective Clinical Referent Index Immun. C-CDA MDMI Model Immun. HL7 V2 MDMI Model C-CDA model • Implementable Perspective HL7 V2 Base Standard Immun. HL7 V2 MDMI Map HL7 V2 MDMI Map Immunization C-CDA standard Immun. C-CDA MDMI Map Implementation (not part of standard) Instance of Immunization HL7 V2 Message Instance of HL7 V2 Message Instance of Immunization C-CDA Doc. Immun. HL7 V2 MDMI Map Immun. C-CDA MDMI Map Runtime Service

8. Information View Only of HL7 SAIF Use Case III: FHIR / HL7 Use Case II: CCD / HL7 V2 Information Exchange Use Case I: Cross Paradigm Immunization Use Case IV: FHIR / CCD Paradigm A A MDA Approach (OMG MDMI) Paradigm B • Conceptual Perspective Immunization DAM C-CDA Model C-CDA Model C-CDA Model Clinical Referent Index • Logical Perspective Referent Index Meta- Model HL7 V2 MDMI Model CCD MDMI Model FHIR MDMI Model CCD MDMI Model Immun. C-CDA MDMI Model Immun. HL7 V2 MDMI Model HL7 V2 Base Standard CCD Model CCD Model FHIR Model Immunization Model C-CDA MDMI Meta-Model • Implementable Perspective CCD MDMI Map Immun. HL7 V2 MDMI Map HL7 V2 MDMI Map FHIR MDMI Map CCD MDMI Map Immun. C-CDA MDMI Map Implementation Instance of Immunization HL7 V2 Message Instance of HL7 V2 Message Instance of CCD Message Instance of -CCD Doc. Instance of -FHIR Doc. Instance of Immunization C-CDA Doc. CCD MDMI Map Immun. HL7 V2 MDMI Map HL7 V2 MDMI Map CCD MDMI Map FHIR MDMI Map Immun. C-CDA MDMI Map Runtime Service

9. Computational (Behavoural) Dimension Current approach: • From conceptual perspective we start with a retro-modeling of DAM Storyboards in BPMN2 process models • From implementable perspective we start with a retro-modeling of existing specification (e.g. HSSP WS* and IHE TF) with SoaML (UML) • Executable UML (fUML/ALF) should be used to create a mapping between services operations of differents paradigms. • fUML combined with MDMI will provide the specification and the implementable specification of the adapters between two paradigms. • The ontology work we’ll be considered in the ongoing work «meet-in-the-middle» approach

10. behavioural dimension SAIF ISM: «language»/metamodels used • Business perspective • Plain english • BPMN 2 (process models) • SoaML (capability) • Platform independent • SoaML (full Services Architectures) • fUML (Semantics of a Foundational Subset for Executable UML Models) • Platform specific • fUML/ALF (Action Language for Foundational UML)

11. Behavioral dimension SAIF ISM: some details Immunization DAM BPMN 2 Process Models from storyboards Identify Capabilities (SoaML) HSSP Inventory Mapping capabilities with HSSPS Services inventory Paradigm B Specific model e.g. IHE TF Paradigm A Specific model e.g. HSSP WS* X Paradigm Services Architecture Model Mapping interfaces (fUMLModelI) Paradigm A Specificification Paradigm B Specidication Mapping (fUML/ALF script) • Service/message protocol A ProtocolBridgingImpl. • Service/message protocol B

12. Technical Dimension • ?Out of scope?

13. Open Issues • How do V3 (C-CDA) and V2 specifications fit into the SAIF ECCF (or do they?) • Is the FHIR resource being developed in PHER isomorphic with the MDMI referent index? • How does the Conceptual level (example: Immunization DAM) work back into the process?