HL7 Version 2 to FHIR
1.0.0 - STU 1
HL7 Version 2 to FHIR
1.0.0 - STU 1
HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/message-mdm-t02-to-bundle | Version: 1.0.0 | |||
| Standards status: Informative | Computable Name: MessageMDM_T02ToBundle | |||
Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved. |
||||
This ConceptMap represents a mapping from the HL7 V2 Message MDM_T02 to the FHIR Message Bundle.
This ConceptMap represents the mapping from the HL7 V2 MDM_T02 Message to the FHIR Message Bundle. See also the FHIR Shorthand or the CSV Source.
| HL7 v2 | Condition (IF True, args) | HL7 FHIR | Comments | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sort Order | Identifier | Syntax | Name | Cardinality - Min | Cardinality - Max | Computable ANTLR | Computable FHIRPath | Narrative | Primary Target | Segment Map | References | |
| 1 | MDM_T02.MSH | MSH | Message Header | 1 | 1 | Bundle | MSH[Bundle] | |||||
| 1 | MDM_T02.MSH | MSH | Message Header | 1 | 1 | MessageHeader | MSH[MessageHeader] | Processing of the MSH segment results in the creation of a new MessageHeader resource | ||||
| 1 | MDM_T02.MSH | MSH | Message Header | 1 | 1 | Provenance | MSH[Provenance-Source] | Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].id | If the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | |||
| 1 | MDM_T02.MSH | MSH | Message Header | 1 | 1 | Provenance | MSH[Provenance-Transformation] | Provenance[2].target.reference=Bundle.id | If the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | |||
| 2 | MDM_T02.SFT | [{SFT}] | Software Segment | 0 | -1 | If the software does not represent the original source system | Provenance.entity.what(Device) | SFT[Device] | Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="derivation" | |||
| 2 | MDM_T02.SFT | [{SFT}] | Software Segment | 0 | -1 | If the software represents the original source system | Provenance.entity.what(Device) | SFT[Device] | Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="source" | |||
| 3 | MDM_T02.UAC | [ UAC ] | User Authentication Credential | 0 | 1 | |||||||
| 4 | MDM_T02.EVN | EVN | Event Type | 1 | 1 | Provenance | EVN[Provenance] | Provenance[3].target.reference=MessageHeader[1].id | ||||
| 5 | MDM_T02.PID | PID | Patient Identification | 1 | 1 | Patient | PID[Patient] | Processing of the PID segment results in the creation of a new Patient resource | ||||
| 5 | MDM_T02.PID | PID | Patient Identification | 1 | 1 | Provenance | PID[Provenance-Patient] | Provenance.target.reference=Patient[1].id | ||||
| 6 | MDM_T02.PV1 | PV1 | Patient Visit | 1 | 1 | Encounter | PV1[Encounter] | Encounter.subject=Patient[PID] | Processing of the PV1 segment results in the creation of a new Encounter resource | |||
| 6 | MDM_T02.PV1 | PV1 | Patient Visit | 1 | 1 | IF PV1-43 VALUED | Basic | PV1[Basic-EncounterHistory] | Basic.extension-EncounterHistory.subject.reference=Patient[1].id | |||
| 6 | MDM_T02.PV1 | PV1 | Patient Visit | 1 | 1 | Patient | PV1[Patient] | |||||
| 6 | MDM_T02.PV1 | PV1 | Patient Visit | 1 | 1 | IF PV1-20 VALUE | Coverage | PV1[Coverage] | Coverage.beneficiary.reference=Patient[1].id | |||
| 7 | MDM_T02.COMMON_ORDER | [{ | --- COMMON_ORDER begin | 0 | -1 | |||||||
| 7.1 | MDM_T02.COMMON_ORDER.ORC | ORC | Common order segment | 1 | 1 | ServiceRequest | ORC[ServiceRequest] | ServiceRequest.subject=Patient[PID] | Processing of each ORC segment results in the creation of a new ServiceRequest resource | |||
| 7.1 | MDM_T02.COMMON_ORDER.ORC | ORC | Common order segment | 1 | 1 | Provenance | ORC[Provenance] | Provenance.target=ServiceRequest[ORC] | Using Provenance is the preferred way, but a local implementation may decide to add extensions to the main resource. As the use and guidance of Provenance matures we wil revisit this later. | |||
| 7.2 | MDM_T02.COMMON_ORDER.TIMING | [{ | --- TIMING begin | 0 | -1 | |||||||
| 7.2.1 | MDM_T02.COMMON_ORDER.TIMING.TQ1 | TQ1 | Timing/Quantity | 1 | 1 | ServiceRequest | TQ1[ServiceRequest] | |||||
| 7.2.2 | MDM_T02.COMMON_ORDER.TIMING.TQ2 | [{TQ2}] | Timing/Quantity Order Sequence | 0 | -1 | |||||||
| 7.2.3 | /MDM_T02.COMMON_ORDER.TIMING | }] | --- TIMING end | |||||||||
| 7.3 | MDM_T02.COMMON_ORDER.OBR | OBR | Observation request segment | 1 | 1 | ServiceRequest | OBR[ServiceRequest] | |||||
| 7.4 | MDM_T02.COMMON_ORDER.NTE | [{ NTE }] | Notes and comments about the observation (OBR) | 0 | -1 | ServiceRequest | NTE[ServiceRequest] | |||||
| 7.5 | /MDM_T02.COMMON_ORDER | }] | --- COMMON_ORDER end | |||||||||
| 8 | MDM_T02.TXA | TXA | Document Notification | 1 | 1 | DocumentReference | TXA[DocumentReference] | DocumentReference[1].context.related.reference=ServiceRequest[1].id | Note for detailed mapping to use | |||
| 8 | MDM_T02.TXA | TXA | Document Notification | 1 | 1 | IF TXA-8 IS VALUED | must be valued to the seconds and with the appropriate/correct timezone | Provenance | TXA[Provenance] | Provenance[1].target=DocumentReference[1].id | It is up to the implementer to be sensitive whether this message is new to the receiver or an update to a prior one and only update Provenance for new updates. Also, as TXA-8 Edit Date Time can repeat, a separate Provenance instance must be created for each edit date time of interest. | |
| 9 | MDM_T02.CON | [{CON}] | Consent Segment | 0 | -1 | |||||||
| 10 | MDM_T02.OBSERVATION | { | --- OBSERVATION begin | 1 | -1 | |||||||
| 10.1 | MDM_T02.OBSERVATION.OBX | OBX | Observation/Result (one or more required) | 1 | 1 | DocumentReference | OBX[DocumentReference] | DocumentReference[1].context.related.reference=ServiceRequest[1].id | ||||
| 10.2 | MDM_T02.OBSERVATION.NTE | [{ NTE }] | Notes and comments about the observation (OBX) | 0 | -1 | DocumentReference | NTE[DocumentReference] | DocumentReference[1].context.related.reference=ServiceRequest[1].id | ||||
| 10.3 | /MDM_T02.OBSERVATION | } | --- OBSERVATION end | |||||||||
Mapping from (not specified) to (not specified)
Group 1 Mapping from unspecified code system to unspecified code system
| Source Concept Details | Relationship | Target Concept Details | Comment | ||||
| Codes from | NarrativeCondition | ComputableANTLR | Codes from | ||||
| MDM_T02.MSH | Message Header | is equivalent to | Bundle | Bundle | |||
| MDM_T02.MSH | Message Header | is equivalent to | MessageHeader[1] | MessageHeader[1] | Processing of the MSH segment results in the creation of a new MessageHeader resource | ||
| MDM_T02.MSH | Message Header | is equivalent to | Provenance[1] | Provenance[1] | If the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | ||
| MDM_T02.MSH | Message Header | is equivalent to | Provenance[2] | Provenance[2] | If the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated. | ||
| MDM_T02.SFT | Software Segment | If the software does not represent the original source system | is equivalent to | Provenance[1].entity.what(Device) | Provenance[1].entity.what(Device) | ||
| MDM_T02.SFT | Software Segment | If the software represents the original source system | is equivalent to | Provenance[1].entity.what(Device) | Provenance[1].entity.what(Device) | ||
| MDM_T02.EVN | Event Type | is equivalent to | Provenance[3] | Provenance[3] | |||
| MDM_T02.PID | Patient Identification | is equivalent to | Patient[1] | Patient[1] | Processing of the PID segment results in the creation of a new Patient resource | ||
| MDM_T02.PID | Patient Identification | is equivalent to | Provenance[4] | Provenance[4] | |||
| MDM_T02.PV1 | Patient Visit | is equivalent to | Encounter[1] | Encounter[1] | Processing of the PV1 segment results in the creation of a new Encounter resource | ||
| MDM_T02.PV1 | Patient Visit | IF PV1-43 VALUED | is equivalent to | Basic | Basic | ||
| MDM_T02.PV1 | Patient Visit | is equivalent to | Patient[1] | Patient[1] | |||
| MDM_T02.PV1 | Patient Visit | IF PV1-20 VALUE | is equivalent to | Coverage[1] | Coverage[1] | ||
| MDM_T02.COMMON_ORDER.ORC | Common order segment | is equivalent to | ServiceRequest[1] | ServiceRequest[1] | Processing of each ORC segment results in the creation of a new ServiceRequest resource | ||
| MDM_T02.COMMON_ORDER.ORC | Common order segment | is equivalent to | Provenance[3] | Provenance[3] | Using Provenance is the preferred way, but a local implementation may decide to add extensions to the main resource. As the use and guidance of Provenance matures we wil revisit this later. | ||
| MDM_T02.COMMON_ORDER.TIMING.TQ1 | Timing/Quantity | is equivalent to | ServiceRequest[1] | ServiceRequest[1] | |||
| MDM_T02.COMMON_ORDER.OBR | Observation request segment | is equivalent to | ServiceRequest[1] | ServiceRequest[1] | |||
| MDM_T02.COMMON_ORDER.NTE | Notes and comments about the observation (OBR) | is equivalent to | ServiceRequest[1] | ServiceRequest[1] | |||
| MDM_T02.TXA | Document Notification | is equivalent to | DocumentReference[1] | DocumentReference[1] | Note for detailed mapping to use | ||
| MDM_T02.TXA | Document Notification | must be valued to the seconds and with the appropriate/correct timezone | IF TXA-8 IS VALUED | is equivalent to | Provenance | Provenance | It is up to the implementer to be sensitive whether this message is new to the receiver or an update to a prior one and only update Provenance for new updates. Also, as TXA-8 Edit Date Time can repeat, a separate Provenance instance must be created for each edit date time of interest.\ |
| MDM_T02.OBSERVATION.OBX | Observation/Result (one or more required) | is equivalent to | DocumentReference[1] | DocumentReference[1] | |||
| MDM_T02.OBSERVATION.NTE | Notes and comments about the observation (OBX) | is equivalent to | DocumentReference[1] | DocumentReference[1] | |||
IG © 2020+ HL7 International / Orders and Observations. Package hl7.fhir.uv.v2mappings#1.0.0 based on FHIR 4.0.1. Generated 2025-08-25
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change