HL7 QRF Original style query filter
HL7 field reference QRF fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| QRF.1 | Where Subject Filter | Yes | Yes | ST | |
| QRF.2 | When Data Start Date/Time | No | No | TS | |
| QRF.3 | When Data End Date/Time | No | No | TS | |
| QRF.4 | What User Qualifier | No | Yes | ST | |
| QRF.5 | Other QRY Subject Filter | No | Yes | ST | |
| QRF.6 | Which Date/Time Qualifier | No | Yes | ID | 0156 |
| QRF.7 | Which Date/Time Status Qualifier | No | Yes | ID | 0157 |
| QRF.8 | Date/Time Selection Qualifier | No | Yes | ID | 0158 |
| QRF.9 | When Quantity/Timing Qualifier | No | No | TQ | |
| QRF.10 | Search Confidence Threshold | No | No | NM |
QRF adds filter detail to older query messages.
The standard describes QRF this way: The QRF segment is used with the QRD segment to further refine the content of an original style query. This segment is not carried forward to the recommended queries for v 2.4.
Query segments define what the sender is asking for, how the receiver should format the answer, and how a multi-message response is continued or limited.
A query is an interface contract. The tag, parameters, row definitions, sort/filter rules, and continuation pointers must match exactly or the receiver may return technically valid data that is not what the requester expected.
The v2.5.1 structures show QRF in ADR_A19 - Patient query, DSR_Q01 - Query sent for immediate response, DSR_Q03 - Deferred response to a query, and MFQ_M01 - Master file not otherwise specified, and 26 other message structures. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
QRF-1 carries the criteria or parameters that narrow the query. Keep each parameter in the expected datatype shape and avoid relying on display text that the receiver cannot evaluate.
Repeats should represent separate criteria or parameters in the order the query profile expects, not a free-form pile of search terms.
QRF-2 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
QRF-3 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
QRF-4 carries What User Qualifier for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
QRF-5 carries the criteria or parameters that narrow the query. Keep each parameter in the expected datatype shape and avoid relying on display text that the receiver cannot evaluate.
Repeats should represent separate criteria or parameters in the order the query profile expects, not a free-form pile of search terms.
QRF-6 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 0156; many real interfaces narrow that list further, so follow the receiver's implementation guide.
QRF-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 0157; many real interfaces narrow that list further, so follow the receiver's implementation guide.
QRF-8 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 0158; many real interfaces narrow that list further, so follow the receiver's implementation guide.
QRF-9 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
QRF-10 carries Search Confidence Threshold for this query workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.