Employment status

OH1 carries a patient's employment status as part of occupational data. It records the status code, effective date range, entry date, and a unique identifier. It appears in ADT and occupational health messages to support exposure tracking and public health reporting.

The employment_status field uses CWE with HL7 table 0957:

from zato.hl7v2.v2_9 import OH1, CWE

oh1 = OH1()
oh1.employment_status = CWE(
    identifier='FT',
    text='Full time',
    name_of_coding_system='HL70957'
)

Use the start and end date fields for the employment period:

from zato.hl7v2.v2_9 import OH1

oh1 = OH1()
oh1.employment_status_start_date = (
    '20230101'
)
oh1.employment_status_end_date = (
    '20240101'
)

The employment_status_unique_identifier field uses the EI datatype:

from zato.hl7v2.v2_9 import OH1, EI

oh1 = OH1()
oh1.employment_status_unique_identifier = EI(
    entity_identifier='OH1-2024-001',
    namespace_id='MAIN'
)

The action_code field accepts standard HL7 action codes for record management:

from zato.hl7v2.v2_9 import OH1

oh1 = OH1()
oh1.set_id = '1'
oh1.action_code = 'AD'

oh1_upd = OH1()
oh1_upd.set_id = '2'
oh1_upd.action_code = 'UP'

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.