Uniform billing data

UB2 carries uniform billing data for institutional claims - co-insurance days, covered and non-covered days, condition codes, value amounts, billing locator fields, and document control numbers. It appears in financial messages to provide the claim-level detail needed for payer adjudication.

Create the segment and access its fields directly:

from zato.hl7v2.v2_9 import UB2

ub2 = UB2()
ub2.covered_days_7 = '3'
ub2.document_control_number = 'DOC001'
ub2.special_visit_count = '2'

covered = ub2.covered_days_7
doc_num = ub2.document_control_number
visit_count = ub2.special_visit_count

The condition_code_24_30 field uses the CWE datatype with HL7 table 0043:

from zato.hl7v2.v2_9 import UB2, CWE

ub2 = UB2()
ub2.condition_code_24_30 = CWE(
    identifier='30',
    text='Annual checkup'
)

UB2 contains several uniform billing locator fields (positions 9-11, 13-16) that carry state and national-level billing identifiers. These are free-text ST fields whose content is defined by the billing jurisdiction. They map to specific form locators on the UB-04 institutional claim form.

Set the covered_days_7 and non_covered_days_8 fields directly as string values:

from zato.hl7v2.v2_9 import UB2

ub2 = UB2()
ub2.set_id_ub2 = '1'
ub2.covered_days_7 = '5'
ub2.non_covered_days_8 = '0'

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.