Release 4 5

This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0: R5 - Mixed Normative and STU ) ). This is the current published version in it's permanent home (it will always be available at this URL). 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: R5 R4B R4 R3

Codesystem-request-intent.xml

Example CodeSystem/request-intent (XML)

Clinical Decision Support Work Group Maturity Level : N/A Standards Status : Informative

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

Definition for Code System RequestIntent SystemRequestIntent

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


  
  
    
  
  
    
    
      
      
        

      
      
      
        
          
            
          
          
            
          
          
            
          
          
            
          
        
        
          
          proposal
            
          
          

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="request-intent"/> 
  <meta> 
    <lastUpdated value="2023-03-26T15:21:02.749+11:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This code system 
        <code> http://hl7.org/fhir/request-intent</code>  defines the following codes:
      </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> 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.
        
        
          
          plan
            
          
          
          The request represents an intention to ensure something occurs without providing an authorization
             for others to act.
        
        
          
          directive
            
          
          
          
        
        
          
          order
            
          
          
          
        
        
          
            original-order
            
          
          
          
        
        
          
            reflex-order
            
          
          
          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.
        
        
          
            filler-order
            
          
          
          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.
        
        
          
              instance-order
            
          
          
          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.
        
        
          
          option
            
          
          
          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.
        
      
    
  
  
    
  
  
    
  
  
    
  
  
  
    
    
  
  
  
  
  
  
  
  
  
    
      
      
    
    
      
      
    
  
  
  
  
  
  
    
    

             to ensure it occurs and without providing an authorization to act.</td> 
        </tr>         <tr>           <td> 1</td>           <td style="white-space:nowrap">plan            <a name="request-intent-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> 1</td>           <td style="white-space:nowrap">directive            <a name="request-intent-directive"> </a>           </td>           <td> Directive</td>           <td> The request represents a legally binding instruction authored by a Patient or RelatedPerson.</td>         </tr>         <tr>           <td> 1</td>           <td style="white-space:nowrap">order            <a name="request-intent-order"> </a>           </td>           <td> Order</td>           <td> The request represents a request/demand and authorization for action by the requestor.</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> The request represents an original authorization for action.</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> 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> 2</td>           <td style="white-space:nowrap">  filler-order            <a name="request-intent-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> 3</td>           <td style="white-space:nowrap">    instance-order            <a name="request-intent-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> 1</td>           <td style="white-space:nowrap">option            <a name="request-intent-option"> </a>           </td>           <td> Option</td>           <td> 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.</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="5.0.0"/>   <name value="RequestIntent"/>   <title value="RequestIntent"/>   <status value="draft"/>   <experimental value="true"/>   <date value="2023-03-26T15:21:02+11: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="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.
  
  
    
    
    The request represents an intention to ensure something occurs without providing an authorization
     for others to act.
  
  
    
    
    
  
  
    
    
    
    
      
      
      
    
    
      
      
      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.
    
    
      
      
      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.
      
        
        
        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.
      
    
  
  
    
    
    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.
  

     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.