HL7 Version 2 to FHIR
0.1.0 - CI Build

HL7 Version 2 to FHIR, published by null. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions

ConceptMap: Message ADT_A01 to Bundle Map

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

</thead> </table>
HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierSyntaxNameCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativePrimary TargetSegment MapReferences
1ADT_A01.MSHMSHMessage Header11BundleMSH[Bundle]
1ADT_A01.MSHMSHMessage Header11MessageHeaderMSH[MessageHeader]Processing of the MSH segment results in the creation of a new MessageHeader resource
1ADT_A01.MSHMSHMessage Header11ProvenanceMSH[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeader[MSH]
2ADT_A01.SFT[{ SFT }]Software Segment0-1MessageHeaderSFT[MessageHeader]Incorporate SFT content for each of the SFT instances into the MessageHeader created from the MSH segment.
3ADT_A01.UAC[ UAC ]User Authentication Credential01
4ADT_A01.EVNEVNEvent Type11ProvenanceEVN[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeader
5ADT_A01.PIDPIDPatient Identification11PatientPID[Patient]Processing of the PID segment results in the creation of a new Patient resource
5ADT_A01.PIDPIDPatient Identification11If PID-10 is for clinical purposesObservationPID[Observation-Race]Observation.subject.reference=Patient[1].id
5ADT_A01.PIDPIDPatient Identification11IF PID-22 is for clinical purposesObservationPID[Observation-EthnicGroup]Obsevation.subject.reference=Patient[1].id
5ADT_A01.PIDPIDPatient Identification11RelatedPersonPID[RelatedPerson-Mother]RelatedPerson.patient.reference=Patient[1].id
5ADT_A01.PIDPIDPatient Identification11AccountPID[Account]Account.subject.reference=Patient[1].id
6ADT_A01.PD1[ PD1 ]Additional Demographics01PatientPD1[Patient]Incorporate PD1 content into the Patient created from the PID segment.
7ADT_A01:follow:PID.ARV[{ ARV }]Access Restrictions0-1IF ARV-1 IN ("PID", "PD1") AND ARV-3 NOT VALUEDPatientARV[Patient]Resource=Patient[1]FHIR does not yet support field level security tags. The ARV, when located with the PID/PD1 in the v2 message, is meant to only apply to the patient. However, technically it could point to other places in the messageas as well. That is considered out of scope as.
8ADT_A01:follow:PID.ROL[{ ROL }]Role0-1IF ROL-3.1 EQUALS "PP" AND ROL-3.3 EQUALS "HL70443"(element("3.1")="PP")and(element("3.3")="HL70443")PatientROL[Patient-PractitionerRole]
8ADT_A01:follow:PID.ROL[{ ROL }]Role0-1IF ROL-3.1 NOT EQUALS "PP" OR ROL-3.3 NOT EQUALS "HL70443"(element("3.1")!="PP")or(element("3.3")!="HL70443")While most likely all other HL70443 values go to RelatedPerson, the implementation needs to determine whether that is fully accurate.RelatedPersonROL[RelatedPerson]RelatedPerson[1].patient.reference=Patient[1].id
9ADT_A01.NK1[{ NK1 }]Next of Kin / Associated Parties0-1IF NK1-3.1 NOT IN ("EMR", "E", "F", "I", "S")RelatedPersonNK1[RelatedPerson]RelatedPerson[2].patient.reference=Patient[1].idTypically, 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.
9ADT_A01.NK1[{ NK1 }]Next of Kin / Associated Parties0-1IF NK1-3.1 NOT IN ("EMR", "E", "F", "I", "S")PatientNK1[Patient]
9ADT_A01.NK1[{ NK1 }]Next of Kin / Associated Parties0-1IF NK1-3.1 IN ("EMR", "E", "F", "I", "S")PatientNK1[Patient]
10ADT_A01.PV1PV1Patient Visit11EncounterPV1[Encounter]Encounter[1].subject.reference=Patient[1].idProcessing of the PV1 segment results in the creation of a new Encounter resource
10ADT_A01.PV1PV1Patient Visit11PatientPV1[Patient]
11ADT_A01.PV2[ PV2 ]Patient Visit - Additional Info.01EncounterPV2[Encounter]Incorporate PV2 content into the Encounter created from the PV1 segment.
12ADT_A01:follow:PV1.ARV[{ ARV }]Access Restrictions0-1IF ARV-3 NOT VALUEDEncounterARV[Encounter]Resource=Encounter[1]FHIR does not yet support field level security tags. The ARV, when located with the PV1/PV2 in the v2 message, is meant to only apply to the encounter. However, technically it could point to other places in the messageas as well. That is considered out of scope as.
13ADT_A01:follow:PV1.ROL[{ ROL }]Role0-1EncounterROL[Encounter-PractitionerRole]
14ADT_A01.DB1[{ DB1 }]Disability Information0-1
15ADT_A01.OBX[{ OBX }]Observation/Result0-1Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet.ObservationOBX[Observation]Observation.subject.reference=Patient[1].id; Observation.encounter.reference=Encounter[1].id
15ADT_A01.OBX[{ OBX }]Observation/Result0-1Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet.ObservationOBX[Observation-Component]Observation.subject.reference=Patient[1].id; Observation.encounter.reference=Encounter[1].id
16ADT_A01.AL1[{ AL1 }]Allergy Information0-1AllergyIntoleranceAL1[AllergyIntolerance]AllergyIntolerance.patient.reference=Patient[1].idProcessing of the AL1 segment results in the creation of a new AllergyIntolerance resource
17ADT_A01.DG1[{ DG1 }]Diagnosis Information0-1If in context of the patientConditionDG1[Condition]Condition.subject.reference=Patient[1].idProcessing of the DG1 segment results in the creation of a new Condition resource
17ADT_A01.DG1[{ DG1 }]Diagnosis Information0-1If in context of an encounterEncounterDG1[Encounter]Encounter[1].diagnosis.reference=Condition[1].id
17ADT_A01.DG1[{ DG1 }]Diagnosis Information0-1If in context of a episode of careEpisodeOfCareDG1[EpisodeOfCare]EpisodeOfCare.diagnosis.reference=Condition[1].id
18ADT_A01.DRG[ DRG ]Diagnosis Related Group01
19ADT_A01.PROCEDURE[{--- PROCEDURE begin0-1
19.1ADT_A01.PROCEDURE.PR1PR1Procedures11ProcedurePR1[Procedure]Procedure.subject.reference=Patient[1].id
19.2ADT_A01.PROCEDURE.ROL[{ ROL }]Role0-1
19.3/ADT_A01.PROCEDURE}]--- PROCEDURE end
20ADT_A01.GT1[{ GT1 }]Guarantor0-1
21ADT_A01.INSURANCE[{--- INSURANCE begin0-1
21.1ADT_A01.INSURANCE.IN1IN1Insurance11CoverageIN1[Coverage]Coverage.subscriber.reference=Patient[1].idProcessing of the IN1 segment results in the creation of a new Coverage resource
21.2ADT_A01.INSURANCE.IN2[ IN2 ]Insurance Additional Info.01CoverageIN2[Coverage]Incorporate IN2 content into the Coverage created from the IN1 segment.
21.3ADT_A01.INSURANCE.IN3[{ IN3 }]Insurance Additional Info - Cert.0-1CoverageIN3[Coverage]Incorporate IN3 content into the Coverage created from the IN1 segment.
21.4ADT_A01.INSURANCE.ROL[{ ROL }]Role0-1
21.5ADT_A01.INSURANCE.AUT[{ AUT }]Authorization Record0-1
21.6ADT_A01.INSURANCE.RF1[{ RF1 }]Referral Information0-1
21.7/ADT_A01.INSURANCE}]--- INSURANCE end
22ADT_A01.ACC[ ACC ]Accident Information01
23ADT_A01.UB1[ UB1 ]Universal Bill Information01
24ADT_A01.UB2[ UB2 ]Universal Bill 92 Information01
25ADT_A01.PDA[ PDA ]Patient Death and Autopsy01

Formats: XML, JSON, Turtle

MessageADT_A01toBundle (http://hl7.org/fhir/uv/v2mappings/message-adt-a01-to-bundle)

Mapping from ADT_A01 to Bundle

ACTIVE (not intended for production usage). Published on 2020-08-12 by HL7 International, Inc (HL7 Orders and Observations Workgroup: http://hl7.org/Special/committ..., Keith W. Boone: kboone@ainq.com). Copyright (c) 2020, HL7 International, Inc., All Rights Reserved.

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


Source Concept DetailsRelationshipDestination Concept DetailsComment
Code from Code from Code from Code from Code from Code from Code from
ADT_A01.MSHMSH[Bundle]is equivalent toBundle
ADT_A01.MSHMSH[MessageHeader]is equivalent toMessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource
ADT_A01.MSHMSH[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeader[MSH]is equivalent toProvenance[1]
ADT_A01.SFTSFT[MessageHeader]is equivalent toMessageHeader[1]Incorporate SFT content for each of the SFT instances into the MessageHeader created from the MSH segment.
ADT_A01.EVNEVN[Provenance]Provenance.target=Bundle; Provenance.target=MessageHeaderis equivalent toProvenance[2]
ADT_A01.PIDPID[Patient]is equivalent toPatient[1]Processing of the PID segment results in the creation of a new Patient resource
ADT_A01.PIDPID[Observation-Race]Observation.subject.reference=Patient[1].idis equivalent toObservation[1]If PID-10 is for clinical purposes
ADT_A01.PIDPID[Observation-EthnicGroup]Obsevation.subject.reference=Patient[1].idis equivalent toObservation[2]IF PID-22 is for clinical purposes
ADT_A01.PIDPID[RelatedPerson-Mother]RelatedPerson.patient.reference=Patient[1].idis equivalent toRelatedPerson
ADT_A01.PIDPID[Account]Account.subject.reference=Patient[1].idis equivalent toAccount
ADT_A01.PD1PD1[Patient]is equivalent toPatient[1]Incorporate PD1 content into the Patient created from the PID segment.
ADT_A01:follow:PID.ARVARV[Patient]Resource=Patient[1]is equivalent toPatient[1]IF ARV-1 IN ("PID", "PD1") AND ARV-3 NOT VALUEDFHIR does not yet support field level security tags. The ARV, when located with the PID/PD1 in the v2 message, is meant to only apply to the patient. However, technically it could point to other places in the messageas as well. That is considered out of scope as.
ADT_A01:follow:PID.ROLROL[Patient-PractitionerRole]is equivalent toPatient[1]IF ROL-3.1 EQUALS "PP" AND ROL-3.3 EQUALS "HL70443"(element("3.1")="PP")and(element("3.3")="HL70443")
ADT_A01:follow:PID.ROLROL[RelatedPerson]RelatedPerson[1].patient.reference=Patient[1].idis equivalent toRelatedPerson[1]While most likely all other HL70443 values go to RelatedPerson, the implementation needs to determine whether that is fully accurate.IF ROL-3.1 NOT EQUALS "PP" OR ROL-3.3 NOT EQUALS "HL70443"(element("3.1")!="PP")or(element("3.3")!="HL70443")
ADT_A01.NK1NK1[RelatedPerson]RelatedPerson[2].patient.reference=Patient[1].idis equivalent toRelatedPerson[2]IF NK1-3.1 NOT IN ("EMR", "E", "F", "I", "S")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.
ADT_A01.NK1NK1[Patient]is equivalent toPatient[1]IF NK1-3.1 NOT IN ("EMR", "E", "F", "I", "S")
ADT_A01.NK1NK1[Patient]is equivalent toPatient[1]IF NK1-3.1 IN ("EMR", "E", "F", "I", "S")
ADT_A01.PV1PV1[Encounter]Encounter[1].subject.reference=Patient[1].idis equivalent toEncounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource
ADT_A01.PV1PV1[Patient]is equivalent toPatient[1]
ADT_A01.PV2PV2[Encounter]is equivalent toEncounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment.
ADT_A01:follow:PV1.ARVARV[Encounter]Resource=Encounter[1]is equivalent toEncounter[1]IF ARV-3 NOT VALUEDFHIR does not yet support field level security tags. The ARV, when located with the PV1/PV2 in the v2 message, is meant to only apply to the encounter. However, technically it could point to other places in the messageas as well. That is considered out of scope as.
ADT_A01:follow:PV1.ROLROL[Encounter-PractitionerRole]is equivalent toEncounter[1]
ADT_A01.OBXOBX[Observation]Observation.subject.reference=Patient[1].id; Observation.encounter.reference=Encounter[1].idis equivalent toObservation[2]Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet.
ADT_A01.OBXOBX[Observation-Component]Observation.subject.reference=Patient[1].id; Observation.encounter.reference=Encounter[1].idis equivalent toObservation[2]Based on profiles, such as Vital Signs, certain observations are represented on the Observation, while others on its components. No computable guidance available yet.
ADT_A01.AL1AL1[AllergyIntolerance]AllergyIntolerance.patient.reference=Patient[1].idis equivalent toAllergyIntoleranceProcessing of the AL1 segment results in the creation of a new AllergyIntolerance resource
ADT_A01.DG1DG1[Condition]Condition.subject.reference=Patient[1].idis equivalent toConditionIf in context of the patientProcessing of the DG1 segment results in the creation of a new Condition resource
ADT_A01.DG1DG1[Encounter]Encounter[1].diagnosis.reference=Condition[1].idis equivalent toEncounter[1]If in context of an encounter
ADT_A01.DG1DG1[EpisodeOfCare]EpisodeOfCare.diagnosis.reference=Condition[1].idis equivalent toEpisodeOfCare[1]If in context of a episode of care
ADT_A01.PROCEDURE.PR1PR1[Procedure]Procedure.subject.reference=Patient[1].idis equivalent toProcedure
ADT_A01.INSURANCE.IN1IN1[Coverage]Coverage.subscriber.reference=Patient[1].idis equivalent toCoverage[1]Processing of the IN1 segment results in the creation of a new Coverage resource
ADT_A01.INSURANCE.IN2IN2[Coverage]is equivalent toCoverage[1]Incorporate IN2 content into the Coverage created from the IN1 segment.
ADT_A01.INSURANCE.IN3IN3[Coverage]is equivalent toCoverage[1]Incorporate IN3 content into the Coverage created from the IN1 segment.

Notes: