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

Be clear on what the patient can change in Task

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US SDOH Clinical Care (FHIR)
    • 1.0.0
    • Patient Care
    • STU
    • SDOHCC Task For Patient
    • 19.16.5
    • Hide

      Add guidance on patient application's that the ability to update the patient task is limited to .Status, .StatusReason, .Output (any of the slices). All other actions are not within the scope of this IG.

      Show
      Add guidance on patient application's that the ability to update the patient task is limited to .Status, .StatusReason, .Output (any of the slices). All other actions are not within the scope of this IG.
    • Bob Dieterle / Jay Lyle : 7-0-0
    • Clarification
    • Non-substantive

    Description

      If the patient updates the Task, it seems there must be certain fields that should not be changed, like code, description, authored, owner, input, etc. because changing those fields would change the definition of the Task.   Suggest invariants or other method to make that clear.  An operation to update Task would even be safer.  Patient app implementers and EHR vendor implementers need more specific guidance.  

      Attachments

        Activity

          People

            Unassigned Unassigned
            vlorenzi Virginia Lorenzi
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: