Material lot

ILT contains material lot information including lot numbers, expiration dates, and quantities for materials management.

Use inventory_lot_number field:

from zato.hl7v2.v2_9 import ILT

ilt = ILT()
ilt.inventory_lot_number = 'LOT20240115001'

Use inventory_expiration_date field with DTM datatype:

from zato.hl7v2.v2_9 import ILT
from zato.hl7v2.v2_9 import DTM

ilt = ILT()
ilt.inventory_expiration_date = DTM('20251231')

ILT contains lot-specific information while ITM contains item master data. Multiple ILT segments can reference the same ITM.

Use inventory_on_hand_date, inventory_on_hand_quantity, and inventory_on_hand_quantity_unit to capture current stock for nutrition, fitness, and self-care supplies between receipts.

from zato.hl7v2.v2_9 import ILT
from zato.hl7v2.v2_9 import DTM, CWE

ilt = ILT()
ilt.inventory_on_hand_date = DTM('20250405120000')
ilt.inventory_on_hand_quantity = '120'
ilt.inventory_on_hand_quantity_unit = CWE(
    identifier='EA',
    text='Each',
    name_of_coding_system='UCUM'
)

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.