Reference+Architecture

hssp.wikispaces.com | Jan 12th 2011 3:00 PM
Stephen Hufnagel PhD is one of the project facilator and this wiki page editor. If you wish to participate or have H-SOA-RA/EHR-SD RM questions or concerns, The related , and projects will be statused on the same call.
: Every Friday: 12:30-01:30 PM EST: +1 770-657-9270: 071582#: for web screen sharing:
CLICK Here to Download Models

Current Documents

Click here to view the 21-Jan-10 slide presentation on Constructing a Future State EHR Reference Architecture

Executive Summary

EHR-SD RM EHR System Design Reference Model aka H-SOA-RA (Healthcare SOA Reference Architecture) TWO Subprojects are:

EHR-S CI-IM EHR System Computationally-Independent Information-Model (Started Jun2010)
This project will produce a set of Constrained Information Models called EHR-S “data profiles”. Each EHR-S data profile corresponds directly with an EHR-S function profile and each EHR-S data profile will include one-or-more Reference Information Model classes. Pairs of EHR-S function profiles and data profiles can be used to define business objects, which can be composed into software components, capabilities, applications, systems and their message exchanges and/or document exchanges and/or services. The superset of EHR-S data profiles is called the EHR-S Computationally-Independent Information-Model, which supports the HL7 Development Process and Service Aware Interoperability Framework. The project will include the development and execution of a communication strategy to ensure that all affected stakeholders are engaged. HF&EA Harmonization Framework and Exchange Architecture (Started Jun2010)

HF&EA Harmonization Framework and Exchange Architecture (Started Jun2010)
The first objective of this HL7 Harmonization Framework and Exchange Architecture (HF&EA) project is to define a notional set of architectural artifacts for HL7 projects and EHR System (EHR-S) development or acquisition projects. The second objective is to define the relationships among HL7 architectural artifacts and how they relate to other healthcare related standards and architectural artifacts, which can support a Model Driven Architecture (MDA) waterfall, spiral, agile or other development methodology. The third objective is to be an implementation guide for the use of the HL7 Development Framework (HDF) process and HL7 Service Aware Interoperability Framework Enterprise Compliance and Conformance Framework (SAIF ECCF) structure by which architectural work products are reused or developed, are organized into an Interoperability Specification and used throughout an architecture development project, the governance that should be enacted on these work products, and the scope of the standardization effort itself. The fourth objective is to define a Healthcare Information Exchange Model (HIEM) for model-driven Healthcare Information Exchange Package Documentation (H-IEPD) and exchange architecture. The fifth objective is to demonstrate how the HDF and ECCF can complement other frameworks such as TOGAF, Agile Scrum, DODAF and Zachman.

STATUS (12-Oct-10): The Service-Aware Interoperability Framework (SAIF ) focuses on specifying artifacts that explicitly express the characteristics of software components that affect interoperability. SAIF organizes and manages architectural complexity with a set of constructs, best practices, processes, procedures and categorizations. SAIF’s scope is the interoperability space between system components. Specifically, SAIF manages the interworking among distributed systems that may involve information exchanges or service interactions and state changes; SAIF is not Enterprise Architecture . SAIF’s goal is to create and manage easy-to-use, traceable, consistent and coherent Interoperability Specifications (ISs) regardless of the message, document or service interoperability-paradigm. SAIF combines four sub-frameworks, that together form a basis for defining comparable interoperability specifications (Information and Behavioral Frameworks) and formalizing governance and conformity assessment methods (Governance and Enterprise Conformance and Compliance Frameworks) critical to defining and using interoperability specifications.

Project Intent

Create informative mapping/analysis document to:

Implement a step in HL7 roadmap
- Identify gaps and overlaps in HL7’s portfolio
- Identify gaps in the EHR-S FM (an artifact exists for which there is no conformance criterion or function in the EHR-S FM)
- Pilot HL7 ARB Services Aware Enterprise Architecture Framework (SAEAF) framework/methodology
Submit H-SOA-RA to ArB for consurrence as an ArB SAEAF artifact
Validate HITSP Multi-Enterprise Architecture of Networked Services Standards (MEANS) framework/methodology
Create Healthcare SOA Reference Architecture (H-SOA-RA) Version 2
Create Healthcare SOA EHR System Design Reference Model (EHR-SD RM) based on EHR-S FM
Create prototype architectural case study using HL7 HSSP Practical Guide for SOA in Healthcare “Sample Health” example and service specifications, EHR-S FM, EHR-SD RM, AHIC Use Cases, HITSP Interoperability Specifications and NHIN services.
Demonstrate standards-driven Model Driven Architecture (MDA) approach

Project Scope

This project will mature the April 2008 Healthcare Services Oriented Reference Architecture (H-SOA-RA) version 1.0 into H-SOA-RA Version 2.0, for HL7 ArB consideratiom, and then integrate it into an EHR System Design Reference Model (EHR-SD RM), using the HL7 SOA-Aware Enterprise Architecture Framework (SAEAF), HITSP Multi-Enterprise Architecture of Networked Services Standards (MEANS), EHR System Functional Model (EHR-S FM). Emphasis will be placed on maintaining AHIC, HITSP, NHIN and CCHIT conformance by maintaining Information Exchange Requirements (IERs) and Data Requirements (DRs) traceability. Mapping and analysis of the HL7 product portfolio against the EHR-S FM will be used to integrate the reference architecture with HL7 product lines and initially mature the resulting model as a technical white papers, then an informative reference model and finally a standard reference model. An HSSP based prototype case study architectural specification will be built to validate the effort.
The following steps will be followed:

Define Healthcare SOA Reference Architecture (H-SOA-RA) Version 2
1. Define priority Information Exchange Requirements (IERs) based on
  1. MHS-VA federal inter-agency exchange projects (e.g., CHDR, BHIE, LDSI, wounded warrior, Federal Hospital Care Center (e.g., “North Chicago joint EHR)),
  2. HITSP, NHIN, Priority Federal Agency exchanges
2. Define priority Data Requirements (DRs) along with IERs.
3. Map IERs and DRs to H-SOA-RM Version 1
4. Build Catalog of candidate Services (HL7 SAEAF classification categories)
  1. Categorize candidate infrastructure services
  2. Categorize candidate Process (e.g., workflow) services
  3. Categorize candidate core business services
  4. Categorize candidate capability (e.g., application) services
5. Show AHIC-HITSP traceability (e.g., AHIC IERs to HITSP ISs to standards)
6. Show NHIN traceability (align with NHIN services)
7. Show CCHIT traceability (align with CCHIT test criteria)
8. Compare and contrast H-SOA-RA with publically available Canada Infoway’s SOA or other
Submit H-SOA-RA to ArB for consurrence as an ArB SAEAF artifact
Define EHR-SD RM
1. Map Priority IERs and DRs to EHR-S FM
2. Map candidate services to EHR-S FM
3. Group IERs into candidate EHR-S FM services
4. Define EHR-SD RM based Business Transformation Architecture methodology for
  1. Legacy system migration
  2. New system development
  3. COTS evaluations and integration
  4. CCHIT certification
Identify gaps and overlaps in HL7’s portfolio
1. Identify artifacts that do not now exist but are indicated in the EHR-S FM
2. Identify the extent of duplication that may exist across HL7 artifacts
Create prototype EHR-SD RM validation case study prototype, using
1. AHIC-HITSP Public Health and Emergency Response use cases and Interoperability Specifications
2. HL7 ARB Services Aware Enterprise Architecture Framework (SAEAF)
3. HITSP Multi-Enterprise Architecture of Networked Services Standards (MEANS) and
4. HL7 HSSP Practical Guide for SOA in Healthcare “sample health” example specifications.
  1. Include mapping to MHS and DOD specific IERs and DRs
Publish HL7 HSSP Practical Guide for SOA in Healthcare Part 2: Case Study.
1. To show HITSP, NHIN and CCHIT conformance criteria, use
  1. OMG Object Constraint Language and/or
  2. OWL Semantic Ontology specification language

The key end user target is US health domain federal agencies and their non-federal contractors and partners; but, the overall results should be universally applicable across healthcare IT. This project also fulfills the federal health architecutre mandate to establish a service reference model (e.g., H-SOA-RA V2) for the health domain as a candidate for the Federal Health Architecture (FHA) Service Reference model (SRM). A draft set of health domain services, their definitions, and mapping of V2.5 message content mappings has already been created and derived from the EHR-S FM by DoD in conjunction with VA. This project will add the V3.0 messages.

Project Objectives and Deliverables

1) Mapping of Federal priority, NHIN and HITSP IERs and DRs to EHR-S FM Mar 2009 (Year 1 task-1)
2) Mappings and validations of V2.5.1, V3 products to EHR-S FM June 2009 (Year 1 task-2)
4) Health SOA Reference Model (H-SOA-RM) draft Version 2.0 June 2009 (Year 1 task-3)
3) HSSP Practical Guide for SOA in Health Care, Part II: Case Study June 2009 (Year 1 task-4)
5) Feedback to HL7 ARB and HITSP on SAEAF and MEANS respectively June 2009 (Year 1 task-5)
6) Balloted “Comments Only” EHR-SD RM white paper, including

HITSP conformant Information Exchange Requirements (IERs) mapped to EHR-S FM
HITSP conformant Data Requirements (DRs) mapped to EHR-S FM
HITSP conformant Candidate Service mapped to EHR-S FM Sept 2009 (Year 1 task-6)

7) Balloted informative EHR-SD RM Sept 2010 (Year 2 task)
8) Balloted normative EHR-SD RM Sept 2011 (Year 3 task)

Project Schedule

Year 1

Jan 09 – harmonize and catalogue priority IERs, DRs and candidate services
Mar 09 – map priority IERs, DRs and candidate services to EHR-S FM
Jun 09 - Mappings of V2.5, V3 products to EHR-S FM
Jun 09 – Healthcare SOA Reference Architecture (H-SOA-RA) version 2.0
Jun 09 - HSSP Practical Guide for SOA in Health Care, Part II: Case Study
Jun 09 - Present at HL7 SOA Conference (for peer feedback)

H-SOA-RA V2.0
HSSP case study

Sep 09 - EHR-SD RM Balloted “comments only” white paper, to socialize the project.
YEAR 2
May-10 - Practical Guide for SOA in Healthcare Volume II: EHR Immunization and Adverse Event Reporting Prototype
Sep 10 - EHR-SD RM Balloted as informative document
YEAR 3
Sep 11 - EHR-SD RM Balloted as a standard

Chronology of Events

12-Jan-09 - GovernmentProjects, HSSP, EHR and PHER approved the project
13-Jan-09 - Project approved by HL7 Steering Division
03-Feb-09 - HSSP telecom to review H-SOA-RA bottom up development steps
22-Sep-09 - Prototype Project report at HL7 work group meeting, Atlanta, GA
05-Oct-09 - Integrate with Federal Health Information and Standards (FHIMS) Project
12-Nov-09 - Integrate HITSP Data Architecture
19-Jan-10 - Presentation of status at HL7 meeting to joint SOA, EHR, PHER meeting
18-May-10 - HSSP Practical Guide for SOA Volume II: Immunization Management Case Study (DRAFT)
05-Oct-10 - Presentation of Status and Plans at HL7 24th Plenary Conference and Workgroup, Cambridge, MA.
12-Oct-10 - SAIF Executive Summary and Implementation Guide
11-Jan-11 - Presentation of status, plans and issues at HL7 Workgroup Meeting, Sydney, Australia

11-Jan-10

Constructing a Future State EHR Reference Architecture 20110111.ppt
EHR SD RM prototype XML (must put *.XML and *.XSL in same directory and click on *.XML)

EHR SD RM BuiltOn EHR-S FM R1.1.xml

FunctionalModel_HTML.xsl

Oct-09 FHIMS Integration

Opportunistic FHIMS Methodology DRAFT-K.doc
FHIMS is Federal Health Information Model and Standards

Sep-09 Project Report

EHR SD RM Prototype Sep-09.ppt <-- updated 10-Oct-09
Overview Slides

Government Projects Project.ppt

AHIC Immunizations & Response Management Use Case

IRM Final Detailed Use Case v1.0.pdf

AHIC Public Health and Case Reporting Use Case

PHCR Final Detailed Use Case v1.0.pdf

HITSP Immunizations & Response Management Interoperability Specification (IS10

)The Immunizations and Response Management Interoperability Specification focuses on: 1) providing information about individuals who need to receive specific vaccines, drugs, or other interventions; 2) the ability to report, track, and manage administration of vaccines, drugs, isolation, and quarantine; 3) the ability to identify and electronically exchange information describing the treatment or prophylaxis status of populations; 4) the ability to exchange specific resource and supply chain data from public and private sectors.

HITSP_IS10_Complete_V1.0.zip

HL7 SAIF

SAEAF has been renamed Service Aware Interoperability Framework (SAIF)
Sep-09 SAEAF Introduction and Enterprise Compliance and Conformance Framework (ECCF)

AtlantaTutorial-MEAD-SAEAF-Intro.pdf
Sep-09 SAEAF Behavioral Framework

HL7SAEAFBehavioral_education200909.pdf
Sep-08 H-SOA-RA V1.0

H_SOA_RA V1.0.zip