Request for information

RFI communicates a payer's request for additional information to support claim processing. It includes the request date, response deadline, patient consent status, and when the provider submitted the requested documentation.

Check whether the date_additional_information_was_submitted field is populated:

from zato.hl7v2.v2_9 import RFI

rfi = RFI()
rfi.request_date = '20240501'
rfi.response_due_date = '20240601'
rfi.date_additional_information_was_submitted = (
    '20240520'
)

The patient_consent field (HL7 table 0136) indicates whether the patient has consented to the release of additional clinical information:

from zato.hl7v2.v2_9 import RFI

rfi = RFI()
# Patient has consented
rfi.patient_consent = 'Y'

# Patient has not consented
rfi.patient_consent = 'N'

Assign a date string to response_due_date:

from zato.hl7v2.v2_9 import RFI

rfi = RFI()
rfi.request_date = '20240315'
rfi.response_due_date = '20240415'

Set the required request_date and response_due_date fields, plus optional consent:

from zato.hl7v2.v2_9 import RFI

rfi = RFI()
rfi.request_date = '20240315'
rfi.response_due_date = '20240415'
rfi.patient_consent = 'Y'

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.