Release 5 Preview #2

This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). 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

4.3.14.53 Code System http://hl7.org/fhir/request-priority

Vocabulary

Work Group

Maturity Level: 0

Informative

Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/request-priority

Version: 4.4.0

Name: RequestPriority

Title: RequestPriority

Definition:

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

Committee: ??

OID: 2.16.840.1.113883.4.642.1.116 (for OID based terminology systems)

Source Resource XML / JSON

This Code system is used in the following value sets:

ValueSet: Request priority (The clinical priority of a diagnostic order.)

4.3.14.53.1 Content

4.3.14.53.2 RequestPriority

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

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

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 code systems 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. See Code System for further information.

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