Segment

Equipment / log service

Records an event or log entry from a laboratory instrument or automated device, carrying the event type code, an optional log file name, start and end timestamps, and free-text transaction data describing what occurred. It is used in equipment-notification and automation messages to maintain an audit trail of device activity such as power cycles, calibrations, errors, and maintenance actions.

5fields

3required

v2.9HL7 version

from zato.hl7v2 import EQP

eqp = EQP()
eqp.event_type = 'LOG'
eqp.start_date_time = '20260515'
eqp.transaction_data = 'Started'

Python examples

Build EQP segments in Python

How to construct and work with real-world EQP segments.

Calibration log

Recording a completed calibration event with start and end times

from zato.hl7v2.v2_9 import EQP
from zato.hl7v2.v2_9 import CWE

eqp = EQP()
eqp.event_type = CWE(
    identifier='CAL',
    text='Calibration',
    name_of_coding_system=
        'HL70450'
)
eqp.file_name = 'cal_20240515.log'
eqp.start_date_time = '20240515080000'
eqp.end_date_time = '20240515081500'
eqp.transaction_data = 'Calibration completed OK'

Power cycle event

Logging a power-on event for an analyzer with transaction details

from zato.hl7v2.v2_9 import EQP
from zato.hl7v2.v2_9 import CWE

eqp = EQP()
eqp.event_type = CWE(
    identifier='PWR',
    text='Power up',
    name_of_coding_system=
        'HL70450'
)
eqp.start_date_time = '20240516060000'
eqp.transaction_data = 'System powered on normally'

Error log entry

Recording an equipment error event with a log file reference

from zato.hl7v2.v2_9 import EQP
from zato.hl7v2.v2_9 import CWE

eqp = EQP()
eqp.event_type = CWE(
    identifier='ERR',
    text='Error',
    name_of_coding_system=
        'HL70450'
)
eqp.file_name = 'err_20240517.log'
eqp.start_date_time = '20240517143000'
eqp.end_date_time = '20240517143005'
eqp.transaction_data = 'Sensor fault detected'

Tutorials

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

Frequently asked questions

EQP records equipment log entries including calibrations, power cycles, errors, and maintenance actions. Each entry has an event type, optional file reference, timestamps, and descriptive transaction data to maintain an audit trail.

The event_type field uses CWE with HL7 table 0450:

from zato.hl7v2.v2_9 import EQP, CWE

eqp = EQP()
eqp.event_type = CWE(
    identifier='CAL',
    text='Calibration',
    name_of_coding_system=
        'HL70450'
)

HL7 table 0450 defines equipment event types:

from zato.hl7v2.v2_9 import EQP, CWE

eqp = EQP()

# CAL = Calibration
eqp.event_type = CWE(identifier='CAL')

# PWR = Power up
eqp.event_type = CWE(identifier='PWR')

# ERR = Error
eqp.event_type = CWE(identifier='ERR')

Use start_date_time and end_date_time in DTM format:

from zato.hl7v2.v2_9 import EQP

eqp = EQP()
eqp.event_type = 'CAL'
eqp.start_date_time = '20240515080000'
eqp.end_date_time = '20240515081500'
eqp.transaction_data = 'Calibration completed OK'

Access the fields directly after creating the segment:

from zato.hl7v2.v2_9 import EQP

eqp = EQP()
eqp.event_type = 'CAL'
eqp.start_date_time = '20240515080000'
eqp.transaction_data = 'OK'

evt = eqp.event_type
start = eqp.start_date_time
data = eqp.transaction_data

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.

Reference

EQP field reference

Complete list of fields in the EQP segment, HL7 v2.9.

#	Python name	Datatype	Usage	Repeatable	Table
1	▶`event_type`	`CWE`	Required	No	`HL70450`
1.1	├`.identifier`	`ST`	Optional	No	-
1.2	├`.text`	`ST`	Optional	No	-
1.3	├`.name_of_coding_system`	`ID`	Optional	No	-
1.4	├`.alternate_identifier`	`ST`	Optional	No	-
1.5	├`.alternate_text`	`ST`	Optional	No	-
1.6	├`.name_of_alternate_coding_system`	`ID`	Optional	No	-
1.7	├`.coding_system_version_id`	`ST`	Optional	No	-
1.8	├`.alternate_coding_system_version_id`	`ST`	Optional	No	-
1.9	├`.original_text`	`ST`	Optional	No	-
1.10	├`.second_alternate_identifier`	`ST`	Optional	No	-
1.11	├`.second_alternate_text`	`ST`	Optional	No	-
1.12	├`.name_of_second_alternate_coding_system`	`ID`	Optional	No	-
1.13	├`.second_alternate_coding_system_version_id`	`ST`	Optional	No	-
1.14	├`.coding_system_oid`	`ST`	Optional	No	-
1.15	├`.value_set_oid`	`ST`	Optional	No	-
1.16	├`.value_set_version_id`	`DTM`	Optional	No	-
1.17	├`.alternate_coding_system_oid`	`ST`	Optional	No	-
1.18	├`.alternate_value_set_oid`	`ST`	Optional	No	-
1.19	├`.alternate_value_set_version_id`	`DTM`	Optional	No	-
1.20	├`.second_alternate_coding_system_oid`	`ST`	Optional	No	-
1.21	├`.second_alternate_value_set_oid`	`ST`	Optional	No	-
1.22	└`.second_alternate_value_set_version_id`	`DTM`	Optional	No	-
2	`file_name`	`ST`	Optional	No	-
3	`start_date_time`	`DTM`	Required	No	-
4	`end_date_time`	`DTM`	Optional	No	-
5	`transaction_data`	`FT`	Required	No	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python