Acknowledges and responds to the corresponding order message with acceptance, modification, or rejection details. The MSA segment reports the status and ORC segments echo the original order control information. Fulfilling systems send this back to the ordering system.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'ORX^O58^ORX_O58|MSG001|P|2.9\r' \
'ORC|NW|ORD001||GRP001|||1^BID'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_numberHow to construct, send, receive, and extract fields from real-world ORX^O58 messages.
Demonstrates receiving and extracting key fields from a general order message with document payload acknowledgment transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'ORX^O58^ORX_O58|MSG001|P|2.9\r' \
'ORC|NW|ORD001||GRP001|||1^BID'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_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||ORX^O58^ORX_O58|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|'
msg = HL7Message.parse(raw)
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_numberBeyond the mandatory MSH header, the required segments are: MSA, PID, ORC, TXA. 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 ORX^O58 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | MSA | Required | No | Message acknowledgment | - |
| 3 | ARV | Optional | Yes | Access restriction | - |
| 4 | ERR | Optional | Yes | Error | - |
| 5 | SFT | Optional | Yes | Software segment | - |
| 6 | UAC | Optional | No | User authentication credential | - |
| 7 | NTE | Optional | Yes | Notes and comments | - |
| 8 | PID | Required | No | Patient identification | RESPONSE |
| 9 | NTE | Optional | Yes | Notes and comments | RESPONSE |
| 10 | PRT | Optional | Yes | Participation information | RESPONSE |
| 11 | ARV | Optional | Yes | Access restriction | RESPONSE |
| 12 | ORC | Required | No | Common order | RESPONSE |
| 13 | PRT | Optional | Yes | Participation information | RESPONSE |
| 14 | TXA | Required | No | Transcription document header | RESPONSE |
| 15 | CTI | Optional | Yes | Clinical trial identification | RESPONSE |
Get started with Zato and connect your systems in minutes.