Message SIU_S12 to Bundle Map
| V2 Segment | Display | FHIR Target | Equivalence |
|---|---|---|---|
SIU_S12.MSH | Message Header | BundleMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource Provenance[1]. Provenance[2] | equivalentequivalentequivalentequivalent |
SIU_S12.SCH | Schedule Activity Information | Appointment[1]ServiceRequest[1..n]Provenance[3] | equivalentequivalentequivalent |
SIU_S12.NTE | Notes and Comments | Appointment[1]Because multiple NTE segments in a message all need to map to a single Appointment.comment element, the content of the NTEs will need to be concatenated together in R4 | equivalent |
SIU_S12.PATIENT.PID | Patient Identification | Patient[1]Processing of the PID segment results in the creation of a new Patient resource Appointment[1]Provenance[4]One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date. | equivalentequivalentequivalent |
SIU_S12.PATIENT.PV1 | Patient Visit | Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource BasicPatient[1]Coverage[1] | equivalentequivalentequivalentequivalent |
SIU_S12.PATIENT.PV2 | Patient Visit - Additional Info | Encounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment. | equivalent |
SIU_S12.PATIENT.OBX | Observation/Result | Observation[1]Observation[1]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. | equivalentequivalent |
SIU_S12.PATIENT.DG1 | Diagnosis | Condition[1]Processing of the DG1 segment results in the creation of a new Condition resource If in context of the patient | equivalent |
SIU_S12.RESOURCES.SERVICE.AIS | Appointment Information - Service | Appointment[1]Determine which AIS populates Appointment if there is more than one AIS. ServiceRequest[n]Note that each ServiceRequest being created includes data from SCH segment. If SCH-26 and SCH-27 repeat, then the implementer needs to determine how to align this with potentially repeating AIS segments.\ | equivalentequivalent |
SIU_S12.RESOURCES.SERVICE.NTE | Notes and Comments | Appointment[1]Because multiple NTE segments in a message all need to map to a single Appointment.comment element, the content of the NTEs will need to be concatenated together in R4 Determine which AIS populates Appointment if there is more than one AIS. | equivalent |
SIU_S12.RESOURCES.GENERAL_RESOURCE.AIG | Appointment Information - General Resource | Appointment[1]Determine which AIG populates Appointment if there is more than one AIG. | equivalent |
SIU_S12.RESOURCES.LOCATION_RESOURCE.AIL | Appointment Information - Location Resource | Appointment[1]Determine which AIL populates Appointment if there is more than one AIL. | equivalent |
SIU_S12.RESOURCES.PERSONNEL_RESOURCE.AIP | Appointment Information - Personnel Resource | Appointment[1] | equivalent |