This
page
is
part
of
the
FHIR
Specification
(v5.0.0:
R5
-
STU
v6.0.0-ballot1:
Release
6
Ballot
(1st
Draft)
(see
Ballot
Notes
).
This
is
the
The
current
published
version
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
Orders
and
Observations
Work
Group
|
Maturity Level : 3 | Trial Use | Use Context : Country: World |
Official
URL
:
http://hl7.org/fhir/ValueSet/task-status
|
Version
:
|
|||
| draft as of 2020-12-28 | Computable Name : TaskStatus | |||
| Flags : Immutable | OID : 2.16.840.1.113883.4.642.3.790 | |||
This value set is used in the following places:
The current status of the task.
http://hl7.org/fhir/task-status
This
expansion
generated
26
Mar
18
Dec
2023
Expansion
based
on
codesystem
Task
Status
v5.0.0
v6.0.0-ballot1
(CodeSystem)
This value set contains 12 concepts
| Code | System | Display | Definition | Canonical Mapping for "Task Status" |
| draft | http://hl7.org/fhir/task-status | Draft |
The task is not yet ready to be acted upon. |
~ draft |
| requested | http://hl7.org/fhir/task-status | Requested |
The task is ready to be acted upon and action is sought. |
~ requested |
| received | http://hl7.org/fhir/task-status | Received |
A potential performer has claimed ownership of the task and is evaluating whether to perform it. |
~ received |
| accepted | http://hl7.org/fhir/task-status | Accepted |
The potential performer has agreed to execute the task but has not yet started work. |
~ accepted |
| rejected | http://hl7.org/fhir/task-status | Rejected |
The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action. |
~ declined |
| ready | http://hl7.org/fhir/task-status | 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 |
| cancelled | http://hl7.org/fhir/task-status | Cancelled |
The task was not completed. |
~ abandoned |
| in-progress | http://hl7.org/fhir/task-status | In Progress |
The task has been started but is not yet complete. |
~ active |
| on-hold | http://hl7.org/fhir/task-status | On Hold |
The task has been started but work has been paused. |
~ suspended |
| failed | http://hl7.org/fhir/task-status | Failed |
The task was attempted but could not be completed due to some error. |
~ failed |
| completed | http://hl7.org/fhir/task-status | Completed |
The task has been completed. |
~ complete |
| entered-in-error | http://hl7.org/fhir/task-status | 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 |