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

Suggest more robust requirements around using Task for patient communications

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US SDOH Clinical Care (FHIR)
    • 1.0.0
    • Patient Care
    • STU
    • SDOHCC Patient Application
    • 19.2.4.1
    • Hide

      Review Actor Capability statements with regard to use of Patient and Referral Task  Will clarify the actors that may update each task and the element that may be updated.

      Cannot change to an operation since the patient/CBO may be using an application and cannot support a FHIR operation.

      Show
      Review Actor Capability statements with regard to use of Patient and Referral Task  Will clarify the actors that may update each task and the element that may be updated. Cannot change to an operation since the patient/CBO may be using an application and cannot support a FHIR operation.
    • Bob Dieterle / Jay Lyle : 7-0-0
    • Correction
    • Compatible, substantive

    Description

      The capability statement for patient says that the referral mgmt task is supported and the patient task is supported.  Both should support version queries since version is important in task mgmt.  Also, it seems that the referrer, the patient, and the recipient, as well as an intermediary can update the Task.  I am concerned that the Task overall definition will be overridden when the main purpose of the Task update function is to update only fields related to the state transition and not the definition of the Task itself.  An operation seems safer.  

      Attachments

        Activity

          People

            lloyd Lloyd McKenzie
            vlorenzi Virginia Lorenzi
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: