...
| Excerpt |
|---|
This guide helps SMART App developers follow best practice guidelines to create marketable "about" pages, social media link previews, and interchangeable manifest files, and patient banners. |
All examples in this page come from the HSPC Patient Data Manager (PDM). The code can be found at https://bitbucket.org/hspconsortium/patient-data-manager.
...
Here's an example of the manifest.prod.json file from the PDM app:
Misc. Best Practice Items
On top of those three guidelines, here are a few more:
...
...
Patient Banner
When an app is viewed in an EHR system, a patient banner containing certain patient demographics may be displayed, keeping the app in the context of the patient being treated. When designing your app, you may want to include a patient banner just in case the system it is launched in does not have one. You are more than welcome to do so, but you don't want to have two patient banners within one window. That's why the SMART authorization standard has included a parameter that your app can accept to indicating whether to show your apps banner or not. The variable is called "need_patient_banner". It is received in the final step of authorization when the access token and patient id are sent to your app. See http://docs.smarthealthit.org/authorization/scopes-and-launch-context/ for full documentation.
In HSPC
The HSPC sandbox may be used to test out this functionality. First, build a launch scenario for your app, click the Launch Embedded option, and launch.
Here's an example of the bilirubin app in embedded mode:
And one using its own patient banner:
