HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

tqConjunctionId

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v2-0472
Version:2.1.0
Name:TqConjunctionId
Title:tqConjunctionId
Status:Active
Content:All the concepts defined by the code system are included in the code system resource
Definition:

HL7-defined code system of concepts specifying that a second timing specification is to follow using the repeat delimiter. Used in HL7 Version 2.x messaging in the TQ1 segment.

Publisher:HL7, Inc
Committee:Orders and Observations
OID:2.16.840.1.113883.18.300 (for OID based terminology systems)
Content Mode:Complete
Value Set:http://terminology.hl7.org/ValueSet/v2-0472 ( is the value set for all codes in this code system)
Copyright:

Copyright HL7. Licensed under creative commons public domain

Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

tqConjunctionId

HL7-defined code system of concepts specifying that a second timing specification is to follow using the repeat delimiter. Used in HL7 Version 2.x messaging in the TQ1 segment.

Copyright Statement: Copyright HL7. Licensed under creative commons public domain

Properties

CodeURLDescriptionType
statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statusStatus of the conceptcode
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedVersion of HL7 in which the code was deprecatedcode
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentV2 Concept Commentstring
v2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubV2 Concept Comment As Publishedstring

This code system http://terminology.hl7.org/CodeSystem/v2-0472 defines the following codes:

CodeDisplayDefinitionV2 Table StatusV2 Concept CommentV2 Concept Comment As Published
S SynchronousSynchronousADo the next specification after this one (unless otherwise constrained by the following fields: TQ1-7-start date/time and TQ1-8-end date/time). An "S" specification implies that the second timing sequence follows the first, e.g., when a service request is written to measure blood pressure Q15 minutes for the 1st hour, then every 2 hours for the next day.Do the next specification after this one (unless otherwise constrained by the following fields: TQ1-7-start date/time and TQ1-8-end date/time). An "S" specification implies that the second timing sequence follows the first, e.g., when a service request is written to measure blood pressure Q15 minutes for the 1st hour, then every 2 hours for the next day.
A AsynchronousAsynchronousADo the next specification in parallel with this one (unless otherwise constrained by the following fields: TQ1-7-start date/time and TQ1-8-end date/time). The conjunction of "A" specifies two parallel instructions, as are sometimes used in medication, e.g., prednisone given at 1 tab on Monday, Wednesday, Friday, and at 1/2 tab on Tuesday, Thursday, Saturday, Sunday.Do the next specification in parallel with this one (unless otherwise constrained by the following fields: TQ1-7-start date/time and TQ1-8-end date/time). The conjunction of "A" specifies two parallel instructions, as are sometimes used in medication, e.g., prednisone given at 1 tab on Monday, Wednesday, Friday, and at 1/2 tab on Tuesday, Thursday, Saturday, Sunday.
C Actuation TimeActuation TimeAIt will be followed by a completion time for the service. This code allows one to distinguish between the time and priority at which a service should be actuated (e.g., blood should be drawn) and the time and priority at which a service should be completed (e.g., results should be reported).It will be followed by a completion time for the service. This code allows one to distinguish between the time and priority at which a service should be actuated (e.g., blood should be drawn) and the time and priority at which a service should be completed (e.g., results should be reported).

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.