HL7 RCL_I06 Clinical Data Listing

An older display-style listing of clinical data returned after an RQC query.
HL7 message structure RCL_I06 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
MSA
 Message Acknowledgment Yes No
QRD
 Original-Style Query Definition Yes No
QRF
 Original style query filter No No
RCL_I06.PROVIDER
 Provider group Yes Yes
PRD
 Provider Data Yes No
CTD
 Contact Data No Yes
PID
 Patient Identification Yes No
DG1
 Diagnosis No Yes
DRG
 Diagnosis Related Group No Yes
AL1
 Patient Allergy Information No Yes
NTE
 Notes and Comments No Yes
DSP
 Display Data No Yes
DSC
 Continuation Pointer No No

RCL_I06 is the display-list cousin of the older RCI_I05 clinical information response. It uses original-mode query segments QRD and QRF, then returns clinical listing rows in DSP.

HL7 marks the I06 event as deprecated in modern terminology, so this page is mostly for maintaining older interfaces. If you are designing a new query, look at the QBP/RSP family instead of building a new QRD/QRF/DSP contract.

A small RCL I06 example

MSH|^~\&|LAB|CITYHOSP|REFERRAL|CITYCLINIC|20260718105500||RCL^I06^RCL_I06|RCL060001|P|2.5.1 MSA|AA|RQC060001 QRD|20260718105400|R|I|RQC060001|||10^RD|123456^^^CITYHOSP^MR|RES|LAB QRF|LAB|20260701000000|20260718235959|CBC^Complete blood count^L PRD|RT|City Hospital^Laboratory|1 Hospital Way^^Auckland^^1010^NZ|^^^LAB|CITYLAB PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F DG1|1|I10|D64.9^Anemia unspecified^I10|Anemia unspecified|20260716100000|A AL1|1||PEN^Penicillin^L|MO|Rash NTE|1||Clinical listing returned for requested date range. DSP|1||20260717 CBC WBC 7.1 10*9/L Normal DSP|2||20260717 CBC HGB 133 g/L Normal DSC|END|I

What workflow it represents

The receiver is giving the requester a displayable listing of clinical data that matched the query. This might support a referral review screen, a manual chart lookup, or a legacy bridge that expects a simple list.

The response is useful for reading, but it is weak for automated filing. If the requester needs discrete observations, an RCI_I05 style response with OBR/OBX, or a modern query response, is easier to map safely.

How to read the structure

MSH and MSA tie the response to the request. QRD and QRF describe the old-style query. PRD and CTD identify the responding provider or system.

PID is required. Optional DG1, DRG, and AL1 can give clinical context. DSP carries the returned display rows, and DSC handles continuation.

Implementation traps

Do not file DSP rows as if they were OBX results. A display line may contain a date, test name, value, units, and status, but unless the profile defines a strict parseable layout, it is just text.

Also treat the deprecated status seriously. If this is a legacy interface, document exactly what the receiver returns and how continuation works. If it is a new interface, choose a modern query pattern instead.

Reference notes

HL7 terminology identifies I06 as RQC/RCL request and receipt of clinical data listing and marks it deprecated. The v2+ patient referral material notes that the original-mode QRD/QRF query style was replaced by later query response message pairs.