The certification criteria a buyer can look up are in 45 CFR 170.315 [1]. The office that publishes them now signs rules as the Assistant Secretary for Technology Policy and the Office of the National Coordinator for Health Information Technology, together ASTP/ONC [4]. The Medicare and Medicaid EHR Incentive Programs were established in 2011 under the HITECH Act [5]. For eligible hospitals and critical access hospitals, CMS continues that work as the Medicare Promoting Interoperability Program, which uses certified electronic health record technology [5]. The Medicaid Promoting Interoperability Program ended on December 31, 2021 [5]. Eligible clinicians report a Promoting Interoperability category inside the Merit-based Incentive Payment System [5]. Certification is a set of criteria on a product listing. It is not a general duty that every behavioral health program buy a certified product.
Criteria that are easy to misread
Decision support is no longer the old clinical decision support criterion. The HTI-1 final rule adopted decision support interventions at § 170.315(b)(11) as the replacement for the clinical decision support criterion at § 170.315(a)(9) [2]. Through December 31, 2024, the Base EHR definition in 45 CFR 170.102 included § 170.315(a)(9) or § 170.315(b)(11) [10]. On and after January 1, 2025, that definition includes § 170.315(b)(11) and does not include § 170.315(a)(9) [10]. It still includes the other criteria in paragraph (3)(i), and it adds § 170.315(b)(4) on and after January 1, 2028 [10]. The text of § 170.315(a)(9) is still in that section, and its adoption for the ONC Health IT Certification Program expired on January 1, 2025 [1]. The current (b)(11) text requires source attributes for evidence-based interventions and for predictive decision support interventions [1].
Order entry and care-coordination criteria sit in different paragraphs. Computerized provider order entry is certified under § 170.315(a)(1) for medications, (a)(2) for laboratory, and (a)(3) for diagnostic imaging [1]. Section 170.315(b)(1) is transitions of care, (b)(2) is clinical information reconciliation and incorporation, and (b)(3) is electronic prescribing [1].
The adopted USCDI version, as of this review, is version 3. Section 170.213 adopts United States Core Data for Interoperability version 1, and that adoption expired on January 1, 2026 [3]. The same section adopts USCDI version 3 [3]. Read the current section before you accept a vendor’s claim about a later version.
A December 2025 proposal would remove or revise criteria. It is not the rule. On December 29, 2025, ASTP/ONC published a proposed rule, 90 FR 60970, that would remove and revise certain certification criteria and information-blocking provisions [4]. Comments were due by February 27, 2026 [4]. As of September 2026, that document is still a proposed rule. Buy against the criteria in the current Code of Federal Regulations, and check the Federal Register again before you treat the proposal as final.
Part 2 records and information blocking
A single consent for treatment, payment, and health care operations lets a Part 2 program, covered entity, or business associate use and disclose Part 2 records for those purposes as the HIPAA regulations permit, until the patient revokes it in writing [7]. That rule applies to Part 2 program records. It is not a rule that every behavioral health note needs its own consent before an API can return it.
If a privacy law requires a precondition, such as a consent, that has not been satisfied, an actor’s refusal to fulfill a request for electronic health information is not information blocking when the practice meets the privacy exception [8]. If the actor cannot unambiguously segment the requested electronic health information from electronic health information that applicable law does not permit to be made available, or that may be withheld under § 171.201, § 171.202, or § 171.206, the infeasibility exception can apply [9]. When the actor does not fulfill the request for a reason in that section, it must, within ten business days of receiving the request, tell the requestor in writing why the request is infeasible [9]. Whether a given interface can do that segmentation is a product question. It is not a fact about every FHIR server.
How to check a product before you sign
Look the product up on the Certified Health IT Product List and read which criteria the listing actually shows [6]. Ask which version of USCDI the module is certified to, whether decision support is certified to § 170.315(b)(11), and how the vendor documents a refusal that relies on the privacy or infeasibility exception. A marketing page that says the product is “certified” without a CHPL listing is not the listing.
Encore OS is not an EHR and is not ONC-certified. Encore OS provides FHIR R4 and US Core data access. That is not a certification.
Sources
- 45 CFR 170.315: Certification criteria, eCFR. Accessed September 29, 2026.
- Health Data, Technology, and Interoperability: Certification Program Updates, Algorithm Transparency, and Information Sharing (HTI-1 final rule), HHS, Federal Register. Accessed September 28, 2026.
- 45 CFR 170.213: United States Core Data for Interoperability, eCFR. Accessed September 28, 2026.
- Health Data, Technology, and Interoperability: ASTP/ONC Deregulatory Actions To Unleash Prosperity (proposed rule, 90 FR 60970), HHS, Federal Register. Accessed September 28, 2026.
- Medicare Promoting Interoperability Program, CMS. Accessed September 28, 2026.
- Certified Health IT Product List (CHPL), ASTP/ONC. Accessed September 28, 2026.
- 42 CFR 2.33: Uses and disclosures permitted with written consent, eCFR. Accessed September 28, 2026.
- 45 CFR 171.202: Privacy exception, eCFR. Accessed September 28, 2026.
- 45 CFR 171.204: Infeasibility exception, eCFR. Accessed September 28, 2026.
- 45 CFR 170.102: Definitions, including Base EHR, eCFR. Accessed September 28, 2026.