HL7 v2.9 Vocabulary
0.1.0 - ci-build

HL7 v2.9 Vocabulary, published by HL7/FO. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/hl7.v2.terminology.v29/ and changes regularly. See the Directory of published versions

## CodeSystem: ActPriority (2.9 - 1.0.0) (Experimental)

Official URL: http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority | Version: 1.0.0
Active as of 2026-01-27 | Computable Name: Actpriority
Other Identifiers: OID:2.16.840.1.113883.18.417
Copyright/Legal: HL7 Inc., 2026

HL7-defined code system of concepts specifying the priority for the shipment. Used in HL7 Version 2.x messaging in the SHP segment.

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

- Hl7VSactpriority

Properties

This code system defines the following properties for its concepts

Name | Code | URI | Type | Description
versionIntroduced | versionIntroduced | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced | string | version when was this code introduced
versionDeprecated | versionDeprecated | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated | string | version when was this code deprecated
status | status | http://hl7.org/fhir/concept-properties#status | code | A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired
comment | comment | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#comment | string | A string that provides additional detail pertinent to the use or understanding of the concept
usage | usage | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage | string | usage notes for this code
modified | modified | http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified | dateTime | date of last modification

Concepts

This case-sensitive code system `http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` defines the following codes:

Code | Display | Definition | versionIntroduced | modified
A | ASAP - As soon as possible, next highest priority after stat | ASAP - As soon as possible, next highest priority after stat | 2.7 | 2015-07-13
CR | Callback results - filler should contact the placer as soon as results are available, even for preliminary results | Callback results - filler should contact the placer as soon as results are available, even for preliminary results | 2.7 | 2015-07-13
CS | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. | 2.7 | 2015-07-13
CSP | Callback placer for scheduling - filler should contact the placer to schedule the service | Callback placer for scheduling - filler should contact the placer to schedule the service | 2.7 | 2015-07-13
CSR | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service | 2.7 | 2015-07-13
EL | Elective - Beneficial to the patient but not essential for survival. | Elective - Beneficial to the patient but not essential for survival. | 2.7 | 2015-07-13
EM | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action | 2.7 | 2015-07-13
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 | 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. | 2.7 | 2015-07-13
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. | 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. | 2.7 | 2015-07-13
R | Routine - Routine service, do at usual work hours | Routine - Routine service, do at usual work hours | 2.7 | 2015-07-13
RR | Rush reporting - A report should be prepared and sent as quickly as possible | Rush reporting - A report should be prepared and sent as quickly as possible | 2.7 | 2015-07-13
S | Stat - With highest priority (e.g. emergency). | Stat - With highest priority (e.g. emergency). | 2.7 | 2015-07-13
T | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). | 2.7 | 2015-07-13
UD | Use as directed - Drug is to be used as directed by the prescriber. | Use as directed - Drug is to be used as directed by the prescriber. | 2.7 | 2015-07-13
UR | Urgent - Calls for prompt action | Urgent - Calls for prompt action | 2.7 | 2015-07-13