Stream: implementers
Topic: Dependent Relationships
Kenneth Chapple (May 03 2016 at 16:04):
Is there a method in the API to identify, link and unlink primary-to-dependent relationships?
Grahame Grieve (May 03 2016 at 16:44):
no. see the Vet / related person / person topic
Jon Clark (Jul 10 2020 at 18:54):
How are folks handling use cases where one person in a family (e.g. subscriber on a health plan) has access to the rest of the families data (e.g. dependents), since FHIR requests are usually in the context of a specific patient? During the login/authorization are you making the user pick the specific patient context for the scopes they are granting? (And thus requiring them to login in once per dependent.) Or are you handling the authorization on the server and in some way that is not a part of the JWT token at all?
Cooper Thompson (Jul 10 2020 at 19:40):
For patient-facing integrations, we (Epic) do require the user to pick the patient they want to access, and lock the scope to that patient. So yes, the user needs to log in and re-authorize the app once for each family member or dependent they want to access. The user-to-patient access rules are managed on our backend, and not directly expressed as FHIR relationships. You can infer the relationships through the SMART and OpenID information, but not directly via FHIR.
Last updated: Apr 12 2022 at 19:14 UTC
