Schedule a demo
Message type

Pharmacy / treatment order

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.

34segments
11required
2groups
v2.9HL7 version
omp-o09.py
# 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_minimum

Build and parse OMP^O09 messages in Python

How to construct, send, receive, and extract fields from real-world OMP^O09 messages.

1

Parse an incoming OMP^O09 message

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_minimum

Learn by building

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

Frequently asked questions

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_number

Beyond 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.

OMP^O09 segment composition

Segments that make up the OMP^O09 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5NTEOptionalYesNotes and comments-
6PIDRequiredNoPatient identificationPATIENT
7PD1RequiredNoPatient additional demographicPATIENT
8PRTOptionalYesParticipation informationPATIENT
9NTEOptionalYesNotes and commentsPATIENT
10ARVOptionalYesAccess restrictionPATIENT
11PV1RequiredNoPatient visitPATIENT
12PV2OptionalNoPatient visit - additional infoPATIENT
13PRTOptionalYesParticipation informationPATIENT
14ARVOptionalYesAccess restrictionPATIENT
15IN1RequiredNoInsurancePATIENT
16IN2OptionalNoInsurance additional infoPATIENT
17IN3OptionalNoInsurance additional info - certificationPATIENT
18GT1OptionalNoGuarantorPATIENT
19AL1OptionalYesPatient allergy informationPATIENT
20ORCRequiredNoCommon orderORDER
21TQ1RequiredNoTiming / quantityORDER
22TQ2OptionalYesTiming / quantity relationshipORDER
23RXORequiredNoPharmacy / treatment orderORDER
24PRTOptionalYesParticipation informationORDER
25NTEOptionalYesNotes and commentsORDER
26RXRRequiredYesPharmacy / treatment routeORDER
27RXCRequiredNoPharmacy / treatment component orderORDER
28NTEOptionalYesNotes and commentsORDER
29CDOOptionalYesClinical study data objectORDER
30OBXRequiredNoObservation resultORDER
31PRTOptionalYesParticipation informationORDER
32NTEOptionalYesNotes and commentsORDER
33FT1OptionalYesFinancial transactionORDER
34BLGOptionalNoBillingORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python