FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 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: R5 R4B R4 R3

Codesystem-request-priority.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

Definition for Code System RequestPriority

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="request-priority"/> 
  <meta> 
    <lastUpdated value="2019-10-24T11:53:00+11:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> RequestPriority</h2> 
      <div> 
        <p> Identifies the level of importance to be assigned to actioning the request</p> 

      </div> 
      <p> This code system http://hl7.org/fhir/request-priority defines the following codes:</p> 
      <table class="codes">
        <tr> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td> routine
            <a name="request-priority-routine"> </a> 
          </td> 
          <td> Routine</td> 
          <td> The request has normal priority</td> 
        </tr> 
        <tr> 
          <td> urgent
            <a name="request-priority-urgent"> </a> 
          </td> 
          <td> Urgent</td> 
          <td> The request should be actioned promptly - higher priority than routine</td> 
        </tr> 
        <tr> 
          <td> asap
            <a name="request-priority-asap"> </a> 
          </td> 
          <td> ASAP</td> 
          <td> The request should be actioned as soon as possible - higher priority than urgent</td> 
        </tr> 
        <tr> 
          <td> stat
            <a name="request-priority-stat"> </a> 
          </td> 
          <td> STAT</td> 
          <td> The request should be actioned immediately - highest possible priority.  E.g. an emergency</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="Informative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <url value="http://hl7.org/fhir/request-priority"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.1.107"/> 
  </identifier> 
  <version value="3.0.2"/> 
  <name value="RequestPriority"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <date value="2019-10-24T11:53:00+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="Identifies the level of importance to be assigned to actioning the request"/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/request-priority"/> 
  <content value="complete"/> 
  <concept> 
    <code value="routine"/> 
    <display value="Routine"/> 
    <definition value="The request has normal priority"/> 
  </concept> 
  <concept> 
    <code value="urgent"/> 
    <display value="Urgent"/> 
    <definition value="The request should be actioned promptly - higher priority than routine"/> 
  </concept> 
  <concept> 
    <code value="asap"/> 
    <display value="ASAP"/> 
    <definition value="The request should be actioned as soon as possible - higher priority than urgent"/> 
  </concept> 
  <concept> 
    <code value="stat"/> 
    <display value="STAT"/> 
    <definition value="The request should be actioned immediately - highest possible priority.  E.g. an emergency"/> 
  </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.