TCU: Automated equipment test code settings update message
This page lists the structures and trigger events TCU defines, taken from the standard. The written commentary that theADT page carries has not been written for TCU.
Recognising TCU messages
TCU announces itself in MSH-9 like this:
TCU^U10^TCU_U10- MSH-9.1
TCUmessage code: what kind of message this is - MSH-9.2
U10trigger event: what happened in the real world - MSH-9.3
TCU_U10message 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
TCU takes 1 structure.
TCU_U10
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 TCU_U11 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, TCC. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| EQU | R | 1..1 | |
| TEST_CONFIGURATION | a group of 2 segments, repeated together | R | 1..* |
| SPM | O | 0..1 | |
| TCC | R | 1..* | |
| ROL | 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: TEST_CONFIGURATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. TCU defines 2.