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

4.3.2.7 4.4.2.7 HL7 v3 Value Set ActPriority

Vocabulary Work Group   Maturity Level : N/A 1 External Draft Use Context : Any

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

Summary

Defining URL: http://hl7.org/fhir/ValueSet/v3-ActPriority 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 Resource XML / JSON

This value set is used in the following places:

4.3.2.7.1 4.4.2.7.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.2.7.2 4.4.2.7.2 Expansion

This expansion generated 19 Apr 2017 Aug 2018

This value set contains 15 concepts

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

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

Lvl Code Display Definition
0 A ASAP As soon as possible, next highest priority after stat.
0 CR callback results Filler should contact the placer as soon as results are available, even for preliminary results. (Was "C" "C" in HL7 version 2.3's reporting priority.)
0 CS callback for scheduling Filler should contact the placer (or target) to schedule the service. (Was "C" "C" in HL7 version 2.3's TQ-priority component.)
1    CSP callback placer for scheduling Filler should contact the placer to schedule the service. (Was "C" "C" in HL7 version 2.3's TQ-priority component.)
1    CSR contact recipient for scheduling Filler should contact the service recipient (target) to schedule the service. (Was "C" "C" in HL7 version 2.3's TQ-priority component.)
0 EL elective Beneficial to the patient but not essential for survival.
0 EM emergency An unforeseen combination of circumstances or the resulting state that calls for immediate action.
0 P preop 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.
0 PRN as needed An "as needed" "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.
0 R routine Routine service, do at usual work hours.
0 RR rush reporting A report should be prepared and sent as quickly as possible.
0 S stat With highest priority (e.g., emergency).
0 T timing critical It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
0 UD use as directed Drug is to be used as directed by the prescriber.
0 UR urgent Calls for prompt action.