Schedule a demo
Message type

Change attending doctor

Updates the attending doctor assignment for a patient. The PV1 segment carries the new attending physician. Clinical systems, order routing, and notification engines consume this to direct communications to the correct provider.

13segments
4required
0groups
v2.9HL7 version
adt-a54.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ADT^A54^ADT_A54|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Build and parse ADT^A54 messages in Python

How to construct, send, receive, and extract fields from real-world ADT^A54 messages.

1

Parse an incoming ADT^A54 message

Demonstrates receiving and extracting key fields from a change attending doctor transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ADT^A54^ADT_A54|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.

from zato.hl7v2 import HL7Message

raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||ADT^A54^ADT_A54|MSG00001|P|2.9\rEVN|A54|20260401120000\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rROL|1|AD|AT^Attending^HL70443|1234^CHEN^DAVID^L^^^MD\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD\rPV1|1|I|MED^201^A^^^MAIN||||1234^CHEN^DAVID^L^^^MD|5678^PATEL^NINA^R^^^MD|||MED|||||||VN-90001|||||||||||||||||||||20260401\rPV2|||^Routine checkup'
msg = HL7Message.parse(raw)

name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Beyond the mandatory MSH header, the required segments are: EVN, PID, PV1. Optional segments provide additional detail when available.

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

ADT^A54 segment composition

Segments that make up the ADT^A54 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5EVNRequiredNoEvent type-
6PIDRequiredNoPatient identification-
7PD1OptionalNoPatient additional demographic-
8ROLOptionalYesRole-
9PRTOptionalYesParticipation information-
10PV1RequiredNoPatient visit-
11PV2OptionalNoPatient visit - additional info-
12ROLOptionalYesRole-
13PRTOptionalYesParticipation information-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python