HL7.TERMINOLOGY\ActPriority

This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: ActPriority

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-ActPriority

Version:

2.0.0

Name:

ActPriority

Status:

Active as of 2014-03-26

Definition:

A code or 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.

Discussion: This attribute is used in orders to indicate the ordered priority, and in event documentation it indicates the actual priority used to perform the act. In definition mood it indicates the available priorities.

OID:

2.16.840.1.113883.1.11.16866 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

Encounter

Logical Definition (CLD)

This value set includes codes based on the following rules:

Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActPriority

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

Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-ActPriorityCallback
Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-xEncounterAdmissionUrgency

Expansion

This value set contains 15 concepts

Expansion based on:

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

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

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance)

Display

The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise