Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fhirContext setting during Smart App launch #1077

Open
dattachandan opened this issue Dec 11, 2024 · 2 comments
Open

fhirContext setting during Smart App launch #1077

dattachandan opened this issue Dec 11, 2024 · 2 comments

Comments

@dattachandan
Copy link

Hi Sean,

Thanks for the sample app embedded in the demo EMR. Especially the EMR patient and provider context launch.

Do you know if the fhirContext in the AU context is being set with the Practitioner and Organisation in addition to the Patient and Encounter?

Happy to discuss more at the Connectathon.

image

image

@adha-admin
Copy link

I am keen to get some adoption/agreement on how we can set these contexts in stone, so that we just start building a library of supported fhirContexts

https://confluence.hl7.org/display/FHIRI/fhirContext+Role+Registry

Cheers
Philip Wilford
ADHA

@fongsean
Copy link
Collaborator

Hi @dattachandan,

Generally the user is retrieved from the id_token. See here for a sample id_token in jwt.io.

ThefhirUser value tells you what the user resource is. In this case, its a Practitioner with resource ID pharmacist.

If you want to pass an Organization through, you might want to use PractitionerRole as the user. From there, you can access both the Practitioner and the Organization resources.

Smart Forms as of now is a bit limited as it expects the user to be a Practitioner, so it might not work when you pass a PractitionerRole as the user. But in theory you can code a SMART app to accept any resource to be the user e.g. Practitioner, PractitionerRole, Person, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants