What is SMART on FHIR (SMART App Launch Framework)?

SMART on FHIR is the HL7 specification, based on OAuth 2.0, that lets an app sign in against an EHR, get the user's permission, and read FHIR data, either launched from inside the EHR or standalone. US-certified EHRs must support it for their patient and clinician APIs.

The formal name is the SMART App Launch implementation guide. It is built on FHIR R4 and describes a set of patterns, based on OAuth 2.0, for apps to authorize, authenticate and connect to FHIR servers. A server publishes its configuration at .well-known/smart-configuration so an app can discover the authorization endpoints and supported features.

The two launch flows

  • EHR launch: a user already in an EHR session opens the app. The EHR passes an iss and a launch parameter, and the app can receive context such as the current patient or encounter.
  • Standalone launch: the user starts the app outside the EHR, for example a patient opening a phone app, and the app goes through discovery and authorization on its own.

Permissions are expressed as scopes, such as user/Encounter.rs. Apps that need to know who the user is request openid and fhirUser and receive an ID token. All SMART apps must support PKCE. A separate Backend Services pattern covers headless systems with no user present, and SMART prefers asymmetric private-key authentication over shared secrets.

Why it matters for buyers

The ONC standardized API criterion requires certified EHRs to support SMART App Launch 2.0.0, including the capability sets for patient standalone apps and clinician EHR launch. It also requires that patients can revoke an app's access, effective within one hour, and that refresh tokens for qualifying apps last at least three months. If you build an app on SMART, the authorization flow should work the same way across certified EHRs. Registration is the exception: the criterion requires that apps can register with the authorization server but does not set a standard for how.

Example

A clinician clicks a risk calculator inside the EHR. The EHR launches it with the open patient's context, the app requests patient-level read scopes, and it pulls recent observations over FHIR without asking the clinician to log in again. We have shipped Epic and athenahealth integrations.