HL7.TERMINOLOGY\tqConjunctionId

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

CodeSystem: tqConjunctionId

Summary

Defining URL:

http://terminology.hl7.org/CodeSystem/v2-0472

Version:

2.1.0

Name:

TqConjunctionId

Status:

Active as of 2019-12-01

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

Content:

Complete: All the concepts defined by the code system are included in the code system resource

OID:

2.16.840.1.113883.18.300 (for OID based terminology systems)

Value Set:

http://terminology.hl7.org/ValueSet/v2-0472 ( is the value set for all codes in this code system)

Source Resource:

XML / JSON / Turtle

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

Hl7VSTqConjunctionId

Properties

Code

URL

Description

Type

status

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

Status of the concept

code

deprecated

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

Version of HL7 in which the code was deprecated

code

v2-concComment

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

V2 Concept Comment

string

v2-concCommentAsPub

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

V2 Concept Comment As Published

string

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

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).

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise

Vocabulary WG

Ted Klein

Migrated to the UTG maintenance environment and publishing tooling.