SSU: Specimen status update message
This page lists the structures and trigger events SSU defines, taken from the standard. The written commentary that theADT page carries has not been written for SSU.
Recognising SSU messages
SSU announces itself in MSH-9 like this:
SSU^U03^SSU_U03- MSH-9.1
SSUmessage code: what kind of message this is - MSH-9.2
U03trigger event: what happened in the real world: specimen status update - MSH-9.3
SSU_U03message 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
SSU takes 1 structure.
SSU_U03: Specimen Status Update
Sent when one thing happens: U03: Specimen Status Update.
You must always send: MSH, EQU, SAC. 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 |
| SPECIMEN_CONTAINER | a group of 3 segments, repeated together | R | 1..* |
| SAC | Specimen Container Detail | R | 1..1 |
| OBX | Specimen related observation | O | 0..* |
| SPECIMEN | a group of 2 segments, repeated together | O | 0..* |
| SPMin SPECIMEN | Specimen | R | 1..1 |
| OBXin SPECIMEN | Specimen related observation | O | 0..* |
| 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: SPECIMEN_CONTAINER, SPECIMEN.
Trigger events
The trigger event is the real-world thing that made the message get sent. SSU defines 1.
| Event | Name | Structure |
|---|---|---|
| U03 | Specimen Status Update | SSU_U03 |