HL7 Version 2 to FHIR
0.1.0 - CI Build

HL7 Version 2 to FHIR, published by HL7 International. This is not an authorized publication; it is the continuous build for version 0.1.0). 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

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 Header11ProvenanceMSH[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeader[MSH]
2ORU_R01.SFT[{ SFT }]Software Segment0-1MessageHeaderSFT[MessageHeader]Incorporate SFT content for each of the SFT instances into the MessageHeader created from the MSH segment.
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
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")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.
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")RelatedPersonPRT[RelatedPerson]RelatedPerson.patient.reference=Patient[1].id
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]
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-10 VALUEDDevicePRT[Device]Observation[1].device.reference=Device.id
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-9 VALUED OR IF PRT-14 VALUEDObservationPRT[Observation-Location]
4.1.7.2ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-5 VALUEDPractitionerRolePRT[PractitionerRole]Observation.performer.reference=PractitionerRole[1].id
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]Incorporate 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-1PractitionerRolePRT[PractitionerRole]Encounter[1].participant.individual.reference=PractitionerRole[2].idIncorporate PRT content into the Encounter created from the PV1 segment.
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 common11ServiceRequestORC[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")PractitionerRolePRT[PractitionerRole]DiagnosticReport[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-1
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 Request11If 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")PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].performer.reference=PractitionerRole[4].id
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")PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].resultsInterpreter.reference=PractitionerRole[5].id
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")PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].specimen[1](Specimen.collection.collector.reference)=PractitionerRole[6].id
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")PractitionerRolePRT[PractitionerRole]DiagnosticReport[1].requester.reference=PractitionerRole[3].id
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 1ObservationOBX[Observation]DiagnosticReport.result.reference=Observation[2].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.
4.2.4.3.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBXObservation related to OBR11IF OBX-5 LST.count GREATER THAN 1ObservationOBX[Observation-Component]DiagnosticReport.result.reference=Observation[2].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.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-10 VALUEDDevicePRT[Device]Observation[2].device.reference=Device.id
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 VALUEDObservationPRT[Observation-Location]Incorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation location information.
4.2.4.3.2ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRT[{PRT}]Participation (Observation Participation)0-1IF PRT-5 VALUEDPractitionerRolePRT[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.
4.2.4.3.3ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.NTE{[NTE]}Notes and comments0-1Observation.noteNTE[Annotation]
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[SPM].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 1
4.2.7.2.1ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPECIMEN_OBSERVATION.OBXOBXObservation (for Patient ID)11IF OBX-5 LST.count GREATER THAN 1
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

Formats: XML, JSON, Turtle

MessageORU_R01toBundle (http://hl7.org/fhir/uv/v2mappings/message-oru-r01-to-bundle)

Mapping from ORU_R01 to Bundle

ACTIVE (not intended for production usage). Published on 2020-08-12 by HL7 International (HL7 Orders and Observations Workgroup: http://hl7.org/Special/committ..., Keith W. Boone: kboone@ainq.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.


Source Concept DetailsRelationshipDestination Concept DetailsComment
Code from Code from Code from Code from Code from Code from Code from
ORU_R01.MSHMSH[Bundle]is equivalent toBundle
ORU_R01.MSHMSH[MessageHeader]is equivalent toMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource
ORU_R01.MSHMSH[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeader[MSH]is equivalent toProvenance[1]
ORU_R01.SFTSFT[MessageHeader]is equivalent toMessageHeader[1]Incorporate SFT content for each of the SFT instances into the MessageHeader created from the MSH segment.
ORU_R01.PATIENT_RESULT.PATIENT.PIDPID[Patient]is equivalent toPatient[1]Processing of the PID segment results in the creation of a new Patient resource
ORU_R01.PATIENT_RESULT.PATIENT.PD1PD1[Patient]is equivalent toPatient[1]Incorporate PD1 content into the Patient created from the PID segment.
ORU_R01.PATIENT_RESULT.PATIENT.PRTPRT[PractitionerRole]Patient[1].generalPractitioner.reference=PractitionerRole[1].idis equivalent toPractitionerRole[1]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.
ORU_R01.PATIENT_RESULT.PATIENT.PRTPRT[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idis equivalent toRelatedPerson[1]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")
ORU_R01.PATIENT_RESULT.PATIENT.NK1NK1[RelatedPerson]RelatedPerson.patient.reference=Patient[1].idis equivalent toRelatedPerson[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.NK1NK1[Patient]is equivalent toPatient[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.OBXOBX[Observation]Observation.subject.reference=Patient[1].idis equivalent toObservation[1]IF OBX-5 LST.count LESS THAN OR EQUALS 1
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.OBXOBX[Observation-Component]is equivalent toObservation[1]IF OBX-5 LST.count GREATER THAN 1
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTPRT[Device]Observation[1].device.reference=Device.idis equivalent toDeviceIF PRT-10 VALUED
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTPRT[Observation-Location]is equivalent toObservation[1]IF PRT-9 VALUED OR IF PRT-14 VALUED
ORU_R01.PATIENT_RESULT.PATIENT.PATIENT_OBSERVATION.PRTPRT[PractitionerRole]Observation.performer.reference=PractitionerRole[1].idis equivalent toPractitionerRole[1]IF PRT-5 VALUED
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1PV1[Encounter]Encounter.subject.reference=Patient[1].idis equivalent toEncounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV1PV1[Patient]is equivalent toPatient[1]
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PV2PV2[Encounter]is equivalent toEncounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment.
ORU_R01.PATIENT_RESULT.PATIENT.VISIT.PRTPRT[PractitionerRole]Encounter[1].participant.individual.reference=PractitionerRole[2].idis equivalent toPractitionerRole[2]Incorporate PRT content into the Encounter created from the PV1 segment.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCORC[DiagnosticReport]DiagnosticReport[1].encounter.reference=Encounter[1].idis equivalent toDiagnosticReport[1]Processing of each ORC segment results in the creation of a new DiagnosticReport resource
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.ORCORC[ServiceRequest]DiagnosticReport[1].basedOn.reference=ServiceRequest[1].idis equivalent toServiceRequest[1]
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.COMMON_ORDER.PRTPRT[PractitionerRole]DiagnosticReport[1].requester.reference=PractitionerRole[3].idis equivalent toPractitionerRole[3]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.OBROBR[DiagnosticReport]is equivalent toDiagnosticReport[1]Incorporate OBR content into the DiagnosticReport created from the ORC segment in the same segment group.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBROBR[ServiceRequest]is equivalent toServiceRequest[1]If a ServiceRequest needs to be created for the receiver.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.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTPRT[PractitionerRole]DiagnosticReport[1].performer.reference=PractitionerRole[4].idis equivalent toPractitionerRole[4]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")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTPRT[PractitionerRole]DiagnosticReport[1].resultsInterpreter.reference=PractitionerRole[5].idis equivalent toPractitionerRole[5]IF PRT-4.1 EQUALS "PRI" AND PRT-4.3 EQUALS "HL70443"(PRT.element(4.1)="PRI")and(PRT.element(4.3)="HL70443")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTPRT[PractitionerRole]DiagnosticReport[1].specimen[1](Specimen.collection.collector.reference)=PractitionerRole[6].idis equivalent toPractitionerRole[6]IF PRT-4.1 EQUALS "SC" AND PRT-4.3 EQUALS "HL70443"(element("4.1")="SC")and(element("4.3")="HL70443")
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.PRTPRT[PractitionerRole]DiagnosticReport[1].requester.reference=PractitionerRole[3].idis equivalent toPractitionerRole[3]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.OBSERVATION.OBXOBX[Observation]DiagnosticReport.result.reference=Observation[2].idis equivalent toObservation[2]IF OBX-5 LST.count LESS THAN OR EQUALS 1Implementers 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.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.OBXOBX[Observation-Component]DiagnosticReport.result.reference=Observation[2].idis equivalent toObservation[2]IF OBX-5 LST.count GREATER THAN 1Implementers 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.PRTPRT[Device]Observation[2].device.reference=Device.idis equivalent toDeviceIF PRT-10 VALUED
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRTPRT[Observation-Location]is equivalent toObservation[2]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.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.PRTPRT[PractitionerRole]Observation[2].performer.reference=PractitionerRole[7].idis equivalent toPractitionerRole[7]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.
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.OBSERVATION.NTENTE[Annotation]is equivalent toObservation[2].note
ORU_R01.PATIENT_RESULT.ORDER_OBSERVATION.SPECIMEN.SPMSPM[Specimen]DiagnosticReport[1].specimen.reference=Specimen[SPM].idis equivalent toSpecimen[1]

Notes: