HL7 V2 | TRIGGER EVENT A02

ADT^A02: Transfer a patient

Sent when a patient moves to a new location, such as another unit, room or bed. PV1-3 holds the new location and PV1-6 the prior one.

Message type: ADT · ADT message
Trigger event: A02
Message structure: ADT_A02 · per HL7's current table 0354; older versions sometimes paired events differently
In MSH-9: ADT^A02^ADT_A02
Response: ACK · General acknowledgment message

Segments in ADT_A02 and their FHIR resources

The segments of the ADT_A02 structure as listed in the HL7 v2-to-FHIR Implementation Guide, with the FHIR resources each one maps to. Square brackets mean optional and braces mean the segment can repeat. Indented segments belong to the group above them; “required” means required whenever that group is present.

Segment	Name	Required	FHIR resources
`MSH`	Message Header	Yes	`Bundle` `MessageHeader` `Provenance`
`[{ ARV }]`	Access Restrictions	No · repeats	—
`[{ SFT }]`	Software Segment	No · repeats	`Provenance`
`[ UAC ]`	User Authentication Credential	No	—
`EVN`	Event Type	Yes	`Provenance`
`PID`	Patient Identification	Yes	`Patient` `Account` `Provenance`
`[ PD1 ]`	Additional Demographics	No	`Patient` `Observation`
`[{ OH1 }]`	Employment Status	No · repeats	—
`[{ OH2 }]`	Past or Present Job	No · repeats	—
`[ OH3 ]`	Usual Work	No	—
`[{ OH4 }]`	Combat Zone Work	No · repeats	—
`[{ ARV }]`	Access Restrictions	No · repeats	—
`[{ ROL }]`	Role	No · repeats	`Patient` `CareTeam`
`[{ PRT }]`	Participation	No · repeats	`Patient` `CareTeam`
`PV1`	Patient Visit	Yes	`Encounter` `Basic` `Patient` `Coverage`
`[ PV2 ]`	Patient Visit - Additional Info.	No	`Encounter`
`[{ ARV }]`	Access Restrictions	No · repeats	—
`[{ ROL }]`	Role	No · repeats	`Encounter`
`[{ PRT }]`	Participation	No · repeats	—
`[{ DB1 }]`	Disability Information	No · repeats	—
OBSERVATION group		No · repeats
`OBX`	Observation/Result	Yes	`Observation`
`[ PDA ]`	Patient Death and Autopsy	No	—

Source: HL7 Terminology (THO) 7.4.0 and the HL7 v2-to-FHIR Implementation Guide 1.0.0, published by HL7 International under CC0. Check your trading partner's specification for the values they actually send.