Health data exchange standards named in federal rules
| Standard | Required by | For what | Date | Source |
|---|---|---|---|---|
| United States Core Data for Interoperability (USCDI) Version 31 | Required byONC Health IT Certification Program: 45 CFR 170.2131 | For whatData classes and elements; Medicare Advantage organizations' Patient Access API must share all data classes and elements in a 170.213 content standard that they maintain, within 1 business day of receipt2 | DateThe eCFR text current to 2026-11-12 says adoption of USCDI Version 1 expires on January 1, 2026; Version 3 is the other adopted version1 | Source45 CFR 170.213; 42 CFR 422.119(b)(1)(iii)1 |
| HL7 FHIR Release 4.0.1, the API base standard at 45 CFR 170.215(a)(1)3 | Required byCMS-0057-F: Medicare Advantage organizations' Provider Access and Payer-to-Payer APIs must conform to 45 CFR 170.215(a)(1), (b)(1)(i) and (d)(1); the Provider Access API also to (c)(1)4 | For whatSharing claims, encounter and clinical data with in-network providers unless the enrollee opts out, and with previous and concurrent payers when the enrollee opts in4 | DateBeginning January 1, 2027, for Medicare Advantage organizations4 | Source45 CFR 170.215(a)(1); 42 CFR 422.121(a) and (b)4 |
| US Core IG STU 3.1.1 and SMART Application Launch Framework 1.0.0 (45 CFR 170.215(b)(1)(i) and (c)(1)); the eCFR text says adoption of both expires on January 1, 20263 | Required byCMS-0057-F: the Prior Authorization API must conform to 45 CFR 170.215(a)(1), (b)(1)(i) and (c)(1)5 | For whatPrior Authorization API listing covered items and services that need prior authorization and the documentation required5 | DateONC's October 28, 2026 rule removes and reserves 170.215(b)(1)(i) and (c)(1); that part of the rule takes effect December 28, 20267 | Source42 CFR 422.122(b); ONC final rule, 91 FR 67916 (October 28, 2026)5 |
| Da Vinci Coverage Requirements Discovery 2.2.1, Documentation Templates and Rules 2.2.0 and Prior Authorization Support 2.2.1 IGs (versions adopted at 45 CFR 170.215(j))3 | Required byRecommended, not required, by CMS-0057-F; CMS said it may propose requiring these and other IGs in future rulemaking, should they reach sufficient maturity6 | For whatImplementing the Prior Authorization API6 | DatePrior Authorization API required beginning January 1, 2027, for Medicare Advantage organizations5 | SourceCMS-0057-F preamble, sections II.D, II.G.3.a and II.G.4 (Table H3); 45 CFR 170.215(j)6 |
| CARIN IG for Blue Button 2.2.0 and Da Vinci Payer Data Exchange (PDex) 2.1.0, with PDex US Drug Formulary and Plan Net IGs (versions adopted at 45 CFR 170.215(k), (m) and (n))3 | Required byRecommended, not required, by CMS-0057-F6 | For whatPatient Access, Provider Access, Provider Directory and Payer-to-Payer APIs, as applicable6 | DateMedicare Advantage Patient Access API required beginning January 1, 2021; prior authorization information added beginning January 1, 20272 | SourceCMS-0057-F preamble, sections II.G.3.a and II.G.4 (Table H3); 45 CFR 170.215(k), (m) and (n)6 |
| X12 278 Health Care Services Review, Request for Review and Response (005010X217)8 | Required byHIPAA transaction standards: 45 CFR 162.1302, for dental, professional and institutional request for review and response8 | For whatPrior authorization between HIPAA covered entities; under GL-2024-02 of February 28, 2024, HHS will not take enforcement action against covered entities that do not use X12 278 as part of an electronic FHIR prior authorization process under CMS-0057-F9 | DateCMS FAQ of June 13, 2024: the enforcement discretion has no specified end date and is expected to be bounded by a future rulemaking10 | Source45 CFR 162.1302; CMS guidance letter GL-2024-02 and FAQ of June 13, 20249 |
| Trusted Exchange Framework and Common Agreement (TEFCA), a nationwide framework for health information sharing whose network-of-networks is made up of Qualified Health Information Networks11 | Required byCMS-0057-F lets payers meet its requirements through TEFCA exchange where that is possible by the compliance dates, but says TEFCA participation does not necessarily meet them, since some TEFCA exchange methods do not use the required FHIR API standards6 | For whatInitial Exchange Purposes: treatment, payment, health care operations, public health, government benefits determination and individual access services11 | DateFirst Qualified Health Information Networks designated in December 202311 | SourceONC TEFCA page; CMS-0057-F preamble, section II.C11 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Method
We read the standards sections of 45 CFR parts 162 and 170 and the Medicare Advantage API sections of 42 CFR part 422 in the eCFR (text current to 2026-11-12, retrieved on 2026-11-14), the CMS-0057-F final rule and ONC's October 28, 2026 final rule on govinfo, CMS's enforcement discretion letter and FAQ, and ONC's TEFCA page. Date cells give Medicare Advantage dates only; Medicaid, CHIP and Exchange plan sections were not compared. Each cell was checked on 2026-11-14. This table explains the rules; it is not legal advice.
Notes
- 42 CFR 422.119(c)(4) lets Medicare Advantage organizations use updated versions of the 45 CFR 170.213 and 170.215 standards if, among other conditions, the National Coordinator has approved them for the ONC Health IT Certification Program.
Sources
- U.S. Department of Health and Human Services. 45 CFR 170.213, United States Core Data for Interoperability. Checked .
- Centers for Medicare & Medicaid Services. 42 CFR 422.119, Access to and exchange of health data and plan information. Checked .
- U.S. Department of Health and Human Services. 45 CFR 170.215, Application Programming Interface Standards. Checked .
- Centers for Medicare & Medicaid Services. 42 CFR 422.121, Access to and exchange of health data for providers and payers. Checked .
- Centers for Medicare & Medicaid Services. 42 CFR 422.122, Prior authorization requirements. Checked .
- Centers for Medicare & Medicaid Services. CMS Interoperability and Prior Authorization final rule, CMS-0057-F (89 FR 8758, February 8, 2024). Checked .
- U.S. Department of Health and Human Services. Health Data, Technology, and Interoperability: ONC Deregulatory Actions To Unleash Prosperity, final rule (91 FR 67916, October 28, 2026). Checked .
- U.S. Department of Health and Human Services. 45 CFR 162.1302, Standards for referral certification and authorization transaction. Checked .
- Centers for Medicare & Medicaid Services. Statement of Enforcement Discretion for Referral Certification and Authorization Transaction Standard at 45 CFR 162.1302 (GL-2024-02, February 28, 2024). Checked .
- Centers for Medicare & Medicaid Services. HIPAA Administrative Simplification FAQs: Statement of Enforcement Discretion for Referral Certification and Authorization Transaction Standard (June 13, 2024). Checked .
- Office of the National Coordinator for Health Information Technology. TEFCA. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.