Message ORU_R01 to Bundle Map

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

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.

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.

If the software does represent not the original source system

If the software represents the original source system

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

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

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

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.\

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".

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

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

Note that when OBX-5 repeats, the standard mapping is to use Observation.component (see OBX[Observation-Component] map) 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.

If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".

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

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

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.\

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".

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

If a ServiceRequest needs to be created for the receiver.

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".

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

The OBR specimen data yields one Specimen resource that all Observations generated for the same OBR need to reference.

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.

If a ServiceRequest needs to be created for the receiver.

If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".

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.\

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.

If PRT-2 is set to "D" and "inactive" cannot be used, please submit a JIRA with context and rationale.

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 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.\

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 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.\

If PRT-2 is valued to "D", delete, then the implementer needs to consider whether to create a Device with Device.status = "inactive".