Release 4

Valueset-task-intent.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Value SetTaskIntent

<?xml version="1.0" encoding="UTF-8"?>

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="task-intent"/> 
  <meta> 
    <lastUpdated value="2021-01-21T15:34:20.265+00:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> TaskIntent</h2> 
      <div> 
        <p> Distinguishes whether the task is a proposal, plan or full order.</p> 

      </div> 
      <p> This value set includes codes from the following code systems:</p> 
      <ul> 
        <li> Include all codes defined in 
          <a href="codesystem-task-intent.html">
            <code> http://hl7.org/fhir/task-intent</code> 
          </a> 
        </li> 
        <li> Include these codes as defined in 
          <a href="codesystem-request-intent.html">
            <code> http://hl7.org/fhir/request-intent</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-proposal">proposal</a> 
              </td> 
              <td> Proposal</td> 
              <td> The request is a suggestion made by someone/something that does not have an intention
                 to ensure it occurs and without providing an authorization to act.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-plan">plan</a> 
              </td> 
              <td> Plan</td> 
              <td> The request represents an intention to ensure something occurs without providing an authorization
                 for others to act.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-order">order</a> 
              </td> 
              <td> Order</td> 
              <td> The request represents a request/demand and authorization for action by a Practitioner.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-original-order">original-order</a> 
              </td> 
              <td> Original Order</td> 
              <td> The request represents an original authorization for action.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-reflex-order">reflex-order</a> 
              </td> 
              <td> Reflex Order</td> 
              <td> The request represents an automatically generated supplemental authorization for action
                 based on a parent authorization together with initial results of the action taken against
                 that parent authorization.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-filler-order">filler-order</a> 
              </td> 
              <td> Filler Order</td> 
              <td> The request represents the view of an authorization instantiated by a fulfilling system
                 representing the details of the fulfiller's intention to act upon a submitted order.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-instance-order">instance-order</a> 
              </td> 
              <td> Instance Order</td> 
              <td> An order created in fulfillment of a broader order that represents the authorization for
                 a single activity occurrence.  E.g. The administration of a single dose of a drug.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-request-intent.html#request-intent-option">option</a> 
              </td> 
              <td> Option</td> 
              <td> The request represents a component or option for a RequestGroup that establishes timing,
                 conditionality and/or other constraints among a set of requests.  Refer to [[[RequestGroup]]]
                 for additional information on how this status is used.</td> 
            </tr> 
          </table> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="oo"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/task-intent"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.1240"/> 
  </identifier> 
  <version value="4.0.1"/> 
  <name value="TaskIntent"/> 
  <title value="TaskIntent"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <date value="2021-01-21T15:34:20+00:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="Distinguishes whether the task is a proposal, plan or full order."/> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/task-intent"/> 
    </include> 
    <include> 
      <system value="http://hl7.org/fhir/request-intent"/> 
      <concept> 
        <code value="proposal"/> 
      </concept> 
      <concept> 
        <code value="plan"/> 
      </concept> 
      <concept> 
        <code value="order"/> 
      </concept> 
      <concept> 
        <code value="original-order"/> 
      </concept> 
      <concept> 
        <code value="reflex-order"/> 
      </concept> 
      <concept> 
        <code value="filler-order"/> 
      </concept> 
      <concept> 
        <code value="instance-order"/> 
      </concept> 
      <concept> 
        <code value="option"/> 
      </concept> 
    </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.