RPR: Return patient list
This page lists the structures and trigger events RPR defines, taken from the standard. The written commentary that theADT page carries has not been written for RPR.
Recognising RPR messages
RPR announces itself in MSH-9 like this:
RPR^I03^RPR_I03- MSH-9.1
RPRmessage code: what kind of message this is - MSH-9.2
I03trigger event: what happened in the real world: request/receipt of patient selection list - MSH-9.3
RPR_I03message 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
RPR takes 1 structure.
RPR_I03: Request/Receipt of Patient Selection List
Sent when one thing happens: I03: Request/Receipt of Patient Selection 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..* | |
| PID | 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 1 such group: PROVIDER.
Trigger events
The trigger event is the real-world thing that made the message get sent. RPR defines 1.
| Event | Name | Structure |
|---|---|---|
| I03 | Request/Receipt of Patient Selection List | RPR_I03 |