athenahealth
AmbulatoryathenaOne, running in everything from solo practices to large multi-specialty groups. Bridge works in the browser client clinicians sit in all day, including the patient chart and the open encounter.
If it runs in a browser, Bridge runs in it. 38 systems are mapped today, and the same thing works in every one of them.
Don't see the EHR you need?
If it runs in a browser, Bridge can run in it. Tell us which one and we will map it.
Tell us which EHRA few of the systems Bridge runs in. Same behaviour in all 38.
athenaOne, running in everything from solo practices to large multi-specialty groups. Bridge works in the browser client clinicians sit in all day, including the patient chart and the open encounter.
One of the largest ambulatory EHRs in the country. Bridge runs in the webEMR browser client, in eCW Cloud and in v12 and later.
Ontada’s oncology EHR, iKnowMed Generation 2, used across community oncology and the US Oncology Network. Bridge reads the patient header clinicians navigate from.
A long-established hospital EHR in community hospitals and health systems. Bridge runs in Expanse, the browser-based generation.
EMA, ModMed’s specialty-built EHR, with a distinct workflow per specialty across dermatology, ophthalmology, orthopedics and more. Bridge also runs in gGastro.
The dominant platform in behavioral health and human services, and widely used across post-acute and home care.
Ambulatory EHR from independent practices through large groups. Bridge runs in NextGen Enterprise and NextGen Office.
Flatiron Health’s oncology EHR, used across community cancer centers. Bridge runs in the patient chart and the scheduler.
The leading platform in senior care. Bridge runs in the resident chart and the clinical views skilled nursing and long-term care staff work in.
The most widely used platform in outpatient rehab. Bridge runs in the WebPT EMR clinicians document in, and Clinicient is in the same family.
Coverage is not spread evenly, and that is deliberate. If you sell into outpatient rehab, Bridge is already in 13 of the systems those practices run.
Bridge reads the chart the clinician already has open. Mapping is the work of teaching it to read one more EHR, and it is our work, not yours.
We work out how that EHR presents the patient, the encounter and the clinical detail in the browser, and teach Bridge to recognise it.
Your app receives the patient and open encounter through the SDK exactly as it does everywhere else. Nothing about your app changes for a new EHR.
There is no reduced mode and no per-EHR feature list. An EHR is either mapped or it is not, and once it is, everything works.
Tell us the system and the criteria, and we will show you the panel in it.