HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

TQ1 segment

The TQ1 segment is used to specify the complex timing of events and actions such as those that occur in order management and scheduling systems. This segment determines the quantity, frequency, priority, and timing of a service. By allowing the segment to repeat, it is possible to have service requests that vary the quantity, frequency and priority of a service request over time. Use cases showing when TQ1 may need to repeat: d) Cardiac enzymes STAT and then q 4 hours

The shape of one line

segmentTQ1|TQ1-1Set ID - TQ1|TQ1-2Quantity|TQ1-3Repeat Pattern|TQ1-4Explicit Time|TQ1-5Relative Time and Units|TQ1-6Service Duration|TQ1-7Start date/time|TQ1-8End date/time|TQ1-9Priority|TQ1-10Condition text| …4 more

optional

Count the pipes to find a field, and count the empty ones too: an empty field still holds its place. Leave out the separator before TQ1-3 and its value arrives as TQ1-2, so the receiver stores Repeat Pattern as Quantity.

This page carries the TQ1 field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for TQ1.

Every field

SEQLENDTOPTRP/#TBL#ITEM#Element nameCardinality
TQ1-14SIO01627Set ID - TQ10..1
20CQO01628Quantity0..1

TQ1-2 is a CQ, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
CQ.116NMOQuantity
CQ.2483CEOUnits
540RPTOY033501629Repeat Pattern0..*

TQ1-3 is a RPT, which holds 11 components separated by carets.

SEQLENDTOPTTBL#Component name
RPT.1705CWER0335Repeat Pattern Code
RPT.22IDO0527Calendar Alignment
RPT.310NMOPhase Range Begin Value
RPT.410NMOPhase Range End Value
RPT.510NMOPeriod Quantity
RPT.610ISCPeriod Units
RPT.71IDO0136Institution Specified Time
RPT.86IDO0528Event
RPT.910NMOEvent Offset Quantity
RPT.1010ISCEvent Offset Units
RPT.11200GTSOGeneral Timing Specification
TQ1-420TMOY01630Explicit Time0..*
20CQOY01631Relative Time and Units0..*

TQ1-5 is a CQ, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
CQ.116NMOQuantity
CQ.2483CEOUnits
20CQO01632Service Duration0..1

TQ1-6 is a CQ, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
CQ.116NMOQuantity
CQ.2483CEOUnits
26TSO01633Start date/time0..1

TQ1-7 is a TS, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
TS.124DTMRTime
TS.21IDB0529Degree of Precision
26TSO01634End date/time0..1

TQ1-8 is a TS, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
TS.124DTMRTime
TS.21IDB0529Degree of Precision
250CWEOY048501635Priority0..*

TQ1-9 is a CWE, which holds 9 components separated by carets.

SEQLENDTOPTTBL#Component name
CWE.120STOIdentifier
CWE.2199STOText
CWE.320IDO0396Name of Coding System
CWE.420STOAlternate Identifier
CWE.5199STOAlternate Text
CWE.620IDO0396Name of Alternate Coding System
CWE.710STCCoding System Version ID
CWE.810STOAlternate Coding System Version ID
CWE.9199STOOriginal Text
TQ1-10250TXO01636Condition text0..1
TQ1-11250TXO01637Text instruction0..1
TQ1-1210IDC042701638Conjunction0..1
20CQO01639Occurrence duration0..1

TQ1-13 is a CQ, which holds 2 components separated by carets.

SEQLENDTOPTTBL#Component name
CQ.116NMOQuantity
CQ.2483CEOUnits
TQ1-1410NMO01640Total occurrence's0..1

Message types carrying TQ1

TQ1 appears in 57 message structures, belonging to 43 message types.