Sterilization parameter

STZ defines the sterilization and maintenance parameters for equipment processing. It specifies the sterilization type, cycle, and maintenance schedule, supporting quality assurance documentation and regulatory compliance for instrument reprocessing.

The sterilization_type field uses the CWE datatype with HL7 table 0806. Common values include STE (Steam), EOG (Ethylene oxide), and PLA (Plasma):

from zato.hl7v2.v2_9 import STZ, CWE

stz = STZ()
stz.sterilization_type = CWE(
    identifier='STE',
    text='Steam',
    name_of_coding_system='HL70806'
)

The sterilization_cycle field uses HL7 table 0702 to indicate the processing cycle:

from zato.hl7v2.v2_9 import STZ, CWE

stz = STZ()
stz.sterilization_cycle = CWE(
    identifier='A',
    text='Express',
    name_of_coding_system='HL70702'
)

Use maintenance_cycle (table 0809) and maintenance_type (table 0811) to define the equipment maintenance schedule:

from zato.hl7v2.v2_9 import STZ, CWE

stz = STZ()
stz.maintenance_cycle = CWE(
    identifier='PM',
    text='Preventive',
    name_of_coding_system='HL70809'
)
stz.maintenance_type = CWE(
    identifier='ANL',
    text='Annual',
    name_of_coding_system='HL70811'
)

STZ defines the sterilization parameters (type, cycle, maintenance), while SLT tracks the lot-level details (device, lot number, bar code). They typically appear together in sterilization messages to provide complete processing documentation.

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.