2026 Standards Version Advancement Process (SVAP) Fact Sheet

This fact sheet describes the voluntary Standards Version Advancement Process (SVAP) available to Health IT developers participating in the ONC Health IT Certification Program (Certification Program). This resource assists Certified Health IT developers in understanding SVAP and their responsibilities if they choose to leverage this flexibility.

What is SVAP?

The ONC Cures Act Final Rule (Final Rule) established the voluntary Standards Version Advancement Process (SVAP) flexibility as part of the Real World Testing Condition and Maintenance of Certification (45 CFR 170.405). SVAP allows Certified Health IT developers participating in the ONC Health IT Certification Program (Certification Program) to voluntarily update their Certified Health IT Modules and to provide newer versions of standards to their customers prior to their adoption in regulation so long as certain conditions are met.

SVAP allows for advanced versions of standards to be approved for use under the Certification Program in a more timely and flexible manner than is possible for new versions of standards that are adopted through ONC rule making. It also gives Certified Health IT developers the ability to incorporate these new and more advanced standard versions into their Certified Health IT, which is essential to supporting real world interoperability.

The process to identify, approve, and make available newer versions of standards takes place on an annual cycle to keep pace with the industry’s standards development efforts. Working with stakeholders and providing ample notice, ONC’s collaborative public comment process seeks feedback each year on newer versions of eligible standards that are also ready for adoption in the Certification Program through the SVAP. For more information on the SVAP public comment process, please visit https://isp.healthit.gov/standards-version-advancement-process.

Approved SVAP versions are announced in June each year and become effective for Certification Program use after a 60-day period in August of that year.

Approved Standards for 2026

The SVAP flexibility is limited to the standards adopted in the certification criteria that meet the Real World Testing Condition and Maintenance of Certification requirement. As part of ONC’s review and assessment of the 2026 SVAP Cycle public comments, the newer versions of adopted standards listed in the table below have been approved for use in the Certification Program.

Table caption
2026 Approved SVAP StandardRegulatory Standard VersionCertification Criteria(on)
United States Core Data for Interoperability (USCDI), Version 6 United States Core Data for Interoperability (USCDI), October 2022 Errata, Version 3§ 170.315(b)(1) – Transitions of care;
§ 170.315(b)(2) – Clinical information reconciliation and incorporation;
§ 170.315(b)(11) – Decision Support Interventions
§ 170.315(e)(1) – View, download, and transmit to 3rd party;
§ 170.315(f)(5) – Transmission to public health agencies – electronic case reporting;
§ 170.315(g)(9) – Application access – all  data request;
§ 170.315(g)(10) – Standardized API for patient and population services
HL7® FHIR® US Core Implementation Guide STU 9.0.0, (June 2026) HL7® FHIR® US Core Implementation Guide STU 6.1.0 (June 19, 2023)§ 170.315(g)(10) – Standardized API for patient and population services
HL7® Consolidated CDA® (C-CDA), Release 5.0.0 – US Realm (June 2026)HL7® Implementation Guide for CDA® Release 2: Consolidated CDA Templates (C-CDA) for Clinical Notes (US Realm), Draft Standard for Trial Use, August 2015, June 2019 (with Errata) 
 
HL7® CDA® R2 Implementation Guide: C-CDA® Templates for Clinical Notes STU Companion Guide, Release 4.1 – US Realm, June 2023 
§ 170.315(b)(1) – Transitions of care;
§ 170.315(b)(2) – Clinical information reconciliation and incorporation;
§ 170.315(b)(9) – Care plan;
§ 170.315(e)(1) – View, download, and transmit to 3rd party;
§ 170.315(g)(9) – Application access – all data request
HL7® FHIR® Da Vinci – Coverage Requirements Discovery (CRD) Implementation Guide, Version 2.2.1—STU 2.2HL7® FHIR® Da Vinci – Coverage Requirements Discovery (CRD) Implementation Guide, Version 2.0.1—STU 2, January 8, 2024§ 170.315(g)(31) – Provider prior authorization API – coverage requirements discovery
HL7® FHIR® Da Vinci – Documentation Templates and Rules (DTR) Implementation Guide, Version 2.2.0—STU 2.2HL7® FHIR® Da Vinci – Documentation Templates and Rules (DTR) Implementation Guide, Version 2.0.1—STU 2, January 11, 2024§ 170.315(g)(32) – Provider prior authorization API -documentation templates and rules
HL7® FHIR® Da Vinci – Prior Authorization Support (PAS) FHIR Implementation Guide, Version 2.2.1—STU 2HL7® FHIR® Da Vinci – Prior Authorization Support (PAS) FHIR Implementation Guide, Version 2.0.1—STU 2, December 1, 2023§170.315(g)(33) – Provider prior authorization API – prior authorization support
2026 CMS QRDA I Implementation Guide for Hospital Quality Reporting (Updated May 2025)CMS Implementation Guide for Quality Reporting Document Architecture: Category I; Hospital Quality Reporting; Implementation Guide for 2020§ 170.315(c)(3) – Clinical quality measures (CQMs) — report
2026 CMS QRDA III Implementation Guide for Eligible Clinicians (Updated December 2025)CMS Implementation Guide for Quality Reporting Document Architecture: Category III; Eligible Clinicians and Eligible Professionals Programs; Implementation Guide for 2020§ 170.315(c)(3) – Clinical quality measures (CQMs) — report

Certified Health IT developers can begin voluntarily incorporating these standard versions on August 29, 2026.

To SVAP to a newer version of USCDI, a developer must conform to either the HL7® FHIR® US Core Implementation Guide (IG) or the HL7® CDA® R2 Implementation Guide: C-CDA® Templates for Clinical Notes R2.1 Companion Guide.

ONC will update all of the associated test data and tools, including the Cypress Testing Tool, the Edge Test Tool’s (ETT), C-CDA® validators, and the Inferno Framework’s “g.10 Standardized API Test Kit” by December 31, 2026.

How to Use SVAP

For the approved SVAP versions, Certified Health IT developers choosing to leverage the SVAP flexibility can do so on initial certification of their Health IT Module or to maintain certification for their Module. To take advantage of the flexibility to update to newer approved versions, a Certified Health IT developer will need to:

  • For existing certifications only, provide advance notice to all affected customers and their ONC-Authorized Certification Body (ONC-ACB), expressing
    • intent to update to the more advanced version of the standard;
    • expectations for how the update will affect interoperability of each affected Health IT Module; and
    • whether they intend to continue to support the certificate(s) for the existing Certified Health IT Module(s) version.
  • Successfully demonstrate conformance with approved more recent versions of the standard(s) included in each updated certification criterion to confirm they meet the updated requirements.
  • Maintain the updated Certified Health IT Module(s) in full conformance with all applicable Certification Program requirements, which includes ensuring their Real World Testing plans and results address the updated standards.

Unless ONC specifically excludes the use of additional data elements or electronic standards in rulemaking, there is nothing that prevents a health IT developer from supporting additional data elements, functionalities, or electronic standards in its health IT modules. This could include the partial support of any of the SVAP versions of standards or individual data classes or elements from an SVAP version of USCDI. However, health IT developers may not indicate that those modules are certified to such standards or data elements unless the health IT module provides full support for the entire SVAP version of the standard and the developer has taken all of the steps listed above. Only when all of the above steps have been completed will a health IT module be considered certified to an SVAP version of a standard and then subsequently updated on the Certified Health IT Product List (CHPL).

For more information on how to use SVAP in the Certification Program, please contact your ONC-ACB.

Previously Approved SVAP Standards

SVAP-approved standard versions will remain available across SVAP cycles for use unless they are superseded by regulatory action or another policy update. In the past, the Certification Program treated each annual SVAP cycle as time-limited, which constrained the availability of previously approved versions. Based on feedback and experience with several SVAP cycles, we believe supporting multiple versions of SVAP-approved standards will better serve industry and advance our shared goals, especially for standards that publish updates annually. As an example for the 2026 SVAP cycle, a Certified Health IT developer with a Health IT Module certified to the standardized API for patient and population services criterion at 45 CFR 170.315(g)(10) using HL7® FHIR® US Core Implementation Guide STU 6.1.0 may use SVAP to support later approved versions, including US Core STU 7.0.0, US Core STU 8.0.0, and now US Core STU 9.0.0.

SVAP Resources

  • SVAP: See the most recent list of Approved Standards for SVAP and operational information for certification.
  • SVAP Annual Process: View information on the annual process, including the list of standards versions being considered for the next Approved Standards List.
  • ONC Standards Bulletin: View and sign up for healthcare stakeholder alerts that include updates about ONC health IT standards initiatives such as the SVAP.
  • Certification Program Resources: Access reference documents and other resources related to ONC’s Health IT Certification Program.

Disclaimer

While every effort has been made to ensure the accuracy of restatements of 45 CFR Part 170, this resource is not a legal document. The official requirements are contained in the relevant laws and regulations.