EAR: Automated equipment response message
This page lists the structures and trigger events EAR defines, taken from the standard. The written commentary that theADT page carries has not been written for EAR.
Recognising EAR messages
EAR announces itself in MSH-9 like this:
EAR^U08^EAR_U08- MSH-9.1
EARmessage code: what kind of message this is - MSH-9.2
U08trigger event: what happened in the real world: automated equipment response - MSH-9.3
EAR_U08message 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
EAR takes 1 structure.
EAR_U08: Automated Equipment Response
Sent when one thing happens: U08: Automated Equipment Response.
You must always send: MSH, EQU, ECD, ECR. 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 |
| COMMAND_RESPONSE | a group of 3 segments, repeated together | R | 1..* |
| ECD | Equipment Command Detail | R | 1..1 |
| SPECIMEN_CONTAINER | a group of 2 segments, repeated together | O | 0..1 |
| SACin SPECIMEN_CONTAINER | Specimen Container Detail | R | 1..1 |
| SPMin SPECIMEN_CONTAINER | Specimen | O | 0..* |
| ECR | Equipment Command Response | R | 1..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 2 such groups: COMMAND_RESPONSE, SPECIMEN_CONTAINER.
Trigger events
The trigger event is the real-world thing that made the message get sent. EAR defines 1.
| Event | Name | Structure |
|---|---|---|
| U08 | Automated Equipment Response | EAR_U08 |