SSR: Specimen status request message
This page lists the structures and trigger events SSR defines, taken from the standard. The written commentary that theADT page carries has not been written for SSR.
Recognising SSR messages
SSR announces itself in MSH-9 like this:
SSR^U04^SSR_U04- MSH-9.1
SSRmessage code: what kind of message this is - MSH-9.2
U04trigger event: what happened in the real world: specimen status request - MSH-9.3
SSR_U04message 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
SSR takes 1 structure.
SSR_U04: Specimen Status Request
Sent when one thing happens: U04: Specimen Status Request.
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 2 segments, repeated together | R | 1..* |
| SAC | Specimen Container Detail | R | 1..1 |
| SPM | Specimen | 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 1 such group: SPECIMEN_CONTAINER.
Trigger events
The trigger event is the real-world thing that made the message get sent. SSR defines 1.
| Event | Name | Structure |
|---|---|---|
| U04 | Specimen Status Request | SSR_U04 |