Stream: smart
Topic: Standalone Launch scope
Sagar Shah (Oct 20 2020 at 20:34):
image.png
Reference: http://hl7.org/fhir/smart-app-launch/index.html#smart-authorization-sequence
I see that for standalone launch sequence, the scope is passed as "launch" from the app. Should that be launch/encounter or launch/patient instead?
Michele Mottini (Oct 20 2020 at 20:51):
Yes, that looks wrong
Sagar Shah (Oct 21 2020 at 12:14):
Thanks. Wanted to make sure my understandings are correct!
Michele Mottini (Oct 21 2020 at 13:56):
I created an issue: https://github.com/HL7/smart-app-launch/issues/316
Sagar Shah (Oct 21 2020 at 14:18):
Thank you @Michele Mottini for creating a ticket
Josh Mandel (Oct 21 2020 at 17:25):
We define the launch scope at http://hl7.org/fhir/smart-app-launch/scopes-and-launch-context/index.html#quick-start -- it's how an app tells the EHR "I want to request access to launch context information"
Josh Mandel (Oct 21 2020 at 17:26):
It can be used in conjunction with more specific scopes, but in the EHR Launch it doesn't need to be... EHR can decide what to include, if launch scope is granted.
Sagar Shah (Oct 21 2020 at 17:32):
Correct, but for standalone launch (when App does not have any patient context), would/can it pass launch as scope to Auth server OR should it be passing launch/patient to indicate that it requires patient context to function correctly? I agree with the documentation available here at http://hl7.org/fhir/smart-app-launch/scopes-and-launch-context/index.html#quick-start. But the diagram on the other page (posted in my first message to this thread) seemed conflicting to me as it showed an example with "launch" as scope instead of launch/patient.
Josh Mandel (Oct 21 2020 at 18:11):
Agreed this doesn't make sense for standalone launch. Good point! This example would be better with launch/patient.
Last updated: Apr 12 2022 at 19:14 UTC
