Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-30148

Failed task or task without result?

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive with Modification
    • Medium
    • US Da Vinci CDex (FHIR)
    • 0.2.0 [deprecated]
    • Patient Care
    • CDex Task Data Request Profile
    • 10.13.1
    • Hide

      Background:  Task status:  http://hl7.org/fhir/valueset-task-status.html#expansion

      See the Task state machine: http://hl7.org/fhir/task.html#statemachine

       

       

      The task in this case could not be completed because there was no data.    i.e. Failed is a terminal state, but it's definitely not 'complete',    FHIR-29559  seeks to clarify the definition of 'falied' to ""The task was attempted but not successful. No further activity will occur."

       

      Either in CDEX or HREX will add a section discussing the Failed vs completed states to clarify and proviide conformance language to the effect that there SHOULD be reason stated in Task.statusReaon  as to why this task is held, failed, or refused.

       

      Regarding next steps for the Client.  That is an implementation specific business rule  (ie a phone call) and is considered self-evident and out of scope. 

      Show
      Background:  Task status:  http://hl7.org/fhir/valueset-task-status.html#expansion See the Task state machine: http://hl7.org/fhir/task.html#statemachine     The task in this case could not be completed because there was no data.    i.e. Failed is a terminal state, but it's definitely not 'complete',    FHIR-29559   seeks to clarify the definition of 'falied' to ""The task was attempted but not successful. No further activity will occur."   Either in CDEX or HREX will add a section discussing the Failed vs completed states to clarify and proviide conformance language to the effect that there SHOULD be reason stated in Task.statusReaon  as to why this task is held, failed, or refused.   Regarding next steps for the Client.  That is an implementation specific business rule  (ie a phone call) and is considered self-evident and out of scope. 
    • Eric Haas/Jay Lyle : 9-0-5
    • Clarification
    • Non-substantive

    Description

      The example "Failed Task" indicates there is no result. Is this actually a failed task or a successful task finding no result? The distinction is important as with any interoperability task there are successful requests and responses (I.e., find something, "something" doesn't exist) Versus "Unable to process the request to determine if there is information." The latter suggest some mitigation might improve similar events in the future or at least fix the reason for the inability to process and successfully send the information. This distinction is sufficient enough that the word "failed" seems misplaced here - or at best it is ambiguous.  Guidance would also be helpful to determine how to handle such "failures."

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              feisenberg Floyd Eisenberg
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: