cross-paradigm interoperability implementation guide for immunizations (“x paradigm”)

© 2010 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.

Cross-Paradigm Interoperability

Implementation Guide for Immunizations(“X Paradigm”)

Service Oriented Architecture

May 2013 update


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.


Service-Aware Interoperability Framework

Next draft will likely follow a straightforward crosswalk of the SAIF Enterprise Conformance and Compliance Framework


Enterprise Dimension Previous draft worked from the Immunization

DAM No reason to change that chapter (yet)


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


Runtime ServiceServiceService

Instance of ImmunizationC-CDA Doc.


Instance of Immunization

HL7 V2 Message


HL7 V2 Message

Implementation

HL7 SAIF: Information View

Use Case:Immunizations

Paradigm AParadigm A “Brute force” approach

“Brute force” approach Paradigm B Paradigm B

Implementable Perspective


Conceptual PerspectiveConceptual Perspective

Logical Perspective

Logical Perspective

ImmunizationModel C-CDAImmunizationModel C-CDA

Clinical ReferentIndex?

Clinical ReferentIndex?

SpreadsheetSpreadsheet HL7 V2IZ field list

C-CDA ModelC-CDA Model


Runtime Service

Immun. C-CDA MDMI Map


Immun. HL7 V2 MDMI Map





HL7 V2 Message


HL7 V2 Message

Implementation (not part of standard)

Applying Model Driven Message Interoperability standard to the Immunization Use Case – SAIF Information View only

Paradigm AParadigm A MDMI artifactsMDMI artifacts Paradigm B Paradigm B








Logical Perspective

Logical Perspective

Immunization DAM (not yet traceable)Immunization DAM (not yet traceable)

ImmunizationC-CDA standardImmunization

C-CDA standard

Clinical Referent

Index

Clinical Referent

Index

Immun.C-CDA MDMIModel


Immun.HL7 V2MDMIModel


HL7 V2 MDMIMap

HL7 V2 MDMIMap

Instance of HL7 V2

Message

Instance of HL7 V2

Message

HL7 V2Base Standard

C-CDA modelC-CDA model

MDMIMetamodel

MDMIMetamodel

MDMIMetamodel

MDMIMetamodel

Referent Index

Metamodel

Referent Index

Metamodel


Runtime Service








HL7 V2 Message


HL7 V2 Message

Implementation

Information View Only of HL7 SAIF

Use Case I: Cross Paradigm Immunization

Paradigm AParadigm A A MDA Approach(OMG MDMI)

A MDA Approach(OMG MDMI) Paradigm B Paradigm B








Logical Perspective

Logical Perspective

ImmunizationDAM

ImmunizationDAM

ImmunizationModel C-CDAImmunizationModel C-CDA

MDMI Meta-Model

MDMI Meta-Model

Referent Index Meta- Model

Referent Index Meta- Model

Clinical Referent

Index

Clinical Referent

Index





Use Case II: CCD / HL7 V2 Information Exchange

CCD MDMIMap

CCD MDMIMap

Instance of -CCD Doc.

Instance of -CCD Doc.

CCD MDMIMap

CCD MDMIMap


CCDModelCCD

Model

CCDMDMIModel

CCDMDMIModel

HL7 V2 MDMIMap

HL7 V2 MDMIMap

Instance of HL7 V2

Message

Instance of HL7 V2

Message

HL7 V2 MDMIMap

HL7 V2 MDMIMap

HL7 V2MDMIModel

HL7 V2MDMIModel

Use Case IV: FHIR / CCDUse Case III: FHIR / HL7

HL7 V2Base Standard

FHIR MDMIMap

FHIR MDMIMap

Instance of -FHIR Doc.

Instance of -FHIR Doc.

FHIR MDMIMap

FHIR MDMIMap


FHIRModelFHIR

Model

FHIRMDMIModel

FHIRMDMIModel

CCD MDMIMap

CCD MDMIMap

Instance of CCD MessageInstance of

CCD MessageCCD MDMI

MapCCD MDMI

Map

CCDMDMIModel

CCDMDMIModel


CCDModelCCD

Model


Computational (Behavoural) Dimension

«meet-in-the-middle» approach

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


behavioural dimension SAIF ISM: «language»/metamodels used

Enterprise dimension

Information dimension

Behavioral dimension

Engineering dimension

Technical dimension

Conceptual perspective

Logical perspective

Implementable perspective

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)


Behavioral dimension SAIF ISM: some detailsBehavioral Dimension

Paradigm A X ParadigmsInteroperability Models

Paradigm B

Conceptual perspective

Logical perspective

Implementable perspective

Immunization DAMImmunization DAM

BPMN 2 Process Models from storyboardsBPMN 2 Process Models from storyboards

Identify Capabilities (SoaML)Identify Capabilities (SoaML)

RLUS

CDSS

IXS CTS2

HCSPDIR

Mapping capabilities with HSSPS Services

inventory

Mapping capabilities with HSSPS Services

inventory

HSSP Inventory

X Paradigm Services Architecture ModelX Paradigm Services Architecture ModelParadigm A

Specific modele.g. HSSP WS*

Paradigm A Specific modele.g. HSSP WS*

Paradigm BSpecific model

e.g. IHE TF

Paradigm BSpecific model

e.g. IHE TF

Mapping interfaces(fUML ModelI)

Mapping interfaces(fUML ModelI)

Paradigm A Specificification

Paradigm A Specificification

Paradigm B SpecidicationParadigm B

SpecidicationMapping

(fUML/ALF script)Mapping

(fUML/ALF script)

Protocol Bridging Impl.Service/message protocol A

Service/message protocol A

Service/message protocol B

Service/message protocol B


Technical Dimension

?Out of scope?


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?

cross-paradigm interoperability implementation guide for immunizations (“x paradigm”)

Documents