Message type

Change an outpatient to an inpatient

Converts an outpatient encounter into an inpatient stay. The PV1 segment carries the updated patient class and assigned bed while PID identifies the patient. Census systems, dietary, and pharmacy use this to adjust service levels.

42segments

8required

4groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ADT^A06^ADT_A06|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

Python examples

Build and parse ADT^A06 messages in Python

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

Parse an incoming ADT^A06 message

Demonstrates receiving and extracting key fields from a change an outpatient to an inpatient transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ADT^A06^ADT_A06|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

Tutorials

Learn by building

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

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

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^A06^ADT_A06|MSG00001|P|2.9\rEVN|A06|20260401120000\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rOH1|1|EMPLOYED^Employed^HL70761|20200101\rOH2|1|SOFTWARE^Software developer^SOC||20200101\rOH3|1|SOFTWARE^Software developer^SOC\rOH4|1|N\rPV1|1|I|MED^201^A^^^MAIN||||1234^CHEN^DAVID^L^^^MD|5678^PATEL^NINA^R^^^MD|||MED|||||||VN-90001|||||||||||||||||||||20260401'
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, NK1, PV1, OBX, PR1, IN1. 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.

Reference

ADT^A06 segment composition

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

#	Segment	Usage	Repeats	Description	Group
1	`MSH`	Required	No	Message header	-
2	`ARV`	Optional	Yes	Access restriction	-
3	`SFT`	Optional	Yes	Software segment	-
4	`UAC`	Optional	No	User authentication credential	-
5	`EVN`	Required	No	Event type	-
6	`PID`	Required	No	Patient identification	-
7	`PD1`	Optional	No	Patient additional demographic	-
8	`OH1`	Optional	Yes	Employment status	-
9	`OH2`	Optional	Yes	Past or present job	-
10	`OH3`	Optional	No	Usual work	-
11	`OH4`	Optional	Yes	Combat zone work	-
12	`ARV`	Optional	Yes	Access restriction	-
13	`ROL`	Optional	Yes	Role	-
14	`PRT`	Optional	Yes	Participation information	-
15	`MRG`	Optional	No	Merge patient information	-
16	`NK1`	Required	No	Next of kin / associated parties	NEXT_OF_KIN
17	`OH2`	Optional	Yes	Past or present job	NEXT_OF_KIN
18	`OH3`	Optional	No	Usual work	NEXT_OF_KIN
19	`PV1`	Required	No	Patient visit	-
20	`PV2`	Optional	No	Patient visit - additional info	-
21	`ARV`	Optional	Yes	Access restriction	-
22	`ROL`	Optional	Yes	Role	-
23	`PRT`	Optional	Yes	Participation information	-
24	`DB1`	Optional	Yes	Disability	-
25	`OBX`	Required	No	Observation result	OBSERVATION
26	`PRT`	Optional	Yes	Participation information	OBSERVATION
27	`AL1`	Optional	Yes	Patient allergy information	-
28	`IAM`	Optional	Yes	Patient adverse reaction information	-
29	`DG1`	Optional	Yes	Diagnosis	-
30	`DRG`	Optional	No	Diagnosis related group	-
31	`PR1`	Required	No	Procedures	PROCEDURE
32	`ROL`	Optional	Yes	Role	PROCEDURE
33	`PRT`	Optional	Yes	Participation information	PROCEDURE
34	`GT1`	Optional	Yes	Guarantor	-
35	`IN1`	Required	No	Insurance	INSURANCE
36	`IN2`	Optional	No	Insurance additional info	INSURANCE
37	`IN3`	Optional	Yes	Insurance additional info - certification	INSURANCE
38	`ROL`	Optional	Yes	Role	INSURANCE
39	`PRT`	Optional	Yes	Participation information	INSURANCE
40	`ACC`	Optional	No	Accident	-
41	`UB1`	Optional	No	UB82	-
42	`UB2`	Optional	No	Uniform billing data	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python