MDMI – Technical Overview Slide 1 Copyright © 2012, FireStar Software, Inc. All rights reserved. What is MDMI? • MDMI is the OMG’s Model Driven Message Interoperability standard. It is an approved OMG Standard. • MDMI is a technical interoperability standard: MDMI is used to move information in one file format into and out of any other file format that uses the standard. • MDMI does not replace any existing industry standards. It uses and enhances existing standards in solving the problem of exchanging electronic information. • For healthcare, MDMI is an open source project in OHT and is a subproject within the OHT MDHT project. The OHT MDMI project contains software (Editor (Design Time) and Runtime), input for the model (MDMI Healthcare Referent Index), and use of the model (MDMI maps). Slide 2 Copyright © 2012, FireStar Software, Inc. All rights reserved. Requirements for MDMI Standard • • • • Must incorporate and leverage existing and future industry standards Re-engineering any legacy system is a non-starter. Must deliver high quality Must add business value: Lower the expertise and time to implement solutions. Quality of information exchange is higher. Dramatically lower the cost and time to solution for change. Slide 3 Copyright © 2012, FireStar Software, Inc. All rights reserved. MDMI – Technical Approach • MDMI is a different approach for information exchange between two parties. Instead of mapping A to B, MDMI solves the problem with two independent maps. Standard 1 MDMI Map Hospital 1 MDMI Map Standard 1 Data Message File MDMI Runtime Standard N Message Data File MDMI Map Clinic N Slide 4 Copyright © 2012, FireStar Software, Inc. All rights reserved. Standard N MDMI Map Components of MDMI • The OMG MDMI Standard MDMI Model Referent Index Slide 5 Copyright © 2012, FireStar Software, Inc. All rights reserved. MDMI Specification The core Semantic model Node +name : String SemanticElement +description : String [0..1] +name : String +minOccurs : int = 1 SemanticElement MDMIBusinessElementReference +description : String [0..1] +name : String +name : String +maxOccurs : int = 1 +elementType : MessageElementType = NORMAL 1 +description : String [0..1] +description : String [0..1] +datatype : MDMIDatatype +elementType : MessageElementType = NORMAL +location : String +reference : URI +businessElement A SemanticElement +datatype : MDMIDatatype : String +propertyQualifier : +uniqueIdentifier String [0..*] [0..1] 1 : String 1+locationExpressionLanguage +propertyQualifier : String [0..*] +referenceDatatype : MDMIDatatype and =all +multipleInstances : Boolean = false +multipleInstances : Boolean falseof its context +fieldName : String [0..1] +ordering : String [0..1] +ordering : String [0..1] 1 +oderingLanguage : String [0..1] +/isSyntacticField : Boolean =: String false[0..1] +oderingLanguage +businessElement +computedValue : MDMIExpression [0..1] +computedInValue : MDMIExpression [0..1] +computedOutValue : MDMIExpression [0..1] 0..* +children +parent 0..1 +fromMdmi 1..* +computedValue : MDMIExpression [0..1] +computedInValue : MDMIExpression [0..1] +toMdmi +computedOutValue : MDMIExpression [0..1] +parent LeafSyntaxTranslator +format : String +formatExpressionLanguage : String [0..1] 0..1 Core of the Syntax Model 0..* 1..* 1..* +context ToBusinessElement 1 ToSemanticElement +children +description : String [0..1] +relatedSemanticElement 1..* +description [0..1] 1 Mapping to the Referent Index ConversionRule +relationships +name : String 0..* +description : String [0..1] +rule : String [0..1] SemanticElementRelationship +ruleExpressionLanguage : String [0..1] +name : String +description : String [0..1] 1 +rule : String +ruleExpressionLanguage : String [0..1] +minOccurs : int = 1 +maxOccurs : int = 1 +sourceIsInstance : boolean = true +targetIsInstance : boolean = true Slide 6 Copyright © 2012, FireStar Software, Inc. All rights reserved. MDMI Referent Index MDMI Referent Index is Equivalent to Webster’s Dictionary Similarities • Business Element is equivalent to a word • The meaning of a Business Element doesn’t change • Business Elements are not deleted • Adding a new Business Element is not difficult and doesn’t impact other words. • Business Elements have synonyms. Differences • A Business Element has one meaning, and only one meaning • There is only one Business Element for a term (semantic clarity). • There are near-synonyms. Slide 7 Copyright © 2012, FireStar Software, Inc. All rights reserved. MDMI Healthcare Referent Index • Leverages and can reference existing standards Business Element Entry Element Name: Description: Unique ID: Reference datatype: Near-Synonyms: Required Information: Business Elements Reference model is HITSP C154 Data Types Simple data types are defined in the Standard and are based on ISO standards. Complex data types are allowed and the reference models are ANSI/HL7 V3 R1 Data Types and MDHT with CDA. Synonyms: Pointers to existing dictionary entries . . Pointers to existing model attributes . Pointers to existing message schema . Meta Data about Business Element: Synonyms, References to Healthcare Information Models, examples, and others . . Slide 8 Copyright © 2012, FireStar Software, Inc. All rights reserved. DEMONSTRATION Slide 9 Copyright © 2012, FireStar Software, Inc. All rights reserved.