STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

V2-0472.vs.xml

Raw XML (canonical form)

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

<ValueSet 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>
  <url value="http://hl7.org/fhir/ValueSet/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)"/>
  <compose>
    <include>
      <system value="http://hl7.org/fhir/v2/0472"/>
    </include>
  </compose>
</ValueSet>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.