Schedule a demo
Segment

Original-style query definition

Served as the primary query definition segment in HL7 v2's original-mode query framework (pre-v2.4), carrying parameters like query date and time, format, priority, query identifier, and subject identifiers. It was used in QRY messages to request patient data, pharmacy data, and other information from responding systems. Retained for backward compatibility, it has been superseded by the QPD (Query Parameter Definition) segment in v2.4 and later.

0fields
0required
v2.9HL7 version
qrd.py
from zato.hl7v2.v2_9 import QRD

qrd = QRD()

Build QRD segments in Python

How to construct and work with real-world QRD segments.

1

Legacy query placeholder

Empty withdrawn segment kept for old wellness export interfaces

from zato.hl7v2.v2_9 import QRD

# Legacy wellness history query stub
qrd = QRD()
2

Batch compatibility row

Minimal wire form when a partner still emits the segment id only

from zato.hl7v2.v2_9 import QRD

# No fields on modern builds; keep for parsers
qrd = QRD()
3

Screening export note

Comment-only usage documents intent without populating fields

from zato.hl7v2.v2_9 import QRD

# Preventive screening extract compatibility
qrd = QRD()

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

HL7 withdrew the original QRD definition from current guides. The class remains so legacy messages parse, but there are no modern fields to populate.

No. Prefer current query and response patterns your integration guide specifies. Emit QRD only when a downstream system still requires the segment for compatibility.

Map the business need to supported segments and message types in your profile, then retire QRD once partners confirm they no longer expect the stub row.

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

QRD field reference

Complete list of fields in the QRD segment, HL7 v2.9.

#Python nameDatatypeUsageRepeatableTable

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python