HL7 Terminology (THO)
3.0.0 - Publication
HL7 Terminology (THO)
3.0.0 - Publication
This page is part of the HL7 Terminology (v3.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions 
Summary
| Defining URL: | http://terminology.hl7.org/ValueSet/v2-0906 |
| Version: | 2.0.0 |
| Name: | Hl7VSActpriority |
| Title: | hl7VS-actpriority |
| Status: | Active as of 12/1/19 |
| Definition: | Value Set of codes specifying the priority for a shipment. |
| Publisher: | HL7, Inc |
| Copyright: | Copyright HL7. Licensed under creative commons public domain |
| OID: | 2.16.840.1.113883.21.434 (for OID based terminology systems) |
| Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v2-0906
This value set contains 15 concepts
Expansion based on actpriority v2.1.0 (CodeSystem)
All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v2-0906
| Code | Display | Definition |
| A | ASAP - As soon as possible, next highest priority after stat | ASAP - As soon as possible, next highest priority after stat |
| CR | 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 | 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 | 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 | 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 | Elective - Beneficial to the patient but not essential for survival. | Elective - Beneficial to the patient but not essential for survival. |
| EM | 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 | 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 | 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 | Routine - Routine service, do at usual work hours | Routine - Routine service, do at usual work hours |
| RR | 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 | Stat - With highest priority (e.g. emergency). | Stat - With highest priority (e.g. emergency). |
| T | 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 | 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 | 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 |
| Source | 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 | Author | Custodian | Comment |
| 2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#3.0.0 based on FHIR 4.0.1. Generated 2021-12-02
Links: Table of Contents |
QA Report
| Version History |
Propose a change