Confusion about Task status and target status - 2016-09 core #589

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • Workflow
    • 12.1.2.12.3
    • Hide

      Will add "cancelled" as a status for Task with the definition "The request for action has been withdrawn prior to commencement of activity."

      "Cancelled" would generally be a terminal state. The originally requested action could still be completed and still attached to the Task but this would not change the status of the task. If the placer cancels a task, it signals they no longer care about the outcome of the task. Will add documentation clarifying this scenario.

      Show
      Will add "cancelled" as a status for Task with the definition "The request for action has been withdrawn prior to commencement of activity." "Cancelled" would generally be a terminal state. The originally requested action could still be completed and still attached to the Task but this would not change the status of the task. If the placer cancels a task, it signals they no longer care about the outcome of the task. Will add documentation clarifying this scenario.
    • Grahame Grieve/Josh Mandel: 7-0-0
    • Clarification
    • Compatible, substantive
    • DSTU2

      Existing Wording: Placer sends an update to the Task setting the status to "cancelled"

      Comment:

      Is there confounding here between the action to be performed, the "cancel" and the status of that action? What does the fullfiller of that cancellation do upon completion, mark the status as "complete"? How then does the Placer know the Task has been completed and/or the action which was undertaken/intended?

      Also, there is no code "cancelled" in the required valueset.

      Summary:

      Confusion about Task status and target status

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: