Getting started with Elation EMR Standardized Patient and Public health API

Elation EMR Standardized Patient and public health API adheres to the HL7® FHIR® R4 specification and requirements for the ONC Certified (g)(10) Standardized API.

Who can access this API?

This Documentation and API helps our partners and customers (trusted developers) utilizing Elation EMR to integrate the API in their workflows to meet the requirements of the Standardized API for Patient and Population Services criterion § 170.315(g)(10) in the 2015 Edition Cures Update.
Let us know you are interested in integrating with Elation. Submit this form to indicate your interest in integrating with Elation.

Review and sign our API terms of service

The Elation API terms of service will be sent to your designated authorized individual who will review and sign the terms of service.
You can access our full terms of use here.

Start using our API in our sandbox environment

After registering as a trusted developer Elation sandbox API credentials will be sent. Test practices in our sandbox environment are PHI-free to keep your test data private.

Once registered as a developer, developer is able to register an Application (client) and get the grants approved by the Elation Administration for token generation purposes. Elation support team will also be available to help you walk through the steps.

Practice grants data-sharing consent and fees

The data sharing entity (i.e. practice) provides written consent to provide production access to integration.

Start using our API in production. For further details on our ONC Certification and API transparency conditions, please refer to the link here
Client registration as developer or patient needs to register use the following links for token generation purposes.

Additional monthly fees may apply to integrators. API pricing is available here or upon request by contacting questions@elationhealth.com.