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

Tighter specification around the updating of Task fields by Patient.

    XMLWordPrintableJSON

Details

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

      We are adding On-Hold as an additional status.  State diagrams will be provided for both the referral and patient tasks.  Additional guidance will indicate which elements a patient's application may change (status, output).

      Show
      We are adding On-Hold as an additional status.  State diagrams will be provided for both the referral and patient tasks.  Additional guidance will indicate which elements a patient's application may change (status, output).
    • Bob Dieterle / Jay Lyle : 7-0-0
    • Clarification
    • Non-substantive

    Description

      Definition says: These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. The values are constrained to ready | cancelled | completed because the task come to the patient in the ready status and the patient can cancel it or complete it.

      So this seems to imply that it would not be OK for a Patient app to update Task without changing the status and that the only status changes allowed are Ready to Cancelled or Ready to Complete.  Perhaps invariants would help here to make this more clear and a state machine.  

       

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: