Developer docs Security & compliance Live demo
Try the demo

Connections / Moving in and out

Bring a practice’s records across — and let it leave with all of them.

An import is read and counted in full before anything is written, because it is the one operation that cannot be undone. The other half is a complete, decrypted export in a format anyone can read — so “no lock-in” is a fact rather than a promise.

A migration part-way through importing: a survey of 44,134 records, 43,637 that would land and 497 needing a person — with reasons such as a missing date of birth — above progress per file.
Every record is counted and explained before anything is imported. Shown with sample data.

What it does

Moving in and out, in practice

A survey before anything moves

A directory of FHIR bulk-export files is read in full and nothing is written: per record type, how many would land and why the rest would not, most common reason first.

Resumable and repeatable

Importing starts only from a survey, runs in batches, pauses and carries on where it stopped. It is keyed on the old system’s own IDs, so re-running never duplicates a chart.

Nothing guessed

A record without a name or date of birth, or an appointment without a patient, goes on a “needs a person” list, grouped by reason.

Moving out

One export of every patient, appointment and clinician, decrypted, one record per line, under its own permission — deleted once downloaded or after 48 hours.

A patient’s own record

One patient’s full record as FHIR, requested by staff or by the patient from their app, also deleted after 48 hours.

How it works

From the first step to the last

  1. 1

    Point it at the files

    The old system’s FHIR bulk export, on the server.

  2. 2

    Read the survey

    What would land, what would not, and why.

  3. 3

    Import

    In batches you can pause — or, leaving, export everything.

What it needs

Before you switch it on

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

Worth knowing

Imports bring patients, clinicians and appointments into Essentials’ working copy; diagnoses and allergies are counted and named but not moved, and nothing is pushed on into OpenEMR yet. Files are read from the server, not uploaded through the page.

See Moving in and out working on a real system.

The demo runs every module against an unmodified OpenEMR, with invented patients. Nothing to install and no sales call.