HL7 v2.9.1 Vocabulary
0.2.0 - ci-build

HL7 v2.9.1 Vocabulary, published by HL7/FO. This guide is not an authorized publication; it is the continuous build for version 0.2.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.v291/ and changes regularly. See the Directory of published versions

## ValueSet: ActPriority (2.9.1 - 1.0.0) (Experimental)

Official URL: http://terminology.hl7.org/v2plusvocab/ValueSet/hl7VSactpriority | Version: 1.0.0
Active as of 2026-03-13 | Computable Name: Hl7VSactpriority
Other Identifiers: OID:2.16.840.1.113883.21.434, urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#http://terminology.hl7.org/v2plusvocab/ValueSet/v2-0906
Copyright/Legal: HL7 Inc., 2026

Value Set of codes specifying the priority for a shipment.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

### Logical Definition (CLD)

- Include all codes defined in `http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` version 📍1.0.0

### Expansion

Expansion performed internally based on codesystem ActPriority (2.9.1 - 1.0.0) v1.0.0 (CodeSystem)

This value set contains 15 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | A | ASAP - As soon as possible, next highest priority after stat | ASAP - As soon as possible, next highest priority after stat |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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 |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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. |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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 |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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 |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | EL | Elective - Beneficial to the patient but not essential for survival. | Elective - Beneficial to the patient but not essential for survival. |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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 |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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. |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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. |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | R | Routine - Routine service, do at usual work hours | Routine - Routine service, do at usual work hours |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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 |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | S | Stat - With highest priority (e.g. emergency). | Stat - With highest priority (e.g. emergency). |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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). |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | 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. |  |
`http://terminology.hl7.org/v2plusvocab/CodeSystem/actpriority` | UR | Urgent - Calls for prompt action | Urgent - Calls for prompt action |  |

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
System | 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