ADT^A15 — Pending Transfer

The transfer is about to happen: A15 announces the future destination (bed, service) without yet moving the patient. A02 will confirm execution.

Purpose

A15 announces a planned transfer (physician prescribed the move, place secured at the receiving service, expected in the coming hours). PV1 still reflects the current location, and PV2 (Patient Visit - Additional Info) carries the planned destination via its Prior Pending Location or the appropriate fields.

A15 → A02 is the standard sequence: pre-reservation then actual transfer. If the transfer is cancelled in between, an appropriate cancellation is emitted (per local rules, A26 Cancel Pending Transfer practical variant).

Segment structure

Structure ADT_A15 with PV1 (current state) and PV2 (planned destination).

Real-world example

Patient in CCU scheduled for transfer to medicine at 16:00 on 16 May:

MSH|^~\&|HIS|HOSP01|EHR|CLINIC02|20260516101500||ADT^A15^ADT_A15|MSG00015001|P|2.5.1|||AL|NE
EVN|A15|20260516101500|||DRJONES^Jones^Sarah^^^DR.
PID|1||MRN567890^^^HOSP^MR||DOE^JOHN^A^^MR.||19720515|M|||100 MAIN ST^^ANYTOWN^CA^90210^USA||(555)555-1234|||S||ACCT123456
PV1|1|I|ICU^101^A^HOSP01|EM|||DRSMITH^Smith^James^A^^DR.|||CAR|||1|||DRSMITH^Smith^James^A^^DR.|ADM|||||||||||||||||||HOSP01|||||20260514102530
PV2|MED^205^B^HOSP01||PLANNED TRANSFER CARDIO->MEDICINE||||||||||20260516160000

Acknowledgment (ACK)

MSH|^~\&|EHR|CLINIC02|HIS|HOSP01|20260516101501||ACK^A15^ACK|ACK00015001|P|2.5.1
MSA|AA|MSG00015001

Common errors

• PV1-3 wrongly updated: A15 does NOT move — PV1-3 must remain the current location. Destination belongs in PV2.
• No A02 after A15: systems stay stuck on the pre-reservation indefinitely.
• A15 / A02 confusion: use A15 when a planned time > 1h in the future, A02 when the move just happened.

Related ADT events

See also: ADT^A02, ADT^A14.