// EHR bridge
Eveda drafts the note on your phone. The bridge is a small browser extension that puts the finished note into the EHR you already use — the one in the tab you already have open. No copy and paste, no second system to learn, and no Eveda password typed into a browser.
Any Chromium browser on Windows, macOS or Linux.
The Firefox build is for Developer Edition or Nightly. Release Firefox will not keep an unsigned add-on installed — we say why below rather than let you find out after a restart.
// Install · Chrome
You will get a folder called eveda-ehr-bridge-chrome-1.0.0. Put it somewhere it can stay — Documents is fine, Downloads is not. Chrome loads the extension from this folder every time it starts, so deleting it uninstalls the bridge.
Type chrome://extensions in the address bar and press Enter. Turn on Developer mode, top right.
Click Load unpacked and choose the folder you unzipped. Select the folder itself, not a file inside it. Eveda — EHR bridge appears in the list.
Pin the Eveda icon to the toolbar and click it. The panel shows an eight-character pairing code. In the Eveda app, open Profile → Connected browsers, type the code, and approve it.
The pairing happens on a device you are already signed in on. That is deliberate: the extension never asks for your Eveda password, because a password box drawn inside browser chrome is a thing any page can learn to imitate.
// Install · Firefox
Firefox will not permanently install an add-on that has not been signed by Mozilla. Until the bridge is through that review, it runs in Developer Edition or Nightly, and it is removed every time the browser closes. If your clinic runs release Firefox, use a Chromium browser for now.
Unzip eveda-ehr-bridge-firefox-1.0.0.zip and keep the folder.
Go to about:debugging#/runtime/this-firefox, click Load Temporary Add-on, and choose the manifest.json inside the folder.
Pairing works exactly as it does in Chrome. The add-on disappears when Firefox closes, so step 02 has to be repeated each session. Your pairing is remembered on the Eveda side.
// Permissions
Your browser will list the permissions when you install. Here is what each one is actually for.
How it fetches your finished notes. This is the only site it can reach without asking.
Requested only when you point the bridge at an EHR, and only for that site. It is listed as optional for exactly this reason: the bridge does not arrive holding permission to read every page you open.
Holds the pairing for this browser and checks for finished notes on a timer. Nothing here leaves the machine, and you can end a pairing from the Eveda app at any time — under Connected browsers, where every linked browser is listed with when it was last used.
// If something is wrong
Expected. This is a direct download rather than a store listing, so Chrome treats it as a developer extension and will remind you on some launches. Keep it if the folder is the one you unzipped from this page. Once the bridge is listed on the Chrome Web Store, that warning goes away and updates arrive on their own.
In Firefox this is normal — a temporary add-on is removed on close, and it has to be loaded again. In Chrome it usually means the unzipped folder was moved, renamed or deleted; Chrome reads the extension from that folder on every launch. Put it back, or load it again from wherever it now lives.
Codes are short-lived. Open the panel again for a fresh one and enter it straight away. Check you are signed in to the same clinic on the app, and that the phone and the browser are both online — the approval travels through Eveda, not between the two devices directly.
The bridge carries notes that are finished. A draft still waiting on your signature will not appear, by design — nothing half-written should reach the record. Sign it in the app, then reopen the panel. If it is still missing, check the browser is still listed under Connected browsers in your profile; an unlinked browser stops receiving notes immediately.
It puts the note into the fields on the page you have open, so it works with EHRs that run in a browser. If yours is a desktop application rather than a website, the bridge cannot reach it — tell us which one and we will say plainly whether it is on the roadmap.