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 ORU_R01 to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/message-oru-r01-to-bundle Version: 1.0.0-ballot
Active as of 2023-12-19 Computable Name: MessageORU_R01ToBundle

Copyright/Legal: Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Message ORU_R01 to the FHIR Message Bundle.

This ConceptMap represents the mapping from the HL7 V2 ORU_R01 Message to the FHIR Message Bundle. See also the FHIR Shorthand or the CSV Source.

</thead> </table>
HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierSyntaxNameCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativePrimary TargetSegment MapReferences
1ORU_R01.MSHMSHMessage Header11BundleMSH[Bundle]
1ORU_R01.MSHMSHMessage Header11MessageHeaderMSH[MessageHeader]Processing of the MSH segment results in the creation of a new MessageHeader resource
1ORU_R01.MSHMSHMessage Header11If there is a source in MSH-4, or known based on the configuration.ProvenanceMSH[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.
1ORU_R01.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.
2ORU_R01.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"
2ORU_R01.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"
3ORU_R01.UAC[UAC]User Authentication Credential01
4ORU_R01.PATIENT_RESULT{--- PATIENT_RESULT begin1-1
4.1ORU_R01.PATIENT_RESULT.PATIENT[--- PATIENT begin01
4.1.1ORU_R01.PATIENT_RESULT.PATIENT.PIDPIDPatient Identification11PatientPID[Patient]Processing of the PID segment results in the creation of a new Patient resource
bORU_R01.PATIENT_RESULT.PATIENT.PIDPIDPatient Identification11IF PID-33 AND PID-34 VALUEDOne may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.ProvenancePID[Provenance-Patient]Provenance.target.reference=Patient[1].id
4.1.2ORU_R01.PATIENT_RESULT.PATIENT.PD1[PD1]Additional Demographics01PatientPD1[Patient]Incorporate PD1 content into the Patient created from the PID segment.
4.1.3ORU_R01.PATIENT_RESULT.PATIENT.PRT[{PRT}]Participation (for Patient)0-1IF PRT-4.1 EQUALS "PP" AND PRT-4.3 EQUALS "HL70443"(PRT.element(4.1)="PP")and(PRT.element(4.3)="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]Patient[1].generalPractitioner.reference=PractitionerRole[1].idIncorporate PRT content into the Patient created from the PID segment when the PRT contains practitioner related data. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.3ORU_R01.PATIENT_RESULT.PATIENT.PRT[{PRT}]Participation (for Patient)0-1IF PRT-4.1 NOT EQUALS "PP" OR PRT-4.3 NOT EQUALS "HL70443"(PRT.element(4.1)!="PP")or(PRT.element(4.3)!="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".RelatedPersonPRT[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.4ORU_R01.PATIENT_RESULT.PATIENT.NTE[{NTE}]Notes and Comments0-1
4.1.5ORU_R01.PATIENT_RESULT.PATIENT.NK1[{NK1}]Next of Kin/Associated Parties0-1The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin dataRelatedPersonNK1[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idTypically, each NK1 will be translated to either a new RelatedPerson resource or added as a new occurrence of Patient.contact, but it's possible to insert the NK1 data into both structures.
4.1.5ORU_R01.PATIENT_RESULT.PATIENT.NK1[{NK1}]Next of Kin/Associated Parties0-1The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin dataPatientNK1[Patient]Typically, each NK1 will be translated to either a new RelatedPerson resource or added as a new occurrence of Patient.contact, but it's possible to insert the NK1 data into both structures.
4.1.6ORU_R01.PATIENT_RESULT.PATIENT.ARV[{ARV}]Access Restrictions0-1
4.1.7ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION[{--- PATIENT_OBSERVATION begin0-1
4.1.7.1ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.OBXOBXObservation (for Patient ID)11IF OBX-5 LST.count LESS THAN OR EQUALS 1ObservationOBX[Observation]Observation.subject.reference=Patient[1].id
4.1.7.1ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.OBXOBXObservation (for Patient ID)11IF OBX-5 LST.count GREATER THAN 1ObservationOBX[Observation-Component]Observation.subject.reference=Patient[1].idNote that when OBX-5 repeats, the standard mapping is to use Observation.component rather than creating separate Observation instances. However, we are aware that some profiles and implementation guides do separate the OBX into multiple observations depending on the OBX-2 value. This is an example of a non-standard interpretation as the OBX should have been separated into multiple OBX segments to start. Please consider the local profiles and implementation guides on how to manage these variants.
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-10 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".DevicePRT[Device]Observation[1].device.reference=Device.idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-9 VALUED OR IF PRT-14 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".ObservationPRT[Observation-Location]If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-5 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]Observation.performer.reference=PractitionerRole[1].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.7.3/ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION}]--- PATIENT_OBSERVATION end
4.1.8ORU_R01.PATIENT_RESULT.PATIENT.VISIT[--- VISIT begin01
4.1.8.1ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1PV1Patient Visit11EncounterPV1[Encounter]Encounter.subject.reference=Patient[1].idProcessing of the PV1 segment results in the creation of a new Encounter resource
4.1.8.1ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1PV1Patient Visit11PatientPV1[Patient]
4.1.8.2ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV2[PV2]Patient Visit - Additional Info01EncounterPV2[Encounter]Encounter.subject.reference=Patient[1].idIncorporate PV2 content into the Encounter created from the PV1 segment.
4.1.8.3ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PRT[{PRT}]Participation (for Patient Visit)0-1If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]Encounter[1].participant.individual.reference=PractitionerRole[2].idIncorporate PRT content into the Encounter created from the PV1 segment. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.1.8.4/ORU_R01.PATIENT_RESULT.PATIENT.VISIT]--- VISIT end
4.1.9/ORU_R01.PATIENT_RESULT.PATIENT]--- PATIENT end
4.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION{--- ORDER_OBSERVATION begin1-1
4.2.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER[--- COMMON_ORDER begin01
4.2.1.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCORCOrder common11DiagnosticReportORC[DiagnosticReport]DiagnosticReport[1].encounter.reference=Encounter[1].idProcessing of each ORC segment results in the creation of a new DiagnosticReport resource
4.2.1.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCORCOrder common11If a ServiceRequest needs to be created for the receiver.ServiceRequestORC[ServiceRequest]DiagnosticReport[1].basedOn.reference=ServiceRequest[1].id
4.2.1.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.PRT[{PRT}]Participation (for Observation)0-1IF PRT-4.1 EQUALS "OP" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="OP")and(element("4.3")="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]ServiceRequest[1].requester.reference=PractitionerRole[3].id
4.2.1.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORDER_DOCUMENT[--- ORDER_DOCUMENT begin01Will be addressed with FHIR R5.
4.2.1.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORDER_DOCUMENT.OBXOBXObservation containing Document11
4.2.1.3.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORDER_DOCUMENT.PRT[{PRT}]Participation0-1If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.1.3.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORDER_DOCUMENT.TXATXATranscription Document Header11
4.2.1.3.4/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORDER_DOCUMENT]--- ORDER DOCUMENT end
4.2.1.4/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER]--- COMMON ORDER end
4.2.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBROBRObservations Request11DiagnosticReportOBR[DiagnosticReport]Incorporate OBR content into the DiagnosticReport created from the ORC segment in the same segment group.
4.2.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBROBRObservations Request11SpecimenOBR[Specimen]DiagnosticReport[1].specimen.reference=Specimen.idThe OBR specimen data yields one Specimen resource that all Observations generated for the same OBR need to reference.
4.2.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBROBRObservations Request11IF ORC VALUEDIf a ServiceRequest needs to be created for the receiver.ServiceRequestOBR[ServiceRequest]Mapping to ServiceRequest as well is needed if the receiver is not the originator of the order to which this results message responds. This mapping will be completed once OMG/OML mapping is sufficiently completed. We will add the other segment mappings below to ServiceRequest then as well.
4.2.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.NTE{[NTE]}Notes and comments0-1
4.2.4ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRT[{PRT}]Participation (for Observation)0-1IF PRT-4.1 IN ("ARI","TN","TR") AND PRT-4.3 EQUALS "HL70443"PRT.element(4.1) in ("ARI","TN", "TR")and(PRT.element(4.3)="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].performer.reference=PractitionerRole[4].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRT[{PRT}]Participation (for Observation)0-1IF PRT-4.1 EQUALS "PRI" AND PRT-4.3 EQUALS "HL70443"(PRT.element(4.1)="PRI")and(PRT.element(4.3)="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].resultsInterpreter.reference=PractitionerRole[5].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRT[{PRT}]Participation (for Observation)0-1IF PRT-4.1 EQUALS "SC" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="SC")and(element("4.3")="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].specimen[1](Specimen.collection.collector.reference)=PractitionerRole[6].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRT[{PRT}]Participation (for Observation)0-1IF PRT-4.1 EQUALS "OP" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="OP")and(element("4.3")="HL70443")If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].requester.reference=PractitionerRole[3].idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.TIMING_QTY[{--- TIMING_QTY begin0-1
4.2.4.1.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.TIMING_QTY.TQ1TQ1Timing/Quantity11
4.2.4.1.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.TIMING_QTY.TQ2[{TQ2}]Timing/Quantity Order Sequence0-1
4.2.4.1.3/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.TIMING_QTY}]--- TIMING_QTY end
4.2.4.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.CTD[CTD]Contact Data01
4.2.4.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION[{--- OBSERVATION begin0-1
4.2.4.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBXObservation related to OBR11IF OBX-5 LST.count LESS THAN OR EQUALS 1 AND OBX-29 NOT IN ("QST", "SCI")ObservationOBX[Observation]DiagnosticReport.result.reference=Observation[2].id Observation[2].subject.reference=Patient[1].id; Observation[2].encounter.reference=Encounter[1].idImplementers should consider the use case where OBX-5 repeats in a given OBX segment. Because the Observation value element is not allowed to repeat, multiple occurrences of OBX-5 must be handled either through the creation of multiple Observation resources, the use of Observation components, the concatenation of the results into a single value or another solution appropriate for the data and the implementation. Note that it is not clear that every OBX represents a results that can be associated with the encounter during which it was ordered/performed.
4.2.4.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBXObservation related to OBR11IF OBX-5 LST.count GREATER THAN 1 AND OBX-29 NOT IN ("QST", "SCI")ObservationOBX[Observation-Component]DiagnosticReport.result.reference=Observation[2].id Observation[2].subject.reference=Patient[1].id; Observation[2].encounter.reference=Encounter[1].idImplementers should consider the use case where OBX-5 repeats in a given OBX segment. Because the Observation value element is not allowed to repeat, multiple occurrences of OBX-5 must be handled either through the creation of multiple Observation resources, the use of Observation components, the concatenation of the results into a single value or another solution appropriate for the data and the implementation. When multiple OBX segments are tranformed into Observation components in a single Observation resource, implementers should consider how the metadata associated with the result (eg performer, status, date/time, etc) are populated. If the OBX segments being combined into a single resource contain different metadata, it must be considered whether or not the use of components is appropriate.
4.2.4.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBXObservation related to OBR11IF OBX-5 LST.count LESS THAN OR EQUALS 1 AND OBX-29 IN ("QST", "SCI")ObservationOBX[Observation]ServiceRequest[1].supportingInfo.reference=Observation[1].id; Observation[1].subject.id=Patient[1].id
4.2.4.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBXObservation related to OBR11IF OBX-5 LST.count GREATER THAN 1 AND OBX-29 AND OBX-29 IN ("QST", "SCI")ObservationOBX[Observation-Component]ServiceRequest[1].supportingInfo.reference=Observation[1].id; Observation[1].subject.id=Patient[1].id
4.2.4.3.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-10 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".DevicePRT[Device]Observation[2].device.reference=Device.idIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4.3.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-9 VALUED OR IF PRT-14 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".ObservationPRT[Observation-Location]Incorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation location information. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4.3.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-5 VALUEDIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".PractitionerRolePRT[PractitionerRole]Observation[2].performer.reference=PractitionerRole[7].idIncorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation practitioner information. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
4.2.4.3.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.NTE{[NTE]}Notes and comments0-1Observation.noteNTE[ServiceRequest]
4.2.4.3/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION}]--- OBSERVATION end
4.2.5ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.FT1[{FT1}]Financial Transaction0-1
4.2.6ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.CTI{[CTI]}Clinical Trial Identification0-1
4.2.7ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN[{--- SPECIMEN begin0-1
4.2.7.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPMSPMSpecimen11SpecimenSPM[Specimen]DiagnosticReport[1].specimen.reference=Specimen[n].id
4.2.7.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION[{--- SPECIMEN_OBSERVATION begin0-1
4.2.7.2.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.OBXOBXObservation (for Patient ID)11IF OBX-5 LST.count LESS THAN OR EQUALS 1ObservationOBX[Observation]Observation[3].subject.reference=Patient[1].id Observation[3].focus.reference=Specimen[n].id
4.2.7.2.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.OBXOBXObservation (for Patient ID)11IF OBX-5 LST.count GREATER THAN 1ObservationOBX[Observation-Component]Observation[3].subject.reference=Patient[1].id Observation[3].focus.reference=Specimen[n].id
4.2.7.2.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1
4.2.7.2.3/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION}]--- SPECIMEN_OBSERVATION end
4.2.7.3/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN}]--- SPECIMEN end
4.2.8/ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION}--- ORDER_OBSERVATION end
4.3/ORU_R01.PATIENT_RESULT}--- PATIENT_RESULT end
5ORU_R01.DSC[DSC]Continuation Pointer

Mapping from ORU_R01 to Bundle

ACTIVE (not intended for production usage). Published on 2023-12-19 by HL7 International / Orders and Observations (HL7 Orders and Observations Workgroup: http://www.hl7.org/Special/com..., Keith W. Boone: kboone@ainq.com, Rob Hausam: rrhausam@gmail.com). Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Message ORU_R01 to the FHIR Message Bundle.


Group 1Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsCommentProperties
Codes from segmentmapreferencesCodes from narrativeantlrfhirpath
ORU_R01.MSHMessage HeaderMSH[Bundle]is equivalent toBundleBundle
ORU_R01.MSHMessage HeaderMSH[MessageHeader]is equivalent toMessageHeader[1]MessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource
ORU_R01.MSHMessage HeaderMSH[Provenance-Source]Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].idis equivalent toProvenance[1]Provenance[1]If there is a source in MSH-4, or known based on the configuration.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.
ORU_R01.MSHMessage HeaderMSH[Provenance-Transformation]Provenance[2].target.reference=Bundle.idis equivalent toProvenance[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.
ORU_R01.SFTSoftware SegmentSFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="derivation"\is equivalent toProvenance[1].entity.what(Device)Provenance[1].entity.what(Device)If the software does represent not the original source system
ORU_R01.SFTSoftware SegmentSFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="source"\is equivalent toProvenance[1].entity.what(Device)Provenance[1].entity.what(Device)If the software represents the original source system
ORU_R01.PATIENT_RESULT.PATIENT.PIDPatient IdentificationPID[Patient]is equivalent toPatient[1]Patient[1]Processing of the PID segment results in the creation of a new Patient resource
ORU_R01.PATIENT_RESULT.PATIENT.PIDPatient IdentificationPID[Provenance-Patient]Provenance.target.reference=Patient[1].idis equivalent toProvenance[4]Provenance[4]One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.IF PID-33 AND PID-34 VALUED
ORU_R01.PATIENT_RESULT.PATIENT.PD1Additional DemographicsPD1[Patient]is equivalent toPatient[1]Patient[1]Incorporate PD1 content into the Patient created from the PID segment.
ORU_R01.PATIENT_RESULT.PATIENT.PRTParticipation (for Patient)PRT[PractitionerRole]Patient[1].generalPractitioner.reference=PractitionerRole[1].idis equivalent toPractitionerRole[1]PractitionerRole[1]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 EQUALS "PP" AND PRT-4.3 EQUALS "HL70443"(PRT.element(4.1)="PP")and(PRT.element(4.3)="HL70443")Incorporate PRT content into the Patient created from the PID segment when the PRT contains practitioner related data. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.\
ORU_R01.PATIENT_RESULT.PATIENT.PRTParticipation (for Patient)PRT[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idis equivalent toRelatedPerson[1]RelatedPerson[1]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 NOT EQUALS "PP" OR PRT-4.3 NOT EQUALS "HL70443"(PRT.element(4.1)!="PP")or(PRT.element(4.3)!="HL70443")If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.PATIENT.NK1Next of Kin/Associated PartiesNK1[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idis equivalent toRelatedPerson[2]RelatedPerson[2]The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin dataTypically, each NK1 will be translated to either a new RelatedPerson resource or added as a new occurrence of Patient.contact, but it's possible to insert the NK1 data into both structures.
ORU_R01.PATIENT_RESULT.PATIENT.NK1Next of Kin/Associated PartiesNK1[Patient]is equivalent toPatient[1]Patient[1]The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin dataTypically, each NK1 will be translated to either a new RelatedPerson resource or added as a new occurrence of Patient.contact, but it's possible to insert the NK1 data into both structures.
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.OBXObservation (for Patient ID)OBX[Observation]Observation.subject.reference=Patient[1].idis equivalent toObservation[1]Observation[1]IF OBX-5 LST.count LESS THAN OR EQUALS 1
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.OBXObservation (for Patient ID)OBX[Observation-Component]Observation.subject.reference=Patient[1].idis equivalent toObservation[1]Observation[1]IF OBX-5 LST.count GREATER THAN 1Note that when OBX-5 repeats, the standard mapping is to use Observation.component rather than creating separate Observation instances. However, we are aware that some profiles and implementation guides do separate the OBX into multiple observations depending on the OBX-2 value. This is an example of a non-standard interpretation as the OBX should have been separated into multiple OBX segments to start. Please consider the local profiles and implementation guides on how to manage these variants.
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTParticipation (Observation Participation)PRT[Device]Observation[1].device.reference=Device.idis equivalent toDeviceDeviceIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-10 VALUEDIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTParticipation (Observation Participation)PRT[Observation-Location]is equivalent toObservation[1]Observation[1]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-9 VALUED OR IF PRT-14 VALUEDIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTParticipation (Observation Participation)PRT[PractitionerRole]Observation.performer.reference=PractitionerRole[1].idis equivalent toPractitionerRole[1]PractitionerRole[1]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-5 VALUEDIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1Patient VisitPV1[Encounter]Encounter.subject.reference=Patient[1].idis equivalent toEncounter[1]Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1Patient VisitPV1[Patient]is equivalent toPatient[1]Patient[1]
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV2Patient Visit - Additional InfoPV2[Encounter]Encounter.subject.reference=Patient[1].idis equivalent toEncounter[1]Encounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment.
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PRTParticipation (for Patient Visit)PRT[PractitionerRole]Encounter[1].participant.individual.reference=PractitionerRole[2].idis equivalent toPractitionerRole[2]PractitionerRole[2]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".Incorporate PRT content into the Encounter created from the PV1 segment. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.\
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCOrder commonORC[DiagnosticReport]DiagnosticReport[1].encounter.reference=Encounter[1].idis equivalent toDiagnosticReport[1]DiagnosticReport[1]Processing of each ORC segment results in the creation of a new DiagnosticReport resource
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCOrder commonORC[ServiceRequest]DiagnosticReport[1].basedOn.reference=ServiceRequest[1].idis equivalent toServiceRequest[1]ServiceRequest[1]If a ServiceRequest needs to be created for the receiver.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.PRTParticipation (for Observation)PRT[PractitionerRole]ServiceRequest[1].requester.reference=PractitionerRole[3].idis equivalent toPractitionerRole[3]PractitionerRole[3]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 EQUALS "OP" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="OP")and(element("4.3")="HL70443")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBRObservations RequestOBR[DiagnosticReport]is equivalent toDiagnosticReport[1]DiagnosticReport[1]Incorporate OBR content into the DiagnosticReport created from the ORC segment in the same segment group.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBRObservations RequestOBR[Specimen]DiagnosticReport[1].specimen.reference=Specimen.idis equivalent toSpecimen[1]Specimen[1]The OBR specimen data yields one Specimen resource that all Observations generated for the same OBR need to reference.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBRObservations RequestOBR[ServiceRequest]is equivalent toServiceRequest[1]ServiceRequest[1]If a ServiceRequest needs to be created for the receiver.IF ORC VALUEDMapping to ServiceRequest as well is needed if the receiver is not the originator of the order to which this results message responds. This mapping will be completed once OMG/OML mapping is sufficiently completed. We will add the other segment mappings below to ServiceRequest then as well.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTParticipation (for Observation)PRT[PractitionerRole]DiagnosticReport[1].performer.reference=PractitionerRole[4].idis equivalent toPractitionerRole[4]PractitionerRole[4]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 IN ("ARI","TN","TR") AND PRT-4.3 EQUALS "HL70443"PRT.element(4.1) in ("ARI","TN", "TR")and(PRT.element(4.3)="HL70443")If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTParticipation (for Observation)PRT[PractitionerRole]DiagnosticReport[1].resultsInterpreter.reference=PractitionerRole[5].idis equivalent toPractitionerRole[5]PractitionerRole[5]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 EQUALS "PRI" AND PRT-4.3 EQUALS "HL70443"(PRT.element(4.1)="PRI")and(PRT.element(4.3)="HL70443")If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTParticipation (for Observation)PRT[PractitionerRole]DiagnosticReport[1].specimen[1](Specimen.collection.collector.reference)=PractitionerRole[6].idis equivalent toPractitionerRole[6]PractitionerRole[6]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 EQUALS "SC" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="SC")and(element("4.3")="HL70443")If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTParticipation (for Observation)PRT[PractitionerRole]DiagnosticReport[1].requester.reference=PractitionerRole[3].idis equivalent toPractitionerRole[3]PractitionerRole[3]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-4.1 EQUALS "OP" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="OP")and(element("4.3")="HL70443")If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXObservation related to OBROBX[Observation]DiagnosticReport.result.reference=Observation[2].id Observation[2].subject.reference=Patient[1].id; Observation[2].encounter.reference=Encounter[1].id\is equivalent toObservation[2]Observation[2]IF OBX-5 LST.count LESS THAN OR EQUALS 1 AND OBX-29 NOT IN ("QST", "SCI")Implementers should consider the use case where OBX-5 repeats in a given OBX segment. Because the Observation value element is not allowed to repeat, multiple occurrences of OBX-5 must be handled either through the creation of multiple Observation resources, the use of Observation components, the concatenation of the results into a single value or another solution appropriate for the data and the implementation. Note that it is not clear that every OBX represents a results that can be associated with the encounter during which it was ordered/performed.\
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXObservation related to OBROBX[Observation-Component]DiagnosticReport.result.reference=Observation[2].id Observation[2].subject.reference=Patient[1].id; Observation[2].encounter.reference=Encounter[1].id\is equivalent toObservation[2]Observation[2]IF OBX-5 LST.count GREATER THAN 1 AND OBX-29 NOT IN ("QST", "SCI")Implementers should consider the use case where OBX-5 repeats in a given OBX segment. Because the Observation value element is not allowed to repeat, multiple occurrences of OBX-5 must be handled either through the creation of multiple Observation resources, the use of Observation components, the concatenation of the results into a single value or another solution appropriate for the data and the implementation. When multiple OBX segments are tranformed into Observation components in a single Observation resource, implementers should consider how the metadata associated with the result (eg performer, status, date/time, etc) are populated. If the OBX segments being combined into a single resource contain different metadata, it must be considered whether or not the use of components is appropriate.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXObservation related to OBROBX[Observation]ServiceRequest[1].supportingInfo.reference=Observation[1].id; Observation[1].subject.id=Patient[1].idis equivalent toObservation[2]Observation[2]IF OBX-5 LST.count LESS THAN OR EQUALS 1 AND OBX-29 IN ("QST", "SCI")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXObservation related to OBROBX[Observation-Component]ServiceRequest[1].supportingInfo.reference=Observation[1].id; Observation[1].subject.id=Patient[1].idis equivalent toObservation[2]Observation[2]IF OBX-5 LST.count GREATER THAN 1 AND OBX-29 AND OBX-29 IN ("QST", "SCI")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRTParticipation (Observation Participation)PRT[Device]Observation[2].device.reference=Device.idis equivalent toDeviceDeviceIf PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-10 VALUEDIf PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRTParticipation (Observation Participation)PRT[Observation-Location]is equivalent toObservation[2]Observation[2]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-9 VALUED OR IF PRT-14 VALUEDIncorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation location information. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.\
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRTParticipation (Observation Participation)PRT[PractitionerRole]Observation[2].performer.reference=PractitionerRole[7].idis equivalent toPractitionerRole[7]PractitionerRole[7]If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".IF PRT-5 VALUEDIncorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation practitioner information. If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.\
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.NTENotes and commentsNTE[ServiceRequest]is equivalent toObservation[2].noteObservation[2].note
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPMSpecimenSPM[Specimen]DiagnosticReport[1].specimen.reference=Specimen[n].idis equivalent toSpecimen[n]Specimen[n]
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.OBXObservation (for Patient ID)OBX[Observation]Observation[3].subject.reference=Patient[1].id Observation[3].focus.reference=Specimen[n].id\is equivalent toObservation[3]Observation[3]IF OBX-5 LST.count LESS THAN OR EQUALS 1
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.OBXObservation (for Patient ID)OBX[Observation-Component]Observation[3].subject.reference=Patient[1].id Observation[3].focus.reference=Specimen[n].id\is equivalent toObservation[3]Observation[3]IF OBX-5 LST.count GREATER THAN 1

Notes: