INR: Automated equipment inventory request message
This page lists the structures and trigger events INR defines, taken from the standard. The written commentary that theADT page carries has not been written for INR.
Recognising INR messages
INR announces itself in MSH-9 like this:
MSH-9
INR^U06^INR_U06- MSH-9.1
INRmessage code: what kind of message this is - MSH-9.2
U06trigger event: what happened in the real world: automated equipment inventory request - MSH-9.3
INR_U06message 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
INR takes 1 structure.
INR_U06: Automated Equipment Inventory Request
Sent when one thing happens: U06: Automated Equipment Inventory Request.
You must always send: MSH, EQU, INV. 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 |
| INV | Inventory Detail | R | 1..* |
| ROL | Role Detail | O | 0..1 |
Trigger events
The trigger event is the real-world thing that made the message get sent. INR defines 1.
| Event | Name | Structure |
|---|---|---|
| U06 | Automated Equipment Inventory Request | INR_U06 |