Conditions & Maintenance of Certification

Regulation

Condition of Certification

Maintenance of Certification

Certification Companion Guide (CCG)

CCG Last Updated

Information Blocking

A health IT developer may not take any actions that constitutes “information blocking” as defined in Section 3022(a) of the Public Health Service Act (PHSA) and § 171.103 on or after April 5, 2021.

There are no accompanying Maintenance of Certification requirements beyond compliance with the Condition.

Guide

03-11-2024

Assurances

A health IT developer must:

1. Provide assurances that it will not take any action that constitutes information blocking, or any other action that may inhibit the appropriate exchange, access, and use of electronic health information,
2. Ensure full compliance and unrestricted implementation of certification criteria capabilities,
3. Not take any action to interfere with a user’s ability to access or use certified capabilities, 
4. Certify a health IT product which electronically stores EHI to the §170.315(b)(10) criteria, and
5. Not inhibit its customer’s timely access to interoperable health IT certified under the Program.

A health IT developer must:

1. For a period of 10 years beginning from the date of certification, retain all records and information necessary that demonstrate initial and ongoing compliance with the requirements of the ONC Health IT Certification Program, and
2. Certify to the criterion in § 170.315(b)(10) by December 31, 2023, if a health IT product electronically stores EHI.
3. Update a Health IT Module, once certified to a certification criterion, to all applicable revised certification criteria, including the most recently adopted capabilities and standards.
4. Provide all Health IT Modules certified to a revised certification criterion to its customers of such certified health IT.
5. Update and provide these updates in a timely manner as specified.
6. For those certified to § 170.315(b)(11), starting January 1, 2025 and ongoing thereafter, review and update source attribute information, intervention risk management practices, and summary information.

Guide

03-11-2024

Communications

A health IT developer may not prohibit or restrict communication regarding the following subjects for Certified Health IT Modules:

1. The usability of its health IT,
2. The interoperability of its health IT,
3. The security of the health IT,
4. Relevant information regarding users’ experiences when using its health IT,
5. The business practices of developers of health IT related to exchanging EHI, and
6. The manner in which a user of the health IT has used such technology.

A health IT developer must:

1. Notify all customers it will not enforce any communication or contract provision contravening the Communication Conditions of Certification requirements annually, beginning in calendar year 2021, up to an until the health IT developer amends the contract or agreement to remove or void the contravening contractual provisions, and
2. Not establish, renew, or enforce any contract or agreement that contravenes the Communications Condition of Certification requirement, and must amend the contract or agreement when it is next modified for other reasons or renewed, as of June 30, 2020 to remove or void contravening contractual provisions. 

Guide

03-11-2024

Application Programming Interfaces (APIs)

A health IT developer of a Health IT Module certified to any certification criteria adopted in § 170.315(g)(7) through (g)(10) must:

1. Publish APIs and allow health information from such technology to be accessed, exchanged, and used without special effort,
2. Publish complete business and technical documentation, via a publicly accessible hyperlink,
3. Publish all terms and conditions for its certified API technology including material information and API Fees,
4. Abide by permitted/prohibited API fees and keep for inspection detailed records of any fees charged with respect to the certified API technology, and 
5. Abide by openness and pro-competitive conditions.

A health IT developer of a Health IT Module that meets the requirements outlined in the Condition of Certification must comply with the following requirements:

1. Authenticity verification and registration for production use,
2. Service Base Uniform Resource Locator (URL) and related organizational details publication by December 31, 2024,
3. Rollout of (g)(10)-Certified APIs by December 31, 2022, and
4. Compliance to API Conditions of Certification for existing certified API technology by April 5, 2021.

Guide

03-11-2024

Real World Testing

A health IT developer with Health IT Module(s) certified to § 170.315(b), (c)(1) through (3), (e)(1), (f), (g)(7) through (10), and (h) must: successfully test the real world use of the technology for interoperability in the type of setting in which such technology would be marketed.

A health IT developer that meets the requirements outlined in the Condition of Certification must:

1. Submit its Real World Testing plan to its ONC-Authorized Certification Body (ONC-ACB) by a date that enables the ONC-ACB to publish the plan on the Certified Health IT Products List (CHPL) no later than December 15 of each calendar year. Initial Real World Testing plans may be posted through December 15, 2021.
2. Report its Real World Testing results to its ONC-ACB by a date that enables the ONC-ACB to publish the results on the CHPL no later than March 15 of each calendar year. Results from initial Real World Testing from the 2022 performance year may be posted through March 15, 2023,

Standards Version Advancement Process

1. A health IT developer with health IT certified to § 170.315(b), (c)(1) through (3), (e)(1), (f), (g)(7) through (10), and/or (h) is permitted to update its certified health IT criteria to newer versions of standards than what has been incorporated by reference in § 170.299 if the newer versions of the standard(s) has been approved for use in the ONC Health IT Certification Program by the national coordinator.
2. A health IT developer seeking to have its health IT certified to § 170.315(b), (c)(1) through (3), (e)(1), (f), (g)(7) through (10), and/or (h) may certify to a newer version of any adopted standard(s) without first obtaining certification to the standard(s) and implementation specifications that have been incorporated by reference in § 170.299 if the newer version of the standard(s) has been approved for use in the ONC Health IT Certification Program by the National Coordinator.

Guide

03-11-2024

Attestation

A health IT developer must attest, as applicable, to compliance with the Conditions and Maintenance of Certification related to:

(1) Information Blocking,

(2) Assurances,

(3) Communications,

(4) API, and

(5) Real World Testing.

A health IT developer must submit their attestations every six months as of the first attestation window beginning on April 1, 2022.

Guide

03-11-2024

Insights Condition

A health IT developer must submit for each reporting period:

1. Responses for specified measures, and/or
2. An attestation response that it does not meet minimum reporting qualifications or have health IT certified to the criteria specified in each measure.

A health IT developer must provide responses to the Insights Condition of Certification annually for any Health IT Module that has or has had an active certification at any time under the Certification Program during the prior six months.

A health IT developer must provide responses for measures specified in:

1. § 170.407(a)(3)(i), (iii), (iv)(A) and (B), and (vi) of beginning July 2027;
2. § 170.407(a)(3)(ii)(A) through (C), (iv)(C), (v), (vi)(A) and (B), and (vii) of beginning July 2028; and
3. § 170.407 (a)(3)(ii)(D), (vii)(A) beginning July 2029.

Coming soon