RPI: Return patient information
This page lists the structures and trigger events RPI defines, taken from the standard. The written commentary that theADT page carries has not been written for RPI.
Recognising RPI messages
RPI announces itself in MSH-9 like this:
RPI^I01^RPI_I01- MSH-9.1
RPImessage code: what kind of message this is - MSH-9.2
I01trigger event: what happened in the real world: request for insurance information - MSH-9.3
RPI_I01message 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
RPI takes 2 structures.
RPI_I01: Request for Insurance Information
Sent when one thing happens: I01: Request for Insurance Information.
You must always send: MSH, MSA, 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 | |
| PROVIDER | a group of 2 segments, repeated together | R | 1..* |
| PRD | R | 1..1 | |
| CTD | O | 0..* | |
| PID | R | 1..1 | |
| NK1 | O | 0..* | |
| GUARANTOR_INSURANCE | a group of 2 segments, repeated together | O | 0..1 |
| GT1in GUARANTOR_INSURANCE | O | 0..* | |
| INSURANCEin GUARANTOR_INSURANCE | a group of 3 segments, repeated together | R | 1..* |
| IN1in INSURANCE | R | 1..1 | |
| IN2in INSURANCE | O | 0..1 | |
| IN3in INSURANCE | O | 0..1 | |
| 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, GUARANTOR_INSURANCE, INSURANCE.
RPI_I04: request for patient demographic data
Sent when one thing happens: I04: request for patient demographic data.
| 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 | R | 1..1 | |
| NK1 | O | 0..* | |
| GUARANTOR_INSURANCE | a group of 2 segments, repeated together | O | 0..1 |
| GT1in GUARANTOR_INSURANCE | O | 0..* | |
| INSURANCEin GUARANTOR_INSURANCE | a group of 3 segments, repeated together | R | 1..* |
| IN1in INSURANCE | R | 1..1 | |
| IN2in INSURANCE | O | 0..1 | |
| IN3in INSURANCE | O | 0..1 | |
| NTE | O | 0..* |
Trigger events
The trigger event is the real-world thing that made the message get sent. RPI defines 2.
| Event | Name | Structure |
|---|---|---|
| I01 | Request for Insurance Information | RPI_I01 |
| I04 | request for patient demographic data | RPI_I04 |