HL7 Development Framework
Version 3.0 Model Driven Standards Development
Abdul-Malik Shakir
Principal Consultant, Shakir Consulting
October 2005
Introduction to Health Level Seven
• Health Level Seven (HL7) is one of several American National Standards Institute
(ANSI) -accredited Standards Developing Organizations (SDOs) operating in the
healthcare arena. Most SDOs produce standards (sometimes called specifications
or protocols) for a particular healthcare domain such as pharmacy, medical
devices, imaging or insurance (claims processing) transactions. Health Level
Seven’s domain is clinical and administrative data.
• Health Level Seven is a not-for-profit volunteer organization. Its members--
providers, vendors, payers, consultants, government groups and others who have
an interest in the development and advancement of clinical and administrative
standards for healthcare—develop the standards. Like all ANSI-accredited SDOs,
Health Level Seven adheres to a strict and well-defined set of operating procedures
that ensures consensus, openness and balance of interest.
• HL7 is an international community of healthcare subject matter experts and
information scientists collaborating to create standards for the exchange,
management and integration of electronic healthcare information. HL7 promotes
the use of such standards within and among healthcare organizations to increase
the effectiveness and efficiency of healthcare delivery for the benefit of all.
October 2005 HL7 Development Framework 2 of 21
HL7 V3 Message Design Information Models
• RIM: Reference Information Model RIM
Derive
• D-MIM: Domain Message Information Model D-MIM
Restrict
• R-MIM: Refined Message Information Model R-MIM
Serialize
• HMD: Hierarchical Message Definition HMD
October 2005 HL7 Development Framework 3 of 21
HL7 V3 Message Development Framework
Application Trigger
RIM
Role Event
Derive
Information Modeling
Storyboard Sender Receiver D-MIM
Triggers Restrict
References
Interaction R-MIM
Example Serialize
Interaction Modeling
HMD
Restrict
Message Design
Storyboard Content Message
Example Type
Use Case Modeling
October 2005 HL7 Development Framework 4 of 21
HL7
Development Framework
October 2005 HL7 Development Framework 5 of 21
Seven Phases of the HDF Methodology
1. Project initiation
2. Requirements Documentation
3. Specification Modeling
4. Specification Documentation
5. Specification Approval
6. Specification Publication
7. Specification Profiling
October 2005 HL7 Development Framework 6 of 21
HDF Workflow Diagram
Initiate Project
Project Charter
Specify
Requirements The HDF workflow is not a waterfall methodology.
Each phase builds upon the prior and may cause
prior activities to be revisited and their deliverables
adjusted.
Requirement
Specification
Reference
Models
Prepare Specification
Design Models
Specification Prepare
Design Models Specification
Approve
Proposed
Specification
Specification
Conformance
Statement
Publish Specification
Approved Published Prepare Specification
Approved Profile
Specification Specification Profiles
Specification
October 2005 HL7 Development Framework 7 of 21
HDF Workflow
During project initiation the project is defined, a project plan is produced, and project approval
is obtained. The primary deliverable produced during project initiation is the project charter.
1 Project initiation
During requirements documentation the problem domain is defined, a model of the domain is
Requirements produced, and the problem domain model is harmonized with HL7 reference models. The
2 Documentation
primary deliverable produced during requirements documentation is the requirements
specification.
During specification modeling reference models are constrained into design models through a
Specification process of iterative refinement driven by requirements specifications and following
3 Modeling
specification design rules, conventions, and guidelines. The primary deliverable produced
during specification modeling is a set of specification design models.
During specification Documentation the specification design models are packaged into logical
Specification units, supplemented with explanatory text, and prepared for approval. The primary deliverable
4 Documentation
produced during specification documentation is a proposed specification.
During specification approval the pre-approval specification is subjected to a series of
Specification approvals steps. The specific approval steps vary by kind of specification, level of approval,
5 Approval
and realm of interest. The primary deliverable produced during specification approval is an
approved specification.
During specification publication the approved specification is prepared for prepared for
Specification publication and distribution. The primary deliverable produced during specification
6 Publication
publication is a published specification.
During specification profiling specification models are further refined and specifications
Specification furthered constrained following the same set of design rules, conventions, and guidelines used
7 Profiling
in the development of the specification to produce a profile of the specification for use in a
particular environment by a defined community of users.
October 2005 HL7 Development Framework 8 of 21
Project initiation
During project initiation the project is defined, a project plan is produced, and
project approval is obtained. The primary deliverable produced during
project initiation is the project charter.
Project Project
Initiation Charter
1. Define project scope, objectives, and intended deliverables
2. Identify project stakeholders, participants, and required resources
3. Document project assumptions, constraints, and risk
4. Prepare preliminary project plan and document inter-project dependencies
5. Obtain project approval and launch the project
October 2005 HL7 Development Framework 9 of 21
Requirements Documentation
During requirements documentation the problem domain is defined, a model
of the domain is produced, and the problem domain model is harmonized with
HL7 reference models. The primary deliverable produced during
requirements documentation is the requirements specification.
Project Requirements Requirements
Charter Documentation Specification
1. Document Business Process: Dynamic Behavior and Static Structure
2. Capture Process Flow: UML Activity Diagram
3. Capture Structure: Domain Analysis Model and Glossary
4. Capture Business Rules: Relationships, Triggers, and Constraints
5. Harmonize the Domain Analysis Model with HL7 Reference Models
October 2005 HL7 Development Framework 10 of 21
Specification Modeling
During specification modeling reference models are constrained into design
models through a process of iterative refinement driven by requirements
specifications and following specification design rules, conventions, and
guidelines. The primary deliverable produced during specification modeling
is a set of specification design models.
Requirements Specification Specification
Specification Modeling Design Models
1. Build design models of static information views
2. Construct design models of behavioral views
3. Define reusable design model components
4. Construct design models of collaboration and interaction
5. Harmonize design models with HL7 Reference Models
October 2005 HL7 Development Framework 11 of 21
Specification Documentation
During specification Documentation the specification design models are
packaged into logical units, supplemented with explanatory text, and prepared
for approval. The primary deliverable produced during specification
documentation is a proposed specification.
Specification Specification Proposed
Design Models Documentation Specification
1. Organize design model elements into logical packages
2. Compose explanatory text, examples, and design rationale
3. Update design models and requirement specifications
4. Assemble a proposed specification package
5. Submit specification for approval
October 2005 HL7 Development Framework 12 of 21
Specification Approval
During specification approval the pre-approval specification is subjected to a
series of approvals steps. The specific approval steps vary by kind of
specification, level of approval, and realm of interest. The primary deliverable
produced during specification approval is an approved specification.
Proposed Specification Approved
Specification Approval Specification
1. Obtain TSC and Board approval to ballot specification
2. Form a ballot pool and conduct specification ballot
3. Assess negative ballots and affirmative comments
4. Modify specification in response to ballot comments
5. Resolve negative ballot responses and if necessary re-ballot
October 2005 HL7 Development Framework 13 of 21
Specification Publication
During specification publication the approved specification is prepared for
prepared for publication and distribution. The primary deliverable produced
during specification publication is a published specification.
Approved Specification Published
Specification Publication Specification
1. Obtain TSC and Board approval to publish specification
2. Prepare specification for publication
3. Submit publication to standards authorities (ANSI/ISO)
4. Render the specification in various forms of publication media
5. Post and distribute approved specifications
October 2005 HL7 Development Framework 14 of 21
Specification Profiling
During specification profiling specification models are further refined and specifications
furthered constrained following the same set of design rules, conventions, and guidelines
used in the development of the specification to produce a profile of the specification for use
in a particular environment by a defined community of users. The primary deliverable
produced during specification profiling is a set of specification profiles and conformance
statements.
Specification
Published Specification Profiles and
Specification Profiling Conformance
Statements
1. Identify community of uses for published specification
2. Further refine and constrain specification design models
3. Document exceptions, extensions, and annotations to specifications
4. Prepare and publish specification profile
5. Prepare and publish conformance statements
October 2005 HL7 Development Framework 15 of 21
HDF Workflow Diagram
Initiate Project
Project Charter
Specify
Requirements The HDF workflow is not a waterfall methodology.
Each phase builds upon the prior and may cause
prior activities to be revisited and their deliverables
adjusted.
Requirement
Specification
Reference
Models
Prepare Specification
Design Models
Specification Prepare
Design Models Specification
Approve
Proposed
Specification
Specification
Conformance
Statement
Publish Specification
Approved Published Prepare Specification
Approved Profile
Specification Specification Profiles
Specification
October 2005 HL7 Development Framework 16 of 21
Seven Phases of the HDF Methodology
1. Project initiation
2. Requirements Documentation
3. Specification Modeling
4. Specification Documentation
5. Specification Approval
6. Specification Publication
7. Specification Profiling
October 2005 HL7 Development Framework 17 of 21
Model Independence
Reference
Healthcare Domain / Information Vocabulary
Problem Space Independent Model Specification
(RIM)
Domain
Domain Analysis
Information
Model
Model
(DAM)
(DIM)
Constrained
Problem Space Specific / Information
Technology Independent Model
(CIM)
Serialized
Information
Model
(SIM)
ITS-Specific Implementation
Technology Specific / Information Technology
Implementation Independent Model Specification
(IIM) (ITS)
October 2005 HL7 Development Framework 18 of 21
HDF UML Profile Project
MIF
UML 2.0 XML Schema
HDF Metamodel
Metamodel Definition
(XSD)
XMI to MIF UML Model
HDF UML Profile Transform Export
(XSLT) (MIF)
UML
UML 2.0
Model Export
Modeling Tool
(XMI)
• HDF UML Profile Project
• UML Profile Implementation
Model
using HDF UML • XMI to MIF Transformation
Profile
October 2005 HL7 Development Framework 19 of 21
Health Level Seven: When and Where
January 8 – 13, 2006
Working Group Meeting
Pointe Hilton Squaw Peak
Scottsdale, AZ
May 6 - 12, 2006
Working Group Meeting
San Antonio Hyatt
San Antonio, TX
September 10 - 15, 2006
20th Plenary and Working Group Meeting
Boca Raton Resort
Boca Raton, FL
October 2005 HL7 Development Framework 20 of 21
Thank You
Abdul-Malik Shakir
Principal Consultant
Shakir Consulting
1911 Foothill Blvd., Suite 148
La Verne, CA 91750
Office: (909) 596-6790 Mobile: (626) 644-4491
Email: AbdulMalik@[Link]
October 2005 HL7 Development Framework 21 of 21
