Stream: implementers
Topic: Smart on fhir
Espen Løke (May 16 2019 at 11:47):
Web based EPR, I need a reccomendation. We are implementing a Smart-on-Fhir portal and are looking at different possibilities of hosting a SmartApp. There are several restrictions e.g. when the EPR changes patient or the EPR initiates an auto logout all SmartApp's must be closed down. As we see it we har 3 options:
1. iFrame. We regard this as giving the best UI experience. Security and dynamic height of the iFrame if the SmartApp changes it's height dynamicly?
2. Open in new pane, do we have control in JavaScript of that page (closing it from the EPR)? E.g. change patient or user closes the EPR pane with the mouse?
3. Open in a new webbrowser instance.
Thoughts and how have other web based EPR vendors done this? Would be simpler in a Windows application where the smartapp could be hosted in child windows of the EPR running its ovn browser instance.
Josh Mandel (May 16 2019 at 14:07):
We've seen integrations with web-based EHRs using (1) and (2 -- assuming by "pane" you mean a new tab/window). Opening a new browser instance (as opposed to a new window) is usually outside of a web app's control. In general, my experience has been that it's no harder to integrate SMART apps with a web-based EHR vs a windows desktop-based EHR (and if anything, a bit easier).
Espen Løke (May 20 2019 at 10:29):
Thanks.
As part of the launch prosess SmartApp's authorize using the OAuth authorization code flow. Somehow the app needs to get the id_token of the user logged on to the EHR. In our case the EHR stores context information, like the current patient, in an internal table. The smart app gets this info during launch as part of the access token. However, how do we do this with the id_token? I see that FHIR client side libraries like fhir-client.js check if the id_token is provided. We need this id_token in our SmartApp.
Josh Mandel (May 20 2019 at 12:45):
The id_token, when available, is returned as a property in the access tokens response JSON payload. Any OAuth client you use (e.g., http://docs.smarthealthit.org/clients/javascript/) should provide access to these properties.
Jeremie Osaghae-Nosa (Jun 07 2019 at 15:04):
In regard to obtaining coverage for 1 patient what is the url query for this when using STU3.
Josh Mandel (Jun 07 2019 at 20:13):
GET /Coverage?patient=123
Lloyd McKenzie (Jun 07 2019 at 23:17):
In STU3 , it would actually have to be GET [base]/Coverage?beneficiary=123 - the 'patient' criteria wasn't defined
Jeremie Osaghae-Nosa (Jun 12 2019 at 17:15):
Has anyone been able to get coverage data from the online sandbox from SMART App Launcher. I'm not sure if they are lacking in patient data for STU3
Josh Mandel (Jun 12 2019 at 23:11):
"Coverage" is not part of the common clinical data set, and we don't have example date in our sandbox server. You can always add some yourself via POST to the open endpoint if you just want to try things out -- it should then be available from the launcher at least until a reset.
Jeremie Osaghae-Nosa (Jun 13 2019 at 13:44):
Thank you, will do
Last updated: Apr 12 2022 at 19:14 UTC
