QI-Core Implementation Guide
7.0.0 - STU7 United States of America flag

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.0 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: Non-Negative Task Status

Official URL: http://hl7.org/fhir/us/qicore/ValueSet/qicore-non-negative-task-status Version: 7.0.0
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

Logical Definition (CLD)

Generated Narrative: ValueSet qicore-non-negative-task-status

  • Include these codes as defined in http://hl7.org/fhir/task-status
    CodeDisplayDefinition
    draftDraftThe task is not yet ready to be acted upon.
    requestedRequestedThe task is ready to be acted upon and action is sought.
    receivedReceivedA potential performer has claimed ownership of the task and is evaluating whether to perform it.
    acceptedAcceptedThe potential performer has agreed to execute the task but has not yet started work.
    readyReadyThe 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.
    cancelledCancelledThe task was not completed.
    in-progressIn ProgressThe task has been started but is not yet complete.
    on-holdOn HoldThe task has been started but work has been paused.
    failedFailedThe task was attempted but could not be completed due to some error.
    completedCompletedThe task has been completed.
    entered-in-errorEntered In ErrorThe task should never have existed and is retained only because of the possibility it may have used.

 

Expansion

Generated Narrative: ValueSet

Expansion based on codesystem TaskStatus v4.0.1 (CodeSystem)

This value set contains 11 concepts

CodeSystemDisplayDefinition
  drafthttp://hl7.org/fhir/task-statusDraft

The task is not yet ready to be acted upon.

  requestedhttp://hl7.org/fhir/task-statusRequested

The task is ready to be acted upon and action is sought.

  receivedhttp://hl7.org/fhir/task-statusReceived

A potential performer has claimed ownership of the task and is evaluating whether to perform it.

  acceptedhttp://hl7.org/fhir/task-statusAccepted

The potential performer has agreed to execute the task but has not yet started work.

  readyhttp://hl7.org/fhir/task-statusReady

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.

  cancelledhttp://hl7.org/fhir/task-statusCancelled

The task was not completed.

  in-progresshttp://hl7.org/fhir/task-statusIn Progress

The task has been started but is not yet complete.

  on-holdhttp://hl7.org/fhir/task-statusOn Hold

The task has been started but work has been paused.

  failedhttp://hl7.org/fhir/task-statusFailed

The task was attempted but could not be completed due to some error.

  completedhttp://hl7.org/fhir/task-statusCompleted

The task has been completed.

  entered-in-errorhttp://hl7.org/fhir/task-statusEntered 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