v2-To-FHIR (PSS in Confluence)

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.

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

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.