Response control parameter

RCP controls how a responding system delivers query results. It sets the execution priority, limits the number of returned records, chooses real-time vs. batch delivery, and optionally sets a deadline or modify flag for subscription queries.

The field uses HL7 table 0091. Common values are I (immediate), D (deferred), and S (stat/urgent):

from zato.hl7v2.v2_9 import RCP

rcp = RCP()

# I = Immediate
rcp.query_priority = 'I'

# D = Deferred
rcp.query_priority = 'D'

Use the quantity_limited_request field with the CQ datatype:

from zato.hl7v2.v2_9 import RCP, CQ

rcp = RCP()
rcp.quantity_limited_request = CQ(
    quantity='10',
    units='RD'
)

The field uses HL7 table 0394 with values like R (real-time), B (batch), and T (bolus/one-time dump):

from zato.hl7v2.v2_9 import RCP, CNE

rcp = RCP()
rcp.response_modality = CNE(
    identifier='R',
    text='Real time',
    name_of_coding_system='HL70394'
)

It uses HL7 table 0395 and indicates whether a subscription query is being modified (M) or created new (N). It only applies to subscription-based query patterns:

from zato.hl7v2.v2_9 import RCP

rcp = RCP()
rcp.query_priority = 'I'
rcp.modify_indicator = 'M'

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.