Requisition detail-1

RQ1 supplements the RQD segment with purchasing details such as anticipated price, manufacturer and vendor identifiers, catalog numbers, taxability, and whether substitutes are acceptable. It helps procurement systems source and price requisitioned items.

The manufacturer_identifier field uses the CWE datatype with HL7 table 0385:

from zato.hl7v2.v2_9 import RQ1, CWE

rq1 = RQ1()
rq1.manufacturer_identifier = CWE(
    identifier='MFG-100',
    text='Acme Medical',
    name_of_coding_system='HL70385'
)

The vendor_id field uses the CWE datatype with HL7 table 0683:

from zato.hl7v2.v2_9 import RQ1, CWE

rq1 = RQ1()
rq1.vendor_id = CWE(
    identifier='VND-200',
    text='Global Supply',
    name_of_coding_system='HL70683'
)

Both fields use HL7 table 0136 (Yes/No indicator). Set them as simple string values:

from zato.hl7v2.v2_9 import RQ1

rq1 = RQ1()
rq1.taxable = 'Y'
rq1.substitute_allowed = 'N'

The anticipated_price, manufacturers_catalog, and vendor_catalog fields are all simple string values:

from zato.hl7v2.v2_9 import RQ1

rq1 = RQ1()
rq1.anticipated_price = '29.95'
rq1.manufacturers_catalog = 'CAT-2024A'
rq1.vendor_catalog = 'VND-CAT-99'

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.