RQC: Request clinical information
This page lists the structures and trigger events RQC defines, taken from the standard. The written commentary that theADT page carries has not been written for RQC.
Recognising RQC messages
RQC announces itself in MSH-9 like this:
RQC^I05^RQC_I05- MSH-9.1
RQCmessage code: what kind of message this is - MSH-9.2
I05trigger event: what happened in the real world: request for patient clinical information - MSH-9.3
RQC_I05message 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
RQC takes 1 structure.
RQC_I05: Request For Patient Clinical Information
2 different trigger events send this structure:
The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate RQC_I06 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.
You must always send: MSH, QRD, 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..* | |
| QRD | R | 1..1 | |
| QRF | 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..* | |
| 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. RQC defines 2.
| Event | Name | Structure |
|---|---|---|
| I05 | Request For Patient Clinical Information | RQC_I05 |
| I06 | Request/Receipt of Clinical Data Listing | RQC_I05 |