HL7.TERMINOLOGY\ActPriority

This page is part of the HL7 Terminology (v2.1.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

CodeSystem: ActPriority

Summary

Defining URL:

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

Version:

2.0.0

Name:

ActPriority

Status:

Active as of 2019-03-20

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.

Publisher:

Health Level 7

Content:

Complete: All the concepts defined by the code system are included in the code system resource

OID:

2.16.840.1.113883.5.7 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

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

Properties

Code

URL

Description

Type

Specializes

The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.

Coding

Generalizes

Inverse of Specializes. Only included as a derived relationship.

Coding

internalId

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id

The internal identifier for the concept in the HL7 Access database repository.

code

status

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

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

code

This code system http://terminology.hl7.org/CodeSystem/v3-ActPriority defines the following codes:

Lvl	Code	Display	Definition	internalId	status
1	A	ASAP	As soon as possible, next highest priority after stat.	16868	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.)	16876	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.)	16871	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.)	16872	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.)	16873	active
1	EL	elective	Beneficial to the patient but not essential for survival.	12239	active
1	EM	emergency	An unforeseen combination of circumstances or the resulting state that calls for immediate action.	12241	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.	16870	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.	16875	active
1	R	routine	Routine service, do at usual work hours.	16869	active
1	RR	rush reporting	A report should be prepared and sent as quickly as possible.	16877	active
1	S	stat	With highest priority (e.g., emergency).	16867	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).	16874	active
1	UD	use as directed	Drug is to be used as directed by the prescriber.	20843	active
1	UR	urgent	Calls for prompt action.	12240	active

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise

Vocabulary WG

Ted Klein

Migrated to the UTG maintenance environment and publishing tooling.