ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
HL7 v2Condition (IF True)HL7 FHIRComments
2
Sort OrderIdentifierSyntaxNameCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativePrimary TargetSegment MapReferences
3
1SIU_S12.MSHMSHMessage Header11BundleMSH[Bundle]
4
1SIU_S12.MSHMSHMessage Header11MessageHeader[1]MSH[MessageHeader]Processing of the MSH segment results in the creation of a new MessageHeader resource
5
1SIU_S12.MSHMSHMessage Header11Provenance[1]MSH[Provenance-Source]Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].id.
6
1SIU_S12.MSHMSHMessage Header11Provenance[2]MSH[Provenance-Transformation]Provenance[2].target.reference=Bundle.id
7
2SIU_S12.SCHSCHSchedule Activity Information11Appointment[1]SCH[Appointment]Appointment.participant.actor=Patient[1].id
8
2SIU_S12.SCHSCHSchedule Activity Information11IF SCH-26 or SCH-27 VALUEDServiceRequest[1..n]SCH[ServiceRequest]Appointment[1].basedOn=ServiceRequest[1..n].id
ServiceRequest[1..n].subject=Patient[1].id
9
2SIU_S12.SCHSCHSchedule Activity Information11Provenance[3]SCH[Provenance]
10
3SIU_S12.NTE[ { NTE } ]Notes and Comments0-1Appointment[1]NTE[Appointment-Comment]Appointment.participant.actor=Patient[1].idBecause 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
11
4SIU_S12.PATIENT[{--- PATIENT begin0-1
12
4.1SIU_S12.PATIENT.PIDPIDPatient Identification11Patient[1]PID[Patient]Processing of the PID segment results in the creation of a new Patient resource
13
4.1SIU_S12.PATIENT.PIDPIDPatient Identification11Appointment[1]PID[Appointment]Appointment.participant.actor=Patient[1].id
14
4.1SIU_S12.PATIENT.PIDPIDPatient Identification11IF PID-33 AND PID-34 VALUEDOne may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.Provenance[4]PID[Provenance-Patient]
Provenance.target.reference=Patient[1].id
15
4.2SIU_S12.PATIENT.PV1[ PV1 ]Patient Visit01Encounter[1]PV1[Encounter]
Encounter[1].subject.reference=Patient[1].id
Processing of the PV1 segment results in the creation of a new Encounter resource
16
4.2SIU_S12.PATIENT.PV1[ PV1 ]Patient Visit01IF PV1-43 VALUEDBasicPV1[Basic-EncounterHistory]
Basic.extension-EncounterHistory.subject.reference=Patient[1].id
17
4.2SIU_S12.PATIENT.PV1[ PV1 ]Patient Visit01Patient[1]PV1[Patient]
18
4.2SIU_S12.PATIENT.PV1[ PV1 ]Patient Visit01IF PV1-20 VALUECoverage[1]PV1[Coverage]
Coverage.beneficiary.reference=Patient[1].id
19
4.3SIU_S12.PATIENT.PV2[ PV2 ] Patient Visit - Additional Info01Encounter[1]PV2[Encounter]Encounter.subject=Patient[1].idIncorporate PV2 content into the Encounter created from the PV1 segment.
20
4.4SIU_S12.PATIENT.OBX[ { OBX } ]Observation/Result0-1IF OBX-5 LST.count LESS THAN OR EQUALS 1 OR OBX-2 IS "NA"Observation[1]OBX[Observation]Observation.subject=Patient[1].id
21
4.4SIU_S12.PATIENT.OBX[ { OBX } ]Observation/Result0-1IF OBX-5 LST.count GREATER THAN 1 AND OBX-2 IS NOT "NA"Observation[1]OBX[Observation-Component]Observation.subject=Patient[1].idNote 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.
22
4.5SIU_S12.PATIENT.DG1[ { DG1 } ]Diagnosis0-1If in context of the patientCondition[1]DG1[Condition]Condition[1].subject.reference=Patient[1].idProcessing of the DG1 segment results in the creation of a new Condition resource
23
4.6SIU_S12.PATIENT}]--- PATIENT end0-1
24
5SIU_S12.RESOURCES{--- RESOURCES begin RGS1-1
25
5.1SIU_S12.RESOURCES.RGSRGSResource Group Segment 11
26
5.2SIU_S12.RESOURCES.SERVICE[{--- SERVICE begin AIS0-1
27
5.2.1SIU_S12.RESOURCES.SERVICE.AISAISAppointment Information - Service11Determine which AIS populates Appointment if there is more than one AIS.Appointment[1]AIS[Appointment]
28
5.2.1SIU_S12.RESOURCES.SERVICE.AISAISAppointment Information - Service11IF SCH-26 IS VALUED OR SCH-27 IS VALUEDServiceRequest[n]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.
29
5.2.2SIU_S12.RESOURCES.SERVICE.NTE[ { NTE } ]Notes and Comments0-1Determine which AIS populates Appointment if there is more than one AIS.Appointment[1]NTE[Appointment-Comment]Appointment.participant.actor=Patient[1].idBecause 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
30
5.2.3SIU_S12.RESOURCES.SERVICE}]--- SERVICE end0-1
31
5.3SIU_S12.RESOURCES.GENERAL_RESOURCE[{--- GENERAL_RESOURCE begin AIG0-1
32
5.3.1SIU_S12.RESOURCES.GENERAL_RESOURCE.AIGAIG
Appointment Information - General Resource
11Determine which AIG populates Appointment if there is more than one AIG.Appointment[1]AIG[Appointment]
33
5.3.2SIU_S12.RESOURCES.GENERAL_RESOURCE.NTE[ { NTE } ]Notes and Comments0-1
34
5.3.3SIU_S12.RESOURCES.GENERAL_RESOURCE}]--- GENERAL_RESOURCE end0-1
35
5.4SIU_S12.RESOURCES.LOCATION_RESOURCE[{--- LOCATION_RESOURCE begin AIL0-1
36
5.4.1SIU_S12.RESOURCES.LOCATION_RESOURCE.AILAIL
Appointment Information - Location Resource
1-1Determine which AIL populates Appointment if there is more than one AIL.Appointment[1]AIL[Appointment]
37
5.4.2SIU_S12.RESOURCES.LOCATION_RESOURCE.NTE[ { NTE } ]Notes and Comments0-1
38
5.4.3SIU_S12.RESOURCES.LOCATION_RESOURCE}]--- LOCATION_RESOURCE end0-1
39
5.5SIU_S12.RESOURCES.PERSONNEL_RESOURCE[{--- PERSONNEL_RESOURCE begin AIP0-1
40
5.5.1SIU_S12.RESOURCES.PERSONNEL_RESOURCE.AIPAIP
Appointment Information - Personnel Resource
1-1Appointment[1]AIP[Appointment]
41
5.5.2SIU_S12.RESOURCES.PERSONNEL_RESOURCE.NTE[ { NTE } ]Notes and Comments0-1
42
5.5.3SIU_S12.RESOURCES.PERSONNEL_RESOURCE}]--- PERSONNEL_RESOURCE end0-1
43
5.6SIU_S12.RESOURCES}--- RESOURCES end1-1
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100