EHR integration that writes back, with an audit log on every write.
We connect intake, telehealth, booking and analytics to the EHR over SMART on FHIR, HL7 and vendor APIs, with field mapping, retries and an audit trail, so nobody re-keys what a patient already typed. Published work: three EHRs mapped into one data model, and a 14-location medical group's intake written into the EHR with no double entry.
Why EHR integrations break, and how we build them so they don't.
Most EHRs now speak FHIR, but each one speaks it differently. In the telehealth platform we built, Epic, Cerner and athenahealth each returned demographics, problem lists, medications and labs in their own shape, so a normalization layer maps all three into one internal model before the app uses them, and coordinator notes and vitals are pushed back to each chart.
The second failure is silent data loss. For a 14-location medical group, an HL7/FHIR bridge through vendor APIs and Redox now carries each patient from intake through appointment to encounter, with field mapping, least-privilege credentials, retries with a dead-letter queue and an audit log on every write. Intake and admin time per patient fell 41%, and the form error and rework rate fell 32%.
What we build into and around the EHR.
Integrations that survive EHR upgrades, and leave a record of every read and write.
SMART on FHIR apps
OAuth2 authorization per EHR, patient matching, and reads of demographics, problems, medications and labs over FHIR R4.
HL7 and FHIR bridges
Event-driven sync through vendor APIs or an interface engine such as Redox, from intake through appointment to encounter.
Normalization across EHRs
One internal data model for Epic, Cerner and athenahealth, so the product does not care which EHR a clinic runs.
Intake write-back
Structured intake answers written into the chart, with validation that catches missing fields before the visit.
Eligibility checks
270/271 insurance eligibility checks run during intake, before the patient reaches the desk.
Analytics from clinical data
Bookings, show rate and provider utilization in a warehouse with dashboards by location, provider and service line.
How an EHR integration runs.
Read the access you have
Which EHRs, which API or interface access your organisation holds, and which fields move in which direction.
Map and normalize
Field mapping and a shared data model, agreed with the clinical team before code.
Build with a safety net
Least-privilege credentials, retries, a dead-letter queue and an audit log on every write.
Test on synthetic data
End-to-end runs with synthetic patients, then a staged go-live by location.
Published prices, mapped to the job.
Every price here is the same one on the pricing page. Work with no published price gets a fixed price in writing before it starts.
Figures in the notes are what past clients paid, from the published case studies; they show the range, not a rate card. Work with no natural end, such as ongoing development, is priced per engineer per month with no lock-in.
When to hire us for this, and when not to.
- Staff re-key what patients already entered, or two systems disagree about the same patient.
- Your product has to work with more than one EHR.
- You need a record of every read and write for compliance.
- Your organisation has no API or interface access to its EHR yet. That starts with the EHR vendor; we can help you ask for the right access.
- You want to replace the EHR itself. That is a selection and migration project, not an integration.
- A built-in connector between two products already does the job. Use it.
Two EHR integrations in production.
A 14-location intake bridge and a telehealth platform on three EHRs, each with the numbers.
Unified HIPAA-aware intake with EHR integration cut intake/admin time 41% and lifted clinician throughput 16% across 14 locations.
HIPAA-compliant telehealth platform with 3 EHR integrations enrolled 1,200 patients in 90 days and backed a $4.5M Series A.
These are past engagements at the prices those clients paid. For build price, monthly cost and payback side by side, see what ten client projects cost.
EHR integration, answered
Which EHRs do you integrate with?
Our published work integrates Epic, Cerner and athenahealth over SMART on FHIR, and other systems through an HL7/FHIR bridge using vendor APIs and Redox. Others that expose FHIR R4 or HL7 interfaces work the same way; we confirm access before quoting.
FHIR or HL7: which do we need?
FHIR is the modern API most EHRs now offer and the one we use for apps that read and write individual records. HL7 v2 messages are still how many hospital and practice systems announce events such as admissions and appointments. Many integrations use both, often through an interface engine.
How long does an EHR integration take?
In the telehealth build, the FHIR work for three EHRs took about a month inside a five-month project. The 14-location intake bridge was part of a 12-week build. Access approvals from the EHR vendor can add time; we start those first.
How do you keep patient data safe in transit?
Least-privilege credentials, encryption in transit and at rest, retries with a dead-letter queue so nothing is silently dropped, and an audit log on every write. We sign a BAA for engagements that touch PHI and develop against synthetic data.
What does an EHR integration cost?
We quote a fixed price after seeing the access you hold and the fields involved. For scale: the whole published telehealth platform, including its three-EHR integration, cost $124,000.
Often scoped alongside.
Healthcare app development
Patient apps, telehealth and provider dashboards.
Healthcare app developmentERP and API integration
NetSuite, Odoo, QuickBooks and Xero connected to your other systems.
ERP and API integrationHealthcare software development
The industry hub for care providers and healthtech.
Healthcare software developmentFrom the field notes
Two systems that should agree?
Tell us which EHR, which other system and what has to move between them. A senior engineer replies with a scoped plan and a fixed price.