v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)
v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)
v2+ Vocabulary - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2025-08-05 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="tqConjunctionIdV111"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><ul><li>Include all codes defined in <a href="CodeSystem-tqConjunctionIdV111.html"><code>http://terminology.hl7.org/v2plusvocab/CodeSystem/tqConjunctionIdV111</code></a></li></ul></div>
</text>
<extension
url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-v2versionCreated">
<valueString value="2.9"/>
</extension>
<extension
url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-versionHistory">
<valueString value="generate correct history somehow"/>
</extension>
<extension
url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-tableNo">
<valueString value="0472"/>
</extension>
<url
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/tqConjunctionIdV111"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.18.300"/>
</identifier>
<version value="1.1.1"/>
<name value="TqConjunctionIdV111"/>
<title value="TQ Conjunction ID (2.9 - 1.1.1)"/>
<status value="active"/>
<experimental value="true"/>
<date value="2025-08-05T15:14:51+02:00"/>
<description
value="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 value="HL7 Inc., 2024"/>
<caseSensitive value="true"/>
<content value="complete"/>
<property>
<code value="versionIntroduced"/>
<uri
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced"/>
<description value="version when was this code introduced"/>
<type value="string"/>
</property>
<property>
<code value="versionDeprecated"/>
<uri
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated"/>
<description value="version when was this code deprecated"/>
<type value="string"/>
</property>
<property>
<code value="status"/>
<uri value="http://hl7.org/fhir/concept-properties#status"/>
<description
value="A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired"/>
<type value="code"/>
</property>
<property>
<code value="comment"/>
<uri
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#comment"/>
<description
value="A string that provides additional detail pertinent to the use or understanding of the concept"/>
<type value="string"/>
</property>
<property>
<code value="usage"/>
<uri
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage"/>
<description value="usage notes for this code"/>
<type value="string"/>
</property>
<property>
<code value="modified"/>
<uri
value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified"/>
<description value="date of last modification"/>
<type value="dateTime"/>
</property>
<concept>
<code value="A"/>
<display value="Asynchronous"/>
<definition value="Asynchronous"/>
<property>
<code value="comment"/>
<valueString
value="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."/>
</property>
<property>
<code value="modified"/>
<valueDateTime value="2015-07-13"/>
</property>
<property>
<code value="versionIntroduced"/>
<valueString value="2.4"/>
</property>
</concept>
<concept>
<code value="C"/>
<display value="Actuation Time"/>
<definition value="Actuation Time"/>
<property>
<code value="comment"/>
<valueString
value="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)."/>
</property>
<property>
<code value="modified"/>
<valueDateTime value="2015-07-13"/>
</property>
<property>
<code value="versionIntroduced"/>
<valueString value="2.4"/>
</property>
</concept>
<concept>
<code value="S"/>
<display value="Synchronous"/>
<definition value="Synchronous"/>
<property>
<code value="comment"/>
<valueString
value="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."/>
</property>
<property>
<code value="modified"/>
<valueDateTime value="2015-07-13"/>
</property>
<property>
<code value="versionIntroduced"/>
<valueString value="2.4"/>
</property>
</concept>
</CodeSystem>