03 · Getting it out
Six steps before any integration project.
The goal is modest: a file you can open, that you trust, on a schedule you control.
Where small hospitals get stuck
The EHR is hosted by a larger health system or shared through a vendor, so the hospital doesn’t build its own reports. That is a contract question, not a dead end. Ask the host what your service agreement says about reports, extracts, and turnaround before assuming the data is out of reach.
About certified EHRs
Federal certification rules have required certified EHRs to offer a standardized API and a way to export electronic health information. Those rules are being revised, so ask your vendor what applies to your version. The regulatory map tracks where they stand.
Read the contract first
Find out what you already pay for: standard reports, a report writer, scheduled extracts, API access. Many hospitals own more than they use.
Start with flat files
A scheduled export to a secure folder beats an integration you can’t staff. Most first projects need one table, refreshed weekly.
Keep patient data where it is
Aggregate or de-identify before anything leaves. No vendor, and no AI feature inside a tool you already use, touches patient data without a business associate agreement.
Write down the definitions
What counts as a transfer, a no-show, a denial, a readmission? One page, agreed by the people who use the numbers, prevents months of argument.
Name an owner for each source
One person per source who knows where it lives, who can pull it, and what is wrong with it. In a small hospital the same name may appear twice. That is fine.
Check one number by hand
Before trusting an extract, count something yourself, such as last Tuesday’s emergency visits, and compare. Do the same with anything an AI tool reports back.