Certified EHR Technology

Certified EHR Technology

eClinicalWorks Mandatory Disclosures

The following Health IT Module(s) have been certified by an ONC-ACB in accordance with the ONC Health IT Certification Program adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.

eClinicalWorks Mandatory Disclosures

Cures Act Communication Condition Compliance

eClinicalWorks is committed to complying with the updates to the 2015 Edition Health IT Certification Program made by the ONC Cures Act Final Rule. As required by the Communications Condition of Certification requirements, eClinicalWorks does not prohibit or restrict the following communications about certain aspects of their health IT, unless otherwise permitted to do so under 45 C.F.R. § 170.403 –

  • The usability, interoperability, or security of our product
  • Relevant information regarding users’ experiences when using our product
  • eClinicalWorks’ business practices related to exchanging electronic health information
  • The manner in which an eClinicalWorks’ user has used our product

eClinicalWorks does not and will not prohibit or restrict its customers or contractual partners from discussing problems with our software or services. This has been a policy of eClinicalWorks for years preceding the ONC Cures Act Final Rule. eClinicalWorks is not aware of the existence of any such restrictive contractual language in our agreements. To the extent that any provision contained in our agreements could be construed as prohibiting or restricting communications protected by the Communications Condition of Certification, eClinicalWorks confirms that any such contract language will not be enforced.

For more details on the Communications Condition and Maintenance of Certification requirements, visit: https://www.healthit.gov/condition-ccg/communications.

Real World Testing

The ONC Health IT Certification Program Conditions and Maintenance of Certification requirements mandate the real-world testing of specific elements of health IT. In November of each year, eClinicalWorks must submit a testing plan for the following calendar year to its ONC-Authorized Certification Body. Upon approval, the plan is used to guide the evaluation of real-world usage of specified interoperability criteria during the following calendar year. Results for prior calendar years are submitted in February to the ONC-Authorized Certification Body for review. Past and current test plans and results are posted below.

eCW Real World Testing – 2022 Results Report – Jan 2023

eCW Real World Testing – 2023 Test Plan

eCW Real World Testing – 2022 Test Plan

Certified APIs

As a health IT developer of certified health IT, eClinicalWorks offers FHIR (Fast Healthcare Interoperability Resources) application programming interfaces (APIs) as required by the ONC Health IT Certification Program, including APIs certified to the Standardized API for Patient and Population Services certification criterion found at § 170.315(g)(10). eClinicalWorks’ APIs serve as the gateway for third-party systems to integrate with eClinicalWorks’ suite of products. Click here to learn more about how eClinicalWorks is furthering interoperability in healthcare. Customers can learn more and enable FHIR APIs through the On-Demand Activation feature in the eClinicalWorks application.

Certified FHIR APIs are available to third-party application developers and eClinicalWorks customers at no cost at this time. This includes patient-centric FHIR APIs through healow and provider-centric and backend (single patient) and bulk (multiple patient) APIs via eClinicalWorks. eClinicalWorks will notify customers of any future API licensing or usage fees at least 30 days in advance of such fees taking effect. eClinicalWorks may also offer chargeable value-added services to application developers at a future date. Any costs or fees associated with the use of certified APIs will be posted on this page.

For comprehensive API business and technical documentation, and to sign up as a developer, visit connect4.healow.com for patient-centric FHIR APIs and fhir.eclinicalworks.com for provider-centric and backend/bulk FHIR APIs.