tqConjunctionId - HL7 Terminology (THO) v6.0.2

HL7 Terminology (THO)
6.0.2 - Publication International flag

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

CodeSystem: tqConjunctionId

Official URL: http://terminology.hl7.org/CodeSystem/v2-0472		Version: 2.0.0
Active as of 2019-12-01	Responsible: Health Level Seven International	Computable Name: TqConjunctionId
Other Identifiers: OID:2.16.840.1.113883.18.300
Copyright/Legal: This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

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.

Underlying Master Code System for V2 table 0472 (TQ Conjunction ID)

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

Hl7VSTqConjunctionId

Generated Narrative: CodeSystem v2-0472

Properties

This code system defines the following properties for its concepts

Name

Code

URI

Type

Description

status

http://terminology.hl7.org/CodeSystem/utg-concept-properties#status

code

Status of the concept

deprecated

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated

code

Version of HL7 in which the code was deprecated

V2 Concept Comment

v2-concComment

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment

string

V2 Concept Comment

V2 Concept Comment As Published

v2-concCommentAsPub

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub

string

V2 Concept Comment As Published

Concepts

This case-sensitive code system http://terminology.hl7.org/CodeSystem/v2-0472 defines the following codes in a Is-A hierarchy:

Code	Display	Definition	V2 Concept Comment	V2 Concept Comment As Published
S	Synchronous	Synchronous	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.	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	Asynchronous	Asynchronous	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.	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 Time	Actuation Time	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).	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).