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: R4 R3 R2

V3-ActPriority.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-ActPriority"/> 
  <meta> 
    <lastUpdated value="2016-11-11T00:00:00.000+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Release Date: 2016-11-11</p> 

      <table class="grid">
 
        <tr> 
          <td> 
            <b> Level</b> 
          </td> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> A
            <a name="A"> </a> 
          </td> 
          <td> ASAP</td> 
          <td> 
                        As soon as possible, next highest priority after stat.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> CR
            <a name="CR"> </a> 
          </td> 
          <td> callback results</td> 
          <td> 
                        Filler should contact the placer as soon as results are available,
               even for preliminary results.  (Was &quot;C&quot; in HL7 version 2.3's reporting priority.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> CS
            <a name="CS"> </a> 
          </td> 
          <td> callback for scheduling</td> 
          <td> 
                        Filler should contact the placer (or target) to schedule the service.
                (Was &quot;C&quot; in HL7 version 2.3's TQ-priority component.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   CSP
            <a name="CSP"> </a> 
          </td> 
          <td> callback placer for scheduling</td> 
          <td> 
                        Filler should contact the placer to schedule the service.  (Was
               &quot;C&quot; in HL7 version 2.3's TQ-priority component.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   CSR
            <a name="CSR"> </a> 
          </td> 
          <td> contact recipient for scheduling</td> 
          <td> 
                        Filler should contact the service recipient (target) to schedule
               the service.  (Was &quot;C&quot; in HL7 version 2.3's TQ-priority component.)
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> EL
            <a name="EL"> </a> 
          </td> 
          <td> elective</td> 
          <td> 
                        Beneficial to the patient but not essential for survival.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> EM
            <a name="EM"> </a> 
          </td> 
          <td> emergency</td> 
          <td> 
                        An unforeseen combination of circumstances or the resulting state
               that calls for immediate action.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> P
            <a name="P"> </a> 
          </td> 
          <td> preop</td> 
          <td> 
                        Used to indicate that a service is to be performed prior to a
               scheduled surgery.  When ordering a service and using the pre-op priority, a check is
               done to see the amount of time that must be allowed for performance of the service.  When
               the order is placed, a message can be generated indicating the time needed for the service
               so that it is not ordered in conflict with a scheduled operation.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> PRN
            <a name="PRN"> </a> 
          </td> 
          <td> as needed</td> 
          <td> 
                        An &quot;as needed&quot; order should be accompanied by a description
               of what constitutes a need. This description is represented by an observation service
               predicate as a precondition.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> R
            <a name="R"> </a> 
          </td> 
          <td> routine</td> 
          <td> 
                        Routine service, do at usual work hours.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> RR
            <a name="RR"> </a> 
          </td> 
          <td> rush reporting</td> 
          <td> 
                        A report should be prepared and sent as quickly as possible.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> S
            <a name="S"> </a> 
          </td> 
          <td> stat</td> 
          <td> 
                        With highest priority (e.g., emergency).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> T
            <a name="T"> </a> 
          </td> 
          <td> timing critical</td> 
          <td> 
                        It is critical to come as close as possible to the requested time
               (e.g., for a through antimicrobial level).
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> UD
            <a name="UD"> </a> 
          </td> 
          <td> use as directed</td> 
          <td> 
                        Drug is to be used as directed by the prescriber.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> UR
            <a name="UR"> </a> 
          </td> 
          <td> urgent</td> 
          <td> 
                        Calls for prompt action.
            <br/>  

                     
          </td> 
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="External"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pa"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/v3-ActPriority"/> 
  <version value="2016-11-11"/> 
  <name value="v3 Code System ActPriority"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2016-11-11"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value=" A set of codes (e.g., for routine, emergency), specifying the urgency under which the
     Act happened, can happen, is happening, is intended to happen, or is requested/demanded
     to happen."/> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/v3/ActPriority"/> 
    </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.