CSU: Unsolicited study data message
This page lists the structures and trigger events CSU defines, taken from the standard. The written commentary that theADT page carries has not been written for CSU.
Recognising CSU messages
CSU announces itself in MSH-9 like this:
CSU^C09^CSU_C09- MSH-9.1
CSUmessage code: what kind of message this is - MSH-9.2
C09trigger event: what happened in the real world - MSH-9.3
CSU_C09message 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
CSU takes 1 structure.
CSU_C09
No trigger event in the standard names this structure.
You must always send: MSH, PID, CSR, OBR, OBX, RXA, RXR. 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..* | |
| PATIENT | a group of 6 segments, repeated together | R | 1..* |
| PID | R | 1..1 | |
| PD1 | O | 0..1 | |
| NTE | O | 0..* | |
| VISIT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in VISIT | R | 1..1 | |
| PV2in VISIT | O | 0..1 | |
| CSR | R | 1..1 | |
| STUDY_PHASE | a group of 2 segments, repeated together | R | 1..* |
| CSP | O | 0..1 | |
| STUDY_SCHEDULE | a group of 3 segments, repeated together | R | 1..* |
| CSS | O | 0..1 | |
| STUDY_OBSERVATION | a group of 4 segments, repeated together | R | 1..* |
| ORC | O | 0..1 | |
| OBR | R | 1..1 | |
| TIMING_QTY | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING_QTY | R | 1..1 | |
| TQ2in TIMING_QTY | O | 0..* | |
| OBX | R | 1..* | |
| STUDY_PHARM | a group of 2 segments, repeated together | R | 1..* |
| ORC | O | 0..1 | |
| RX_ADMIN | a group of 2 segments, repeated together | R | 1..* |
| RXA | R | 1..1 | |
| RXR | R | 1..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 8 such groups: PATIENT, VISIT, STUDY_PHASE, STUDY_SCHEDULE, STUDY_OBSERVATION, TIMING_QTY, STUDY_PHARM, RX_ADMIN.
Trigger events
The trigger event is the real-world thing that made the message get sent. CSU defines 0.
| Event | Name | Structure |
|---|