How to integrate with Elation Health
This page lists what Elation Health publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: http://www.elationhealth.com.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| Elation EMR | Version 3 | Active | 2018-12-31 | 15.04.04.2717.Elat.03.00.1.181231 |
| ElationEMR | 1.0 | Retired | 2011-07-19 | CHP-006433 |
| ElationEMR | 2 | Retired | 2018-12-13 | 14.04.04.2717.Elat.02.01.0.181213 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://elationfhir.readme.io/reference/getting-started-with-standardized-api
- Application Access - Patient Selection (170.315 (g)(7)): https://elationfhir.readme.io/reference/getting-started-with-standardized-api
- Application Access - All Data Request (170.315 (g)(9)): https://elationfhir.readme.io/reference/getting-started-with-standardized-api
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://fhir.elationemr.com/fhir/fhir-base-url.
ONC Lantern tracks 1 FHIR endpoints for Elation Health.
How to integrate
- Read the (g)(10) documentation above. ONC criterion 170.315(g)(10) requires a standardized FHIR API for patient and population services.
- Register your application with the vendor, as its documentation describes.
- Authorize with SMART App Launch, or with SMART Backend Services for system-to-system access.
- Find the practice's FHIR base URL in the service base URL list.
- Plan for the gaps. (g)(10) certifies read access to USCDI data. Scheduling, charges, claims and write-back need vendor-specific APIs or another route.
