Shared Care Planning (SCP) Implementation Guide
0.3.0 - ci-build

Shared Care Planning (SCP) Implementation Guide - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: Shared Care Planning: Task Status

Official URL: http://santeonnl.github.io/shared-care-planning/ValueSet/scp-task-status Version: 0.3.0
Active as of 2025-04-01 Computable Name: SCPTaskStatus

References

Logical Definition (CLD)

Generated Narrative: ValueSet scp-task-status

This value set includes codes based on the following rules:

  • Import all the codes that are contained in TaskStatus

This value set excludes codes based on the following rules:

 

Expansion

ValueSet

This value set contains 11 concepts

CodeSystemDisplay (en-US)Definition
  requestedhttp://hl7.org/fhir/task-status

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

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

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

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

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

  rejectedhttp://hl7.org/fhir/task-status

The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action.

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

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

The task was not completed.

  in-progresshttp://hl7.org/fhir/task-status

The task has been started but is not yet complete.

  on-holdhttp://hl7.org/fhir/task-status

The task has been started but work has been paused.

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

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

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

The task has been completed.

  entered-in-errorhttp://hl7.org/fhir/task-status

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