Timing/quantity relationship

TQ2 links timing and quantity segments (TQ1) to related placer, filler, and group identifiers and describes sequencing, cyclic behavior, and relationships between service requests. It supports structured wellness, fitness, and nutrition programs where multiple orders must run in a defined order or cadence.

Create a TQ2 segment and read its attributes directly:

from zato.hl7v2.v2_9 import TQ2, EI

tq2 = TQ2()
tq2.set_id_tq2 = '1'
tq2.related_placer_number = [
    EI(entity_identifier='ORD100', universal_id_type='WELL')]

placers = tq2.related_placer_number

Fields 3 and 4 use EI (entity identifier). They may repeat; assign a list of EI values in Python:

from zato.hl7v2.v2_9 import TQ2, EI

tq2 = TQ2()
tq2.related_placer_number = [
    EI(entity_identifier='ORD100', universal_id_type='WELL')]
tq2.related_filler_number = [
    EI(entity_identifier='LAB50', universal_id_type='GV')]

TQ1 describes when and how often something happens; TQ2 describes how separate TQ1 blocks or related orders connect (sequence flags, cyclic entry and exit, intervals, and relationship codes). Messages often carry TQ1 rows for each timing block and TQ2 rows to express dependencies between them.

Field 8 is a composite quantity with units, typically using CWE for coded units:

from zato.hl7v2.v2_9 import TQ2, CQ, CWE

tq2 = TQ2()
tq2.sequence_condition_time_interval = CQ(
    quantity='30', units=CWE(identifier='D'))

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.