Bridge puts your app in the chart
Bridge runs inside the EHR your customers already use. It reads the chart, hands it to your app through one SDK, and gets out of the way.
L1–L4 run on the clinic's machine, in the physician's sessionL5 is your app: your rules, your brandL6 is your servers
Your app runs in the session they already have
Bridge is a browser extension that works alongside the physician's existing EHR sign-in. It doesn't create a new login or a back door into the EHR. Where the clinic uses single sign-on, Bridge's session rides on it, and your app can sign the physician in through Bridge instead of asking again.
- Chrome and Edge, installed by IT policy or by the physician
- OIDC and SAML federation, including EHR-native SSO
- Sees only what the signed-in physician can see
- Session credential is never exposed to your app
You decide when you show up, and it's decided in the tab
Your rules decide which patients your app appears for and what it says. As the physician opens charts and encounters, the runtime updates the patient context and the SDK passes each change to your app, and your logic runs right there in the browser. Checking whether a patient fits your program, for example, happens in the tab, so nothing is sent anywhere to make that call.
- You decide when the tile appears and for whom
- Rules run locally, the moment a chart opens
- Patients who don't qualify: nothing transmitted
// your rules, running in the tab payerIn(insurance, accepted) ✓ icd10Prefix(problems, "E11") ✓ ageMin(dob, 18) ✓ → show("Refer Aldus")
Illustrative. Rules shown are the demo program's.
When they act, all they see is you
The tile on the edge of the chart and the panel it opens are your product: your name, logo, colors, words and workflow. A referral form, an enrollment flow or your whole platform. Bridge is the infrastructure underneath and stays out of sight.
- Your app loads from your own servers, in its own frame
- Your copy on every verdict and every button
- No Bridge branding in front of the physician
A sample partner, Northwind Care, in its own brand.
Patient data leaves only on "Refer"
Up to the moment the physician clicks, everything has happened in their browser. When they refer, enroll or submit, your app sends that one record straight to your backend. It doesn't pass through Bridge's servers.
- HTTPS from the browser to your own endpoint
- Covered by your BAA with the clinic
- What leaves is visible in your own traffic
Before the click
0records sent while charts open, rules run and your panel shows
On "Refer Aldus"
1referral, straight to you
The full data flow, with trust boundaries, is on the security page.
Built once, runs in every EHR Bridge runs in
Every EHR shows the chart differently. The runtime learns each one and turns it into the same patient and encounter context, so your app is written against one SDK and works in all of them. When an EHR changes, we update the runtime. Your app doesn't change.
- One context shape across every mapped EHR
- No per-EHR code, no reduced mode
- We handle EHR updates
// what your app receives, in every EHR patient: { first: "Aldus", last: "Carter", dob: "1945-10-25", xdata: { primaryInsurance: "Medicare", problems: ["E11.69 Type 2 diabetes"] } }, encounter: { date: "2026-09-29", provider: { name: "Scott Crunkleton, MD" } }
Simplified. Field names follow the Bridge SDK's patient and encounter objects.
Common questions
- Does this replace the EHR's own referral order?
- No. Bridge finds the patients and captures the clinical context for your program. It sits alongside whatever ordering the practice already does.
- What does it take to add a program?
- A configuration file. It names the criteria, what each one reads, the copy for each verdict, the referral form and the status steps. No new code ships to add a program.
- What happens when data is missing?
- A missing value is unconfirmed, not failed. The panel says it could not be confirmed and lets the clinician refer with a note.
- Which EHRs does it work in?
- Any browser-based EHR can be mapped, and 38 are mapped today. The full list is on the EHRs page.
Want it configured for your program?
Send us your criteria and we will stand up a demo on your rules. Shortly after, we'll set you up with a working demo you can install and use yourself.