Not requesting launch/patient scope about cardiac-risk-app

[jmandel]

Technically this should request at least the launch scope, if not also launch/patient. We document launch/patient as a requirement in our Standalone launch flow. Since this app uses the EHR launch flow, it doesn't specifically need to request launch/patient, but I think it's still a good practice to be explicit.

[burcakulug]

Thank you for the quick response. On the platform side, can you assume that if the app requests any patient/* kind of scope, the platform should provide or let the user to pick a patient context?

[vlad-ignatov]

In fact, when launched from an EHR (when iss and launch parameters are passed to the launch.html) the fhirclient library will automatically add launch to the requested scopes if it is missing. If that library was not used, then you are correct that lauch scope should be added.