Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

1.25.4.1.7 HL7 v3 Code System ActPriority

This code system (http://hl7.org/fhir/v3/ActPriority) is defined as part of HL7 v3.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-ActPriority
Name:v3 Code System ActPriority
Definition: 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.
OID: (for OID based terminology systems)
System URL:http://hl7.org/fhir/v3/ActPriority
System OID:2.16.840.1.113883.5.7
Source ResourceXML / JSON

This value set is not currently used

1.25.4.1.7.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/v3/ActPriority, which defines the following codes:

LvlCodeDisplayDefinition
1A ASAPAs soon as possible, next highest priority after stat.
1CR callback resultsFiller should contact the placer as soon as results are available, even for preliminary results. (Was "C" in HL7 verion 2.3's reporting priority.)
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.)
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.)
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.)
1EL electiveBeneficial to the patient but not essential for survival.
1EM emergencyAn unforeseen combination of circumstances or the resulting state that calls for immediate action.
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.
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.
1R routineRoutine service, do at usual work hours.
1RR rush reportingA report should be prepared and sent as quickly as possible.
1S statWith highest priority (e.g., emergency).
1T timing criticalIt is critical to come as close as possible to the requested time (e.g., for a through antimicrobial level).
1UD use as directedDrug is to be used as directed by the prescriber.
1UR urgentCalls for prompt action.