LSU: Automated equipment log/service update message
This page lists the structures and trigger events LSU defines, taken from the standard. The written commentary that theADT page carries has not been written for LSU.
Recognising LSU messages
LSU announces itself in MSH-9 like this:
LSU^U12^LSU_U12- MSH-9.1
LSUmessage code: what kind of message this is - MSH-9.2
U12trigger event: what happened in the real world: automated equipment log/service update - MSH-9.3
LSU_U12message 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
LSU takes 1 structure.
LSU_U12: Automated Equipment Log/Service Update
2 different trigger events send this structure:
The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate LSU_U13 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.
You must always send: MSH, EQU, EQP. 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 |
| EQP | Equipment Log/Service | R | 1..* |
| ROL | Role Detail | O | 0..1 |
Trigger events
The trigger event is the real-world thing that made the message get sent. LSU defines 2.
| Event | Name | Structure |
|---|---|---|
| U12 | Automated Equipment Log/Service Update | LSU_U12 |
| U13 | Automated Equipment Log/Service Request | LSU_U12 |