HL7 ADT_A61 Change Consulting Doctor
ADT_A61 is sent when the consulting doctor or consulting doctor list changes for a patient. It is a provider participation event, usually tied to the active visit.
Receivers use it for specialist worklists, billing attribution, notifications, consult tracking, and clinical-team displays. The message is small, but the downstream consequences can be very visible to clinicians.
A small A61 example
What systems do with it
The sender is usually the PAS/EHR. Receivers update consulting-provider attribution for the visit and may start, stop, or re-route specialist tasks from the event time onward.
If a consultant is removed rather than added, the local profile needs a clear action-code or role-end-date convention. Otherwise one system may see a current list while another keeps accumulating historical consultants.
How to read the structure
The key visit field is PV1-9, Consulting Doctor. The message also includes MSH, EVN, PID, optional PD1, required PV1, optional ROL, and optional PV2.
Implementation traps
Do not bury patient demographic changes in A61. Send or expect A08 separately when demographics changed at the same time. Also confirm whether PV1-9 is a full replacement list or a delta in your local profile; repeated provider fields are a classic place for quiet drift.
Reference notes
The HL7 v2+ ADT_A61 page describes A61 as a change in consulting physician(s), with the new consulting doctor(s) in PV1-9 and event timing in EVN-6 when available.