MDMI_Overview_0621

Report
MDMI in Healthcare
Slide 1
Copyright © 2012, FireStar Software, Inc. All rights reserved.
The Problem
• Unaffiliated Healthcare organizations cannot exchange
clinical data today.
• Not having electronic exchange of healthcare data is a
problem
 $ billions in cost
 Decrease quality of healthcare (people die)
 Stopping innovation in healthcare
• The US government understands this problem and is spending
$ Billions in an attempt to solve this problem
Slide 2
Copyright © 2012, FireStar Software, Inc. All rights reserved.
MDMI is a solution
• Simplifies this problem for each and every healthcare
organization
• Significantly lowers the economic model for everyone; from
the largest to the smallest. Everyone can participate.
• Provides an environment designed to accommodate change
and dramatically lower the cost of change
Slide 3
Copyright © 2012, FireStar Software, Inc. All rights reserved.
How can MDMI do this?
• Model Driven Architecture
• It is a Standard - OMG
• Open Source – Open Health Tools
Slide 4
Copyright © 2012, FireStar Software, Inc. All rights reserved.
How does MDMI work?
•
•
The MDMI Standard is a model for a Map: There are tools to create MDMI
Maps. (Declarative not Procedural)
These tools generate a MDMI Map has a clean, simple, “standard” interface to
move data back and forth with any other MDMI Map.
Source File
Source
Target
MDMI Map
MDMI Map
Source
Target
MDMI Map
MDMI Map
MDMI Runtime
“Source” Map
- Deconstructs Message (any syntax)
- Using Semantic Elements (your Data)
- Interface (move data to any MMDI map)
Slide 5
Target File
“Target" Map
- Interface (move data to any MMDI map)
- Using your Semantic Elements
- Reconstruct Message (any syntax)
Copyright © 2012, FireStar Software, Inc. All rights reserved.
Use Case – Value to Healthcare Provider
MDMI Map
MDMI Map
MDMI
Map
MDMI
MDMI
Map
ONC
TOCMap
ONCMDMI
SD
V2Map
MDMI
ONC
TOC
SDMap
RefHL7
ONC
SD
V3
V3
MDMI
Map
MDMI
Map
ONC
SD
V4 Map
HL7
V2
MDMI
MDMI
Map
NIEM
V2
VLER
MDMI Map
NIEMV3
SSA
NIEM
Provider
MDMI Map
Provider
Application
Data
File
OHT MDMI
Runtime
ONCTOC
TOCSD
Ref
ONC
ONC
TOC
SD
ONC
TOC SD
Message
Message
V2
HL7
V3SD
ONC
TOC
Message
Message
V3 V2
HL7
NIEM
VLER
Message
Message
V4
SSA
NIEM
Message
Message
V2
Message
NIEM
Message
Message
V3
Message
Value to Healthcare Provider
1. Don’t have to know as much
2. Don’t have to do as much
3. One to many: One map can talk to any other MDMI map
4. The cost of change to the Provider Organization is dramatically lowered.
Slide 6
Copyright © 2012, FireStar Software, Inc. All rights reserved.
Use Case– Value to Standards Organization
Standard
Provider 1
Provider 2
Provider 3
Provider 4
Provider N
Map
Standard
Message
Value to Standards Organization
1. Easier for community to implement your solution; including healthcare
solution providers (vendors)
2. Higher Quality: experts develop the maps and maps are reused.
3. The pain of change is dramatically reduce: Maps are versioned.
Slide 7
Copyright © 2012, FireStar Software, Inc. All rights reserved.
Use Case– Future Innovations
Provider 1
Foundation for new applications
such as a healthcare semantic
web
Provider 2
Map for
Query
Message
Message
Consolidated
Message
Message
Results
Provider 3
Provider N
Slide 8
Copyright © 2012, FireStar Software, Inc. All rights reserved.
Demonstration
Slide 9
Copyright © 2012, FireStar Software, Inc. All rights reserved.
Technical Overview
Slide 10
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 11
Copyright © 2012, FireStar Software, Inc. All rights reserved.
MDMI Referent Index
MDMI Referent Index
is
Equivalent
to
Webster’s Dictionary
Business Elements in RI are like words in dictionary
Similarities:
• The meaning of a Business Element doesn’t change
• Business Elements are not deleted
• Adding a new Business Element is not difficult.
• Adding a new Business Element doesn’t impact other words.
• Business Elements have synonyms.
Differences
• A Business Element has only and only one meaning
• There is only one Business Element for a term (semantic clarity).
• There are near-synonyms.
Slide 12
Copyright © 2012, FireStar Software, Inc. All rights reserved.
MDMI Healthcare Referent Index
• Healthcare Domain
 Leverages existing healthcare standards
• Core Components of Referent Index
 Business Elements
• Basis is HITSP C154
• Unique ID – the basis for the clean, simple, interface for the MDMI
Runtime Machine
 Data Types
• Simple data types are defined in the OMG MDMI Standard and
are based on ISO standards.
• There are complex data types. Reference Model is for the
Healthcare MDMI Domain Referent Index is HL7 CDA R1 Data
Types with extensions for HL CDA R2 Data Types.
• Published on OHT WIKI
 OHT MDMI RI Working Group governs MDMI Healthcare RI
Slide 13
Copyright © 2012, FireStar Software, Inc. All rights reserved.
MDMI Referent Index
Business Element Entry
The unique ID is a permanent ID
for this Element. Once defined
the element can not be deleted
but it can be made obsolete
Element Name:
Description:
Unique ID:
The Reference Datatype
represents a required standard
format for the value of the
Business Element
Reference datatype:
Near-Synonyms:
Synonyms:
Pointers to existing dictionary entries
.
.
Pointers to existing model attributes
Contained in
dictionaries or hierarchies
.
Pointers to existing message schema
.
Contained in messages formats
Contained in domain models
.
.
Slide 14
Copyright © 2012, FireStar Software, Inc. All rights reserved.

similar documents