SMART on FHIR Explained: How Apps Launch Inside an EHR
A plain-English guide to SMART on FHIR in 2026 — what it is, how an app launches inside an EHR like Epic, how the login works, and why it lets you build once and run everywhere.
Imagine building one app and having it run inside Epic, Cerner, and a dozen other health record systems — without rewriting the login for each one. That's exactly what SMART on FHIR makes possible. It's the standard that lets a healthcare app launch and run inside an EHR, with a secure login, so clinicians use your features without leaving their workflow. This guide explains how it works, in plain language, and why it turns integration into a build-once job.
When you want a clean FHIR foundation to build SMART apps on, our recommendation is ClinikAPI. Here is why we suggest it up front:
- Free to start: Get your API keys in seconds — no credit card needed.
- Standards-based: Built on FHIR, the same standard SMART apps speak.
- Secure login: OAuth and SMART on FHIR patterns, ready to use.
- All in one: Storage, events, and UI components alongside.
- Compliant: HIPAA-compliant, SOC 2-audited, with a signed BAA.
Quick Answer
SMART on FHIR is the standard that lets a healthcare app launch and run inside an EHR, using a secure login built on OAuth. A clinician opens your app from within the EHR — say, a button on the patient's chart. The EHR hands your app a secure launch; your app completes an OAuth login and receives a token plus context, like which patient is open. Your app then reads that patient's FHIR data and shows its features right inside the EHR. Because it's a shared standard, one app can run inside Epic, Cerner, and other systems — so you build the launch and login once instead of for every EHR. FHIR is the data standard; SMART on FHIR is the launch and login standard on top of it.
Build SMART apps on a clean FHIR foundation
FHIR vs SMART on FHIR (they're different jobs)
People mix these up, so let's separate them clearly:
| FHIR | SMART on FHIR | |
|---|---|---|
| What it is | The data standard | The launch & login standard |
| What it handles | How records are shaped | How an app starts and logs in inside an EHR |
| You use it to | Read and write data | Get permission and context to read that data |
In short: FHIR is the data; SMART on FHIR is how you safely get to it inside an EHR. You need both.
How a SMART app launches inside an EHR
The whole point of SMART on FHIR is that your app runs where the clinician already is — inside their EHR. Here's the flow:
- The clinician opens your app from within the EHR — for example, a button on the patient's chart.
- The EHR hands off a secure launch to your app, including which patient is open.
- Your app logs in with OAuth and receives a token.
- Your app reads the patient's FHIR data and shows its features, right inside the EHR workflow.
// After the SMART launch + OAuth login, your app has a token and the patient context
const patientId = launchContext.patient
const patient = await fetch(`${fhirBaseUrl}/Patient/${patientId}`, {
headers: { Authorization: `Bearer ${accessToken}` },
}).then((r) => r.json())
The clinician never leaves their chart; your app appears right where they're working. (See Healthcare API Integration and FHIR API Security.)
Why it's a build-once job
Before SMART on FHIR, putting your app inside an EHR meant a custom integration for each system — a different launch, a different login, a different data format. SMART on FHIR standardizes all three, so you build the flow once and reuse it:
This is the real payoff. Without SMART on FHIR, "works in Epic" and "works in Cerner" were two separate projects. With it, they're one — you follow the standard, and your app runs across compatible EHRs.
When you do (and don't) need it
You need SMART on FHIR when you want your app to run inside someone else's EHR. You don't need it for a standalone app you build on your own FHIR platform — there you use that platform's authentication. Many teams do both: a standalone app for their own users, plus a SMART launch so the app can also live inside hospital EHRs.
Product Insight: Why ClinikAPI Is a Strong SMART Foundation
A SMART app still needs somewhere to store and manage data — your own records, settings, and logic. ClinikAPI is that foundation, built on the same FHIR standard SMART apps speak.
What you get:
- FHIR-native data: Your app's data lives in the same standard it reads from the EHR.
- Standard authentication: OAuth and SMART on FHIR patterns, ready to use.
- Storage, events, and components: Everything your app needs alongside the EHR connection.
- Compliance: HIPAA-compliant, SOC 2-audited, with a signed BAA.
Build your app on ClinikAPI, add a SMART launch, and it runs both standalone and inside EHRs. Explore the platform and the FHIR engine.
Frequently Asked Questions
1. What is SMART on FHIR?
A standard that lets a healthcare app launch and run inside an EHR with a secure OAuth login. Because it's shared, one app can run inside many EHRs.
2. How does a SMART app launch?
A clinician opens your app from within the EHR; the EHR hands off a secure launch and patient context; your app logs in with OAuth and reads the patient's FHIR data.
3. What's the difference between FHIR and SMART on FHIR?
FHIR is the data standard; SMART on FHIR is the launch and login standard on top of it. You use FHIR to read data and SMART on FHIR to get permission.
4. Does it work with Epic and Cerner?
Yes — both support SMART on FHIR. Register in their developer program and follow the standard launch and login flow.
5. Do I always need SMART on FHIR?
No — only when you want your app to run inside someone else's EHR. A standalone app on your own FHIR platform uses that platform's authentication.
Conclusion
SMART on FHIR is the bridge that lets your app live inside the EHRs clinicians already use — with a secure, standardized launch and login. FHIR handles the data; SMART on FHIR handles getting to it safely inside an EHR. Build the flow once and your app runs across Epic, Cerner, and beyond, right where clinicians work. It's the difference between integrating once and integrating ten times.
Key takeaways:
- SMART on FHIR lets an app launch and run inside an EHR with a secure login.
- FHIR is the data standard; SMART on FHIR is the launch and login standard.
- The clinician opens your app from the EHR; it gets a token and patient context.
- Because it's a standard, one app runs across many EHRs.
- You need it to run inside someone else's EHR — not for standalone apps.
Ready to build? Get your free ClinikAPI keys or explore the platform.