The short answer
FHIR gives you standard APIs for common clinical data, and SMART on FHIR gives you a standard way to launch and authorize apps. Reading patient demographics, encounters, labs, medications and notes is widely supported in the US. Writing back, custom data and workflow triggers vary by EHR, so check each vendor's capabilities, app review process and customer security requirements before you promise features.
What FHIR can and can't do
| FHIR does well | Plan around |
|---|---|
| Reading common data: patients, encounters, labs, meds, allergies, conditions | Write-back support that varies by vendor and resource |
| Launching apps in the EHR with SMART | Each health system enabling and approving your app |
| Population exports with Bulk FHIR | Custom fields and local codes |
| Standard profiles through US Core | Real-time event triggers, often needing vendor-specific options |
Key building blocks
- Resources: Patient, Practitioner, Encounter, Observation, Condition, MedicationRequest, DocumentReference and more.
- US Core profiles: the minimum data US certified systems support.
- SMART on FHIR: OAuth 2.0 scopes such as
patient/*.read, plus EHR launch context. - Bulk FHIR: asynchronous exports for analytics and population health.
- EHR marketplaces: vendor programs for registering, testing and listing apps.
A 6-step integration plan
- Define the workflow: which users, inside or outside the EHR, which data and which actions.
- Check vendor capabilities for each target EHR: resources, write support, launch types and marketplace rules.
- Build against sandboxes with realistic test data and handle local code mappings.
- Secure it: HIPAA safeguards, least-privilege scopes, audit logs and a BAA with each customer.
- Pass reviews: vendor app review and each health system's security questionnaire.
- Go live per customer with monitoring, error handling and support runbooks.
How Zuroth helps
- API development and system integration for FHIR, SMART apps, HL7 v2 and bulk exports.
- HIPAA compliance from $499 a month and security reviews for health system buyers.
- Web and mobile apps that work inside clinical workflows.
Our AI virtual care case study shows FHIR-based integration behind an AI scribe across 14 clinics.
Next step: book a free consultation.
Related reading
- Healthcare & HealthTech
- AI scribes for clinics
- HIPAA and generative AI
- API development & system integration
- HIPAA compliance
Frequently asked questions
What is FHIR?
FHIR (Fast Healthcare Interoperability Resources) is an HL7 standard for exchanging healthcare data through modern web APIs. Data is organized into resources such as Patient, Encounter, Observation and MedicationRequest, exchanged as JSON or XML over REST. FHIR R4 is the version most widely used today.
What is SMART on FHIR?
SMART on FHIR is a framework that lets apps launch inside or alongside an EHR and access FHIR data securely, using OAuth 2.0 and OpenID Connect for authorization. It allows one app to work across different EHRs that support the standard.
Can FHIR APIs write data back into the EHR?
Sometimes. Read access to common resources is widely supported because of US interoperability rules, but write access varies by EHR vendor, resource and customer. Plan for limited write-back, and check each EHR's documentation and marketplace terms early.
What is US Core?
US Core is a set of FHIR implementation guides that define the minimum data elements and profiles US systems must support, aligned with the United States Core Data for Interoperability (USCDI). Certified health IT must support it, which makes common data more predictable.
How long does an EHR integration take?
A read-only SMART on FHIR app for one EHR can take 6 to 12 weeks, including sandbox work and app review. Multi-EHR support, write-back, bulk data and customer-by-customer go-lives add time. Vendor approval and each health system's security review are often the slowest steps.