2-To-FHIR

Project Name: Definitive HL7 V2 - HL7 FHIR Mapping

Project ID:

• TSC Notification Informative/STU to Normative    

Date : 1481

• Investigative Project

Date : 

2.a.Primary Sponsor/Work Group:
(1 (And Only 1) Allowed)

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Clinical Genomics

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Infrastructure and Messaging

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Patient Administration

Indicate the level of involvement that the co-sponsor will have for this project:

Financial Management

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 FHIR Management Group

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Modeling & Methodology

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Conformance

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Service Oriented Architecture

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Patient Care

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Pharmacy

Indicate the level of involvement that the co-sponsor will have for this project:

(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)

 Public Health

Indicate the level of involvement that the co-sponsor will have for this project:

Project facilitator (1Mandatory)

Hans Buitendijk

Other interested parties and their roles

<Interested Party & Role>

Multi-disciplinary project team (recommended)

       Modeling facilitator

<Facilitator>

       Publishing facilitator

<Facilitator>

       Vocabulary facilitator

<Facilitator>

       Domain expert rep

Mapping: Kevin Power, Clem McDonald, Andrea Pitkus, Gil Alterovitz, David Burgess, Vince McCauley, Freida Hall, Frank Oemig, Kathleen Connor, Craig Newman, Nathan Bunker

Tooling/Methodology: Robert Worden, Ken Lord, Sean Muir, Frank Oemig, Rob Snelick

       Business requirement analyst

       Conformance facilitator (for IG projects)

       Other facilitators (SOA, etc)

Implementers (2 Mandatory for STU projects)

FHIR Project Note: The implementer requirement will be handled by the “balloting” project.  Therefore work groups do not fill out the above section.  However, feel free to list implementers specific to your work group’s resources if you know of any.

1) Orion

2) Cerner

With the advent of HL7 FHIR, a definitive mapping of HL7 V2 components to HL7 FHIR components would aid in the consistent transition of data communicated using either standard, while creating a starting point for those interested to convert HL7 V2 messages into FHIR based approaches. The current mapping information in HL7 FHIR is limited to addressing HL7 FHIR components only and incomplete in that it does not go down to the data type component level.

The scope of the project is:

• While V2.8.2/V2.9 would be the starting point, any deprecated data types would be mapped as well to enable mapping from prior HL7 V2 versions.
• FHIR R4 will be the initial FHIR target.
• Tooling
  • Establish the publication approach/structure/tools and relationship with the existing FHIR mapping sections/tabs and collaborating with the SOA's Cross-Paradigm Interoperability Extension Implementation Guide project that has a common tooling interest and Robert Worden's TBX that enables sample mappings.
• Data Types:
  • Establish V2-FHIR data type mappings and resolve missing data type components in FHIR for V2 data type components.
• Data Type Profiling:
  
  • Establish FHIR data type profiles/structure definitions representing V2 data types to support V2 equivalent constructs in FHIR.
• Fields/Segments:
  • For every segment-field.datatype component in HL7 V2 to either identify
    • the equivalent core HL7 FHIR resource.attribute.datatype component, or
    • identify/propose/approve an HL7 FHIR extension that represents the HL7 V2 segment-field.datatype component to encourage consistent use rather than everybody defining their own extensions for HL7 V2 equivalents.
• Maintenance
  
  • Once mappings have been established, both FHIR and V2 are expected to evolve and the mappings will be kept up-to-date.
  • As the start of the project is expected to have V2.8.2 available, once V2.9 is published, it would progress using that version as the starting point.

The immediate goal is to have mappings available for data types and segments/fields that are a accessible in context of FHIR and V2+ (once established) elements, and independently.

Note that:

• Data Types is a pre-requisite to Fields/Segments.
• Fields/Segments can be done any time after Data Types are done, and can be done piece-meal as needed plus based on priority/use, thus spread across multiple ballots.
• The intent is to achieve normative status of the mappings
• Detailed requirements and constraints of tooling to utilize where possible common data model will be addressed in the Tooling track.

Initially Out-Of-Scope:

• Define a FHIR profile for every V2 segment to reflect the cardinality, optionality, and conditionality of V2 segments.
  • This would only be done for the latest V2.8.2/V2.9, until there is interest to do so for earlier versions on a case by case situation.
• For every message in HL7 V2 define a corresponding HL7 FHIR profile/structure definition that reflects the full HL7 V2 message content, which can be the basis for either HL7 FHIR based services or message approaches.
  
  • This would only be done for the latest V2.8.2/V2.9, until there is interest to do so for earlier versions on a case by case situation.
• Value set mapping
• FHIR=>V2 considerations/guidance, particularly where it is not feasible.
• Implementation guide tailored mappings.

As interest in representing data in HL7 V2 and HL7 FHIR consistently and predictably across implementations, and aid the transition from HL7 V2 to HL7 FHIR as needed, a clear mapping needs to exist that HL7 endorses, thus can be the starting point for everybody else to create implementation guides accordingly. At this time, everybody needs to create their own extensions where they wish to represent the richness of HL7 V2 in their implementations.

Will this project produce executable(s), for example, schemas, transforms, style sheets, executable program, etc.  If so the project must review and document security risks.

Yes

 X

No

Unknown

Not applicable

Target Date

Phase I: Initial pilot/prototype using select data types and segments to establish appropriate format (e.g., FHIR Mapping Language, MDMI, other)

January 2019

Phase II: For comment ballot with initial set of all data types and initial prioritized segments

2019 May WGM

Phase III: For comment ballot with complete set of data types and segments (based on progress may be adjusted)

2019 September Ballot

Phase IV: FHIR HL7 V2 extension ballot for prioritized data type components, data type profiles, and fields

2020 January WGM

Phase V: FHIR HL7 V2 extension ballot for remaining data type components, data type profiles, and fields

TBD

Phase VI: Normative ballot with complete set of mappings

Project End Date (all objectives have been met)

TBD

2-To-FHIR

Not applicable

• FHIR R4 and approach on core extensions
• If tools developed by the HL7 Cross Paradigm Interoperability Implementation Guide Extension are chosen for use in this project, else this dependency goes away.

Initially, documentation will be kept in Confluence here (2-To-FHIR Project), and once we understand how to publish the actual mappings, the location of those constructs will be added here and on the project page.

Are the items being produced by this project backward compatible?

Yes

No

Unknown

N/A

 X

For V3, are you using the current data types? 

(Refer to TSC position statement on new projects using R2B for more information on the current V3 data types)

Yes

No

Unknown

N/A

If you check 'No' please explain the reason:

If desired, enter additional information regarding Backwards Compatibility.

Will this project include/reference external vocabularies?

Yes

No

Unknown

N/A

 X

If yes, please list the vocabularies:

Non Product Project - (Educ. Marketing, Elec. Services, etc.)

V3 Domain Information Model (DIM / DMIM)

Arden Syntax

V3 Documents – Administrative (e.g. SPL)

Clinical Context Object Workgroup (CCOW)

V3 Documents – Clinical (e.g. CDA)

Domain Analysis Model (DAM)

V3 Documents - Knowledge

Electronic Health Record (EHR) Functional Profile

V3 Foundation – RIM

Logical Model

V3 Foundation – Vocab Domains & Value Sets

X 

V2 Messages – Administrative

V3 Messages - Administrative

X 

V2 Messages - Clinical

V3 Messages - Clinical

 X

V2 Messages - Departmental

V3 Messages - Departmental

 X

V2 Messages – Infrastructure

V3 Messages - Infrastructure

X 

FHIR Implementation Guide

V3 Rules - GELLO

X 

FHIR Profiles

V3 Services – Java Services (ITS Work Group)

 X

FHIR Resources

V3 Services – Web Services (SOA)

New/Modified/HL7 Policy/Procedure/Process

White Paper

New Product Definition

New Product Family

Create new standard

X 

Supplement to a current standard

Revise current standard (see text box below)

Implementation Guide (IG) will be created/modified

Reaffirmation of a standard

Project is adopting/endorsing an externally developed IG:

New/Modified HL7 Policy/Procedure/Process

Specify external organization in Sec. 6 below;

Withdraw an Informative Document

Externally developed IG is to be (select one):

White Paper (select one):

Adopted  - OR -

Endorsed

Balloted Informative OR

Non-balloted WG White Paper

N/A  (Project not directly related to an HL7 Standard)