2015May core #974 - Add security guidance for 'read'

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • REST (http)
    • Hide

      Propose Reject: The core specification should not define 'best practice' policy. Policy is out-of-scope.

      Show
      Propose Reject: The core specification should not define 'best practice' policy. Policy is out-of-scope.
    • James Agnew / Grahame Grieve: 4-0-0
    • Enhancement

      Existing Wording: Add something like: ".Only authorized systems/user (those that meet the access control including "Consent" directives) will be allowed to "read" the resource.

      Proposed Wording: This operation needs additional explicit caveats to avoid this authorized unauthorized "read".

      Comment:

      We need to explain precisely how the security guidance should be applied to this *specific" operation including the use of Consent and Provenance to make access control decisions. (http://hl7.org/fhir/2015May/security.html) including consent to make sure only authorized systems an users are viewing, changing, updating, or reviewing the update history of a resource.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: