HL7 EAN_U09 (Automated Equipment Notification) | Integration Soup HL7 Reference Guide

HL7 EAN_U09 Automated Equipment Notification

Alerts and notifications from equipment, without pretending they are results.

HL7 message structure EAN_U09 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
EQU	Equipment Detail	Yes	No
EAN_U09.NOTIFICATION	Notification group	Yes	Yes
NDS	Notification Detail	Yes	No
NTE	Notes and Comments	No	No
ROL	Role	No	No

EAN_U09 sends equipment notifications from automated equipment to another application. In practice, these are alerts, warnings, audit events, or operational notices that a Laboratory Automation System or middleware layer needs to display, route, clear, or store.

It is different from ESU_U01. ESU reports state. EAN reports a notification event, such as an alarm, drift warning, door open event, reagent issue, or other equipment-specific notice.

A small EAN U09 example

MSH|^~\&|ANALYZER01|CORELAB|LAS|CITYHOSP|20260723112000||EAN^U09^EAN_U09|EAN090001|P|2.5.1 EQU|ANALYZER01^Chemistry Analyzer 1^CITYHOSP|20260723112000|BUSY^Busy^HL70365|REMOTE^Remote control^L|W^Warning^HL70367 NDS|900201|20260723111945|W^Warning^HL70367|DU001^Detector drift warning^L NTE|1|L|Analyzer reports detector drift above warning threshold; calibration check recommended.|ALERT^Alert note^L

What workflow it represents

The device is raising an event that the receiving system should care about. That may drive an operator alert, a maintenance ticket, a temporary routing rule, or simply an audit trail entry.

Many EAN feeds are noisy until the notification code list is well governed. The useful implementation work is deciding which notifications require action and which are background history.

How to read the structure

MSH identifies the notification event, optional SFT identifies software, and required EQU identifies the equipment.

Each NOTIFICATION group contains required NDS. NDS carries the notification reference number, notification date/time, severity, and notification code. Optional NTE can add display text for operators or support staff.

Implementation traps

Severity needs agreement. If one device sends "warning" for something harmless and another sends "warning" for work-stopping conditions, a shared dashboard will teach users to ignore it.

Do not use NTE as the only actionable content. The notification code should carry the behavior-driving meaning; comments are for context.

Also define clearing behavior. If notifications can be cleared with CNS inside an EAC_U07 command, both sides need to agree whether clearing means acknowledged, resolved, hidden, or deleted.

Reference notes

HL7 v2+ describes EAN_U09 as a message for sending equipment notifications, such as alerts sent by automated equipment to a Laboratory Automation System.