ONC Certification

Medi-EHR is certified health IT under the ONC Health IT Certification Program. Medi-EHR version 2.1 holds certificate number 15.02.05.2979.MEDI.02.02.1.260225_6, originally certified on February 25, 2026 and updated on June 15, 2026. The certification covers 41 criteria under 45 CFR 170.315 and six electronic clinical quality measures, tested and certified by an ONC-Authorized Certification Body.

That certificate is what allows a practice using Medi-EHR to meet the Certified Electronic Health Record Technology (CEHRT) requirement in federal programs. If your practice reports to MIPS, participates in an ACO or an alternative payment model, or attests to Promoting Interoperability, this is the page your compliance team is looking for.

Official certification documents

View this listing on the Certified Health IT Product List (CHPL), or download the certificate as a PDF.

Why ONC certification matters when you choose an EHR

Certification is not a marketing badge. It is a tested, audited assertion that specific software functions behave the way federal regulation requires. An ONC-ACB puts the product through conformance testing against each criterion separately, and the resulting certificate is published publicly on the Certified Health IT Product List (CHPL).

For a practice, three things follow from that:

• Federal program eligibility. MIPS Promoting Interoperability performance, ACO participation, and most alternative payment models require certified technology. Uncertified software disqualifies the reporting, not just the vendor.
• Data portability is guaranteed, not promised. Criterion 170.315(b)(10) requires certified systems to export a patient’s full electronic health information in a documented format. Your data can leave, on your terms.
• Security controls are tested, not asserted. The (d) series covers authentication, encryption, audit logging, automatic timeout, and multi-factor authentication, each verified independently.

What Medi-EHR is certified for

Medi-EHR 2.1 is certified against the following criteria. Grouped by what they do rather than by regulatory subsection:

Clinical care and ordering

• 170.315(a)(1) Computerized provider order entry – medications
• 170.315(a)(2) Computerized provider order entry – laboratory
• 170.315(a)(3) Computerized provider order entry – diagnostic imaging
• 170.315(a)(4) Drug-drug and drug-allergy interaction checks for CPOE
• 170.315(a)(5) Demographics
• 170.315(a)(12) Family health history
• 170.315(a)(14) Implantable device list
• 170.315(b)(11) Decision support interventions

Care coordination and exchange

• 170.315(b)(1) Transition of care
• 170.315(b)(2) Clinical information reconciliation and incorporation
• 170.315(b)(3) Electronic prescribing
• 170.315(b)(7) Security tags – summary of care, send
• 170.315(b)(8) Security tags – summary of care, receive
• 170.315(b)(10) Electronic health information (EHI) export
• 170.315(h)(1) Direct Project

Quality measurement

• 170.315(c)(1) Clinical quality measures – record and export
• 170.315(c)(2) Clinical quality measures – import and calculate
• 170.315(c)(3) Clinical quality measures – report
• 170.315(g)(2) Automated measure calculation

Privacy and security

• 170.315(d)(1) Authentication, access control, and authorization
• 170.315(d)(2) Auditable events and tamper-resistance
• 170.315(d)(3) Audit reports, conformant to ASTM E2147-18
• 170.315(d)(4) Amendments
• 170.315(d)(5) Automatic access timeout
• 170.315(d)(6) Emergency access
• 170.315(d)(7) End-user device encryption
• 170.315(d)(8) Integrity
• 170.315(d)(9) Trusted connection
• 170.315(d)(12) Encrypt authentication credentials
• 170.315(d)(13) Multi-factor authentication

Patient access and public health

• 170.315(e)(1) View, download, and transmit to third party
• 170.315(f)(1) Transmission to immunization registries
• 170.315(f)(2) Transmission to public health agencies – syndromic surveillance
• 170.315(f)(5) Transmission to public health agencies – electronic case reporting

APIs and design

• 170.315(g)(3) Safety-enhanced design
• 170.315(g)(4) Quality management system
• 170.315(g)(5) Accessibility-centered design
• 170.315(g)(6) Consolidated CDA creation performance
• 170.315(g)(7) Application access – patient selection
• 170.315(g)(9) Application access – all data request
• 170.315(g)(10) Standardized API for patient and population services

Criterion 170.315(g)(10) is the standardized HL7 FHIR API required for patient and population data access. Medi-EHR publishes that API openly, with developer documentation available through our developer portal.

Certified clinical quality measures

Medi-EHR is certified to record, calculate, and report the following eCQMs:

• CMS68 – Documentation of current medications in the medical record
• CMS69 – Preventive care and screening: body mass index (BMI) screening and follow-up plan
• CMS125 – Breast cancer screening
• CMS130 – Colorectal cancer screening
• CMS138 – Preventive care and screening: tobacco use, screening and cessation intervention
• CMS165 – Controlling high blood pressure

Real World Testing

Certified health IT developers are required to demonstrate that certified capabilities work in real production settings, not only in a test lab. Medi-EHR publishes a Real World Testing plan and results annually. Plans and results for 2023, 2024, and 2025 are available on our Real World Testing page.

Cost transparency

ONC certification requires developers to disclose costs and limitations that a buyer might not otherwise anticipate. Medi-EHR publishes these in full. In summary: data migration from a prior EHR may carry additional cost depending on volume, format, and complexity; standard data export on departure is included, while a custom export from a non-standard environment carries a fee; and interfaces to outside labs, EMRs, or other systems are quoted individually. Full disclosures are published on our transparency page.

Frequently asked questions

Is Medi-EHR ONC certified?

Yes. Medi-EHR version 2.1 is certified under the ONC Health IT Certification Program, certificate number 15.02.05.2979.MEDI.02.02.1.260225_6, certified February 25, 2026 and updated June 15, 2026.

Where can I verify Medi-EHR’s certification independently?

Every certification is published on the Certified Health IT Product List (CHPL), maintained by ASTP/ONC. You can search for Medi-EHR there and view the full criteria list, test results, and certification history without taking our word for any of it.

Does Medi-EHR meet CEHRT requirements for MIPS?

Yes. Medi-EHR is certified health IT and meets the CEHRT definition used by CMS for MIPS Promoting Interoperability, ACO participation, and alternative payment models. Practices remain responsible for their own reporting and attestation.

Can I export my data if I leave Medi-EHR?

Yes. Medi-EHR is certified for 170.315(b)(10), electronic health information export, which covers both single-patient and full-population export in documented standard formats. Standard export is included. A custom export from a non-standard environment may carry an additional fee.

Does Medi-EHR offer a FHIR API?

Yes. Medi-EHR is certified for 170.315(g)(10), the standardized API for patient and population services, built on HL7 FHIR. Documentation is published openly through our developer portal and the public FHIR API page.

How often is the certification updated?

Certification is maintained continuously against current regulation. Medi-EHR’s certificate was most recently updated on June 15, 2026. Developers are required to keep certified capabilities current as ONC adopts new criteria, including the updates required under the HTI-1 final rule.

Talk to us about certification requirements

If you are evaluating EHRs against a federal program requirement, or replacing a system that lost certification, we can walk through exactly which criteria your program requires and how Medi-EHR maps to them.

This Health IT Module is compliant with the ONC Certification Criteria for Health IT and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.

Additional software relied upon: EMR Direct.