Inventory item master

IIM carries master-level inventory item data including item codes, lot numbers, expiration dates, manufacturer details, received and on-hand quantities, and associated costs. It is used to synchronize stock records between supply-chain, pharmacy, and materials-management systems.

The service_item_code field uses the CWE datatype to identify the catalogued item:

from zato.hl7v2.v2_9 import IIM, CWE

iim = IIM()
iim.service_item_code = CWE(
    identifier='IV-SET-001',
    text='IV Set Standard',
    name_of_coding_system=
        'SUPPLIERCAT'
)

Set the quantity, its unit via CWE, and the cost via MO:

from zato.hl7v2.v2_9 import IIM
from zato.hl7v2.v2_9 import CWE, MO

iim = IIM()
iim.inventory_received_quantity = '50'
iim.inventory_received_quantity_unit = CWE(
    identifier='EA',
    text='Each',
    name_of_coding_system='UCUM'
)
iim.inventory_received_item_cost = MO(
    quantity='15.00',
    denomination='USD'
)

Use the on-hand date, quantity, and quantity unit fields together:

from zato.hl7v2.v2_9 import IIM, CWE

iim = IIM()
iim.inventory_on_hand_date = '20240601'
iim.inventory_on_hand_quantity = '120'
iim.inventory_on_hand_quantity_unit = CWE(
    identifier='BX',
    text='Box',
    name_of_coding_system='UCUM'
)

The procedure_code field uses CNE with HL7 table 0088:

from zato.hl7v2.v2_9 import IIM, CNE

iim = IIM()
iim.procedure_code = CNE(
    identifier='99213',
    text='Office visit',
    name_of_coding_system='CPT'
)

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.