FHIR Chat · SMART: Embed vs Linked

Stream: implementers

Topic: SMART: Embed vs Linked

Tim Berezny (Jan 24 2019 at 20:38):

From what i can tell, there are two ways to launch SMART on FHIR apps: open in a new tab + open in an iFrame.

I'm building an app which i want to behave slightly different depending on whether it's launched in an iFrame vs as a new tab (in particular, when launched in an iFrame i want to hide some page headers and footers, but show them when launched in a new tab). Does SMART on FHIR have a defined approach to informing the app whether it's being launched as iFrame vs. in a new tab?

Mikael Rinnetmäki (Jan 25 2019 at 12:53):

There's the launch context parameter need_patient_banner . Not sure whether that's directly applicable to your use case, but based on your description seems so. See http://www.hl7.org/fhir/smart-app-launch/scopes-and-launch-context/index.html#launch-context-arrives-with-your-access_token

Tim Berezny (Jan 25 2019 at 14:44):

Interesting, seems very similar. What is a "patient banner"?

Michael Donnelly (Jan 25 2019 at 16:30):

Many EHRs have a section at the top of the screen with at least the patient's name (and often other information that will regularly be needed). While this can serve many purposes, the most important is reminding the provider which patient's record he or she is editing. A SMART app might implement a similar header, but if the SMART app is launched in an iFrame, it likely won't want to show the header, since then there would be two headers costing needless screen real estate.

Tim Berezny (Feb 27 2019 at 14:43):

Those launch context parameters seem very useful. Are these the ONLY launch parameters that are allows with SoF, or might i be able to add a new one? I see that it can launch for a specific PATIENT or CONTEXT, but i want to launch an app for a specific SERVICEREQUEST or USER.

would it be ok to add a launch parameter called "servicerequest" in my SoF app, and then just specify that that can be used in my implementation guide?

Mikael Rinnetmäki (Feb 27 2019 at 15:23):

At least it would be perfectly safe to use the intent parameter for that. See http://www.hl7.org/fhir/smart-app-launch/scopes-and-launch-context/index.html#launch-intent.
I do realize passing multiple values with that parameter would be tricky. But if your aim is to launch to a view that shows information about a service request or a user, that would be the way to go, I believe.
Note the language:

Note: SMART makes no effort to standardize intent values. Intents simply provide a mechanism for tighter custom integration between an app and a SMART host. The meaning of intents must be negotiated between the app and the host.

Mikael Rinnetmäki (Feb 27 2019 at 15:25):

You'd just need to find a way to embed the information on which particular service request or user to show into the value of the intent, in addition to specifying the view itself.

Tim Berezny (Feb 27 2019 at 15:26):

Sounds do-able I think... since every service request has a different ID, and i might want to leverage intent for other things as well, i'd probably have to do something like include the resource name + ID

e.g.,
intent=servicerequest98344
intent=servicerequest14543

Is that too hack-y?