Source: https://www.healthit.gov/topic/certification-ehrs/conditions-maintenance-certification
Timestamp: 2020-07-16 15:15:42
Document Index: 219030020

Matched Legal Cases: ['§ 171', '§170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170']

Conditions & Maintenance of Certification | HealthIT.gov
The 21st Century Cures Act (Section 4002) requires the Secretary of Health and Human Services (HHS) to establish Conditions and Maintenance of Certification requirements for the ONC Health IT Certification Program. ONC has finalized the Conditions and Maintenance of Certification requirements to express initial requirements and ongoing requirements for health IT developers and their certified Health IT Module(s). There are seven Conditions of Certification with accompanying Maintenance of Certification Requirements. We have not yet established an EHR Reporting Program for the seventh Conditions and Maintenance of Certification requirement; the EHR reporting criteria submission. Once we establish such program, we will undertake rulemaking to propose and implement the associated Condition and Maintenance of Certification requirements for health IT developers.
The Conditions and Maintenance of Certification requirements, except for the Information Blocking and Assurances Conditions and Maintenance of Certification requirements, apply only to actions and behaviors of health IT developers related to their certified health IT as well as to the certified health IT itself. The Information Blocking and Assurances Conditions and Maintenance of Certification require that a health IT developer is responsible to ensure that all of its health IT and related actions and behaviors do not constitute information blocking or inhibit the appropriate access, exchange, and use of electronic health information (EHI).
The Conditions and Maintenance of Certification requirements are defined in Subpart D of the 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program Final Rule (ONC Cures Act Final Rule).
Condition of Certification (CoC)
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.
There are no accompanying MoC requirements beyond compliance with the Condition.
A health IT developer must:
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,
Ensure full compliance and unrestricted implementation of certification criteria capabilities,
Not take any action to interfere with a user’s ability to access or use certified capabilities, and
Certify a health IT product which electronically stores EHI to the §170.315(b)(10) criteria.
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
Certify to the criterion in § 170.315(b)(10) within 36 months of May 1, 2020, if a health IT product electronically stores EHI.
A health IT developer may not prohibit or restrict communication regarding the following subjects for certified Health IT Modules:
The usability of its health IT,
The interoperability of its health IT,
The security of the health IT,
Relevant information regarding users’ experiences when using its health IT,
The business practices of developers of health IT related to exchanging EHI, and
Notify all customers within six months of the effective date that of the ONC Cures Act Final Rule that any communication or contract, or agreement provision that violates the Communication Condition of Certification will not be enforced by the health IT developer, and
Notify all customers annually up to and until the health IT developer amends the contract or agreement to remove or void any contractual provisions that violate the Condition of Certification.
A health IT developer of a Health IT Module certified to any certification criteria adopted in § 170.315(g)(7) through (g)(10) must:
Publish APIs and allow health information from such technology to be accessed, exchanged, and used without special effort,
Publish complete business and technical documentation, via a publicly accessible hyperlink,
Publish all terms and conditions for its certified API technology
API Fees,
Keep for inspection detailed records of any fees charged with respect to the certified API technology, and
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:
Authenticity verification and registration for production use,
Service Base Uniform Resource Locator (URL) publication,
Rollout of (g)(10)-Certified APIs, and
Transparency of Existing API Documentation.
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:
Submit its real world testing plan to its ONC-Authorized Certification Bodies (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,
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,
Update its certified health IT to be compliant to § 170.315(b)(1), (e)(1), (g)(6), (f)(5), and/or (g)(9) by the ONC Cures Act Final Rule's effective date and provide customers of previously certified health IT with certified health IT that meets § 170.315(b)(1), (e)(1), (g)(6), (f)(5), and/or (g)(9) no later than May 2, 2022,
Update its certified health IT to be compliant to § 170.315(b)(1), (b)(2), (b)(9), (e)(1), (g)(6), and/or (g)(9) and provide customers of previously certified health IT with certified health IT that meets § 170.315(b)(1), (b)(2), (b)(9), (e)(1), (g)(6), and/or (g)(9) no later than May 2, 2022,
Update its certified health IT to be compliant to § 170.315(b)(3) and provide customers of previously certified health IT with certified health IT that meets § 170.315(b)(3) no later than May 2, 2022, and
Update its certified health IT to be compliant to § 170.315(b)(7) and/or § 170.315(b)(8) and provide customers of previously certified health IT with certified health IT that meets § 170.315(b)(7) and/or § 170.315(b)(8) no later than May 2, 2022.
A health IT developer must attest, as applicable, to compliance with the Conditions and Maintenance of Certification related to:
(1) Information Blocking,
(2) Assurances,
(4) API, and
(5) Real World Testing.
A health IT developer must submit their attestations every six months.