RCI: Return clinical information
This page lists the structures and trigger events RCI defines, taken from the standard. The written commentary that theADT page carries has not been written for RCI.
Recognising RCI messages
RCI announces itself in MSH-9 like this:
RCI^I05^RCI_I05- MSH-9.1
RCImessage code: what kind of message this is - MSH-9.2
I05trigger event: what happened in the real world: request for patient clinical information - MSH-9.3
RCI_I05message 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
RCI takes 1 structure.
RCI_I05: Request For Patient Clinical Information
Sent when one thing happens: I05: Request For Patient Clinical Information.
You must always send: MSH, MSA, QRD, PRD, PID. 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..* | |
| MSA | R | 1..1 | |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| PROVIDER | a group of 2 segments, repeated together | R | 1..* |
| PRD | R | 1..1 | |
| CTD | O | 0..* | |
| PID | R | 1..1 | |
| DG1 | O | 0..* | |
| DRG | O | 0..* | |
| AL1 | O | 0..* | |
| OBSERVATION | a group of 3 segments, repeated together | O | 0..* |
| OBRin OBSERVATION | R | 1..1 | |
| NTEin OBSERVATION | O | 0..* | |
| RESULTSin OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin RESULTS | R | 1..1 | |
| NTEin RESULTS | O | 0..* | |
| NTE | O | 0..* |
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 3 such groups: PROVIDER, OBSERVATION, RESULTS.
Trigger events
The trigger event is the real-world thing that made the message get sent. RCI defines 1.
| Event | Name | Structure |
|---|---|---|
| I05 | Request For Patient Clinical Information | RCI_I05 |