Pharmacy/treatment route

RXR records route of administration and related details such as site, device, method, and instructions for pharmacy and nutrition workflows. It complements ORC, RXO, RXE, RXD, RXG, and PID when systems document how a wellness product is given.

Field 1 (route) is required. Populate administration_site, administration_device, administration_method, routing_instruction, and administration_site_modifier when your interface specification uses them.

from zato.hl7v2.v2_9 import RXR, CWE

rxr = RXR()
rxr.route = CWE(
    identifier='PO', text='Oral')

Use administration_site when the route depends on a specific body location, for example transdermal application on the forearm or intravenous access at the antecubital fossa. Oral routes often leave this field empty.

administration_method describes the technique (for example drip versus push), while routing_instruction can carry partner-specific directions. Follow your trading partner guide for which field holds each kind of note.

RXE encodes structured order lines; RXD documents a dispense; RXR states how the product is administered. The same order may include one RXR or several when routes differ.

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.