SMART on FHIR app provider flow with Multiple entry points

[Jeremy Klein]

We are developing a SMART on FHIR app web application that will leverage the provider app flow. Depending on which link in the EHR that the provider clicks, we would like to display a specific a different route within the app. I was looking for the best way to implement this. Any suggestions would be greatly appreciated!

Jeremy

[Josh Mandel]

Your EHR may support the configuration of an "intent" launch parameter (see http://hl7.org/fhir/smart-app-launch/scopes-and-launch-context/index.html#launch-context-arrives-with-your-access_token) that varies based on which launch link is clicked. It may also support the addition of arbitrary URL parameters to your initial launch request

As a fallback,cyou could register multiple copies of your app, each associated with the different launch on point.

If you can, let us know how this works out!

On Mon, Jun 14, 2021, 21:42 Jeremy Klein <jeremy.jo...@gmail.com> wrote:

We are developing a SMART on FHIR app web application that will leverage the provider app flow. Depending on which link in the EHR that the provider clicks, we would like to display a specific a different route within the app. I was looking for the best way to implement this. Any suggestions would be greatly appreciated!

Jeremy

--
You received this message because you are subscribed to the Google Groups "SMART on FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to smart-on-fhi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/smart-on-fhir/95ab3fd8-459f-4802-97a0-1c4966de2d9bn%40googlegroups.com.

[Jeremy Klein]

Thanks Josh!

I'll follow up with the EHR vendor(Epic) and see if they have something implemented for this use case. 

My concern with creating separate apps for each client is that we would need to configure app specific configuration (i.e scopes etc.) in multiple places and keep them in sync. Additionally we are trying to figure out if different EHR vendors will have different costs associated with the number of apps you have created.

We are thinking about setting a slightly different path for the launch of each page. For example, www.example.com/path/to/launch/page1/launch.html www.example.com/path/to/launch/page2/launch.html. the app will save the path in local storage and then after redirect route to the appropriate component. Do you have any thoughts on this approach?

Jeremy

[Josh Mandel]

Sure thing, Jeremy! If Epic supports independent that scheme (independent launch URLs for a given app, depending on where it's launched from) that'd work well.

To view this discussion on the web visit https://groups.google.com/d/msgid/smart-on-fhir/36ef00ab-43dc-4f37-a9ec-eba57438ffa2n%40googlegroups.com.