When a task is complete what triggers the termination of a payer's ability to fetch data?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US Da Vinci CDex (FHIR)
    • current
    • Patient Care
    • Specification [deprecated]
    • 8.3.5
    • Hide

      The default assumption is that task and the data referenced from it is indefinitely accessible.

      But the authorization layer can set the timeframe to the Task and any resource the Task may reference.

      Will add guidance to say that per business rules ( and are other constraints such as those based on privacy law on time limits to data access) to say the data source may limit the time the Task and the data referenced from are accessible.  It is up to the responder to determine how long they wish to provide access to the request.

      Show
      The default assumption is that task and the data referenced from it is indefinitely accessible. But the authorization layer can set the timeframe to the Task and any resource the Task may reference. Will add guidance to say that per business rules ( and are other constraints such as those based on privacy law on time limits to data access) to say the data source may limit the time the Task and the data referenced from are accessible.  It is up to the responder to determine how long they wish to provide access to the request.
    • Clarification
    • Non-substantive
    • Yes

      When a task is complete what triggers the termination of a payer's ability to fetch data?

      Existing Wording:

      When the task is complete, the Payer fetches the data of interest which is referenced by Task.output.

      (Comment 10 - imported by: Jean Duteau)

            Assignee:
            Unassigned
            Reporter:
            Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: