Connections / EMR connection

Connect your EMR once. Every module works from it.

Keeps a working copy of the parts of the record the modules need — patients, appointments, clinicians — through the Bridge, which talks to OpenEMR or another EMR’s API. The EMR stays the record; this is a cache with an audit trail.

Try it in the live demo All modules

The EMR connection page: a live connection to OpenEMR 8.2.0 with counts of patients, appointments and visits still to come, and a three-column map of which record types work both ways, read only, or not at all. — Exactly what your EMR will and will not let the modules do — before you find out the hard way. Shown with sample data.

What it does

EMR connection, in practice

A working copy, not a second record

Patients, appointments, clinicians and locations, sent in by the Bridge. Each delivery is applied once even if it arrives twice, and identifying details are encrypted on arrival with the practice’s own key.

Keeps working when the EMR does not

Reminders and booking run from the copy rather than calling the EMR for every appointment, so maintenance at the EMR does not stop them.

Says when it has gone quiet

Counts of what is held and when the last change arrived; if nothing has arrived for over a day, the panel is flagged.

The capability map

Every record type listed as “both ways”, “read only” or “not through the EMR”, from what the Bridge declares — with the missing operations and why.

Credentials stay in the Bridge

EMR credentials live in the separate Bridge console, never in the workspace. “Test the connection” asks the Bridge to check the link.

How it works

From the first step to the last

1
Connect
An API credential for your EMR, entered in the Bridge console.
2
Map
The Bridge declares what that EMR allows, per record type and operation.
3
Sync
Changes arrive continuously; every module works from them.

What it needs

Before you switch it on

Nothing elseWorks on its own, with or without an EMR connected.

Every module switches on and off by itself, per clinic, with its own screens, permissions and audit trail.

Worth knowing

The EMR stays the record; this is a cache with an audit trail. For OpenEMR, appointments can be booked and cancelled but not moved, and there is no billing API — the map says so rather than hiding it.

Goes well with