HL7 Version 2 to FHIR
1.0.0 - STU 1

HL7 Version 2 to FHIR - Downloaded Version 1.0.0 See the Directory of published versions

## ConceptMap: Message SIU_S12 to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/message-siu-s12-to-bundle | Version: 1.0.0
Standards status: Informative | Computable Name: MessageSIU_S12ToBundle
Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Message SIU_S12 to the FHIR Message Bundle.

This ConceptMap represents the mapping from the HL7 V2 SIU_S12 Message to the FHIR Message Bundle. See also the FHIR Shorthand or the CSV Source.

HL7 v2 | Condition (IF True, args) | HL7 FHIR | Comments
--- | --- | --- | ---
Sort Order | Identifier | Syntax | Name | Cardinality - Min | Cardinality - Max | Computable ANTLR | Computable FHIRPath | Narrative | Primary Target | Segment Map | References
1 | SIU_S12.MSH | MSH | Message Header | 1 | 1 |  |  |  | Bundle | MSH[Bundle] |  |
1 | SIU_S12.MSH | MSH | Message Header | 1 | 1 |  |  |  | MessageHeader | MSH[MessageHeader] |  | Processing of the MSH segment results in the creation of a new MessageHeader resource
1 | SIU_S12.MSH | MSH | Message Header | 1 | 1 |  |  |  | Provenance | MSH[Provenance-Source] | Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].id | .
1 | SIU_S12.MSH | MSH | Message Header | 1 | 1 |  |  |  | Provenance | MSH[Provenance-Transformation] | Provenance[2].target.reference=Bundle.id |
2 | SIU_S12.SCH | SCH | Schedule Activity Information | 1 | 1 |  |  |  | Appointment | SCH[Appointment] | Appointment.participant.actor=Patient[1].id |
2 | SIU_S12.SCH | SCH | Schedule Activity Information | 1 | 1 | IF SCH-26 or SCH-27 VALUED |  |  | ServiceRequest | SCH[ServiceRequest] | Appointment[1].basedOn=ServiceRequest[1..n].id ServiceRequest[1..n].subject=Patient[1].id |
2 | SIU_S12.SCH | SCH | Schedule Activity Information | 1 | 1 |  |  |  | Provenance | SCH[Provenance] |  |
3 | SIU_S12.NTE | [ { NTE } ] | Notes and Comments | 0 | -1 |  |  |  | Appointment | NTE[Appointment-Comment] | Appointment.participant.actor=Patient[1].id | 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
4 | SIU_S12.PATIENT | [{ | --- PATIENT begin | 0 | -1 |  |  |  |  |  |  |
4.1 | SIU_S12.PATIENT.PID | PID | Patient Identification | 1 | 1 |  |  |  | Patient | PID[Patient] |  | Processing of the PID segment results in the creation of a new Patient resource
4.1 | SIU_S12.PATIENT.PID | PID | Patient Identification | 1 | 1 |  |  |  | Appointment | PID[Appointment] | Appointment.participant.actor=Patient[1].id |
4.1 | SIU_S12.PATIENT.PID | PID | Patient Identification | 1 | 1 | IF PID-33 AND PID-34 VALUED |  | One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date. | Provenance | PID[Provenance-Patient] | Provenance.target.reference=Patient[1].id |
4.2 | SIU_S12.PATIENT.PV1 | [ PV1 ] | Patient Visit | 0 | 1 |  |  |  | Encounter | PV1[Encounter] | Encounter[1].subject.reference=Patient[1].id | Processing of the PV1 segment results in the creation of a new Encounter resource
4.2 | SIU_S12.PATIENT.PV1 | [ PV1 ] | Patient Visit | 0 | 1 | IF PV1-43 VALUED |  |  | Basic | PV1[Basic-EncounterHistory] | Basic.extension-EncounterHistory.subject.reference=Patient[1].id |
4.2 | SIU_S12.PATIENT.PV1 | [ PV1 ] | Patient Visit | 0 | 1 |  |  |  | Patient | PV1[Patient] |  |
4.2 | SIU_S12.PATIENT.PV1 | [ PV1 ] | Patient Visit | 0 | 1 | IF PV1-20 VALUE |  |  | Coverage | PV1[Coverage] | Coverage.beneficiary.reference=Patient[1].id |
4.3 | SIU_S12.PATIENT.PV2 | [ PV2 ] | Patient Visit - Additional Info | 0 | 1 |  |  |  | Encounter | PV2[Encounter] | Encounter.subject=Patient[1].id | Incorporate PV2 content into the Encounter created from the PV1 segment.
4.4 | SIU_S12.PATIENT.OBX | [ { OBX } ] | Observation/Result | 0 | -1 | IF OBX-5 LST.count LESS THAN OR EQUALS 1 OR OBX-2 IS "NA" |  |  | Observation | OBX[Observation] | Observation.subject=Patient[1].id |
4.4 | SIU_S12.PATIENT.OBX | [ { OBX } ] | Observation/Result | 0 | -1 | IF OBX-5 LST.count GREATER THAN 1 AND OBX-2 IS NOT "NA" |  |  | Observation | OBX[Observation-Component] | Observation.subject=Patient[1].id | 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.
4.5 | SIU_S12.PATIENT.DG1 | [ { DG1 } ] | Diagnosis | 0 | -1 |  |  | If in context of the patient | Condition | DG1[Condition] | Condition[1].subject.reference=Patient[1].id | Processing of the DG1 segment results in the creation of a new Condition resource
4.6 | SIU_S12.PATIENT | }] | --- PATIENT end | 0 | -1 |  |  |  |  |  |  |
5 | SIU_S12.RESOURCES | { | --- RESOURCES begin RGS | 1 | -1 |  |  |  |  |  |  |
5.1 | SIU_S12.RESOURCES.RGS | RGS | Resource Group Segment | 1 | 1 |  |  |  |  |  |  |
5.2 | SIU_S12.RESOURCES.SERVICE | [{ | --- SERVICE begin AIS | 0 | -1 |  |  |  |  |  |  |
5.2.1 | SIU_S12.RESOURCES.SERVICE.AIS | AIS | Appointment Information - Service | 1 | 1 |  |  | Determine which AIS populates Appointment if there is more than one AIS. | Appointment | AIS[Appointment] |  |
5.2.1 | SIU_S12.RESOURCES.SERVICE.AIS | AIS | Appointment Information - Service | 1 | 1 | IF SCH-26 IS VALUED OR SCH-27 IS VALUED |  |  | ServiceRequest | AIS[ServiceRequest] |  | 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.
5.2.2 | SIU_S12.RESOURCES.SERVICE.NTE | [ { NTE } ] | Notes and Comments | 0 | -1 |  |  | Determine which AIS populates Appointment if there is more than one AIS. | Appointment | NTE[Appointment-Comment] | Appointment.participant.actor=Patient[1].id | 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
5.2.3 | SIU_S12.RESOURCES.SERVICE | }] | --- SERVICE end | 0 | -1 |  |  |  |  |  |  |
5.3 | SIU_S12.RESOURCES.GENERAL_RESOURCE | [{ | --- GENERAL_RESOURCE begin AIG | 0 | -1 |  |  |  |  |  |  |
5.3.1 | SIU_S12.RESOURCES.GENERAL_RESOURCE.AIG | AIG | Appointment Information - General Resource | 1 | 1 |  |  | Determine which AIG populates Appointment if there is more than one AIG. | Appointment | AIG[Appointment] |  |
5.3.2 | SIU_S12.RESOURCES.GENERAL_RESOURCE.NTE | [ { NTE } ] | Notes and Comments | 0 | -1 |  |  |  |  |  |  |
5.3.3 | SIU_S12.RESOURCES.GENERAL_RESOURCE | }] | --- GENERAL_RESOURCE end | 0 | -1 |  |  |  |  |  |  |
5.4 | SIU_S12.RESOURCES.LOCATION_RESOURCE | [{ | --- LOCATION_RESOURCE begin AIL | 0 | -1 |  |  |  |  |  |  |
5.4.1 | SIU_S12.RESOURCES.LOCATION_RESOURCE.AIL | AIL | Appointment Information - Location Resource | 1 | -1 |  |  | Determine which AIL populates Appointment if there is more than one AIL. | Appointment | AIL[Appointment] |  |
5.4.2 | SIU_S12.RESOURCES.LOCATION_RESOURCE.NTE | [ { NTE } ] | Notes and Comments | 0 | -1 |  |  |  |  |  |  |
5.4.3 | SIU_S12.RESOURCES.LOCATION_RESOURCE | }] | --- LOCATION_RESOURCE end | 0 | -1 |  |  |  |  |  |  |
5.5 | SIU_S12.RESOURCES.PERSONNEL_RESOURCE | [{ | --- PERSONNEL_RESOURCE begin AIP | 0 | -1 |  |  |  |  |  |  |
5.5.1 | SIU_S12.RESOURCES.PERSONNEL_RESOURCE.AIP | AIP | Appointment Information - Personnel Resource | 1 | -1 |  |  |  | Appointment | AIP[Appointment] |  |
5.5.2 | SIU_S12.RESOURCES.PERSONNEL_RESOURCE.NTE | [ { NTE } ] | Notes and Comments | 0 | -1 |  |  |  |  |  |  |
5.5.3 | SIU_S12.RESOURCES.PERSONNEL_RESOURCE | }] | --- PERSONNEL_RESOURCE end | 0 | -1 |  |  |  |  |  |  |
5.6 | SIU_S12.RESOURCES | } | --- RESOURCES end | 1 | -1 |  |  |  |  |  |  |

Mapping from (not specified) to (not specified)

Group 1 Mapping from `unspecified code system` to `unspecified code system`

Source Concept Details | Relationship | Target Concept Details | Comment
Codes from | NarrativeCondition | ComputableANTLR |  | Codes from |
SIU_S12.MSH | Message Header |  |  | is equivalent to | Bundle | Bundle |
SIU_S12.MSH | Message Header |  |  | is equivalent to | MessageHeader[1] | MessageHeader[1] | Processing of the MSH segment results in the creation of a new MessageHeader resource
SIU_S12.MSH | Message Header |  |  | is equivalent to | Provenance[1] | Provenance[1] | .
SIU_S12.MSH | Message Header |  |  | is equivalent to | Provenance[2] | Provenance[2] |
SIU_S12.SCH | Schedule Activity Information |  |  | is equivalent to | Appointment[1] | Appointment[1] |
SIU_S12.SCH | Schedule Activity Information |  | IF SCH-26 or SCH-27 VALUED | is equivalent to | ServiceRequest[1..n] | ServiceRequest[1..n] |
SIU_S12.SCH | Schedule Activity Information |  |  | is equivalent to | Provenance[3] | Provenance[3] |
SIU_S12.NTE | Notes and Comments |  |  | is equivalent to | Appointment[1] | 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
SIU_S12.PATIENT.PID | Patient Identification |  |  | is equivalent to | Patient[1] | Patient[1] | Processing of the PID segment results in the creation of a new Patient resource
SIU_S12.PATIENT.PID | Patient Identification |  |  | is equivalent to | Appointment[1] | Appointment[1] |
SIU_S12.PATIENT.PID | Patient Identification | One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date. | IF PID-33 AND PID-34 VALUED | is equivalent to | Provenance[4] | Provenance[4] |
SIU_S12.PATIENT.PV1 | Patient Visit |  |  | is equivalent to | Encounter[1] | Encounter[1] | Processing of the PV1 segment results in the creation of a new Encounter resource
SIU_S12.PATIENT.PV1 | Patient Visit |  | IF PV1-43 VALUED | is equivalent to | Basic | Basic |
SIU_S12.PATIENT.PV1 | Patient Visit |  |  | is equivalent to | Patient[1] | Patient[1] |
SIU_S12.PATIENT.PV1 | Patient Visit |  | IF PV1-20 VALUE | is equivalent to | Coverage[1] | Coverage[1] |
SIU_S12.PATIENT.PV2 | Patient Visit - Additional Info |  |  | is equivalent to | Encounter[1] | Encounter[1] | Incorporate PV2 content into the Encounter created from the PV1 segment.
SIU_S12.PATIENT.OBX | Observation/Result |  | IF OBX-5 LST.count LESS THAN OR EQUALS 1 OR OBX-2 IS "NA" | is equivalent to | Observation[1] | Observation[1] |
SIU_S12.PATIENT.OBX | Observation/Result |  | IF OBX-5 LST.count GREATER THAN 1 AND OBX-2 IS NOT "NA" | is equivalent to | 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.
SIU_S12.PATIENT.DG1 | Diagnosis | If in context of the patient |  | is equivalent to | Condition[1] | Condition[1] | Processing of the DG1 segment results in the creation of a new Condition resource
SIU_S12.RESOURCES.SERVICE.AIS | Appointment Information - Service | Determine which AIS populates Appointment if there is more than one AIS. |  | is equivalent to | Appointment[1] | Appointment[1] |
SIU_S12.RESOURCES.SERVICE.AIS | Appointment Information - Service |  | IF SCH-26 IS VALUED OR SCH-27 IS VALUED | is equivalent to | ServiceRequest[n] | 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.\
SIU_S12.RESOURCES.SERVICE.NTE | Notes and Comments | Determine which AIS populates Appointment if there is more than one AIS. |  | is equivalent to | Appointment[1] | 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
SIU_S12.RESOURCES.GENERAL_RESOURCE.AIG | Appointment Information - General Resource | Determine which AIG populates Appointment if there is more than one AIG. |  | is equivalent to | Appointment[1] | Appointment[1] |
SIU_S12.RESOURCES.LOCATION_RESOURCE.AIL | Appointment Information - Location Resource | Determine which AIL populates Appointment if there is more than one AIL. |  | is equivalent to | Appointment[1] | Appointment[1] |
SIU_S12.RESOURCES.PERSONNEL_RESOURCE.AIP | Appointment Information - Personnel Resource |  |  | is equivalent to | Appointment[1] | Appointment[1] |

### Notes: