Material item

ITM contains material item information including item identifiers, descriptions, types, and status for materials management.

Common item types from HL70778 include SUP (Supply), MED (Medication), and EQP (Equipment).

Use item_identifier field with EI datatype:

from zato.hl7v2.v2_9 import ITM
from zato.hl7v2.v2_9 import EI

itm = ITM()
itm.item_identifier = EI(entity_identifier='ITEM001')

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

Contract_date windows and manufacturer_contact_information make it easier to align fresh ingredients, supplements, and fitness accessories with reliable vendor touchpoints for proactive, healthy-lifestyle programs.

from zato.hl7v2.v2_9 import ITM
from zato.hl7v2.v2_9 import DR, XPN, XTN

itm = ITM()
itm.contract_date = DR(
    dr_1='20240101',
    dr_2='20251231'
)
itm.manufacturer_contact_name = XPN(
    family_name='Harvest',
    given_name='Wellness'
)
itm.manufacturer_contact_information = XTN(
    telecommunication_use_code='WPN',
    telecommunication_equipment_type='PH',
    country_code='1',
    area_city_code='503',
    local_number='5550199'
)

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.