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
.
Page
versions:
R5
R4B
R4
R3
Responsible
Owner:
Orders
and
Observations
Work
Group
|
Trial Use |
Use
Context
:
|
Official
URL
:
http://hl7.org/fhir/ValueSet/task-status
|
|
|||
| draft as of 2020-12-28 |
|
|||
|
|
|
|||
This value set is used in the following places:
The current status of the task.
Generated Narrative: ValueSet task-status
Last updated: 2025-11-10T15:17:08.817Z
http://hl7.org/fhir/task-status
version
📦6.0.0-ballot3
This
expansion
generated
01
10
Nov
2019
2025
ValueSet
This
value
set
contains
12
concepts
Expansion
performed
internally
based
on
http://hl7.org/fhir/task-status
version
4.0.1
All
codes
from
system
http://hl7.org/fhir/task-status
codesystem
Task
Status
v6.0.0-ballot3
(CodeSystem)
This value set contains 12 concepts
| System | Code | Display | Definition |
Canonical
|
http://hl7.org/fhir/task-status
| draft | Draft | The task is not yet ready to be acted upon. | ~ draft |
http://hl7.org/fhir/task-status
| requested | Requested | The task is ready to be acted upon and action is sought. | ~ requested |
http://hl7.org/fhir/task-status
| received | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it. | ~ received |
http://hl7.org/fhir/task-status
| accepted | Accepted | The potential performer has agreed to execute the task but has not yet started work. | ~ accepted |
http://hl7.org/fhir/task-status
| rejected | Rejected | The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action. | ~ declined |
http://hl7.org/fhir/task-status
| ready | Ready | The 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. | ~ on-target |
http://hl7.org/fhir/task-status
| cancelled | Cancelled | The task was not completed. | ~ abandoned |
http://hl7.org/fhir/task-status
| in-progress | In Progress | The task has been started but is not yet complete. | ~ active |
http://hl7.org/fhir/task-status
| on-hold | On Hold | The task has been started but work has been paused. | ~ suspended |
http://hl7.org/fhir/task-status
| failed | Failed |
The
task
was
attempted
but
|
~ failed |
http://hl7.org/fhir/task-status
| completed | Completed | The task has been completed. | ~ complete |
http://hl7.org/fhir/task-status
| entered-in-error | Entered in Error | The task should never have existed and is retained only because of the possibility it may have used. | ~ error |
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 |