Title: Message Development Framework (MDF)
1(No Transcript)
2(No Transcript)
3(No Transcript)
4Message Development Framework (MDF)
- Is a Methodology for building HL7 models
- Is a description for defining HL7 standard
messages - Full instruction book for HL7 participants
- Basis for member training
- Five years in development
- Continues to evolve as we gain experience
5MDF Model Relationships
Analysis
Design
Voting
Requirements Analysis Use
Case Model (UCM)
Domain Analysis Domain Information
Model (DIM)
Interaction Design Interaction Model (IM
)
Message Design HierarchicalMessageDescr
iptions (HMD)
Approval Ballots
2-nd Order 1 choice of 0-n Drug
0-1 Nursing
Reference Model Repository
RIM
6Models developed in Phases
7Models are used to build the HMD
Reference
Information Model
Interaction
Model
Common
Hierarchical
Message
Message
Element
Description
Types
8The HMD ITS then give messages
9Committee Vs. HL7 RIM
- What is the RIM?
- A HL7-wide common reference model that integrates
all Technical Committees domain views - Why do we need a common model?
- To ensure consistency of concepts
- To ensure consistent vocabulary
- How will we coordinate these efforts?
- Iterative reviews
- Harmonization meetings
- Who controls the RIM?
- The MM committee
- Format, syntax, style
- Revision histories
- The Technical Steering Committee
- Dispute resolution
- Overseer
10Reference Information Model Domain Subject Areas
- Stakeholders
- Patient
- Person
- Stakeholder
- Healthcare_service_ provider
- Organization
-
- Healthcare finances
- Patient_billing_account
- Healthcare_benefit_plan
- Guarantor_contract
- Patient_encounters
- Pharmacy_service_event
- Scheduling
- Patient_service_location
- Patient_service_order
- Patient_encounter
- Patient_service_event
- Patient_clinical_pathway
- Master_tables
- Clinical_pathway_master
- Service_catalog_item
- Observation_service_ catalog_item
11RIM Harmonization Process
Prepare RIM Change Proposal
Document Rationale for not supporting RIM change
proposal
Present RIM Harmonization Report to TSC
12Sources of Models for Harmonization
13Reference Information Model Subject Classes
- The Subject Classes are those classes in the RIM
that express the concepts that are central to
managing healthcare, e.g. Patient, Order. - Subject Classes are the focus for trigger events,
use cases application roles. - State transition modeling of Subject Classes
discovers potential trigger events. - Subject Classes capture the domain behaviors that
the HL7 committee feels are most important
14State Transition Modeling
- Identify States
- From Use Cases
- Document States
- Which attributes must be valued/unvalued?
- What are the constraints on the values?
- What associations must be established?
- What associations must not exist?
- Capture State Model
- UML State Transition Model
15Message Design
16Message Specification
17Message Information Model (MIM)
18Information Model Mapping
MIM and R-MIM
19Putting the pieces together
20How this is done
- UML and the Rational Rose toolset is used to
capture many models - HL7 has developed a large number of tools and
templates to assist in the process - Detailed tools training tutorials are held during
Work Group meetings and harmonization meetings - Model and Methods is the overseer of the tools
and the process - URL to download Tooling
- http//www.mcis.duke.edu/standards/HL7/committees
/methodology-modeling/Rose tooling/ - this includes a text file to describe what each
downloadable file is