HL7 Terminology (THO)
5.5.0 - Publication International flag

This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: hl7VS-actpriority

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: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn: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

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)

Logical Definition (CLD)

 

Expansion

Expansion based on codesystem actpriority v2.0.0 (CodeSystem)

This value set contains 15 concepts.

CodeSystemDisplayDefinition
  Ahttp://terminology.hl7.org/CodeSystem/v2-0906ASAP - As soon as possible, next highest priority after stat

ASAP - As soon as possible, next highest priority after stat

  CRhttp://terminology.hl7.org/CodeSystem/v2-0906Callback 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

  CShttp://terminology.hl7.org/CodeSystem/v2-0906Callback 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.

  CSPhttp://terminology.hl7.org/CodeSystem/v2-0906Callback 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

  CSRhttp://terminology.hl7.org/CodeSystem/v2-0906Contact 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

  ELhttp://terminology.hl7.org/CodeSystem/v2-0906Elective - Beneficial to the patient but not essential for survival.

Elective - Beneficial to the patient but not essential for survival.

  EMhttp://terminology.hl7.org/CodeSystem/v2-0906Emergency - 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

  Phttp://terminology.hl7.org/CodeSystem/v2-0906Preop - 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.

  PRNhttp://terminology.hl7.org/CodeSystem/v2-0906As 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.

  Rhttp://terminology.hl7.org/CodeSystem/v2-0906Routine - Routine service, do at usual work hours

Routine - Routine service, do at usual work hours

  RRhttp://terminology.hl7.org/CodeSystem/v2-0906Rush 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

  Shttp://terminology.hl7.org/CodeSystem/v2-0906Stat - With highest priority (e.g. emergency).

Stat - With highest priority (e.g. emergency).

  Thttp://terminology.hl7.org/CodeSystem/v2-0906Timing 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).

  UDhttp://terminology.hl7.org/CodeSystem/v2-0906Use 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.

  URhttp://terminology.hl7.org/CodeSystem/v2-0906Urgent - 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

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.