QI-Core Implementation Guide
7.0.2 - STU 7

QI-Core Implementation Guide, published by HL7 International / Clinical Quality Information. This guide is not an authorized publication; it is the continuous build for version 7.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-qi-core/ and changes regularly. See the Directory of published versions

## ValueSet: Positive Task Status

Official URL: http://hl7.org/fhir/us/qicore/ValueSet/qicore-positive-task-status | Version: 7.0.2
Standards status: Trial-use | Maturity Level: 4 | Computable Name: PositiveTaskStatus

This value set defines the set of codes that indicate a positive task status

This value set was defined to support the set of task statuses in FHIR that indicate a positive status.

References

- QICore Task Done

### 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.
  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.
  completed | Completed | The task has been completed.

### Expansion

Expansion performed internally based on codesystem TaskStatus v4.0.1 (CodeSystem)

This value set contains 8 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` | 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` | completed | Completed | The task has been completed. |  |

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