HL7 Terminology (THO)
3.1.0 - Publication International flag

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

ValueSet: hl7VS-actpriority

Official URL: http://terminology.hl7.org/ValueSet/v2-0906 Version: 2.0.0
Active as of 2019-12-01 Responsible: HL7, Inc Computable Name: Hl7VSActpriority
Other Identifiers: : urn:oid:2.16.840.1.113883.21.434

Copyright/Legal: Copyright HL7. Licensed under creative commons public domain

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)

 

Expansion

This value set contains 15 concepts

Expansion based on actpriority v2.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v2-0906

CodeDisplayDefinition
AASAP - As soon as possible, next highest priority after statASAP - As soon as possible, next highest priority after stat
CRCallback results - filler should contact the placer as soon as results are available, even for preliminary resultsCallback results - filler should contact the placer as soon as results are available, even for preliminary results
CSCallback 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.
CSPCallback placer for scheduling - filler should contact the placer to schedule the serviceCallback placer for scheduling - filler should contact the placer to schedule the service
CSRContact recipient for scheduling - Filler should contact the service recipient (target) to schedule the serviceContact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service
ELElective - Beneficial to the patient but not essential for survival.Elective - Beneficial to the patient but not essential for survival.
EMEmergency - An unforeseen combination of circumstances or the resulting state that calls for immediate actionEmergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action
PPreop - 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 orderPreop – 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.
PRNAs 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.
RRoutine - Routine service, do at usual work hoursRoutine - Routine service, do at usual work hours
RRRush reporting - A report should be prepared and sent as quickly as possibleRush reporting - A report should be prepared and sent as quickly as possible
SStat - With highest priority (e.g. emergency).Stat - With highest priority (e.g. emergency).
TTiming 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).
UDUse 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.
URUrgent - Calls for prompt actionUrgent - 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

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.