SMART on FHIR App Development for Healthcare

Apps that open inside the clinician's EHR session with the right patient, the right data and nothing more.

The SMART on FHIR specification is open, but every EHR applies it in its own way. An app that passes in a sandbox can still stall in a vendor's security review, or fail on its first launch from a clinician's workspace.

Cabot delivers SMART on FHIR healthcare app development for digital health companies, health systems and payers. We design the launch, the authorization and the data access together, so the app clears review and holds up in the live workflow. Every SMART on FHIR app development project starts with the EHR you need to reach, because that choice decides the launch type, the scopes and the review path.

EHR launch · Standalone launch · Backend services

Tell us which EHR you need to reach

Name the EHR and the workflow the app supports. A Cabot healthcare engineer will reply with the questions that decide the launch type and the review path.

No obligation. Your details stay private.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

What Is SMART on FHIR, and What Does a SMART App Actually Do?

SMART on FHIR is an HL7 standard that lets a third party app launch from inside or outside an EHR, sign in through OAuth 2.0, and read or write only the FHIR data the user has approved.

SMART stands for Substitutable Medical Applications, Reusable Technologies. The current HL7 release is SMART App Launch 2.2.0, built on FHIR R4. A SMART app registers with the EHR, asks for specific scopes, receives a short lived authorization code and exchanges it for an access token. In principle the same app can then run on any EHR that supports the standard. In practice each EHR sets its own registration steps, supported resources and review process, which is why SMART on FHIR app development is an engineering discipline and not a specification exercise.

FHIR apps take three shapes. A provider app opens inside the chart with the patient already selected. A patient app lets a person see or contribute to their own record, and sits close to our patient engagement solutions and patient onboarding software. A backend service moves data between systems with no user present. Cabot builds all three.

Why Do SMART on FHIR Projects Stall After the Prototype Works?

The specification is rarely the problem. These are the six failures that turn a working prototype into a stalled launch, and each one shapes how we scope the build.
science

The EHR is not the sandbox. Sandbox data is tidy. Production charts carry missing fields, local code sets and unusual encounters that only appear after launch.

hub

Each EHR reads the specification its own way. Registration, supported scopes and launch behavior differ between vendors, so an app built for one needs real work to run on the next.

fact_check

App review is a process, not a ticket. EHR vendors and health systems run security and clinical review, and a build that ignores it loses weeks at the end.

lock_open

Scopes are chosen last. Asking for more access than the workflow needs draws reviewer findings and erodes clinician trust.

timer_off

Sessions fail in ways demos hide. Expired tokens, lost launch context and a second browser tab break the workflow a clinician actually follows.

update

Version drift arrives quietly. SMART App Launch has moved from version 1 to version 2 permissions, and servers now advertise which they support, so an app needs a plan for both.

Smart on FHIR Application development

What Does a SMART on FHIR Build Cover From Launch to Listing?

Six workstreams take SMART on FHIR app development from architecture to a live EHR launch. Interface work, HL7 v2 feeds and SMART on FHIR integration beyond a single app sit with our healthcare integration services.

What Will a SMART on FHIR App Cost to Build?

SMART on FHIR app development cost follows the number of EHRs, the launch types and whether the app writes data back, far more than it follows the number of screens. Estimate a build in a few minutes, or put a specific question to an engineer.

Where Does AI Fit in a SMART on FHIR Build?

AI shortens the repetitive parts of SMART on FHIR app development: mapping FHIR resources to your data model, generating test cases from the requested scopes, and checking authorization flows for common mistakes. Scope decisions, clinical judgment and security sign off stay with engineers. Work that goes beyond the app, such as an assistant that reads FHIR data, sits with our AI agents for healthcare practice.
Three commitments apply to every build. We stay model neutral, so we choose the model for the task and your policy and not the other way round. An engineer reads and approves every change before it ships. And we never use your code or your data to train a model.

Which Stack and Tools Do We Use to Build and Test SMART Apps?

We match the stack to your environment and not to a house standard, and every stage produces something you can review. Here is both the stack and the place where a person steps in.

SMART app stack

Front end

React
TypeScript

Back end

Node.js
Python
.NET

FHIR and cloud

HAPI FHIR
Azure Health Data Services
AWS HealthLake
Google Cloud Healthcare API

Where AI helps and where a person decides

Stage
What AI does
What stays human
Tools used
Design and scoping
What AI does
Drafts workflow maps and candidate scope lists from your requirements.
What stays human
Chooses the scopes and the launch types.
Tools used
Claude Code
Build
What AI does
Generates resource mapping and boilerplate for launch and token handling.
What stays human
Reviews every change before merge.
Tools used
GitHub Copilot, HAPI FHIR
Test
What AI does
Generates test cases from scopes and sample FHIR bundles.
What stays human
Decides what counts as passing and reads the results.
Tools used
SMART Health IT sandbox, Inferno
Review and release
What AI does
Assembles security documentation drafts from the code.
What stays human
Signs the evidence and owns the submission.
Tools used
Vendor developer portals
Operate
What AI does
Flags specification and EHR changes that affect the app.
What stays human
Decides when and how to update.
Tools used
Cloud monitoring

How Do You Choose Among SMART on FHIR Development Companies?

Six questions separate a team that has launched SMART apps from one that has read the specification. A team offering SMART on FHIR app development, or broader FHIR application development services, should answer each with specifics.
What you are weighing
Typical company
Cabot
Standards depth
Typical company
Cites the specification.
Cabot
Builds to the current HL7 release and runs conformance tests before submission.
EHR coverage
Typical company
One EHR and one sandbox.
Cabot
Plans for every EHR you need and documents how they differ.
Launch types
Typical company
EHR launch only.
Cabot
EHR launch, standalone launch and backend services, scoped to the workflow.
Scope design
Typical company
Broad scopes to avoid errors.
Cabot
Least privilege scopes, reviewed with your security team.
Security review
Typical company
A checklist at the end.
Cabot
Evidence prepared from the first sprint.
Listing and review
Typical company
Hands over the code.
Cabot
Supports vendor or health system review through release.
After launch
Typical company
A support ticket queue.
Cabot
A plan for EHR updates and for changes between SMART permission versions.

Which EHRs Run SMART Apps, and How Do They Differ?

Every EHR below supports SMART on FHIR in some form, and an Epic SMART on FHIR app follows a different route from one built for MEDITECH. The differences that matter sit in the developer route, the launch types and the review step, and each should be confirmed with the vendor before design starts.
EHR
Developer route
Confirm before design
Epic
Developer route
Epic on FHIR developer program, with listing through Epic's app marketplace
Confirm before design
Launch types by app type, and review timeline.
Oracle Health
Developer route
Oracle Health developer documentation and code console
Confirm before design
Provider and patient app registration, and tenant provisioning.
MEDITECH
Developer route
Greenfield collaborative environments
Confirm before design
FHIR resources available on your platform version.
athenahealth
Developer route
athenahealth developer portal and marketplace
Confirm before design
API access tier and app approval.
eClinicalWorks
Developer route
eClinicalWorks developer program
Confirm before design
Practice level enablement and supported resources.

Which Buyers Does Cabot Build SMART Apps For?

Each buyer judges a SMART app by a different test, so we build for the one you are.

Which Standards and Security Controls Does a SMART App Have to Meet?

Security comes first. Scopes are least privilege, tokens are short lived and refreshed through the standard flow, secrets stay out of the client, and every access to patient data is written to an audit log. Patient data never lands in application logs.

Regulatory expectations follow the market. Certified EHRs in the US must expose a standardized FHIR R4 API with SMART support, which is why an app can rely on one specification across vendors. Whether the app itself is a regulated medical device depends on what it does with the data, which our last FAQ answer covers.

OAuth 2.0 with PKCE
OpenID Connect
SMART App Launch 2.2
SMART Backend Services
FHIR R4
US Core and USCDI
ONC g(10)
HIPAA
Audit logging

How Does SMART on FHIR App Development Move From Idea to a Live EHR Launch?

The process runs in six steps, and each one ends with a decision that is yours.

fact_check

1. Choose the EHR and launch type

You decide which EHRs and which launch types ship first.

design_services

2. Design the workflow and scopes

You decide the smallest set of scopes the workflow needs.

integration_instructions

3. Build against the sandbox

You decide which FHIR resources the app reads and which it writes.

science

4. Test with realistic data

You decide what evidence the reviewer will see.

rocket_launch

5. Pass review and register

You decide who owns the vendor or health system submission.

insights

6. Launch and maintain

You decide the update cadence for EHR and specification changes.

Who Builds and Owns Your SMART on FHIR App?

The team has one accountable owner per risk. A solution architect owns launch and authorization design. A FHIR engineer owns data access and mapping. A front end engineer owns the clinician experience. A QA engineer owns test evidence. A security reviewer owns the controls. A delivery lead owns the plan and your questions.

Our SMART on FHIR developers are deepest in four areas: EHR launch and authorization design, FHIR R4 mapping with US Core, clinician facing React interfaces, and test evidence for security and clinical review.

You work with the team directly. Sprint demos run against a real sandbox, the backlog is shared, engineers join your channels, and every scope and launch decision is logged with its reason.

Why Healthcare Leaders Choose Cabot for EHR-Embedded SMART on FHIR App Development

A launch only counts when the app survives review and works in the chart. Cabot earns repeat work on these six points.

Client Success Stories

See all Cabot case studies

What Should You Look at Next?

A live SMART app is one part of a connected build. These are the situations leaders reach next, and where to go for each.

Our Clients

Have Questions About SMART on FHIR App Development? Cabot Answers
Which EHRs support SMART on FHIR apps?

Most major US EHRs support SMART on FHIR, including Epic, Oracle Health, MEDITECH, athenahealth and eClinicalWorks, but each differs in launch types, available resources and review steps. Confirm the developer route with each vendor before design, because it decides the scopes, the sandbox and the approval timeline for your app.

What is the difference between EHR launch and standalone launch?

An EHR launch starts inside the EHR and passes the patient and encounter context to the app, while a standalone launch starts outside the EHR and asks the user to authorize and select a patient. Provider apps usually need the first, patient apps often use the second, and many products support both.

How long does SMART on FHIR app development take for a healthtech startup?

The build and the EHR review run on different clocks, and the review often sets the launch date. A focused first version can be built in a short series of sprints, while vendor approval depends on the EHR, so start the registration conversation in the first week.

How much does SMART on FHIR app development cost?

Cost depends mainly on the number of EHRs you target, the launch types you support and whether the app writes to the EHR, not on screen count, and writing to the EHR adds review work. Use the Cost Calculator for a first estimate, then confirm the scope in a scoping call.

Is SMART on FHIR the same as FHIR?

No. FHIR defines the data model and the API, while SMART defines how an app launches, signs in and receives approved access to that data. A SMART on FHIR app uses both.

Do we need to migrate a SMART version 1 app to version 2?

Not always, but servers now advertise version 1 and version 2 permission support separately, so an app must match what each target EHR supports. We review existing apps against each EHR and plan the scope changes before they become a launch blocker.

Can a SMART app write data back to the EHR?

Sometimes. Write access depends on the EHR, the FHIR resource and the scopes granted, and many EHRs allow writing to a limited set of resources only. Decide early which writes the workflow truly needs, because that choice shapes both the design and the review.

Is our SMART app regulated as a medical device?

It can be. An app that supports diagnosis or treatment decisions may fall under FDA oversight, while an app that only displays records usually does not. We prepare the evidence and your regulatory counsel makes the determination.