Diagnosis

DG1 carries diagnosis information for a patient encounter - the diagnosis code, type (admitting, working, final), priority, diagnosing clinician, classification, and attestation date. It appears in ADT, DFT, and BAR messages to support billing, clinical documentation, and care coordination.

Create the segment and access its fields directly:

from zato.hl7v2.v2_9 import DG1, CWE

dg1 = DG1()
dg1.diagnosis_code_dg1 = CWE(
    identifier='Z00.00',
    text='General exam',
    name_of_coding_system='I10'
)
dg1.diagnosis_type = CWE(identifier='A')
dg1.diagnosis_priority = '1'

code = dg1.diagnosis_code_dg1
dx_type = dg1.diagnosis_type
priority = dg1.diagnosis_priority

A message can contain multiple DG1 segments, each with a different set_id_dg1. Create multiple segments to represent them:

from zato.hl7v2.v2_9 import DG1, CWE

dg1_primary = DG1()
dg1_primary.set_id_dg1 = '1'
dg1_primary.diagnosis_code_dg1 = CWE(
    identifier='Z00.00',
    text='General exam',
    name_of_coding_system='I10'
)

dg1_secondary = DG1()
dg1_secondary.set_id_dg1 = '2'
dg1_secondary.diagnosis_code_dg1 = CWE(
    identifier='Z23',
    text='Immunization encounter',
    name_of_coding_system='I10'
)

The diagnosis_type field uses HL7 table 0052. Common values include:

from zato.hl7v2.v2_9 import DG1, CWE

dg1 = DG1()

# A = Admitting
dg1.diagnosis_type = CWE(identifier='A')

# W = Working
dg1.diagnosis_type = CWE(identifier='W')

# F = Final
dg1.diagnosis_type = CWE(identifier='F')

The diagnosing_clinician field uses the XCN (extended composite name) datatype:

from zato.hl7v2.v2_9 import DG1, XCN

dg1 = DG1()
dg1.diagnosing_clinician = XCN(
    person_identifier='12345',
    family_name='Smith',
    given_name='John',
    suffix='MD'
)

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.