HL7 OSQ_Q06 (Order Status Query) | Integration Soup HL7 Reference Guide

HL7 OSQ_Q06 Order Status Query

The older QRD/QRF query for asking a filler what status it knows for an order.

HL7 message structure OSQ_Q06 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

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
QRD	Original-Style Query Definition	Yes	No
QRF	Original style query filter	No	No
DSC	Continuation Pointer	No	No

OSQ_Q06 is an original-mode query for order status. A requester sends OSQ when it needs the current status of an order from the system that owns or fills that order. The response is OSR_Q06.

This is an older query pattern, built with QRD and optional QRF. Newer implementations often prefer event-driven order updates or query-by-parameter profiles, but OSQ still appears in legacy order-entry and ancillary workflows.

A small OSQ Q06 example

MSH|^~\&|EHR|CITYHOSP|LAB|CITYLAB|20260717124000||OSQ^Q06^OSQ_Q06|OSQ060001|P|2.5.1 QRD|20260717124000|R|I|OSQ060001|||1^RD|ORD448811^EHR|ORD|CITYHOSP QRF|LAB|20260715000000|20260717235959

What workflow it represents

The sender is usually checking on an order that was previously placed. The receiver might be a lab, radiology system, pharmacy, supply system, or another filler application. The request should carry enough identifier context for the receiver to find exactly one order.

In practice, that means the query profile must say whether QRD carries placer order number, filler order number, accession, patient identifier, or some combination. Guessing from a naked order number is not reliable.

How to read the structure

MSH identifies OSQ^Q06^OSQ_Q06. QRD is required and holds the query timing, priority, query ID, subject filter, and what is being requested. QRF can narrow the query by filler, dates, status, or other profile-defined filters. DSC supports continuation.

The message structure is small because the local agreement carries a lot of meaning. Document how order identifiers are represented, which system is authoritative, and whether patient context is required.

Implementation traps

The biggest trap is asking by the wrong order number. A placer order number assigned by the EHR may not be enough for the lab after accessioning. If both placer and filler identifiers exist, send the one the responder owns, or send both in the profiled form.

Also be careful with status expectations. OSQ asks for what the filler knows now. It should not be used to command the filler to change the order state.

Reference notes

HL7 references describe Q06 as OSQ/OSR query for order status, using the original-mode QRD/QRF query pattern. HL7 terminology describes order status values as reports of status, not commands to initiate action.