HL7 Version 2 to FHIR
1.0.0-ballot - ballot International flag

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-ballot 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

ConceptMap: Message MDM_T02 to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/message-mdm-t02-to-bundle Version: 1.0.0-ballot
Active as of 2024-10-30 Computable Name: MessageMDM_T02ToBundle

Copyright/Legal: Copyright (c) 2020, 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 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierSyntaxNameCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativePrimary TargetSegment MapReferences
1MDM_T02.MSHMSHMessage Header11BundleMSH[Bundle]
1MDM_T02.MSHMSHMessage Header11MessageHeaderMSH[MessageHeader]Processing of the MSH segment results in the creation of a new MessageHeader resource
1MDM_T02.MSHMSHMessage Header11ProvenanceMSH[Provenance-Source]Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].idIf 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.
1MDM_T02.MSHMSHMessage Header11ProvenanceMSH[Provenance-Transformation]Provenance[2].target.reference=Bundle.idIf 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.
2MDM_T02.SFT[{SFT}]Software Segment0-1If the software does represent not the original source systemProvenance.entity.what(Device)SFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="derivation"
2MDM_T02.SFT[{SFT}]Software Segment0-1If the software represents the original source systemProvenance.entity.what(Device)SFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="source"
3MDM_T02.UAC[ UAC ]User Authentication Credential01
4MDM_T02.EVNEVNEvent Type11ProvenanceEVN[Provenance]Provenance[3].target.reference=MessageHeader[1].id
5MDM_T02.PIDPIDPatient Identification11PatientPID[Patient]Processing of the PID segment results in the creation of a new Patient resource
5MDM_T02.PIDPIDPatient Identification11ProvenancePID[Provenance-Patient]Provenance.target.reference=Patient[1].id
6MDM_T02.PV1PV1Patient Visit11EncounterPV1[Encounter]Encounter.subject=Patient[PID]Processing of the PV1 segment results in the creation of a new Encounter resource
6MDM_T02.PV1PV1Patient Visit11IF PV1-43 VALUED​EncounterHistoryPV1[EncounterHistory]EncounterHistory.subject.reference=Patient[1].id
6MDM_T02.PV1PV1Patient Visit11PatientPV1[Patient]
6MDM_T02.PV1PV1Patient Visit11IF PV1-20 VALUECoverage​PV1[Coverage]Coverage.beneficiary.reference=Patient[1].id
7MDM_T02.COMMON_ORDER[{--- COMMON_ORDER begin0-1
7.1MDM_T02.COMMON_ORDER.ORCORCCommon order segment11ServiceRequestORC[ServiceRequest]ServiceRequest.subject=Patient[PID]Processing of each ORC segment results in the creation of a new ServiceRequest resource
7.1MDM_T02.COMMON_ORDER.ORCORCCommon order segment11ProvenanceORC[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.2MDM_T02.COMMON_ORDER.TIMING[{--- TIMING begin0-1
7.2.1MDM_T02.COMMON_ORDER.TIMING.TQ1TQ1Timing/Quantity11ServiceRequestTQ1[ServiceRequest]
7.2.2MDM_T02.COMMON_ORDER.TIMING.TQ2[{TQ2}]Timing/Quantity Order Sequence0-1
7.2.3/MDM_T02.COMMON_ORDER.TIMING}]--- TIMING end
7.3MDM_T02.COMMON_ORDER.OBROBRObservation request segment11ServiceRequestOBR[ServiceRequest]
7.4MDM_T02.COMMON_ORDER.NTE[{ NTE }]Notes and comments about the observation (OBR)0-1ServiceRequestNTE[ServiceRequest]
7.5/MDM_T02.COMMON_ORDER}]--- COMMON_ORDER end
8MDM_T02.TXATXADocument Notification11DocumentReferenceTXA[DocumentReference]DocumentReference[1].context.related.reference=ServiceRequest[1].idNote for detailed mapping to use
8MDM_T02.TXATXADocument Notification11ProvenanceTXA[Provenance]Provenance[1].target=DocumentReference[1].id
9MDM_T02.CON[{CON}]Consent Segment0-1
10MDM_T02.OBSERVATION{--- OBSERVATION begin1-1
10.1MDM_T02.OBSERVATION.OBXOBXObservation/Result (one or more required)11DocumentReferenceOBX[DocumentReference]DocumentReference[1].context.related.reference=ServiceRequest[1].id
10.2MDM_T02.OBSERVATION.NTE[{ NTE }]Notes and comments about the observation (OBX)0-1DocumentReferenceNTE[DocumentReference]DocumentReference[1].context.related.reference=ServiceRequest[1].id
10.3/MDM_T02.OBSERVATION}--- OBSERVATION end

Generated Narrative: ConceptMap message-mdm-t02-to-bundle

Mapping from MDM_T02 to Bundle


Group 1 Mapping from unspecified code system to unspecified code system

Source CodeRelationshipTarget CodeComment
MDM_T02.MSH (Message Header)is equivalent toBundle
MDM_T02.MSH (Message Header)is equivalent toMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource
MDM_T02.MSH (Message Header)is equivalent toProvenance[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 toProvenance[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)is equivalent toProvenance[1].entity.what(Device)
MDM_T02.SFT (Software Segment)is equivalent toProvenance[1].entity.what(Device)
MDM_T02.EVN (Event Type)is equivalent toProvenance[3]
MDM_T02.PID (Patient Identification)is equivalent toPatient[1]Processing of the PID segment results in the creation of a new Patient resource
MDM_T02.PID (Patient Identification)is equivalent toProvenance[4]
MDM_T02.PV1 (Patient Visit)is equivalent toEncounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource
MDM_T02.PV1 (Patient Visit)is equivalent toEncounterHistory
MDM_T02.PV1 (Patient Visit)is equivalent toPatient[1]
MDM_T02.PV1 (Patient Visit)is equivalent toCoverage[1]
MDM_T02.COMMON_ORDER.ORC (Common order segment)is equivalent toServiceRequest[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 toProvenance[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 toServiceRequest[1]
MDM_T02.COMMON_ORDER.OBR (Observation request segment)is equivalent toServiceRequest[1]
MDM_T02.COMMON_ORDER.NTE (Notes and comments about the observation (OBR))is equivalent toServiceRequest[1]
MDM_T02.TXA (Document Notification)is equivalent toDocumentReference[1]Note for detailed mapping to use
MDM_T02.TXA (Document Notification)is equivalent toProvenance
MDM_T02.OBSERVATION.OBX (Observation/Result (one or more required))is equivalent toDocumentReference[1]
MDM_T02.OBSERVATION.NTE (Notes and comments about the observation (OBX))is equivalent toDocumentReference[1]

Notes: