DRG Master File Information

DMI carries Diagnosis Related Group reference data in master file messages. It provides the DRG code, major diagnostic category, length-of-stay trim points, average stay, and relative weight used by billing and case-management systems for reimbursement calculations.

The diagnostic_related_group field uses the CNE datatype with HL7 table 0055:

from zato.hl7v2.v2_9 import DMI, CNE

dmi = DMI()
dmi.diagnostic_related_group = CNE(
    identifier='470',
    text='Major joint replacement',
    name_of_coding_system='HL70055'
)

The lower_and_upper_trim_points field uses the NR (numeric range) datatype with low and high values:

from zato.hl7v2.v2_9 import DMI, NR

dmi = DMI()
dmi.lower_and_upper_trim_points = NR(
    low_value='2',
    high_value='10'
)

Use a CNE value referencing HL7 table 0118 for the MDC classification:

from zato.hl7v2.v2_9 import DMI, CNE

dmi = DMI()
dmi.major_diagnostic_category = CNE(
    identifier='8',
    text='Musculoskeletal',
    name_of_coding_system='HL70118'
)

Both fields are simple numeric values representing days and the CMS relative weight:

from zato.hl7v2.v2_9 import DMI

dmi = DMI()
dmi.average_length_of_stay = '4.5'
dmi.relative_weight = '1.9406'

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.