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

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

ValueSet: ActPriority

Official URL: http://terminology.hl7.org/ValueSet/v3-ActPriority Version: 2.0.0
Active as of 2014-03-26 Computable Name: ActPriority
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.16866

A code or 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.

Discussion: This attribute is used in orders to indicate the ordered priority, and in event documentation it indicates the actual priority used to perform the act. In definition mood it indicates the available priorities.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActPriority
    CodeDisplayDefinition
    AASAPAs soon as possible, next highest priority after stat.
    CRcallback resultsFiller should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 version 2.3's reporting priority.)
    ELelectiveBeneficial to the patient but not essential for survival.
    EMemergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.
    PpreopUsed 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 neededAn "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.
    RroutineRoutine service, do at usual work hours.
    RRrush reportingA report should be prepared and sent as quickly as possible.
    SstatWith highest priority (e.g., emergency).
    Ttiming criticalIt is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
    UDuse as directedDrug is to be used as directed by the prescriber.
    URurgentCalls for prompt action.
  • Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-ActPriorityCallback
  • Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-xEncounterAdmissionUrgency

 

Expansion

This value set contains 15 concepts

CodeSystemDisplayDefinition
  Ahttp://terminology.hl7.org/CodeSystem/v3-ActPriorityASAP

As soon as possible, next highest priority after stat.

  CRhttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycallback 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.)

  ELhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityelective

Beneficial to the patient but not essential for survival.

  EMhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityemergency

An unforeseen combination of circumstances or the resulting state that calls for immediate action.

  Phttp://terminology.hl7.org/CodeSystem/v3-ActPrioritypreop

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.

  PRNhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityas 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.

  Rhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityroutine

Routine service, do at usual work hours.

  RRhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityrush reporting

A report should be prepared and sent as quickly as possible.

  Shttp://terminology.hl7.org/CodeSystem/v3-ActPrioritystat

With highest priority (e.g., emergency).

  Thttp://terminology.hl7.org/CodeSystem/v3-ActPrioritytiming critical

It is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).

  UDhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityuse as directed

Drug is to be used as directed by the prescriber.

  URhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityurgent

Calls for prompt action.

  CShttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycallback for scheduling

Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)

  CSPhttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycallback placer for scheduling

Filler should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)

  CSRhttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycontact 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.)


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
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26