HL7 Terminology (THO)
6.0.2 - Publication
This page is part of the HL7 Terminology (v6.0.2: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v2-0906 | Version: 2.0.0 | |||
Active as of 2019-12-01 | Responsible: Health Level Seven International | Computable Name: Hl7VSActpriority | ||
Other Identifiers: OID:2.16.840.1.113883.21.434 | ||||
Copyright/Legal: This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
Value Set of codes specifying the priority for a shipment.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet v2-0906
http://terminology.hl7.org/CodeSystem/v2-0906
Generated Narrative: ValueSet
Expansion based on codesystem actpriority v2.0.0 (CodeSystem)
This value set contains 15 concepts
Code | System | Display | Definition |
A | http://terminology.hl7.org/CodeSystem/v2-0906 | ASAP - As soon as possible, next highest priority after stat | ASAP - As soon as possible, next highest priority after stat |
CR | http://terminology.hl7.org/CodeSystem/v2-0906 | Callback results - filler should contact the placer as soon as results are available, even for preliminary results | Callback results - filler should contact the placer as soon as results are available, even for preliminary results |
CS | http://terminology.hl7.org/CodeSystem/v2-0906 | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. |
CSP | http://terminology.hl7.org/CodeSystem/v2-0906 | Callback placer for scheduling - filler should contact the placer to schedule the service | Callback placer for scheduling - filler should contact the placer to schedule the service |
CSR | http://terminology.hl7.org/CodeSystem/v2-0906 | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service |
EL | http://terminology.hl7.org/CodeSystem/v2-0906 | Elective - Beneficial to the patient but not essential for survival. | Elective - Beneficial to the patient but not essential for survival. |
EM | http://terminology.hl7.org/CodeSystem/v2-0906 | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action |
P | http://terminology.hl7.org/CodeSystem/v2-0906 | 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 | 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. |
PRN | http://terminology.hl7.org/CodeSystem/v2-0906 | 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. | 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. |
R | http://terminology.hl7.org/CodeSystem/v2-0906 | Routine - Routine service, do at usual work hours | Routine - Routine service, do at usual work hours |
RR | http://terminology.hl7.org/CodeSystem/v2-0906 | Rush reporting - A report should be prepared and sent as quickly as possible | Rush reporting - A report should be prepared and sent as quickly as possible |
S | http://terminology.hl7.org/CodeSystem/v2-0906 | Stat - With highest priority (e.g. emergency). | Stat - With highest priority (e.g. emergency). |
T | http://terminology.hl7.org/CodeSystem/v2-0906 | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). |
UD | http://terminology.hl7.org/CodeSystem/v2-0906 | Use as directed - Drug is to be used as directed by the prescriber. | Use as directed - Drug is to be used as directed by the prescriber. |
UR | http://terminology.hl7.org/CodeSystem/v2-0906 | Urgent - Calls for prompt action | Urgent - Calls for prompt action |
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
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |