RQP: Request patient demographics
This page lists the structures and trigger events RQP defines, taken from the standard. The written commentary that theADT page carries has not been written for RQP.
Recognising RQP messages
RQP announces itself in MSH-9 like this:
RQP^I04^RQP_I04- MSH-9.1
RQPmessage code: what kind of message this is - MSH-9.2
I04trigger event: what happened in the real world: request for patient demographic data - MSH-9.3
RQP_I04message 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
RQP takes 1 structure.
RQP_I04: request for patient demographic data
Sent when one thing happens: I04: request for patient demographic data.
You must always send: MSH, 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..* | |
| 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..* | |
| 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. RQP defines 1.
| Event | Name | Structure |
|---|---|---|
| I04 | request for patient demographic data | RQP_I04 |