ONC has established the voluntary Standards Version Advancement Process (SVAP)1 to enable health IT developers’ ability to incorporate newer versions of Secretary-adopted standards and implementation specifications, as part of the “Real World Testing” Condition and Maintenance of Certification requirement (§ 170.405) of the 21st Century Cures Act.
Using SVAP, certified health IT developers are permitted to voluntarily use a more advanced version of the standard(s) and implementation specification(s) approved by the National Coordinator than is adopted in the ONC 2015 Edition Certification Criteria. Currently, this flexibility is limited to standards and implementation specifications that are adopted in the certification criteria required to meet “Real World Testing” condition of certification, which include § 170.315(b), (c)(1) through (c)(3), (e)(1), (f), (g)(7) through (g)(10), and (h).
Health IT developers taking advantage of the SVAP flexibility must ensure that their real-world testing plans and results of the certified health modules use these updated standards and implementation specifications. Additionally, certified health IT developers are required to provide advance notice to their clients and their ONC-Authorized Certification Body (ONC-ACB) before adopting the new standards.
Working with industry stakeholders and providing ample notice, ONC will follow a collaborative process to identify a more advanced version of the standards or implementation specifications, for approval by the National Coordinator.
The table below lists the standards and implementation specifications (and their versions) that will be considered for advancement and those that have received National Coordinator approval via the Standards Version Advancement Process. It does not include any minimum vocabulary standards as health IT can continue to be certified or upgraded to newer version(s) of identified minimum standard code sets, unless newer version(s) are explicitly prohibited by the Secretary. The table can be sorted by either "Current Standard/Implementation Specification" or "Regulatory Text Citation" by clicking on the column name.
The table below will be updated throughout the year to include standards with newer versions under consideration for the current SVAP cycle. However, if there is a newer version of a standard and it’s not listed below it can still be considered for inclusion in the current SVAP cycle. As with previous SVAP cycles, future public comment periods will align with important standards development activities, such as the yearly release of new United States Core Data for Interoperability (USCDI) versions and HL7® standards related to C-CDA® and FHIR® US Core, thereby establishing a consistent cadence of SVAP comment periods and releases. The yearly SVAP comment cycle is open from January to May with a final release of SVAP approved standards for each year to occur in June. The public comment period for SVAP 2024 ran from January 16 through May 21.
The SVAP Approved Standards for 2024 are now published. For the latest information on the approved standards for use, see the ONC Health IT Certification Program SVAP page.
View / Comment | Current Standard / Implementation Specification listing in IBR (170.299) | Regulatory Text Citation for Standard / Implementation Specification Adopted Sort descending | Certification Criteria(on) References Standard / Implementation Specification | National Coordinator Approved Advanced Version(s) | View / Comment |
---|---|---|---|---|---|
§ 170.202(a)(2) |
|||||
§ 170.202(b) |
|||||
§ 170.202(d) |
|||||
§ 170.202(e)(1) |
|||||
§ 170.204(a)(1) |
|||||
§ 170.204(a)(2) |
|||||
§ 170.205(a)(3) |
|||||
§ 170.205(a)(4) |
|||||
§ 170.205(a)(4) |
|||||
§ 170.205(a)(5) |
|||||
§ 170.205(a)(6) |
|||||
§ 170.205(b)(1) |
|||||
§ 170.205(d)(4) |
|||||
§ 170.205(d)(4) |
|||||
§ 170.205(e)(4) |
|||||
§ 170.205(e)(4) |
|||||
§ 170.205(g) |
|||||
§ 170.205(g) |
|||||
§ 170.205(h)(2) |
|||||
§ 170.205(h)(3) |
|||||
§ 170.205(i)(2) |
|||||
§ 170.205(i)(2) |
|||||
§ 170.205(k)(3) |
|||||
§ 170.205(o)(1) |
|||||
§ 170.205(p)(1) |
|||||
§ 170.205(r)(1) |
|||||
§ 170.205(s)(1) |
|||||
§ 170.205(s)(1) |
|||||
§ 170.213 |
|||||
§ 170.213 |
|||||
§ 170.215(a)(1) |
|||||
§ 170.215(a)(3) |
|||||
§ 170.215(a)(3) |
|||||
§ 170.215(a)(4) |
|||||
§ 170.215(b) |
|||||
§ 170.215(b)(1) |
|||||
§ 170.215(b)(1) |
1SVAP is permitted in ONC’s 21st Century Cures Act Final Rule in the Real World Testing CoC/MoC: § 170.405(b)(7) and (8) and ONC-ACB PoPC §170.523(t)
Comment
Submitted by FEHRMSVAP51 on
FEHRM Comments
The Federal Electronic Health Records Modernization (FEHRM) Program appreciates the opportunity to review and provide feedback on ONC’s 2024 SVAP. The FEHRM understands that the SVAP allows developers to incorporate newer digital health standards. The FEHRM reviewed the list of new standard versions under consideration and supports advancing:
United States Core Data for Interoperability (USCDI) version 4
Consolidated Clinical Document Architecture (C-CDA) Release 3
US Core 7.0.0
We appreciate the opportunity to comment on the SVAP. Please feel free to contact us if you have any questions or would like any further information.
Submitted by alec-matulka on
Epic Comments on SVAP 2024
Please see the attached document with Epic's feedback on SVAP 2024. Thank you for your consideration.
Submitted by Solarf3050 on
Health Level Seven SVAP Comments
Attached are the comments from Health Level Seven International on ONC’s Standards Version Advancement Process (SVAP). Thank you for the opportunity to provide feedback!
Submitted by Amanda Deering on
CDC/NIOSH - SVAP Comments 2024
Please see attached comments for consideration.
Submitted by chris.baumgart… on
WA State Department of Health - SVAP Comments
Please find attached our comments for the 2024 SVAP.
Submitted by Toni Wilken on
MEDITECH Comments on 2024 SVAP
On behalf of Medical Information Technology, Inc. (MEDITECH), thank you for the opportunity to provide feedback. Please see the attached comment letter on the 2024 Standards Version Advancement Process (SVAP).
Submitted by knicholoff@ehra.org on
EHR Association Comments on 2024 SVAP
On behalf of our 29 member companies, the HIMSS Electronic Health Record (EHR) Association appreciates the opportunity to provide feedback to the ONC on the 2024 Standards Version Advancement Process (SVAP). Our comments are attached.
Submitted by Prachi on
Request to include HL7 CDA V3.1 IG into the HCS SVAP
We would like to advocate to add HL7 CDA® R2 Implementation Guide: National Health Care Surveys (NHCS), R1 STU Release 3.1 - US Realm as a recognized standard under SVAP for National Health Care Surveys. This way, data collected for health care surveys reflects the latest thoughts in the content and structure as advocated by NCHS, CDC and the HL7 standards body.
Submitted by brett@waveonea… on
HL7 FHIR® SMART Application Launch Framework v2.1.0
Please update the HL7 FHIR® SMART Application Launch Framework to v2.1.0 published April 28, 2023. There is an incompatibility in how SMART's "fhirContext" launch parameter is used in 2.0.0 vs 2.1.0. It would be best for all servers and clients to adopt the latest version before this incompatibility is deployed requiring servers/clients to support two formats.
Alternatively, we expect SMART v2.2.0 to be published in April/May 2024. This verson could also be considered.
Submitted by Cardiac Imaging Inc. on
This is a great resource!!
The Standards Version Advancement Process (SVAP) is a crucial step in improving healthcare IT systems and ensuring they meet the latest standards. It's exciting to see such a structured approach to enhancing interoperability and advancing technology for better patient care. Kudos to the team for providing this clear and informative guide!