This page is part of the HL7 Version 2 to FHIR (v1.0.0-ballot: STU1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/uv/v2mappings/message-siu-s12-to-bundle | Version: 1.0.0-ballot | |||
Active as of 2023-12-19 | Computable Name: MessageSIU_S12ToBundle | |||
Copyright/Legal: Copyright (c) 2020, 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 | </thead>|
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 | Patient | PV1[Patient] | |||||
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 | Observation | OBX[Observation] | Observation.subject=Patient[1].id | ||||
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 SIU_S12 to Bundle
ACTIVE (not intended for production usage). Published on 2023-12-19 by HL7 International / Orders and Observations (HL7 Orders and Observations Workgroup: http://www.hl7.org/Special/com..., Keith W. Boone: kboone@ainq.com, Rob Hausam: rrhausam@gmail.com). Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.
This ConceptMap represents a mapping from the HL7 V2 Message SIU_S12 to the FHIR Message Bundle.
Group 1Mapping from unspecified code system
to unspecified code system
Source Concept Details | Relationship | Target Concept Details | Comment | Properties | |||||||||
Codes from | segmentmap | references | Codes from | antlr | narrative | ||||||||
SIU_S12.MSH | Message Header | MSH[Bundle] | is equivalent to | Bundle | Bundle | ||||||||
SIU_S12.MSH | Message Header | MSH[MessageHeader] | 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 | MSH[Provenance-Source] | Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].id | is equivalent to | Provenance[1] | Provenance[1] | . | ||||||
SIU_S12.MSH | Message Header | MSH[Provenance-Transformation] | Provenance[2].target.reference=Bundle.id | is equivalent to | Provenance[2] | Provenance[2] | |||||||
SIU_S12.SCH | Schedule Activity Information | SCH[Appointment] | Appointment.participant.actor=Patient[1].id | is equivalent to | Appointment[1] | Appointment[1] | |||||||
SIU_S12.SCH | Schedule Activity Information | SCH[ServiceRequest] | Appointment[1].basedOn=ServiceRequest[1..n].id ServiceRequest[1..n].subject=Patient[1].id\ | is equivalent to | ServiceRequest[1..n] | ServiceRequest[1..n] | IF SCH-26 or SCH-27 VALUED | ||||||
SIU_S12.SCH | Schedule Activity Information | SCH[Provenance] | is equivalent to | Provenance[3] | Provenance[3] | ||||||||
SIU_S12.NTE | Notes and Comments | NTE[Appointment-Comment] | Appointment.participant.actor=Patient[1].id | 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 | PID[Patient] | 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 | PID[Appointment] | Appointment.participant.actor=Patient[1].id | is equivalent to | Appointment[1] | Appointment[1] | |||||||
SIU_S12.PATIENT.PID | Patient Identification | PID[Provenance-Patient] | Provenance.target.reference=Patient[1].id | is equivalent to | Provenance[4] | Provenance[4] | 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. | |||||
SIU_S12.PATIENT.PV1 | Patient Visit | PV1[Encounter] | Encounter[1].subject.reference=Patient[1].id | 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 | PV1[Patient] | is equivalent to | Patient[1] | Patient[1] | ||||||||
SIU_S12.PATIENT.PV2 | Patient Visit - Additional Info | PV2[Encounter] | Encounter.subject=Patient[1].id | is equivalent to | Encounter[1] | Encounter[1] | Incorporate PV2 content into the Encounter created from the PV1 segment. | ||||||
SIU_S12.PATIENT.OBX | Observation/Result | OBX[Observation] | Observation.subject=Patient[1].id | is equivalent to | Observation | Observation | |||||||
SIU_S12.PATIENT.DG1 | Diagnosis | DG1[Condition] | Condition[1].subject.reference=Patient[1].id | is equivalent to | Condition[1] | Condition[1] | If in context of the patient | Processing of the DG1 segment results in the creation of a new Condition resource | |||||
SIU_S12.RESOURCES.SERVICE.AIS | Appointment Information - Service | AIS[Appointment] | is equivalent to | Appointment[1] | Appointment[1] | Determine which AIS populates Appointment if there is more than one AIS. | |||||||
SIU_S12.RESOURCES.SERVICE.AIS | Appointment Information - Service | AIS[ServiceRequest] | is equivalent to | ServiceRequest[n] | ServiceRequest[n] | IF SCH-26 IS VALUED OR SCH-27 IS VALUED | 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 | NTE[Appointment-Comment] | Appointment.participant.actor=Patient[1].id | is equivalent to | Appointment[1] | Appointment[1] | Determine which AIS populates Appointment if there is more than one AIS. | 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 | AIG[Appointment] | is equivalent to | Appointment[1] | Appointment[1] | Determine which AIG populates Appointment if there is more than one AIG. | |||||||
SIU_S12.RESOURCES.LOCATION_RESOURCE.AIL | Appointment Information - Location Resource | AIL[Appointment] | is equivalent to | Appointment[1] | Appointment[1] | Determine which AIL populates Appointment if there is more than one AIL. | |||||||
SIU_S12.RESOURCES.PERSONNEL_RESOURCE.AIP | Appointment Information - Personnel Resource | AIP[Appointment] | is equivalent to | Appointment[1] | Appointment[1] |