FHIR Release 3 (STU) R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.0.2: STU 3). (v3.5.0: R4 Ballot #2). 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-status.xml

Vocabulary Patient Care Work Group Maturity Level : N/A Ballot Status : Informative

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

Definition for Code System RequestStatus

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


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="request-status"/> 
  <meta> 
    

    <lastUpdated value="2018-08-19T21:48:56.559+10:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> RequestStatus</h2> 
      <div> 
        

        <p> Codes identifying the lifecycle stage of a request.</p> 

      </div> 
      <p> This code system http://hl7.org/fhir/request-status defines the following codes:</p> 
      <table class="codes">
        <tr> 
          

          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          draft

          <td style="white-space:nowrap">draft
            <a name="request-status-draft"> </a> 
          </td> 
          <td> Draft</td> 
          

          <td> The request has been created but is not yet complete or ready for action.</td> 
        </tr> 
        <tr> 
          active

          <td style="white-space:nowrap">active
            <a name="request-status-active"> </a> 
          </td> 
          <td> Active</td> 
          

          <td> The request is in force and ready to be acted upon.</td> 
        </tr> 
        <tr> 
          suspended
            

          <td style="white-space:nowrap">on-hold
            <a name="request-status-on-hold"> </a> 
          </td> 
          

          <td> On Hold</td> 
          <td> The authorization/request to act has been temporarily withdrawn but is expected to resume
             in the future

             in the future.</td> 

        </tr> 
        <tr> 
          cancelled
            

          <td style="white-space:nowrap">revoked
            <a name="request-status-revoked"> </a> 
          </td> 
          
          The authorization/request to act has been terminated prior to the full completion of the
             intended actions.  No further activity should occur.

          <td> Revoked</td> 
          <td> The authorization/request to act has been terminated prior to the known full completion
             of the intended actions.  No further activity should occur.</td> 

        </tr> 
        <tr> 
          completed

          <td style="white-space:nowrap">completed
            <a name="request-status-completed"> </a> 
          </td> 
          <td> Completed</td> 
          <td> Activity against the request has been sufficiently completed to the satisfaction of the
             requester

             requester.</td> 

        </tr> 
        <tr> 
          entered-in-error

          <td style="white-space:nowrap">entered-in-error
            <a name="request-status-entered-in-error"> </a> 
          </td> 
          <td> Entered in Error</td> 
          <td> This electronic record should never have existed, though it is possible that real-world
             decisions were based on it.  (If real-world activity has occurred, the status should be
             &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.)

             &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.).</td> 

        </tr> 
        <tr> 
          unknown

          <td style="white-space:nowrap">unknown
            <a name="request-status-unknown"> </a> 
          </td> 
          <td> Unknown</td> 
          <td> The authoring system does not know which of the status values currently applies for this
             request.  Note: This concept is not to be used for &quot;other&quot; . One of the listed
             statuses is presumed to apply,  but the system creating the request doesn't know.

             statuses is presumed to apply,  but the system creating the request does not know.</td> 

        </tr> 
      </table> 
    </div> 
  </text> 
  
    
  
  
    
  

  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueString value="Trial Use"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/> 
  </extension> 
  <url value="http://hl7.org/fhir/request-status"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    

    <value value="urn:oid:2.16.840.1.113883.4.642.1.112"/> 
  </identifier> 
  

  <version value="3.5.0"/> 
  <name value="RequestStatus"/> 
  <title value="RequestStatus"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  

  <date value="2018-08-19T21:48:56+10: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 identifying the lifecycle stage of a request."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/request-status"/> 
  <content value="complete"/> 
  <concept> 
    <code value="draft"/> 
    <display value="Draft"/> 
    

    <definition value="The request has been created but is not yet complete or ready for action."/> 
  </concept> 
  <concept> 
    <code value="active"/> 
    <display value="Active"/> 
    

    <definition value="The request is in force and ready to be acted upon."/> 
  </concept> 
  <concept> 
    
    

    <code value="on-hold"/> 
    <display value="On Hold"/> 
    <definition value="The authorization/request to act has been temporarily withdrawn but is expected to resume
     in the future

     in the future."/> 

  </concept> 
  <concept> 
    
    
    The authorization/request to act has been terminated prior to the full completion of the
     intended actions.  No further activity should occur.

    <code value="revoked"/> 
    <display value="Revoked"/> 
    <definition value="The authorization/request to act has been terminated prior to the known full completion
     of the intended actions.  No further activity should occur."/> 

  </concept> 
  <concept> 
    <code value="completed"/> 
    <display value="Completed"/> 
    <definition value="Activity against the request has been sufficiently completed to the satisfaction of the
     requester

     requester."/> 

  </concept> 
  <concept> 
    <code value="entered-in-error"/> 
    <display value="Entered in Error"/> 
    <definition value="This electronic record should never have existed, though it is possible that real-world
     decisions were based on it.  (If real-world activity has occurred, the status should be
     &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.)

     &quot;cancelled&quot; rather than &quot;entered-in-error&quot;.)."/> 

  </concept> 
  <concept> 
    <code value="unknown"/> 
    <display value="Unknown"/> 
    <definition value="The authoring system does not know which of the status values currently applies for this
     request.  Note: This concept is not to be used for &quot;other&quot; . One of the listed
     statuses is presumed to apply,  but the system creating the request doesn't know.

     statuses is presumed to apply,  but the system creating the request does not know."/> 

  </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.