FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/request-intent (XML)

Clinical Decision Support Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Code SystemRequestIntent

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

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="request-intent"/> 
  <meta> 
    <lastUpdated value="2024-04-19T18:19:53.040+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This case-sensitive code system 
        <code> http://hl7.org/fhir/request-intent</code>  defines the following codes in an undefined heirarchy:
      </p> 
      <table class="codes">
        <tr> 
          <td> 
            <b> Lvl</b> 
          </td> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">proposal
            <a name="request-intent-proposal"> </a> 
          </td> 
          <td> Proposal</td> 
          <td> 
            <div> 
              <p> 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.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">plan
            <a name="request-intent-plan"> </a> 
          </td> 
          <td> Plan</td> 
          <td> 
            <div> 
              <p> The request represents an intention to ensure something occurs without providing
                 an authorization for others to act.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">directive
            <a name="request-intent-directive"> </a> 
          </td> 
          <td> Directive</td> 
          <td> 
            <div> 
              <p> The request represents a legally binding instruction authored by a Patient or RelatedPerson.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">order
            <a name="request-intent-order"> </a> 
          </td> 
          <td> Order</td> 
          <td> 
            <div> 
              <p> The request represents a request/demand and authorization for action by the requestor.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  original-order
            <a name="request-intent-original-order"> </a> 
          </td> 
          <td> Original Order</td> 
          <td> 
            <div> 
              <p> The request represents an original authorization for action.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  reflex-order
            <a name="request-intent-reflex-order"> </a> 
          </td> 
          <td> Reflex Order</td> 
          <td> 
            <div> 
              <p> 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.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 2</td> 
          <td style="white-space:nowrap">  filler-order
            <a name="request-intent-filler-order"> </a> 
          </td> 
          <td> Filler Order</td> 
          <td> 
            <div> 
              <p> 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.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 3</td> 
          <td style="white-space:nowrap">    instance-order
            <a name="request-intent-instance-order"> </a> 
          </td> 
          <td> Instance Order</td> 
          <td> 
            <div> 
              <p> 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.</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> 1</td> 
          <td style="white-space:nowrap">option
            <a name="request-intent-option"> </a> 
          </td> 
          <td> Option</td> 
          <td> 
            <div> 
              <p> The request represents a component or option for a RequestOrchestration that establishes
                 timing, conditionality and/or other constraints among a set of requests.  Refer
                 to 
                <a href="requestorchestration.html#RequestOrchestration">RequestOrchestration</a>  for additional information on how this status is used.
              </p> 

            </div> 
          </td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/> 
  </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="4"/> 
  </extension> 
  <url value="http://hl7.org/fhir/request-intent"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.4.114"/> 
  </identifier> 
  <version value="6.0.0-cibuild"/> 
  <name value="RequestIntent"/> 
  <title value="RequestIntent"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2024-04-19T18:19:53+00:00"/> 
  <publisher value="HL7 International / Clinical Decision Support"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://www.hl7.org/Special/committees/fiwg"/> 
    </telecom> 
  </contact> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://www.hl7.org/Special/committees/dss"/> 
    </telecom> 
  </contact> 
  <description value="Codes indicating the degree of authority/intentionality associated with a request."/> 
  <jurisdiction> 
    <coding> 
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> 
      <code value="001"/> 
      <display value="World"/> 
    </coding> 
  </jurisdiction> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/request-intent"/> 
  <content value="complete"/> 
  <concept> 
    <code value="proposal"/> 
    <display value="Proposal"/> 
    <definition value="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."/> 
  </concept> 
  <concept> 
    <code value="plan"/> 
    <display value="Plan"/> 
    <definition value="The request represents an intention to ensure something occurs without providing
     an authorization for others to act."/> 
  </concept> 
  <concept> 
    <code value="directive"/> 
    <display value="Directive"/> 
    <definition value="The request represents a legally binding instruction authored by a Patient or RelatedPerson."/> 
  </concept> 
  <concept> 
    <code value="order"/> 
    <display value="Order"/> 
    <definition value="The request represents a request/demand and authorization for action by the requestor."/> 
    <concept> 
      <code value="original-order"/> 
      <display value="Original Order"/> 
      <definition value="The request represents an original authorization for action."/> 
    </concept> 
    <concept> 
      <code value="reflex-order"/> 
      <display value="Reflex Order"/> 
      <definition value="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."/> 
    </concept> 
    <concept> 
      <code value="filler-order"/> 
      <display value="Filler Order"/> 
      <definition value="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."/> 
      <concept> 
        <code value="instance-order"/> 
        <display value="Instance Order"/> 
        <definition value="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."/> 
      </concept> 
    </concept> 
  </concept> 
  <concept> 
    <code value="option"/> 
    <display value="Option"/> 
    <definition value="The request represents a component or option for a RequestOrchestration that establishes
     timing, conditionality and/or other constraints among a set of requests.  Refer
     to [[[RequestOrchestration]]] for additional information on how this status is
     used."/> 
  </concept> 
</CodeSystem> 

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.