RPA: Return patient authorization
This page lists the structures and trigger events RPA defines, taken from the standard. The written commentary that theADT page carries has not been written for RPA.
Recognising RPA messages
RPA announces itself in MSH-9 like this:
RPA^I08^RPA_I08- MSH-9.1
RPAmessage code: what kind of message this is - MSH-9.2
I08trigger event: what happened in the real world: request for treatment authorization information - MSH-9.3
RPA_I08message 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
RPA takes 1 structure.
RPA_I08: Request for Treatment Authorization Information
No trigger event in the standard names this structure.
You must always send: MSH, MSA, PRD, PID, PR1. 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 | |
| RF1 | O | 0..1 | |
| AUTHORIZATION | a group of 2 segments, repeated together | O | 0..1 |
| AUTin AUTHORIZATION | R | 1..1 | |
| CTDin AUTHORIZATION | O | 0..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..* | |
| GT1 | O | 0..* | |
| INSURANCE | a group of 3 segments, repeated together | O | 0..* |
| IN1in INSURANCE | R | 1..1 | |
| IN2in INSURANCE | O | 0..1 | |
| IN3in INSURANCE | O | 0..1 | |
| ACC | O | 0..1 | |
| DG1 | O | 0..* | |
| DRG | O | 0..* | |
| AL1 | O | 0..* | |
| PROCEDURE | a group of 2 segments, repeated together | R | 1..* |
| PR1 | R | 1..1 | |
| AUTHORIZATION | a group of 2 segments, repeated together | O | 0..1 |
| AUTin AUTHORIZATION | R | 1..1 | |
| CTDin AUTHORIZATION | O | 0..1 | |
| 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..* | |
| VISIT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in VISIT | R | 1..1 | |
| PV2in VISIT | 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 8 such groups: AUTHORIZATION, PROVIDER, INSURANCE, PROCEDURE, AUTHORIZATION, OBSERVATION, RESULTS, VISIT.
Trigger events
The trigger event is the real-world thing that made the message get sent. RPA defines 0.
| Event | Name | Structure |
|---|