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:
Cardiac enzymes STAT and then q 4 hours.
Streptokinase studies, draw 1st Stat and run Stat, then draw q 4 hours and run Stat.
Gentamicin 100mg Now and 80mg q12h second dose (First 80mg dose) given exactly 12 hours after the 100mg dose. (Might be 2 service requests.)
Activase 15mg bolus Stat then 50mg over 30 minutes, then 35mg over the next 60 minutes. (Might be 2 service requests.)
Imodium 4mg (2 caps) po initially, then 2mg (1cap) after each unformed stool to a maximum of 16 mg per day. (Might be 2 service requests.)
Zithromax 500mg (2tabs) po on the first day then 250mg (1tab) po qd for 5 days. (Might be 2 service requests.)
Zyban (Bupropion) Start 150mg po qam x 3 days, then increase to 150mg po bid for 7 to 12 weeks.
Colchicine 1mg (2 tabs) po now then 1 tablet q1 to 2 hours until pain relief or undesirable side effects (Diarrhea, GI upset). (Might be 2 service requests.)
doxycylcine 100mg po bid on the first day then 100mg po qd.
scopolamine, xxx mg, 1 hour before surgery. Relative time = -1^hour, priority = P (preop), or alternately repeat pattern = P1H^Preop, 1 Hour before Surgery^99LocalCode, Relative time would be empty and priority would be P (preop).
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
TQ1
|
|||||||||
1
|
Set ID - TQ1 | SI | O | [0..1] | 01627 | [1..4] | |||
|
2
|
Quantity | CQ | O | [0..1] | 01628 | ||||
|
3
|
Repeat Pattern | RPT | O | [0..*] | 01629 | ||||
|
4
|
Explicit Time | TM | O | [0..*] | 01630 | ||||
|
5
|
Relative Time and Units | CQ | O | [0..*] | 01631 | ||||
|
6
|
Service Duration | CQ | O | [0..1] | 01632 | ||||
|
7
|
Start date/time | DTM | O | [0..1] | 01633 | ||||
|
8
|
End date/time | DTM | O | [0..1] | 01634 | ||||
|
9
|
Priority | CWE | O | [0..*] | 01635 | ||||
|
10
|
Condition text | TX | O | [0..1] | 01636 | 250 | # | ||
|
11
|
Text instruction | TX | O | [0..1] | 01637 | 250 | # | ||
|
12
|
Conjunction | ID | C | [0..1] | 01638 | [1..1] | |||
|
13
|
Occurrence duration | CQ | O | [0..1] | 01639 | ||||
14
|
Total occurrences | NM | O | [0..1] | 01640 | 10 | # | ||
Definition: For the first timing specification transmitted, the sequence number shall be 1; for the second timing specification, it shall be 2; and so on.
Definition: This field specifies the numeric quantity of the service that should be provided at each service interval. For example, if two blood cultures are to be obtained every 4 hours, the quantity would be '2', or if three units of blood are to be typed and cross-matched, the quantity would be '3'. The default value for this field is '1'.
If multiple identical services are to be requested, it is strongly recommended that multiple service requests be placed, giving each service request its own unique placer/filler number.
Definition: The repeating frequency with which the treatment is to be administered. It is similar to the frequency and SIG code tables used in order entry systems.
This field may be repeated to build up more complex repeat patterns. For example, daily at bedtime can be represent as "|QD~HS|".
When the quantity timing specification must change to a different repeat pattern after some period of time, a new TQ1 segment must be used to show the new repeat pattern. Note that the end date of the current TQ1 will show when the current timing specification ends, and the start date of the next TQ1 shows when the new timing specification begins. The Conjunction field, TQ1-12 determines if the next TQ1 segment is to be performed sequentially or in parallel.
Definition: This field explicitly lists the actual times referenced by the code in TQ1-3. This field will be used to clarify the TQ1-3 in cases where the actual administration times vary within an institution. If the time of the service request spans more than a single day, this field is only practical if the same times of administration occur for each day of the service request. If the actual start time of the service request (as given by TQ1-7) is after the first explicit time, the first administration is taken to be the first explicit time after the start time. In the case where the patient moves to a location having a different set of explicit times, the existing service request may be updated with a new quantity/timing segment showing the changed explicit times.
Usage Note: This field is not valued if a Repeat Pattern is not present.
Definition: This field is used to define the interval between schedules for service request or bottle records. If this field contains a value, it overrides any value in the explicit time interval field. The units component of the CQ data type is constrained to units of time.
Examples:
TQ1|1|1|Q1H||60^min&&ANS+ - Q1H is defined with an interval between services of 60 minutes
TQ1|1|1|Q6H||6^hr&&ANS+ - Q6H is defined with an interval between services of 6 hours
TQ1|1|1|QD||1^d&&ANS+ - QD is defined with an interval between services of 1 day
Definition: This field contains the duration for which the service is requested.
The quantity component of this field must be a positive, non-zero number. The unit's portion of this field is constrained to units of time.
Example: Whirlpool twenty minutes three times per day for 3 days. Three days is the service duration.
TQ1|1||TID|||3^d&&ANS+||||||20^min&&ANS+|9<cr>
Definition: This field may be specified by the requester, in which case it indicates the earliest date/time at which the services should be started. In many cases, however, the start date/time will be implied or will be defined by other fields in the service request record (e.g., urgency - STAT). In such a case, this field will be empty.
The filling service will often record a value in this field after receipt of the service request, however, and compute an end time on the basis of the start date/time for the filling service's internal use.
Definition: When filled in by the requester of the service, this field should contain the latest date/time that the service should be performed. If it has not been performed by the specified time, it should not be performed at all. The requester may not always fill in this value, yet the filling service may fill it in on the basis of the instruction it receives and the actual start time.
Regardless of the value of the end date/time, the service should be stopped at the earliest of the date/times specified by either the duration or the end date/time.
Definition: This field describes the urgency of the request. If this field is blank, the default is R. Refer to User-Defined Table 0485 – Extended Priority Codes in Chapter 2C, Code Tables, for suggested values.
Definition: This is a free text field that describes the conditions under which the drug is to be given. For example, "PRN pain," or "to keep blood pressure below 110."
The presence of text in this field should be taken to mean that human review is needed to determine the how and/or when this drug should be given.
For complex codified conditions see the TQ2 segment below.
Definition: This field is a full text version of the instruction (optional).
Definition: This field indicates that a second TQ1 segment is to follow. Refer To HL7 Table 0472 – TQ Conjunction ID in Chapter 2C, Code Tables, for allowed values.
For continuous or periodic services, the point at which the service is actually stopped is determined by the field TQ1-8 end date/time and TQ1-6 duration, whichever indicates an earlier stopping time. Ordinarily, only one of these fields would be present.
Condition Rule: If the TQ1 segment is repeated in the message, this field must be populated with the appropriate Conjunction code indicating the sequencing of the following TQ1 segment.
Definition: This field contains the duration for which a single performance of a service is requested. The quantity component of this field must be a positive, non-zero number when populated. The units component is constrained to be units of time.
Example: Whirlpool twenty minutes three times per day for three days. Twenty minutes is the occurrence duration.
TQ1|1||TID|||3^d&&ANS+||||||20^min&&ANS+|9<cr>
Definition: This field contains the total number of occurrences of a service that should result from this service request. If both the end date/time (TQ1-8) and the total occurrences are valued and the occurrences would extend beyond the end date/time, then the end date/time takes precedence. Otherwise the number of occurrences takes precedence.
Example: Whirlpool twenty minutes three times per day for three days. The total occurrences would be 9.
TQ1|1||TID|||3^d&&ANS+||||||20^min&&ANS+|9<cr>
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
