Submits a pharmacy or treatment order with encoded medication details. The ORC segment carries order control and RXO defines the prescribed medication. Pharmacy systems consume this to dispense and verify drug orders.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'OMP^O09^OMP_O09|MSG001|P|2.9\r' \
'ORC|NW|ORD001||GRP001|||1^BID\r' \
'RXO|54321^Metformin^NDC|500||mg|TAB'
# .. 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_number
drug = msg.rxo.requested_give_code
dose = msg.rxo.requested_give_amount_minimumHow to construct, send, receive, and extract fields from real-world OMP^O09 messages.
Demonstrates receiving and extracting key fields from a pharmacy / treatment order transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'OMP^O09^OMP_O09|MSG001|P|2.9\r' \
'ORC|NW|ORD001||GRP001|||1^BID\r' \
'RXO|54321^Metformin^NDC|500||mg|TAB'
# .. 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_number
drug = msg.rxo.requested_give_code
dose = msg.rxo.requested_give_amount_minimumStep-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||OMP^O09^OMP_O09|MSG00001|P|2.9'
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: PID, PD1, PV1, IN1, ORC, TQ1, RXO, RXR. 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 OMP^O09 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | ARV | Optional | Yes | Access restriction | - |
| 3 | SFT | Optional | Yes | Software segment | - |
| 4 | UAC | Optional | No | User authentication credential | - |
| 5 | NTE | Optional | Yes | Notes and comments | - |
| 6 | PID | Required | No | Patient identification | PATIENT |
| 7 | PD1 | Required | No | Patient additional demographic | PATIENT |
| 8 | PRT | Optional | Yes | Participation information | PATIENT |
| 9 | NTE | Optional | Yes | Notes and comments | PATIENT |
| 10 | ARV | Optional | Yes | Access restriction | PATIENT |
| 11 | PV1 | Required | No | Patient visit | PATIENT |
| 12 | PV2 | Optional | No | Patient visit - additional info | PATIENT |
| 13 | PRT | Optional | Yes | Participation information | PATIENT |
| 14 | ARV | Optional | Yes | Access restriction | PATIENT |
| 15 | IN1 | Required | No | Insurance | PATIENT |
| 16 | IN2 | Optional | No | Insurance additional info | PATIENT |
| 17 | IN3 | Optional | No | Insurance additional info - certification | PATIENT |
| 18 | GT1 | Optional | No | Guarantor | PATIENT |
| 19 | AL1 | Optional | Yes | Patient allergy information | PATIENT |
| 20 | ORC | Required | No | Common order | ORDER |
| 21 | TQ1 | Required | No | Timing / quantity | ORDER |
| 22 | TQ2 | Optional | Yes | Timing / quantity relationship | ORDER |
| 23 | RXO | Required | No | Pharmacy / treatment order | ORDER |
| 24 | PRT | Optional | Yes | Participation information | ORDER |
| 25 | NTE | Optional | Yes | Notes and comments | ORDER |
| 26 | RXR | Required | Yes | Pharmacy / treatment route | ORDER |
| 27 | RXC | Required | No | Pharmacy / treatment component order | ORDER |
| 28 | NTE | Optional | Yes | Notes and comments | ORDER |
| 29 | CDO | Optional | Yes | Clinical study data object | ORDER |
| 30 | OBX | Required | No | Observation result | ORDER |
| 31 | PRT | Optional | Yes | Participation information | ORDER |
| 32 | NTE | Optional | Yes | Notes and comments | ORDER |
| 33 | FT1 | Optional | Yes | Financial transaction | ORDER |
| 34 | BLG | Optional | No | Billing | ORDER |
Get started with Zato and connect your systems in minutes.