This page is part of the Quality Improvement Core Framework (v6.0.0-ballot: STU6 (v6.0.0) Ballot 1) based on FHIR R4. The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/qicore/ValueSet/qicore-non-negative-task-status | Version: 6.0.0-ballot | |||
Active as of 2018-12-05 | Computable Name: NonNegativeTaskStatus |
This value set defines the set of codes that indicate a non-negated task status (i.e. codes that are not rejected
)
This value set was defined to support the set of task statuses in FHIR that do not explicitly indicate a negative status (i.e. all the codes from the http://hl7.org/fhir/task-status code system that are not rejected
).
References
http://hl7.org/fhir/task-status
Code | Display | Definition |
draft | Draft | The task is not yet ready to be acted upon. |
requested | Requested | The task is ready to be acted upon and action is sought. |
received | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it. |
accepted | Accepted | The potential performer has agreed to execute the task but has not yet started work. |
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. |
cancelled | Cancelled | The task was not completed. |
in-progress | In Progress | The task has been started but is not yet complete. |
on-hold | On Hold | The task has been started but work has been paused. |
failed | Failed | The task was attempted but could not be completed due to some error. |
completed | Completed | The task has been completed. |
entered-in-error | Entered In Error | The task should never have existed and is retained only because of the possibility it may have used. |
This value set contains 11 concepts
Expansion based on TaskStatus v4.0.1 (CodeSystem)
Code | System | Display | Definition |
draft | http://hl7.org/fhir/task-status | Draft | The task is not yet ready to be acted upon. |
requested | http://hl7.org/fhir/task-status | Requested | The task is ready to be acted upon and action is sought. |
received | http://hl7.org/fhir/task-status | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it. |
accepted | http://hl7.org/fhir/task-status | Accepted | The potential performer has agreed to execute the task but has not yet started work. |
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. |
cancelled | http://hl7.org/fhir/task-status | Cancelled | The task was not completed. |
in-progress | http://hl7.org/fhir/task-status | In Progress | The task has been started but is not yet complete. |
on-hold | http://hl7.org/fhir/task-status | On Hold | The task has been started but work has been paused. |
failed | http://hl7.org/fhir/task-status | Failed | The task was attempted but could not be completed due to some error. |
completed | http://hl7.org/fhir/task-status | Completed | The task has been completed. |
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. |
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. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |