Guarantor

GT1 identifies the person or organization financially responsible for a patient's account. It carries the guarantor's name, address, phone numbers, relationship to the patient, employer information, and demographic details. It appears in ADT, BAR, and DFT messages.

Create the segment, set its fields, then read them back:

from zato.hl7v2.v2_9 import GT1, XPN, CWE

gt1 = GT1()
gt1.guarantor_name = XPN(
    family_name='SMITH',
    given_name='JOHN'
)
gt1.guarantor_type = CWE(identifier='I')

name = gt1.guarantor_name
gtype = gt1.guarantor_type

The guarantor_relationship field uses the CWE datatype with HL7 table 0063 codes:

from zato.hl7v2.v2_9 import GT1, CWE

gt1 = GT1()
gt1.guarantor_relationship = CWE(identifier='SEL')

# Common codes:
# SEL = Self
# SPO = Spouse
# PAR = Parent
# GRD = Guardian

Create separate GT1 instances for each guarantor, each with its own set_id_gt1:

from zato.hl7v2.v2_9 import GT1, XPN, CWE

primary = GT1()
primary.set_id_gt1 = '1'
primary.guarantor_name = XPN(
    family_name='SMITH',
    given_name='JOHN'
)

secondary = GT1()
secondary.set_id_gt1 = '2'
secondary.guarantor_name = XPN(
    family_name='GARCIA',
    given_name='ELENA'
)

Use the employer fields to capture the guarantor's workplace information:

from zato.hl7v2.v2_9 import GT1
from zato.hl7v2.v2_9 import XPN, XAD, XTN

gt1 = GT1()
gt1.guarantor_employer_name = XPN(family_name='GREENVALLEY WELLNESS')
gt1.guarantor_employer_address = XAD(
    street_address='100 Wellness Blvd',
    city='Denver',
    state_or_province='CO',
    zip_or_postal_code='80202'
)
gt1.guarantor_employer_phone_number = XTN(
    telecommunication_use_code='WPN',
    telecommunication_equipment_type='PH',
    country_code='1',
    area_city_code='720',
    local_number='5558000'
)

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.