Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

4.3.2.62 CodeSystem http://hl7.org/fhir/request-priority

Clinical Decision Support icon Work Group Maturity Level: 4Trial Use Use Context: Country: World, Not yet ready for Production use
Official URL: http://hl7.org/fhir/request-priority Version: 5.0.0
draft as of 2023-03-26 Computable Name: RequestPriority
Flags: Experimental, CaseSensitive, Complete. All codes ValueSet: RequestPriority OID: 2.16.840.1.113883.4.642.4.116

This Code system is used in the following value sets:

  • ValueSet: RequestPriority (Identifies the level of importance to be assigned to actioning the request.)

4.3.2.62.1 Definition

Identifies the level of importance to be assigned to actioning the request.

4.3.2.62.2 Content

This code system http://hl7.org/fhir/request-priority defines the following codes:

CodeDisplayDefinitionCopy
routine RoutineThe request has normal priority.btn btn
urgent UrgentThe request should be actioned promptly - higher priority than routine.btn btn
asap ASAPThe request should be actioned as soon as possible - higher priority than urgent.btn btn
stat STATThe request should be actioned immediately - highest possible priority. E.g. an emergency.btn btn

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code