FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

CodeSystem: ActPriority

Official URL: http://terminology.hl7.org/CodeSystem/v3-ActPriority Version: 2.1.0
Standards status: Informative Maturity Level: 0 Computable Name: ActPriority

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.

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

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
Specializes Specializes Coding The 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.
Generalizes Generalizes Coding Inverse of Specializes. Only included as a derived relationship.
internalId internalId http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id code The internal identifier for the concept in the HL7 Access database repository.
Status status http://hl7.org/fhir/concept-properties#status code Designation of a concept's state. Normally is not populated unless the state is retired.

Concepts

This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-ActPriority defines the following codes in a Is-A hierarchy:

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