EAN: Automated equipment notification message
This page lists the structures and trigger events EAN defines, taken from the standard. The written commentary that theADT page carries has not been written for EAN.
Recognising EAN messages
EAN announces itself in MSH-9 like this:
EAN^U09^EAN_U09- MSH-9.1
EANmessage code: what kind of message this is - MSH-9.2
U09trigger event: what happened in the real world: automated equipment notification - MSH-9.3
EAN_U09message 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
EAN takes 1 structure.
EAN_U09: Automated Equipment Notification
Sent when one thing happens: U09: Automated Equipment Notification.
You must always send: MSH, EQU, NDS. 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 |
| NOTIFICATION | a group of 2 segments, repeated together | R | 1..* |
| NDS | Notification Detail | R | 1..1 |
| NTE | Notification Note | O | 0..1 |
| ROL | Role Detail | O | 0..1 |
R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 1 such group: NOTIFICATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. EAN defines 1.
| Event | Name | Structure |
|---|---|---|
| U09 | Automated Equipment Notification | EAN_U09 |