Estonian Terminology resources
1.0.0 - trial-use Estonia flag

Publication Build: This will be filled in by the publication tooling

ValueSet: Act Priority

Official URL: https://fhir.ee/ValueSet/act-priority Version: 1.0.0
Active as of 2025-06-19 Computable Name: EEActPriority

Act Priority

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

CodeSystemDisplay (en-US)Definition
  Ahttp://terminology.hl7.org/CodeSystem/v3-ActPriorityASAPAs soon as possible, next highest priority after stat.
  CRhttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycallback 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.)
  ELhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityelectiveBeneficial to the patient but not essential for survival.
  EMhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityemergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.
  Phttp://terminology.hl7.org/CodeSystem/v3-ActPrioritypreopUsed 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 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.
  Rhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityroutineRoutine service, do at usual work hours.
  RRhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityrush reportingA report should be prepared and sent as quickly as possible.
  Shttp://terminology.hl7.org/CodeSystem/v3-ActPrioritystatWith highest priority (e.g., emergency).
  Thttp://terminology.hl7.org/CodeSystem/v3-ActPrioritytiming criticalIt 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 directedDrug is to be used as directed by the prescriber.
  URhttp://terminology.hl7.org/CodeSystem/v3-ActPriorityurgentCalls for prompt action.
  CShttp://terminology.hl7.org/CodeSystem/v3-ActPrioritycallback for schedulingFiller 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 schedulingFiller 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 schedulingFiller 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