Task.status examples don't match with value set

XMLWordPrintableJSON

    • Type: Technical Correction
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • 0.2.0 [deprecated]
    • Clinical Interoperability Council
    • HRex Task Data Request Profile
      HRex Task Status ValueSet
    • Exchanges allowing human intervention [deprecated]
    • Hide

      Will correct to align with statuses in the value set and will add on-hold to the value set

      Show
      Will correct to align with statuses in the value set and will add on-hold to the value set
    • Correction

      The exchanging with human intervention page (Sections 3.7.1.4 and 3.7.2) list some Task.status values - eg:

      Step 2: The data source may optionally update the Task to change the status (e.g. from requested to accepted or refused and eventually to in-progress or on-hold. 

       

      However, the profile on Task requires that .status use a value set that doesn't include several of these statuses (eg refused (there is a rejected status) and on-hold). The example text should probably be cleaned up (assuming the value set is correct).

       

      Code Display
      requested Requested The task is ready to be acted upon and action is sought.
      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.
      in-progress In Progress The task has been started but is not yet complete.
      failed Failed The task was attempted but could not be completed due to some error.
      completed Completed The task has been completed.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: