Message ADT_A01 to Bundle Map

This ConceptMap represents a mapping from the HL7 V2 Message ADT_A01 to the FHIR Message Bundle.
V2 SegmentDisplayFHIR TargetEquivalence
ADT_A01.MSHMessage Header
Bundle
MessageHeader[1]

Processing of the MSH segment results in the creation of a new MessageHeader resource.

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.

If there is a source in MSH-4, or known based on the configuration.

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.

equivalentequivalentequivalentequivalent
ADT_A01.SFTSoftware Segment
Provenance[1].entity.what(Device)

If the software does not represent the original source system

Provenance[1].entity.what(Device)

If the software represents the original source system

equivalentequivalent
ADT_A01.EVNEvent Type
Provenance[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.

equivalentequivalent
ADT_A01.PIDPatient Identification
Patient[1]

Processing of the PID segment results in the creation of a new Patient resource

Account
Provenance[4]

One may drop PID-33 from the condition if PID-34 Last Update Facility is still sufficient without a date.

equivalentequivalentequivalent
ADT_A01.PD1Additional Demographics
Patient[1]

Incorporate PD1 content into the Patient created from the PID segment.

Observation[1]
equivalentequivalent
ADT_A01:follow:PID.ROLRole
Patient[1]
CareTeam[1]

When the ROL includes entries with roles in Table HL70443 other than "PP", then they may be candidates for CareTeam, but not all. That is implementation specific.

equivalentequivalent
ADT_A01:follow:PID.PRTParticipation
Patient[1]

If only person information

CareTeam[1]
equivalentequivalent
ADT_A01.NEXT_OF_KIN.NK1Next of Kin / Associated Parties
RelatedPerson[2]

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.

Patient[1]
Patient[1]
equivalentequivalentequivalent
ADT_A01.PV1Patient Visit
Encounter[1]

Processing of the PV1 segment results in the creation of a new Encounter resource

Basic
Patient[1]
Coverage[1]
equivalentequivalentequivalentequivalent
ADT_A01.PV2Patient Visit - Additional Info.
Encounter[1]

Incorporate PV2 content into the Encounter created from the PV1 segment.

equivalent
ADT_A01:follow:PV1.ROLRole
Encounter[1]
equivalent
ADT_A01.OBSERVATION.OBXObservation/Result
Observation[3]

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].

Observation[3]

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].

equivalentequivalent
ADT_A01.AL1Allergy Information
AllergyIntolerance

Processing of the AL1 segment results in the creation of a new AllergyIntolerance resource

equivalent
ADT_A01.DG1Diagnosis Information
Condition[1]

Processing of the DG1 segment results in the creation of a new Condition resource

If in context of the patient

Encounter[1]

If in context of an encounter

EpisodeOfCare[1]

If in context of a episode of care

equivalentequivalentequivalent
ADT_A01.PROCEDURE.PR1Procedures
Procedure
equivalent
ADT_A01.INSURANCE.IN1Insurance
Coverage[1]

Processing of the IN1 segment results in the creation of a new Coverage resource

equivalent
ADT_A01.INSURANCE.IN3Insurance Additional Info - Cert.
CareTeam[1]

Incorporate IN3 content into the Coverage created from the IN1 segment.

equivalent

Equivalence Legend

equivalentExact match
wider/narrowerBroader/more specific meaning
relatedtoRelated but not exact
unmatchedNo equivalent in target