ESU: Automated equipment status update message
This page lists the structures and trigger events ESU defines, taken from the standard. The written commentary that theADT page carries has not been written for ESU.
Recognising ESU messages
ESU announces itself in MSH-9 like this:
MSH-9
ESU^U01^ESU_U01- MSH-9.1
ESUmessage code: what kind of message this is - MSH-9.2
U01trigger event: what happened in the real world: automated equipment status update - MSH-9.3
ESU_U01message structure: which segments to expect, and in what order
How to use these specifications explains MSH-9 in full, with a worked example.
Message structures
ESU takes 1 structure.
ESU_U01: Automated Equipment Status Update
Sent when one thing happens: U01: Automated Equipment Status Update.
You must always send: MSH, EQU. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| SFT | Software Segment | O | 0..* |
| EQU | Equipment Detail | R | 1..1 |
| ISD | Interaction Status Detail | O | 0..* |
| ROL | Role Detail | O | 0..1 |
Trigger events
The trigger event is the real-world thing that made the message get sent. ESU defines 1.
| Event | Name | Structure |
|---|---|---|
| U01 | Automated Equipment Status Update | ESU_U01 |