Patient Cost Transparency Implementation Guide
2.0.1 - STU 2

Patient Cost Transparency Implementation Guide, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-pct/ and changes regularly. See the Directory of published versions

## ValueSet: Provider GFE Contributor Task Status Codes

Official URL: http://hl7.org/fhir/us/davinci-pct/ValueSet/PCTContributorTaskStatusCodes | Version: 2.0.1
Standards status: Trial-use | Maturity Level: 2 | Computable Name: PCTContributorTaskStatusCodes
Other Identifiers: OID:2.16.840.1.113883.4.642.40.4.48.11

Codes allowed for a GFE Contributor-specific service task status

References

- PCT GFE Contributor Task
- PCT GFE Contributor Task

Changes since version 1.1.0:

- New Content

### 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.
  rejected | Rejected | The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action.
  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 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` | rejected | Rejected | The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action. |  |
`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