RPL: Return patient display list
This page lists the structures and trigger events RPL defines, taken from the standard. The written commentary that theADT page carries has not been written for RPL.
Recognising RPL messages
RPL announces itself in MSH-9 like this:
RPL^I02^RPL_I02- MSH-9.1
RPLmessage code: what kind of message this is - MSH-9.2
I02trigger event: what happened in the real world: request/receipt of patient selection display list - MSH-9.3
RPL_I02message 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
RPL takes 1 structure.
RPL_I02: Request/Receipt of Patient Selection Display List
Sent when one thing happens: I02: Request/Receipt of Patient Selection Display List.
You must always send: MSH, MSA, PRD. 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 | |
| PROVIDER | a group of 2 segments, repeated together | R | 1..* |
| PRD | R | 1..1 | |
| CTD | 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. RPL defines 1.
| Event | Name | Structure |
|---|---|---|
| I02 | Request/Receipt of Patient Selection Display List | RPL_I02 |