An integration per EHR
Every new customer runs a different system, and each one becomes its own project before your product can appear in the chart.
EHR integration, without the integration project
A referral button, an enrollment form, or your entire platform, under your brand, in the chart at the moment clinical decisions are made.
- Works in 38 EHR systems
- Live in 45 days or less
- No IT project
- HIPAA, BAA included
The contract is not the end of implementation
You won the customer. Now your product has to show up in their EHR, at every site, in front of physicians who have never heard of it.
A deployment per site
Even on the same EHR, each practice has its own rollout, its own IT and its own timeline.
Physicians who forget you're there
The product works, but it lives in a portal, and enrollment depends on someone remembering to open it.
What Bridge changes
One layer between your product and every EHR it needs to run in.
Your UI, your brand
Your product appears beside the chart in a panel that carries your name and your sign-in. Physicians never see Bridge.
The open chart, normalized
Patient, encounter, insurance and problem list arrive in one shape, whichever EHR the practice runs.
Your rules decide when to appear
Your criteria run in the physician's browser against the chart that's open, so your button lights up for the patients who qualify and stays quiet for the rest.
We keep the EHR mappings
When an EHR changes its screens, we update Bridge. Your product doesn't change.
We build it for you, or your team builds on the SDK
Managed: send us your form or portal; we build and run the tile and panel, with uptime committed through to your endpoints.
SDK: chart-context events, tile and panel control, OIDC sign-in. Your UI, running in our extension.
import { getPatient, onPatientChanged } from '@arrowhealth/bridge-sdk'
getPatient().then(patient => console.log('patient', patient))
const offPatientChanged = onPatientChanged(patient => {
console.log('patient:changed', patient.id)
})
When a prospect asks if you work in their EHR, say yes
Bridge already runs where your customers work.
- EHRs
- 38+
- active workstation installs
- 12,000+
- patient charts daily
- 80,000+
As of September 2026.
Running today in
- athenahealth
- eClinicalWorks
- NextGen Healthcare
- ModMed
- WebPT
- Prompt EMR
- OncoEMR
- iKnowMed
- PointClickCare
- MatrixCare
- Netsmart
- MEDITECH
- Elation Health
- Tebra
- AdvancedMD
- Raintree Systems
- See all 38
All product names are trademarks of their respective owners. Their use here indicates the systems Bridge runs in and does not imply endorsement or affiliation.
Being in the chart makes all the difference
Three companies put their product beside the patient chart. Here is what it did for growth, lead conversion and time to go live.
Social determinants of health in cancer careEHR go-live in weeks, not monthsWhat once took months and massive investment is now a turnkey, revenue-generating process, with implementation down from 6 months to approaching 6 weeks.~6 weeks to go live in a customer's EHR, down from 6 monthsFaster deploymentAdoptionRead the case study 
Remote therapeutic monitoringOne site to hundreds of practicesSaRA Health used Bridge to work across its customers' EHRs without building integrations, and grew from a single site to hundreds of practices.3,262% increase in RTM enrollmentMulti-EHR scaleAdoptionRead the case study 
Chronic care managementTwice the lead conversion, from inside the chartA 5% lift in enrollment would have been game-changing. Arrowhealth Bridge delivered 5x the growth MetaPhy was expecting.2× lead conversion, against MetaPhy's other lead sourcesHigher conversionAdoptionRead the case study You have options for EHR integration
Here's how they stack up, including where going through the EHR is the better fit.
| Capability | Integrate through the EHR | Bridge |
|---|---|---|
| Physicians see you in the chart | Depends on what the EHR offers; often data only | Yes, beside the chart on patients who qualify |
| Whole-population data | Yes, e.g. every diabetic patient in a practice | No, only the chart that's open |
| Custom order sets | Yes, inside the EHR's own ordering | No, works alongside the EHR's ordering |
| EHRs covered | One at a time | 38 browser-based EHRs |
| Desktop EHRs | Yes | Not supported |
| Time to live | Months per EHR | 45 days or less |
| What the clinic has to do | An IT project per site | Install the extension on each workstation |
| When the EHR changes | You and the vendor update it | We update Bridge |
Questions product teams ask first
- What does the clinic have to do?
- Install the Bridge extension on each workstation, in Chrome or Edge, and sign in once. Clinics that manage browsers centrally can deploy it by policy. There is no interface to build on their side.
- What if a customer's EHR isn't on the list?
- Bridge works in browser-based EHRs. 38 are mapped today, listed here, and mapping a new one is our work, not yours. Tell us which one.
- Can we use the app we already have?
- Usually, with modest changes. A web app can run in the panel beside the chart; the SDK hands it the open chart and the physician's sign-in. We'll tell you what it takes on the first call.
- Whose brand do physicians see?
- Yours. The button, the panel and the sign-in carry your name.
- Does patient data go through Arrowhealth?
- Bridge doesn't send it to us. It reads the chart in the physician's browser and hands it to your app, which sends what it needs to your own backend. Our servers handle sign-in, configuration and health checks. The security page has the detail.
- Do we have to build anything?
- Not unless you want to. Send us a form or a portal and we build and run the tile and panel. Or build your own UI on the SDK, with chart-context events, panel control and sign-in.
See your product beside the chart
Twenty minutes, and your product or workflow beside the chart. Shortly after, we'll set you up with a working demo you can install and use yourself.