Billing

BLG tells downstream billing systems when to post charges, which charge category applies, which financial account to use, and the business reason for that choice. It is usually paired with order or observation segments in the same message.

Field when_to_charge uses the CCD datatype with HL70100 (when to charge). Populate both components for a clear code and display text:

from zato.hl7v2.v2_9 import BLG, CCD

blg = BLG()
blg.when_to_charge = CCD(
    ccd_1='O', ccd_2='Order complete')

Use account_id with the CX datatype so identifiers stay structured:

from zato.hl7v2.v2_9 import BLG, CX

blg = BLG()
blg.account_id = CX(
    id_number='ACCT2024', assigning_authority='WELL')

charge_type_reason is a CWE referencing HL70475. It explains why the charge type was selected—for example a bundled wellness program or preventive package.

BLG provides billing control on an order or observation, while FT1 records detailed financial transaction lines. A message may carry BLG near ORC/OBR and FT1 rows that expand posted amounts for the same encounter.

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.