HL7 Terminology (THO)
7.0.0 - publication
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. 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)
http://terminology.hl7.org/CodeSystem/v2-0906 version 📍2.0.0
Expansion performed internally based on codesystem actpriority v2.0.0 (CodeSystem)
This value set contains 15 concepts
| System | Code | Display (en) | JSON | XML |
http://terminology.hl7.org/CodeSystem/v2-0906 | A | ASAP - As soon as possible, next highest priority after stat | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | CR | Callback results - filler should contact the placer as soon as results are available, even for preliminary results | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | CS | Callback for scheduling - Filler should contact the placer (or target) to schedule the service. | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | CSP | Callback placer for scheduling - filler should contact the placer to schedule the service | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | CSR | Contact recipient for scheduling - Filler should contact the service recipient (target) to schedule the service | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | EL | Elective - Beneficial to the patient but not essential for survival. | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | EM | Emergency - An unforeseen combination of circumstances or the resulting state that calls for immediate action | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | 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 | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | 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. | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | R | Routine - Routine service, do at usual work hours | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | RR | Rush reporting - A report should be prepared and sent as quickly as possible | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | S | Stat - With highest priority (e.g. emergency). | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | T | Timing critical - It is critical to come as close as possible to the requested time (e.g. for a through antimicrobial level). | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | UD | Use as directed - Drug is to be used as directed by the prescriber. | ||
http://terminology.hl7.org/CodeSystem/v2-0906 | UR | 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 | Author | Custodian | Comment |
| 2023-11-14 | revise | Marc Duteau | TSMG | Add standard copyright and contact to internal content; up-476 |
| 2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |