Stream: implementers
Topic: Linking user to patient and/or practitioner record
santiago gil (Oct 08 2018 at 17:44):
Hello there guys, I wanted to know if anyone here has experience linking a user to a patient or a practitioner. For example, when User1 logs in he is linked to a patient and all of his records.
nicola (RIO/SS) (Oct 10 2018 at 20:01):
This question is out of specification scope and upto implementers. In aidbox we provide FHIR-like custom resource User, which can be linked to Patient or Practitioner or both. And we used a lot in our apps. Im working on post about this, which is scheduled for next week.
Grahame Grieve (Oct 10 2018 at 20:02):
we say no to a User resource about once a year ;-). Have you looked at SCIM?
Grahame Grieve (Oct 10 2018 at 20:07):
I use SCIM with a custom SCIM extension to link user to patient or practitioner
Michele Mottini (Oct 10 2018 at 21:15):
We are using Person for that - we map it from our internal users, with links to Patient or Practitioner as appropriate
Lloyd McKenzie (Oct 10 2018 at 22:34):
The issue with that is that Person can't be an actor - it can't have responsibility, can't be pointed to as an author, performer, target or anything else. Person's sole purpose is to maintain a shared set of demographics and identity across all of the other demographic resources.
John Moehrke (Oct 11 2018 at 17:49):
What kind of an Actor is needed that is beyond the list of Actor types we have today? Thus user identity, as managed by a User Identity Management system (like SCIM) is a good Identifier element in Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson)
Christiaan Knaap (Oct 21 2018 at 15:46):
Vonk allows you to give it a SMART on FHIR 'patient' claim in the OIDC token. Internally that translates to a patient compartment that the user will be confined to.
Grahame Grieve (Oct 22 2018 at 10:10):
what's the syntax for that?
John Moehrke (Oct 22 2018 at 13:39):
@Christiaan Knaap is that simply using SMART-on-FHIR patient launch context parameter? http://docs.smarthealthit.org/authorization/scopes-and-launch-context/
John Moehrke (Oct 22 2018 at 13:44):
I would expect the Resource Server within the agent kind of Resources (Patient, Practitioner, etc) to have a .identifier that is mapped authoritatively to the OIDC identity. Mapping the other way puts too much reliance on well-behaved OIDC authorities, that are typically not healthcare specific. Thus I would expect a search within the Resource Server (or some federated id authority) for those agent kind of Resources that have the OIDC identity.
Christiaan Knaap (Oct 29 2018 at 12:18):
@Christiaan Knaap is that simply using SMART-on-FHIR patient launch context parameter? http://docs.smarthealthit.org/authorization/scopes-and-launch-context/
Yes indeed. Only extra we provide is that the contents of the claim can be a more complex filter on patient than just its 'id'. Details are in the documentation.
Last updated: Apr 12 2022 at 19:14 UTC
