Certified Health IT Product List (CHPL)

Key facts

Maintained by

ASTP/ONC, with data reported by ONC-Authorized Certification Bodies

Covers

Certified EHRs, modules and other certified health IT

Includes

Criteria met, certification status, surveillance and non-conformities

Access

Web search, downloadable files and an API

CMS use

Generates the CMS EHR Certification ID used in program attestation

What is the Certified Health IT Product List?

Every product that earns certification under the ONC Health IT Certification Program gets a CHPL listing. The list is maintained by the Assistant Secretary for Technology Policy and Office of the National Coordinator for Health IT (ASTP/ONC), with listing data submitted by the ONC-Authorized Certification Bodies (ONC-ACBs) that issue certifications.

A listing identifies a specific product version, not a company in general. One developer can have many listings for different products, modules and versions, each with its own CHPL product number.

The CHPL does not show which hospitals or clinicians use a product. It documents what the product was certified to do and how it has fared under oversight.

What a CHPL listing contains

A typical listing includes:

• Developer name, product name, version and certification date.
• The certification criteria the product meets, such as standardized FHIR APIs or electronic prescribing.
• Certification status, such as active, suspended, withdrawn or terminated.
• Surveillance activities and any non-conformities, with corrective action plan details.
• Real world testing plans and results, and developer attestations to Conditions and Maintenance of Certification.
• Links to API documentation and required disclosures about additional costs and limitations.

Why the CHPL matters

Hospitals and clinicians reporting to the Medicare Promoting Interoperability Program or the MIPS Promoting Interoperability category use the CHPL to generate a CMS EHR Certification ID for the certified product or combination of products they used.

• Health IT buyers and investors check listing history for suspensions, terminations and open non-conformities before signing with or valuing a developer.
• Integration teams use API documentation links and published FHIR endpoint lists to find where to connect.
• Market analysts count certified products by criterion to see which developers support capabilities such as bulk FHIR export or decision support interventions.
• Where a data set links providers or facilities to CMS EHR Certification IDs or CHPL product numbers, the CHPL supplies the developer and product details for the join.