Message type

Automated equipment response

Reports the response from automated equipment after receiving a command. The EQU segment identifies the equipment and ECR segments carry the command response details.

9segments

5required

1group

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'EAR^U08^EAR_U08|MSG001|P|2.9\r' \
      'EQU|EQ001|20260701|PU^Powered up'

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

# .. whose fields we can now access.
equipment_id = msg.equ.equipment_instance_identifier
event_time = msg.equ.event_date_time

Python examples

Build and parse EAR^U08 messages in Python

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

Parse an incoming EAR^U08 message

Demonstrates receiving and extracting key fields from a automated equipment response transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'EAR^U08^EAR_U08|MSG001|P|2.9\r' \
      'EQU|EQ001|20260701|PU^Powered up'

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

# .. whose fields we can now access.
equipment_id = msg.equ.equipment_instance_identifier
event_time = msg.equ.event_date_time

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||EAR^U08^EAR_U08|MSG00001|P|2.9\rEQU|ANALYZER-001|20260401120000\rROL|1|AD|AT^Attending^HL70443|1234^CHEN^DAVID^L^^^MD'
msg = HL7Message.parse(raw)

equipment_id = msg.equ.equipment_instance_identifier
event_time = msg.equ.event_date_time

Beyond the mandatory MSH header, the required segments are: EQU, ECD, SAC, ECR. 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

EAR^U08 segment composition

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

#	Segment	Usage	Repeats	Description	Group
1	`MSH`	Required	No	Message header	-
2	`SFT`	Optional	Yes	Software segment	-
3	`UAC`	Optional	No	User authentication credential	-
4	`EQU`	Required	No	Equipment detail	-
5	`ECD`	Required	No	Equipment command	COMMAND_RESPONSE
6	`SAC`	Required	No	Specimen container detail	COMMAND_RESPONSE
7	`SPM`	Optional	Yes	Specimen	COMMAND_RESPONSE
8	`ECR`	Required	No	Equipment command response	COMMAND_RESPONSE
9	`ROL`	Optional	No	Role	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python