2026 US Quality Core Implementation Guide
0.5.0 - release
2026 US Quality Core Implementation Guide
0.5.0 - release
2026 US Quality Core Implementation Guide - Downloaded Version 0.5.0 See the Directory of published versions
| Official URL: http://fhir.org/guides/onc/us-quality-core/ValueSet/us-quality-core-non-negative-task-status | Version: 0.5.0 | ||||
| Active as of 2026-06-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)
References
http://hl7.org/fhir/task-status version 📦4.0.1| 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. |
Expansion performed internally based on codesystem TaskStatus v4.0.1 (CodeSystem)
This value set contains 11 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://hl7.org/fhir/task-status | draft | Draft | The task is not yet ready to be acted upon. | ||
http://hl7.org/fhir/task-status | requested | Requested | The task is ready to be acted upon and action is sought. | ||
http://hl7.org/fhir/task-status | received | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it. | ||
http://hl7.org/fhir/task-status | accepted | Accepted | The potential performer has agreed to execute the task but has not yet started work. | ||
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. | ||
http://hl7.org/fhir/task-status | cancelled | Cancelled | The task was not completed. | ||
http://hl7.org/fhir/task-status | in-progress | In Progress | The task has been started but is not yet complete. | ||
http://hl7.org/fhir/task-status | on-hold | On Hold | The task has been started but work has been paused. | ||
http://hl7.org/fhir/task-status | failed | Failed | The task was attempted but could not be completed due to some error. | ||
http://hl7.org/fhir/task-status | completed | Completed | The task has been completed. | ||
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. |