Launch Context

There are 2 kinds of launch contexts.

Both EHR Launch and Standalone Launch cater to both patient and provider contexts. Patients can initiate app launches from inside or outside their patient portal, similar to how providers might launch apps within their EMR/EHR. EHR and Standalone launches are supported by our SMARTerFHIR toolkit.

In addition to these, there is another connection type known as the Backend Service Connection, primarily used for server-to-server connections rather than contextual launches. We also have an EHR Auth Gateway service available.

Learn more about Launch contexts in this YouTube video

EHR Launch

EHR Launched apps typically have a provider focus, such as with clinical decision support applications, voice assistants, and other tools accessed within EMR/EHR patient context. Providers typically launch these apps using button inside the EMR/EHR.

Standalone Launch

Standalone Launch supports applications like dashboards and data access, presenting information in a separate window from the EHR. Users navigate to the app from their web browser, log in, and retrieve information from their EHR, whether they are a patient or a provider.

Backend Service Connection

Backend services offer a server-to-server connection from a given app to the EMR/EHR. Often these kinds of applications are headless and need routine access to EMR/EHR data.

Any app that needs to use BulkFHIR, such as an analytics app or dashboard, is a great candidate for a Backend Service connection.

Most EMR/EHR vendors prefer to keep the number of backend connections to a minimum for security reasons, and prefer developers to use EHR and Standalone Launch whenever possible.

Multicontext Apps

Some apps may need to use multiple launch contexts, usually when their users include both patients and providers. Examples include:

  • A chatbot that captures patient information and saves it to the EMR/EHR
  • Remote patient monitoring apps

In many of these contexts there is no front-end user interaction, which would require the app to use a backend connection. Then, if the provider were to view the data, it would use an EHR Launch or Standalone Launch.

When choosing contexts, consider your users and how you want them to access the information.

Questions?

Please contact us if want to discuss contexts with regards to your app.