This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Patient Care Work Group | Maturity Level: 3 | Informative | Use Context: Not Intended for Production use |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/request-priority |
Name: | RequestPriority |
Definition: | The clinical priority of a diagnostic order. |
Committee: | Patient Care Work Group |
OID: | 2.16.840.1.113883.4.642.3.106 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://hl7.org/fhir/request-priority
This expansion generated 19 Apr 2017
This value set contains 4 concepts
Expansion based on http://hl7.org/fhir/request-priority version 3.0.2
All codes from system http://hl7.org/fhir/request-priority
Code | Display | Definition |
routine | Routine | The request has normal priority |
urgent | Urgent | The request should be actioned promptly - higher priority than routine |
asap | ASAP | The request should be actioned as soon as possible - higher priority than urgent |
stat | STAT | The request should be actioned immediately - highest possible priority. E.g. an emergency |
See the full registry of value sets defined as part of FHIR.
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |