Certified EHR Technology

API Documentation

Click here to view the registration process to gain access to i-heal integration API use. This will also grant you access to the API used for user authentication, password management, facility authorization, patient search, demographics and patient common data sets.
Click here to view the API used for users authentication, password management and facility authorization.
Click here to view the API used for patient search and patient demographics access.
Click here to view the API used for accessing patient common data sets.
Click here to view g10 170.315(g)(10) FHR Integration documentation.
Click here to view g10 170.315(g)(10) FHR Integration Base URL.
Click here to view §170.315(b)(10) Electronic Health Information Export Documentation.

Mandatory Disclosure

Click here to view the mandatory disclosure form.
Click here to view the Certificate of Health IT Compliance.

Real World Test Plan

Click here to view our Real World Test Plan – 2025
Click here to view our Real World Test Plan – 2024
Click here to view our Real World Test Plan Results – 2024
Click here to view our Real World Test Plan – 2023
Click here to view our Real World Test Plan Results – 2023
Click here to view our Real World Test Plan – 2022
Click here to view our Real World Test Plan Results – 2022

Standards Version Advancement Process (SVAP) Notices
Notice of Intent to Implement HL7 FHIR US Core Implementation Guide STU 4.0.0 for 170.315(g)(10)
Issued: January 30, 2023
Please be advised that Healogics. Inc. has opted to leverage ONC’s SVAP process for the certification criteria at 170.315(g)(10) to adopt the HL7 FHIR US Core Implementation Guide STU 4.0.0 in its Patient and Population API Services. The adoption of the updated version will provide better forward compatibility and longevity for the APIs certified to this criterion. Because Healogics, Inc. is adopting this version in its initial certification of to the (g)(10) criterion, it is expected that the adoption of the updated version will have no impact on the interoperability of the affected module.