2026 US Quality Core Implementation Guide
0.5.0 - cibuild US

2026 US Quality Core Implementation Guide, published by Office of the National Coordinator for Health Information Technology (ONC). This guide is not an authorized publication; it is the continuous build for version 0.5.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/FHIR/us-quality-core/ and changes regularly. See the Directory of published versions

## ValueSet: Non-Negative Task Status

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-05-15 | 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

- US Quality Core Task

### Logical Definition (CLD)

- Include these codes as defined in `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

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

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