HL7 Terminology
1.0.0 - Publication
HL7 Terminology
1.0.0 - Publication
This page is part of the HL7 Terminology (v1.0.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 
Source view
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="v2-0472"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><h2>tqConjunctionId</h2><div><p>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.</p> </div><p><b>Copyright Statement:</b> Copyright HL7. Licensed under creative commons public domain</p><p><b>Properties</b></p><table class="grid"><tr><td><b>Code</b></td><td><b>URL</b></td><td><b>Description</b></td><td><b>Type</b></td></tr><tr><td>status</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#status</td><td>Status of the concept</td><td>code</td></tr><tr><td>deprecated</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated</td><td>Version of HL7 in which the code was deprecated</td><td>code</td></tr><tr><td>v2-concComment</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment</td><td>V2 Concept Comment</td><td>string</td></tr><tr><td>v2-concCommentAsPub</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub</td><td>V2 Concept Comment As Published</td><td>string</td></tr></table><p>This code system http://terminology.hl7.org/CodeSystem/v2-0472 defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>V2 Table Status</b></td><td><b>V2 Concept Comment</b></td><td><b>V2 Concept Comment As Published</b></td></tr><tr><td style="white-space:nowrap">S<a name="v2-0472-S"> </a></td><td>Synchronous</td><td>Synchronous</td><td>A</td><td>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.</td><td>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.</td></tr><tr><td style="white-space:nowrap">A<a name="v2-0472-A"> </a></td><td>Asynchronous</td><td>Asynchronous</td><td>A</td><td>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.</td><td>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.</td></tr><tr><td style="white-space:nowrap">C<a name="v2-0472-C"> </a></td><td>Actuation Time</td><td>Actuation Time</td><td>A</td><td>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).</td><td>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).</td></tr></table></div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="oo"/> </extension> <url value="http://terminology.hl7.org/CodeSystem/v2-0472"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.18.300"/> </identifier> <version value="2.1.0"/> <name value="TqConjunctionId"/> <title value="tqConjunctionId"/> <status value="active"/> <experimental value="false"/> <date value="2019-12-01T00:00:00-05:00"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/"/> </telecom> </contact> <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."/> <purpose value="Underlying Master Code System for V2 table 0472 (TQ Conjunction ID)"/> <copyright value="Copyright HL7. Licensed under creative commons public domain"/> <caseSensitive value="true"/> <valueSet value="http://terminology.hl7.org/ValueSet/v2-0472"/> <hierarchyMeaning value="is-a"/> <compositional value="false"/> <versionNeeded value="false"/> <content value="complete"/> <property> <code value="status"/> <uri value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#status"/> <description value="Status of the concept"/> <type value="code"/> </property> <property> <code value="deprecated"/> <uri value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated"/> <description value="Version of HL7 in which the code was deprecated"/> <type value="code"/> </property> <property> <code value="v2-concComment"/> <uri value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment"/> <description value="V2 Concept Comment"/> <type value="string"/> </property> <property> <code value="v2-concCommentAsPub"/> <uri value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub"/> <description value="V2 Concept Comment As Published"/> <type value="string"/> </property> <concept id="4869"> <code value="S"/> <display value="Synchronous"/> <definition value="Synchronous"/> <property> <code value="v2-concComment"/> <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="v2-concCommentAsPub"/> <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="status"/> <valueCode value="A"/> </property> </concept> <concept id="4870"> <code value="A"/> <display value="Asynchronous"/> <definition value="Asynchronous"/> <property> <code value="v2-concComment"/> <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="v2-concCommentAsPub"/> <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="status"/> <valueCode value="A"/> </property> </concept> <concept id="4871"> <code value="C"/> <display value="Actuation Time"/> <definition value="Actuation Time"/> <property> <code value="v2-concComment"/> <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="v2-concCommentAsPub"/> <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="status"/> <valueCode value="A"/> </property> </concept> </CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#1.0.0 based on FHIR 4.0.1. Generated 2020-05-09
Links: Table of Contents |
QA Report | Search
| Version History |
Propose a change