RCL: Return clinical list
This page lists the structures and trigger events RCL defines, taken from the standard. The written commentary that theADT page carries has not been written for RCL.
Recognising RCL messages
RCL announces itself in MSH-9 like this:
RCL^I06^RCL_I06- MSH-9.1
RCLmessage code: what kind of message this is - MSH-9.2
I06trigger event: what happened in the real world: request/receipt of clinical data listing - MSH-9.3
RCL_I06message 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
RCL takes 1 structure.
RCL_I06: Request/Receipt of Clinical Data Listing
Sent when one thing happens: I06: Request/Receipt of Clinical Data Listing.
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..* | |
| NTE | O | 0..* | |
| DSP | O | 0..* | |
| DSC | 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: PROVIDER.
Trigger events
The trigger event is the real-world thing that made the message get sent. RCL defines 1.
| Event | Name | Structure |
|---|---|---|
| I06 | Request/Receipt of Clinical Data Listing | RCL_I06 |