SMART on FHIR
SMART on FHIR is a standard that lets a third-party app launch securely from inside an EHR, using the clinician's existing login and pulling patient context automatically. It is how clinical apps appear inside a provider's normal workflow instead of requiring a separate login.
Key takeaways
- Launches a third-party app securely from inside the EHR
- Uses the clinician's existing login and current patient context
- OAuth-style authorization grants scoped, limited access
- Removes double logins and manual patient re-entry
- Correct auth and context handling is critical for security
What SMART on FHIR means
SMART on FHIR is the standard that lets a third-party app launch securely from inside an EHR and pick up where the clinician already is, using their existing login and the patient currently open on screen. It combines FHIR for the data with OAuth-style authorization for secure, scoped access. The result is an app that feels like a native part of the EHR rather than a separate destination.
The mechanics rest on an authorization flow that grants your app a token with specific, limited permissions, plus a launch context that tells it which patient and user are in play. This means clinicians do not log in twice or manually re-enter who they are looking at, which removes a huge amount of friction. It also keeps access tightly scoped, so an app only sees what it was granted, which matters for both security and trust.
For a buyer, SMART on FHIR is how you get adoption inside a clinician's real workflow instead of asking them to leave it. Building it correctly means getting the authorization and context handling right, since mistakes there are both a usability and a security problem. It pairs naturally with the broader FHIR and compliance work a healthcare product already needs.
Explore this on Agnotic
Where SMART on FHIR shows up in how we build.