Schedule a demo
Message type

Pharmacy / treatment give

Reports the giving (administration) of a pharmacy or treatment order. The ORC carries order control and RXG reports the administered medication and dose.

41segments
16required
6groups
v2.9HL7 version
rgv-o15.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RGV^O15^RGV_O15|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXG|1|1|54321^Metformin^NDC|500|mg'

# .. 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.rxg.give_code
dose = msg.rxg.give_amount_minimum

Build and parse RGV^O15 messages in Python

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

1

Parse an incoming RGV^O15 message

Demonstrates receiving and extracting key fields from a pharmacy / treatment give transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RGV^O15^RGV_O15|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXG|1|1|54321^Metformin^NDC|500|mg'

# .. 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.rxg.give_code
dose = msg.rxg.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||RGV^O15^RGV_O15|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, PV1, ORC, TQ1, RXO, NTE, RXR, RXC. 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.

RGV^O15 segment composition

Segments that make up the RGV^O15 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
7PRTOptionalYesParticipation informationPATIENT
8NTEOptionalYesNotes and commentsPATIENT
9AL1OptionalYesPatient allergy informationPATIENT
10ARVOptionalYesAccess restrictionPATIENT
11PV1RequiredNoPatient visitPATIENT
12PV2OptionalNoPatient visit - additional infoPATIENT
13PRTOptionalYesParticipation informationPATIENT
14ARVOptionalYesAccess restrictionPATIENT
15ORCRequiredNoCommon orderORDER
16PRTOptionalYesParticipation informationORDER
17TQ1RequiredNoTiming / quantityORDER
18TQ2OptionalYesTiming / quantity relationshipORDER
19RXORequiredNoPharmacy / treatment orderORDER
20PRTOptionalYesParticipation informationORDER
21NTERequiredYesNotes and commentsORDER_DETAIL_SUPPLEMENT
22RXRRequiredYesPharmacy / treatment routeORDER_DETAIL_SUPPLEMENT
23RXCRequiredNoPharmacy / treatment component orderORDER_DETAIL_SUPPLEMENT
24NTEOptionalYesNotes and commentsORDER_DETAIL_SUPPLEMENT
25RXERequiredNoPharmacy / treatment encoded orderORDER
26PRTOptionalYesParticipation informationORDER
27NTEOptionalYesNotes and commentsORDER
28TQ1RequiredNoTiming / quantityTIMING_ENCODED
29TQ2OptionalYesTiming / quantity relationshipTIMING_ENCODED
30RXRRequiredYesPharmacy / treatment routeORDER
31RXCOptionalYesPharmacy / treatment component orderORDER
32RXGRequiredNoPharmacy / treatment giveORDER
33PRTOptionalYesParticipation informationORDER
34TQ1RequiredNoTiming / quantityTIMING_GIVE
35TQ2OptionalYesTiming / quantity relationshipTIMING_GIVE
36RXRRequiredYesPharmacy / treatment routeORDER
37RXCOptionalYesPharmacy / treatment component orderORDER
38CDOOptionalYesClinical study data objectORDER
39OBXRequiredNoObservation resultOBSERVATION
40PRTOptionalYesParticipation informationOBSERVATION
41NTEOptionalYesNotes and commentsOBSERVATION

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python