Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions Value Set

Orders and Observations Work Group Maturity Level: 2Trial Use Use Context: Any

This is a value set defined by the FHIR project.


Defining URL:

The current status of the task.

Committee:Orders and Observations Work Group
OID:2.16.840.1.113883.4.642.3.790 (for OID based terminology systems)
Source Resource:XML / JSON

This value set is used in the following places:


This expansion generated 13 Aug 2022

This value set contains 12 concepts

Expansion based on TaskStatus v5.0.0-cibuild (CodeSystem)

All codes in this table are from the system

  draftDraftThe task is not yet ready to be acted upon.
  requestedRequestedThe task is ready to be acted upon and action is sought.
  receivedReceivedA potential performer has claimed ownership of the task and is evaluating whether to perform it.
  acceptedAcceptedThe potential performer has agreed to execute the task but has not yet started work.
  rejectedRejectedThe potential performer who claimed ownership of the task has decided not to execute it prior to performing any action.
  readyReadyThe task is ready to be performed, but no action has yet been taken. Used in place of requested/received/accepted/rejected when request assignment and acceptance is a given.
  cancelledCancelledThe task was not completed.
  in-progressIn ProgressThe task has been started but is not yet complete.
  on-holdOn HoldThe task has been started but work has been paused.
  failedFailedThe task was attempted but could not be completed due to some error.
  completedCompletedThe task has been completed.
  entered-in-errorEntered in ErrorThe task should never have existed and is retained only because of the possibility it may have used.


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

Explanation of the columns that may appear on this page:

LvlA 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
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