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 HL7 v3 Value Set ActPriority

Vocabulary Work Group Maturity Level: N/AExternalUse Context: Any

This value set (http://hl7.org/fhir/ValueSet/v3-ActPriority) is defined as part of HL7 v3.


Defining URL:http://hl7.org/fhir/ValueSet/v3-ActPriority
Name:v3 Code System ActPriority
Definition: 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.
OID: (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

This value set includes codes from the following code systems:


This expansion generated 19 Apr 2017

This value set contains 15 concepts

Expansion based on http://hl7.org/fhir/v3/ActPriority version 2016-11-11

All codes from system http://hl7.org/fhir/v3/ActPriority

AASAPAs soon as possible, next highest priority after stat.
CRcallback resultsFiller should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 version 2.3's reporting priority.)
CScallback for schedulingFiller should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
  CSPcallback placer for schedulingFiller should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
  CSRcontact recipient for schedulingFiller should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
ELelectiveBeneficial to the patient but not essential for survival.
EMemergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.
PpreopUsed 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.
PRNas neededAn "as needed" order should be accompanied by a description of what constitutes a need. This description is represented by an observation service predicate as a precondition.
RroutineRoutine service, do at usual work hours.
RRrush reportingA report should be prepared and sent as quickly as possible.
SstatWith highest priority (e.g., emergency).
Ttiming criticalIt is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
UDuse as directedDrug is to be used as directed by the prescriber.
URurgentCalls for prompt action.