Message ORM_O01 to Bundle Map

This ConceptMap represents a mapping from the HL7 V2 Message ORM_O01 to the FHIR Message Bundle.
V2 SegmentDisplayFHIR TargetEquivalence
ORM_O01.MSHMessage Header
Bundle
MessageHeader[1]

Processing of the MSH segment results in the creation of a new MessageHeader resource

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.

If there is a source in MSH-4, or known based on the configuration.

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.

equivalentequivalentequivalentequivalent
ORM_O01.PATIENT.PIDPatient Identification
Patient[1]

Processing of the PID segment results in the creation of a new Patient resource

Provenance[4]

One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.

equivalentequivalent
ORM_O01.PATIENT.PD1Additional Demographics
Patient[1]

Incorporate PD1 content into the Patient created from the PID segment.

Observation[2]
equivalentequivalent
ORM_O01.PATIENT.VISIT.PV1Patient Visit
Encounter[1]

Processing of the PV1 segment results in the creation of a new Encounter resource

Basic
Patient[1]
Coverage[1]
equivalentequivalentequivalentequivalent
ORM_O01.PATIENT.VISIT.PV2Patient Visit- Additional Info
Encounter[1]

Incorporate PV2 content into the Encounter created from the PV1 segment.

equivalent
ORM_O01.PATIENT.INSURANCE.IN1Insurance
Coverage[1]

Processing of the IN1 segment results in the creation of a new Coverage resource

equivalent
ORM_O01.PATIENT.INSURANCE.IN2Insurance Additional Info
Coverage[1]

Incorporate IN2 content into the Coverage created from the IN1 segment.

equivalent
ORM_O01.PATIENT.INSURANCE.IN3Insurance Add'l Info – Cert.
Coverage[1]

Incorporate IN3 content into the Coverage created from the IN1 segment.

equivalent
ORM_O01.PATIENT.AL1Allergy Information
AllergyIntolerance

Processing of the AL1 segment results in the creation of a new AllergyIntolerance resource

equivalent
ORM_O01.ORDER.ORCCommon Order
ServiceRequest[1]

Processing of each ORC segment results in the creation of a new ServiceRequest resource

Task[1]

Processing of each ORC segment results in the creation of a new Task resource which is linked back to the ServiceRequest created for the same ORC segment. =*= The creation of a Task resource and its inclusion in the FHIR bundle should only happen when the receiving system is responsible for fulfillment of the ServiceRequest. Other systems may receive notification of the order, but should not receive a Task Resource if they are not the intended filler system. =*= The actual value of the ORC-1 Order Control Code will yield different population of the Task resource.

Provenance[2]
equivalentequivalentequivalent
ORM_O01.ORDER_DETAIL.CHOICE.OBROrder Detail Segment OBR, etc.
ServiceRequest[1]

Incorporate OBR content into the ServiceRequest created from the ORC segment in the same segment group.

SupplyRequest[1]
equivalentequivalent
ORM_O01.ORDER_DETAIL.CHOICE.RXOPharmacy/Treatment Order
MedicationRequest
equivalent
ORM_O01.ORDER_DETAIL.CHOICE.ODSDietary Orders, Supplements, and Preferences
SupplyRequest[2]
equivalent
ORM_O01.ORDER_DETAIL.NTENotes and Comments (for Detail)
ServiceRequest[1].note
equivalent
ORM_O01.ORDER_DETAIL.DG1Diagnosis
ServiceRequest[1].reasonReference(Condition)

Processing of the DG1 segment results in the creation of a new Condition resource which is referenced in the ServiceRequest created by the ORC segment

equivalent
ORM_O01.ORDER_DETAIL.OBSERVATION.OBXObservation/Result
Observation[1]
Observation[1]
equivalentequivalent

Equivalence Legend

equivalentExact match
wider/narrowerBroader/more specific meaning
relatedtoRelated but not exact
unmatchedNo equivalent in target