SMART App Launch
Open your full app embedded inside the EHR, scoped to the patient on screen.
SMART App Launch is the pattern for opening your application from inside an EHR. The clinician clicks your app from the chart, Medblocks handles the SMART launch, and your app receives a launch context it can use to load the right experience.
Use it when your app needs more than a small alert or recommendation. A care coordination view, trial matching workspace, prior authorization tool, specialty workflow, or documentation assistant usually wants a full application surface.
How the flow works
- The provider organization enables your app in the EHR.
- A clinician launches the app from the patient chart.
- The EHR sends launch context to Medblocks.
- Medblocks completes the SMART authorization flow and redirects to your app launch URL.
- Your backend resolves the Medblocks launch token and loads the patient, user, organization, and encounter context.
The clinician does not need to search for the patient again, and your app does not need to implement the EHR-specific launch exchange for every source.
What to configure
In Configure Clinical Workflows, add the URL where Medblocks should send the clinician after launch. For Epic, the same page shows the launch URL and redirect URI needed by the EHR administrator.
If your organization owns the EHR app registration, switch the connection to your own credentials and copy the Medblocks callback values into the EHR developer setup.
Not sure if this fits you?
Tell us what you're building and we'll show you exactly what you can integrate.