HL7 Version 2 to FHIR
1.0.0 - STU 1 International flag

HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. 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_A09 to Bundle Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/message-adt-a09-to-bundle Version: 1.0.0
Standards status: Informative Computable Name: MessageADT_A09ToBundle

Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

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

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

HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierSyntaxNameCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativePrimary TargetSegment MapReferences
1ADT_A09.MSHMSHMessage Header11BundleMSH[Bundle]
1ADT_A09.MSHMSHMessage Header11MessageHeaderMSH[MessageHeader]Processing of the MSH segment results in the creation of a new MessageHeader resource.
1ADT_A09.MSHMSHMessage Header11If there is a source in MSH-4, or known based on the configuration.ProvenanceMSH[Provenance-Source]Provenance[1].target.reference=Bundle.id; Provenance[1].target.reference=MessageHeader[1].idIf the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Proviance resource instance to the relevant FHIR resources generated.
1ADT_A09.MSHMSHMessage Header11ProvenanceMSH[Provenance-Transformation]Provenance[2].target.reference=Bundle.idIf the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated.
2ADT_A09.ARV[{ ARV }]Access Restrictions0-1
3ADT_A09.SFT[{ SFT }]Software Segment0-1If the software does represent not the original source systemProvenance.entity.what(Device)SFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="derivation"
3ADT_A09.SFT[{ SFT }]Software Segment0-1If the software represents the original source systemProvenance.entity.what(Device)SFT[Device]Provenance[1].entity.what.reference=Device.id Provenance[1].entity.role="source"
4ADT_A09.UAC[ UAC ]User Authentication Credential01
5ADT_A09.EVNEVNEvent Type11ProvenanceEVN[Provenance]Provenance[3].target.reference=MessageHeader[1].id
5ADT_A09.EVNEVNEvent Type11IF EVN-5 NOT VALUED AND (MSH-22 IS VALUED OR MSH-4 IS VALUED)ProvenanceMSH[Provenance-Operator]Provenance[3].target.reference=MessageHeader[1].idIf EVN-5 is not valued, then the MSH may have either the sending responsible organization (MSH-22) or the sending facility (MSH-4) to reasonable approximate the agent relevant for this Provenance instance.
6ADT_A09.PIDPIDPatient Identification11PatientPID[Patient]Processing of the PID segment results in the creation of a new Patient resource
6ADT_A09.PIDPIDPatient Identification11AccountPID[Account]Account.subject.reference=Patient[1].id
6ADT_A09.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.ProvenancePID[Provenance-Patient]Provenance[4].target.reference=Patient[1].id
7ADT_A09.PD1[ PD1 ]Additional Demographics01PatientPD1[Patient]Incorporate PD1 content into the Patient created from the PID segment.
7ADT_A01.PD1[ PD1 ]Additional Demographics01IF PD1-7 VALUEDObservationPD1[Observation-LivingWill]Observation[1].subject.reference=Patient[1].id
8ADT_A09.PV1PV1Patient Visit11EncounterPV1[Encounter]Encounter[1].subject.reference=Patient[1].idProcessing of the PV1 segment results in the creation of a new Encounter resource
8ADT_A09.PV1PV1Patient Visit11IF PV1-43 VALUEDBasicPV1[Basic-EncounterHistory]Basic.extension-EncounterHistory.subject.reference=Patient[1].id
8ADT_A09.PV1PV1Patient Visit11PatientPV1[Patient]
8ADT_A09.PV1PV1Patient Visit11IF PV1-20 VALUECoveragePV1[Coverage]Coverage.beneficiary.reference=Patient[1].id
9ADT_A09.PV2[ PV2 ]Patient Visit - Additional Info.01EncounterPV2[Encounter]Incorporate PV2 content into the Encounter created from the PV1 segment.
10ADT_A09.DB1[{ DB1 }]Disability Information0-1
11ADT_A09.OBSERVATION[{--- OBSERVATION begin0-1
11.1ADT_A09.OBSERVATION.OBXOBXObservation/Result0-1IF OBX-5 LST.count LESS THAN OR EQUALS 1 OR OBX-2 IS "NA"ObservationOBX[Observation]Observation[2].subject.reference=Patient[1].idOne cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1].
11.1ADT_A09.OBSERVATION.OBXOBXObservation/Result0-1IF OBX-5 LST.count GREATER THAN 1 AND OBX-2 IS NOT "NA"ObservationOBX[Observation-Component]Observation[2].subject.reference=Patient[1].idOne cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1].
11.2ADT_A09.OBSERVATION.PRT[{ PRT }]Participation0-1
11.3/ADT_A09.OBSERVATION}]--- OBSERVATION end

Mapping from (not specified) to (not specified)


Group 1 Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from NarrativeConditionComputableANTLRCodes from
ADT_A09.MSHMessage Headeris equivalent toBundleBundle
ADT_A09.MSHMessage Headeris equivalent toMessageHeader[1]MessageHeader[1]Processing of the MSH segment results in the creation of a new MessageHeader resource.
ADT_A09.MSHMessage HeaderIf there is a source in MSH-4, or known based on the configuration.is equivalent toProvenance[1]Provenance[1]If the FHIR transformation does not yield a FHIR message, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Proviance resource instance to the relevant FHIR resources generated.
ADT_A09.MSHMessage Headeris equivalent toProvenance[2]Provenance[2]If the FHIR transformation does not yield a FHIR Bunlde, but only a set of resource (APIs, repository, etc.) than one should consider attaching this Provenance resource instance to the relevant FHIR resources generated.
ADT_A09.SFTSoftware SegmentIf the software does represent not the original source systemis equivalent toProvenance[1].entity.what(Device)Provenance[1].entity.what(Device)
ADT_A09.SFTSoftware SegmentIf the software represents the original source systemis equivalent toProvenance[1].entity.what(Device)Provenance[1].entity.what(Device)
ADT_A09.EVNEvent Typeis equivalent toProvenance[3]Provenance[3]
ADT_A09.EVNEvent TypeIF EVN-5 NOT VALUED AND (MSH-22 IS VALUED OR MSH-4 IS VALUED)is equivalent toProvenance[3]Provenance[3]If EVN-5 is not valued, then the MSH may have either the sending responsible organization (MSH-22) or the sending facility (MSH-4) to reasonable approximate the agent relevant for this Provenance instance.
ADT_A09.PIDPatient Identificationis equivalent toPatient[1]Patient[1]Processing of the PID segment results in the creation of a new Patient resource
ADT_A09.PIDPatient Identificationis equivalent toAccountAccount
ADT_A09.PIDPatient IdentificationOne 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 VALUEDis equivalent toProvenance[4]Provenance[4]
ADT_A09.PD1Additional Demographicsis equivalent toPatient[1]Patient[1]Incorporate PD1 content into the Patient created from the PID segment.
ADT_A01.PD1Additional DemographicsIF PD1-7 VALUEDis equivalent toObservation[1]Observation[1]
ADT_A09.PV1Patient Visitis equivalent toEncounter[1]Encounter[1]Processing of the PV1 segment results in the creation of a new Encounter resource
ADT_A09.PV1Patient VisitIF PV1-43 VALUEDis equivalent toBasicBasic
ADT_A09.PV1Patient Visitis equivalent toPatient[1]Patient[1]
ADT_A09.PV1Patient VisitIF PV1-20 VALUEis equivalent toCoverage[1]Coverage[1]
ADT_A09.PV2Patient Visit - Additional Info.is equivalent toEncounter[1]Encounter[1]Incorporate PV2 content into the Encounter created from the PV1 segment.
ADT_A09.OBSERVATION.OBXObservation/ResultIF OBX-5 LST.count LESS THAN OR EQUALS 1 OR OBX-2 IS "NA"is equivalent toObservation[2]Observation[2]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1].
ADT_A09.OBSERVATION.OBXObservation/ResultIF OBX-5 LST.count GREATER THAN 1 AND OBX-2 IS NOT "NA"is equivalent toObservation[2]Observation[2]One cannot determine whether this observation made during the PV1/PV2 communicated above, or from a prior visit/stay. It is therefore up to the implementer whether to populate Observation.encounter.reference with the Encounter[1].id or not. Only when the ADT message involves an event before the encounter occurs, e.g., the intiial registration, it is clear that the observation is NOT associated with Encounter[1].

Notes: