Task and Procedure resources completely overlap - need clarifying descriptions

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • Procedure
      Task
    • Hide

      See Corresponding Tracker GF#19109 for Task

      Add to Boundaries Section the following: 'A Task is a workflow step such as cancelling an order, fulfilling an order, signing an order, merging a set of records, admitting a patient. Procedures are actions that are intended to result in a physical or mental change to or for the subject (e.g. surgery, physiotherapy, training, counseling). A Task resource often exists in parallel with clinical resources. For example, a Task might request fulfillment of a ServiceRequest ordering a Procedure'

      Show
      See Corresponding Tracker GF# 19109 for Task Add to Boundaries Section the following: 'A Task is a workflow step such as cancelling an order, fulfilling an order, signing an order, merging a set of records, admitting a patient. Procedures are actions that are intended to result in a physical or mental change to or for the subject (e.g. surgery, physiotherapy, training, counseling). A Task resource often exists in parallel with clinical resources. For example, a Task might request fulfillment of a ServiceRequest ordering a Procedure'
    • Michael/Danielle: 18-0-0
    • Clarification
    • Non-substantive
    • STU3

      The current FHIR resources for Task and for Procedure seem to completely overlap. Clarifying guidance is needed to direct usage consistently.

      Task - "A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity." (http://build.fhir.org/task.html)

      Procedure - "This resource is used to record the details of current and historical procedures performed on a patient. A procedure is an activity that is performed with or on a patient as part of the provision of care. Examples include surgical procedures, diagnostic procedures, endoscopic procedures, biopsies, counseling, physiotherapy, exercise, etc. Procedures may be performed by a healthcare professional, a friend or relative or in some cases by the patient themselves." (http://build.fhir.org/procedure.html)

      Thus - a Task might be a Procedure, and a Procedure might be a Task. In which scenarios should each be used? If they are completely interchangeable, the resulting confusion will be problematic. Note that Task includes the ability to request and to perform a task. Procedure requires use of ServiceRequest to propose, plan or order it.

      Please clarify.

            Assignee:
            Unassigned
            Reporter:
            Floyd Eisenberg
            Floyd Eisenberg
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: