Returns a query response containing the requested data. The QAK segment reports the query status, QPD echoes the original query parameters, and the payload segments carry the result data. Query-response workflows consume this.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'RSP^Z88^RSP_Z88|MSG001|P|2.9\r' \
'QAK|QRY001|OK|Q22\r' \
'QPD|Q22^FindCandidates|QRY001|SMITH^JOHN'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
query_tag = msg.qak.query_tag
status = msg.qak.query_response_status
query_name = msg.qpd.message_query_name
query_tag = msg.qpd.query_tagHow to construct, send, receive, and extract fields from real-world RSP^Z88 messages.
Demonstrates receiving and extracting key fields from a dispense information response transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'RSP^Z88^RSP_Z88|MSG001|P|2.9\r' \
'QAK|QRY001|OK|Q22\r' \
'QPD|Q22^FindCandidates|QRY001|SMITH^JOHN'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
query_tag = msg.qak.query_tag
status = msg.qak.query_response_status
query_name = msg.qpd.message_query_name
query_tag = msg.qpd.query_tagStep-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||RSP^Z88^RSP_Z88|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|\rQAK|QRY-2001|OK\rQPD|QRY-1001|QRY-2001|\rRCP|I|10^RD\rDSC|CONT-001'
msg = HL7Message.parse(raw)
query_tag = msg.qak.query_tag
status = msg.qak.query_response_statusBeyond the mandatory MSH header, the required segments are: MSA, QAK, QPD, RCP, PID, AL1, PV1, ORC. 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 RSP^Z88 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | SFT | Optional | Yes | Software segment | - |
| 3 | UAC | Optional | No | User authentication credential | - |
| 4 | MSA | Required | No | Message acknowledgment | - |
| 5 | ERR | Optional | No | Error | - |
| 6 | QAK | Required | No | Query acknowledgment | - |
| 7 | QPD | Required | No | Query parameter definition | - |
| 8 | RCP | Required | No | Response control parameter | - |
| 9 | PID | Required | No | Patient identification | QUERY_RESPONSE |
| 10 | PD1 | Optional | No | Patient additional demographic | QUERY_RESPONSE |
| 11 | NTE | Optional | Yes | Notes and comments | QUERY_RESPONSE |
| 12 | AL1 | Required | Yes | Patient allergy information | ALLERGY |
| 13 | PV1 | Required | No | Patient visit | ALLERGY |
| 14 | PV2 | Optional | No | Patient visit - additional info | ALLERGY |
| 15 | ORC | Required | No | Common order | QUERY_RESPONSE |
| 16 | TQ1 | Required | No | Timing / quantity | TIMING |
| 17 | TQ2 | Optional | Yes | Timing / quantity relationship | TIMING |
| 18 | RXO | Required | No | Pharmacy / treatment order | ORDER_DETAIL |
| 19 | NTE | Optional | Yes | Notes and comments | ORDER_DETAIL |
| 20 | RXR | Required | Yes | Pharmacy / treatment route | ORDER_DETAIL |
| 21 | RXC | Required | Yes | Pharmacy / treatment component order | ORDER_DETAIL |
| 22 | NTE | Optional | Yes | Notes and comments | ORDER_DETAIL |
| 23 | RXE | Required | No | Pharmacy / treatment encoded order | ORDER_ENCODED |
| 24 | TQ1 | Required | No | Timing / quantity | ORDER_ENCODED |
| 25 | TQ2 | Optional | Yes | Timing / quantity relationship | ORDER_ENCODED |
| 26 | RXR | Required | Yes | Pharmacy / treatment route | ORDER_ENCODED |
| 27 | RXC | Optional | Yes | Pharmacy / treatment component order | ORDER_ENCODED |
| 28 | RXD | Required | No | Pharmacy / treatment dispense | QUERY_RESPONSE |
| 29 | RXR | Required | Yes | Pharmacy / treatment route | QUERY_RESPONSE |
| 30 | RXC | Optional | Yes | Pharmacy / treatment component order | QUERY_RESPONSE |
| 31 | OBX | Optional | No | Observation result | OBSERVATION |
| 32 | NTE | Optional | Yes | Notes and comments | OBSERVATION |
| 33 | DSC | Required | No | Continuation pointer | - |
Get started with Zato and connect your systems in minutes.