How do you get data into an EMR without a usable API?
Use the EMR vendor's approved API if it covers the task, then a vendor import or interface, then an eReferral or integration engine. Only if none fits, type through the screen with a program, and read the saved record back another way. Write APIs are often gated by vendor agreements and per-clinic enablement, so check access early.
Updated 2026-10-14
The options, in order
| Option | Good when | Watch out for |
|---|---|---|
| The vendor's approved API | It covers the whole task, such as creating a patient and a referral | Write access often needs a vendor agreement, fees and enablement for each clinic |
| A vendor import or interface (for example HL7 or a bulk import) | Data arrives in batches | Set-up time on the vendor's side |
| An eReferral network or integration engine | Referrals already travel electronically | Not every referring office uses it |
| Screen entry by a program, with a read-back | None of the above fits, or access is pending | It needs a second way to read the record; a person approves at first |
| Staff typing it | Low volume | Staff time and typing errors |
If you enter through the screen
- Run it on a computer the clinic controls, in a staff member's own session, so the EMR's audit log shows it.
- Read every saved record back through the EMR's own data: read-only API access, a reporting database or a report export. Re-reading the screen doesn't count.
- Stop on a possible duplicate patient instead of creating a second chart.
- Have a person approve each save until a readiness test supports approving only exceptions.
In our OpenEMR test, a program learned from a demonstration saved 7 of 8 synthetic referrals, with 12 of 12 fields read back by our test setup, and stopped on a possible duplicate. We haven't tested a commercial EMR.
Is screen entry allowed?
It uses the EMR the way your staff do, in their own session. Read your EMR contract; we haven't found a published Canadian EMR term that bans or allows it. Ask your vendor about API access at the same time.
Where OpenAdapt fits
OpenAdapt is the fourth option: a program learned from a demonstration, with a read-back. See referral intake, API or screen automation? and For healthcare AI teams.
Sources
- OpenAdapt on OpenEMR 8.0.0.3 (open-source EMR), local test copy, 11 Oct 2026. One program ran over 8 synthetic eReferrals in one batch, with 0 AI model calls. 7 new patients were saved; our test setup read each chart back through the OpenEMR API and database, and 12 of 12 fields matched the referral. The 8th (Rosa Delgado, same name as an existing chart, different birth date) stopped at the EMR's duplicate check; afterwards no new chart existed. The engine labels the saved runs "Finished, not checked" (practice profile) and the stop "Check the record".
See it on your process
Bring one task your team types every day. We'll tell you whether it fits, and what a test on your own system would cover.