Message OML_O21 to Bundle Map
| V2 Segment | Display | FHIR Target | Equivalence |
|---|---|---|---|
OML_O21.MSH | Message Header | BundleMessageHeader[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 |
OML_O21.SFT | Software | Provenance[1].entity.what(Device)If the software does not represent the original source system Provenance[1].entity.what(Device)If the software represents the original source system | equivalentequivalent |
OML_O21.PATIENT.PID | Patient 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 |
OML_O21.PATIENT.PD1 | Additional Demographics | Patient[1]Incorporate PD1 content into the Patient created from the PID segment. Observation[2] | equivalentequivalent |
OML_O21.PATIENT.PRT | Participation (for Patient) | PractitionerRole[1]Incorporate PRT content into the Patient created from the PID segment when the PRT contains practitioner related data. RelatedPerson[1] | equivalentequivalent |
OML_O21.PATIENT.NK1 | Next of Kin/Associated Parties | RelatedPerson[2]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. The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin data Patient[1]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. The FHIR location will depend on the nature of the data being exchanged and how the systems use next of kin data | equivalentequivalent |
OML_O21.PATIENT.PATIENT_VISIT.PV1 | Patient Visit | Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource BasicPatient[1]Coverage[1] | equivalentequivalentequivalentequivalent |
OML_O21.PATIENT.PATIENT_VISIT.PV2 | Patient Visit- Additional Info | Encounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment. | equivalent |
OML_O21.PATIENT.PATIENT_VISIT.PRT | Participation (for Patient Visit) | PractitionerRole[2]Incorporate PRT content into the Encounter created from the PV1 segment. | equivalent |
OML_O21.PATIENT.INSURANCE.IN1 | Insurance | Coverage[1]Processing of the IN1 segment results in the creation of a new Coverage resource | equivalent |
OML_O21.PATIENT.INSURANCE.IN3 | Insurance Additional Information, Certification | Coverage[1] | equivalent |
OML_O21.PATIENT.AL1 | Allergy Information | AllergyIntoleranceProcessing of the AL1 segment results in the creation of a new AllergyIntolerance resource | equivalent |
OML_O21.ORDER.ORC | Common Order | ServiceRequest[1]Processing of each ORC segment results in the creation of a new ServiceRequest resource 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. | equivalentequivalent |
OML_O21.ORDER.PRT | Participation (for Common Order) | PractitionerRole[3] | equivalent |
OML_O21.ORDER.TIMING.TQ1 | Timing/Quantity | ServiceRequest[1] | equivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.OBR | Observation Request | ServiceRequest[1]Incorporate OBR content into the ServiceRequest created from the ORC segment in the same segment group. Specimen[each] | equivalentequivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.NTE | Notes and Comments (for Detail) | ServiceRequest[1] | equivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.PRT | Participation (for Observation Request) | PractitionerRole[4]PractitionerRole[3] | equivalentequivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.DG1 | Diagnosis | Condition[1]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 |
OML_O21.ORDER.OBSERVATION_REQUEST.OBSERVATION.OBX | Observation/Result | Observation[1]Observation[1] | equivalentequivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.OBSERVATION.PRT | Participation (for OBX) | Device[1]Observation[1]Incorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation location information. PractitionerRole[7]Incorporate PRT content into the Observation created from the OBX segment in the same segment group when it represents observation practitioner information. | equivalentequivalentequivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.OBSERVATION.NTE | Notes and Comments (for Results) | Observation[1] | equivalent |
OML_O21.ORDER.OBSERVATION_REQUEST.SPECIMEN.SPM | Specimen | Specimen | equivalent |