HL7 Terminology (THO)
2.1.33 - Continuous Process Integration (ci build)

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

CodeSystem: ActPriority


Defining URL:http://terminology.hl7.org/CodeSystem/v3-ActPriority
Status:Active as of 2019-03-20

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

Publisher:Health Level 7
Content:Complete: All the concepts defined by the code system are included in the code system resource
OID:2.16.840.1.113883.5.7 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

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


SpecializesThe child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.Coding
GeneralizesInverse of Specializes. Only included as a derived relationship.Coding
internalIdhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-idThe internal identifier for the concept in the HL7 Access database repository.code
statushttp://hl7.org/fhir/concept-properties#statusDesignation of a concept's state. Normally is not populated unless the state is retired.code

This code system http://terminology.hl7.org/CodeSystem/v3-ActPriority defines the following codes:

1A ASAPAs soon as possible, next highest priority after stat.16868active
1CR callback 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.)16876active
1CS callback for schedulingFiller should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)16871active
2  CSP callback placer for schedulingFiller should contact the placer to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)16872active
2  CSR contact recipient for schedulingFiller should contact the service recipient (target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)16873active
1EL electiveBeneficial to the patient but not essential for survival.12239active
1EM emergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.12241active
1P preopUsed 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.16870active
1PRN as 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.16875active
1R routineRoutine service, do at usual work hours.16869active
1RR rush reportingA report should be prepared and sent as quickly as possible.16877active
1S statWith highest priority (e.g., emergency).16867active
1T timing criticalIt is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).16874active
1UD use as directedDrug is to be used as directed by the prescriber.20843active
1UR urgentCalls for prompt action.12240active


2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.