Submits a parameterized query to a responding system. The QPD segment carries the query parameters and RCP defines response control preferences. Query-response workflows use this to request specific data.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'QBP^O34^QBP_O34|MSG001|P|2.9\r' \
'QPD|Q22^FindCandidates|QRY001|SMITH^JOHN\r' \
'SFT|ACME^Software|v4.1|EHR System|BIN001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
query_name = msg.qpd.message_query_name
query_tag = msg.qpd.query_tag
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_numberHow to construct, send, receive, and extract fields from real-world QBP^O34 messages.
Demonstrates receiving and extracting key fields from a query for order status - order based transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'QBP^O34^QBP_O34|MSG001|P|2.9\r' \
'QPD|Q22^FindCandidates|QRY001|SMITH^JOHN\r' \
'SFT|ACME^Software|v4.1|EHR System|BIN001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
query_name = msg.qpd.message_query_name
query_tag = msg.qpd.query_tag
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_numberStep-by-step guides for working with HL7 v2 in Zato.
Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.
from zato.hl7v2 import HL7Message
raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||QBP^O34^QBP_O34|MSG00001|P|2.9\rQPD|QRY-1001|QRY-2001|\rRCP|I|10^RD'
msg = HL7Message.parse(raw)
query_name = msg.qpd.message_query_name
query_tag = msg.qpd.query_tagBeyond the mandatory MSH header, the required segments are: QPD, RCP. Optional segments provide additional detail when available.
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.
Segments that make up the QBP^O34 message, in order. Groups are shown with their child segments.
Get started with Zato and connect your systems in minutes.