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

Patient scope and linked patients

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • STU
    • App Launch: Scopes and Launch Context
    • 2.2.8
    • Hide

      (Today the FHIR clinical safety checklist says "My system ensures checks for patient links (and/or merges) and handles data that is linked to patients accordingly". There's not a lot of specific direction.)

      Update the spec to say: if a FHIR server supports replacing one Patient record with another via Patient.link, the server documentation SHALL describe its authorization behavior. 

       

      (Note from FHIR-I discussion:  we identified several possibilities but didn't feel comfortable adding them to the spec, for lack of experience. For example, a server might grant access to Patients whenever a "replaced-by" or "replaces" link is present; or a server might automatically re-interpret queries about a "replaced-by" patient to treat them as queries about the "replaces" patient; or a server might require that a client re-authorize with user-level scopes.)

       

      Show
      (Today the FHIR clinical safety checklist says "My system ensures checks for patient links (and/or merges) and handles data that is linked to patients accordingly". There's not a lot of specific direction.) Update the spec to say: if a FHIR server supports replacing one Patient record with another via Patient.link, the server documentation SHALL describe its authorization behavior.    (Note from FHIR-I discussion:  we identified several possibilities but didn't feel comfortable adding them to the spec, for lack of experience. For example, a server might grant access to Patients whenever a "replaced-by" or "replaces" link is present; or a server might automatically re-interpret queries about a "replaced-by" patient to treat them as queries about the "replaces" patient; or a server might require that a client re-authorize with user-level scopes.)  
    • Alexander Zautke / Dan Gottlieb: 8-0-0
    • Clarification
    • Non-substantive

    Description

      How do we deal with linked patients? Where another patient resource is marked as being the same as the current one? Is this accessible or not? 

      If not, does this require user scopes? That might be a little to much.

       

      Attachments

        Activity

          People

            carl-anderson-msft Carl Anderson (Inactive)
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: