Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.4.1.312 4.4.1.349 Value Set ValueSet http://hl7.org/fhir/ValueSet/request-status

  Maturity Level : 2
Responsible Owner: FHIR Infrastructure icon Work Group Trial Use Use Context : Any Country: World
This is a value set defined by the FHIR project. Summary Committee:
Official URL : Title: http://hl7.org/fhir/ValueSet/request-status RequestStatus Definition: Codes identifying the lifecycle stage of a request. Version : 6.0.0-ballot3
draft as of 2025-11-10 FHIR Infrastructure Computable Name : RequestStatus Work Group
OID: Flags : Immutable 2.16.840.1.113883.4.642.3.111 (for OID based terminology systems) Source Resource XML / JSON : 2.16.840.1.113883.4.642.3.111

This value set is used in the following places:

Codes identifying the lifecycle stage of a request.


Generated Narrative: ValueSet request-status This value set includes codes from the following code systems:

Last updated: 2025-11-10T15:17:08.817Z

 

This expansion generated 01 10 Nov 2019 2025


ValueSet

Expansion performed internally based on codesystem RequestStatus v6.0.0-ballot3 (CodeSystem)

This value set contains 7 8 concepts

Expansion based on http://hl7.org/fhir/request-status version 4.0.1 All codes from system
http://hl7.org/fhir/request-status Level System Code Display Definition Canonical Status Mapping for "RequestStatus"
1 http://hl7.org/fhir/request-status    draft Draft The request has been created but is not yet complete or ready for action. ~ draft
1 http://hl7.org/fhir/request-status    active Active The request is in force and ready to be acted upon. ~ active
1 http://hl7.org/fhir/request-status    on-hold On Hold The request (and any implicit authorization to act) has been temporarily withdrawn but is expected to resume in the future. ~ suspended
1 revoked http://hl7.org/fhir/request-status    entered-in-error Entered in Error This request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity has occurred, the status should be "revoked" rather than "entered-in-error".). ~ error
Revoked 1 http://hl7.org/fhir/request-status    ended The Ended This request (and any implicit authorization is no longer to act) be acted upon. This status does not differentiate what degree of action (if any) has already been terminated prior to the known full completion of undertaken against the intended actions. No further activity should occur. request. ~ failed ended
2 http://hl7.org/fhir/request-status      completed Completed The activity described by the request has been fully performed. No further activity will occur. ~ complete
2 entered-in-error http://hl7.org/fhir/request-status      revoked Entered in Error Revoked This The request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity (and any implicit authorization to act) has occurred, been terminated prior to the status known full completion of the intended actions. No further activity should be "revoked" rather than "entered-in-error".). occur. ~ error failed
1 http://hl7.org/fhir/request-status    unknown Unknown The authoring/source system does not know which of the status values currently applies for this request. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, but the authoring/source system does not know which. ~ unknown

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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