V2-0472.cs.xml

FHIR Value set/code system definition for HL7 v2 table 0472 ( TQ Conjunction ID)

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v2-0472"/>
  <meta>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="additional"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>TQ Conjunction ID</p>

      <table class="grid">
        <tr>
          <td>
            <b>Code</b>
          </td>
          <td>
            <b>Description</b>
          </td>
          <td>
            <b>Comment</b>
          </td>
          <td>
            <b>Version</b>
          </td>
        </tr>
        <tr>
          <td>a
            <a name="a"> </a>
          </td>
          <td>Asynchronous</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
               &quot;A&quot; specifies two parallel instructions, as are sometimes used in medication,
               e.</td>
          <td>added v2.4</td>
        </tr>
        <tr>
          <td>c
            <a name="c"> </a>
          </td>
          <td>Actuation Time</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 complet</td>
          <td>added v2.4</td>
        </tr>
        <tr>
          <td>s
            <a name="s"> </a>
          </td>
          <td>Synchronous</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 &quot;S&quot; specification
               implies that the second timing sequence follows the first, e.g. when a service request
               is</td>
          <td>added v2.4</td>
        </tr>
      </table>

    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.133883.18.300"/>
  </extension>
  <url value="http://hl7.org/fhir/v2/0472"/>
  <version value="2.8.2"/>
  <name value="v2 TQ Conjunction ID"/>
  <status value="active"/>
  <experimental value="true"/>
  <publisher value="HL7, Inc"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org"/>
    </telecom>
  </contact>
  <description value="FHIR Value set/code system definition for HL7 v2 table 0472 ( TQ Conjunction ID)"/>
  <caseSensitive value="false"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/v2-0472"/>
  <content value="complete"/>
  <concept>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-comments">
      <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
         &quot;A&quot; specifies two parallel instructions, as are sometimes used in medication,
         e."/>
    </extension>
    <code value="A"/>
    <display value="Asynchronous"/>
  </concept>
  <concept>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-comments">
      <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 complet"/>
    </extension>
    <code value="C"/>
    <display value="Actuation Time"/>
  </concept>
  <concept>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-comments">
      <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 &quot;S&quot; specification
         implies that the second timing sequence follows the first, e.g. when a service request
         is"/>
    </extension>
    <code value="S"/>
    <display value="Synchronous"/>
  </concept>
</CodeSystem>