HL7 LSU_U12 (Automated Equipment Log/Service Update) | Integration Soup HL7 Reference Guide

HL7 LSU_U12 Automated Equipment Log/Service Update

Equipment service and log events that need to leave the device.

HL7 message structure LSU_U12 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
EQP	Equipment/log Service	Yes	Yes
ROL	Role	No	No

LSU_U12 sends log or service events from automated equipment to another application, usually a Laboratory Automation System, middleware layer, service dashboard, or audit repository.

Where EAN_U09 is for notifications and alerts, LSU_U12 is better suited to service and log events: maintenance performed, file or transaction logs produced, service intervals, or audit trail entries that need to be stored outside the equipment.

A small LSU U12 example

MSH|^~\&|ANALYZER01|CORELAB|LAS|CITYHOSP|20260723114500||LSU^U12^LSU_U12|LSU120001|P|2.5.1 EQU|ANALYZER01^Chemistry Analyzer 1^CITYHOSP|20260723114500|IDLE^Idle^HL70365|REMOTE^Remote control^L|N^Normal^HL70367 EQP|PM^Preventive maintenance^L|ANALYZER01_20260723_PM.log|20260723103000|20260723114000|Preventive maintenance completed; calibration verification passed.

What workflow it represents

The equipment is publishing a log or service event so another system can retain it, display it, or use it for operational monitoring. This is useful when instrument maintenance history, error logs, or service activity needs to be visible beyond the device console.

LSU_U12 can also support downtime reconstruction. If an instrument was serviced or produced log evidence during an incident, the receiving system has a record outside the device itself.

How to read the structure

MSH identifies the log/service update. Optional SFT can describe the sending software. Required EQU identifies the equipment.

Repeating required EQP rows carry the event type, optional file name, start and end times, and transaction data. Optional ROL can identify the responsible person or role if the site uses it.

Implementation traps

EQP-5 transaction data is free text, so it is tempting to hide everything there. That is fine for display, but not fine for behavior. If routing, severity, retention, or reporting depends on the event, put the behavior-driving value in a profiled code field.

Time ranges matter. Service events often have a start and end, and the difference between "maintenance started" and "maintenance completed" is operationally important.

Also agree retention and privacy rules. Equipment logs can include operator names, sample identifiers, file paths, or local workstation details if vendors are not careful.

Reference notes

HL7 v2+ describes LSU_U12 as a message used to send log and service events from automated equipment to another application, such as a Laboratory Automation System.