Patient Cost Transparency Implementation Guide
2.0.0 - STU 2 United States of America flag

This page is part of the Da Vinci Patient Cost Transparency Implementation Guide (v2.0.0: STU 2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: GFE Coordination Task Status Codes

Official URL: http://hl7.org/fhir/us/davinci-pct/ValueSet/PCTCoordinationTaskStatusCodes Version: 2.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: PCTCoordinationTaskStatusCodes
Other Identifiers: OID:2.16.840.1.113883.4.642.40.4.48.13

Codes allowed for a GFE Coordination Task status

References

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
      CodeDisplayDefinition
      draftDraftThe task is not yet ready to be acted upon.
      requestedRequestedThe task is ready to be acted upon and action is sought.
      in-progressIn ProgressThe task has been started but is not yet complete.
      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.
      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

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

    This value set contains 9 concepts

    CodeSystemDisplayDefinition
      drafthttp://hl7.org/fhir/task-statusDraftThe task is not yet ready to be acted upon.
      requestedhttp://hl7.org/fhir/task-statusRequestedThe task is ready to be acted upon and action is sought.
      in-progresshttp://hl7.org/fhir/task-statusIn ProgressThe task has been started but is not yet complete.
      readyhttp://hl7.org/fhir/task-statusReadyThe 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-statusCancelledThe task was not completed.
      on-holdhttp://hl7.org/fhir/task-statusOn HoldThe task has been started but work has been paused.
      failedhttp://hl7.org/fhir/task-statusFailedThe task was attempted but could not be completed due to some error.
      completedhttp://hl7.org/fhir/task-statusCompletedThe task has been completed.
      entered-in-errorhttp://hl7.org/fhir/task-statusEntered in ErrorThe 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