EHR notes
Every certified EHR exposes FHIR, but no two behave the same way in practice. EHR notes record what implementers have learned about each one: how access is set up, which export options work, how data the measures need is actually recorded, and the behaviours that cause a silent gap.
Each note is specific to one EHR product. Notes describe behaviour observed by implementers; they are not vendor documentation and do not reproduce it. Where a behaviour needs a fix before the measures can read the data, it becomes a candidate for a vendor-tier rule — the cookbook is where that knowledge starts.
How to use these notes
Section titled “How to use these notes”- Starting with a new EHR? Read its note alongside Onboarding a new EHR.
- Chasing a missing number? Check the note’s known behaviours, then the relevant recipe.
- Found something new? Every page has an Edit page link, or submit a recipe.
All EHR notes
Section titled “All EHR notes”| EHR | What the note covers |
|---|---|
| athenahealth | Accessing athenahealth's FHIR R4 API for quality reporting — practice scoping, rate limits, and a paging trap. |
| Compulink | Accessing Compulink Advantage FHIR for quality reporting — a non-standard export and "404 means empty". |
| eClinicalWorks | Bulk export and REST access to eClinicalWorks FHIR R4 for quality reporting, including a duplicate A1c trap. |
| Elation | Accessing Elation FHIR for quality reporting — per-practice client credentials and structured questionnaires. |
| Epic | Accessing Epic's FHIR APIs for quality reporting, and Epic-specific behaviour to plan for. |
| EyeMD | Accessing EyeMD FHIR for quality reporting — a tenant id in the token response and enumerating patients without population search. |
| Greenway | Accessing Greenway FHIR for quality reporting — per-practice enablement and roster-scoped cohorts. |
| ModMed | Accessing ModMed (EMA) FHIR R4 for quality reporting — ES384, unstable bulk manifests, and date-search traps. |
| Nextech | Accessing Nextech FHIR R4 for quality reporting — per-practice client ids and why paginated search beats bulk. |
| NextGen | Accessing NextGen FHIR for quality reporting — why backend tokens cannot search patients, and the headers data calls need. |
| Oracle Health (Cerner) | Accessing Oracle Health (Cerner Millennium) FHIR R4 APIs for quality reporting, and behaviour to plan for. |
| Other EHRs | Short notes on smaller EHRs and offline formats — Amazing Charts, Meditab, MeldRx, CareCloud, Tebra and more. |
| Practice Fusion | Bulk export from Practice Fusion for quality reporting — screenings stored as Conditions and other data-shape quirks. |
| Veradigm (Allscripts) | Processing Veradigm / Allscripts bulk FHIR exports for quality reporting. |