Payee information

PYE identifies who receives payment for a healthcare claim. It specifies the payee type (provider, subscriber, or other), optionally the payee's relationship to the patient, and includes the payee's name, address, and preferred payment method.

The payee_type field uses the CWE datatype with HL7 table 0557:

from zato.hl7v2.v2_9 import PYE, CWE

pye = PYE()
pye.payee_type = CWE(
    identifier='PROV',
    text='Provider',
    name_of_coding_system='HL70557'
)

The payee_address field uses the XAD datatype:

from zato.hl7v2.v2_9 import PYE, XAD

pye = PYE()
pye.payee_address = XAD(
    street_address='100 Main St',
    city='Springfield',
    state='IL',
    zip_code='62701'
)

The payee_person_name field uses the XPN datatype:

from zato.hl7v2.v2_9 import PYE, XPN

pye = PYE()
pye.payee_person_name = XPN(
    family_name='DOE',
    given_name='JOHN'
)

The payee_identification_list field uses the XON datatype:

from zato.hl7v2.v2_9 import PYE, XON

pye = PYE()
pye.payee_identification_list = XON(organization_name='City Hospital')

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.