5 Star Reviews

Top Software Developer

2026 Clutch Ranking

5 Star Reviews

Top App Developer

2026 BusinessofApps

EHR-connected patient appsBAA before any data

Patient Apps
Connected to Your EHR
via FHIR

We build iOS, Android and web patient apps that read records from your EHR through its FHIR R4 API and SMART App Launch, and write back appointments, forms or messages where the vendor's own API allows. We check what your EHR supports before we scope, and sign a BAA before any data.

FHIR R4 and SMART App Launch
We sign a BAA
iOS, Android and web
Tom Spencer
Deniz
Ted
Manley
Andrew
Grant Calder
Grant Kendzior
Cary Jack
Willie Shutter

"If you're looking for a team that can support you, help scale your product, and be a true technical partner, slashdev.io is the way to go. Features that took months to finish are getting done in days. They have completely changed my business!"

Tom SpencerCEO & Founder AdvocacyAI
1 of 9

Can a patient app read and write data in our EHR?

Reading is standardized; writing depends on the vendor. Health IT certified to ONC's § 170.315(g)(10) criterion supports a FHIR R4 API for patient access, secured with SMART App Launch 2.0.0 and built on US Core 6.1.0 profiles. The services that criterion requires specifically exclude write capabilities, so booking, forms and messages written back to the EHR depend on each vendor's own APIs and approval. We confirm what your EHR allows before we scope the app.

Standard
FHIR R4 (v4.0.1) with SMART App Launch 2.0.0
Data
US Core 6.1.0 profiles, the baseline in ONC's (g)(10) criterion
Writes
Not part of the (g)(10) API; vendor-specific
Rates
Managed development from $75 per hour; engineer rates $50 to $150 per hour by seniority; one fixed price from a free build plan
BAA
We sign a Business Associate Agreement before any patient data is shared

How We Work

Outcome-Based Pricing

We don't sell hours — we sell outcomes. Every engagement starts with a clear scope, defined deliverables, and upfront estimates so you know exactly what you're getting before work begins. You get full accountability, transparent progress, and a team that's committed to shipping results — not burning through a budget.

Scoped Upfront

Every project starts with clear deliverables, timeline estimates, and success criteria — before a single line of code is written.

Full Accountability

We own the outcome, not just the hours. Transparent progress updates, milestone reviews, and a commitment to shipping what we promised.

Flexible Engagement

Managed development with a dedicated team, or senior engineers embedded in yours. Scale up or down as your project evolves.

Most Popular

Managed Development

from$75/hour

We define the outcome, assemble the right engineers, and own the delivery from kickoff to production.

  • Scoped deliverables & milestones
  • Dedicated project lead
  • Weekly progress reviews
  • Full delivery accountability
  • AI-accelerated development

What an EHR-Connected Patient App Includes

Read access through the standard API, plus write features where your EHR's own API allows them.

Sign-In with SMART

Patients sign in and authorize the app against the EHR's authorization server.

  • SMART App Launch standalone patient launch
  • OAuth 2.0 based authorization
  • Scoped, revocable access
  • MFA on the app account

Read Records

Show patients their own data from the EHR in a clear mobile view.

  • US Core profiles over FHIR R4
  • Results, medications and allergies
  • Visit history
  • Read-only by design

Appointments

Booking and reminders, where the EHR's API allows writes.

  • Available slots shown in the app
  • Booking written back where supported
  • Reminders without PHI in the text
  • Fallback to a request form

Forms and Intake

Intake completed before the visit and delivered to the practice.

  • Mobile-friendly forms
  • Written to the EHR where its API allows
  • Otherwise delivered to staff securely
  • Audit trail per submission

Messaging

Secure messages between patients and the care team.

  • Encrypted threads
  • Routing to the right staff
  • Notifications that never expose PHI
  • EHR inbox where the vendor supports it

Audit and Consent

Every access logged, and the patient's authorization recorded.

  • Audit log of every read and write
  • Consent captured in the app
  • Access revoked on request
  • Logs for your compliance team

From EHR Access to a Live App

We confirm what your EHR allows before anything is scoped.

01

Confirm Your EHR's API Access

We review your EHR's developer documentation and your agreements to confirm which FHIR endpoints, scopes and write APIs are available to you.

02

Sign the BAA

We sign a Business Associate Agreement before any patient data is shared.

03

Build Against the Sandbox

We build and test against the vendor's test environment with synthetic data, then move to production access.

04

Launch and Monitor

We release to the App Store, Google Play and the web, and monitor API errors and access in production.

EHR-Connected Patient App Questions

What is SMART on FHIR?

SMART App Launch is an HL7 implementation guide that describes how a user-facing app is authorized to connect to a FHIR server, using patterns based on OAuth 2.0. Together with FHIR R4 it is how patient apps connect to certified EHRs: ONC's § 170.315(g)(10) criterion requires SMART App Launch 2.0.0, including standalone patient launch.

Is the patient-access API read-only?

Yes. ONC's § 170.315(g)(10) page says the services it requires specifically exclude write capabilities. Writing data back, such as booking an appointment or filing a form, depends on each EHR vendor's own APIs and approval.

Does it work with athenahealth?

We confirm what is available from athenahealth's own developer documentation and your account before we scope anything, and we do not assume write access. We do not make claims here about another company's APIs, fees or approval steps.

Does it work with ModMed?

The same applies: we check ModMed's own documentation and your agreements first, and scope only what is confirmed.

Does it work with eClinicalWorks?

We cover the main ways to get data out of eClinicalWorks, including FHIR and HL7, in our guide at /eclinicalworks-data-access.

How much does an EHR-connected patient app cost?

Managed development starts from $75 per hour, and engineer rates range from $50 to $150 per hour depending on seniority. A free build plan gives you one fixed price before any code is written, and every engagement starts with a 7-day risk-free trial. EHR integration is usually the largest single item, and write features add more than read-only access.

Is Slashdev affiliated with these EHR vendors?

No. Slashdev is an independent company and is not affiliated with, sponsored by or endorsed by any EHR vendor named on this page.

Sources We Checked

The certification criterion and HL7 standards behind the statements on this page.

Free Build Plan

Find Out What Your EHR Allows

Tell us your EHR and what the app should do. We'll check the API access available to you and send a build plan with one fixed price.

Free build plan
BAA available
7-day risk-free trial
Professional Services
Loading insights...