ActPriority - HL7 Terminology (THO) v7.1.0

HL7 Terminology (THO)
7.1.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

CodeSystem: ActPriority

Official URL: http://terminology.hl7.org/CodeSystem/v3-ActPriority	Version: 4.0.0	Highlight text changes?
	Responsible: Health Level Seven International	Computable Name: ActPriority
Other Identifiers: OID:2.16.840.1.113883.5.7
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

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.

This Code system is referenced in the definition of the following value sets:

Language: en

Properties

This code system defines the following properties for its concepts

Name

Code

URI

Type

Description

Status

status

http://hl7.org/fhir/concept-properties#status

code

Designation of a concept's state. Normally is not populated unless the state is retired.

Concepts

This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-ActPriority defines the following codes in a Is-A hierarchy:

Lvl	Code	Display	Definition	Status
1	A	ASAP	As soon as possible, next highest priority after stat.	active
1	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.)	active
1	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.)	active
2	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.)	active
2	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.)	active
1	EL	elective	Beneficial to the patient but not essential for survival.	active
1	EM	emergency	An unforeseen combination of circumstances or the resulting state that calls for immediate action.	active
1	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.	active
1	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.	active
1	R	routine	Routine service, do at usual work hours.	active
1	RR	rush reporting	A report should be prepared and sent as quickly as possible.	active
1	S	stat	With highest priority (e.g., emergency).	active
1	T	timing critical	It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).	active
1	UD	use as directed	Drug is to be used as directed by the prescriber.	active
1	UR	urgent	Calls for prompt action.	active