Sterilization lot

SLT identifies sterilization lots by linking device numbers and names to lot numbers, item identifiers, and bar codes. It enables traceability of sterilized instruments and supplies across processing cycles for recall management and regulatory compliance.

Create an SLT instance and set the device and lot information:

from zato.hl7v2.v2_9 import SLT, EI

slt = SLT()
slt.device_number = EI(
    entity_identifier='DEV-100',
    universal_id_type='CSSD'
)
slt.device_name = 'Autoclave-7'

The lot_number field uses the EI (entity identifier) datatype to uniquely identify the sterilization lot:

from zato.hl7v2.v2_9 import SLT, EI

slt = SLT()
slt.lot_number = EI(
    entity_identifier='LOT-2024-055',
    universal_id_type='CSSD'
)

Use the item_identifier field to assign a unique EI value to each instrument within a sterilization lot:

from zato.hl7v2.v2_9 import SLT, EI

slt = SLT()
slt.lot_number = EI(
    entity_identifier='LOT-2024-055',
    universal_id_type='CSSD'
)
slt.item_identifier = EI(
    entity_identifier='ITEM-8847',
    universal_id_type='CSSD'
)

The bar_code field is a simple string value representing the scannable identifier for the sterilization lot:

from zato.hl7v2.v2_9 import SLT

slt = SLT()
slt.bar_code = 'BC-20240601-001'

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.