Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) 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: R4 R3

4.4.2.7 HL7 v3 Value Set ActPriority

Vocabulary Work Group Maturity Level: 1Draft Use Context: Any

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

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-ActPriority
Version:2018-08-12
Name:v3.ActPriority
Title: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 01 Nov 2019


This value set contains 15 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-ActPriority version 2018-08-12

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActPriority

LvlCodeDisplayDefinition
0AASAPAs soon as possible, next highest priority after stat.
0CRcallback 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.)
0CScallback for schedulingFiller should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
1  CSPcallback placer for schedulingFiller should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
1  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.)
0ELelectiveBeneficial to the patient but not essential for survival.
0EMemergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.
0PpreopUsed 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.
0PRNas 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.
0RroutineRoutine service, do at usual work hours.
0RRrush reportingA report should be prepared and sent as quickly as possible.
0SstatWith highest priority (e.g., emergency).
0Ttiming criticalIt is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
0UDuse as directedDrug is to be used as directed by the prescriber.
0URurgentCalls for prompt action.