<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agriculture
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Rural Business-Cooperative Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17243-17244</PGS>
                    <FRDOCBP>2026-06590</FRDOCBP>
                      
                    <FRDOCBP>2026-06591</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17260</PGS>
                    <FRDOCBP>2026-06579</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Disease</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee on Immunization Practices, </SJDOC>
                    <PGS>17279-17280</PGS>
                    <FRDOCBP>2026-06577</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Medicare Program:</SJ>
                <SJDENT>
                    <SJDOC>Contract Year 2027 and Certain Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program, </SJDOC>
                    <PGS>17384-17602</PGS>
                    <FRDOCBP>2026-06600</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Medicare Program:</SJ>
                <SJDENT>
                    <SJDOC>Fiscal Year 2027 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Program Requirements, </SJDOC>
                    <PGS>17338-17382</PGS>
                    <FRDOCBP>2026-06604</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Inpatient Rehabilitation Facility Prospective Payment System for Federal Fiscal Year 2027 and Updates to the IRF Quality Reporting Program, </SJDOC>
                    <PGS>17195-17230</PGS>
                    <FRDOCBP>2026-06642</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17280-17281, 17283-17284</PGS>
                    <FRDOCBP>2026-06570</FRDOCBP>
                      
                    <FRDOCBP>2026-06573</FRDOCBP>
                </DOCENT>
                <SJ>Medicare Program:</SJ>
                <SJDENT>
                    <SJDOC>Delayed Implementation of Certain Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction Model, </SJDOC>
                    <PGS>17282</PGS>
                    <FRDOCBP>2026-06616</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Implementation of Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction Model; Correction, </SJDOC>
                    <PGS>17282-17283</PGS>
                    <FRDOCBP>2026-06617</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Public Data Asset Release Under the Open, Public, Electronic, and Necessary (OPEN) Government Data Act, </DOC>
                    <PGS>17281-17282</PGS>
                    <FRDOCBP>2026-06618</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Children</EAR>
            <HD>Children and Families Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Reducing Bureaucracy and Burden for Children, Youth, and Family Programs, </DOC>
                    <PGS>17235-17239</PGS>
                    <FRDOCBP>2026-06646</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Reducing Bureaucracy and Burden in Family Violence and Prevention Services, </DOC>
                    <PGS>17239-17242</PGS>
                    <FRDOCBP>2026-06633</FRDOCBP>
                </DOCENT>
                <SJ>Work Participation Rate Calculation Changes:</SJ>
                <SJDENT>
                    <SJDOC>Recalibration of the Caseload Reduction Credit and Prohibition of Small Checks in Work Participation Rate Calculation, </SJDOC>
                    <PGS>17230-17235</PGS>
                    <FRDOCBP>2026-06632</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>New Jersey Advisory Committee, </SJDOC>
                    <PGS>17245</PGS>
                    <FRDOCBP>2026-06659</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>West Virginia Advisory Committee, </SJDOC>
                    <PGS>17244-17245</PGS>
                    <FRDOCBP>2026-06639</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Special Local Regulation:</SJ>
                <SJDENT>
                    <SJDOC>4th of July Fireworks, East River and Upper New York Bay, Manhattan, Queens, and Brooklyn, NY, </SJDOC>
                    <PGS>17170-17176</PGS>
                    <FRDOCBP>2026-06619</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Comptroller</EAR>
            <HD>Comptroller of the Currency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Privacy of Consumer Financial Information, </SJDOC>
                    <PGS>17331-17332</PGS>
                    <FRDOCBP>2026-06558</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Army Department</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17260-17261</PGS>
                    <FRDOCBP>2026-06582</FRDOCBP>
                </DOCENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Department of Defense Wage Committee, </SJDOC>
                    <PGS>17261-17264</PGS>
                    <FRDOCBP>2026-06645</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Pre-Implementation Planning Checklist for State Unemployment Insurance Information Technology Modernization Projects, </SJDOC>
                    <PGS>17308-17309</PGS>
                    <FRDOCBP>2026-06595</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Energy Information Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Energy Information</EAR>
            <HD>Energy Information Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17264-17265</PGS>
                    <FRDOCBP>2026-06593</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air Quality State Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>Arizona; Phoenix-Mesa Nonattainment Area; Determination of Attainment by the Attainment Date but for International Emissions for the 2015 Ozone National Ambient Air Quality Standards, </SJDOC>
                    <PGS>17144</PGS>
                    <FRDOCBP>C1-2026-05601</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Drinking Water Contaminant Candidate List 6-Draft, </DOC>
                    <PGS>17186-17195</PGS>
                    <FRDOCBP>2026-06662</FRDOCBP>
                    <PRTPAGE P="iv"/>
                </DOCENT>
                <SJ>Protection of Stratospheric Ozone:</SJ>
                <SJDENT>
                    <SJDOC>Listing of Substitutes under the Significant New Alternatives Policy Program in Refrigeration and Air Conditioning and Fire Suppression, </SJDOC>
                    <PGS>17176-17186</PGS>
                    <FRDOCBP>2026-06665</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Access to Confidential Business Information:</SJ>
                <SJDENT>
                    <SJDOC>Deaf Access Solutions, Inc., </SJDOC>
                    <PGS>17273-17274</PGS>
                    <FRDOCBP>2026-06585</FRDOCBP>
                      
                    <FRDOCBP>2026-06586</FRDOCBP>
                </SJDENT>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Establishing No-Discharge Zones Under Clean Water Act Section 312 (Renewal), </SJDOC>
                    <PGS>17272-17273</PGS>
                    <FRDOCBP>2026-06588</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airspace Designations and Reporting Points:</SJ>
                <SJDENT>
                    <SJDOC>Birch Creek Airport, Birch Creek, AK, </SJDOC>
                    <PGS>17143</PGS>
                    <FRDOCBP>2026-06625</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Airplanes, </SJDOC>
                    <PGS>17129-17132</PGS>
                    <FRDOCBP>2026-06628</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Airbus Helicopters, </SJDOC>
                    <PGS>17135-17137, 17141-17143</PGS>
                    <FRDOCBP>2026-06621</FRDOCBP>
                      
                    <FRDOCBP>2026-06622</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Baykar Piaggio Aerospace S.p.A. (Type Certificate Previously Held by Piaggio Aviation S.p.A.) Airplanes, </SJDOC>
                    <PGS>17132-17135</PGS>
                    <FRDOCBP>2026-06599</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Dassault Aviation Airplanes, </SJDOC>
                    <PGS>17137-17141</PGS>
                    <FRDOCBP>2026-06627</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airspace Designations and Reporting Points:</SJ>
                <SJDENT>
                    <SJDOC>Dover, OH, </SJDOC>
                    <PGS>17164-17165</PGS>
                    <FRDOCBP>2026-06574</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Pilatus Aircraft Ltd. Airplanes, </SJDOC>
                    <PGS>17161-17164</PGS>
                    <FRDOCBP>2026-06605</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17274-17275, 17277-17278</PGS>
                    <FRDOCBP>2026-06655</FRDOCBP>
                      
                    <FRDOCBP>2026-06656</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Prohibiting Importation and Marketing of Previously Authorized Covered Communications Equipment Added to the Covered List in 2024 or Earlier, </DOC>
                    <PGS>17275-17276</PGS>
                    <FRDOCBP>2026-06653</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Big Wood Canal Co., </SJDOC>
                    <PGS>17271</PGS>
                    <FRDOCBP>2026-06637</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>17265-17269</PGS>
                    <FRDOCBP>2026-06634</FRDOCBP>
                      
                    <FRDOCBP>2026-06636</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Gulf South Pipeline Co., LLC, Texas Gas Transmission, LLC, Kosciusko Junction Pipeline Project, </SJDOC>
                    <PGS>17269-17270</PGS>
                    <FRDOCBP>2026-06635</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Motor</EAR>
            <HD>Federal Motor Carrier Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Quantifying the Benefits of Creating New Truck Parking Spaces, </SJDOC>
                    <PGS>17324-17326</PGS>
                    <FRDOCBP>2026-06597</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Change in Bank Control:</SJ>
                <SJDENT>
                    <SJDOC>Acquisitions of Shares of a Bank or Bank Holding Company; Correction, </SJDOC>
                    <PGS>17278</PGS>
                    <FRDOCBP>2026-06643</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>17278-17279</PGS>
                    <FRDOCBP>2026-06644</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Endangered and Threatened Species; Implementation of the Gray Wolf (Canis lupus) Nonessential Experimental Population Rule in Colorado, </SJDOC>
                    <PGS>17297-17299</PGS>
                    <FRDOCBP>2026-06638</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Drug Products Not Withdrawn From Sale for Reasons of Safety or Effectiveness:</SJ>
                <SJDENT>
                    <SJDOC>STRATTERA (Atomoxetine Hydrochloride) Capsules 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams, </SJDOC>
                    <PGS>17285-17286</PGS>
                    <FRDOCBP>2026-06661</FRDOCBP>
                </SJDENT>
                <SJ>Regional Data Elements and Implementation Schedule:</SJ>
                <SJDENT>
                    <SJDOC>Electronic Submission of Postmarketing Individual Case Safety Reports to the Food and Drug Administration Adverse Event Monitoring System Using International Council of Harmonisation E2B(R3) Data Standards, </SJDOC>
                    <PGS>17284-17285</PGS>
                    <FRDOCBP>2026-06660</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Production Activity:</SJ>
                <SJDENT>
                    <SJDOC>Turbocam Inc., Foreign-Trade Zone 21, Ladson, SC, </SJDOC>
                    <PGS>17245-17246</PGS>
                    <FRDOCBP>2026-06562</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Children and Families Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Guidance:</SJ>
                <SJDENT>
                    <SJDOC>Fair Housing and Equal Opportunity; Withdrawal, </SJDOC>
                    <PGS>17291-17292</PGS>
                    <FRDOCBP>2026-06624</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>17290-17297</PGS>
                    <FRDOCBP>2026-06606</FRDOCBP>
                      
                    <FRDOCBP>2026-06607</FRDOCBP>
                      
                    <FRDOCBP>2026-06609</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>National Environmental Policy Act Implementing Procedures for the Bureau of Land Management, </DOC>
                    <PGS>17299-17305</PGS>
                    <FRDOCBP>2026-06602</FRDOCBP>
                      
                    <FRDOCBP>2026-06603</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>17333</PGS>
                    <FRDOCBP>2026-06611</FRDOCBP>
                </DOCENT>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Rules for Certain Rental Real Estate Activities, </SJDOC>
                    <PGS>17332-17333</PGS>
                    <FRDOCBP>2026-06592</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Float Glass Products From the People's Republic of China, </SJDOC>
                    <PGS>17250-17253</PGS>
                    <FRDOCBP>2026-06647</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="v"/>
                    <SJDOC>Float Glass Products From the People's Republic of China and Malaysia, </SJDOC>
                    <PGS>17253-17256</PGS>
                    <FRDOCBP>2026-06649</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Polyethylene Retail Carrier Bags From the People's Republic of China, </SJDOC>
                    <PGS>17247-17250</PGS>
                    <FRDOCBP>2026-06560</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Sodium Nitrite From India; Correction, </SJDOC>
                    <PGS>17253</PGS>
                    <FRDOCBP>2026-06561</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Steel Concrete Reinforcing Bar From the Republic of Turkiye, </SJDOC>
                    <PGS>17246-17247</PGS>
                    <FRDOCBP>2026-06559</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Certain Display Devices, Streaming Players, and Components Thereof, </SJDOC>
                    <PGS>17305-17306</PGS>
                    <FRDOCBP>2026-06580</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Certain Ink Cartridges and Components Thereof II, </SJDOC>
                    <PGS>17307-17308</PGS>
                    <FRDOCBP>2026-06575</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Non-Oriented Electrical Steel From China, Germany, Japan, South Korea, Sweden, and Taiwan, </SJDOC>
                    <PGS>17306-17307</PGS>
                    <FRDOCBP>2026-06576</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Mine Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Occupational Safety and Health Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Application for Use of Public Space by Non-Department of Labor Agencies in the Frances Perkins Building, </SJDOC>
                    <PGS>17309-17310</PGS>
                    <FRDOCBP>2026-06594</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Withdrawal Application:</SJ>
                <SJDENT>
                    <SJDOC>Upper Pecos River Watershed Protection Area, New Mexico; Cancellation, </SJDOC>
                    <PGS>17305</PGS>
                    <FRDOCBP>2026-06658</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Maritime</EAR>
            <HD>Maritime Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Icebreaker Collaboration Effort Pact, </SJDOC>
                    <PGS>17326-17327</PGS>
                    <FRDOCBP>2026-06648</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Mine</EAR>
            <HD>Mine Safety and Health Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Lowering Miners' Exposure to Respirable Crystalline Silica and Improving Respiratory Protection, </DOC>
                    <PGS>17143-17144</PGS>
                    <FRDOCBP>2026-06584</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Motor Vehicle Safety Standards:</SJ>
                <SJDENT>
                    <SJDOC>Occupant Crash Protection, Seat Belt Reminder Systems, </SJDOC>
                    <PGS>17144-17159</PGS>
                    <FRDOCBP>2026-06614</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Initial Decision That Certain Frontal Driver Air Bag Inflators Contain a Safety Defect:</SJ>
                <SJDENT>
                    <SJDOC>Jilin Province Detiannuo Safety Technology Co., Ltd. (DTN), </SJDOC>
                    <PGS>17327-17331</PGS>
                    <FRDOCBP>2026-06620</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Hazardous Waste Worker Training, </SJDOC>
                    <PGS>17286</PGS>
                    <FRDOCBP>C1-2026-05238</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>17286-17290</PGS>
                    <FRDOCBP>2026-06650</FRDOCBP>
                      
                    <FRDOCBP>2026-06651</FRDOCBP>
                      
                    <FRDOCBP>2026-06654</FRDOCBP>
                      
                    <FRDOCBP>2026-06657</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Modifications To Conform U.S. Fishery Regulations With the Presidential Proclamation Unleashing Commercial Fishing in the Atlantic, </DOC>
                    <PGS>17159-17160</PGS>
                    <FRDOCBP>2026-06663</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Fisheries of the South Atlantic; Southeast Data, Assessment, and Review, </SJDOC>
                    <PGS>17256-17257</PGS>
                    <FRDOCBP>2026-06613</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Mid-Atlantic Fishery Management Council, </SJDOC>
                    <PGS>17257</PGS>
                    <FRDOCBP>2026-06612</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>South Atlantic Fishery Management Council, </SJDOC>
                    <PGS>17259-17260</PGS>
                    <FRDOCBP>2026-06615</FRDOCBP>
                </SJDENT>
                <SJ>Initiation of Review of Management Plan:</SJ>
                <SJDENT>
                    <SJDOC>Flower Garden Banks National Marine Sanctuary, </SJDOC>
                    <PGS>17257-17259</PGS>
                    <FRDOCBP>2026-06587</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Tennessee Valley Authority, Clinch River Nuclear Site, Unit 1, </SJDOC>
                    <PGS>17312-17313</PGS>
                    <FRDOCBP>2026-06571</FRDOCBP>
                </SJDENT>
                <SJ>Licenses; Exemptions, Applications, Amendments, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Gas and Electric Co., Diablo Canyon Nuclear Power Plant, Units 1 and 2; Record of Decision, </SJDOC>
                    <PGS>17310-17312</PGS>
                    <FRDOCBP>2026-06641</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Occupational Safety Health Adm</EAR>
            <HD>Occupational Safety and Health Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Walking-Working Surfaces, </DOC>
                    <PGS>17165-17170</PGS>
                    <FRDOCBP>2026-06578</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Regulatory</EAR>
            <HD>Postal Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>New Postal Products, </DOC>
                    <PGS>17313</PGS>
                    <FRDOCBP>2026-06598</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Rural Business</EAR>
            <HD>Rural Business-Cooperative Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Funding Opportunity:</SJ>
                <SJDENT>
                    <SJDOC>Delta Health Care Services Grant for Fiscal Year 2026, </SJDOC>
                    <PGS>17244</PGS>
                    <FRDOCBP>2026-06623</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Order:</SJ>
                <SJDENT>
                    <SJDOC>Limited Exemptions Under the Securities Exchange Act, </SJDOC>
                    <PGS>17313-17318</PGS>
                    <FRDOCBP>2026-06569</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>NYSE American LLC, </SJDOC>
                    <PGS>17318-17320</PGS>
                    <FRDOCBP>2026-06567</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>17320-17322</PGS>
                    <FRDOCBP>2026-06568</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Annual Brokering Report, </SJDOC>
                    <PGS>17324</PGS>
                    <FRDOCBP>2026-06631</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Brokering Prior Approval (License), </SJDOC>
                    <PGS>17323</PGS>
                    <FRDOCBP>2026-06630</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Foreign Assistance Requirements, </SJDOC>
                    <PGS>17322-17323</PGS>
                    <FRDOCBP>2026-06640</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Release of Waybill Data, </DOC>
                    <PGS>17324</PGS>
                    <FRDOCBP>2026-06583</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Motor Carrier Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Maritime Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Comptroller of the Currency</P>
            </SEE>
            <SEE>
                <PRTPAGE P="vi"/>
                <HD SOURCE="HED">See</HD>
                <P>Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Interest Rate Paid on Cash Deposited To Secure U.S. Immigration and Customs Enforcement Immigration Bonds, </DOC>
                    <PGS>17333-17334</PGS>
                    <FRDOCBP>2026-06629</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>List of Countries Requiring Cooperation With an International Boycott, </DOC>
                    <PGS>17333</PGS>
                    <FRDOCBP>2026-06596</FRDOCBP>
                </DOCENT>
                <SJ>Request for Membership Application:</SJ>
                <SJDENT>
                    <SJDOC>Treasury Tribal Advisory Committee, </SJDOC>
                    <PGS>17334</PGS>
                    <FRDOCBP>2026-06652</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>DFC</EAR>
            <HD>U.S. International Development Finance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals; Correction, </DOC>
                    <PGS>17260</PGS>
                    <FRDOCBP>2026-06626</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Edith Nourse Rogers STEM Scholarship Application, </SJDOC>
                    <PGS>17334-17335</PGS>
                    <FRDOCBP>2026-06589</FRDOCBP>
                </SJDENT>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Veterans Rural Health Advisory Committee, </SJDOC>
                    <PGS>17335-17336</PGS>
                    <FRDOCBP>2026-06610</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>17338-17382</PGS>
                <FRDOCBP>2026-06604</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>17384-17602</PGS>
                <FRDOCBP>2026-06600</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents electronic mailing list, go to https://public.govdelivery.com/accounts/USGPOOFR/subscriber/new, enter your e-mail address, then follow the instructions to join, leave, or manage your subscription.</P>
        </AIDS>
    </CNTNTS>
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="17129"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2025-2547; Project Identifier MCAI-2025-00242-T; Amendment 39-23299; AD 2026-07-04]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for certain Airbus Canada Limited Partnership Model BD-500-1A10 and BD-500-1A11 airplanes. This AD was prompted by a report that, during a quality check in production, it was found that some of the tie rods supporting the overhead stowage compartments in the passenger cabin did not have enough thread engagement of the turnbuckle into the tie rod. This AD requires an inspection for proper thread engagement of the tie rods and, if necessary, adjustment of the tie rod engagement. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective May 11, 2026.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 11, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2547; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For Transport Canada material identified in this AD, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca</E>
                        . You may find this material on the Transport Canada website at 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2547.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Camille Seay, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 817-222-5149; email: 
                        <E T="03">camille.l.seay@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to certain Airbus Canada Limited Partnership Model BD-500-1A10 and BD-500-1A11 airplanes. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on September 16, 2025 (90 FR 44587). The NPRM was prompted by AD CF-2025-11, dated March 3, 2025 (Transport Canada AD CF-2025-11) (also referred to as the MCAI), issued by Transport Canada, which is the aviation authority for Canada. The MCAI states that during a quality check in production, it was found that some of the tie rods supporting the overhead stowage compartments in the passenger cabin did not have enough thread engagement of the turnbuckle into the tie rod. Further investigation of this deficiency determined that all overhead stowage compartments in the passenger cabin have the potential to be affected by this deficiency. The affected tie rods support the overhead stowage compartments during an emergency landing and if the tie rods become disengaged, the overhead stowage compartments have the potential of impacting occupants of the passenger cabin, resulting in serious injuries and possibly impeding passenger and crew egress during emergency evacuation.
                </P>
                <P>In the NPRM, the FAA proposed to require an inspection for proper thread engagement of the tie rods and, if necessary, adjustment of the tie rod engagement, as specified in Transport Canada AD CF-2025-11. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2025-2547.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received comments from three individuals who supported the NPRM without change.</P>
                <P>The FAA received additional comments from the Citizens Rulemaking Alliance and Delta Air Lines (Delta). The following presents the comments received on the NPRM and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Request To Clarify the Requirements for Tie Rod Engagement Adjustments</HD>
                <P>Delta requested that the FAA revise paragraph (h)(2) of the proposed AD to clarify that tie rod engagement adjustments must be done before further flight after the inspection, if the inspection reveals improper tie rod engagement. Delta stated the exception in the proposed AD can be misinterpreted to mean all tie rod engagement adjustments must be done on every airplane, regardless of whether the tie rods are found to be properly engaged during the inspection. Delta noted Transport Canada AD CF-2025-11 specifies to adjust the tie rod engagement if the tie rod is found to have inadequate thread engagement. Delta presumed that if the tie rods pass the inspection, no further action is required.</P>
                <P>
                    The FAA agrees that tie rod engagement adjustments must be done before further flight after the inspection, only if thread engagement is found to be inadequate during the inspection. The FAA has revised paragraph (h)(2) of this AD accordingly.
                    <PRTPAGE P="17130"/>
                </P>
                <HD SOURCE="HD1">Request To Justify Forgoing Notice and Comment or Issue an NPRM</HD>
                <P>The commenter requested that the FAA either provide its justification for finding good cause to bypass notice and comment procedures, convert this action to an NPRM, or extend the comment period and defer the compliance dates and enforcement until after comments are analyzed. The commenter asserted the FAA has not adequately justified use of the good cause exemption.</P>
                <P>
                    The FAA notes the comment was submitted in response to an NPRM for which the FAA provided a 45-day comment period. This final rule is effective 35 days after its publication in the 
                    <E T="04">Federal Register</E>
                    . Therefore, no change to this AD is necessary.
                </P>
                <HD SOURCE="HD1">Request To Comply With the Paperwork Reduction Act (PRA)</HD>
                <P>The commenter requested that the FAA revise the AD to comply with the PRA if reporting is required or remove any reporting provisions until PRA requirements are satisfied. If reporting is not required, the commenter requested the FAA clarify that in the AD.</P>
                <P>The FAA notes this AD does not require reporting. If an AD were to require reporting, the preamble of the AD would include a paragraph titled “Paperwork Reduction Act” that would provide the applicable OMB control number, required PRA statements, and the estimated time to collect the required information (burden). Any costs associated with the reporting requirement would be included in the Costs of Compliance section in the preamble of the AD. Therefore, the FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Consider Impact on Small Entities</HD>
                <P>The commenter requested that the FAA add to the AD docket the number of small entities operating affected airplanes and the factual basis for the FAA's Regulatory Flexibility Act (RFA) certification that the AD will not impact a substantial number of small entities.</P>
                <P>The FAA provides the following clarification. The RFA of 1980 (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121) and the Small Business Jobs Act of 2010 (Pub. L. 111-240), requires Federal agencies to consider the effects of the regulatory action on small business and other small entities and to minimize any significant economic impact. The term “small entities” comprises small businesses and not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The FAA identified two air carriers and two corporate trustees that will be affected by this AD. Based on the Small Business Administration size standard for air carriers and corporate trustees, all four entities are large businesses:</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="xs72,r100,xs72">
                    <TTITLE>Small Business Size Standards</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            NAICS 
                            <SU>2</SU>
                             code
                        </CHED>
                        <CHED H="1">Description</CHED>
                        <CHED H="1">Size standard</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">481111</ENT>
                        <ENT>Scheduled Passenger Air Transportation</ENT>
                        <ENT>1,500 employees.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">523991</ENT>
                        <ENT>Trust, Fiduciary, and Custody Activities</ENT>
                        <ENT>$47.0 million.</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Source: U.S. Small Business Administration, Table of Small Business Size Standards, 
                        <E T="03">https://www.sba.gov/sites/default/files/2023-06/Table%20of%20Size%20Standards_Effective%20March%2017%2C%202023%20%282%29.pdf</E>
                        .
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         North American Industrial Classification System.
                    </TNOTE>
                </GPOTABLE>
                <P>If an agency determines that a rulemaking will not result in a significant economic impact on a substantial number of small entities, the head of the agency may so certify under section 605(b) of the RFA. Therefore, as provided in section 605(b) and based on the foregoing, the head of FAA certifies that this AD will not result in a significant economic impact on a substantial number of small entities. The FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Provide Additional Cost Information</HD>
                <P>The commenter requested that the FAA add to the AD docket the cost methodology that supports its conclusion that the AD is not significant under Executive Order 12866 and the Unfunded Mandates Reform Act (UMRA). The commenter stated that the FAA should also provide the fleet size, per airplane labor and parts cost, and any assumed downtime or out-of-service impacts.</P>
                <P>The FAA recognizes that, in doing the actions required by an AD, operators might incur indirect costs in addition to the direct costs. The cost analysis in an AD typically describes only the direct costs of the specific actions required by an AD, which does not include indirect costs since the FAA lacks data on those costs and they vary significantly among operators. The number of work hours necessary to do the required actions of an AD is provided by the manufacturer. This number represents the time necessary to perform only the actions actually required by an AD. The cost of parts or special tools, if necessary, to complete the actions required by an AD is also provided by the manufacturer. Further, when the FAA is informed that the manufacturer may cover some or all of the estimated costs of an AD under warranty, the FAA indicates that in the AD.</P>
                <P>In the Cost of Compliance section of the proposed AD, the FAA disclosed the number of affected airplanes on the U.S. registry and number of estimated work hours. The FAA did not disclose an estimated parts cost since this AD does not require any parts. Additionally, the FAA considered the impact that this AD will have on affected operators and determined this AD will not trigger any downtime costs because the requirements of this AD can be performed during regularly scheduled maintenance. Since the FAA has assessed and disclosed the total known costs of the AD requirements in the Costs of Compliance section of the proposed AD, and the commenter did not provide additional cost data for the FAA to consider in its cost analysis, it is not necessary to provide additional information in the AD docket. The FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>
                    These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, and any other 
                    <PRTPAGE P="17131"/>
                    changes described previously, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.
                </P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed Transport Canada AD CF-2025-11, which specifies procedures for inspecting for proper thread engagement of the affected tie rods, and if the thread engagement is inadequate, adjustment of the tie rod engagement.</P>
                <P>
                    This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 80 airplanes of U.S. registry. The FAA estimates the following costs to comply with this AD:</P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s50,10C,15C,20C">
                    <TTITLE>Estimated Costs for Required Actions</TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">12 work-hours × $85 per hour = $1,020</ENT>
                        <ENT>None</ENT>
                        <ENT>$1,020</ENT>
                        <ENT>$81,600</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The FAA estimates the following costs to do any necessary on-condition action that would be required based on the results of any required actions. The FAA has no way of determining the number of aircraft that might need this on-condition action:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,10C,15C">
                    <TTITLE>Estimated Costs of On-Condition Actions</TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1 work-hour × $85 per hour = $85</ENT>
                        <ENT>None</ENT>
                        <ENT>$85</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-07-04 Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.):</E>
                             Amendment 39-23299; Docket No. FAA-2025-2547; Project Identifier MCAI-2025-00242-T.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective May 11, 2026.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to Airbus Canada Limited Partnership (Type Certificate previously held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Model BD-500-1A10 and BD-500-1A11 airplanes, certificated in any category, as identified in Transport Canada AD CF-2025-11, dated March 3, 2025 (Transport Canada AD CF-2025-11).</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 25, Equipment/Furnishings.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by a report that, during a quality check in production, it was found that some of the tie rods supporting the overhead stowage compartments in the passenger cabin did not have enough thread engagement of the turnbuckle into the tie rod. The FAA is issuing this AD to address affected tie rods that could disengage during an emergency landing. The unsafe condition, if not addressed, could result in the overhead stowage compartments impacting occupants of the passenger cabin, resulting in serious injuries and possibly impeding passenger and crew egress during emergency evacuation.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Requirements</HD>
                        <P>
                            Except as specified in paragraph (h) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, Transport Canada AD CF-2025-11.
                            <PRTPAGE P="17132"/>
                        </P>
                        <HD SOURCE="HD1">(h) Exceptions to Transport Canada AD CF-2025-11</HD>
                        <P>(1) Where Transport Canada AD CF-2025-11 refers to its effective date, this AD requires using the effective date of this AD.</P>
                        <P>(2) Where Transport Canada AD CF-2025-11 specifies “if the tie rod is found to have inadequate thread engagement, adjust the tie rod engagement”, this AD requires replacing that text with “if the tie rod is found to have inadequate thread engagement, adjust the tie rod engagement before further flight after the inspection”.</P>
                        <HD SOURCE="HD1">(i) Additional AD Provisions</HD>
                        <P>The following provisions also apply to this AD:</P>
                        <P>
                            (1) 
                            <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                             The Manager, AIR-520, Continued Operational Safety Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or responsible Flight Standards Office, as appropriate. If sending information directly to the manager of the Operational Safety Branch, send it to the attention of the person identified in paragraph (j) of this AD and email to: 
                            <E T="03">AMOC@faa.gov</E>
                            . Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Contacting the Manufacturer:</E>
                             For any requirement in this AD to obtain instructions from a manufacturer, the instructions must be accomplished using a method approved by the Manager, AIR-520, Continued Operational Safety Branch, FAA; or Transport Canada; or Airbus Canada Limited Partnership's Transport Canada Design Approval Organization (DAO). If approved by the DAO, the approval must include the DAO-authorized signature.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Required for Compliance (RC):</E>
                             Except as required by paragraph (i)(2) of this AD, if any material contains procedures or tests that are identified as RC, those procedures and tests must be done to comply with this AD; any procedures or tests that are not identified as RC are recommended. Those procedures and tests that are not identified as RC may be deviated from using accepted methods in accordance with the operator's maintenance or inspection program without obtaining approval of an AMOC, provided the procedures and tests identified as RC can be done and the airplane can be put back in an airworthy condition. Any substitutions or changes to procedures or tests identified as RC require approval of an AMOC.
                        </P>
                        <HD SOURCE="HD1">(j) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Camille Seay, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 817-222-5149; email: 
                            <E T="03">camille.l.seay@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this material as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                        <P>(i) Transport Canada AD CF-2025-11, dated March 3, 2025.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For Transport Canada material identified in this AD, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                            <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca.</E>
                             You may find this material on the Transport Canada website at 
                            <E T="03">tc.canada.ca/en/aviation.</E>
                        </P>
                        <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on March 25, 2026.</DATED>
                    <NAME>Lona C. Saccomando,</NAME>
                    <TITLE>Acting Deputy Director, Integrated Certificate Management Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06628 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-0019; Project Identifier MCAI-2025-00293-A; Amendment 39-23294; AD 2026-06-05]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Baykar Piaggio Aerospace S.p.A. (Type Certificate Previously Held by Piaggio Aviation S.p.A.) Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for certain Baykar Piaggio Aerospace S.p.A. (type certificate previously held by Piaggio Aviation S.p.A.) (Piaggio) Model P-180 airplanes. This AD was prompted by reports of corrosion and cracks affecting the vertical stabilizer. This AD requires repetitive visual and non-destructive testing (NDT) inspections, a one-time NDT inspection of the vertical stabilizer assembly, and, depending on findings, accomplishment of corrective actions. In addition, this AD provides a terminating action for the repetitive inspections if certain actions of the service material are accomplished. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective May 11, 2026.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 11, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-0019; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For Piaggio Aerospace material identified in this AD, contact Piaggio, P180 Customer Support, via Pionieri e Aviatori d'Italia, snc—16154 Genoa, Italy; phone: +39 331 679 74 93; email: 
                        <E T="03">technicalsupport@piaggioaerospace.it.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-0019.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Doug Rudolph, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (816) 329-4059; email: 
                        <E T="03">doug.rudolph@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to certain Piaggio Model P-180 airplanes. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on January 21, 2026 (91 FR 2507). The NPRM was prompted by European Union Aviation Safety Agency (EASA) AD 2025-0054, dated March 6, 2025 (EASA AD 2025-0054) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI states that corrosion and cracks affecting the vertical stabilizer were reported on Model P-180 airplanes. This condition, if not addressed, could result in reduced structural integrity of the vertical 
                    <PRTPAGE P="17133"/>
                    stabilizer and the rudder with consequent reduced control of the airplane.
                </P>
                <P>In the NPRM, the FAA proposed to require repetitive visual and NDT inspections, a one-time NDT inspection of the vertical stabilizer assembly, and, depending on findings, accomplishment of corrective actions. The FAA also proposed to provide a terminating action for the repetitive inspections. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-0019.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received a comment from one commenter. The commenter was the Air Line Pilots Association, International, who supported the NPRM without change.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed Piaggio Aerospace Service Bulletin (SB) 80-0493, Revision 0, dated November 21, 2024 (Piaggio Aerospace SB 80-0493, Rev. 0). This material specifies procedures for repetitive visual and NDT (including high-frequency eddy current (HFEC) and film radiographic (FR/D2) testing) inspections, a one-time NDT inspection, and post-repair instructions for the parts and structural elements of the vertical stabilizer assembly for evidence of damage of the protective finish, corrosion, and cracking, and applicable corrective actions. Corrective actions include, depending on inspection findings, repairing or replacing affected parts or contacting Piaggio to obtain an approved Repair Design Approval Sheet (RDAS), which is terminating action for certain repetitive inspections.</P>
                <P>
                    This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Differences Between This AD and the Referenced Material</HD>
                <P>Step (49) of Piaggio Aerospace SB 80-0493, Rev. 0, provides instructions to contact Piaggio to obtain an approved RDAS and accomplish that repair accordingly, including post-repair follow-on action(s), as applicable. This AD instead requires contacting either the Manager, International Validation Branch, FAA; EASA; or Piaggio's EASA Design Organization Approval (DOA) for approved repair instructions and, within the compliance time specified therein, accomplish those instructions accordingly, including post-repair follow-on action(s), as applicable. If approved by the DOA, the approval must include the DOA-authorized signature.</P>
                <P>Although Piaggio Aerospace SB 80-0493, Rev. 0, states that certain subsequent inspections are in accordance with the aircraft maintenance manual inspection program chapter 05-20-00, this AD does not require those actions.</P>
                <P>Although steps (17), (20), (24), (28), (33), (38), (41), (44), (47), (48), and Note 21 of Piaggio Aerospace SB 80-0493, Rev. 0, require reporting inspection results to Piaggio, this AD does not require those actions.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 107 airplanes of U.S. registry.</P>
                <P>The FAA estimates the following costs to comply with this AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,p7,7/8,i1" CDEF="s60,r50,r25,r25,r25">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">
                            Cost on U.S.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">One-time NDT inspection of the vertical stabilizer assembly</ENT>
                        <ENT>Up to 27 work-hours × $85 per hour = $2,295</ENT>
                        <ENT>$0</ENT>
                        <ENT>Up to $2,295</ENT>
                        <ENT>Up to $245,565.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Repetitive visual and NDT inspections of the vertical stabilizer assembly</ENT>
                        <ENT>Up to 40 work-hours × $85 per hour = $3,400 (per inspection)</ENT>
                        <ENT>$0 (per inspection)</ENT>
                        <ENT>Up to $3,400 (per inspection)</ENT>
                        <ENT>Up to $363,800 (per inspection).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The FAA estimates the following costs to do any repairs that would be required based on the results of the inspections. The agency has no way of determining the number of airplanes that might need these repairs:</P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s75,r60,xs72,xs72">
                    <TTITLE>On-Condition Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Repair of parts and structural elements of the vertical stabilizer assembly</ENT>
                        <ENT>Up to 280 work-hours × $85 per hour = $23,800</ENT>
                        <ENT>Up to $1,000</ENT>
                        <ENT>Up to $24,800.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Replace parts and structural elements of the vertical stabilizer assembly</ENT>
                        <ENT>Up to 160 work-hours × $85 per hour = $13,600</ENT>
                        <ENT>Up to $10,000</ENT>
                        <ENT>Up to $23,600.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>
                    The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and 
                    <PRTPAGE P="17134"/>
                    procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
                </P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-06-05 Baykar Piaggio Aerospace S.p.A. (type certificate previously held by Piaggio Aviation S.p.A.):</E>
                             Amendment 39-23294; Docket No. FAA-2026-0019; Project Identifier MCAI-2025-00293-A.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective May 11, 2026.</P>
                        <HD SOURCE="HD1"> (b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1"> (c) Applicability</HD>
                        <P>This AD applies to Baykar Piaggio Aerospace S.p.A. (type certificate previously held by Piaggio Aviation S.p.A.) Model P-180 airplanes, manufacturer serial numbers 1002, 1004 through 3016, and 3018, certificated in any category.</P>
                        <HD SOURCE="HD1"> (d) Subject</HD>
                        <P>Joint Aircraft System Component (JASC) Code 5530, Vertical Stabilizer Structure.</P>
                        <HD SOURCE="HD1"> (e) Unsafe Condition</HD>
                        <P>This AD was prompted by reports of corrosion and cracks affecting the vertical stabilizer. The FAA is issuing this AD to address this unsafe condition. The unsafe condition, if not addressed, could result in reduced structural integrity of the vertical stabilizer and the rudder with consequent reduced control of the airplane.</P>
                        <HD SOURCE="HD1"> (f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1"> (g) Required Actions</HD>
                        <P>(1) Within the applicable compliance time specified in table 1 to paragraph (g)(1) of this AD and thereafter at intervals not to exceed 660 hours time-in-service (TIS) or 26 months, whichever occurs first, do the applicable repetitive visual and non-destructive testing (NDT) inspections of the parts of the vertical stabilizer assembly for evidence of damage to the protective finish, corrosion, and cracking, in accordance with section 2.B, PART A, items (i) through (vii) as applicable, of Piaggio Aerospace Service Bulletin (SB) 80-0493, Revision 0, dated November 21, 2024 (Piaggio Aerospace SB 80-0493, Rev. 0). Where Piaggio Aerospace SB 80-0493, Rev. 0, states that subsequent inspections shall be performed in accordance with the aircraft maintenance manual inspection program chapter 05-20-00, this AD does not require those actions.</P>
                        <GPOTABLE COLS="02" OPTS="L2,nj,i1" CDEF="s50,r125">
                            <TTITLE>
                                Table 1 to Paragraph (
                                <E T="01">g</E>
                                )(1)—Compliance Times
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">P-180 Serial No.</CHED>
                                <CHED H="1">
                                    Compliance time 
                                    <LI>(hours TIS or calendar time, whichever occurs first after the effective date of this AD)</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">1002, 1004 through 3016 </ENT>
                                <ENT>Within 220 hours TIS or 13 months.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">3018 </ENT>
                                <ENT>Within 660 hours TIS or 26 months.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>(2) Within the applicable compliance time specified in table 1 to paragraph (g)(1) of this AD, do the applicable one-time NDT inspections of the parts of the vertical stabilizer assembly for evidence of damage to the protective finish, corrosion and cracking, in accordance with section 2.B, PART A, items (viii) and (ix), as applicable, of Piaggio Aerospace SB 80-0493, Rev. 0.</P>
                        <P>(3) If, during any inspection required by paragraph (g)(1) or (2) of this AD any corrosion or cracking is found, before further flight, accomplish the applicable corrective action(s), including post-repair inspections, in accordance with the instructions of section 2.B, PART B, of Piaggio Aerospace SB 80-0493, Rev. 0.</P>
                        <P>(4) Where the Accomplishment Instructions, section 2.B, PART B, step (49) of Piaggio SB 80-0493, Rev. 0, state to contact Piaggio to obtain an approved repair design approval sheet (RDAS) and accomplish that repair accordingly including post-repair follow-on actions(s), as applicable, before further flight, contact either the Manager, International Validation Branch, FAA; European Union Aviation Safety Agency (EASA); or Piaggio's EASA Design Organization Approval (DOA) for approved repair instructions and, within the compliance time specified therein, accomplish those instructions accordingly, including post-repair follow-on action(s), as applicable. If approved by the DOA, the approval must include the DOA-authorized signature.</P>
                        <HD SOURCE="HD1"> (h) Terminating Action</HD>
                        <P>Accomplishment of any action identified as “terminating action” for a given inspection in section 2.B, PART B, of Piaggio Aerospace SB 80-0493, Rev. 0, constitutes terminating action for the repetitive inspections, as applicable, required by paragraph (g)(1) of this AD for that airplane.</P>
                        <HD SOURCE="HD1"> (i) No Reporting Requirement</HD>
                        <P>Although certain steps of Piaggio Aerospace SB 80-0493, Rev. 0, specify to submit inspection findings to the manufacturer, this AD does not include that requirement.</P>
                        <HD SOURCE="HD1"> (j) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (k) of this AD and email to: 
                            <E T="03">AMOC@faa.gov.</E>
                             Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local Flight Standards District Office/certificate holding district office.
                        </P>
                        <HD SOURCE="HD1"> (k) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Doug Rudolph, Aviation Safety 
                            <PRTPAGE P="17135"/>
                            Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (816) 329-4059; email: 
                            <E T="03">doug.rudolph@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1"> (l) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this material as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(i) Piaggio Aerospace Service Bulletin 80-0493, Revision 0, dated November 21, 2024.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For Piaggio Aerospace material identified in this AD, contact Baykar Piaggio Aerospace S.p.A., P180 Customer Support, via Pionieri e Aviatori d'Italia, snc—16154 Genoa, Italy; phone: +39 331 679 74 93; email: 
                            <E T="03">technicalsupport@piaggioaerospace.it</E>
                            .
                        </P>
                        <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email 
                            <E T="03">fr.inspection@nara.gov</E>
                            .
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on March 19, 2026.</DATED>
                    <NAME>Steven W. Thompson,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06599 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2025-5039; Project Identifier MCAI-2024-00426-R; Amendment 39-23303; AD 2026-07-08]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for all Airbus Helicopters Model AS355E, AS355F, AS355F1, AS355F2, AS355N, and AS355NP helicopters. This AD was prompted by a report of a structural crack in the vertical attachment spar of the tail fin. This AD requires repetitive inspections of certain vertical upper fin spars and, depending on the results, corrective action. This AD also prohibits installing certain upper fin assemblies. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective May 11, 2026.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 11, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-5039; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find the EASA material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Office of the Regional Counsel, Southwest Region, 10101 Hillwood Parkway, Room 6N-321, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-5039.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Yves Petiote, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (202) 975-4867; email: 
                        <E T="03">yves.petiote@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to all Airbus Helicopters Model AS355E, AS355F, AS355F1, AS355F2, AS355N, and AS355NP helicopters. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on December 17, 2025 (90 FR 58519). The NPRM was prompted by EASA AD 2023-0154R1, dated July 19, 2024 (EASA AD 2023-0154R1) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI advises of a report of a structural crack (not a complete failure) in the vertical attachment spar of the tail fin. The MCAI states that the unsafe condition, if not addressed, may lead to in-flight separation of the upper part of the vertical fin, which could result in loss of control of the helicopter.
                </P>
                <P>EASA has issued related EASA AD 2024-0139, dated July 12, 2024 (EASA AD 2024-0139), for these same model helicopters as well as certain Model AS350B3 helicopters, to address cracking in a different area of the upper fin spar as well as the fin's front attachment screws. The FAA issued AD 2025-24-04, Amendment 39-23199 (90 FR 56679, December 8, 2025) (AD 2025-24-04), to address EASA AD 2024-0139. This AD includes actions that would be contingent on some of the required actions in AD 2025-24-04.</P>
                <P>In the NPRM, the FAA proposed to require repetitive inspections of certain vertical upper fin spars and, depending on the results, corrective action. The FAA also proposed to prohibit installing certain upper fin assemblies. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2025-5039.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received comments from four commenters. The commenters were two anonymous commenters and two individual commenters. The commenters supported the NPRM without change.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed EASA AD 2023-0154R1, which specifies procedures for removing the tail gear box (TGB) fairing and the rear fairing from the tail boom, cleaning, and inspecting the right-hand external side around the two top screws 
                    <PRTPAGE P="17136"/>
                    of certain upper fin spars for a crack. EASA AD 2023-0154R1 also specifies procedures for conducting repetitive borescope inspections of that upper fin spar area for a crack or repeating the initial inspection as an alternative. Additionally, EASA AD 2023-0154R1 specifies accomplishing the inspections before and after maintenance flights that exceed the reduced Velocity Never Exceed (V
                    <E T="52">NE</E>
                    ) required by EASA AD 2024-0139 and before the next flight following any other exceedance of the reduced V
                    <E T="52">NE</E>
                     required by EASA AD 2024-0139. Depending on the results of an inspection, EASA AD 2023-0154R1 specifies procedures for marking the two top right-hand screw ends or replacing the upper fin. EASA AD 2023-0154R1 further specifies that installing an upper fin assembly part number (P/N) 355A14-0522-1751 constitutes terminating action for its repetitive inspection requirements and prohibits installing certain upper fin assemblies on any helicopter. This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI</HD>
                <P>Where the MCAI defines an affected part as those listed in any revision of the manufacturer's service information, this AD defines an affected part as those listed in specific versions of the manufacturer's service information and would include upper fin assemblies for which the P/N cannot be determined.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects 177 helicopters of U.S. registry. Labor rates are estimated at $85 per hour. Based on these numbers, the FAA estimates the following costs to comply with this AD.</P>
                <P>Initial cleaning and inspection of the vertical fin spar and, if necessary, application of a paint mark on the top two right-hand screw ends takes 2.5 work-hours for an estimated cost of $213 per helicopter and $37,701 for the U.S. fleet.</P>
                <P>Repetitive borescope inspection of the upper fin spar takes 0.5 work-hour for an estimated cost of $43 per helicopter and up to $7,611 for the U.S. fleet, per inspection cycle. Alternatively, repeating the initial inspection takes 2.5 work-hours for an estimated cost of $213 per helicopter and up to $37,701 for the U.S. fleet, per inspection cycle.</P>
                <P>If required, removing the upper fin from service and installing upper fin assembly P/N 355A14-0522-1751 to modify the upper fin takes 40 work-hours and parts cost $25,360 for an estimated cost of $28,760 per helicopter.</P>
                <P>The FAA has included all known costs in its cost estimate. According to the manufacturer, however, some of the costs of this AD may be covered under warranty, thereby reducing the cost impact on affected operators.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-07-08 Airbus Helicopters:</E>
                             Amendment 39-23303; Docket No. FAA-2025-5039; Project Identifier MCAI-2024-00426-R.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective May 11, 2026.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>This AD affects AD 2025-24-04, Amendment 39-23199 (90 FR 56679, December 8, 2025) (AD 2025-24-04).</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to Airbus Helicopters Model AS355E, AS355F, AS355F1, AS355F2, AS355N, and AS355NP helicopters, certificated in any category.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Joint Aircraft System Component (JASC) Code 5531, Vertical Stabilizer, Spar/Rib Structure.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by a report of a structural crack in the vertical attachment spar of the tail fin. The FAA is issuing this AD to address cracking in the upper fin spar. This condition, if not addressed, could lead to in-flight separation of the upper part of the vertical fin, which could result in loss of control of the helicopter.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Requirements</HD>
                        <P>Except as specified in paragraphs (h) and (i) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, European Union Aviation Safety Agency (EASA) AD 2023-0154R1, dated July 19, 2024 (EASA AD 2023-0154R1).</P>
                        <HD SOURCE="HD1">(h) Exceptions to EASA AD 2023-0154R1</HD>
                        <P>(1) Where EASA AD 2023-0154R1 defines an “affected part,” this AD requires replacing that text with “an upper fin assembly having a part number (P/N) identified in the Applicability, Accomplishment Procedure, of Airbus Helicopters Emergency Alert Service Bulletin EASB AS355-05-00-0001, Issue 001, dated July 25, 2023, or Issue 002, dated July 9, 2024, or an upper fin assembly having a P/N that cannot be determined”.</P>
                        <P>
                            <E T="04">Note 1 to paragraph (h)(1):</E>
                             MOD 0720098 involves installing a new upper fin that has a reinforced fin spar (P/N 355A14-0522-1751) that is not affected by this AD. Airbus 
                            <PRTPAGE P="17137"/>
                            Helicopters Alert Service Bulletin No. AS355-55.00.18, Revision 1, dated June 6, 2024, contains information regarding MOD 0720098.
                        </P>
                        <P>(2) Where EASA AD 2023-0154R1 refers to August 3, 2023 (the effective date of EASA AD 2023-0154, dated July 27, 2023), this AD requires using the effective date of this AD.</P>
                        <P>(3) Where EASA AD 2023-0154R1 requires compliance in terms of flight hours, this AD requires using hours time-in-service.</P>
                        <P>
                            (4) Where paragraph (3) of EASA AD 2023-0154R1 specifies “following the Rotorcraft Flight Manual (RFM) amendment as required by paragraph (1) or (2) of EASA AD 2024-0139, as applicable, it is allowed to exceed the temporary reduced Vne during a maintenance flight”, this AD requires replacing that text with “following the Rotorcraft Flight Manual (RFM) amendment required by AD 2025-24-04, it is allowed to exceed the temporary reduced Velocity Never Exceed (V
                            <E T="52">NE</E>
                            ) during a flight to perform an operational check as specified in 14 CFR 91.407”.
                        </P>
                        <P>(5) Where paragraphs (3.1), (3.2), and (3.3) of EASA AD 2023-0154R1 specify “maintenance flight”, this AD requires replacing that text with “flight to perform an operational check as specified in 14 CFR 91.407”.</P>
                        <P>
                            (6) Where paragraph (4) of EASA AD 2023-0154R1 specifies “if, following the RFM amendment as required by paragraph (1) or (2) of EASA AD 2024-0139, as applicable, the temporary reduced Vne is exceeded on a helicopter”, this AD requires replacing that text with “if, following the RFM amendment required by AD 2025-24-04, the temporary reduced V
                            <E T="52">NE</E>
                             is exceeded on a helicopter”.
                        </P>
                        <P>
                            (7) Where Note 1 of EASA AD 2023-0154R1 specifies “It is allowed to temporarily remove the RFM amendment and the placard, as required by paragraph (1) or (2) of EASA AD 2024-0139, as applicable, to allow maintenance flight(s) during which the temporarily reduced Vne may be exceeded”, this AD requires replacing that text with “It is allowed to temporarily remove the RFM amendment and the placard required by AD 2025-24-04 to allow flight(s) to perform an operational check as specified in 14 CFR 91.407, during which the temporarily reduced V
                            <E T="52">NE</E>
                             may be exceeded”.
                        </P>
                        <P>
                            <E T="04">Note 2 to paragraph (h)(7):</E>
                             Refer to AD 2025-24-04 for requirements pertaining to exceeding V
                            <E T="52">NE</E>
                             110 kts. Airbus Helicopters Emergency Alert Service Bulletin EASB AS355-05-00-0001, Issue 002, dated July 9, 2024, also contains information regarding exceeding V
                            <E T="52">NE</E>
                             110 kts.
                        </P>
                        <P>(8) Instead of complying with paragraph (6) of EASA AD 2023-0154R1, if there is a crack as a result of the inspections required by paragraphs (1) through (4) of EASA AD 2023-0154R1, this AD requires, before further flight, removing the upper fin from service and installing upper fin assembly P/N 355A14-0522-1751 in accordance with paragraph (7) and Note 2 of EASA AD 2023-0154R1.</P>
                        <P>(9) Where Note 2 of EASA AD 2023-0154R1 specifies “paragraph (12) of EASA AD 2024-0139”, this AD requires replacing that text with “AD 2025-24-04”.</P>
                        <P>(10) This AD does not adopt the “Remarks” section of EASA AD 2023-0154R1.</P>
                        <HD SOURCE="HD1">(i) No Reporting Requirement</HD>
                        <P>Although the material referenced in EASA AD 2023-0154R1 specifies to submit certain information to the manufacturer, this AD does not include that requirement.</P>
                        <HD SOURCE="HD1">(j) Special Flight Permits</HD>
                        <P>Special flight permits are prohibited.</P>
                        <HD SOURCE="HD1">(k) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (l)(1) of this AD and email to: 
                            <E T="03">AMOC@faa.gov.</E>
                        </P>
                        <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                        <HD SOURCE="HD1">(l) Related Information</HD>
                        <P>
                            (1) For more information about this AD, contact Yves Petiote, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (202) 975-4867; email: 
                            <E T="03">yves.petiote@faa.gov.</E>
                        </P>
                        <P>
                            (2) Airbus Helicopters material identified in this AD that is not incorporated by reference is available at Airbus Helicopters, 2701 North Forum Drive, Grand Prairie, TX 75052; phone: (972) 641-0000 or (800) 232-0323; fax: (972) 641-3775; website 
                            <E T="03">airbus.com/en/products-services/helicopters/hcare-services/airbusworld.</E>
                        </P>
                        <HD SOURCE="HD1">(m) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this material as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                        <P>(i) European Union Aviation Safety Agency (EASA) AD 2023-0154R1, dated July 19, 2024.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                            <E T="03">ADs@easa.europa.eu;</E>
                             website: 
                            <E T="03">easa.europa.eu.</E>
                             You may find the EASA material on the EASA website at 
                            <E T="03">ad.easa.europa.eu.</E>
                        </P>
                        <P>(4) You may view this material at the FAA, Office of the Regional Counsel, Southwest Region, 10101 Hillwood Parkway, Room 6N-321, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on March 31, 2026.</DATED>
                    <NAME>Christopher R. Parker,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06621 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2025-2553; Project Identifier MCAI-2025-00186-T; Amendment 39-23297; AD 2026-07-02]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Dassault Aviation Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for certain Dassault Aviation Model FALCON 2000EX airplanes. This AD was prompted by a report of simultaneous failures of the main DC buses powered by Generator 1 (GEN1), and Generator 2 (GEN2) after flap extension during approach. This AD requires revising the existing airplane flight manual (AFM). The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective May 11, 2026.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 11, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2553; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; telephone +49 221 8999 000; email 
                        <E T="03">ADs@easa.europa.eu.</E>
                         You may find this material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                        <PRTPAGE P="17138"/>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2025-2553.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Steven Dzierzynski, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: 516-228-7367; email: 
                        <E T="03">9-AVS-AIR-BACO-COS@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to certain Dassault Aviation Model FALCON 2000EX airplanes. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on September 26, 2025 (90 FR 46365). The NPRM was prompted by AD 2025-0042, dated February 19, 2025 (EASA AD 2025-0042) (also referred to as the MCAI), issued by EASA, which is the Technical Agent for the Member States of the European Union. The MCAI states there was a report of simultaneous failures of the main DC buses powered by GEN1 and GEN2 after flap extension during approach. This event resulted in intermittent crew alerting system (CAS) messages, including the red CAS message “2 GEN'S FAIL,” data flickering on the display units, and flashing lights on the overhead panel, which led to the loss of the main DC buses after a short period.
                </P>
                <P>In the NPRM, the FAA proposed to require revising the existing AFM, as specified in EASA AD 2025-0042. The FAA is issuing this AD to address intermittent and flickering data, as well as CAS messages. The unsafe condition, if not addressed, could lead to increased pilot workload, possibly during a critical phase of flight.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2025-2553.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received comments from the Citizens Rulemaking Alliance. The following presents the comments received on the NPRM and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Request To Issue an NPRM or Delay Effective Date for Non-Immediate Tasks</HD>
                <P>The commenter requested that the FAA either convert this action to an NPRM or delay the effective date for non-immediate tasks by 60 to 120 days and request comments for those non-immediate tasks. The commenter asserted the FAA's use of the good cause exemption appears overbroad given the compliance is 1 month instead of before further flight.</P>
                <P>
                    The FAA notes the comment was submitted in response to an NPRM for which the FAA provided a 45-day comment period. This final rule is effective 35 days after its publication in the 
                    <E T="04">Federal Register</E>
                    . Therefore, no change to this AD is necessary.
                </P>
                <HD SOURCE="HD1">Request To Make Incorporation by Reference (IBR) Materials Reasonably Available</HD>
                <P>The commenter stated that the FAA's current practices for IBR frequently fail to meet the legal and regulatory standards for reasonable availability. The commenter called on the FAA to guarantee that all IBR materials are easily and freely accessible to the public and affected parties for both commenting and compliance purposes. They also requested that this access be documented in the rulemaking record.</P>
                <P>
                    The FAA's practices comply with 5 U.S.C. 552(a) of the Administrative Procedure Act and 1 CFR part 51. The FAA makes IBR materials available in the AD docket when the final rule is published in the 
                    <E T="04">Federal Register</E>
                    , following formal approval of the IBR by the Office of the Federal Register. Materials may only be posted before the final rule's publication if they are already publicly available or if there is written consent from the owner of the IBR material. All relevant materials incorporated by reference will be accessible in the AD docket on 
                    <E T="03">Regulations.gov,</E>
                     which the public can access without registration or fees.
                </P>
                <P>The FAA also provides summaries and access details in the preamble and regulatory text, makes materials available for inspection at FAA and National Archives and Records Administration (NARA) offices, offers publisher contact information, and obtains formal IBR approval from the Office of the Federal Register. These efforts are intended to ensure that all IBR materials meet the “reasonably available” standard required by 1 CFR part 51. The FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Comply With the Paperwork Reduction Act (PRA)</HD>
                <P>The commenter requested that the FAA revise the AD to comply with the PRA if reporting is required or remove any reporting provisions until PRA requirements are satisfied. If reporting is not required, the commenter requested the FAA clarify that in the AD.</P>
                <P>The FAA notes this AD does not require reporting. If an AD were to require reporting, the preamble of the AD would include a paragraph titled “Paperwork Reduction Act” that would provide the applicable OMB control number, required PRA statements, and the estimated time to collect the required information (burden). Any costs associated with the reporting requirement would be included in the Costs of Compliance section in the preamble of the AD. Therefore, the FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Consider Impact on Small Entities</HD>
                <P>The commenter requested that the FAA either provide the factual basis for its Regulatory Flexibility Act (RFA) certification that the AD will not have a significant economic impact on a substantial number of small entities, or prepare an initial regulatory flexibility analysis and consider less burdensome alternatives for small operators and small repair stations.</P>
                <P>The FAA provides the following clarification. The RFA of 1980 (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121) and the Small Business Jobs Act of 2010 (Pub. L. 111-240), requires Federal agencies to consider the effects of the regulatory action on small business and other small entities and to minimize any significant economic impact. The term “small entities” comprises small businesses and not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>
                    This AD will affect 230 small and non-small entities, 1 Tribal government, and 3 individuals. Of the affected entities, FAA identified 143 small entities in multiple industries as follows:
                    <PRTPAGE P="17139"/>
                </P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="xs60,r100,13,12">
                    <TTITLE>Number of Small Entities Affected per Industry and Cost Significance</TTITLE>
                    <BOXHD>
                        <CHED H="1">NAICS code</CHED>
                        <CHED H="1">Description</CHED>
                        <CHED H="1">
                            Number of
                            <LI>small entities</LI>
                            <LI>affected</LI>
                        </CHED>
                        <CHED H="1">
                            Cost per
                            <LI>AD/annual</LI>
                            <LI>revenue</LI>
                            <LI>(%)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">481211</ENT>
                        <ENT>Nonscheduled Chartered Passenger Air Transportation</ENT>
                        <ENT>89</ENT>
                        <ENT>0.00 to 0.02</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">481219</ENT>
                        <ENT>Other Nonscheduled Air Transportation</ENT>
                        <ENT>13</ENT>
                        <ENT>0.00 to 0.02</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">532411</ENT>
                        <ENT>Commercial Air, Rail, and Water Transportation Equipment Rental and Leasing</ENT>
                        <ENT>11</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">488190</ENT>
                        <ENT>Other Support Activities for Air Transportation</ENT>
                        <ENT>4</ENT>
                        <ENT>0.00 to 0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">551112</ENT>
                        <ENT>Offices of Other Holding Companies</ENT>
                        <ENT>4</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">211120</ENT>
                        <ENT>Crude Petroleum Extraction</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">326299</ENT>
                        <ENT>All Other Rubber Product Manufacturing</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">334511</ENT>
                        <ENT>Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing</ENT>
                        <ENT>1</ENT>
                        <ENT>n.a.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">336411</ENT>
                        <ENT>Aircraft Manufacturing</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">336414</ENT>
                        <ENT>Guided Missile and Space Vehicle Manufacturing</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">423820</ENT>
                        <ENT>Farm and Garden Machinery and Equipment Merchant Wholesalers</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">423860</ENT>
                        <ENT>Transportation Equipment and Supplies Merchant Wholesalers</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">425120</ENT>
                        <ENT>Wholesale Trade Agents and Brokers</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">484121</ENT>
                        <ENT>General Freight Trucking, Long-Distance, Truckload</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">523120</ENT>
                        <ENT>Securities Brokerage</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">525990</ENT>
                        <ENT>Other Investment Pools and Funds</ENT>
                        <ENT>1</ENT>
                        <ENT>n.a.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">531190</ENT>
                        <ENT>Lessors of Other Real Estate Property</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">531390</ENT>
                        <ENT>Other Activities Related to Real Estate</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">532310</ENT>
                        <ENT>General Rental Centers</ENT>
                        <ENT>1</ENT>
                        <ENT>n.a.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">532490</ENT>
                        <ENT>Other Commercial and Industrial Machinery and Equipment Rental and Leasing</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">541110</ENT>
                        <ENT>Offices of Lawyers</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">541511</ENT>
                        <ENT>Custom Computer Programming Services</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">541512</ENT>
                        <ENT>Computer Systems Design Services</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">541611</ENT>
                        <ENT>Administrative Management and General Management Consulting Services</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">551114</ENT>
                        <ENT>Corporate, Subsidiary, and Regional Managing Offices</ENT>
                        <ENT>1</ENT>
                        <ENT>0.01</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">611512</ENT>
                        <ENT>Flight Training</ENT>
                        <ENT>1</ENT>
                        <ENT>n.a.</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">811310</ENT>
                        <ENT>Commercial and Industrial Machinery and Equipment (except Automotive and Electronic) Repair and Maintenance</ENT>
                        <ENT>1</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>143</ENT>
                        <ENT/>
                    </ROW>
                </GPOTABLE>
                <P>While FAA has determined that this final AD affects a substantial number of small entities, the compliance cost of the AD per small entity to their annual revenue is de minimis. Therefore, as provided in section 605(b) and based on the foregoing, the head of FAA certifies that this AD will not result in a significant economic impact on a substantial number of small entities. The FAA did not change this AD as a result of this comment.</P>
                <HD SOURCE="HD1">Request To Revise the Cost Estimate</HD>
                <P>The commenter requested that the FAA update the labor rate and downtime assumptions in the cost estimate, consider alternatives that minimize downtime and scheduling disruptions, and revise the FAA's certification that the AD is not a significant regulatory action under Executive Order 12866 if the updated costs justify it.</P>
                <P>
                    The FAA has determined that the current labor rate of $85 per hour remains accurate for this AD. The FAA evaluates this rate periodically, based on U.S. Department of Labor Statistic (BLS) data found at 
                    <E T="03">https://data.bls.gov/oes,</E>
                     and will change the rate when appropriate. The FAA used a blended wage rate to estimate the labor rate for this AD, where the FAA assumes 60 percent weight for aircraft mechanics (at a fully burdened mean wage rate of $69.85 per hour) and 40 percent for general and operations managers (at a fully burdened mean wage rate of $108.15 per hour). To calculate the blended wage rate, the FAA multiplied each wage rate by its corresponding weight and added up the products to obtain a wage rate of $85.17, which the FAA rounded down to $85. Additionally, the FAA considered the impact that this AD will have on affected operators and determined that this AD will not trigger any downtime costs because AFM revisions are administrative actions that do not normally lead to burdensome scheduling disruptions. Therefore, the FAA did not change this AD as a result of this comment.
                </P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed EASA AD 2025-0042, which specifies procedures for revising the AFM to provide flightcrew with emergency procedures to address intermittent and flickering data and CAS messages.</P>
                <P>
                    This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>
                    The FAA estimates that this AD affects 304 airplanes of U.S. registry. The FAA estimates the following costs to comply with this AD:
                    <PRTPAGE P="17140"/>
                </P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s50,10C,15C,20C">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1 work-hour × $85 per hour = $85</ENT>
                        <ENT>$0</ENT>
                        <ENT>$85</ENT>
                        <ENT>$25,840</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-07-02 Dassault Aviation:</E>
                             Amendment 39-23297; Docket No. FAA-2025-2553; Project Identifier MCAI-2025-00186-T.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective May 11, 2026.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to Dassault Aviation Model FALCON 2000EX airplanes, certificated in any category, as identified in European Union Aviation Safety Agency (EASA) AD 2025-0042, dated February 19, 2025 (EASA AD 2025-0042).</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 24, Electrical power.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by a report of simultaneous failures of the main DC buses powered by Generator 1 (GEN1), and Generator 2 (GEN2) after flap extension during approach, which initially resulted in intermittent display of crew alerting system (CAS) messages, and led to the loss of the main DC buses. The FAA is issuing this AD to address intermittent and flickering data, as well as CAS messages. The unsafe condition, if not addressed, could lead to increased pilot workload, possibly during a critical phase of flight.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Requirements</HD>
                        <P>Except as specified in paragraph (h) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, EASA AD 2025-0042.</P>
                        <HD SOURCE="HD1">(h) Exceptions to EASA AD 2025-0042</HD>
                        <P>(1) Where paragraph (1) of EASA AD 2025-0042 specifies to “inform all flight crews and, thereafter, operate the airplane accordingly,” this AD does not require those actions as those actions are already required by existing FAA operating regulations (see 14 CFR 91.9 and 91.505 and 14 CFR 121.137).</P>
                        <P>(2) Where EASA AD 2025-0042 refers to its effective date, this AD requires using the effective date of this AD.</P>
                        <P>(3) This AD does not adopt the “Remarks” section of EASA AD 2025-0042.</P>
                        <HD SOURCE="HD1">(i) Additional AD Provisions</HD>
                        <P>The following provisions also apply to this AD:</P>
                        <P>
                            (1) 
                            <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                             The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or responsible Flight Standards Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (j) of this AD and email to: 
                            <E T="03">AMOC@faa.gov.</E>
                             Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Contacting the Manufacturer:</E>
                             For any requirement in this AD to obtain instructions from a manufacturer, the instructions must be accomplished using a method approved by the Manager, International Validation Branch, FAA; or EASA; or Dassault Aviation's EASA Design Organization Approval (DOA). If approved by the DOA, the approval must include the DOA-authorized signature.
                        </P>
                        <HD SOURCE="HD1">(j) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Steven Dzierzynski, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: 516-228-7367; email: 
                            <E T="03">9-AVS-AIR-BACO-COS@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this material as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                        <P>(i) European Union Aviation Safety Agency (EASA) AD 2025-0042, dated February 19, 2025.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; telephone +49 221 8999 000; email 
                            <E T="03">ADs@easa.europa.eu.</E>
                             You may find this material on the EASA website at 
                            <E T="03">ad.easa.europa.eu.</E>
                        </P>
                        <P>
                            (4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the 
                            <PRTPAGE P="17141"/>
                            availability of this material at the FAA, call 206-231-3195.
                        </P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on March 25, 2026.</DATED>
                    <NAME>Steven W. Thompson,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06627 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-0008; Project Identifier MCAI-2025-01103-R; Amendment 39-23304; AD 2026-07-09]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is adopting a new airworthiness directive (AD) for all Airbus Helicopters Model H160-B helicopters. This AD was prompted by a report of a leak on a gas cylinder within the emergency life raft system (ELRS) container assembly due to geometrical gaps between the burst disk and the valve body. This AD requires replacing the ELRS container assembly and prohibits installing an affected ELRS container assembly unless certain requirements are met. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective May 11, 2026.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 11, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-0008; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The address for Docket Operations is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Safety Agency (EASA) material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu;</E>
                         website: 
                        <E T="03">easa.europa.eu.</E>
                         You may find the EASA material on the EASA website at 
                        <E T="03">ad.easa.europa.eu.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Office of the Regional Counsel, Southwest Region, 10101 Hillwood Parkway, Room 6N-321, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-0008.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Matthew Williams, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (316) 946-4134; email: 
                        <E T="03">matthew.t.williams@faa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to all Airbus Helicopters Model H160-B helicopters. The NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on January 9, 2026 (91 FR 929). The NPRM was prompted by EASA AD 2025-0130R1, dated June 16, 2025 (EASA AD 2025-0130R1) (also referred to as the MCAI) issued by EASA, which is the Technical Agent for the Member States of the European Union. EASA AD 2025-0130R1 states that an occurrence was reported of a leak on a gas cylinder within the ELRS container assembly. Subsequent investigation revealed that this leakage was due to geometrical gaps between the burst disk and the valve body. EASA AD 2025-0130R1 specifies procedures for replacement of an affected ELRS container assembly and prohibits the installation of affected ELRS container assembly unless certain requirements are met.
                </P>
                <P>In the NPRM, the FAA proposed to require replacing the ELRS container assembly. The FAA also proposed to prohibit installing an affected ELRS container assembly unless certain requirements are met. The FAA is issuing this AD to address the unsafe condition on these products.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-0008.
                </P>
                <HD SOURCE="HD1">Discussion of Final Airworthiness Directive</HD>
                <HD SOURCE="HD1">Comments</HD>
                <P>The FAA received no comments on the NPRM or on the determination of the costs.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA reviewed the relevant data, considered any comments received, and determined that air safety requires adopting this AD as proposed. Accordingly, the FAA is issuing this AD to address the unsafe condition on these products. Except for minor editorial changes, this AD is adopted as proposed in the NPRM. None of the changes will increase the economic burden on any operator.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed EASA AD 2025-0130R1, which specifies procedures to replace the ELRS container assembly having Airbus left-hand part number (P/N) U256A80A1005 or right-hand P/N U256A80A1006 with a serviceable ELRS container assembly and sending an affected ELRS container assembly to a Safran Aerosystems repair facility for further corrective actions. EASA AD 2025-0130R1 also prohibits installing an affected ELRS container assembly on any helicopter unless certain requirements are met. This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI</HD>
                <P>The MCAI specifies sending the affected ELRS container assembly to a Safran Aerosystems repair facility, whereas this AD allows sending the affected ELRS container assembly to a Safran Aerosystems repair facility or an FAA-approved repair facility</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD affects nine helicopters of U.S. registry.</P>
                <P>
                    The FAA estimates the following costs to comply with this AD:
                    <PRTPAGE P="17142"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s40,r40,r50,10,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">
                            Cost per
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">
                            Cost on U.S.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Replace ELRS container assembly</ENT>
                        <ENT>2 work-hours × $85 per hour = $170</ENT>
                        <ENT>no definitive data on cost of affected part or shipment of part</ENT>
                        <ENT>$170</ENT>
                        <ENT>$1,530</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Will not affect intrastate aviation in Alaska, and</P>
                <P>(3) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2026-07-09 Airbus Helicopters:</E>
                             Amendment 39-23304; Docket No. FAA-2026-0008; Project Identifier MCAI-2025-01103-R.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This airworthiness directive (AD) is effective May 11, 2026.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to all Airbus Helicopters Model H160-B helicopters, certificated in any category.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Joint Aircraft System Component (JASC) Code 2564, Life Raft.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by a report of a leak on a gas cylinder within the emergency life raft system (ELRS) container assembly due to geometrical gaps between the burst disk and the valve body. The FAA is issuing this AD to address the leakage of the gas cylinder within the ELRS container assembly. The unsafe condition, if not addressed, could result in the failure of the release of the life rafts during an emergency landing on water and consequently prevent a timely egress from the helicopter, which could result in injury to helicopter occupants.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Requirements</HD>
                        <P>Except as specified in paragraphs (h) and (i) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, European Union Aviation Safety Agency (EASA) AD 2025-0130R1, dated June 16, 2025 (EASA AD 2025-0130R1).</P>
                        <HD SOURCE="HD1">(h) Exceptions to EASA AD 2025-0130R1</HD>
                        <P>(1) Where EASA AD 2025-0130R1 refers to its effective date, this AD requires using the effective date of this AD.</P>
                        <P>(2) Where EASA AD 2025-0130R1 refers to flight hours (FH), this AD requires using hours time-in-service.</P>
                        <P>(3) Where the material referenced in EASA AD 2025-0130R1 specifies to send the affected ELRS container assembly to a Safran Aerosystems repair facility, this AD allows operators to send the affected ELRS container assembly to Safran Aerosystems repair facility or an FAA-approved repair facility.</P>
                        <P>(4) This AD does not adopt the “Remarks” section of EASA AD 2025-0130R1.</P>
                        <HD SOURCE="HD1">(i) No Reporting Requirement</HD>
                        <P>Although the material referenced in EASA AD 2025-0130R1 specifies to submit certain information to the manufacturer, this AD does not require this action.</P>
                        <HD SOURCE="HD1">(j) Special Flight Permit</HD>
                        <P>Special flight permits may be issued in accordance with 14 CFR 21.197 and 21.199, provided there are no flights over water.</P>
                        <HD SOURCE="HD1">(k) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person identified in paragraph (l) of this AD and email to: 
                            <E T="03">AMOC@faa.gov.</E>
                        </P>
                        <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                        <HD SOURCE="HD1">(l) Additional Information</HD>
                        <P>
                            For more information about this AD, contact Matthew Williams, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (316) 946-4134; email: 
                            <E T="03">matthew.t.williams@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(m) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this material as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(i) European Union Aviation Safety Agency (EASA) AD 2025-0130R1, dated June 16, 2025.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                            <E T="03">ADs@easa.europa.eu;</E>
                              
                            <PRTPAGE P="17143"/>
                            website: 
                            <E T="03">easa.europa.eu.</E>
                             You may find the EASA material on the EASA website at 
                            <E T="03">ad.easa.europa.eu.</E>
                        </P>
                        <P>(4) You may view this material at the FAA, Office of the Regional Counsel, Southwest Region, 10101 Hillwood Parkway, Room 6N-321, Fort Worth, TX 76177. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                             or email 
                            <E T="03">fr.inspection@nara.gov.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued on March 30, 2026.</DATED>
                    <NAME>Christopher R. Parker,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06622 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2025-5140; Airspace Docket No. 25-AAL-171]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Establishment of Class E Airspace; Birch Creek Airport, Birch Creek, AK</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action corrects a final rule published by the FAA in the 
                        <E T="04">Federal Register</E>
                         on March 20, 2026, establishing Class E airspace extending upward from 700 feet above the surface at Birch Creek Airport, Birch Creek, Alaska (AK). Specifically, this action corrects the region code associated with the affected airspace.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The effective date of the final rule published in the 
                        <E T="04">Federal Register</E>
                         on March 20, 2026, remains 0901 UTC, May 14, 2026. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order JO 7400.11 and publication of conforming amendments.
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order JO 7400.11K, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Policy Directorate, Federal Aviation Administration, 600 Independence Avenue SW, Washington, DC 20597; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Bryantjay T. Toves, Federal Aviation Administration, Western Service Center, Operations Support Group, 2200 S 216th Street, Des Moines, WA 98198; telephone (206) 231-3465.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a final rule in the 
                    <E T="04">Federal Register</E>
                     (91 FR 13495; March 20, 2026) for Docket FAA-2025-5140, which established Class E airspace extending upward from 700 feet above the surface at Birch Creek Airport, Birch Creek, AK. Subsequent to publication, the FAA identified an administrative error in the FAA regional routing symbol used in the final rule. This action corrects the error by replacing the incorrect regional routing symbol, “ANM,” with the intended regional routing symbol, “AAL.”
                </P>
                <HD SOURCE="HD1">Correction to Final Rule</HD>
                <P>
                    Accordingly, pursuant to the authority delegated to me, the final rule for Docket No. FAA-2025-5140, as published in the 
                    <E T="04">Federal Register</E>
                     on March 20, 2026 (91 FR 13495), FR Doc. 2026-05500, is corrected as follows:
                </P>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>
                        On page 13496, in the first column, revise the header of the airspace legal description for “
                        <E T="04">ANM AK E5 Birch Creek, AK [NEW]</E>
                        ” to read “
                        <E T="04">AAL AK E5 Birch Creek, AK [NEW]</E>
                        ”.
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Des Moines, Washington, on April 2, 2026.</DATED>
                    <NAME>B.G. Chew,</NAME>
                    <TITLE>Group Manager, Operations Support Group, Western Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06625 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Mine Safety and Health Administration</SUBAGY>
                <CFR>30 CFR Parts 56 and 57</CFR>
                <DEPDOC>[Docket No. MSHA-2023-0001]</DEPDOC>
                <RIN>RIN 1219-AB36</RIN>
                <SUBJECT>Lowering Miners' Exposure to Respirable Crystalline Silica and Improving Respiratory Protection; Delay of Effective Date of Conforming Amendments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Mine Safety and Health Administration (MSHA), Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; delay of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>MSHA is issuing this notification following a judicial stay of the compliance deadlines established in the 2024 final rule titled “Lowering Miners' Exposure to Respirable Crystalline Silica and Improving Respiratory Protection” (2024 Silica Rule). The 2024 Silica Rule made conforming amendments for metal and nonmetal (MNM) standards that are scheduled to take effect on April 8, 2026. Since a judicial stay is in effect, this notification delays the conforming amendments indefinitely, pending judicial review.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        As of April 6, 2026, the effective date of amendments 4, 5, 8, 9, 13, 14, 17, and 18 published at 89 FR 28218, April 18, 2024, is delayed indefinitely, pending judicial review. MSHA will publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing further action once the court-ordered stay is terminated.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jessica D. Senk, Acting Director, Office of Standards, Regulations, and Variances, MSHA at 202-693-9440 (voice). This is not a toll-free number.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>On April 18, 2024, MSHA published the 2024 Silica Rule, which amended MSHA's existing standards for respirable crystalline silica and respiratory protection. The 2024 Silica Rule established 30 CFR part 60, a standalone standard for respirable crystalline silica which lowers the permissible exposure limit (PEL) for respirable crystalline silica at coal and MNM mines. The 2024 Silica Rule also made conforming amendments in 30 CFR parts 56 and 57 to align with the new part 60.</P>
                <P>The 2024 Silica Rule established an effective date of April 8, 2026, for the conforming amendments in 30 CFR parts 56 and 57. The preamble in the 2024 Silica Rule explained that the existing standards in 30 CFR parts 56 and 57 would remain in place until April 8, 2026, to ensure that MNM miners would continue to be protected until the conforming amendments were in effect (89 FR 28348).</P>
                <P>
                    Following publication of the 2024 Silica Rule, industry groups filed petitions in the United States Court of Appeals for the Eighth Circuit (Court). On April 11, 2025, the Court issued an order staying the 2024 Silica Rule's compliance deadlines until the Court completes a substantive review of the petition. The judicial stay delaying compliance with the 2024 Silica Rule is still in effect. Therefore, the existing standards in 30 CFR 56.5001, 56.5005, 57.5001, and 57.5005 are still in effect and the conforming amendments in 30 CFR 56.5001T, 56.5005T, 57.5001T, and 
                    <PRTPAGE P="17144"/>
                    57.5005T are delayed indefinitely, pending judicial review.
                </P>
                <HD SOURCE="HD1">Discussion of Changes to Parts 56 and 57</HD>
                <P>
                    In the 2024 Final Rule, MSHA provided a specific set of instructions to the Office of the Federal Register for the conforming amendments. The instructions established temporary sections with the new requirements that will replace the existing sections in the CFR on the effective date. This was required for the 
                    <E T="04">Federal Register</E>
                     to maintain the existing standards in CFR parts 56 and 57 until April 8, 2026. In the 2024 Silica Rule, the conforming amendments were published to temporary sections, designated by the suffix “T” at the end of the section number (
                    <E T="03">e.g.,</E>
                     § 56.5001T). These temporary sections indicate how the paragraphs will read on the effective date for the conforming amendments. On the effective date, the existing sections in parts 56 and 57 will be removed and the temporary sections associated with the conforming amendments will replace the existing sections without the “T” designation (
                    <E T="03">e.g.</E>
                     § 56.5001T will be redesignated § 56.5001). With the redesignation, compliance with the conforming amendments will be required.
                </P>
                <P>This notification ensures the Court's order staying compliance with the 2024 Silica Rule is carried out by indefinitely delaying the effective date for the conforming amendments to 30 CFR parts 56 and 57. Until the Court's stay is terminated, MNM mine operators must continue to follow the existing standards in parts 56 and 57.</P>
                <HD SOURCE="HD1">Indefinite Delay for Conforming Amendments to Parts 56 and 57</HD>
                <P>In accordance with the Court order, MSHA will continue to enforce the existing standards in 30 CFR 56.5001, 56.5005, 57.5001, and 57.5005 indefinitely, until the Court-ordered stay is terminated and there is a resolution on how to proceed. MSHA will also delay enforcement of the conforming amendments in 30 CFR 56.5001T, 56.5005T, 57.5001T, and 57.5005T until that time.</P>
                <HD SOURCE="HD1">Procedural Issues and Regulatory Review</HD>
                <P>This ministerial action delays the effective date for the conforming amendments in 30 CFR parts 56 and 57 in response to the Court-ordered mandate issued on April 11, 2025. This action is not subject to review by the Office of Management and Budget (OMB) under Executive Order (E.O.) 12866, “Regulatory Planning and Review” 58 FR 51735 (Oct. 4, 1993).</P>
                <P>Section 553(b) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)(B)) provides that, when an agency for good cause finds that notice and public procedure are impracticable, unnecessary, or contrary to the public interest, the agency may issue a rule without providing notice and an opportunity for public comment. MSHA has determined that there is good cause for issuing this final rule without the opportunity for notice and comment because this ministerial action merely reflects the Court's April 11, 2025, order staying the 2024 Silica Rule's compliance deadlines. The Agency lacks discretion to depart from the Court's mandate.</P>
                <P>
                    In addition, this action is not subject to the Regulatory Flexibility Act (RFA) (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). The RFA applies only to rules subject to notice and comment rulemaking requirements under the APA.
                </P>
                <P>
                    This action imposes no new information collection or recordkeeping requirements that require approval by OMB under the Paperwork Reduction Act (PRA) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ). Accordingly, OMB clearance is not required under the Paperwork Reduction Act.
                </P>
                <P>MSHA has examined this final rule and has determined that it is consistent with the policies and directives outlined in E.O. 14154, “Unleashing American Energy” 90 FR 8353 (Jan. 29, 2025); E.O. 14192, “Unleashing Prosperity Through Deregulation” 90 FR 9065 (Feb. 6, 2025); E.O. 14267, “Reducing Anti-Competitive Regulatory Barriers” 90 FR 15629 (Apr. 9, 2025); and the Presidential Memorandum, “Delivering Emergency Price Relief for American Families and Defeating the Cost-of-Living Crisis” 90 FR 8245 (Jan. 28, 2025).</P>
                <P>As required by 5 U.S.C. 801, MSHA will report to Congress on the promulgation of this rule before its effective date. The report will state that it has been determined that the rule is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
                <SIG>
                    <NAME>Jessica D. Senk,</NAME>
                    <TITLE>Acting Director for the Office of Standards, Regulations, and Variances, Mine Safety and Health Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06584 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4520-43-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R09-OAR-2025-2833; FRL-13057-02-R9]</DEPDOC>
                <SUBJECT>Determination of Attainment by the Attainment Date But for International Emissions for the 2015 Ozone National Ambient Air Quality Standards; Phoenix-Mesa Nonattainment Area, Arizona</SUBJECT>
                <HD SOURCE="HD2">Correction</HD>
                <P>In rule document 2026-05601 beginning on page 13777 in the issue of Monday, March 23, 2026, make the following correction:</P>
                <P>On page 13778, in the first column, in the 14th and 15th lines, “March 23, 2026” should read “April 22, 2026”.</P>
            </PREAMB>
            <FRDOC>[FR Doc. C1-2026-05601 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 0099-10-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <CFR>49 CFR Part 571</CFR>
                <DEPDOC>[Docket No. NHTSA-2026-0727]</DEPDOC>
                <RIN>RIN 2127-AM80</RIN>
                <SUBJECT>Federal Motor Vehicle Safety Standards; Occupant Crash Protection, Seat Belt Reminder Systems</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This interim final rule amends the seat belt warning requirements in Federal Motor Vehicle Safety Standard (FMVSS) No. 208, “Occupant crash protection” in response to petitions for reconsideration of the January 2025 final rule. This interim final rule delays the compliance dates and makes technical clarifications to the regulatory text. NHTSA denies the remainder of the requests. Though these amendments are effective immediately, to benefit from comments interested parties and the public may have, NHTSA requests that any comments be submitted to the docket for this rule. Following the close of the comment period, NHTSA will publish a final rule responding to any comments received and making any appropriate changes to the interim final rule.</P>
                </SUM>
                <EFFDATE>
                    <PRTPAGE P="17145"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This interim final rule is effective April 6, 2026. Comments concerning this document are due no later than May 21, 2026. The compliance date of this interim final rule is September 1, 2028, with optional early compliance permitted. Multi-stage manufacturers and alterers have an additional year to comply.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments electronically to the docket identified in the heading of this document by visiting the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>Alternatively, you can file comments using the following methods:</P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management, U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Suite W58-213, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays. To be sure someone is there to help you, please call (202) 366-9826 or (202) 366-9317 before coming.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency name and docket number or Regulatory Information Number (RIN) for this rulemaking. For detailed instructions on submitting comments and additional information on the rulemaking process, see the Public Participation heading of the 
                        <E T="02">Supplementary Information</E>
                         section of this document. Note that all comments received will be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided. Please see the Privacy Act heading below.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received, go to 
                        <E T="03">https://www.regulations.gov</E>
                         or the street address listed above. Follow the online instructions for accessing the dockets via internet.
                    </P>
                    <P>
                        <E T="03">Confidential Business Information:</E>
                         If you claim that any of the information in your comment (including any additional documents or attachments) constitutes confidential business information within the meaning of 5 U.S.C. 552(b)(4) or is protected from disclosure pursuant to 18 U.S.C. 1905, please see the detailed instructions given under the Public Participation heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                    <P>
                        <E T="03">Privacy Act:</E>
                         Please see the Privacy Act heading under the Regulatory Analyses section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For non-legal issues, you may contact Ms. Carla Rush, Office of Crashworthiness Standards (
                        <E T="03">Carla.Rush@dot.gov;</E>
                         facsimile: (202) 493-2739). For legal issues, you may contact Mr. John Piazza, Office of Chief Counsel (
                        <E T="03">John.Piazza@dot.gov</E>
                        ). You can reach these officials by phone at 202-366-1810. Address: National Highway Traffic Safety Administration, U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building, Washington, DC 20590.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP-2">II. Petitions for Reconsideration</FP>
                    <FP SOURCE="FP-2">III. Response to Petitions</FP>
                    <FP SOURCE="FP1-2">a. Lead Time</FP>
                    <FP SOURCE="FP1-2">b. Front Seat Belt First-Phase Audible Warning Duration Requirement</FP>
                    <FP SOURCE="FP1-2">c. Visibility of Rear Seat Belt Visual Warning in Vehicles With No Driver's Designated Seating Position</FP>
                    <FP SOURCE="FP1-2">d. Front Seat Belt Audible Warning Trigger Requirement</FP>
                    <FP SOURCE="FP1-2">e. Rear Seat Belt Warning System Occupancy Criteria</FP>
                    <FP SOURCE="FP1-2">f. Rear Seat Change-Of-Status Warning Requirement for Two-Door Vehicles</FP>
                    <FP SOURCE="FP1-2">g. Telltales Associated With Multiple Front Outboard Seats</FP>
                    <FP SOURCE="FP-2">IV. Basis for Issuing an Interim Final Rule Effective Immediately</FP>
                    <FP SOURCE="FP-2">V. Request for Comment</FP>
                    <FP SOURCE="FP-2">VI. Rulemaking Analyses and Notices</FP>
                    <FP SOURCE="FP-2">VII. Public Participation</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On January 3, 2025, NHTSA published a final rule (90 FR 390) that amended the seat belt warning system provisions in FMVSS No. 208, “Occupant crash protection.” The final rule followed a 2023 Notice of Proposed Rulemaking (NPRM).
                    <SU>1</SU>
                    <FTREF/>
                     The final rule had two main components. The first required a seat belt warning for the rear seats. The second updated and enhanced the current seat belt warning requirements for the driver's seat belt and extended those requirements to the front outboard passenger seat. The rule completed NHTSA's response to a mandate in the Moving Ahead for Progress in the 21st Century Act (MAP-21) 
                    <SU>2</SU>
                    <FTREF/>
                     that directed NHTSA to initiate a rulemaking to require a seat belt warning for the rear seats in motor vehicles; it also completed NHTSA's action on a rulemaking petition from Public Citizen and Advocates for Highway and Auto Safety for the same rule. The final rule applies (with some exceptions) to passenger cars, trucks, most buses, and multipurpose passenger vehicles (MPVs) with a gross vehicle weight rating (GVWR) of 4,536 kilograms (10,000 pounds) or less.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         88 FR 61674 (Sept. 7, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law 112-141 (2012).
                    </P>
                </FTNT>
                <P>The final rule established a compliance date for the amendments as follows. Covered vehicles must comply with the front seat belt warning system requirements by September 1, 2026, and the rear seat belt warning system requirements by September 1, 2027, with optional early compliance permitted. Consistent with 49 CFR 571.8(b), multi-stage manufacturers and alterers have an additional year to comply.</P>
                <HD SOURCE="HD1">II. Petitions for Reconsideration</HD>
                <P>
                    NHTSA regulations allow any interested person to petition the Administrator for reconsideration of a rule.
                    <SU>3</SU>
                    <FTREF/>
                     Under NHTSA's regulations, petitions for reconsideration must explain why compliance with the rule is not practicable, is unreasonable, or is not in the public interest. Petitions must be received within 45 days of the publication of the final rule.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         49 CFR 553.35.
                    </P>
                </FTNT>
                <P>
                    NHTSA received petitions for reconsideration of the final rule from IEE Sensing Inc. (IEE); 
                    <SU>4</SU>
                    <FTREF/>
                     the Alliance for Automotive Innovation (Auto Innovators); 
                    <SU>5</SU>
                    <FTREF/>
                     Volkswagen Group of America (Volkswagen); 
                    <SU>6</SU>
                    <FTREF/>
                     and the Autonomous Vehicle Industry Association (AVIA).
                    <SU>7</SU>
                    <FTREF/>
                     Volkswagen supported Auto Innovators' petition. Auto Innovators also submitted supplemental information to NHTSA.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Docket No. NHTSA-2024-0071-0007.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Docket No. NHTSA-2024-0071-0006.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Docket No. NHTSA-2024-0071-0004.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Docket No. NHTSA-2024-0071-0005.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Docket No. NHTSA-2024-0071-0008.
                    </P>
                </FTNT>
                <P>Generally, the issues raised by the petitioners are of two types. Auto Innovators and Volkswagen asked NHTSA to delay the compliance date for the requirements, and all petitioners requested revisions or clarifications of certain aspects of the rule. These requests and NHTSA's responses are discussed below.</P>
                <HD SOURCE="HD1">III. Response to Petitions</HD>
                <HD SOURCE="HD2">a. Lead time</HD>
                <P>The final rule established a compliance date of September 1, 2026 for the front seat belt warning system requirements and September 1, 2027 for the rear seat belt warning system requirements, with optional early compliance. Consistent with 49 CFR 571.8(b), multi-stage manufacturers and alterers were given an additional year to comply.</P>
                <P>
                    Comments on the NPRM regarding lead time were mixed. Auto Innovators and other industry commenters requested additional lead time. For example, Auto Innovators, Ford, and 
                    <PRTPAGE P="17146"/>
                    Honda requested a synchronized two-year phase-in for both the front and rear row seating position requirements that begins three years after publication of the final rule. On the other hand, other commenters requested less lead time. For example, Advocates for Highway and Auto Safety (Advocates) and Public Citizen stated that one year should be sufficient for rear systems, noting that the Insurance Institute for Highway Safety (IIHS) testing has demonstrated that this deadline is achievable and that delaying will cost lives.
                </P>
                <HD SOURCE="HD3">Reconsideration Requests</HD>
                <P>Auto Innovators requested that the agency delay the start date for the front seat belt warning system requirements to September 1, 2027, and delay the start date for the rear seat belt warning system requirements to September 1, 2028. With respect to the requirements for the front seat belts, Auto Innovators stated that implementing the rule will require significant hardware and software changes to support occupant detection, possible modifications to the instrument panel for the visual warnings, and changes to account for the audible warning requirements. It also argued that the increased complexity of the test procedures will require time and resource-intensive design, development, and validation. Auto Innovators cited similar concerns with respect to meeting the rear seat belt reminder system requirements, such as solving design challenges associated with folding or removable seats and developing a change-of-status audible warning. Auto Innovators also commented that implementing changes such as those required by the final rule to vehicles that have already completed development, or are in the late stages of development, is highly disruptive, and that it may not be possible for Tier 1 suppliers to meet the updated timelines. Volkswagen supported Auto Innovators' petition.</P>
                <P>In its supplemental submission, Auto Innovators provided additional information based on a survey it conducted of its members to better understand the impact of the final rule based on the current lead time. Based on the survey, it identified that the most significant compliance challenges posed by the final rule stem from the need to either redesign the instrument panel to accommodate the requirements of the rule (for the front and rear seats) or redesign existing seat belt reminder systems that were voluntarily installed. Auto Innovators stated that some manufacturers reported already incurring costs because of the current lead time, but because manufacturers are still in the process of adjusting their production schedules to meet the final rule, it is not possible to assess what the overall cost impact will be. Further, Auto Innovators stated that while cost is a factor, its members were more concerned with the practicability of making late-stage design changes (specifically, about not having enough time to test software for bugs or unintended consequences), and that unpredictable results during validation could require launch delays or even cancellations. Auto Innovators stated that while manufacturers typically require between 24 and 36 months to validate a new software rollout on one model, the final rule allows only 15 months to validate new software on all makes/models, which will be difficult-to-impossible to accomplish. It further stated that “[t]here seems to be strong consensus among our members that delays will happen, but the actual volume, or the models at risk, are unknown until the software/hardware validation is finished.”</P>
                <P>
                    Auto Innovators also requested that the agency implement a two-year phase-in of the front seat belt warning requirements if NHTSA does not adopt Auto Innovators' requested changes to those requirements.
                    <SU>9</SU>
                    <FTREF/>
                     Specifically, Auto Innovators requested a two-year phase-in under which 50 percent of covered vehicles would comply beginning on September 1, 2027, and 100 percent of covered vehicles would comply by September 1, 2028.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Those requested changes are discussed in Section III.g.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>On consideration of the petitions and additional information submitted to NHTSA, NHTSA concludes that Auto Innovators' arguments for delaying the compliance dates have merit. In response to Auto Innovators' request to amend the front seat belt visual warning requirements (see Section III.g.), NHTSA is extending the compliance date for the front seat belt warning requirements to 2028. Instead of specifying the phase-in requested by Auto Innovators, NHTSA is unifying the compliance dates for the front and rear requirements, so that full compliance with the front and rear seat belt warning requirements will need to be met by September 1, 2028. Taking into account typical design cycles, the necessary adjustments to existing systems, and the implementation of a rear seat belt warning system in some vehicles, NHTSA concludes the burden on manufacturers is extensive enough to warrant such a delay and unification of the compliance dates.</P>
                <P>The change in lead time provides regulatory relief and addresses a potential economic disruption to the light vehicle market based on new information not available at the time that the Final Regulatory Impact Analysis (FRIA) was developed in support of the 2025 final rule.</P>
                <P>Based on the information submitted to NHTSA, light vehicle manufacturers are facing challenges in ensuring full compliance with the requirements of the 2025 final rule within the current lead time. The challenges faced by light vehicle manufacturers are based on the time needed to validate their systems, to redesign instrument panels, and to redesign current voluntarily-installed systems to meet the requirements for all models. As a result of these challenges, light vehicle manufacturers who are working towards meeting the requirements of the 2025 final rule within the current lead time would likely incur greater costs than were estimated in the FRIA and still potentially face noncompliance. NHTSA has developed a Regulatory Impact Analysis (RIA) in support of this interim final rule, included in the docket for this rulemaking, that provides an assessment of the benefits and costs associated with the rule. The assessment is based on available data, and NHTSA requests comments on potential costs and benefits not reflected in those estimates.</P>
                <P>The RIA takes into account new information that indicates light vehicle manufacturers are facing challenges in ensuring full compliance across their entire fleet under the given lead time. To ensure full compliance within the current lead time, light vehicle manufacturers may incur additional costs associated with conducting validation tests in an expedited manner and potential late-stage design changes. Given any uncertainty in meeting the requirements, vehicle manufacturers are faced with the decision to either move forward in an effort to meet the requirements and take on additional costs or delay the production of that vehicle until they can ensure it would meet the requirements. NHTSA believes that these decisions have already been made for MY2027 and MY2028, which would be produced during the extension in lead time. In addition, as the compliance dates of the 2025 SBWS final rule grow closer, any deviation from those current production plans would become increasingly costly or even infeasible.</P>
                <P>
                    Due to limitations, NHTSA is unable to quantify benefits and costs under the baseline and, therefore, is unable to estimate the incremental benefits and 
                    <PRTPAGE P="17147"/>
                    costs under the IFR. More specifically, NHTSA is unable to establish which makes and models would face challenges in meeting the requirements, assess the total number of vehicles impacted, how manufacturers would operate in facing those challenges, and the resulting impacts on consumers, safety outcomes, and the light vehicle market as a whole. As a result of these limitations, NHTSA discusses the benefits and costs qualitatively and assesses the overall impacts of this IFR based on the plausible range of outcomes.
                </P>
                <P>For those vehicles that can meet the requirements under the current lead time, with or without additional costs, the extension in lead time would have no impact on benefits or costs. For those vehicles that would not be able to meet the requirements under the current lead time, regardless of cost, the extension in lead time provides regulatory relief that may result in cost savings. These cost savings would result from the case that, in absence of the extension in lead time, manufacturers would continue to dedicate resources and costs towards testing and validating these systems under a timeline that was not feasible.</P>
                <P>Overall, the extension in lead time provides enough time for vehicle manufacturers to operate in a manner that ensures that they can achieve compliance with the requirements with potential cost savings. Therefore, on net, the extension in lead time provided by IFR would be beneficial to society.</P>
                <HD SOURCE="HD2">b. Front Seat Belt First-Phase Audible Warning Duration Requirement</HD>
                <P>The final rule regulatory text in S7.5(b)(2)(ii) states that the first phase audible warning for the front seats “. . . must continue for 30 seconds, until the seat belt that triggered the warning is in use, until the seat is no longer occupied, or until the second-phase warning activates, whichever comes first.”</P>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>Volkswagen noted that this language is different than that used in the rear seat change-of-status warning requirement which specifies that the warning must last “at least 30 seconds.” However, Volkswagen also noted that there were several references in the preamble of the final rule that indicate the first phase audible warning must last for “at least” 30 seconds, suggesting that it was not NHTSA's intent to limit the warning to 30 seconds. Volkswagen therefore requested changing the regulatory text to “at least 30 seconds.”</P>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>Volkswagen is correct that it was not NHTSA's intent to limit the front seat belt first-phase audible warning to 30 seconds. This interim final rule revises the regulatory text to clarify this. NHTSA seeks comment on this clarification.</P>
                <HD SOURCE="HD2">c. Visibility of Rear Seat Belt Visual Warning in Vehicles With No Driver's Designated Seating Position</HD>
                <P>
                    The final rule requires that the rear seat belt visual warning must be visible from the driver's seat 
                    <SU>10</SU>
                    <FTREF/>
                     and does not include any provisions applicable to vehicles equipped with an Automated Driving System (ADS). The final rule does, however, include visibility requirements for the front seat belt warning specifically tailored to ADS-equipped vehicles. Specifically, the final rule requires that for dual-mode ADS-equipped vehicles that still have a driver's seat, the visual warning for the front outboard passenger seat belt must be visible from the front outboard passenger seat. For ADS vehicles without a driver's seating position, the final rule requires that the visual warning for each outboard designated seating position be visible from each outboard passenger seating position (
                    <E T="03">i.e.,</E>
                     the visual warning for the outboard seat on the left must be visible from both the left and right outboard seats, and same for the outboard seat on the right). In the final rule NHTSA stated that the visibility of rear seat belt warnings for ADS-equipped vehicles was outside the scope of the rule and noted that research was underway.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         S7.5(c)(3)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>AVIA disagreed that such research is necessary or that rear seat belt warnings for ADS-dedicated vehicles should be out of scope (regardless of seating configuration). AVIA petitioned NHTSA to modify the final rule to require that, in the absence of a driver's designated seating position, all rear outboard visual warnings should be visible to each front outboard seating position.</P>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>
                    NHTSA is denying this request. NHTSA continues to believe that the visibility of the rear seat belt warnings for ADS-equipped vehicles is out of scope of the rule, and continues to research this issue to determine the most effective implementation of telltales and warnings for ADS-equipped vehicles. While AVIA's proposed modification would provide consistency in the visual warning requirements for front and rear designated seating positions, we note that the use cases for front row and rear row occupancy in vehicles without a driver's designated seating position may differ from those with a driver's designated seating position and are not yet well-defined. For example, in a rideshare vehicle there may be cases where only the rear seats are occupied, and a visual warning visible to each front outboard seating position may not be visible to the rear seat occupants. Thus, such a warning would be ineffective. Similarly, there may be cases where the vehicle occupants of a rideshare vehicle do not know each other, thus when the front outboard seat occupants are presented visual warnings related to rear seat belt usage, they may not feel compelled to act. Effective implementation of the visual warnings in vehicles with unconventional seating (and other related considerations, such as bi-directional vehicles) would also need to be taken into consideration. NHTSA plans to issue a separate rulemaking document that will focus on telltales and warnings for ADS-equipped vehicles.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">https://www.reginfo.gov/public/do/eAgendaViewRule?pubId=202410&amp;RIN=2127-AM07.</E>
                    </P>
                </FTNT>
                <P>However, we note that manufacturers of ADS-equipped vehicles, in complying with the front seat belt visual warning requirement for vehicles without a driver's designated seating position (S7.5(b)(1)(iii)) by locating the visual warnings for each front outboard passenger designated seating position such that they are visible from each front outboard passenger designated seating position, may choose to locate the visual warnings for the rear seat designated seating positions in the same location. NHTSA has considered this issue and determined that the final regulatory text would not prohibit such an implementation.</P>
                <P>Manufacturers of ADS-equipped vehicles without a driver's designated seating position can petition the agency for an exemption from S7.5(c)(3)(ii), provided that an alternate approach to effective communication of rear seat belt warnings to the rear seat occupants is implemented.</P>
                <HD SOURCE="HD2">d. Front Seat Belt Audible Warning Trigger Requirement</HD>
                <P>
                    The final rule requires that the front seat belt first-phase audible warning activate whenever the ignition switch is placed in the “on” or “start” position, “or upon manual activation of the propulsion system, but prior to the vehicle being placed in `possible active 
                    <PRTPAGE P="17148"/>
                    driving mode' as defined by FMVSS No. 305,” among other trigger conditions.
                </P>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>Volkswagen requested clarification on whether the option to activate the front seat belt first-phase audible warning not only at ignition but also at activation of the propulsion system applies to internal combustion engine (ICE) vehicles that have been shifted into a reverse or driving gear as well as electric vehicles (EVs).</P>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>
                    The final rule requires that the relevant trigger for the first-phase audible warning in ICE vehicles is when the ignition switch is placed in the “on” or “start” position. The proposed regulatory text referred simply to the ignition switch being in the “on” or “start” position. However, commenters pointed out that this did not take EVs into account. NHTSA agreed, and added the language to which VW refers (that the warning activate upon manual activation of the propulsion system, but before the vehicle is placed in “possible active driving mode” as defined by FMVSS No. 305). As we explained in the final rule, our goal in adding this language was to specify a time in the start-up process to begin the start-of-trip warning for EVs that is roughly the same as the time we specified for vehicles with a conventional ignition switch such that the safety benefits for EVs would be the same as for ignition-equipped vehicles. That is, the intent of the language was to specify a trigger for EVs that approximated the trigger for ICE vehicles, not the other way around. Moreover, VW's suggested change would permit the audible warning in an ICE vehicle to be delayed until the vehicle is shifted into gear. As NHTSA explained in both the NPRM 
                    <SU>12</SU>
                    <FTREF/>
                     and final rule, we believe that for ICE vehicles, basing the trigger on the ignition switch is preferable to delaying the warning until the vehicle is placed in gear. With that delay, there could be instances where a driver would pull out onto the road before the warning starts and before passengers have belted.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         88 FR 61674 (Sept. 7, 2023).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">e. Rear Seat Belt Warning System Occupancy Criteria</HD>
                <P>The use of occupant detection enables the use of more effective warnings, such as audible alerts. NHTSA recognized in the final rule, however, that occupant detection for the rear seats continues to present technological and cost challenges, so the final rule does not require or necessitate occupant detection to meet the rear seat belt warning system requirements. (Approximately 7 percent of MY 2022 vehicles in the U.S. were equipped with occupant detection in the rear seats.) The final rule requires only a start-of-trip visual warning indicating how many or which rear seat belts are in use and/or not in use; this necessitates a seat belt buckle sensor and associated components, not any occupant detection capabilities. For vehicles that manufacturers equip voluntarily with occupant detection, the final rule specifies that a visual warning is not required for an unoccupied seat.</P>
                <P>
                    For testing the seat belt warning with an occupied seat, the final rule specifies (at the option of the manufacturer) either an anthropomorphic test device at least as large as a 49 CFR part 572, subpart N 6-year-old child dummy or a human occupant 21 kg (46.5 lbs.) or more in weight and 114 cm (45 inches) or more in height.
                    <SU>13</SU>
                    <FTREF/>
                     This differs from Economic Commission for Europe (ECE) Regulation No. 16 (R16), which specifies the use of a fifth percentile female (108 lbs. [50 kg]) or similar weight.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         These are the bottom of the ranges specified in FMVSS No. 208 S29.1(e) for the weight and height of a human child who may be used in certain of the advanced air bag testing in place of the six-year-old child dummy. The child 6-year-old dummy weighs approximately 24 kg (53 lb).
                    </P>
                </FTNT>
                <P>A number of commenters to the NPRM disagreed with specifying a six-year-old child dummy and recommended specifying criteria corresponding to a fifth percentile female. Among other things, they identified technological issues with detecting occupants as small as a six-year-old. They also commented that vehicle models already equipped with rear seat occupant detection were based on detecting a fifth percentile female and argued that if NHTSA specified the use of an occupant corresponding to a six-year-old, manufacturers would be forced to downgrade the rear seat belt warning systems in these vehicles by removing the occupant detection.</P>
                <P>
                    NHTSA finalized the use of a six-year-old child dummy because it determined that a system based on a fifth percentile female could result in unbelted child occupants in the rear not benefitting from the seat belt warning. For instance, if a negative-only system 
                    <SU>14</SU>
                    <FTREF/>
                     with occupant detection did not detect an unbelted child smaller than the fifth percentile female seated in a rear seat, the visual warning would not indicate an unbelted child occupant (
                    <E T="03">e.g.,</E>
                     for systems with a pictogram that indicates which seat are not in use, the pictogram would likely display something like a “grayed-out” seat to indicate that the system was registering a seat as unoccupied). In this scenario, the driver may not realize that the system is not detecting the unbelted child occupant and may believe the child is restrained when they are not. We noted that this concern is not hypothetical and pointed to an owner's manual alerting the owner that the seat belt system might not detect a child (or small adult) sitting in the seat. We also noted that the fact that the system does not work for some classes of occupants could also lead the driver to be less likely to respond to accurate warnings, and that these shortcomings could also affect consumer acceptance.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         A negative-only system indicates how many or which rear seat belts are not in use. A negative-only system with occupant detection indicates how many or which of the occupied seats have seat belts which are not in use.
                    </P>
                </FTNT>
                <P>NHTSA recognized the technical and cost challenges detection of a six-year-old presents, but noted that the final rule does not require occupant detection. We also suggested that these challenges were not insurmountable. The final rule acknowledged that because the belt use rates for children ages 6 to 10 are already so high, there would be much smaller monetizable benefits for those children. There would be greater benefits for older children, but because NHTSA did not have the data for older children broken out from the data for adults, NHTSA was unable to specifically estimate the benefits for older children as a group. NHTSA acknowledged that specifying the 6-year-old child dummy could lead manufacturers to offer fewer rear seat belt reminder systems with occupant detection. However, we believed that it was important to ensure that vulnerable younger occupants would be covered by the warning.</P>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>
                    IEE urged NHTSA to specify criteria corresponding to a fifth percentile female for the purposes of testing the seat belt reminder system with an occupied seat. At the same time, however, IEE appeared to recognize that occupant detection based on a fifth percentile female (together with a start-of-trip audible warning for such occupants that are unbelted) are compatible with the final rule. This is possible because the final rule requires simply a visual warning indicating belt status at vehicle start-up; manufacturers may therefore comply with the final rule by providing a visual warning indicating the status of the rear seat belts—regardless of whether the system detects an occupant at a seat—together with an audible warning for occupants at least as large as a fifth percentile 
                    <PRTPAGE P="17149"/>
                    female that the occupant detection system is able to detect. Nevertheless, IEE made a number of arguments in support of its request to specify criteria corresponding to a fifth percentile female.
                </P>
                <P>IEE argued that MAP-21 does not mandate or identify a specific target population for the rear seat belt warning, and that seat belt reminder systems are not a “child safety” technology. IEE also commented that NHTSA did not provide adequate notice and opportunity to comment on the proposal because the final rule interpreted MAP-21 in a way that the NPRM did not; IEE therefore could not take this reasoning into account in its NPRM comments.</P>
                <P>IEE also urged NHTSA to harmonize with ECE R16 and worldwide New Car Assessment Program (NCAP) protocols, which use the fifth percentile female occupancy criteria for performance testing purposes. IEE also commented that the European market shows that vehicle manufacturers respond positively to incentives for enhanced rear seat SBR systems and that fitment with occupant detection has increased greatly since Euro NCAP began incentivizing it in 2018. In addition, IEE argued that this would also lead to lower costs and more technological improvement than the final rule. IEE also argued that the restrictive final rule requirements leave almost no room for NCAP to incentivize performance above and beyond the regulatory minimum.</P>
                <P>
                    IEE also commented on various technological challenges with detecting smaller occupants, such as variables in the vehicle environment and the need to detect consistently and accurately such small occupants for the purposes of a compliance test while at the same time minimizing false warnings. IEE also commented that while additional in-cabin sensing technologies (
                    <E T="03">e.g.,</E>
                     cameras) are installed increasingly for other functionalities, such technologies cannot be considered within the lead time provided by the final rule, but that instead specifying a fifth percentile female would give vehicle manufacturers the opportunity to innovate. IEE also commented that the rule was not practicable with the finalized lead time, and that even if possibly feasible, the efforts to achieve compliance would lead to significant redevelopment costs.
                </P>
                <P>IEE commented that specifying criteria corresponding to a six-year-old would impact negatively the safety of vehicles already available on the market by discouraging vehicle manufacturers from adding voluntarily occupant detection and enhanced features that go beyond the basic compliance option. IEE commented that this would degrade safety because vehicles with occupant detection are able to provide more effective enhanced reminders. IEE also argued that NHTSA provided no evidence to justify safety concerns about vehicles equipped with rear seat belt reminder systems utilizing occupant detection based on a fifth percentile female.</P>
                <P>Related to this, IEE argued that the appropriate target population for occupant detection-enabled systems is teens and adults, not small children, because, as noted in the final rule (and FRIA), the belt use rate for children ages 6 to 10 is very high (98 percent), so that the potential benefits for this group is quite small compared to occupants 11 years old and older. IEE argued that most child occupants 11 years old and older would be detected by sensors designed to detect a fifth percentile female.</P>
                <P>
                    Accordingly, IEE argued that there would be greater benefits if NHTSA were to specify occupant criteria corresponding to a fifth percentile female for the purposes of testing with a rear seat occupied. Based on a 2012 study,
                    <SU>15</SU>
                    <FTREF/>
                     IEE estimated that an audio-visual rear seat belt warning is 3.3 times more effective than a visual-only warning to the driver. Based on this effectiveness estimate, IEE estimated the potential benefits of occupant detection given different fitment rates for occupant detection (the percentage of the fleet with such systems). IEE estimated that for occupants 11 years old and older, benefits range from 53 lives saved (with a 20 percent fitment rate) to 114 (with a 100 percent fitment rate). On the other hand, IEE estimated that under the final rule, which requires 100 percent fitment, only 2 lives would be saved for children ages 6 to 10. IEE argued that this showed that the potential loss for adults (by removing occupant detection and enhanced warnings) is significantly higher than the potential gain for children (by imposing 6-year-old detection).
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         M. Akamatsu, et al “Assessment Method of Effectiveness of Passenger Seat Belt Reminder,” SAE 2012-01-0050 (2012).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>NHTSA is denying IEE's request because the flexibility IEE is requesting is, to a great extent, already permitted by the final rule. To the extent that IEE is requesting additional flexibility that would be enabled by specifying occupancy criteria corresponding to a fifth percentile female, NHTSA is denying the request because NHTSA believes that specifying criteria corresponding to a fifth percentile female would allow a visual start-of-trip warning that would not alert the driver to an unbelted young (small) occupant.</P>
                <P>NHTSA agrees, as IEE points out in its petition, that a visual warning that complies with the final rule can be implemented independently of the occupant detection threshold or any occupant detection. Therefore, the final rule need not—and does not—prohibit vehicles from being equipped with an occupant detection system capable of detecting occupants only at least as large as a fifth percentile female (and providing an audible warning for such occupants who are unbelted), as long as the visual warning complies with the final rule when the vehicle is tested for compliance using an occupant as small as a six-year-old dummy.</P>
                <P>A manufacturer wishing to equip vehicles with an occupant detection system capable of detecting occupants only at least as large as a fifth percentile female could proceed as follows: The final rule requires a visual warning to the driver at vehicle start-up indicating how many or which rear seat belts are in use and/or not in use, irrespective of the occupancy status of the rear seats. It is therefore possible to comply with this visual warning requirement using only buckle sensors; it does not necessitate occupant detection. As long as the seat belt warning system provides a compliant start-of-trip visual warning that informs the driver of the use status of the rear seat belts, irrespective of occupancy, nothing precludes the manufacturer from also equipping the vehicle with an occupant detection system capable of detecting occupants only as large as a fifth percentile female. Further, there is nothing in the final rule preventing the seat belt warning system from using this occupant detection capability to provide, in addition to the visual warning on vehicle start-up, an audible warning.</P>
                <P>
                    So, for example, a manufacturer could equip a vehicle with a full-status system 
                    <SU>16</SU>
                    <FTREF/>
                     with a visual warning indicating the use status of the rear seat belts, and also provide an audible warning if the system detects an unbuckled occupant at least as large as a fifth percentile female. Such a system would be able to pass a compliance test if NHTSA seated a six-year-old dummy, because the final rule requires only a 
                    <PRTPAGE P="17150"/>
                    start-of-trip visual warning which is based on buckle status, not occupancy. The rule would require a visual warning that does not depend on occupant size, and so will not leave out young children who should be belted, while at the same time providing manufacturers the flexibility to utilize occupant detection and an audio-visual warning for larger occupants (teens and adults).
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         A full-status system indicates how many or which rear seat belts are in use and how many or which rear seat belts are not in use. A full-status system with occupant detection indicates, for the occupied rear seats, how many or which rear seat belts are in use and how many or which rear seat belts are not in use.
                    </P>
                </FTNT>
                <P>
                    However, because an occupant detection system based on a fifth percentile female would not be capable of detecting occupants as small as a six-year-old, the system would not be permitted to take advantage of all the flexibilities the final rule would permit for systems capable of detecting a six-year-old. In particular, the system would not be able to take advantage of the exemption in the final rule from providing a start-of-trip visual warning for an unoccupied seat for systems that are able to determine whether a seat is occupied. (ECE R16 has a similar provision for systems with occupant detection.
                    <SU>17</SU>
                    <FTREF/>
                    ) This enables the warning system to provide more streamlined and informative warnings to the driver. It would allow the seat belt reminder system to function as more of a “true” warning (
                    <E T="03">i.e.,</E>
                     providing a warning only if there is an unbuckled occupant).
                    <SU>18</SU>
                    <FTREF/>
                     These types of warnings might be more effective than the warnings a system without occupant detection is able to provide. However, NHTSA is not aware of any data on whether there is a difference in effectiveness between a “true” warning and an informational warning, and, if there is a difference in effectiveness, the magnitude of this difference. NHTSA has concluded that whatever advantages such warnings could offer for older (larger) occupants, out of concern for younger (smaller) occupants the final rule should not allow it.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         The revised final rule similarly permits the rear seat belt change-of-status warning to deactivate if the seat with the unfastened belt is no longer occupied (see Section III.f.).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         A reminder system utilizing occupant detection based on a fifth percentile female would not be permitted to offer such features because if NHTSA tested the system with a six-year-old dummy in one of the rear seats, the system would not comply with the start-of-trip visual warning requirements (it would classify incorrectly the seat as unoccupied, and therefore not provide a visual warning for it).
                    </P>
                </FTNT>
                <P>
                    NHTSA acknowledges that while the finalized regulatory text permits a rear seat belt warning system that utilizes occupant detection based on a fifth percentile female, the final rule preamble introduced ambiguity on this issue inadvertently. In many instances NHTSA stated accurately that the final rule specified the dummy NHTSA would use in testing compliance.
                    <SU>19</SU>
                    <FTREF/>
                     However, at other points, NHTSA stated that the final rule specified the minimum size of occupant that an occupant detection system must be able to detect.
                    <SU>20</SU>
                    <FTREF/>
                     NHTSA is now clarifying that the final rule does not prevent a manufacturer from equipping a vehicle with an occupant detection system capable of detecting occupants only at least as large as a fifth percentile female. Rather, the final rule specifies that for testing purposes NHTSA may seat an occupant as small as the six-year-old dummy and the system must provide a start-of-trip visual warning indicating accurately how many or which rear seat belts are in use and/or not in use.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See, e.g. id.</E>
                         at 410 (“After considering the comments, NHTSA has decided to adopt the proposal to use (at the option of the manufacturer) either a anthropomorphic test device at least as large as a 49 CFR part 572, subpart N 6-year-old child dummy or a person, at the manufacturer's option, that is at least 21 kg in weight and 114 cm in height to define an occupied rear designated seating position for the purposes of testing the rear seat belt reminder system.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See, e.g., id.</E>
                         at 410 (“NHTSA has concluded that it would . . . [be] appropriate to require that an occupant detection system be capable of detecting at least a 6-year-old.”).
                    </P>
                </FTNT>
                <P>
                    NHTSA does not have information on whether already-deployed occupant detection systems would comply with the final rule. If they do, no changes would be necessary to comply with the final rule. If not, they will need to be modified. NHTSA is clarifying in this interim final rule, however, that the system would not need to be capable of detecting a six-year-old child dummy; consequently, any modifications would be to the visual warning. Such changes should not be unduly burdensome and are in line with other changes to already-deployed visual warnings that might be necessitated by other parts of the final rule, such as redesigning the visual display and modifying software. The final rule would therefore not necessarily require manufacturers to downgrade significantly vehicle models that are already equipped with occupant detection systems that detect occupants only as small as a fifth percentile female. To the extent that deployed systems do not already comply with the final rule, IEE is correct that NHTSA does not have data on whether such systems have led to consumer confusion or safety issues (
                    <E T="03">i.e.,</E>
                     the driver believing that an unrestrained younger child was belted). However, as we discuss here and in the final rule, NHTSA is concerned that this leaves out an entire category of occupants. In the absence of data either way, NHTSA is deciding to specify a six-year-old criterion for testing with a seat occupied to ensure that the driver does not receive a visual warning that could lead her or him to believe erroneously an unbelted child is belted.
                </P>
                <P>The clarification that the final rule does not prevent manufacturers from equipping vehicles with an occupant detection system capable of detecting occupants only at least as large as a fifth percentile female resolves many of the arguments IEE raises in its petition. The final rule therefore allows manufacturers to take advantage of most of the enhanced features provided by systems utilizing occupant detection based on a fifth percentile female. The final rule is also compatible with ECE R16 because a rear seat belt system with an occupant detection system designed to detect reliably occupants as small as a six-year-old will also be able to detect larger occupants. The fact that the final rule is compatible with occupant detection based on a fifth percentile female also addresses IEE's argument concerning the take rate for occupant detection in Europe. With respect to lead time, though systems utilizing occupant detection based on a fifth-percentile female might still need some modifications, this should not necessarily be more burdensome than equipping vehicles with rear seat belt warnings generally and providing a compliant warning, especially with the delayed compliance date.</P>
                <P>Turning to IEE's other arguments, NHTSA agrees that MAP-21 does not necessarily require NHTSA to specify an occupant corresponding to a six-year-old child for compliance testing. Among other things, the MAP-21 mandate is subject expressly to § 30111 of the Safety Act, which requires that a safety standard both meet the need for safety and be practicable. In any case, as NHTSA also pointed out in the final rule, the Safety Act gives NHTSA the discretionary authority to issue safety standards to address specific safety needs. NHTSA's decision therefore does not depend on MAP-21 because NHTSA has concluded independently that specifying occupancy criteria corresponding to a six-year-old meets the need for safety and is practicable.</P>
                <P>
                    NHTSA does not disagree that there are technological challenges associated with detecting a six-year-old. NHTSA also appreciates IEE's point, in response to NHTSA's observation in the final rule that some vehicle owners' manuals seem to suggest that some rear seat occupant detection systems may be capable of detecting occupants as small as a six-year-old, that there is a difference between detection of a small object at the edge of a system's performance envelope and a system that 
                    <PRTPAGE P="17151"/>
                    is able to detect reliably smaller occupants in a pass-fail compliance context. It is for these reasons that the final rule does not require occupant detection.
                </P>
                <P>NHTSA does not agree with IEE that the target population for rear seat belt reminders would be represented adequately by specifying criteria corresponding to a fifth percentile female. There are a couple of reasons for this.</P>
                <P>
                    First, NHTSA does not agree with IEE that the target population for rear seat belt reminders is limited to teens and adults and does not or should not include younger (smaller) children. That is, even though NHTSA's regulatory analysis shows that there are fewer monetizable benefits for children ages 6 to 10, NHTSA is not convinced that this group should not get the benefit of a warning. Children 12 years old or younger account for over half of rear seat occupants,
                    <SU>21</SU>
                    <FTREF/>
                     and many of these children (depending on their height and weight) will (and should) be wearing a seat belt.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Based on police-reported crashes documented in the Crash Report Sampling System (CRSS). Out of all sampled crashes from 2016-2022, 57 percent of rear seat occupants were 12 years old or younger.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         88 FR 61674, 
                        <E T="03">See also</E>
                         Stephanie Huang and Matthew P. Reed (2006). Comparison of Child Body Dimensions with Rear Seat Geometry. Warrendale, PA: SAE International. The findings from this study were based on National Automotive Sampling System General Estimates System (NASS-GES) data. It also reported that approximately 70 percent of rear seat occupants of passenger cars, sport utility vehicles, and minivans are children under the age of 18.
                    </P>
                </FTNT>
                <P>
                    Second, IEE's request recognizes implicitly that the target population includes some children smaller than a fifth percentile female. IEE stated that “ `low' belt wearing rates are typically an issue for adults and teenagers” 
                    <SU>23</SU>
                    <FTREF/>
                     and that “[t]he 11+ age group is a good approximation of the population covered by sensors designed for a 5% female detection, and most occupants in that group will be detected[.]” 
                    <SU>24</SU>
                    <FTREF/>
                     However, based on weight, specifying criteria corresponding to a fifth-percentile female ((which weighs 108 lbs. [50 kg])) would exclude the following proportions of children by age, each of which weighs less than 108 lbs.: 
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Comment at pg. 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Comment at pg. 10.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Center for Disease Control Growth Charts for Children 2-20 years of age Data Files, published in May 2000 and available at 
                        <E T="03">https://www.cdc.gov/growthcharts/cdc-data-files.htm</E>
                         (last accessed April 23, 2025).
                    </P>
                </FTNT>
                <P>• 92 percent of 11-year-old boys and 90 percent of 11-year-old girls;</P>
                <P>• 80 percent of 12-year-old boys and 77 percent of 12-year-old girls;</P>
                <P>• 66 percent of 13-year-old boys and 64 percent of 13-year-old girls;</P>
                <P>• 42 percent of 14-year-old boys and 49 percent of 14-year-old girls;</P>
                <P>• 21 percent of 15-year-old boys and 36 percent of 15-year-old girls;</P>
                <P>• 9 percent of 16-year-old boys and 26 percent of 16-year-old girls;</P>
                <P>• 4 percent of 17-year-old boys and 20 percent of 17-year-old girls; and</P>
                <P>• 2 percent of 18-year-old boys and 16 percent of 18-year-old girls.</P>
                <P>NHTSA also does not agree with IEE's benefits analysis, for a few reasons.</P>
                <P>First, IEE's analysis overstates the benefits because a system that detects occupants only at least as large as a fifth percentile female would not be able to detect a non-trivial proportion of the pre-teens and teens that IEE agrees is part of the target population for a rear seat belt warning system. Many pre-teens and teens are smaller than a fifth percentile female and would not be detected by a rear seat belt reminder system employing an occupant detection system able to detect occupants only as large or larger than a fifth percentile female—and so would not get the benefit of an audio-visual warning.</P>
                <P>
                    Second, while NHTSA agrees that a seat belt reminder system that provides an audio-visual warning could be more effective than a visual-only warning, NHTSA is not aware of any persuasive evidence that an audio-visual warning would be three times more effective than a visual-only warning. IEE's effectiveness estimate comes from a 2012 paper that reported the results of an experimental study conducted in Japan on seat belt reminders. That study (which was cited and discussed, but not relied on, in the FRIA) has a number of limitations that make it inappropriate for use in this rulemaking. These limitations stem from the overall design of the study, differences in how seat belt laws are enforced, and seat belt use rates in the U.S. and Japan, among other things. The study was experimental; test subjects were asked to subjectively rate the effectiveness of different types of seat belt reminders. The lack of realism (as opposed to the FRIA, which used observational data) makes the estimates from the study not appropriate for use in this rulemaking. For another thing, the baseline seat belt use rate reported in the study for rear seat occupants in vehicles without a seat belt warning system in Japan was 38 percent. In comparison, the analysis in the FRIA estimated that the baseline rear seat belt use rate without a seat belt warning system in the U.S. was 73.5 percent and 98.2 percent for rear seat occupants ages 6 to 10 and those 11 years and older, respectively.
                    <SU>26</SU>
                    <FTREF/>
                     These differences between Japan and the U.S. mean that any results do not necessarily translate well to the U.S.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         For more discussion, please see the FRIA (page 72).
                    </P>
                </FTNT>
                <P>
                    Third and finally, a three-fold increase in effectiveness does not translate into a three-fold increase in benefits. To estimate benefits, IEE multiplied simply the number of fatalities prevented by three, and adjusts this number based on the fitment rate. This oversimplifies the appropriate benefits estimation in a number of ways. For instance, an appropriate benefits estimation requires more than multiplying simply the number of avoided fatalities by the fitment rate. A proper analysis must examine the incremental benefits of the rule: that is, it must account for the baseline fitment rate and the corresponding seat belt use rate to then account for how seat belt use would change and its resulting impact on both non-fatal injuries and fatalities prevented by seat belts. The FRIA presents this analysis in detail.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         For more discussion, please see the FRIA (page 87).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">f. Rear Seat Change-Of-Status Warning Requirement for Two-Door Vehicles</HD>
                <P>
                    The final rule requires an audio-visual rear seat change-of-status warning that activates whenever a fastened rear seat belt is unfastened while the vehicle is in a forward or reverse drive mode and must last for at least 30 seconds or until the seat belt that triggered the warning is re-fastened. This requirement included an exception for the activation of the rear seat change-of-status warning when a rear door is opened (
                    <E T="03">i.e.,</E>
                     for a drop-off scenario: a change-of-status warning is not required if a rear passenger unbuckles and exits the vehicle).
                </P>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>
                    Volkswagen sought clarification on this requirement and questioned if the front doors are allowed as a trigger for deactivating the rear change-of-status warning in the case of a vehicle that has rear seating positions and only two front doors (
                    <E T="03">i.e.,</E>
                     no rear doors). Volkswagen further requested including a provision for such vehicles to avoid an unnecessary audio-visual warning for a rear seat occupant that has exited the vehicle via a front door, as it has for vehicles that have rear doors.
                </P>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>
                    NHTSA has taken this request into consideration, but is denying the request. The majority of vehicles with rear designated seating positions are 
                    <PRTPAGE P="17152"/>
                    equipped with rear doors (approximately 36 percent of vehicles are two-door vehicles,
                    <SU>28</SU>
                    <FTREF/>
                     but not all of these vehicles have rear designated seating positions). In addition, the requirement that the vehicle must be in a forward or reverse drive mode for a rear seat change-of-status warning to activate aims to mitigate the occurrence of such events. Furthermore, because the change-of-status warning has a required duration that is short, the exposure to the warning in such events would be limited. Lastly, NHTSA determined that specifying simply the use of the front doors would not address sufficiently foreseeable scenarios in which a front door might be opened. For example, if a rear passenger unbuckled their seat belt at the same time that a front passenger exited the vehicle, the change-of-status warning would not be activated for the rear passenger. Therefore, a viable solution would be more complicated than referencing simply the opening of a front door for these vehicles. The additional design changes (
                    <E T="03">e.g.,</E>
                     seat track sensor, seat back angle sensor) and cost that would be necessary for a vehicle to comply with a more robust regulatory specification would likely not be justified by the minimal benefit of such efforts (
                    <E T="03">i.e.,</E>
                     mitigating consumer annoyance by allowing the deactivation of an already short-duration warning).
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Wards Automotive Yearbook, based on average of MY 2017—MY 2021 data.
                    </P>
                </FTNT>
                <P>
                    However, to further mitigate nuisance activations of the change-of-status warning when a rear passenger has exited the vehicle, NHTSA is revising the requirement to add additional deactivation conditions. Specifically, this interim final rule amends the requirements to permit the warning to deactivate if the vehicle is stopped and no longer in forward or reverse drive mode, or until any rear door is opened,
                    <SU>29</SU>
                    <FTREF/>
                     or if the system is able to determine that the seating position that triggered the warning is no longer occupied. A behavioral solution to this issue would be for the driver to learn to put the transmission into the park position (or an equivalent mode for an EV) when offloading a rear seat passenger in a two-door vehicle. NHTSA seeks comment on this provision.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         This additional allowance for the warning to deactivate if a rear door is opened is meant to address change-of-status events where the rear seat passenger opens the door to exit the vehicle after the change-of-status warning is activated, whereas, the door condition in the original regulatory text, that is unchanged by this final rule, prevents the warning from activating if any rear door is open when the change-of-status occurs.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">g. Telltales Associated With Multiple Front Outboard Seats</HD>
                <P>
                    The final rule established several requirements for the front seat belt visual warning. Among other things, it required that the visual warning may be continuous or intermittent and must display the identifying symbol or the words specified in table 2 of FMVSS No. 101 (§ 571.101). It also required, in S7.5(b)(1)(v), that a visual warning associated with multiple front outboard seats must identify clearly the seating positions for which the warnings are intended.
                    <SU>30</SU>
                    <FTREF/>
                     In the preamble of the final rule, NHTSA explained that this requirement did not require a separate telltale for each front seating position nor any particular visual warning design. NHTSA explained that it was giving vehicle manufacturers the flexibility to design their systems such that they can certify in good faith that the visual warning identifies clearly the seating position(s) for which the warning(s) is intended.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         S7.5(b)(1)(v) (“For a visual warning associated with multiple front outboard seats, the visual warning must clearly identify the seating positions for which the warnings are intended.”).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Reconsideration Request</HD>
                <P>
                    Auto Innovators requested that NHTSA modify the requirement that a visual warning associated with multiple front outboard seats must identify the seating position for which the warning was intended. It argued that the requirement is ambiguous and not objectively defined. It also argued that it was unnecessary, because if a visual warning is provided to the driver, the driver should be able to determine if the warning is for them or the front outboard passenger. It argued that the standard should permit the use of a single telltale (
                    <E T="03">i.e.,</E>
                     the longstanding telltale specified in FMVSS No. 101) without any additional identifying visual design elements. To accomplish this, Auto Innovators suggested either deleting S7.5(b)(1)(v) in its entirety or modifying it to specify that “the visual warning may include additional visual information.” Auto Innovators pointed out that some existing vehicles already use a single telltale for multiple front seating positions with no additional identifiers and stated consumers are already familiar with this approach. Auto Innovators also commented that, to the extent that NHTSA does not address its comment regarding visual warnings for multiple outboard seats, additional lead time will be needed to implement necessary hardware and software changes to all vehicle model lines. In this scenario, Auto Innovators requested a two-year phase-in beginning on September 1, 2027 (Y1 50%) with full compliance by September 1, 2028 (Y2 100%).
                </P>
                <HD SOURCE="HD3">Agency Response</HD>
                <P>NHTSA agrees that the regulatory language associated with the requirement that a visual warning associated with multiple front outboard seats must “clearly identify” the seating position for which the warning was intended can be specified more clearly. In this interim final rule, NHTSA revises the regulatory text to specify that the warning must use supplementary symbols, words, or abbreviations to indicate the seating positions for which the warnings are intended. As one example, if the manufacturer provides a pictogram, in addition to the FMVSS No. 101 symbol, indicating the buckle status of all seating positions in the vehicle, this pictogram would satisfy this requirement.</P>
                <P>However, NHTSA is denying Auto Innovators' suggestion to delete S7.5(b)(1)(v) altogether or make it voluntary. NHTSA's response in the preamble to the final rule described why we are requiring that visual warnings associated with multiple front outboard seats identify the seat for which the warning is intended. NHTSA does not have a basis to conclude that a single telltale with no additional identifiers is familiar to customers, as Auto Innovators did not provide data to support this claim. NHTSA continues to believe that visual warnings associated with multiple front outboard seats must identify the seat for which the warning is intended. This is particularly important when the driver is unbelted, where a visual warning that does not identify which seat the warning is for would not provide useful information to the driver as to whether the front outboard passenger is buckled. Though we are denying this aspect of the petition, NHTSA believes that describing the requirements for visual warnings associated with multiple front outboard seats more clearly (as described above), as well as granting a lead time extension (as described below), will satisfy the request from Auto Innovators.</P>
                <P>
                    Removing the requirement would also not align with the level of detail required for the rear seat visual warning, which specifies that the warning must indicate how many or which rear seat belts are in use or not in use. In addition, as noted above, if a manufacturer, in addition to using a single FMVSS No. 101 seat belt telltale symbol for both front seats, uses a pictogram that includes the front seats 
                    <PRTPAGE P="17153"/>
                    (perhaps integrated with a pictogram that is used to comply with the new rear seat belt warning requirements) this would comply with the requirement to “use supplementary symbols, words, or abbreviations to indicate the seating positions for which the warnings are intended.”
                </P>
                <P>In its petition for reconsideration, Auto Innovators stated that, if its proposed modifications to the requirements for visual warnings associated with multiple front outboard seats were not addressed by NHTSA, manufacturers would need additional lead time to implement the necessary system changes. In that case, Auto Innovators asked for a two-year phase-in, where 50 percent of vehicles would need to meet the requirements beginning on September 1, 2027 and 100 percent of vehicles would need to meet the requirements beginning on September 1, 2028. As discussed earlier, this interim final rule provides additional lead time such that the front seat belt warning system requirements would become mandatory starting September 1, 2028. As such, the amended lead time would meet the timeline requested by Auto Innovators if the requirements for visual warnings associated with multiple front outboard seats were not amended as requested. Thus, NHTSA is denying Auto Innovators' request for modifications to the requirements for visual warnings associated with multiple front outboard seats, but granting an extension to lead time that encompasses its requested two-year phase-in.</P>
                <P>In addition, in reviewing this request from Auto Innovators, NHTSA became aware that the requirements for the rear seat visual warning in S7.5(c)(3)(iv) stated that the rear seat change-of-status warning “may use the same telltale as the start of trip warning.” This language may have been understood to preclude the example described earlier, for telltales associated with multiple front outboard seats, where a manufacturer may choose to display a pictogram in addition to the FMVSS No. 101 telltale. Because the final rule required a telltale for the rear seat change-of-status visual warning, the described pictogram approach would not satisfy the requirement. NHTSA is therefore amending S7.5(c)(3)(iv) to replace “telltale” with “visual warning” to enable this design flexibility.</P>
                <P>NHTSA seeks comment on these changes.</P>
                <HD SOURCE="HD1">IV. Basis for Issuing an Interim Final Rule Effective Immediately</HD>
                <P>
                    The Administrative Procedure Act (APA) authorizes agencies to issue a rule without notice and comment, and to make a rule effective sooner than 30 days after its publication, if the agency finds good cause for doing so and provides an explanation in the preamble. Similarly, while the National Traffic and Motor Vehicle Safety Act (Safety Act) 
                    <SU>31</SU>
                    <FTREF/>
                     generally requires that a motor vehicle safety standard may not become effective sooner than the 180th day after the standard is prescribed, it too permits NHTSA to establish an earlier effective date if there is good cause to do so. As we explain below, NHTSA has concluded that there is good cause to issue this interim final rule without notice and comment and to make it effective immediately.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         49 U.S.C. 30101 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Good Cause Justification Under the APA for Waiving Prior Notice and Opportunity for Comment</HD>
                <P>
                    The APA permits an agency to issue a rule without prior notice and opportunity for comment “when the agency for good cause finds (and incorporates the finding and a brief statement of reasons therefor in the rules issued) that notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” 
                    <SU>32</SU>
                    <FTREF/>
                     Impracticable “means a situation in which the due and required execution of the agency functions would be unavoidably prevented by its undertaking public rule-making proceedings.” 
                    <SU>33</SU>
                    <FTREF/>
                     Unnecessary refers to “those situations in which the administrative rule is a routine determination, insignificant in nature and impact, and inconsequential to the industry and to the public.” 
                    <SU>34</SU>
                    <FTREF/>
                     The public interest element of the good cause exception is properly invoked when “the timing and disclosure requirements of the usual procedures would defeat the purpose of the proposal[.]” 
                    <SU>35</SU>
                    <FTREF/>
                     “The question is not whether dispensing with notice and comment would be contrary to the public interest, but whether providing notice and comment would be contrary to the public interest.” 
                    <SU>36</SU>
                    <FTREF/>
                     Providing notice and comment would be impracticable and contrary to the public interest in the specific circumstances of this interim final rule for several reasons.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         5 U.S.C. 553(b)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Cotton,</E>
                         760 F. Supp. 2d 116, 129 (D.D.C. 2011) (citing legislative history) (citations and quotations omitted).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">Mack Trucks, Inc.</E>
                         v. 
                        <E T="03">Envtl. Prot. Agency,</E>
                         682 F.3d 87, 94 (D.C. Cir. 2012) (citations and quotations omitted).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">Id.</E>
                         at 95.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>First, providing prior notice and opportunity for comment would mean that the final rule would be published too late for manufacturers to utilize the extra lead time afforded by this rule. As noted earlier, based on recent information Auto Innovators has submitted to NHTSA, vehicle manufacturers are experiencing design and production challenges such that they may not be able to ensure full compliance of all covered vehicles within the current lead time. Manufacturers, absent this final rule, are designing and planning production for their vehicles based on the fact that the new front seat belt warning requirements become obligatory on September 1, 2026. Production planning (tooling, supply chains, etc.) necessitates that vehicle designs and concomitant production plans be established well before September 1 for production to take place on and after September 1. Therefore, the delay in lead time implemented by this final rule (which NHTSA believes is necessary for the reasons provided in Section III.a,) would likely come too late for at least some vehicle models were NHTSA to provide for notice and comment; by the time NHTSA were to publish a final rule, manufacturers may have already decided to pause production of some vehicle models due to an inability to fully validate rule-compliant front seat belt systems in time for model year 2027. Accordingly, if this final rule is not published sufficiently in advance of September 1, manufacturers would likely have to delay or even cancel production of vehicle models that they had not yet been able to bring into compliance. Any lapses or delays in production can adversely affect manufacturer revenue, operations, and supply chains, and, if the lapse is long enough, could cause delays or even cancellations of model year launches. This could even include models that currently have provided voluntarily rear or front passenger SBRSs that, while not meeting all of the new requirements, do provide safety benefits. This would affect not only vehicle manufacturers and suppliers, but also consumers, who would enjoy fewer choices in the vehicle market; additional costs caused by the delay might also be passed onto consumers.</P>
                <P>
                    Second, NHTSA believes it is reasonable to conclude that there is a non-trivial risk that such launch delays or cancellations would occur and that these would not be isolated occurrences. The new seat belt warning requirements apply to a large majority of the new vehicle fleet. Auto Innovators recently 
                    <PRTPAGE P="17154"/>
                    surveyed its members to “understand the impact of the rule based on the current lead time.” 
                    <SU>37</SU>
                    <FTREF/>
                     It stated that “[t]here seems to be strong consensus among our members” that launch delays or even cancellations would occur, though “the actual volume, or the models at risk, are unknown” until vehicle validation is complete.
                    <SU>38</SU>
                    <FTREF/>
                     Therefore, while NHTSA does not have complete information on this issue and some uncertainty necessarily exists, NHTSA finds that the risk of non-trivial disruption is sufficiently likely to justify waiving notice and comment.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Auto Innovators supplemental submission (Docket No. NHTSA-2024-0071-0008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Other factors also support NHTSA's conclusion that there is good cause to waive notice and comment in these particular circumstances. First, this interim final rule is limited in scope. The rule responds to petitions for reconsideration of the January 2025 final rule. NHTSA received a limited number of petitions on a narrow range of topics, most of which concerned relatively minor technical issues and requests for clarification. This interim final rule does not remove or significantly alter any of the requirements in the January 2025 final rule. The major substantive request that NHTSA received, and the change that this interim final rule makes, is to grant vehicle and equipment manufacturers' request for more lead time. However, even this change to the January 2025 final rule is of relatively limited scope and duration. This interim final rule simply provides an additional year of lead time for the rear seat belt requirements and an additional two years for the front seat belt requirements for manufacturers to produce vehicles that comply with the new requirements. Importantly, we do not expect this interim final rule to lead to any decrease in vehicle safety compared to if we did not issue this interim final rule. In addition, the amendments this interim final rule makes are within the scope of the September 2023 NPRM that the public initially commented on, so that, to a large extent, the public has already had the opportunity to comment, and NHTSA has considered those comments in issuing this interim final rule. Finally, NHTSA has no reason to believe vehicle manufacturers have not made a good faith effort to bring vehicles into compliance with the new requirements in a timely fashion; the fact that this is an issue being faced across the entire industry—as opposed to one or two manufacturers—supports this belief. Providing notice and an opportunity to comment prior to the rule taking effect would therefore be contrary to the public interest and defeat one of the purposes of this interim final rule, which is to provide manufacturers with more lead time to prevent any disruptions to the market. NHTSA therefore believes that the public interest would be best served by foregoing notice and comment in this unusual situation.
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         NHTSA similarly believes that there is good cause to waive notice and comment with respect to the amendment to the regulatory text for the front seat belt first-phase audible warning. This amendment is a minor technical correction that clarifies the regulatory text so that it more clearly expresses the intent of the requirement, as explained in the preamble to the January 2025 final rule.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Good Cause Justification Under the APA and Safety Act for an Immediate Effective Date</HD>
                <P>
                    This interim final rule is effective immediately. While the APA generally requires that the effective date be no sooner than 30 days after the publication date, the APA permits agencies to make rules effective sooner than this for, among other things, “good cause found and published with the rule” 
                    <SU>40</SU>
                    <FTREF/>
                     and rules which grant or recognize an exemption or relieve a restriction.
                    <SU>41</SU>
                    <FTREF/>
                     Similarly, while the Safety Act generally requires that a motor vehicle safety standard may not become effective sooner than the 180th day after the standard is issued, it too permits an earlier effective date if the Secretary (NHTSA by delegation) determines there is good cause and it is in the public interest.
                    <SU>42</SU>
                    <FTREF/>
                     For the reasons discussed above, NHTSA finds there is good cause, and it is in the public interest, for this interim final rule to be effective immediately. In addition, to the extent that this interim final rule relieves a restriction (in that it delays the compliance date), this rule is exempt from the APA's effective date delay requirements on that basis as well.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         5 U.S.C. 553(d)(3) (exception to effective date requirement “as otherwise provided by the agency for good cause found and published with the rule”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         5 U.S.C. 553(d)(1) (exception to effective date requirement for “a substantive rule which grants or recognizes an exemption or relieves a restriction”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         49 U.S.C. 30111(d) (“The Secretary shall specify the effective date of a motor vehicle safety standard prescribed under this chapter in the order prescribing the standard. A standard may not become effective before the 180th day after the standard is prescribed or later than one year after it is prescribed. However, the Secretary may prescribe a different effective date after finding, for good cause shown, that a different effective date is in the public interest and publishing the reasons for the finding.”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Request for Comment</HD>
                <P>As explained above, the Administrative Procedure Act authorizes NHTSA to issue this interim final rule without prior notice or opportunity for public comment. As an interim final rule, this regulation is in effect and binding upon its effective date. No further regulatory action by NHTSA is necessary to make this rule effective. However, to benefit from comments that interested parties and the public may have, NHTSA is requesting that any comments be submitted to the docket for this notice. NHTSA is providing an opportunity for comment on this interim final rule for 45 days after this action's publication date. Comments received in response to this notice will be considered by the agency. Following the close of the comment period, the agency will publish a final rule responding to the comments and making any necessary changes to the provisions of this interim final rule.</P>
                <HD SOURCE="HD1">VI. Rulemaking Analyses and Notices</HD>
                <HD SOURCE="HD2">Executive Orders 12866 and 14192</HD>
                <P>NHTSA has considered the impact of this interim final rule under Executive Order 12866 and Executive Order 14192. NHTSA has considered the costs and benefits of the rule under the principles of these executive orders. Please refer to Section III.a, Lead time and the docketed Regulatory Impact Analysis, for this discussion. The Office of Management and Budget has determined that the interim final rule is a significant regulatory action as defined in section 3(f)(1) of E.O. 12866 and reviewed the rule pursuant to E.O. 12866. This interim final rule is an E.O. 14192 deregulatory action.</P>
                <HD SOURCE="HD2">Promoting International Regulatory Cooperation</HD>
                <P>The policy statement in section 1 of Executive Order 13609 provides that the regulatory approaches taken by foreign governments may differ from those taken by the United States to address similar issues, and that in some cases the differences between them might not be necessary and might impair the ability of American businesses to export and compete internationally. It further recognizes that in meeting shared challenges involving health, safety, and other issues, international regulatory cooperation can identify approaches that are at least as protective as those that are or would be adopted in the absence of such cooperation and can reduce, eliminate, or prevent unnecessary differences in regulatory requirements.</P>
                <P>
                    In addition, section 24211 of the Infrastructure, Investment, and Jobs Act, Global Harmonization, provides that 
                    <PRTPAGE P="17155"/>
                    DOT “shall cooperate, to the maximum extent practicable, with foreign governments, nongovernmental stakeholder groups, the motor vehicle industry, and consumer groups with respect to global harmonization of vehicle regulations as a means for improving motor vehicle safety.” 
                    <SU>43</SU>
                    <FTREF/>
                     As discussed in the September 2023 NPRM and the January 2025 final rule, there are foreign regulations for seat belt reminder requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         H.R. 3684 (117th Congress) (2021).
                    </P>
                </FTNT>
                <P>As discussed in the January 2025 Final Rule, this interim final rule harmonizes with ECE R16, Euro NCAP, and the IIHS protocol as much as possible, but deviates where NHTSA determined deviation was justified with respect to the Safety Act criteria (need for safety, objectivity, and practicability). In general, NHTSA determined that though this rule deviates from these requirements or protocols in some ways, it is not incompatible with them, so that it is possible to design a seat belt reminder system that complies with both this rule and protocols such as R16. The updates included in this interim final rule are intended to further improve compatibility with international standards. Thus, the requirements in this interim final rule are consistent with these international programs and complement those international efforts to increase seat belt use by all vehicle occupants.</P>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>
                    Under the Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612) (as amended by the Small Business Regulatory Enforcement Fairness Act (SBREFA) of 1996; 5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), where a proposed rule must be published for comment by 5 U.S.C. 553 or any other law, agencies must prepare and make available for public comment a regulatory flexibility analysis that describes the effect of the rule on small entities (
                    <E T="03">i.e.,</E>
                     small businesses, small organizations, and small government jurisdictions). No regulatory flexibility analysis is required, however, if the head of an agency or an appropriate designee certifies that the rule will not have a significant economic impact on a substantial number of small entities. Because NHTSA was not required by law to publish a proposed rule, the analytical requirements of the RFA do not apply.
                </P>
                <P>NHTSA has nonetheless analyzed the economic impacts of this rule to determine whether the rule would have a significant economic impact on a substantial number of small entities.</P>
                <P>Under the Small Business Administration's size standards regulations used to define small businesses, manufacturers of the vehicles covered by this rule would fall under North American Industry Classification System (NAICS) No. 336211, Automobile Manufacturing, which has a size standard of 1,000 employees or fewer.</P>
                <P>NHTSA estimates that there are twelve light vehicle manufacturers in the U.S. with 1,000 employees or fewer. As noted in Section 11.1 of the final regulatory impact analysis, the estimated annual vehicle sales for these manufacturers is less than 100 vehicles with a sales price range of $65,900 to $1,600,000. There are several hundred second-stage or final-stage manufacturers and alterers that could be impacted by this rule, some of which may be considered small. Though this analysis is unable to estimate how many small entities may be impacted by the rule, the rule would either have no impact or generate cost savings for those entities.</P>
                <P>The delay in the compliance date would reduce the burden on small entities by providing more time to comply with the new requirements. Revising the regulatory text to clarify that it was not NHTSA's intent to limit the front seat belt first-phase audible warning to 30 seconds also provides manufacturers with more flexibility in designing the system. NHTSA's clarification that the final rule requires that the relevant trigger for the first-phase audible warning in ICE vehicles is when the ignition switch is placed in the “on” or “start” position, and not when the vehicle is in gear, is not a burden on small manufacturers because this mirrors the trigger for the longstanding requirements for the driver's seat belt warning. Amending the rule to specify that the front seat belt visual warning must use supplementary symbols, words, or abbreviations to indicate the seating positions for which the warnings are intended would not have a significant impact because the change merely clarifies the existing regulatory text.</P>
                <P>Therefore, NHTSA has concluded that the rule would not have a significant economic impact on a substantial number of small entities.</P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) (UMRA) requires Federal agencies to assess the effects of regulatory actions that may result in the expenditure by a State, local, or Tribal government, in the aggregate, or by the private sector of $206 million (the value equivalent of $100 million in 1995, adjusted for inflation to 2025) or more in any 1 year. This rule does not contain Federal mandates (under the regulatory provisions of Title II of the UMRA) for State, local and Tribal governments, or the private sector of $206 million or more in any one year. Thus, the analytical requirements of the UMRA do not apply to this action.</P>
                <HD SOURCE="HD2">Executive Order 13175</HD>
                <P>Executive Order 13175 requires Federal agencies to consult and coordinate with Tribes on a government-to-government basis on policies that have Tribal implications, including regulations, legislative comments or proposed legislation, and other policy statements or actions that have substantial direct effects on one or more Indian Tribes, on the relationship between the Federal Government and Indian Tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes. NHTSA has assessed the impact of this interim final rule on Indian tribes and determined that this rule would not have tribal implications that require consultation under Executive Order 13175.</P>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information, unless the collection displays a currently valid Office of Management and Budget (OMB) control number. This rule does not impose any additional information collection requirements requiring OMB approval under the PRA.</P>
                <HD SOURCE="HD2">E-Government Act Compliance</HD>
                <P>
                    NHTSA is committed to complying with the E-Government Act, 2002 to promote the use of the internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes. The E-Government Act of 2002 (Pub. L. 107-347, sec. 208, 116 Stat. 2899, 2921, Dec. 17, 2002), requires Federal agencies to conduct a privacy impact assessment for new or substantially changed technology that collects, maintains, or disseminates information in an identifiable form. No new or substantially changed technology would collect, maintain, or disseminate information as a result of this rule. Accordingly, NHTSA has not conducted a privacy impact assessment.
                    <PRTPAGE P="17156"/>
                </P>
                <HD SOURCE="HD2">Executive Order 13132; Federalism Summary Impact Statement</HD>
                <P>NHTSA has examined this rule pursuant to Executive Order 13132 (64 FR 43255; Aug. 10, 1999) and concluded that no additional consultation with States, local governments, or their representatives is mandated beyond the rulemaking process. The agency has concluded that the rule does not have sufficient federalism implications to warrant consultation with State and local officials or the preparation of a federalism summary impact statement. The rule does not have “substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.” NHTSA rules can have preemptive effect in two ways. First, the National Traffic and Motor Vehicle Safety Act contains an express preemption provision: When a motor vehicle safety standard is in effect under this chapter, a State or a political subdivision of a State may prescribe or continue in effect a standard applicable to the same aspect of performance of a motor vehicle or motor vehicle equipment only if the standard is identical to the standard prescribed under this chapter. 49 U.S.C. 30103(b)(1). It is this statutory command by Congress that preempts any non-identical State legislative and administrative law address the same aspect of performance.</P>
                <P>The express preemption provision described above is subject to a savings clause under which “[c]compliance with a motor vehicle safety standard prescribed under this chapter does not exempt a person from liability at common law.” 49 U.S.C. 30103(e). Pursuant to this provision, State common law tort causes of action against motor vehicle manufacturers that might otherwise be preempted by the express preemption provision are generally preserved. However, the Supreme Court has recognized the possibility, in some instances, of implied preemption of State common law tort causes of action by virtue of NHTSA's rules—even if not expressly preempted.</P>
                <P>
                    This second way that NHTSA rules can preempt is dependent upon the existence of an actual conflict between an FMVSS and the higher standard that would effectively be imposed on motor vehicle manufacturers if someone obtained a State common law tort judgment against the manufacturer—notwithstanding the manufacturer's compliance with the NHTSA standard. Because most NHTSA standards established by an FMVSS are minimum standards, a State common law tort cause of action that seeks to impose a higher standard on motor vehicle manufacturers will generally not be preempted. However, if and when such a conflict does exist—for example, when the standard at issue is both a minimum and a maximum standard—the State common law tort cause of action is preempted impliedly. See 
                    <E T="03">Geier</E>
                     v. 
                    <E T="03">American Honda Motor Co.,</E>
                     529 U.S. 861 (2000).
                </P>
                <P>Pursuant to Executive Order 13132, NHTSA has considered whether this rule could or should preempt State common law causes of action. The agency's ability to announce its conclusion regarding the preemptive effect of one of its rules reduces the likelihood that preemption will be an issue in any subsequent tort litigation.</P>
                <P>
                    To this end, the agency has examined the nature (
                    <E T="03">e.g.,</E>
                     the language and structure of the regulatory text) and objectives of this rule and does not foresee any potential State requirements that might conflict with it. NHTSA does not intend that this rule preempt state tort law that would effectively impose a higher standard on motor vehicle manufacturers than that established by this rule. Establishment of a higher standard by means of State tort law would not conflict with the standards in this rule. Without any conflict, there could not be any implied preemption of a State common law tort cause of action.
                </P>
                <HD SOURCE="HD2">National Environmental Policy Act</HD>
                <P>
                    The Department has analyzed the environmental impacts of this rule pursuant to the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). Pursuant to 49 CFR 1.81, the Secretary has delegated the “functions” under NEPA to the Administrators “as they relate to the matters within the primary responsibility of each Operating Administration.” NHTSA has determined that this rule is categorically excluded pursuant to 23 CFR 771.118(c)(4). Categorical exclusions are actions identified in an agency's NEPA procedures that do not normally have a significant impact on the environment and therefore do not require either an environmental assessment (EA) or environmental impact statement (EIS).
                    <SU>44</SU>
                     This rulemaking, which responds to petitions for consideration on NHTSA's final seat belt reminder systems rule issued in January 2025, is categorically excluded pursuant to 23 CFR 771.118(c)(4): “Planning and administrative activities that do not involve or lead directly to construction, such as: Training, technical assistance and research; promulgation of rules, regulations, directives, or program guidance; approval of project concepts; engineering; and operating assistance to transit authorities to continue existing service or increase service to meet routine demand.” NHTSA does not anticipate any environmental impacts, and there are no extraordinary circumstances present in connection with this rulemaking.
                </P>
                <HD SOURCE="HD2">Executive Order 12988 (Civil Justice Reform)</HD>
                <P>With respect to the review of the promulgation of a new regulation, section 3(b) of Executive Order 12988, “Civil Justice Reform” (61 FR 4729, February 7, 1996) requires that Executive agencies make every reasonable effort to ensure that the regulation: (1) specifies clearly the preemptive effect; (2) specifies clearly the effect on existing Federal law or regulation; (3) provides a clear legal standard for affected conduct, while promoting simplification and burden reduction; (4) specifies clearly the retroactive effect, if any; (5) defines key terms adequately; and (6) addresses other important issues affecting clarity and general draftsmanship under any guidelines issued by the Attorney General. This document is consistent with that requirement.</P>
                <P>NHTSA has reviewed this rulemaking and determined that this rulemaking action conforms to the applicable standards in sections 3(a) and 3(b)(2) of E.O. 12988, Civil Justice Reform. The issue of preemption is discussed above in connection with E.O. 13132. NHTSA notes further that there is no requirement that individuals submit a petition for reconsideration or pursue other administrative proceeding before they may file suit in court.</P>
                <HD SOURCE="HD2">National Technology Transfer and Advancement Act</HD>
                <P>
                    Under the National Technology Transfer and Advancement Act of 1995 (NTTAA) (Pub. L. 104-113), “all Federal agencies and departments shall use technical standards that are developed or adopted by voluntary consensus standards bodies, using such technical standards as a means to carry out policy objectives or activities determined by the agencies and departments.” Voluntary consensus standards are technical standards (
                    <E T="03">e.g.,</E>
                     materials specifications, test methods, sampling procedures, and business practices) that are developed or adopted by voluntary consensus standards bodies, such as SAE (formerly, the Society of Automotive Engineers). The NTTAA 
                    <PRTPAGE P="17157"/>
                    directs this agency to provide Congress, through OMB, explanations when the agency decides not to use available and applicable voluntary consensus standards. NHTSA is not aware of any voluntary standards that exist regarding the seat belt warnings in this rule.
                </P>
                <HD SOURCE="HD2">Plain Language</HD>
                <P>Executive Order 12866 and E.O. 13563 require each agency to write all rules in plain language. Application of the principles of plain language includes consideration of the following questions:</P>
                <P>• Have we organized the material to suit the public's needs?</P>
                <P>• Are the requirements in the rule stated clearly?</P>
                <P>• Does the rule contain technical language or jargon that is not clear?</P>
                <P>• Would a different format (grouping and order of sections, use of headings, paragraphing) make the rule easier to understand?</P>
                <P>• Would more (but shorter) sections be better?</P>
                <P>• Could we improve clarity by adding tables, lists, or diagrams?</P>
                <P>• What else could we do to make the rule easier to understand?</P>
                <P>NHTSA has considered these questions and attempted to use plain language in writing this rule. Please inform the agency if you can suggest how NHTSA can improve its use of plain language.</P>
                <HD SOURCE="HD2">Regulation Identifier Number (RIN)</HD>
                <P>The Department of Transportation assigns a regulation identifier number (RIN) to each regulatory action listed in the Unified Agenda of Federal Regulations. The Regulatory Information Service Center publishes the Unified Agenda in April and October of each year. You may use the RIN contained in the heading at the beginning of this document to find this action in the Unified Agenda.</P>
                <HD SOURCE="HD2">Privacy Act</HD>
                <P>
                    In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its rulemaking process. DOT posts these comments, without edit, to 
                    <E T="03">www.regulations.gov,</E>
                     as described in the system of records notice, DOT/ALL-14 FDMS, accessible through 
                    <E T="03">www.dot.gov/privacy.</E>
                     To facilitate comment tracking and response, we encourage commenters to provide their name, or the name of their organization; however, submission of names is completely optional. Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <HD SOURCE="HD2">Congressional Review Act</HD>
                <P>As required by 5 U.S.C. 801, NHTSA will submit to Congress a report regarding the issuance of this interim final rule prior to the effective date set forth at the outset of this interim final rule. The report will state that it has been determined that this interim final rule is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
                <HD SOURCE="HD1">VII. Public Participation</HD>
                <HD SOURCE="HD2">How do I prepare and submit comments?</HD>
                <P>Your comments must be written and in English. To ensure that your comments are filed correctly in the Docket, please include the docket number indicated in this document in your comments.</P>
                <P>Your comments must not be more than 15 pages long. (49 CFR 553.21). We established this limit to encourage you to write your primary comments in a concise fashion. However, you may attach necessary additional documents to your comments. There is no limit on the length of the attachments.</P>
                <P>If you are submitting comments electronically as a PDF (Adobe) file, NHTSA asks that the documents be submitted using the Optical Character Recognition (OCR) process, thus allowing NHTSA to search and copy certain portions of your submissions.</P>
                <P>
                    Please note that pursuant to the Data Quality Act, for substantive data to be relied upon and used by the agency, it must meet the information quality standards set forth in the OMB and DOT Data Quality Act guidelines. Accordingly, we encourage you to consult the guidelines in preparing your comments. OMB's guidelines may be accessed at 
                    <E T="03">https://www.transportation.gov/regulations/dot-information-dissemination-quality-guidelines.</E>
                </P>
                <HD SOURCE="HD2">How can I be sure that my comments were received?</HD>
                <P>If you wish the Docket to notify you upon its receipt of your comments, enclose a self-addressed, stamped postcard in the envelope containing your comments. Upon receiving your comments, the Docket will return the postcard by mail.</P>
                <HD SOURCE="HD2">How do I submit confidential business information?</HD>
                <P>
                    You should submit a redacted “public version” of your comment (including redacted versions of any additional documents or attachments) to the docket using any of the methods identified under 
                    <E T="02">ADDRESSES</E>
                    . This “public version” of your comment should contain only the portions for which no claim of confidential treatment is made and from which those portions for which confidential treatment is claimed has been redacted. See below for further instructions on how to do this.
                </P>
                <P>You also need to submit a request for confidential treatment directly to the Office of Chief Counsel. Requests for confidential treatment are governed by 49 CFR part 512. Your request must set forth the information specified in part 512. This includes the materials for which confidentiality is being requested (as explained in more detail below); supporting information, pursuant to § 512.8; and a certificate, pursuant to § 512.4(b) and part 512, appendix A.</P>
                <P>You are required to submit to the Office of Chief Counsel one unredacted “confidential version” of the information for which you are seeking confidential treatment. Pursuant to § 512.6, the words “ENTIRE PAGE CONFIDENTIAL BUSINESS INFORMATION” or “CONFIDENTIAL BUSINESS INFORMATION CONTAINED WITHIN BRACKETS” (as applicable) must appear at the top of each page containing information claimed to be confidential. In the latter situation, where not all information on the page is claimed to be confidential, identify each item of information for which confidentiality is requested within brackets: “[ ].”</P>
                <P>
                    You are also required to submit to the Office of Chief Counsel one redacted “public version” of the information for which you are seeking confidential treatment. Pursuant to § 512.5(a)(2), the redacted “public version” should include redactions of any information for which you are seeking confidential treatment (
                    <E T="03">i.e.,</E>
                     the only information that should be unredacted is information for which you are not seeking confidential treatment).
                </P>
                <P>
                    NHTSA is currently treating electronic submission as an acceptable method for submitting confidential business information to the agency under part 512. Please do not send a hardcopy of a request for confidential treatment to NHTSA's headquarters. The request should be sent to Dan Rabinovitz in the Office of the Chief Counsel at 
                    <E T="03">Daniel.Rabinovitz@dot.gov.</E>
                     You may either submit your request via email or request a secure file transfer link. Manufacturers or any companies that already have a Confidential Business Information (CBI) Portal account or an Enterprise Account with 
                    <PRTPAGE P="17158"/>
                    NHTSA should use the CBI Portal for their submission. If you submit a CBI request, please also email a courtesy copy of the request to John Piazza at 
                    <E T="03">John.Piazza@dot.gov.</E>
                </P>
                <HD SOURCE="HD2">Will the agency consider late comments?</HD>
                <P>
                    We will consider all comments received before the close of business on the comment closing date indicated above under 
                    <E T="02">DATES</E>
                    . To the extent possible, we will also consider comments that the docket receives after that date. If the docket receives a comment too late for us to consider in developing a final rule (assuming that one is issued), we will consider that comment as an informal suggestion for future rulemaking action.
                </P>
                <HD SOURCE="HD2">How can I read the comments submitted by other people?</HD>
                <P>
                    You may read the comments received by the docket at the address given above under 
                    <E T="02">ADDRESSES</E>
                    . The hours of the docket are indicated above in the same location. You may also see the comments on the internet. To read the comments on the internet, go to 
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the online instructions for accessing the dockets.
                </P>
                <P>
                    Please note that even after the comment closing date, we will continue to file relevant information in the docket as it becomes available. Further, some people may submit late comments. Accordingly, we recommend that you periodically check the Docket for new material. You can arrange with the docket to be notified when others file comments in the docket. See 
                    <E T="03">www.regulations.gov</E>
                     for more information.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 49 CFR Part 571</HD>
                    <P>Imports, Motor vehicle safety, Motor vehicles.</P>
                </LSTSUB>
                <P>In consideration of the foregoing, NHTSA amends 49 CFR part 571 as set forth below.</P>
                <PART>
                    <HD SOURCE="HED">PART 571—FEDERAL MOTOR VEHICLE SAFETY STANDARDS</HD>
                </PART>
                <REGTEXT TITLE="49" PART="571">
                    <AMDPAR>1. The authority citation for part 571 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 322, 30111, 30115, 30117, and 30166; delegation of authority at 49 CFR 1.95.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="49" PART="571">
                    <AMDPAR>2. Amend § 571.208 by:</AMDPAR>
                    <AMDPAR>a. Revising paragraphs S4.1.5.7 and S4.1.5.7.1;</AMDPAR>
                    <AMDPAR>b. Adding paragraph S4.1.5.7.2;</AMDPAR>
                    <AMDPAR>c. Removing paragraphs S4.1.5.8 and S4.1.5.8.1;</AMDPAR>
                    <AMDPAR>d. Revising paragraphs S4.2.8 and S4.2.8.1;</AMDPAR>
                    <AMDPAR>e. Adding paragraph S4.2.8.2;</AMDPAR>
                    <AMDPAR>f. Removing paragraphs S4.2.9 and S4.2.9.1;</AMDPAR>
                    <AMDPAR>g. Revising paragraphs S4.4.3.4 and S4.4.3.4.1;</AMDPAR>
                    <AMDPAR>h. Adding paragraph S4.4.3.4.2;</AMDPAR>
                    <AMDPAR>i. Removing paragraphs S4.4.3.5 and S4.4.3.5.1; and</AMDPAR>
                    <AMDPAR>j. Revising paragraphs S7.5 introductory text, S7.5(b)(1)(v), S7.5(b)(2)(ii), S7.5(c)(2), and S7.5(c)(3)(iv).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 571.208 </SECTNO>
                        <SUBJECT>Standard No. 208; Occupant crash protection.</SUBJECT>
                        <STARS/>
                        <P>
                            S4.1.5.7. 
                            <E T="03">Seat belt warnings for passenger cars manufactured on or after September 1, 2028.</E>
                        </P>
                        <P>S4.1.5.7.1 Any front outboard designated seating position and any front inboard designated seating position for which a seat belt warning is required in S4.1.5.6 shall comply with S7.5 of this standard.</P>
                        <P>S4.1.5.7.2. All rear designated seating positions, except in law enforcement vehicles, shall comply with S7.5 of this standard.</P>
                        <STARS/>
                        <P>
                            S4.2.8 
                            <E T="03">Seat belt warnings for trucks and multipurpose passenger vehicles manufactured on or after September 1, 2028 with a GVWR of 4,536 kg (10,000 lb) or less.</E>
                        </P>
                        <P>S4.2.8.1. Any front outboard designated seating position certified to a compliance option requiring a seat belt and any front inboard designated seating position for which a seat belt warning is required by S4.2.6.4 shall comply with S7.5 of this standard.</P>
                        <P>S4.2.8.2. All rear designated seating positions certified to a compliance option requiring a seat belt, except for ambulances, as defined by FMVSS No. 201 (§ 571.201), and law enforcement vehicles, shall comply with S7.5 of this standard.</P>
                        <STARS/>
                        <P>
                            S4.4.3.4 
                            <E T="03">Seat belt warnings for buses manufactured on or after September 1, 2028 with a GVWR of 4,536 kg (10,000 lb) or less.</E>
                        </P>
                        <P>S4.4.3.4.1 All front outboard designated seating positions and any front inboard designated seating position for which a seat belt warning is required by S4.2.6.4 shall comply with S7.5 of this standard.</P>
                        <P>S4.4.3.4.2 All rear designated seating positions certified to a compliance option requiring a seat belt, except for school buses and law enforcement vehicles, shall comply with S7.5 of this standard.</P>
                        <STARS/>
                        <P>
                            S7.5 
                            <E T="03">Seat belt warning systems for vehicles manufactured on or after September 1, 2028 provided in accordance with the requirements S4.1.5.7, S4.2.8, and S4.4.3.4 of this standard.</E>
                        </P>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>(v) For a visual warning associated with multiple front outboard seats, the visual warning must use supplementary symbols, words, or abbreviations to indicate the seating positions for which the warnings are intended.</P>
                        <STARS/>
                        <P>(2) * * *</P>
                        <P>(ii) The audible warning must continue for at least 30 seconds, until the seat belt that triggered the warning is in use, until the seat is no longer occupied, or until the second-phase warning activates. The audible warning may be paused during the activation of another audible safety warning that is designed to alert the driver to take immediate action, but the seat belt audible warning must be resumed for the remainder of the required duration after the other audible warning deactivates.</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>
                            (2) 
                            <E T="03">Change-of-status warning.</E>
                             An audio-visual warning indicating how many or which rear seat belts have undergone a change of status from in use to not in use must activate when the status of any rear seat belt changes from in use to not in use and the vehicle is in either forward or reverse drive mode, unless any rear door is open. The warning must continue for at least 30 seconds, until the seat belt that triggered the warning is in use, until the vehicle is stopped and no longer in forward or reverse drive mode, or until any rear door is opened. The warning may deactivate if the system is able to determine that the number of seat belts in use is restored and all the doors remained closed, or if the system is able to determine that the seating position that triggered the warning is no longer occupied.
                        </P>
                        <P>(3) * * *</P>
                        <P>
                            (iv) The change-of-status warning may use the same visual warning as the start of trip warning, provided that the color of an illuminated symbol or number
                            <E T="03">,</E>
                             used to indicate to the driver how many or which rear seat belts have undergone a change of status from in use to not in use is red.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <PRTPAGE P="17159"/>
                    <P>Issued under authority delegated in 49 CFR 1.95.</P>
                    <NAME>Jonathan Morrison,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06614 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 600</CFR>
                <DEPDOC>[Docket No. 260401-0091]</DEPDOC>
                <RIN>RIN 0648-BO47</RIN>
                <SUBJECT>Magnuson-Stevens Fishery Conservation and Management Act Provisions; Modifications To Conform U.S. Fishery Regulations With the Presidential Proclamation Unleashing Commercial Fishing in the Atlantic</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action rescinds regulations issued under the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) that restrict commercial fishing within the Northeast Canyons and Seamounts Marine National Monument (Monument). This action is necessary to conform U.S. fishing regulations with the February 6, 2026, Presidential Proclamation 
                        <E T="03">Unleashing Commercial Fishing in the Atlantic.</E>
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective April 3, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Allison Murphy, Fishery Policy Analyst, 978-281-9122.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On September 15, 2016, the Northeast Canyons and Seamounts Marine National Monument (Monument) was designated in the waters of the North Atlantic (Presidential Proclamation 9496; 81 FR 65161, September 21, 2016), including both a Canyons Unit and a Seamounts Unit. This Proclamation prohibited commercial fishing within the Monument with a 7-year exemption for the American lobster and Atlantic deep-sea red crab fisheries. In June 2020, Monument prohibitions were revised via Proclamation 10049 (85 FR 35793, June 11, 2020), which removed commercial fishing from the list of prohibited activities set forth in the 2016 Proclamation. In October 2021, Proclamation 10287 (86 FR 57349, October 15, 2021) returned commercial fishing to the list of prohibited activities, providing “for the prohibition of all commercial fishing in the Monument, except for red crab and American lobster commercial fishing, which may be permitted until September 15, 2023.” NMFS published a final rule (89 FR 12282) on February 16, 2024, conforming the U.S. fishing regulations at 50 CFR part 600 to Proclamations 9496 and 10287, and adding § 600.725(x) to reflect the commercial fishing prohibition in the two Proclamations. On February 6, 2026, the Presidential Proclamation 
                    <E T="03">Unleashing Commercial Fishing in the Atlantic</E>
                     (91 FR 6489, February 11, 2026) again removed the prohibition on commercial fishing in the Monument.
                </P>
                <HD SOURCE="HD1">Approved Measures</HD>
                <P>Consistent with the February 2026 Presidential Proclamation, which removed the prohibition on commercial fishing within the boundaries of the Monument, and the requirements of the Magnuson-Stevens Act, this action rescinds the regulations at 50 CFR 600.725(x).</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>NMFS is issuing this rule pursuant to section 305(d) of the Magnuson-Stevens Act to comply with section 303(a)(1)(C) by rescinding regulations at § 600.725(x) to ensure that all fishery management plans and measures implemented by the Secretary of Commerce are consistent with, and conform to, the February 2026 Proclamation and the Antiquities Act. The NMFS Assistant Administrator has determined that this rule is consistent with other applicable law.</P>
                <P>Pursuant to 5 U.S.C. 553(b)(B), there is good cause to waive prior notice and opportunity for public comment on this action. Prior notice and opportunity for public comment on this final rule would be impracticable, unnecessary, and contrary to the public interest. The removal of the prohibition on commercial fishing went into effect immediately upon issuance of the Proclamation. Subject to federal regulation, including regulations at 50 CFR 648.373, commercial fishing may now take place within the Monument. This rule removes the regulations at § 600.725(x), which reflected the prior Proclamations' prohibition on commercial fishing in the Monument, to conform to the current Proclamation. This rule provides clarity and certainty to the fishing industry that the restrictions on commercial fishing no longer apply. Therefore, it is impracticable and contrary to the public interest to provide for prior notice and opportunity for public comment for removal of a regulation whose legal justification no longer exists.</P>
                <P>
                    This final rule merely conforms U.S. fishing regulations to the requirements of the Antiquities Act and the Presidential Proclamation 
                    <E T="03">Unleashing Commercial Fishing in the Atlantic.</E>
                     The Magnuson-Stevens Act, which governs the activities associated with commercial fishing in the U.S. Exclusive Economic Zone, requires fishery management plans and measures implemented by the Secretary of Commerce to be consistent with all applicable law, including Presidential Proclamations issued under the authority of the Antiquities Act. The Antiquities Act authorizes the President to establish national marine monuments and to make the final decision on what is protected and what uses will be restricted. The Presidential Proclamation 
                    <E T="03">Unleashing Commercial Fishing in the Atlantic</E>
                     is, therefore, within the President's authority under the Antiquities Act. The President removed the prohibition on commercial fishing within the Monument in the February 2026 Proclamation. This action, which removes regulations that do not reflect current law, is therefore not discretionary, making the opportunity for prior public comment unnecessary because NMFS has no ability for public comment to inform decision-making.
                </P>
                <P>
                    There is good cause to implement this action immediately upon publication without a 30-day delay pursuant to 5 U.S.C. 553(d)(3). Waiting an additional 30 days for this rule to become effective would be impracticable, unnecessary, and contrary to the public interest for all of the same reasons that it would be impracticable, unnecessary, and contrary to the public interest to provide prior notice and opportunity for public comment above and are not repeated. Further, commercial fishing was allowed in the Monument on February 6, 2026, upon release of the Presidential Proclamation 
                    <E T="03">Unleashing Commercial Fishing in the Atlantic.</E>
                     Delaying effectiveness would only lengthen the time period in which U.S. fishing regulations do not conform with other applicable law and would create confusion within the fishing industry as to whether commercial fishing is allowed within the Monument. Moreover, for the same reason, the regulated industry does not need time to prepare for the effectiveness of the removal of the regulation. 
                    <E T="03">See</E>
                     5 U.S.C. 553(d)(1).
                </P>
                <P>
                    The National Environmental Policy Act does not apply to this action. 
                    <PRTPAGE P="17160"/>
                    Because this action merely conforms the Magnuson-Stevens Act regulations to applicable law under the Presidential Proclamation 
                    <E T="03">Unleashing Commercial Fishing in the Atlantic,</E>
                     NMFS has no discretion. As a result, there is no decision-making process, and no alternatives to consider. There is no “proposal” for action, as discussed in the June 30, 2025, NOAA Administrative Order 216-6A Companion Manual.
                </P>
                <P>This rule has been determined to be significant for purposes of Executive Order (E.O.) 12866.</P>
                <P>This final rule is considered an Executive Order 14192 deregulatory action.</P>
                <P>NMFS has determined that this action would not have a substantial direct effect on one or more Indian Tribes, on the relationship between the Federal Government and Indian Tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes; therefore, consultation with Tribal officials under E.O. 13175 is not required, and the requirements of section (5)(b) and (c) of E.O. 13175 also do not apply. A Tribal summary impact statement under section (5)(b)(2)(B) and (c)(2)(B) of E.O. 13175 is not required and has not been prepared.</P>
                <P>
                    Because prior notice and opportunity for public comment are not required for this rule by 5 U.S.C. 553, or any other law, the analytical requirements of the Regulatory Flexibility Act, 5 U.S.C. 601 
                    <E T="03">et seq.,</E>
                     are inapplicable.
                </P>
                <P>This rule contains no information collection requirements under the Paperwork Reduction Act of 1995.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 50 CFR Part 600</HD>
                    <P>Fisheries, Fishing.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: April 1, 2026. </DATED>
                    <NAME>Samuel D. Rauch III,</NAME>
                    <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                </SIG>
                <P>For the reasons set out in the preamble, NMFS amends 50 CFR part 600 to read as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 600—MAGNUSON-STEVENS ACT PROVISIONS</HD>
                </PART>
                <REGTEXT TITLE="50" PART="600">
                    <AMDPAR>1. The authority citation for part 600 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             5 U.S.C. 561 and 16 U.S.C. 1801 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 600.725 </SECTNO>
                    <SUBJECT> [Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="50" PART="600">
                    <AMDPAR>2. Amend § 600.725 by removing and reserving paragraph (x).</AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06663 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="17161"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-3474; Project Identifier MCAI-2025-01807-A]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Pilatus Aircraft Ltd. Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to supersede Airworthiness Directive (AD) 2021-11-08, which applies to all Pilatus Aircraft Ltd. (Pilatus) Model PC-6, PC-6-H1, PC-6-H2, PC-6/350, PC-6/350-H1, PC-6/350-H2, PC-6/A, PC-6/A-H1, PC-6/A-H2, PC-6/B-H2, PC-6/B1-H2, PC-6/B2-H2, PC-6/B2-H4, PC-6/C-H2, and PC-6/C1-H2 airplanes. AD 2021-11-08 requires revising the airworthiness limitation section (ALS) of the existing aircraft maintenance manual (AMM) or instructions for continued airworthiness (ICA) to incorporate new airworthiness limitations and adding an additional eddy current inspection of the fuselage wing fittings and wing-to-fuselage fittings if the last inspection was performed using an earlier version of the material. Since the FAA issued AD 2021-11-08, the FAA has determined that new or more restrictive airworthiness limitations are necessary. This proposed AD would require revising the ALS of the existing AMM or ICA for these airplanes. The FAA is proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this NPRM by May 21, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-3474; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this NPRM, the mandatory continuing airworthiness information (MCAI) any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For European Union Aviation Agency (EASA) material identified in this NPRM, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu</E>
                        ; website: 
                        <E T="03">easa.europa.eu</E>
                        . You may find this material on the EASA website at 
                        <E T="03">ad.easa.europa.eu</E>
                        .
                    </P>
                    <P>• You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Doug Rudolph, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (816) 329-4059; email: 
                        <E T="03">doug.rudolph@faa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    The FAA invites you to send any written relevant data, views, or arguments about this proposal. Send your comments using a method listed under 
                    <E T="02">ADDRESSES</E>
                    . Include “Docket No. FAA-2026-3474; Project Identifier MCAI-2025-01807-A” at the beginning of your comments. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. The FAA will consider all comments received by the closing date and may amend the proposal because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <E T="03">regulations.gov</E>
                    , including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this NPRM.
                </P>
                <HD SOURCE="HD1">Confidential Business Information</HD>
                <P>CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this NPRM contain commercial or financial information that is customarily treated as private, that you actually treat as private, and that is relevant or responsive to this NPRM, it is important that you clearly designate the submitted comments as CBI. Please mark each page of your submission containing CBI as “PROPIN.” The FAA will treat such marked submissions as confidential under the FOIA, and they will not be placed in the public docket of this NPRM. Submissions containing CBI should be sent to Doug Rudolph, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590. Any commentary that the FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The FAA issued AD 2021-11-08, Amendment 39-21570 (86 FR 30155, June 7, 2021), (AD 2021-11-08), for all Pilatus Model PC-6, PC-6-H1, PC-6-H2, PC-6/350, PC-6/350-H1, PC-6/350-H2, PC-6/A, PC-6/A-H1, PC-6/A-H2, PC-6/B-H2, PC-6/B1-H2, PC-6/B2-H2, PC-6/B2-H4, PC-6/C-H2, and PC-6/C1-H2 airplanes. AD 2021-11-08 was prompted by an MCAI originated by EASA, which is the Technical Agent for the Member States of the European Union. EASA issued EASA AD 2007-0241R4, dated August 31, 2010, (EASA AD 2007-0241R4) to correct an unsafe condition identified as corrosion, wear, and cracks in the upper wing strut fittings on some PC-6 airplanes. EASA also issued EASA AD 2020-0278, dated 
                    <PRTPAGE P="17162"/>
                    December 14, 2020, (EASA AD 2020-0278) to correct an unsafe condition identified as a failure to revise the ALS of the existing AMM by introducing new or more restrictive tasks and limitations, including corrected material which includes installing certain bushes using grease instead of a bonding agent and an additional one-time eddy current inspection of the fuselage wing fittings and wing-to-fuselage fittings if the last inspection was performed using an earlier version of the material. EASA AD 2020-0278 states that these instructions have been identified as mandatory for continued airworthiness, and failure to accomplish them could result in an unsafe condition.
                </P>
                <P>AD 2021-11-08 requires revising the ALS of the existing AMM or ICA to incorporate new airworthiness limitations and adding an additional eddy current inspection of the fuselage wing fittings and wing-to-fuselage fittings if the last inspection was performed using an earlier version of the material. The FAA issued AD 2021-11-08 to address reduced airplane controllability due to possible loss of structural integrity of certain parts.</P>
                <HD SOURCE="HD1">Actions Since AD 2021-11-08 Was Issued</HD>
                <P>Since the FAA issued AD 2021-11-08, EASA superseded EASA AD 2007-0241R4 and EASA AD 2020-0278 and issued EASA AD 2025-0281, dated December 11, 2025 (EASA AD 2025-0281) (also referred to as the MCAI), for all Pilatus Model PC-6 airplanes. The MCAI states that new or more restrictive tasks and limitations have been developed. These include adding life limits for the control column pitch trim relay. The MCAI also states that failure to accomplish these instructions could result in an unsafe condition. The FAA is issuing this AD to address failure of certain parts, which could result in loss of control of the airplane.</P>
                <P>Additionally, the actions required to address the unsafe condition in AD 2021-11-08 are included in “the applicable ALS,” as defined in EASA AD 2025-0281.</P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-3474.
                </P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>The FAA reviewed EASA AD 2025-0281, which specifies procedures for revising the aircraft maintenance program (AMP) by incorporating airworthiness limitations, tasks, and associated thresholds and intervals, including life limits and maintenance tasks. EASA AD 2025-0281 also specifies performing corrective actions if any discrepancy is found during accomplishment of any task in paragraph (1) of EASA AD 2025-0281 and revising the AMP by incorporating the limitations, tasks, and associated thresholds and intervals described in “the applicable ALS” as defined in EASA AD 2025-0281.</P>
                <P>
                    This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>These products have been approved by the civil aviation authority (CAA) of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop on other products of the same type design.</P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require revising the ALS of the existing AMM or ICA for the airplane and the existing approved maintenance or inspection program, as applicable, by incorporating new or more restrictive actions and associated thresholds and intervals, including any life limits, specified in EASA AD 2025-0281, described previously, as incorporated by reference, except for any differences identified as exceptions in the regulatory text of this proposed AD. See “Differences Between this NPRM and the MCAI” for a discussion of the general differences included in this proposed AD.</P>
                <P>The owner/operator (pilot) holding at least a private pilot certificate may revise the ALS of the existing AMM or ICA for the airplane, and performance of this incorporation must be entered into the aircraft records showing compliance with this AD in accordance with 14 CFR 43.9(a) and 14 CFR 91.417(a)(2)(v). The record must be maintained as required by 14 CFR 91.417, 121.380, or 135.439.</P>
                <HD SOURCE="HD1">Differences Between This Proposed AD and the MCAI</HD>
                <P>Where EASA AD 2025-0281 specifies revising the approved AMP within 12 months after the effective date of EASA AD 2025-0281, this proposed AD would require revising the ALS of the existing approved maintenance or inspection program, as applicable, within 30 days after the effective date of this proposed AD.</P>
                <HD SOURCE="HD1">Explanation of Required Compliance Information</HD>
                <P>
                    In the FAA's ongoing efforts to improve the efficiency of the AD process, the FAA developed a process to use some CAA ADs as the primary source of information for compliance with requirements for corresponding FAA ADs. The FAA has been coordinating this process with manufacturers and CAAs. As a result, the FAA proposes to incorporate EASA AD 2025-0281 by reference in the FAA final rule. This proposed AD would, therefore, require compliance with EASA AD 2025-0281 in its entirety through that incorporation, except for any differences identified as exceptions in the regulatory text of this proposed AD. Using common terms that are the same as the heading of a particular section in EASA AD 2025-0281 does not mean that operators need comply only with that section. For example, where the AD requirement refers to “all required actions and compliance times,” compliance with this AD requirement is not limited to the section titled “Required Action(s) and Compliance Time(s)” in EASA AD 2025-0281. Material required by EASA AD 2025-0281 for compliance will be available at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-3474 after the FAA final rule is published.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 30 airplanes of U.S. registry.</P>
                <P>
                    The FAA estimates the following costs to comply with this proposed AD:
                    <PRTPAGE P="17163"/>
                </P>
                <GPOTABLE COLS="05" OPTS="L2,nj,i1" CDEF="s50,r50,10,10,12">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Revise the ALS</ENT>
                        <ENT>1 work-hour × $85 per hour = $85</ENT>
                        <ENT>$0</ENT>
                        <ENT>$85</ENT>
                        <ENT>$2,550</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: General requirements. Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>The FAA determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that the proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>(3) Would not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(g), 40113, 44701.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 39.13 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The FAA amends § 39.13 by:</AMDPAR>
                <AMDPAR>a. Removing Airworthiness Directive 2021-11-08, Amendment 39-21570 (86 FR 30155, June 7, 2021); and</AMDPAR>
                <AMDPAR>b. Adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">Pilatus Aircraft Ltd.:</E>
                         Docket No. FAA-2026-3474; Project Identifier MCAI-2025-01807-A.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by May 21, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>This AD replaces AD 2021-11-08, Amendment 39-21570 (86 FR 30155, June 7, 2021); (AD 2021-11-08).</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to all Pilatus Aircraft Ltd., Model PC-6, PC-6-H1, PC-6-H2, PC-6/350, PC-6/350-H1, PC-6/350-H2, PC-6/A, PC-6/A-H1, PC-6/A-H2, PC-6/B-H2, PC-6/B1-H2, PC-6/B2-H2, PC-6/B2-H4, PC-6/C-H2, and PC-6/C1-H2 airplanes, certificated in any category.</P>
                    <P>
                        <E T="04">Note 1 to paragraph (c):</E>
                         These airplanes may also be identified as Fairchild Republic Company airplanes, Fairchild Industries airplanes, Fairchild Heli Porter airplanes, or Fairchild-Hiller Corporation airplanes.
                    </P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 2740, Stabilizer Control System.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by a revision to the airworthiness limitations section (ALS) of the existing aircraft maintenance manual (AMM) introducing new and more restrictive instructions and maintenance tasks. These include adding life limits for the control column pitch trim relay. The FAA is issuing this AD to ensure revision of the ALS of the existing AMM or instructions for continued airworthiness (ICA) for the airplane. The unsafe condition, if not addressed, could result in failure of certain parts, which could result in loss of control of the airplane.</P>
                    <HD SOURCE="HD1">(f) Compliance</HD>
                    <P>Comply with this AD within the compliance times specified, unless already done.</P>
                    <HD SOURCE="HD1">(g) Required Actions</HD>
                    <P>(1) Except as specified in paragraphs (h) and (i) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, European Union Aviation Safety Agency (EASA) AD 2025-0281, dated December 11, 2025 (EASA AD 2025-0281).</P>
                    <P>(2) The actions required by this AD may be performed by the owner/operator (pilot) holding at least a private pilot certificate and must be entered into the aircraft records showing compliance with this AD in accordance with 14 CFR 43.9(a) and 91.417(a)(2)(v). The record must be maintained as required by 14 CFR 91.417, 121.380, or 135.439.</P>
                    <HD SOURCE="HD1">(h) Exceptions to EASA AD 2025-0281</HD>
                    <P>(1) Where EASA AD 2025-0281 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) This AD does not adopt paragraphs (1), (2), (4), and (5) of EASA AD 2025-0281.</P>
                    <P>(3) Where paragraph (3) of EASA AD 2025-0281 specifies “Within 12 months after the effective date of this AD, revise the approved AMP,” this AD requires replacing that text with “Within 30 days after the effective date of this AD, revise the ALS of the existing AMM or ICA and the existing approved maintenance or inspection program, as applicable.”</P>
                    <P>(4) The initial compliance time for doing the tasks specified in paragraph (3) of EASA AD 2025-0281 is on or before the applicable limitations and associated thresholds as incorporated by the requirements of paragraph (3) of EASA AD 2025-0281 or within 30 days after the effective date of this AD, whichever occurs later.</P>
                    <P>(5) This AD does not adopt the “Remarks” section of EASA AD 2025-0281.</P>
                    <HD SOURCE="HD1">(i) Provisions for Alternative Actions and Intervals</HD>
                    <P>After the action required by paragraph (g)(1) of this AD has been done, no alternative actions and associated thresholds and intervals, including any life limits, are allowed unless they are approved as specified in the provisions of the “Ref. Publications” section of EASA AD 2025-0281.</P>
                    <HD SOURCE="HD1">(j) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>
                        (1) The Manager, International Validation Branch, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the International Validation Branch, send it to the attention of the person 
                        <PRTPAGE P="17164"/>
                        identified in paragraph (k) of this AD and email to: 
                        <E T="03">AMOC@faa.gov</E>
                        .
                    </P>
                    <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office/certificate holding district office.</P>
                    <HD SOURCE="HD1">(k) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Doug Rudolph, Aviation Safety Engineer, FAA, 1600 Stewart Avenue, Suite 410, Westbury, NY 11590; phone: (816) 329-4059; email: 
                        <E T="03">doug.rudolph@faa.gov</E>
                        .
                    </P>
                    <HD SOURCE="HD1">(l) Material Incorporated by Reference</HD>
                    <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                    <P>(2) You must use this material as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                    <P>(i) European Union Aviation Safety Agency (EASA) AD 2025-0281, dated December 11, 2025.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For EASA material identified in this AD, contact EASA, Konrad-Adenauer-Ufer 3, 50668 Cologne, Germany; phone: +49 221 8999 000; email: 
                        <E T="03">ADs@easa.europa.eu</E>
                        ; website: 
                        <E T="03">easa.europa.eu</E>
                        . You may find this EASA AD on the EASA website at 
                        <E T="03">ad.easa.europa.eu</E>
                        .
                    </P>
                    <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov</E>
                        .
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued on March 31, 2026.</DATED>
                    <NAME>Christopher R. Parker,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06605 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2026-3637; Airspace Docket No. 26-AGL-3]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Establishment of Class E Airspace; Dover, OH</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action proposes to establish Class E airspace at Dover, OH. The FAA is proposing this action to support new instrument procedures and instrument flight rule (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before May 21, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by FAA Docket No. FAA-2026-3637 and Airspace Docket No. 26-AGL-3 using any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov</E>
                         and follow the online instructions for sending your comments electronically.
                    </P>
                    <P>
                        * 
                        <E T="03">Mail:</E>
                         Send comments to Docket Operations, M-30; U.S. Department of Transportation, 1200 New Jersey Avenue SE, Room W12-140, West Building Ground Floor, Washington, DC 20590-0001.
                    </P>
                    <P>
                        * 
                        <E T="03">Hand Delivery or Courier:</E>
                         Take comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        * 
                        <E T="03">Fax:</E>
                         Fax comments to Docket Operations at (202) 493-2251.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         Background documents or comments received may be read at 
                        <E T="03">www.regulations.gov</E>
                         at any time. Follow the online instructions for accessing the docket or go to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        FAA Order JO 7400.11K, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/</E>
                        . You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 600 Independence Avenue SW, Washington, DC 20597; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Raul Garza Jr., Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5874.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it would establish Class E airspace extending upward from 700 feet above the surface at Cleveland Clinic, Union Hospital Heliport, Dover, OH, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, commenters should submit only one time if comments are filed electronically, or commenters should send only one copy of written comments if comments are filed in writing.</P>
                <P>The FAA will file in the docket all comments it receives, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, the FAA will consider all comments it received on or before the closing date for comments. The FAA will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. The FAA may change this proposal in light of the comments it receives.</P>
                <P>
                    <E T="03">Privacy:</E>
                     In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its rulemaking process. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov</E>
                     as described in the system of records notice (DOT/ALL-14FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy</E>
                    .
                </P>
                <HD SOURCE="HD1">Availability of Rulemaking Documents</HD>
                <P>
                    An electronic copy of this document may be downloaded through the internet at 
                    <E T="03">www.regulations.gov</E>
                    . Recently published rulemaking documents can also be accessed through the FAA's web page at 
                    <E T="03">www.faa.gov/air_traffic/publications/airspace_amendments/</E>
                    .
                </P>
                <P>
                    You may review the public docket containing the proposal, any comments received, and any final disposition in 
                    <PRTPAGE P="17165"/>
                    person in the Dockets Office (see the 
                    <E T="02">ADDRESSES</E>
                     section for the address, phone number, and hours of operation). An informal docket may also be examined during normal business hours at the Federal Aviation Administration, Air Traffic Organization, Central Service Center, Operations Support Group, 10101 Hillwood Parkway, Fort Worth, TX 76177.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class E airspace is published in paragraph 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document proposes to amend the current version of that order, FAA Order JO 7400.11K, dated August 4, 2025, and effective September 15, 2025. These updates would be published subsequently in the next update to FAA Order JO 7400.11. FAA Order JO 7400.11K, which lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points, is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                </P>
                <HD SOURCE="HD1">The Proposal</HD>
                <P>The FAA is proposing an amendment to 14 CFR part 71 that would establish Class E airspace extending upward from 700 feet above the surface to within an 8.1-mile radius of Cleveland Clinic, Union Hospital Heliport, Dover, OH.</P>
                <P>This action is the result of instrument procedures being developed for this airport to support IFR operations.</P>
                <HD SOURCE="HD1">Regulatory Notices and Analyses</HD>
                <P>The FAA has determined that this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Order 2100.6B, “Policies and Procedures for Rulemakings” (March 10, 2025); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this proposed rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <HD SOURCE="HD1">Environmental Review</HD>
                <P>This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1G, “FAA National Environmental Policy Act Implementing Procedures” prior to any FAA final regulatory action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(f), 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 71.1 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11K, Airspace Designations and Reporting Points, dated August 4, 2025, and effective September 15, 2025, is amended as follows:</AMDPAR>
                <EXTRACT>
                    <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth</HD>
                    <STARS/>
                    <HD SOURCE="HD1">AGL OH E5 Dover, OH [Establish]</HD>
                    <FP SOURCE="FP-2">Cleveland Clinic, Union Hospital Heliport, OH</FP>
                    <FP SOURCE="FP1-2">(Lat. 40°30′57″ N, long. 81°27′21″ W)</FP>
                    <P>That airspace extending upward from 700 feet above the surface within an 8.1-mile radius of Cleveland Clinic, Union Hospital Heliport.</P>
                    <STARS/>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on April 1 2026.</DATED>
                    <NAME>Jerry J. Creecy,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06574 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Occupational Safety and Health Administration</SUBAGY>
                <CFR>29 CFR Part 1910</CFR>
                <DEPDOC>[Docket No. OSHA-2025-0072]</DEPDOC>
                <RIN>RIN 1218-AD73</RIN>
                <SUBJECT>Walking-Working Surfaces</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Occupational Safety and Health Administration (OSHA), Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This proposed rule removes a deadline in OSHA's Walking-Working Surfaces standard by which all fixed ladders that extend more than 24 feet above a lower level must be equipped with personal fall arrest systems or ladder safety systems. Additionally, OSHA is seeking comment on repealing or revising the requirement that employers use personal fall arrest systems on all fixed ladders over 24 feet tall and instead permitting employers to continue to use ladder cages or wells.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and other information, including requests for a hearing, must be received on or before June 5, 2026.</P>
                    <P>
                        <E T="03">Informal public hearing:</E>
                         OSHA will schedule an informal public hearing on the rule if requested during the comment period. If a hearing is requested, the location and date of the hearing, procedures for interested parties to notify the agency of their intention to participate, and procedures for participants to submit their testimony and documentary evidence will be announced in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Written comments:</E>
                         You may submit comments and attachments, identified by Docket No. OSHA-2025-0072, electronically at 
                        <E T="03">https://www.regulations.gov,</E>
                         which is the Federal e-Rulemaking Portal. Follow the instructions online for making electronic submissions.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency's name and the docket number for this rulemaking (Docket No. OSHA-2025-0072). When uploading multiple attachments to 
                        <E T="03">https://www.regulations.gov,</E>
                         please number all of your attachments because 
                        <E T="03">https://www.regulations.gov</E>
                         will not automatically number the attachments. This will be very useful in identifying all attachments. For example,
                    </P>
                    <P>Attachment 1—title of your document,</P>
                    <P>Attachment 2—title of your document,</P>
                    <P>Attachment 3—title of your document.</P>
                    <P>
                        For assistance with commenting and uploading documents, please see the Frequently Asked Questions on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        All comments, including any personal information you provide, are placed in the public docket without change and may be made available online at 
                        <E T="03">https://www.regulations.gov.</E>
                         Therefore, OSHA cautions commenters about submitting 
                        <PRTPAGE P="17166"/>
                        information they do not want made available to the public or submitting materials that contain personal information (either about themselves or others), such as Social Security Numbers and birthdates.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         The docket for this rulemaking (Docket No. OSHA-2025-0072) is available at 
                        <E T="03">https://www.regulations.gov,</E>
                         the Federal eRulemaking Portal. Most exhibits are available at 
                        <E T="03">https://www.regulations.gov;</E>
                         some exhibits (
                        <E T="03">e.g.,</E>
                         copyrighted material) are not available to download from that web page. However, all materials in the dockets are available for inspection at the OSHA Docket Office.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">For press inquiries:</E>
                         Contact Frank Meilinger, Director, OSHA Office of Communications, Occupational Safety and Health Administration; telephone: (202) 693-1999; email: 
                        <E T="03">meilinger.francis2@dol.gov.</E>
                    </P>
                    <P>
                        <E T="03">General information and technical inquiries:</E>
                         Contact Andrew Levinson, Director, OSHA Directorate of Standards and Guidance, Occupational Safety and Health Administration; telephone: (202) 693-1950; email: 
                        <E T="03">osha.dsg@dol.gov.</E>
                    </P>
                    <P>
                        <E T="03">Copies of this</E>
                          
                        <E T="04">Federal Register</E>
                          
                        <E T="03">notice:</E>
                         Electronic copies are available at 
                        <E T="03">https://www.regulations.gov.</E>
                         This 
                        <E T="04">Federal Register</E>
                         notice, as well as news releases and other relevant information, also are available at OSHA's web page at 
                        <E T="03">https://www.osha.gov.</E>
                         A “100-word summary” is also available on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Executive Summary</FP>
                    <FP SOURCE="FP-2">II. Legal Authority and Preliminary Findings</FP>
                    <FP SOURCE="FP-2">III. Background</FP>
                    <FP SOURCE="FP-2">IV. Summary and Explanation of the Proposed Requirements</FP>
                    <FP SOURCE="FP-2">V. Preliminary Economic Analysis</FP>
                    <FP SOURCE="FP-2">VI. Additional Requirements</FP>
                    <FP SOURCE="FP-2">VII. Authority and Signature</FP>
                    <FP SOURCE="FP-2">VIII. Regulatory Text</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <P>This proposed rule is intended to provide greater compliance flexibility for employers subject to the requirements in OSHA's Walking-Working Surfaces standard (29 CFR, Subpart D). OSHA is proposing to remove a provision that sets a deadline (November 18, 2036) for the installation of personal fall arrest systems or ladder safety systems on all fixed ladders that extend more than 24 feet above a lower level. This change is based on the agency's reassessment of certain assumptions in the 2016 final rule (81 FR 82494) that established this deadline. The requirement to ensure that any new or replacement fixed ladders are equipped with a personal fall arrest system or ladder safety system would be maintained. Consistent with the agency's original intent for this provision, this change will allow employers to update their ladders when the ladders reach the end of their service lives, accommodating the lengthy service life of fixed ladders while significantly reducing costs and offering greater flexibility.</P>
                <HD SOURCE="HD1">II. Legal Authority and Preliminary Findings</HD>
                <P>
                    The purpose of the Occupational Safety and Health Act (29 U.S.C. 651 
                    <E T="03">et seq.</E>
                    ) (“the Act” or “the OSH Act”) is “to assure so far as possible every working man and woman in the Nation safe and healthful working conditions and to preserve our human resources” (29 U.S.C. 651(b)). To achieve this goal, Congress authorized the Secretary of Labor (“the Secretary”) to promulgate standards to protect workers, including the authority “to set mandatory occupational safety and health standards applicable to businesses affecting interstate commerce” (29 U.S.C. 651(b)(3); see also 29 U.S.C. 654(a)(2) (requiring employers to comply with OSHA standards), 29 U.S.C. 655(a) (authorizing summary adoption of existing consensus and established federal standards within two years of the Act's enactment), 29 U.S.C. 655(b) (authorizing promulgation, modification or revocation of standards pursuant to notice and comment)). An occupational safety and health standard is “. . . a standard which requires conditions, or the adoption or use of one or more practices, means, methods, operations, or processes, reasonably necessary or appropriate to provide safe or healthful employment and places of employment” (29 U.S.C. 652(8)).
                </P>
                <P>
                    Before OSHA may promulgate a health or safety standard, it must find that a standard is reasonably necessary or appropriate within the meaning of section 652(8) of the OSH Act. As required by the OSH Act, OSHA determined when promulgating the Walking-Working Surfaces standard that the standard would substantially reduce a significant risk of material harm (see 81 FR 82494, 82497 (November 18, 2016)). When, as here, OSHA has previously determined that its standard substantially reduces a significant risk, it is unnecessary for the agency to make additional findings on risk for every provision of that standard (
                    <E T="03">see, e.g., Pub. Citizen Health Research Grp.</E>
                     v. 
                    <E T="03">Tyson,</E>
                     796 F.2d 1479, 1502 n.16 (D.C. Cir. 1986) (rejecting the argument that OSHA must “find that each and every aspect of its standard eliminates a significant risk”)). Rather, once OSHA makes a general significant risk finding in support of a standard, the next question is whether a particular requirement is reasonably related to the purpose of the standard as a whole (
                    <E T="03">see Asbestos Info. Ass'n/N. Am.</E>
                     v. 
                    <E T="03">Reich,</E>
                     117 F.3d 891, 894 (5th Cir. 1997); 
                    <E T="03">Forging Indus. Ass'n</E>
                     v. 
                    <E T="03">Sec'y of Labor,</E>
                     773 F.2d 1436, 1447 (4th Cir. 1985); 
                    <E T="03">United Steelworkers of Am., AFL-CIO-CLC</E>
                     v. 
                    <E T="03">Marshall,</E>
                     647 F.2d 1189, 1237-38 (D.C. Cir. 1980) (“
                    <E T="03">Lead I</E>
                    ”)). The revision proposed here does not affect the agency's previous determination that the fixed ladder requirements in 29 CFR 1910.28(b)(9) are reasonably related to the purpose of the Walking-Working Surfaces standard.
                </P>
                <P>
                    A standard is technologically feasible if the protective measures it requires already exist, can be brought into existence with available technology, or can be created with technology that is reasonably expected to be developed (see 
                    <E T="03">Am. Iron and Steel Inst.</E>
                     v. 
                    <E T="03">OSHA,</E>
                     939 F.2d 975, 980 (D.C. Cir. 1991)). Courts have also interpreted technological feasibility to mean that a typical firm in each affected industry or application group will reasonably be able to implement the requirements of the standard in most operations most of the time (see, 
                    <E T="03">e.g., Public Citizen</E>
                     v. 
                    <E T="03">OSHA,</E>
                     557 F.3d 165, 170-71 (3d Cir. 2009) (citing 
                    <E T="03">Lead I</E>
                     at 1272)).
                </P>
                <P>In the 2016 final rule, OSHA determined that the fixed ladder requirements in 29 CFR 1910.28(b)(9) are technologically feasible (see 81 FR 82801). OSHA is not revisiting that finding. Because this proposed rule would merely remove a deadline for compliance with the existing requirement, OSHA preliminarily finds that this proposal would present no technological feasibility issues for employers.</P>
                <P>
                    In determining economic feasibility, OSHA must consider the cost of compliance in an industry rather than for individual employers. In its economic analyses, OSHA “must construct a reasonable estimate of compliance costs and demonstrate a reasonable likelihood that these costs will not threaten the existence or competitive structure of an industry, even if it does portend disaster for some marginal firms” (
                    <E T="03">Am. Iron and Steel Inst.,</E>
                     939 F.2d at 980, quoting 
                    <E T="03">Lead I</E>
                     647 F.2d at 1272). OSHA has preliminarily determined that this proposal is economically feasible because this action is deregulatory and imposes no additional costs. OSHA's 
                    <PRTPAGE P="17167"/>
                    economic analysis is presented in Section V.
                </P>
                <P>The Administrative Procedures Act directs agencies to include in each rule adopted “a concise general statement of [the rule's] basis and purpose” (5 U.S.C. 553(c)); cf. 29 U.S.C. 655(e) (requiring the Secretary to publish a “statement of reasons” for any standard promulgated). This notice satisfies this concise statement requirement.</P>
                <HD SOURCE="HD1">III. Background</HD>
                <P>OSHA first promulgated the Walking-Working Surfaces standard in 1971 (36 FR 10466). OSHA finalized the current Walking-Working Surfaces standard in 2016 (81 FR 82494). The standard contains fall protection requirements for fixed ladders that extend more than 24 feet above a lower level, among other provisions. In the 2016 final rule, OSHA noted that the revised standard reflected advances in technology and made the standard consistent with more recent OSHA standards and national consensus standards (81 FR 82494).</P>
                <P>On July 28, 2025, OSHA received a letter on behalf of member companies of the American Fuel &amp; Petrochemical Manufacturers (AFPM), American Chemistry Council (ACC), and American Petroleum Institute (API) (the “industry petition”), petitioning the agency to initiate rulemaking that would repeal the requirement to use personal fall arrest systems on all fixed ladders that extend more than 24 feet above a lower level and allow employers to continue to use cages and wells or, alternatively, that would allow the use of cages and wells on these ladders and require installation of personal fall arrest systems or ladder safety systems only on the ladders installed or modified after a new final rule (Ex. OSHA-2025-0072-0002). The letter states that retrofitting existing fixed ladders with personal fall arrest systems or ladder safety systems imposes extraordinary costs on the industry with “very little, if any, safety enhancement.” The member companies contend that these expenses are unjustified, as there have been very few incidents involving fixed ladders.</P>
                <P>This rulemaking proposes removing the fixed deadline from 29 CFR 1910.28(b)(9)(i). For the reasons discussed below and consistent with Executive Order (E.O.) 14219, “Ensuring Lawful Governance and Implementing the President's `Department of Government Efficiency' Deregulatory Initiative,” E.O. 14192, “Unleashing Prosperity Through Deregulation,” and the goal of significantly reducing the private expenditures required to comply with Federal regulations to secure American's economic prosperity and national security and the highest possible quality of life for each citizen, OSHA preliminarily concludes that removing the fixed deadline from 29 CFR 1910.28(b)(9)(i) will reduce the compliance burden on the regulated community while effectuating OSHA's original intent for this provision. OSHA seeks comment on the proposed change and this preliminary conclusion.</P>
                <HD SOURCE="HD1">IV. Summary and Explanation of the Proposed Requirements</HD>
                <P>OSHA is proposing to revise paragraph (b)(9) of its general industry Walking-Working Surfaces fall protection standard (29 CFR 1910.28) by removing the deadline for employers to install a personal fall arrest system or ladder safety system on fixed ladders (that extend more than 24 feet above a lower level) by November 18, 2036 (29 CFR 1910.28(b)(9)(i)(D)). Removing this deadline will allow fixed ladders with cages or wells to remain in use until the end of their service lives without an installed personal fall arrest or ladder safety system. Once these fixed ladders, cages, or wells are replaced, including due to reaching the end of their service lives, a personal fall arrest system or ladder safety system would need to be installed in at least that replaced section of the fixed ladder, cage, or well pursuant to existing paragraph (b)(9)(i)(C). Similarly, the requirement in existing paragraph (b)(9)(i)(B) that any new fixed ladders must be equipped with a personal fall arrest system or ladder safety system would remain unchanged.</P>
                <P>In explaining its decision to adopt a 20-year compliance deadline, OSHA stated in the 2016 final rule that it “set the extended phase-out period to take into account normal replacement and average useful life of fixed ladders, cages, and wells” (81 FR 82494). The agency estimated that, within 20 years, “the large majority of fixed ladders will have been replaced or in need of replacement.” In selecting a compliance date subsequent to the replacement or service duration of the “vast majority” of fixed ladders, OSHA sought to avoid undue burdens for employers by providing them “ample time to plan and carry out this transition as part of their normal business and replacement cycles, instead of retrofitting fixed ladders” (81 FR 82603). Indeed, OSHA's assessment of the economic feasibility of the requirement relied on this assumption (81 FR 82611).</P>
                <P>The concerns raised by the industry petition draw into question OSHA's assumption in the 2016 final rule that 20 years is sufficient to ensure that most employers can come into compliance with the fixed ladder fall protection requirements through their normal business and replacement cycles. By removing the fixed deadline in paragraph (b)(9)(i)(D) while maintaining the replacement requirements in existing paragraph (b)(9)(i)(C), this proposed revision would accomplish OSHA's original intent while reducing future economic burdens by avoiding costly retrofitting of currently compliant fixed ladders that have cages and wells, are in good repair, and that are not at the end of their service lives.</P>
                <P>As an alternative to removing the compliance deadline as discussed above, the petitioners requested the repeal of the requirement that employers use personal fall arrest systems on all fixed ladders over 24 feet tall and that OSHA permit them to continue to use ladder cages or wells. OSHA therefore requests comment on whether it should remove the requirement that employers use personal fall arrest systems on all fixed ladders over 24 feet tall. OSHA welcomes additional evidence regarding the costs and benefits of cages, wells, and personal fall arrest systems, and ladder safety systems, and whether cages and wells provide equivalent safety outcomes compared to personal fall arrest systems or ladder safety systems across relevant industries and ladder configurations. Employers must continue to ensure fixed ladders meet all applicable ladder requirements in 29 CFR 1910.23, Ladders, and the general requirements for all walking-working surfaces in section 1910.22, which sets requirements for safe loads, safe access and egress, inspection, general maintenance, and good repair.</P>
                <P>
                    The agency preliminarily concludes that the proposed revision to 29 CFR 1910.28(b)(9)(i) would best effectuate the agency's intent in the 2016 final rule while also serving the goals of reducing undue burden and improving compliance with OSHA's fall protection requirements. OSHA does not have evidence to suggest that removal of the deadline in section 1910.28(b)(9)(i)(D) will significantly impact the safety benefits identified in the 2016 final rule. In the final rule, OSHA estimated the rule would prevent 11.4 ladder-related fatalities and 2,161 ladder-related lost-workday injuries per year across all ladder types and all covered employers (81 FR at 82674). This includes fatalities and injuries prevented by all ladder-related provisions of the final rule, including the portable and fixed ladder design and use requirements in section 1910.23 and the fall protection requirements in section 1910.28. OSHA 
                    <PRTPAGE P="17168"/>
                    expects this proposed rule to only impact a small subset of affected ladders: fixed ladders between 24 and 30 feet in length 
                    <SU>1</SU>
                    <FTREF/>
                     that do not currently have a ladder safety system or personal fall arrest system installed and that would not be replaced by November 2036.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In the 2016 final rule, OSHA determined that fixed ladders more than 30 feet in length already use a ladder safety system or personal fall arrest system and therefore employers would not need to retrofit those ladders to comply with section 1910.28(b)(9)(i) (81 FR at 82930).
                    </P>
                </FTNT>
                <P>OSHA is unable to determine whether any of the potential fatalities or injuries avoided due to the 2016 final rule would be associated with the limited scope of this proposal; that is, whether any of those fatalities or injuries would occur among this subset of ladders in the time between 2036 and the later date at which these ladders will now be replaced. However, OSHA expects the impact of this proposal to be small. One reason is that many if not most fixed ladders covered by the 2016 final rule are still likely to be replaced by 2036. Another is that this proposal merely extends the time provided for employers to come into compliance with the fall protection requirements of section 1910.28(b)(9), it does not eliminate the requirement. Finally, OSHA anticipates that most workplaces with affected ladders are likely to have at least some ladders with personal fall arrest systems or ladder safety systems installed and employees of those employers will therefore have been trained to recognize fall hazards related to these ladders. As explained in the 2016 final rule, OSHA expects that the increased level of worker training on personal fall arrest systems and ladder safety systems required by the final rule, and the heightened recognition of related fall hazards resulting from this training, will contribute to the prevention of injuries and fatalities from falls from ladders (81 FR at 82784-82785). Based on this, the agency preliminarily determines that this proposal is not likely to result in a meaningful increase in risk to workers and the standard as a whole would remain highly protective. OSHA requests comments regarding these changes including any relevant scientific studies or other evidence.</P>
                <HD SOURCE="HD1">V. Preliminary Economic Analysis</HD>
                <HD SOURCE="HD2">A. Estimated Cost Savings</HD>
                <P>This proposed rule would allow employers more time to come into compliance with 29 CFR 1910.28(b)(9)(i), and therefore OSHA has preliminarily concluded that there would be no additional costs imposed by these proposed revisions. OSHA also anticipates that there would be significant cost savings associated with this rule, based on employers being able to avoid retrofitting or replacing current fixed ladders equipped with cages and wells while those fixed ladders are still within their useful service life. Because this rule would impose no new costs, OSHA has made a preliminary determination that the rule would be economically feasible.</P>
                <P>In the industry petition cited earlier, the petitioners state that a survey of their member companies indicated these companies have “incurred significant costs before the physical work of retrofitting has begun”; that one company alone “has spent thousands of hours over the last two years conducting fixed ladder assessments in anticipation of the work . . . $1.2 million just to identify which ladders are affected”; and that another “company estimates that it will spend $5 million to do the same” (Ex. OSHA-2025-0072-0002).</P>
                <P>The petitioners further state that their members, if made to comply with the ladder safety/personal fall arrest system requirements, would spend more than $1.2 billion to bring more than 22,000 ladders into compliance. They further noted that their member survey “represents just over one-third of the petroleum refineries in the country and a tiny fraction of other chemical manufacturing facilities.” Extrapolating from these results, petitioners suggest that this requirement could cost more than $3 billion across the U.S. refining industry (Ex. OSHA-2025-0072-0002). Based on the limited information provided by the petitioners, OSHA is unable to ascertain whether there are unique aspects of the industries represented by the petitioners that would drive costs higher than OSHA's 2016 estimate. The agency welcomes comment on whether the petitioner's estimates are representative of costs in other industries.</P>
                <P>In the 2016 final economic analysis, OSHA estimated that annualized costs of the final rule would total $305 million (81 FR 82847). Of those total costs, OSHA estimated that retrofitting fixed ladders between 24 feet and 30 feet in height with ladder safety and personal fall arrest systems would total $8.5 million in multi-year aggregated costs, or $1.2 million in annualized costs, for the approximately 109,200 fixed ladders affected by the requirement (29 CFR 1910.28(b)(9)) mandating replacement of cages and wells after November 2036 (81 FR 82841). This estimate accounted for the costs of new equipment and time for installation (2 hours per ladder) and relied on the assumptions regarding the useful life of fixed ladders that the agency is now reconsidering. If OSHA underestimated the useful life of affected ladders, then a larger percentage of affected employers would need to retrofit existing ladders to comply with the November 2036 deadline, resulting in higher costs than originally estimated.</P>
                <P>Based on petitioners' data, OSHA calculates a compliance cost of $55,000 per ladder ($1.2 billion divided by 22,000 ladders rounded to the nearest thousand); however, other entities in the petitioners' industry not surveyed could indicate different potential cost savings associated with the other two-thirds of this industry's ladders, thus the $55,000 estimate may not reflect the true average. By applying these per-ladder compliance costs to an estimated 66,000 ladders in this industry sector (extrapolating the petitioner's report of 22,000 ladders in one third of the industry to the whole industry), OSHA estimates cost savings over $3.6 billion could be achieved in this sector alone by eliminating the compliance deadline. OSHA seeks public comment on these estimates.</P>
                <P>OSHA requests comments and data on whether and to what extent the agency underestimated the number of ladders in other covered industries that would need to be retrofitted or replaced to comply with the deadline in 29 CFR 1910.28(b)(9)(i)(D). If OSHA also underestimated the number of affected ladders in other industries, the total cost savings of this proposal could be significantly higher.</P>
                <HD SOURCE="HD3">Request for Comment</HD>
                <P>To assist OSHA in evaluating the potential costs or cost savings that would result from this proposed rule, the agency requests comments, data, and information on the following:</P>
                <P>1. OSHA requests public comments on the service life of fixed ladders that extend more than 24 feet above a lower level. Additionally, OSHA requests details used to evaluate factors affecting remaining service of these ladders.</P>
                <P>2. OSHA requests public comments on what other assumptions might be driving the difference between the 2016 cost estimates and the costs claimed in the industry petition, including assumptions regarding the extent to which ladder safety and personal fall arrest systems are already installed on fixed ladders above 24 feet.</P>
                <P>
                    3. OSHA requests public comments on the petitioners' compliance cost estimates noted above for identifying, assessing, and retrofitting fixed ladders affected by paragraph 1910.28(b)(9).
                    <PRTPAGE P="17169"/>
                </P>
                <P>4. OSHA requests public comments on the agency's estimate of cost savings that would result from eliminating the need for employers to retrofit existing fixed ladders in the petitioners' industry sector to meet paragraph 1910.28(b)(9)'s November 18, 2036, deadline.</P>
                <P>5. OSHA requests data and information on the installation costs of ladder safety systems and personal fall arrest systems on fixed ladders over 24 feet in height in other industries. The agency requests that the commenters elaborate on the resource inputs that contribute to the estimate of total costs, where possible, with specific details on facility type, the operational use (function) of the ladder, frequency of climbs, the type and components of the fall safety system currently installed, the cost of replacing a fixed ladder (on a per-foot or per-section basis if appropriate), the timing of a retrofit (proximity to 2036) if the 2016 rule were to remain in place without revision, and the type of fall safety system projected for retrofitting affected fixed ladders. The petitioners identified 22,000 ladders that would be affected by the 2016 final rule's deadline for replacement in portions of two industries. OSHA requests additional information on the number of fixed ladders in petroleum refineries, chemical manufacturing, and other industries that might be affected by this proposed rule.</P>
                <P>6. OSHA requests data from all interested parties on current (baseline) practices for the provision of fall protection on fixed ladders, including survey data on the extent of existing practices among affected employers for assessing the performance and effectiveness of fall prevention systems on fixed ladders, as well as survey data on current, baseline administrative controls such as manager familiarization, training, and recordkeeping.</P>
                <P>7. If employers have already incurred costs or cost savings as a result of implementing paragraph 1910.28(b)(9)(i), please describe in detail (for example, cost or cost savings per worker, per process unit, or per production operation) the size and scope of the costs or cost savings, and the size and scope of any benefits that have been achieved from the changes in the use of fall safety systems on fixed ladders.</P>
                <P>8. OSHA invites all stakeholders to comment on any technological, economic, and safety-related impacts of the proposed removal of paragraph 1910.28(b)(9)(i)(D).</P>
                <P>9. OSHA requests comment on whether it should repeal or revise the requirement that employers use personal fall arrest systems on all fixed ladders over 24 feet. OSHA welcomes additional evidence regarding whether cages and wells provide equivalent safety outcomes compared to personal fall arrest systems or ladder safety systems across relevant industries and ladder configurations.</P>
                <HD SOURCE="HD2">B. Review Under the Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ) requires preparation of an initial regulatory flexibility analysis (IRFA) and a final regulatory flexibility analysis (FRFA) for any rule that by law must be proposed for public comment, unless the agency certifies that the rule, if promulgated, will not have a significant economic impact on a substantial number of small entities. The Act requires each IRFA to describe regulatory alternatives that would “minimize any significant economic impact of the proposed rule on small entities.” 5 U.S.C. 603(c). Each FRFA must describe “steps the agency has taken to minimize the significant economic impact on small entities.” 
                    <E T="03">Id.</E>
                     § 604(a)(6). The term “significant economic impact,” as used in the Act to trigger IRFA and FRFA requirements, thus refers to 
                    <E T="03">adverse</E>
                     economic impacts that should be minimized.
                </P>
                <P>OSHA reviewed this proposed rule under the provisions of the Regulatory Flexibility Act. This rule would eliminate a regulatory requirement and reduce compliance burdens on both small and large employers. Therefore, OSHA certifies that the revision would not have a “significant economic impact on a substantial number of small entities,” and that the preparation of an IRFA is not warranted. OSHA will transmit this certification and supporting statement of factual basis to the Chief Counsel for Advocacy of the Small Business Administration for review under 5 U.S.C. 605(b).</P>
                <HD SOURCE="HD2">C. Review Under Executive Order 12866</HD>
                <P>E.O. 12866, “Regulatory Planning and Review” (58 FR 51735 (Oct. 4, 1993)), requires agencies, to the extent permitted by law, to (1) propose or adopt a regulation only upon a reasoned determination that its benefits justify its costs (recognizing that some benefits and costs are difficult to quantify); (2) tailor regulations to impose the least burden on society, consistent with obtaining regulatory objectives, taking into account, among other things, and to the extent practicable, the costs of cumulative regulations; (3) select, in choosing among alternative regulatory approaches, those approaches that maximize net benefits; (4) to the extent feasible, specify performance objectives, rather than specifying the behavior or manner of compliance that regulated entities must adopt; and (5) identify and assess available alternatives to direct regulation, including providing economic incentives to encourage the desired behavior, such as user fees or marketable permits, or providing information upon which choices can be made by the public.</P>
                <P>Section 6(a) of E.O. 12866 also requires agencies to submit “significant regulatory actions” to the Office of Information and Regulatory Affairs (OIRA) for review. OIRA has determined that this proposed rule is a “significant regulatory action” under the criteria in section 3(f) of E.O. 12866. Accordingly, this proposed rule was submitted to OIRA for review under E.O. 12866.</P>
                <HD SOURCE="HD1">VI. Additional Requirements</HD>
                <HD SOURCE="HD2">A. Requirements for States With OSHA-Approved State Plans</HD>
                <P>
                    Under section 18 of the OSH Act (29 U.S.C. 651 
                    <E T="03">et seq.</E>
                    ), Congress expressly provides that States may adopt, with Federal approval, a plan for the development and enforcement of occupational safety and health standards that are “at least as effective” as the Federal standards in providing safe and healthful employment and places of employment (29 U.S.C. 667). OSHA refers to these OSHA-approved, State-administered occupational safety and health programs as “State Plans.” 
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Of the 29 States and U.S. territories with OSHA-approved State Plans, 22 cover public and private-sector employees: Alaska, Arizona, California, Hawaii, Indiana, Iowa, Kentucky, Maryland, Michigan, Minnesota, Nevada, New Mexico, North Carolina, Oregon, Puerto Rico, South Carolina, Tennessee, Utah, Vermont, Virginia, Washington, and Wyoming. The remaining six States and one U.S. territory cover only State and local government employees: Connecticut, Illinois, Maine, Massachusetts, New Jersey, New York, and the Virgin Islands.
                    </P>
                </FTNT>
                <P>
                    When Federal OSHA promulgates a new standard or a more stringent amendment to an existing standard, State Plans must either amend their standards to be identical to, or “at least as effective as,” the new Federal standard or amendment, or show that an existing State Plan standard covering this issue is “at least as effective” as the new Federal standard or amendment (29 CFR 1953.5(a)). However, when OSHA promulgates a new standard or amendment that does not impose additional or more stringent requirements than an existing standard, State Plans do not have to amend their standards, although they may opt to do so. OSHA has preliminarily determined this proposed rule does not impose 
                    <PRTPAGE P="17170"/>
                    additional or more stringent requirements than the existing standard, and therefore State Plans are not required to amend their standards. OSHA seeks comment on this assessment of its proposal.
                </P>
                <HD SOURCE="HD2">B. OMB Review Under the Paperwork Reduction Act of 1995</HD>
                <P>The Paperwork Reduction Act (PRA) defines “collection of information” to mean “the obtaining, causing to be obtained, soliciting, or requiring the disclosure to third parties or the public, of facts or opinions by or for an agency, regardless of form or format” (44 U.S.C. 3502(3)(A)). Under the PRA, a federal agency cannot conduct or sponsor a collection of information unless it is approved by OMB under the PRA and the agency displays a currently valid OMB control number (44 U.S.C. 3507). Also, notwithstanding any other provisions of law, no person shall be subject to penalty for failing to comply with a collection of information if the collection of information does not display a currently valid OMB control number (44 U.S.C. 3512(a)(1)). The process for OMB approval is found in 5 CFR part 1320. This proposed rule would impose no new information collection requirements. Because the proposed revisions do not affect the currently approved information collections, OMB approval is not required for this proposed rule.</P>
                <HD SOURCE="HD2">C. Environmental Impacts/National Environmental Policy Act (NEPA)</HD>
                <P>
                    OSHA has reviewed this proposed rule according to the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), as amended by the Fiscal Responsibility Act of 2023 (Pub. L. 118-5,  321, 137 Stat. 10), and the Department of Labor's NEPA procedures (29 CFR part 11). Under the Department's regulations, the “[p]romulgation, modification or revocation of any [OSHA] safety standard” is categorically excluded from the requirement to prepare an environmental assessment absent extraordinary circumstances indicating the potential for significant environmental effects (29 CFR 11.10(a)(1)). OSHA has preliminarily determined that no such extraordinary circumstances exist, and that this proposal would have no impact on the quality of the human environment.
                </P>
                <HD SOURCE="HD2">D. Other Statutory and Executive Order Considerations</HD>
                <P>
                    OSHA has considered its obligations under the Unfunded Mandates Reform Act (UMRA) (2 U.S.C. 1501 
                    <E T="03">et seq.</E>
                    ) and the Executive Orders on Consultation and Coordination With Indian Tribal Governments (E.O. 13175, 65 FR 67249 (Nov. 6, 2000)), Federalism (E.O. 13132, 64 FR 43255 (Aug. 10, 1999)), and Protection of Children From Environmental Health Risks and Safety Risks (E.O. 13045, 62 FR 19885 (Apr. 23, 1997)). Given that this is a proposed deregulatory action that involves the removal of requirements, does not result in any Federal mandates, and does not constitute a policy that has federalism or tribal implications, OSHA has determined that no further agency action or analysis is required to comply with these statutes and executive orders. Furthermore, OSHA has determined that this proposal is consistent with the policies and directives outlined in E.O. 14192, “Unleashing Prosperity Through Deregulation.” If finalized as proposed, this NPRM is expected to be an E.O. 14192 deregulatory action.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 29 CFR Part 1910</HD>
                    <P>Falls, Fall arrest, Fall protection, Fixed ladders, Ladders, Ladder cages, Ladder safety systems, Ladder wells, Occupational safety and health, Personal fall arrest systems, Walking-Working Surfaces. </P>
                </LSTSUB>
                <HD SOURCE="HD1">VII. Authority and Signature</HD>
                <P>This document was prepared under the direction of David Keeling, Assistant Secretary of Labor for Occupational Safety and Health. It is issued under the authority of sections 4, 6, and 8 of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653, 655, and 657), 5 U.S.C. 553, Secretary of Labor's Order No. 8-2020 (85 FR 58393), and 29 CFR part 1911.</P>
                <SIG>
                    <NAME>David Keeling,</NAME>
                    <TITLE>Assistant Secretary of Labor for Occupational Safety and Health.</TITLE>
                </SIG>
                <HD SOURCE="HD1">VIII. Regulatory Text</HD>
                <HD SOURCE="HD2">Proposed Amendments</HD>
                <P>For the reasons set forth in the preamble, OSHA is amending 29 CFR part 1910 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1910—OCCUPATIONAL SAFETY AND HEALTH STANDARDS</HD>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart D—Walking-Working Surfaces</HD>
                    </SUBPART>
                </PART>
                <REGTEXT TITLE="29" PART="1910">
                    <AMDPAR>1. The authority citation for subpart D is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>29 U.S.C. 653, 655, and 657; Secretary of Labor's Order No. 12-71 (36 FR 8754), 8-76 (41 FR 25059), 9-83 (48 FR 35736), 1-90 (55 FR 9033), 6-96 (62 FR 111), 3-2000 (65 FR 50017), 5-2002 (67 FR 65008); 5-2007 (72 FR 31160), 4-2010 (75 FR 55355), 1-2012 (77 FR 3912), 8-2020 (85 FR 58393), or 7-2025 (90 FR 27878); 29 CFR part 1911; and 5 U.S.C. 553, as applicable.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="1910">
                    <AMDPAR>2. Amend § 1910.28 by removing paragraph (b)(9)(i)(D) and revising paragraph (b)(9)(i) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1910.28 </SECTNO>
                        <SUBJECT>Duty to have fall protection and falling object protection.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(9) * * *</P>
                        <P>(i) * * *</P>
                        <P>(A) Existing fixed ladders. Each fixed ladder installed before November 19, 2018 is equipped with a personal fall arrest system, ladder safety system, cage, or well;</P>
                        <P>(B) New fixed ladders. Each fixed ladder installed on and after November 19, 2018, is equipped with a personal fall arrest system or a ladder safety system; and</P>
                        <P>(C) Replacement. When a fixed ladder, cage, or well, or any portion of a section thereof, is replaced, a personal fall arrest system or ladder safety system is installed in at least that section of the fixed ladder, cage, or well where the replacement is located.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06578 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-26-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 100</CFR>
                <DEPDOC>[Docket Number USCG-2025-1120]</DEPDOC>
                <RIN>RIN 1625-AA08</RIN>
                <SUBJECT>Special Local Regulation; 4th of July Fireworks, East River and Upper New York Bay, Manhattan, Queens, and Brooklyn, NY</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is proposing to establish a temporary special local regulation (SLR) for certain navigable waters of the East River and Upper New York Bay in New York Harbor, NY. The SLR is needed to provide for the safety of life on these highly congested waterways immediately before, during, and after a 4th of July fireworks display. The rule would control vessel movement, prohibit entry into moving protection zones around transiting fireworks barges, establish exclusion zones near launch sites, and create spectator zones. The Coast Guard invites public comment on this proposed rulemaking.</P>
                </SUM>
                <EFFDATE>
                    <PRTPAGE P="17171"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and related material must be received by the Coast Guard on or before May 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To submit comments and view available documents at 
                        <E T="03">https://www.regulations.gov</E>
                         and search for USCG-2025-1120.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this proposed rule, contact MST1 Scott Baumgartner, Sector New York Waterways Management Division, U.S. Coast Guard; telephone 718-801-2932, or email 
                        <E T="03">Scott.A.Baumgartner@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">COTP Captain of the Port, Sector New York</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">
                        FR 
                        <E T="03">Federal Register</E>
                    </FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">SLR Special Local Regulation</FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                    <FP SOURCE="FP-1">VHF FM Very High Frequency Modulated Radio Transmission </FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background and Authority</HD>
                <P>Macy's has hosted an annual 4th of July fireworks display in New York harbor since 1976 in varying locations. In 2022, the Coast Guard established a permanent special local regulation (SLR) for the event, codified at 33 CFR 100.110.</P>
                <P>
                    However, the locations of the barge-based fireworks launch sites and the number of barges used have varied each year since then. On October 23, 2025, the Coast Guard received an updated Application for Marine Event, Form CG-4423, in which Macy's proposed to launch fireworks from multiple locations in a significantly larger event in 2026 than in past years. On January 16, 2026, Macy's updated their fireworks launch location to five barges on the East River south of Roosevelt Island, NY, three barges on the East River southwest of the Brooklyn Bridge near Manhattan, NY, and one land-based location from the deck of the Brooklyn Bridge over the East River. As such, the Coast Guard is proposing a temporary rule for Macy's 2026 fireworks display. Additionally, this year's proposed display would take place concurrently with an International Naval Review and Sail 4th 250 event in New York Harbor. Refer to Notice of Proposed Rulemaking (NPRM) published in the 
                    <E T="04">Federal Register</E>
                     on December 19, 2025, titled “Special Local Regulation, Temporary Anchorage Ground Suspension, and Security Zones: Sail 4th 250, International Naval Review 250; Port of New York and New Jersey” (90 FR 59422). Any waterway restrictions established as a result of the temporary final rule for that regulatory project would also apply to any Special Local Regulation established under this regulatory project. The comment period for that regulatory project has closed. The Coast Guard is not accepting any comments on that rulemaking and is evaluating all comments already received.
                </P>
                <P>Hazards from fireworks displays include accidental discharge of fireworks, dangerous projectiles, and falling hot embers or other debris. The COTP has therefore determined that potential hazards associated with fireworks are a safety concern for anyone within exclusion areas Charlie and Echo. In addition, when large numbers of vessels operate in close proximity to one another, the potential for other hazards, such as collisions and allisions with persons, vessels, and infrastructure is also heightened. The COTP has determined the high volume of commercial and recreational vessels expected to be operating in close proximity to one another in addition to the hazard areas around the fireworks displays warrant additional regulation to ensure the safety of participant and non-participant vessels. This rule also proposes to prohibit the operation of all personal watercraft within the regulated areas during the enforcement period of the rule. Due to their high speed and maneuverability, coupled with a history of incursions into exclusion zones within New York harbor, personal watercraft pose a significant safety risk in congested waterways and are considered a risk to the safety and security of this event.</P>
                <P>The COTP is proposing this rule under the authority of 46 U.S.C. 70041 to ensure the safety of participants, spectators, non-participants, and other transiting vessels by establishing multiple zones for viewing the event and ensuring a safe distance from the fireworks launch sites. The proposed regulatory text appears at the end of this document.</P>
                <HD SOURCE="HD1">III. Discussion of the Rule</HD>
                <P>This proposed rule would establish a special local regulation from 5:30 p.m. on July 4, 2026, until 11:30 p.m. on July 5, 2026. It would only be enforced from 5:30 p.m. until 11:30 p.m. on July 4, 2026, unless the event is delayed because of weather conditions, in which case it will be subject to enforcement during those same hours on July 5, 2026. The duration of the enforcement times is intended to ensure the safety of vessels, participants, spectators and non-participants, and other vessels transiting the area immediately before, during, and after the fireworks display.</P>
                <P>The regulated area would cover all navigable waters within 50 yards of the eight fireworks barges during their transit from their respective staging area to their respective launch location. This proposed rule would also create seven stationary regulated areas: an exclusion area around the Brooklyn Bridge area fireworks launch locations, an exclusion area around the Roosevelt Island area fireworks launch locations, and five spectator viewing areas. As shown in Figure 1 below, the exclusion areas, CHARLIE (“C”) and ECHO (“E”), would exclude all non-participant vessels, including spectator vessels, from the area surrounding the fireworks launch locations immediately before, during, and after the fireworks display. The five separate spectator viewing areas, ALPHA (“A”), BRAVO (“B”), DELTA (“D”), FOXTROT (“F”) and GOLF (“G)”, would be available to vessels based on the vessel's length and the timing of its entry into each zone. This proposed rule is based on the best available planning information at this time. It is important to note that, due to ongoing discussions regarding navigational safety and security concerns, spectator area DELTA (“D”) may ultimately be designated as an exclusion area rather than a spectator area in the temporary final rule. However, at this stage, the rule is being proposed with DELTA (“D”) included as a spectator area. We welcome and encourage all comments on this topic to help us understand the complex competing demands within this area.</P>
                <P>
                    Spectator area DELTA (“D”) would be open to all vessels. Any vessel desiring to utilize spectator area DELTA (“D”) would have to enter the regulated area by 7:30 p.m. and would not be permitted to exit the area through either exclusion area, CHARLIE (“C”) or ECHO (“E”), until those areas are disestablished, or until spectator and other non-participant vessels are released from area Delta (“D”) by the COTP or their designated representative. Spectator areas ALPHA (“A”) and FOXTROT (“F”) would be open to vessels greater than 65.6 feet (20 meters) in length. Spectator areas BRAVO (“B”) and GOLF (“G)” would be open to vessels 65.6 feet (20 meters) or less in length. Vessels desiring to utilize areas ALPHA (“A”), BRAVO (“B”), FOXTROT (“F”) and GOLF (“G)” would be able to begin entering their designated viewing area at 8:00 p.m. Additionally, vessels desiring to utilize area FOXTROT (“F”) would have to be in a holding position no later than 9:00 p.m. and would be required to depart the area without delay following the 
                    <PRTPAGE P="17172"/>
                    conclusion of the fireworks display to enable the safe and timely resumption of ferry services. The conclusion of the fireworks display will be announced via a Broadcast Notice to Mariners on VHF-FM Channel 16 or on-scene by the COTP or their designated representative. The waters to the west, north, and south of spectator area Foxtrot (“F”) will be immediately available for these purposes while the waters to the east within exclusion area ECHO (“E”) will remain closed to unauthorized traffic until the “cooling off” period for the fireworks barges has expired.
                </P>
                <P>
                    Some of the areas regulated by this proposed rule overlap with areas covered by the proposed rule, “Special Local Regulation, Temporary Anchorage Ground Suspension, and Security Zones: Sail 4th 250, International Naval Review 250; Port of New York and New Jersey,” published in the 
                    <E T="04">Federal Register</E>
                     on December 19, 2025 (90 FR 59422). Only vessels authorized under the Sail 4th 250 and International Naval Review 250 proposed rule would be allowed to operate in the regulated areas proposed in this rulemaking during the enforcement period.
                </P>
                <BILCOD>BILLING CODE 9110-04-P</BILCOD>
                <HD SOURCE="HD1">Figure 1: Chartlet Showing the Area and Proposed Layout of the Special Local Regulation</HD>
                <GPH SPAN="3" DEEP="583">
                    <PRTPAGE P="17173"/>
                    <GID>EP06AP26.084</GID>
                </GPH>
                <BILCOD>BILLING CODE 9110-04-C</BILCOD>
                <P>Navigation rules, 33 CFR part 83, which are now in force, would continue to apply at all times within the regulated areas. The Coast Guard would provide notice of the special local regulation by Local Notice to Mariners, Broadcast Notice to Mariners, and on-scene designated representatives. The regulatory text we are proposing appears at the end of this document.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this proposed rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders.</P>
                <HD SOURCE="HD2">A. Impact on Small Entities</HD>
                <P>
                    The Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, as amended, requires Federal agencies to consider 
                    <PRTPAGE P="17174"/>
                    the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule would not have a significant economic impact on a substantial number of small entities for the following reasons.
                </P>
                <P>Vessel traffic would be able to safely transit around this regulated area using the Hudson River and Harlem River. Vessel traffic would only be restricted in the regulated area for approximately six hours on either July 4, 2026, or July 5, 2026. In addition, the Coast Guard would make advance public notification through a Broadcast Notice to Mariners (BNM) via VHF FM marine channel 16, a Local Notice to Mariners (LNM), a Marine Safety Information Bulletin (MSIB), and/or a Coast Guard Advisory Notice (CGAN) which would allow small entities to adjust their transit plans and operations. The proposed rule would also allow vessels to request permission to enter the regulated area from the COTP.</P>
                <P>
                    If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this proposed rule would have a significant economic impact on it, please submit a comment (see 
                    <E T="02">ADDRESSES</E>
                    ) explaining why you think it qualifies and how and to what degree this proposed rule would economically affect it.
                </P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), if this proposed rule will affect your small business, organization, or governmental jurisdiction and you have questions, contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. Small businesses may send comments to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards by calling 1-888-REG-FAIR (1-888-734-3247).
                </P>
                <HD SOURCE="HD2">B. Collection of Information</HD>
                <P>This proposed rule does not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">C. Federalism and Indian Tribal Governments</HD>
                <P>We have analyzed this proposed rule under Executive Order 13132, Federalism, and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in that Order.</P>
                <P>Also, this proposed rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
                <P>As required by The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538), the Coast Guard certifies that this proposed rule would not result in an annual expenditure of $100,000,000 or more (adjusted for inflation) by a State, local, or tribal government, in the aggregate, or by the private sector.</P>
                <HD SOURCE="HD2">E. Environment</HD>
                <P>
                    We have analyzed this proposed rule under Department of Homeland Security Directive 023-01, Rev. 1, associated implementing instructions, and Environmental Planning COMDTINST 5090.1 (series), which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321, 
                    <E T="03">et seq.</E>
                    ), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
                </P>
                <P>This proposed rule is a special local regulation. It is categorically excluded from further review under paragraph L61.</P>
                <HD SOURCE="HD1">V. Public Participation and Request for Comments</HD>
                <P>We view public participation as essential to effective rulemaking and will consider all comments and material received during the comment period. Your comment can help shape the outcome of this rulemaking. If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.</P>
                <P>
                    <E T="03">Submitting comments.</E>
                     We encourage you to submit comments at 
                    <E T="03">https://www.regulations.gov.</E>
                     To do so, go to 
                    <E T="03">https://www.regulations.gov,</E>
                     type USCG-2025-1120 in the search box and click “Search.” Next, look for this document in the Search Results column, and click on it. Then click on the Comment option. If you cannot submit your material by using 
                    <E T="03">https://www.regulations.gov,</E>
                     call or email the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this proposed rule for alternate instructions.
                </P>
                <P>
                    <E T="03">Viewing material in the docket.</E>
                     To view available documents, find the docket as described in the previous paragraph, and then select “Supporting &amp; Related Material” in the Document Type column. We will post public comments in our online docket. Additional information is on the 
                    <E T="03">https://www.regulations.gov</E>
                     Frequently Asked Questions web page.
                </P>
                <P>
                    <E T="03">Personal information.</E>
                     We accept anonymous comments. Comments we post to 
                    <E T="03">https://www.regulations.gov</E>
                     will include any personal information you have provided. For more about privacy and submissions to the docket in response to this document, see DHS's eRulemaking System of Records notice (85 FR 14226, March 11, 2020).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
                    <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard is proposing to amend 33 CFR part 100 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>46 U.S.C. 70041; 33 CFR 1.05-1.</P>
                </AUTH>
                <AMDPAR>2. Add § 100.T0199-1120 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 100.T0199-1120</SECTNO>
                    <SUBJECT>Special Local Regulation; 4th of July Fireworks, East River and Upper New York Bay, Manhattan, Queens, and Brooklyn, NY</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Regulated areas.</E>
                         The regulations in this section apply to the following areas:
                    </P>
                    <P>
                        (1) 
                        <E T="03">Spectator Area ALPHA (“A”):</E>
                         All navigable waters of the East River bounded by a line connecting the following points: starting at 40°45′30.76″ N, 073°57′30.62″ W (near the Ed Koch Queensboro Bridge, Manhattan); thence to 40°45′26.02″ N, 073°57′19.97″ W (near the Ed Koch Queensboro Bridge, Roosevelt Island); thence along shore to 40°44′58.05″ N, 073°57′41.72″ W (near the southern tip of Roosevelt Island); thence to 40°45′04.74″ N, 073°57′54.27″ W (near E 48th Street, Manhattan), then along the shoreline back to the point of origin.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Spectator Area BRAVO (“B”):</E>
                         All navigable waters of the East River bounded by a line connecting the following points: starting at 
                        <PRTPAGE P="17175"/>
                        40°45′22.71″ N, 073°57′12.19″ W (near the Ed Koch Queensboro Bridge, Roosevelt Island); thence to 40°45′18.72″ N, 073°57′03.05″ W (near the Ed Koch Queensboro Bridge, Queens); thence along shore to 40°44′51.80″ N, 073°57′28.67″ W (near 46th Avenue, Queens); thence to 40°44′57.87″ N, 073°57′41.46″ W (near the southern tip of Roosevelt Island), then along shore back to the point of origin.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Exclusion Area CHARLIE (“C”):</E>
                         All navigable waters of the East River bounded by a line connecting the following points: starting at 40°45′04.74″ N, 073°57′54.27″ W (near E. 48th Street, Manhattan); thence to 40°44′51.80″ N, 073°57′28.67″ W (near 46th Avenue, Queens); thence along shore to 40°43′48.62″ N, 073°57′40.66″ W (near Greenpoint Water View, Brooklyn); thence to 40°43′47.56″ N, 073°58′18.59″ W (near E 15th Street, Manhattan), then along shore back to the point of origin.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Spectator Area DELTA (“D”):</E>
                         All waters of the East River bounded by a line connecting the following points: starting at 40°43′47.56″ N, 073°58′18.59″ W (near E 15th Street, Manhattan); thence to 40°43′48.62″ N, 073°57′40.66″ W (near Greenpoint Water View, Brooklyn); thence to 40°42′16.42″ N, 073°59′20.13″ W (near Manhattan Bridge; Brooklyn); thence to 40°42′34.43″ N, 073°59′30.24″ W (near Manhattan Bridge; Manhattan), then along the shore back to the point of origin.
                    </P>
                    <P>
                        (5) 
                        <E T="03">Exclusion Area ECHO (“E”):</E>
                         All navigable waters of the East River bounded by a line connecting the following points: starting at 40°42′34.43″ N, 073°59′30.24″ W (near Manhattan Bridge; Manhattan); thence to 40°42′16.42″ N, 073°59′20.13″ W (near Manhattan Bridge; Brooklyn); thence along shore to 40°41′38.59″ N, 074°00′12.43″ W (near Pier 6, Brooklyn); thence to 40°41′33.44″ N, 074°00′43.56″ W (near the Hugh Carey Tunnel Ventilator Building, Governors Island); thence to 40°42′00.15″ N, 074°00′43.06″ W (near the Whitehall Ferry Terminal, Manhattan); then along shore back to the point of origin.
                    </P>
                    <P>
                        (6) 
                        <E T="03">Spectator Area FOXTROT (“F”):</E>
                         All navigable waters of New York Harbor bounded by a line connecting the following points: starting at 40°42′00.15″ N, 074°00′43.06″ W (near the Whitehall Ferry Terminal, Manhattan); thence to 40°41′33.44″ N, 074°00′43.56″ W (near the Hugh Carey Tunnel Ventilator Building, Governors Island); thence along shore to 40°41′35.48″ N, 074°01′10.57″ W (near Castle Williams, Governors Island); thence to 40°41′52.28″ N, 074°01′16.13″ W (near Deep Water Channel Lighted Buoy “1”); thence to 40°42′11.45″ N, 074°01′03.02″ W (near Castle Clinton, Manhattan); then along shore back to the point of origin.
                    </P>
                    <P>
                        (7) 
                        <E T="03">Spectator Area GOLF (“G”):</E>
                         All navigable waters of New York Harbor bounded by a line connecting the following points: starting at 40°41′33.44″ N, 074°00′43.56″ W (near the Hugh Carey Tunnel Ventilator Building, Governors Island); thence to 40°41′38.59″ N, 074°00′12.43″ W (near Pier 6, Brooklyn); thence along shore to 40°40′44.32″ N, 074°01′10.24″ W (near Brooklyn Cruise Terminal, Brooklyn); thence to 40°41′03.13″ N, 074°01′32.08″ W (near the southern tip of Governors Island); then along shore back to the point of origin.
                    </P>
                    <P>
                        (8) 
                        <E T="03">Moving Protection Zone:</E>
                         A moving protection zone on all navigable waters within a 50-yard radius of the participating barges while they are loaded with explosive material will be enforced from the point of departure within the COTP New York zone until placement at the intended destination. The point of departure will be determined prior to enforcement of the moving protection zone, and the details will be released through a Broadcast Notice to Mariners.
                    </P>
                    <P>(9) These coordinates are based on the World Geodetic System (WGS 84)/North American Datum 83 (NAD 83).</P>
                    <P>
                        (b) 
                        <E T="03">Definitions.</E>
                         As used in this section—
                    </P>
                    <P>
                        (1) 
                        <E T="03">Designated representative</E>
                         means a Coast Guard Patrol Commander, including a Coast Guard coxswain, petty officer, or other officer operating a Coast Guard vessel and a Federal, State, and local officer designated by or assisting the Captain of the Port Sector New York (COTP) in the enforcement of the regulated areas in this section.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Official Patrol Vessel</E>
                         means any Coast Guard, Coast Guard Auxiliary, Federal, State or local law enforcement vessel assigned or approved by the COTP to assist in the enforcement of the regulated areas in this section.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Participant</E>
                         means all persons and vessels registered with the event sponsor as a participant in the event.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Personal watercraft</E>
                         means any vessel propelled by a water-jet pump or other machinery as its primary source of motive power and designed to be operated by a person sitting, standing, or kneeling on the vessel, rather than sitting or standing within the vessel's hull.
                    </P>
                    <P>
                        (5) 
                        <E T="03">Non-participant</E>
                         means a person or vessel, including a spectator or spectator vessel, not registered with the event sponsor as participants or official patrol vessels.
                    </P>
                    <P>
                        (c) 
                        <E T="03">Regulations.</E>
                         (1) All non-participants are prohibited from entering, transiting through, anchoring in, or remaining within the regulated areas described in paragraph (a) of this section, except as provided in paragraph (c)(2), unless authorized by the COTP or their designated representative.
                    </P>
                    <P>(2) All vessels that are authorized by the COTP or their designated representative to enter the regulated areas established by this section must adhere to the following restrictions:</P>
                    <P>(i) Spectator Area ALPHA (“A”) is limited to vessels over 65.6 feet (20 meters) in length. Vessels desiring to use spectator area ALPHA (A”) may enter the area starting at 8:00 p.m.</P>
                    <P>(ii) Spectator Area BRAVO (“B”) is limited to vessels less-than or equal to 65.6 feet (20 meters) in length. Vessels desiring to use spectator area BRAVO (“B”) may enter the area starting at 8:00 p.m.</P>
                    <P>(iii) All non-participant vessels are prohibited from entering exclusion area CHARLIE (“C”) without permission from the COTP or their designated representative after 7:30 p.m. All vessels authorized to transit by the COTP or their designated representative must pass as close to the pierhead as safely possible and must transit through the area no later than 8:00 p.m. Vessels must operate at the minimum speed necessary to maintain safe course while crossing through area CHARLIE (“C”) and comply with all directions that may be provided by the COTP or their designated representative.</P>
                    <P>(iv) Spectator Area DELTA (“D”) is open to all vessels. All vessels desiring to enter and exit area DELTA (“D”) must complete their transit by 7:30 p.m. Vessels within spectator area DELTA (“D”) at 7:30 p.m. will not be able to exit through exclusion areas CHARLIE (“C”) and ECHO (“E”) until those areas are disestablished by COTP or after receiving authorization from the COTP or their designated representative.</P>
                    <P>
                        (v) All non-participant vessels are prohibited from entering exclusion area ECHO (“E”) without permission from the COTP or their designated representative after 7:30 p.m. All vessels authorized to transit by the COTP or their designated representative must pass as close to the pierhead as safely possible and must transit through the area no later than 8:00 p.m. Vessels must operate at the minimum speed necessary to maintain safe course while crossing through area ECHO (“E”) and comply with all directions that may be provided by the Coast Guard.
                        <PRTPAGE P="17176"/>
                    </P>
                    <P>(vi) Spectator Area FOXTROT (“F”) is limited to vessels over 65.6 feet (20 meters) in length. Vessels desiring to use area FOXTROT (“F”) may begin entering the designated spectator area at 8:00 p.m. and must be in a holding position no later than 9:00 p.m. Vessels must depart spectator area FOXTROT (“F”) without delay following the conclusion of the fireworks display.</P>
                    <P>(vii) Spectator Area Golf (“G”) is limited to vessels less than or equal to 65.6 feet (20 meters) in length. Vessels desiring to use spectator area GOLF (“G”) may enter the area starting at 8:00 p.m.</P>
                    <P>(3) During periods of enforcement all persons and vessels in the regulated areas must comply with all lawful orders and directions from the COTP or their designated representative.</P>
                    <P>(4) During periods of enforcement, the COTP or their designated representative may restrict the number of vessels allowed within the regulated area to prevent overcrowding and ensure safe navigation. Once the COTP or their designated representative determines that the regulated area has reached a safe capacity, no additional vessels will be allowed to enter unless specifically authorized by the COTP or their designated representative.</P>
                    <P>
                        (5) The operation of 
                        <E T="03">personal watercraft</E>
                         is prohibited in any regulated areas.
                    </P>
                    <P>(6) Vessel operators desiring to enter or operate within the regulated areas outside the restrictions identified in (c)(2) of this section should contact the COTP or their designated representative at 844-NYC-USCG or on VHF 16 to obtain permission.</P>
                    <P>(7) Non-participant and Spectator Vessels must not anchor, block, loiter or impede the transit of event participants or official patrol vessels in the regulated areas during the enforcement period and times unless authorized by the COTP or their designated representative.</P>
                    <P>
                        (d) 
                        <E T="03">Enforcement periods.</E>
                         (1) This section is in effect from 5:30 p.m. July 4, 2026, to 11:30 p.m. July 5, 2026. It will only be subject to enforcement, however, from 5:30 p.m. through 11:30 p.m. on Saturday, July 4, 2026, unless the event is delayed because of weather conditions, in which case it may be subject to enforcement of those same hours on July 5, 2026.
                    </P>
                    <P>(2) The COTP will provide advance notice of the enforcement period for the regulated areas as well as any changes to the enforcement times of the regulated area through local notice to mariners, broadcast notice to mariners, and through on-scene notice by the COTP's designated representative or official patrol vessels.</P>
                </SECTION>
                <SIG>
                    <NAME>Jonathan A. Andrechik,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Sector New York.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06619 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 82</CFR>
                <DEPDOC>[EPA-HQ-OAR-2024-0503; FRL-12207-03-OAR]</DEPDOC>
                <RIN>RIN 2060-AW45</RIN>
                <SUBJECT>Protection of Stratospheric Ozone: Listing of Substitutes Under the Significant New Alternatives Policy Program in Refrigeration and Air Conditioning and Fire Suppression; Supplemental Notice of Proposed Rulemaking</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Supplemental proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the U.S. Environmental Protection Agency's Significant New Alternatives Policy program, this action proposes to list the refrigerant 2,3,3,3-tetrafluoropropene, also known as HFO-1234yf, as acceptable, subject to use conditions, in the motor vehicle air conditioning end-use for retrofit of heavy-duty pickup trucks and complete heavy-duty vans. This action supplements the Agency's November 10, 2025, proposal with respect to the proposed listings in the motor vehicle air conditioning end-use for retrofit of heavy-duty pickup trucks and heavy-duty vans (both complete and incomplete vans). The EPA is also supplementing that proposal to clarify the intended scope of that proposed rule. The EPA is providing an opportunity for public comment on the additional listing and the clarification. The EPA is not reopening the comment period for any portions of the November 10, 2025, proposal which are not explicitly addressed in this supplemental proposal.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments on this supplemental proposal must be received on or before May 6, 2026 unless a public hearing is held. If a public hearing is held, comments on this supplemental proposal must be received on or before 30 days after the date of the public hearing. 
                        <E T="03">Public hearing:</E>
                         Any party requesting a public hearing must notify the contact listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section, which is Emily Maruyama at email address: 
                        <E T="03">maruyama.emily@epa.gov</E>
                         by 5 p.m. Eastern Daylight Time on or before April 13, 2026. If a public hearing is held, it will take place on or around April 21, 2026. Please refer to the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for additional information on the public hearing.
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, identified by Docket ID No. EPA-HQ-OAR-2024-0503 by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Portal: https://www.regulations.gov</E>
                         (our preferred method). Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: a-and-r-Docket@epa.gov.</E>
                         Include Docket ID No. EPA-HQ-OAR-2024-0503 in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Environmental Protection Agency, EPA Docket Center, Air and Radiation Docket, Mail Code 28221T, 1200 Pennsylvania Avenue NW, Washington, DC 20460.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier:</E>
                         EPA Docket Center, WJC West Building, Room 3334, 1301 Constitution Avenue NW, Washington, DC 20004. The Docket Center's hours of operations are 8:30 a.m. to 4:30 p.m., Monday-Friday (except Federal Holidays).
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID No. for this rulemaking. Comments received may be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including personal information provided. For detailed instructions on sending comments and additional information on the rulemaking process, see the “Public Participation” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. For information on EPA Docket Center services, please visit us online at 
                        <E T="03">https://www.epa.gov/dockets.</E>
                    </P>
                    <P>
                        If a public hearing is requested on or before April 13, 2026, the EPA will post an update at 
                        <E T="03">https://www.epa.gov/snap.</E>
                         The EPA does not intend to publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing updates. The public hearing will be held on or around April 21, 2026. Information on the hearing including the time and URL will be posted on the EPA's Stratospheric Ozone website at 
                        <E T="03">https://www.epa.gov/snap.</E>
                         Refer to the section titled, Public Participation for additional information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about this proposed rule, contact Emily Maruyama, Chemicals, Coatings, and Products Division, Office of Clean Air Programs (Mail Code 6205A), Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460; telephone 
                        <PRTPAGE P="17177"/>
                        number: (202) 564-2809; email address: 
                        <E T="03">maruyama.emily@epa.gov.</E>
                         Notices and rulemakings under the EPA's Significant New Alternatives Policy program are available on the EPA's website at 
                        <E T="03">https://www.epa.gov/snap/snap-regulations.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Preamble acronyms and abbreviations.</E>
                     Throughout this preamble the use of “we,” “us,” or “our” is intended to refer to the EPA. We use multiple acronyms and terms in this preamble. While this list may not be exhaustive, to ease the reading of this preamble and for reference purposes, the EPA defines the following terms and acronyms here:
                </P>
                  
                <EXTRACT>
                    <FP SOURCE="FP-1">AC Air Conditioning</FP>
                    <FP SOURCE="FP-1">ANSI American National Standards Institute</FP>
                    <FP SOURCE="FP-1">ASHRAE American Society of Heating, Refrigerating and Air-Conditioning Engineers</FP>
                    <FP SOURCE="FP-1">CAA Clean Air Act</FP>
                    <FP SOURCE="FP-1">CAS Reg. No. Chemical Abstracts Service Registry Identification Number</FP>
                    <FP SOURCE="FP-1">CBI Confidential Business Information</FP>
                    <FP SOURCE="FP-1">CFC Chlorofluorocarbon</FP>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">
                        CO
                        <E T="52">2</E>
                         Carbon Dioxide
                    </FP>
                    <FP SOURCE="FP-1">CRP Cooperative Research Program</FP>
                    <FP SOURCE="FP-1">DIY Do it yourself</FP>
                    <FP SOURCE="FP-1">EEAP Environmental Effects Assessment Panel</FP>
                    <FP SOURCE="FP-1">EPA United States Environmental Protection Agency</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">GVWRv Gross Vehicle Weight Rating</FP>
                    <FP SOURCE="FP-1">HCFC Hydrochlorofluorocarbon</FP>
                    <FP SOURCE="FP-1">HD Heavy-duty</FP>
                    <FP SOURCE="FP-1">HFC Hydrofluorocarbon</FP>
                    <FP SOURCE="FP-1">HFO Hydrofluoroolefin</FP>
                    <FP SOURCE="FP-1">ICF ICF International, Inc.</FP>
                    <FP SOURCE="FP-1">LD Light-duty</FP>
                    <FP SOURCE="FP-1">LFL Lower Flammability Limit</FP>
                    <FP SOURCE="FP-1">LMDV Light- and medium-Duty Vehicle</FP>
                    <FP SOURCE="FP-1">MD Medium-duty</FP>
                    <FP SOURCE="FP-1">mJ Millijoules</FP>
                    <FP SOURCE="FP-1">MVAC Motor Vehicle Air Conditioning or Motor Vehicle Air Conditioner</FP>
                    <FP SOURCE="FP-1">MY Model Year</FP>
                    <FP SOURCE="FP-1">NAAQS National Ambient Air Quality Standard</FP>
                    <FP SOURCE="FP-1">NAICS North American Industrial Classification System</FP>
                    <FP SOURCE="FP-1">NPRM Notice of Proposed Rulemaking</FP>
                    <FP SOURCE="FP-1">ODS Ozone-Depleting Substances</FP>
                    <FP SOURCE="FP-1">OEL Occupational Exposure Limit</FP>
                    <FP SOURCE="FP-1">OEM Original Equipment Manufacturer</FP>
                    <FP SOURCE="FP-1">OMB United States Office of Management and Budget</FP>
                    <FP SOURCE="FP-1">PBI Proprietary Business Information</FP>
                    <FP SOURCE="FP-1">PMN Pre-Manufacture Notice</FP>
                    <FP SOURCE="FP-1">ppm Parts Per Million</FP>
                    <FP SOURCE="FP-1">PRA Paperwork Reduction Act</FP>
                    <FP SOURCE="FP-1">RFA Regulatory Flexibility Act</FP>
                    <FP SOURCE="FP-1">SAE SAE International, previously known as the Society of Automotive Engineers</FP>
                    <FP SOURCE="FP-1">SDS Safety Data Sheet</FP>
                    <FP SOURCE="FP-1">SIP State Implementation Plan</FP>
                    <FP SOURCE="FP-1">SNAP Significant New Alternatives Policy</FP>
                    <FP SOURCE="FP-1">SNUR Significant New Use Rule</FP>
                    <FP SOURCE="FP-1">TFA Trifluoroacetic Acid</FP>
                    <FP SOURCE="FP-1">TLV Threshold Limit Value</FP>
                    <FP SOURCE="FP-1">TWA Time Weighted Average</FP>
                    <FP SOURCE="FP-1">UMRA Unfunded Mandates Reform Act</FP>
                    <FP SOURCE="FP-1">VOC Volatile Organic Compounds</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Table of Contents </HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Executive Summary</FP>
                    <FP SOURCE="FP1-2">A. Purpose of the Regulatory Action</FP>
                    <FP SOURCE="FP1-2">B. Summary of the Major Provisions of the Regulatory Action</FP>
                    <FP SOURCE="FP-2">II. Public Participation</FP>
                    <FP SOURCE="FP1-2">A. Written Comments</FP>
                    <FP SOURCE="FP1-2">B. Participation in Virtual Public Hearing</FP>
                    <FP SOURCE="FP-2">III. General Information</FP>
                    <FP SOURCE="FP1-2">A. Does this action apply to me?</FP>
                    <FP SOURCE="FP1-2">B. What action is the Agency proposing to take?</FP>
                    <FP SOURCE="FP1-2">C. What is the Agency's authority for taking this action?</FP>
                    <FP SOURCE="FP1-2">D. What are the guiding principles of the SNAP program and what are the SNAP criteria for evaluating substitutes?</FP>
                    <FP SOURCE="FP1-2">E. Children's Environmental Health</FP>
                    <FP SOURCE="FP-2">IV. Proposed Listing for Motor Vehicle Air Conditioning</FP>
                    <FP SOURCE="FP1-2">A. What is the EPA proposing in this action?</FP>
                    <FP SOURCE="FP1-2">B. Background on MVACs in HD Pickup Trucks and HD Vans</FP>
                    <FP SOURCE="FP1-2">C. What are the ASHRAE classifications for refrigerant flammability and toxicity?</FP>
                    <FP SOURCE="FP1-2">D. What is refrigerant HFO-1234yf and how does it compare to other refrigerants in this end-use?</FP>
                    <FP SOURCE="FP1-2">E. What use conditions is the EPA proposing for HFO-1234yf for retrofit of MVACs in this end-use and what existing requirements apply to this refrigerant?</FP>
                    <FP SOURCE="FP-2">V. Clarification of Intended Scope of the 2025 NPRM and Other Clarifications</FP>
                    <FP SOURCE="FP-2">VI. On which topics is the EPA specifically requesting comment?</FP>
                    <FP SOURCE="FP-2">VII. Statutory and Executive Order Reviews</FP>
                    <FP SOURCE="FP1-2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</FP>
                    <FP SOURCE="FP1-2">B. Executive Order 14192: Unleashing Prosperity Through Deregulation</FP>
                    <FP SOURCE="FP1-2">C. Paperwork Reduction Act (PRA)</FP>
                    <FP SOURCE="FP1-2">D. Regulatory Flexibility Act (RFA)</FP>
                    <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act (UMRA)</FP>
                    <FP SOURCE="FP1-2">F. Executive Order 13132: Federalism</FP>
                    <FP SOURCE="FP1-2">G. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</FP>
                    <FP SOURCE="FP1-2">H. Executive Order 13045: Protection of Children From Environmental Health and Safety Risks</FP>
                    <FP SOURCE="FP1-2">I. Executive Order 13211: Actions That Significantly Affect Energy Supply, Distribution, or Use</FP>
                    <FP SOURCE="FP1-2">J. National Technology Transfer and Advancement Act</FP>
                    <FP SOURCE="FP-2">VIII. References</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Purpose of the Regulatory Action</HD>
                <P>
                    The EPA is proposing a new listing after our evaluation of human health and environmental information for one substitute under Clean Air Act (CAA) section 612, Significant New Alternatives Policy (SNAP) program. The Agency is proposing this new listing in the refrigeration and air conditioning (AC) sector based on the information the EPA included in the docket. This supplemental notice of proposed rulemaking, hereafter referred to as the “supplemental proposal” or “supplemental action,” would provide a new refrigerant option in specific uses, thereby increasing flexibility for industry. The EPA is also supplementing the Agency's November 10, 2025, Notice of Proposed Rulemaking (NPRM), hereafter referred to as the “2025 NPRM,” to clarify the intended scope of that proposal.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         90 FR 50766 (November 10, 2025).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Summary of the Major Provisions of the Regulatory Action</HD>
                <P>
                    This action proposes to list 2,3,3,3-tetrafluoropropene,
                    <SU>2</SU>
                    <FTREF/>
                     also known as hydrofluoroolefin (HFO)-1234yf or R-1234yf, hereafter referred to as “HFO-1234yf,” as acceptable, subject to use conditions, in the motor vehicle air conditioning (MVAC) end-use for retrofit of heavy-duty (HD) pickup trucks and complete HD vans. This proposal supplements the 2025 NPRM with respect to the proposed listings in the MVAC end-use for retrofit of HD pickup trucks and HD vans (both complete and incomplete vans). In the 2025 NPRM, the EPA proposed to list three other substitutes as acceptable, subject to use conditions, for similar end-uses. The EPA is supplementing the 2025 NPRM to clarify the intended scope of that proposal for R-444A as acceptable, subject to use conditions, in the MVAC end-use. In the 2025 NPRM, the EPA proposed a listing for R-444A in the MVAC end-use for retrofit of HD pickup trucks and HD vans (both complete and incomplete). The Agency included incomplete HD vans in error and is clarifying that we intended for this proposed listing to apply to HD pickup trucks and complete HD vans only. The scope of the proposals in the 2025 NPRM for the two other substitutes proposed in this end-use, R-456A and R-480A, are not affected by this supplemental proposal and thus remain unchanged.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         CAS Reg. No. 754-12-1.
                    </P>
                </FTNT>
                <P>
                    The proposed new listing for HFO-1234yf would appear as a change to appendix B of 40 Code of Federal Regulations (CFR) part 82, subpart G, within row 12 in the table titled “Refrigerants—Acceptable Subject to Use Conditions.” The clarification of the intended scope of the 2025 NPRM listing for R-444A in the MVAC end-use 
                    <PRTPAGE P="17178"/>
                    discussed in section V of this supplemental proposal would appear as a change to appendix B of 40 CFR part 82, subpart G, within row 10 in the same table titled “Refrigerants—Acceptable Subject to Use Conditions.” In this supplemental proposal, the EPA is not proposing changes beyond these. The specific proposed regulatory changes to appendix B are available in a document in the docket under the title “Proposed Changes to Appendix B for SNAP 27 Supplemental Proposal.” 
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         To see the adjustments to the proposed regulatory text discussed in this supplemental action in context with all the other proposed changes and listings discussed in the 2025 NPRM, see the document in the docket for this rulemaking under the title “Proposed Regulatory Text for SNAP Rule 27—Supplemental Proposal.”
                    </P>
                </FTNT>
                  
                <HD SOURCE="HD1">II. Public Participation</HD>
                <HD SOURCE="HD2">A. Written Comments</HD>
                <P>
                    Submit your comments, identified by Docket ID No. EPA-HQ-OAR-2024-0503 at 
                    <E T="03">https://www.regulations.gov</E>
                     (our preferred method), or the other methods identified in the 
                    <E T="02">ADDRESSES</E>
                     section. Once submitted, comments cannot be edited or removed from the docket. The EPA may publish any comment received in the public docket. Do not submit to the EPA's docket at 
                    <E T="03">https://www.regulations.gov</E>
                     any information you consider to be Confidential Business Information (CBI), Proprietary Business Information (PBI), or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                    <E T="03">i.e.,</E>
                     on the web, cloud, or other file sharing system). Please visit 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets</E>
                     for additional submission methods; the full EPA public comment policy; information about CBI, PBI, or multimedia submissions; and general guidance on making effective comments.
                </P>
                <HD SOURCE="HD2">B. Participation in Virtual Public Hearing</HD>
                <P>
                    The EPA may hold a virtual public hearing if the Agency receives a request to hold one. Any party requesting a public hearing must notify the contact listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section, which is Emily Maruyama at email address: 
                    <E T="03">maruyama.emily@epa.gov</E>
                     by 5 p.m. Eastern Daylight Time on or before April 13, 2026. If a virtual public hearing is held, it will take place on or around April 21, 2026 and further information will be provided on the EPA's Stratospheric Ozone website at 
                    <E T="03">https://www.epa.gov/snap.</E>
                </P>
                <P>
                    The EPA will make every effort to follow the schedule as closely as possible on the day of the hearing; however, please plan for the hearings to run either ahead of schedule or behind schedule. Each commenter will have three to five minutes to provide oral testimony. The EPA encourages commenters to provide a copy of their oral testimony electronically by emailing it to 
                    <E T="03">maruyama.emily@epa.gov.</E>
                     The EPA also recommends submitting the text of your oral comments as written comments to the rulemaking docket EPA-HQ-OAR-2024-0503. Written statements and supporting information submitted during the comment period will be considered with the same weight as oral comments and supporting information presented at the public hearing. The EPA may ask clarifying questions during the oral presentations but will not respond to the presentations at that time.
                </P>
                <P>
                    Please note that any updates made to any aspect of the hearing will be posted online at 
                    <E T="03">https://www.epa.gov/snap.</E>
                     While the EPA expects the hearing to go forward as set forth above, please monitor our website or contact Emily Maruyama, 202-564-2809, 
                    <E T="03">maruyama.emily@epa.gov</E>
                     to determine if there are any updates. The EPA does not intend to publish a document in the 
                    <E T="04">Federal Register</E>
                     (FR) announcing updates.
                </P>
                <HD SOURCE="HD1">III. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>The following list identifies regulated entities that may be affected by this rulemaking and their respective North American Industrial Classification System (NAICS) codes:</P>
                <P>• All Other Basic Organic Chemical Manufacturing (325199).</P>
                <P>• Motor Vehicle Manufacturing (3361).</P>
                <P>• Motor Vehicle Parts Manufacturing (3363).</P>
                <P>• Recyclable Material Merchant Wholesalers (423930).</P>
                <P>• General Automotive Repair (811111).</P>
                <P>
                    This list is not intended to be exhaustive, but rather to provide a guide for readers regarding entities likely to be affected by this action. To determine whether your facility, company, business, or organization could be affected by this action, you should carefully examine the regulations at 40 CFR part 82, subpart G, and the proposed revisions. If you have questions regarding the applicability of this action to a particular entity, consult the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <HD SOURCE="HD2">B. What action is the Agency proposing to take?</HD>
                <P>The EPA is proposing to list HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans. The EPA is also supplementing the 2025 NPRM to clarify the intended scope of that proposal. Specifically, in the 2025 NPRM, the EPA proposed to list R-444A as acceptable, subject to use conditions, in the MVAC end-use for retrofit of complete and incomplete HD vans. This supplemental action is clarifying that the EPA intended for this proposed listing to apply only to complete HD vans.</P>
                <HD SOURCE="HD2">C. What is the Agency's authority for taking this action?</HD>
                <P>This proposal supplements the 2025 NPRM. See the 2025 NPRM for a full discussion of the Agency's authority for taking this action. </P>
                <HD SOURCE="HD2">D. What are the guiding principles of the SNAP program and what are the SNAP criteria for evaluating substitutes?</HD>
                <P>This proposal supplements the 2025 NPRM. See the 2025 NPRM for a full discussion of the guiding principles of the SNAP program and the SNAP criteria for evaluating substitutes.</P>
                <HD SOURCE="HD2">E. Children's Environmental Health</HD>
                <P>
                    This action is subject to the EPA's Policy on Children's Health (
                    <E T="03">https://www.epa.gov/children/childrens-health-policy-and-plan</E>
                    ) because the rule has considerations for human health. Accordingly, we have evaluated the environmental health effects of HFO-1234yf to general population exposure.
                </P>
                <P>
                    In summary, the risk screen for the use of HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans found that this substitute is not expected to cause a significant risk to human health in the general population when manufactured for use and used as a refrigerant in HD pickup truck and complete HD van AC systems. Additionally, the EPA found that the toxicity risks of using HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans are comparable to or lower than that of other available substitutes in the same end-use. The risk screen found that HFO-1234yf can be used without exceeding the recommended 
                    <PRTPAGE P="17179"/>
                    occupational exposure limit (OEL) of 500 ppm (8-hr OEL); thus, the toxicity risks of this refrigerant are comparable to those of other acceptable substitutes in MVACs, which also are used without exceeding their OELs. The risk screen also found that HFO-1234yf in HD pickup trucks and complete HD vans does not pose a significant risk of end-use exposure, provided systems are installed in appropriate spaces with proper engineering controls, emergency response plans, and according to guidelines from the manufacturer, standards, and the safety data sheet. While the EPA has not conducted a separate analysis of risks to infants and children associated with this rule, the rule does contain use conditions that would reduce exposure risks to the general population, with the reduction of exposure being most important to the most sensitive individuals.
                </P>
                <P>The results of this evaluation are contained in section IV.D. of this preamble and in the risk screen titled “Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Heavy-Duty Pickup Trucks and Complete Heavy-Duty Vans) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf).” A copy of this document is available in the public docket for this action at Docket ID No. EPA-HQ-OAR-2024-0503.</P>
                <P>This action is consistent with the EPA's Policy on Children Health because it provides an additional retrofit option and would not pose additional adverse effects to human health when used in accordance with existing and proposed requirements and as intended by the submitter.</P>
                <P>
                    Furthermore, Executive Order 13045 (“
                    <E T="03">Protection of Children from Environmental Health Risks and Safety Risks”</E>
                    ) applies to this action. Information on how this action is subject to this Executive Order is available in a section of this preamble under the same name.
                </P>
                <HD SOURCE="HD1">IV. Proposed Listing for Motor Vehicle Air Conditioning</HD>
                <HD SOURCE="HD2">A. What is the EPA proposing in this action?  </HD>
                <P>The EPA is proposing to list HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans. In the 2025 NPRM, the EPA proposed to list three substitutes, R-444A, R-456A, and R-480A as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete and incomplete HD vans. During the public comment period, the EPA received comments and feedback from stakeholders highlighting that the proposal did not include a listing of HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and HD vans. The EPA reviewed these comments and agrees that the Agency should have included all four refrigerants for this end-use consistent with other MVAC listings in the 2025 NPRM and is issuing this supplemental proposal to add this listing. To support this listing, the Agency has provided in the docket the risk screen for HFO-1234yf for this end-use and proposes to find HFO-1234yf acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans.</P>
                <P>The 2025 NPRM proposed to list HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of light- and medium-duty vehicles (LMDVs). HFO-1234yf has not otherwise been listed as acceptable for other MVAC retrofit applications. The proposed listing for HFO-1234yf in this supplemental action would allow for retrofits of chlorofluorocarbon (CFC)-12 MVACs as well as for retrofits of MVACs using any of the refrigerants the SNAP program lists as acceptable or acceptable, subject to use conditions, in this end-use.</P>
                <HD SOURCE="HD2">B. Background on MVACs in HD Pickup Trucks and HD Vans</HD>
                <P>
                    The SNAP program uses the term MVAC broadly to describe a wide variety of non-stationary AC systems that provide passenger comfort cooling for LMDVs, HD vehicles, nonroad vehicles, buses, and trains. The SNAP MVAC end-use includes systems that may also be subject to other CAA regulatory programs, including for example, where those systems fit within the regulatory definition of “MVAC” under 40 CFR 82.32,
                    <SU>4</SU>
                    <FTREF/>
                     or the definition of an “MVAC-like appliance” 
                    <SU>5</SU>
                    <FTREF/>
                     or “appliance” under 40 CFR 82.152, or both.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         As defined in 40 CFR 82.32, Motor vehicle air conditioners mean mechanical vapor compression refrigeration equipment used to cool the driver's or passenger's compartment of any motor vehicle. This definition is not intended to encompass the hermetically sealed refrigeration systems used on motor vehicles for refrigerated cargo and the air conditioning systems on passenger buses using hydrochlorofluorocarbon (HCFC)-22 refrigerant. 
                        <E T="03">See also</E>
                         40 CFR 82.152 (defining MVAC to mean “any appliance that is a motor vehicle air conditioner as defined in subpart B of 40 CFR part 82”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         As defined in 40 CFR 82.152 MVAC-like appliance means a mechanical vapor compression, open-drive compressor appliance with a full charge of 20 pounds or less of refrigerant used to cool the driver's or passenger's compartment of off-road vehicles or equipment. This includes, but is not limited to, the air-conditioning equipment found on agricultural or construction vehicles. This definition is not intended to cover appliances using R-22 refrigerant.
                    </P>
                </FTNT>
                <P>
                    To appropriately evaluate human health and environmental risks, the SNAP program considers the type of vehicle in which the proposed alternative would be used. The vehicle types within the MVAC end-use addressed in this supplemental proposal to list HFO-1234yf as acceptable, subject to use conditions, include limited types of vehicles, specifically, HD pickup trucks and complete HD vans (
                    <E T="03">e.g.,</E>
                     large passenger vehicles such as large pickup trucks or vans). In this supplemental action, the EPA is not making any changes to the proposed MVAC acceptability listings for HFO-1234yf included in the 2025 NPRM (
                    <E T="03">e.g.,</E>
                     retrofit LMDVs, new HD on-highway vehicles, and new buses) and is not reopening the comment period for those proposed listings.
                </P>
                <P>HD vehicles are often subdivided by vehicle weight classifications, as defined by the vehicle's gross vehicle weight rating (GVWR), which is a measure of the combined curb (empty) weight and cargo carrying capacity of the truck. HD vehicles have GVWRs above 8,500 pounds. HD pickup trucks and HD vans are Class 2b and 3 vehicles with GVWRs between 8,501 and 14,000 pounds.</P>
                <P>
                    The types of vehicles for which the EPA is proposing to list HFO-1234yf for retrofit use as acceptable, subject to use conditions, in this supplemental action, are in many ways more similar to light-duty (LD) or medium-duty (MD) vehicles than they are to the HD vehicles with a higher GVWR classification. These vehicle types are similar to LD vehicles technologically and most are manufactured by companies with major LD markets in the United States and in a similar manner to LD vehicles.
                    <SU>6</SU>
                    <FTREF/>
                     In many cases, these types of HD vehicles are versions of their LD counterparts.
                    <SU>7</SU>
                    <FTREF/>
                     The primary difference between HD pickup trucks and HD vans and their LD counterpart vehicles is that HD pickup trucks and HD vans are occupational or work vehicles that are designed for much higher towing and payload capabilities than are LD pickup trucks and LD vans. HD pickup trucks and HD vans share many design similarities with their 
                    <PRTPAGE P="17180"/>
                    lighter counterparts. For example, MVAC systems in HD pickup trucks and HD vans generally have a similar configuration and use similar components as their lighter counterparts. Differences may exist in terms of cooling capacity (
                    <E T="03">e.g.,</E>
                     based on cabin volume), system layout (
                    <E T="03">e.g.,</E>
                     the number of evaporators), and the durability requirements due to longer truck life.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         This is more broadly true for HD pickup trucks than HD vans because every manufacturer of HD pickup trucks also makes LD pickup trucks, while only some HD van manufacturers also make LD vans (80 FR 40148; July 13, 2015).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         ICF. (2026a). Technical Support Document for Motor Vehicle Air Conditioning in Limited Heavy-Duty Applications.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         ICF. (2026a).
                    </P>
                </FTNT>
                <P>
                    All types of HD vehicles can be sold as “complete” or “incomplete” vehicles.
                    <SU>9</SU>
                    <FTREF/>
                     Approximately 90 percent of HD pickup trucks and HD vans are 
                    <FR>3/4</FR>
                    -ton and 1-ton pickup trucks, 15-passenger vans, and large work vans that are sold by vehicle manufacturers as complete vehicles.
                    <SU>10</SU>
                    <FTREF/>
                     Complete vehicles are sold by vehicle manufacturers to end users with no secondary manufacturer making substantial modifications prior to registration and use. Incomplete vehicles are sold by vehicle manufacturers to secondary manufacturers without the primary load-carrying device or container attached.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         76 FR 57259-60 (September 15, 2011).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         ICF. (2026a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Incomplete HD vehicles can also be sold to and modified by tertiary or subsequent manufacturers. For the purposes of this supplemental proposal, the discussion of modifications made by secondary manufacturers also applies to modifications made by tertiary or subsequent manufacturers.
                    </P>
                </FTNT>
                <P>Examples of modifications by secondary manufacturers to HD pickup trucks are installing a flatbed platform or tool storage bins. The EPA is not aware of any equipment added by a secondary manufacturer to an incomplete HD pickup truck that would result in a secondary manufacturer modifying or adjusting the already installed MVAC system to provide cooling capacity.</P>
                <P>Incomplete HD vans are typically sold with no enclosed cabin area behind the driver's seat, and secondary manufacturer modifications could include applications such as conversion to ambulances, shuttle vans, and motor homes. Incomplete HD vans may include original equipment manufacturer (OEM) MVACs that are identical to those installed in the complete HD van on which the incomplete model is based. In some cases, these systems are designed solely for cooling the front driver area, while other systems are manufactured by the OEM with additional capability to provide cooling behind the driver area to the cabin after modification.</P>
                <P>
                    MVACs across all vehicle types are typically charged during vehicle manufacture. Incomplete HD vehicles are modified by secondary manufacturers and that modification may or may not involve the installation of additional AC or refrigeration equipment.
                    <SU>12</SU>
                    <FTREF/>
                     While some secondary manufacturers use the OEM MVAC system with no modification to the contained refrigerant system (hoses, connections, heat exchangers, compressor, etc.), this is not a uniform practice. At the time of this supplemental action, the EPA does not have sufficient information on the potential for modifications to OEM-installed MVAC systems of incomplete HD vans by secondary manufacturers and the impact of those modifications on the safe use of HFO-1234yf. For this reason, the EPA is not proposing to find HFO-1234yf acceptable, subject to use conditions, in the MVAC end-use for retrofit of incomplete HD vans in this supplemental proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         For example, AC for the rear compartment of an ambulance or shuttle van.
                    </P>
                </FTNT>
                <P>
                    Historically, the class I ozone-depleting substances (ODS) refrigerant CFC-12 was the primary refrigerant used in MVACs for passenger vehicles and trucks. In the initial 1994 SNAP rulemaking, hydrofluorocarbon (HFC)-134a, amongst other substitutes, was listed as acceptable for use in new and retrofit MVACs, including HD pickup trucks and HD vans.
                    <SU>13</SU>
                    <FTREF/>
                     Since then, the EPA has listed additional alternatives for MVACs as acceptable, subject to use conditions, for use in new HD pickup trucks and complete HD vans, including HFO-1234yf, HFC-152a, and carbon dioxide (R-744).
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         59 FR 13044 (March 18, 1994).
                    </P>
                </FTNT>
                <P>
                    The EPA previously listed HFO-1234yf as acceptable, subject to use conditions, in newly manufactured HD pickup trucks and complete HD vans.
                    <SU>14</SU>
                    <FTREF/>
                     As of model year (MY) 2026, both HFO-1234yf and HFC-134a are used in new HD pickup trucks that are manufactured and imported in the United States. New complete HD vans continue to primarily use HFC-134a.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         81 FR 86778 (December 1, 2016).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         ICF. (2026a).
                    </P>
                </FTNT>
                <P>The EPA considers other relevant regulatory programs when developing listing decisions and use conditions. For example, CAA section 609 and implementing regulations in 40 CFR part 82, subpart B address the repair and servicing of MVACs as well as technician training and certification. CAA section 608 and implementing regulations in 40 CFR part 82, subpart F restrict the sale of refrigerant and address disposal and other activities involving MVACs that are not regulated under CAA section 609.</P>
                <P>By considering the regulatory requirements that already exist, consistent with the SNAP program's guiding principles, the EPA has been able to limit the use conditions the Agency would have otherwise considered, particularly for retrofits. See the 2025 NPRM for a full discussion of the EPA's regulatory approach under CAA sections 609 and 612 regarding the repair and servicing of MVACs and recovery, recycling, and recharging equipment.</P>
                <HD SOURCE="HD2">C. What are the ASHRAE classifications for refrigerant flammability and toxicity?</HD>
                <P>
                    American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) Standard 34-2024 assigns a safety group for each refrigerant, which consists of two to three alphanumeric characters (
                    <E T="03">e.g.,</E>
                     A2L or B1).
                    <SU>16</SU>
                    <FTREF/>
                     The initial character indicates the toxicity, and the numeral, with or without suffix letter, denotes the flammability. HFO-1234yf is in the A2L Safety Group. ASHRAE classifies Class A refrigerants as refrigerants for which toxicity has not been identified at concentrations less than or equal to 400 parts per million (ppm) by volume, based on data used to determine threshold limit value-time-weighted average (TLV-TWA) or consistent indices. Throughout this document, refrigerants in the flammability class of “2L” are referred to as lower flammability refrigerants. See the 2025 NPRM for a full discussion of the ASHRAE classifications for refrigerant flammability and toxicity.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         ASHRAE. (2024). ANSI/ASHRAE Standard 34-2024: Designation and Safety Classification of Refrigerants.
                    </P>
                </FTNT>
                  
                <HD SOURCE="HD2">D. What is refrigerant HFO-1234yf and how does it compare to other refrigerants in this end-use?</HD>
                <P>The EPA is proposing to list HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans.</P>
                <P>
                    The redacted submission and supporting documentation for this proposed refrigerant are in the docket.
                    <SU>17</SU>
                    <FTREF/>
                     The EPA performed a risk screening assessment to examine the human health and environmental risks of this substitute, also available in the docket.
                    <FTREF/>
                    <SU>18</SU>
                      
                    <PRTPAGE P="17181"/>
                    The EPA notes that the environmental, flammability, and toxicity information in this section is similar to the information provided in the 2025 NPRM related to the proposed listing of HFO-1234yf in the MVAC end-use for retrofit of LMDVs. As mentioned in the 2025 NPRM, the environmental, flammability, and toxicity information about this proposed substitute does not differ between LMDV MVACs and HD pickup truck and complete HD van MVACs.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Docket ID No. EPA-HQ-OAR-2024-0503.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         ICF. (2026b). Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Heavy-Duty Pickup Trucks and Complete Heavy-Duty Vans) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf). 
                        <E T="03">See</E>
                         Docket ID No. EPA-HQ-OAR-2024-0503.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Environmental information:</E>
                     The specific atmospheric effects values can be found in the risk screen developed for HFO-1234yf for the proposed listing in this supplemental action. These were determined consistent with the source information noted in section III.D. of the 2025 NPRM.
                </P>
                <P>
                    HFO-1234yf is excluded from the EPA's regulatory definition of volatile organic compounds (VOCs), which is used for addressing the development of state implementation plans (SIPs) to attain and maintain the National Ambient Air Quality Standard (NAAQS).
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         40 CFR 51.100(s).
                    </P>
                </FTNT>
                <P>
                    HFO-1234yf can break down into trifluoroacetic acid (TFA) in the atmosphere. HFO-1234yf is almost completely transformed into TFA.
                    <SU>20</SU>
                    <FTREF/>
                     For more information on TFA, see the response to comments section of SNAP Rule 26.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         EEAP. (2023). Environmental Effects of Stratospheric Ozone Depletion, UV Radiation, and Interactions with Climate Change. 2022 Assessment Report. UNEP, Environmental Effects Assessment Panel. 
                        <E T="03">https://ozone.unep.org/system/files/documents/EEAP-2022-Assessment-Report-May2023.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         88 FR 50457-8 (June 13, 2024).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Flammability information:</E>
                     HFO-1234yf is a lower flammability refrigerant (ASHRAE flammability classification 2L). HFO-1234yf may pose a greater flammability risk than nonflammable substitutes in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans. The flammability risk, determined by the likelihood of exceeding the lower flammability limit (LFL), is evaluated in the risk screen referenced in this section. The EPA is proposing to determine that HFO-1234yf may be used safely since flammability risk can be mitigated by use consistent with the proposed labeling requirements in appendix D of 40 CFR part 82, subpart G, recommendations in the manufacturers' safety data sheet (SDS), and other safety precautions common in the refrigeration and AC industry. The flammability characteristics of HFO-1234yf make the risk of ignition low. HFO-1234yf requires an open flame to ignite, such as a match or lighter, because of its relatively high minimum ignition energy of greater than 5,000 millijoules (mJ).
                    <SU>22</SU>
                    <FTREF/>
                     HFO-1234yf has an LFL of 62,000 ppm,
                    <SU>23</SU>
                    <FTREF/>
                     and has a low burning velocity 
                    <SU>24</SU>
                    <FTREF/>
                     compared to refrigerants with flammability classification of 2 such as HFC-152a 
                    <SU>25</SU>
                    <FTREF/>
                     or with flammability classification of 3 such as hydrocarbon refrigerants.
                    <SU>26</SU>
                    <FTREF/>
                     As a result of these flammability characteristics, HFO-1234yf is difficult to ignite, and is generally unable to propagate a flame once ignited (
                    <E T="03">i.e.,</E>
                     flames resulting from HFO-1234yf put themselves out).
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Minor, B. et al. (2009). (111g) Flammability Characteristics of Low GWP Refrigerant HFO-1234yf. 
                        <E T="03">AIChE 2009 Spring Meeting &amp; 5th Global Congress on Process Safety. https://proceedings.aiche.org/conferences/aiche-spring-meeting-and-global-congress-on-process-safety/2009/proceeding/paper/111g-flammability-characteristics-low-gwp-refrigerant-hfo-1234yf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">Manufacturer's Safety Data Sheet for HFO-1234yf.</E>
                         Honeywell (May 23, 2019). 
                        <E T="03">See also</E>
                         Minor, B. et al. (2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         A2L refrigerants have a burning velocity of less than 0.1 meters/second (m/s), per International Standards Organization 817 and ASHRAE 34-2024. HFO-1234yf has a burning velocity of 0.015m/s, see Minor, B. et al. (2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         The burning velocity of HFC-152a is measured at approximately 0.236 m/s. Takizawa, K. et al. (2005). Burning velocity measurement of fluorinated compounds by the spherical-vessel method, 
                        <E T="03">Combustion and Flame,</E>
                         Volume 141, Issue 3, Pages 298-307: 
                        <E T="03">https://doi.org/10.1016/j.combustflame.2005.01.009.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The burning velocity of R-290 is at least 0.4 m/s, depending on temperature and pressure. Metghalchi, M. &amp; Keck, J.C. (1980). Laminar Burning Velocity of Propane-Air Mixtures at High Temperature and Pressure. 
                        <E T="03">Combustion And Flame</E>
                         38: 143-154 
                        <E T="03">https://james-keck-memorial-collection.unibs.it/JCKeck-papers/MetghalchiKeck-CombustionFlame-38-143-1980.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    Consistent with the other proposed listings in the 2025 NPRM, under this supplemental action, HFO-1234yf could be used to retrofit MVACs originally designed for an A1 refrigerant. The EPA considered if this could create additional flammability risk distinct from its use in a new MVAC that is specifically designed with mitigation measures to use a flammable refrigerant. The original submission for HFO-1234yf in new vehicles included analyses that evaluated the flammability and toxicity risks of HFO-1234yf in MVACs that were originally designed for HFC-134a. These analyses consist of reports published in 2008, 2009, and 2013 from the SAE International, previously known as the Society of Automotive Engineers (SAE), Cooperative Research Program (CRP). The vehicles in these analyses did not feature any design changes to address potential flammability. In this way, MVACs used in the original analyses were analogous to vehicles that would be retrofit under this supplemental proposal, because they could be originally designed for an A1 refrigerant.
                    <SU>27</SU>
                    <FTREF/>
                     The 2008 report found that the increased flammability risk of HFO-1234yf in a vehicle designed for use with HFC-134a is well below those commonly accepted by the general public.
                    <SU>28</SU>
                    <FTREF/>
                     A revised 2009 report found that the risks of HFO-1234yf were low overall, and somewhat less than the toxicity risks posed by R-744.
                    <SU>29</SU>
                    <FTREF/>
                     The submitter of HFO-1234yf provided these analyses to the EPA to support the Agency's original consideration of HFO-1234yf in new vehicles, and the Agency based its listing of acceptability in part on the findings of these analyses. The EPA concluded that the risks of HFO-1234yf are comparable to or less than the risks from other available or potentially available alternatives in this end-use that the Agency had already listed or proposed as acceptable (
                    <E T="03">e.g.,</E>
                     HFC-152a, HFC-134a, and R-744).
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         Gradient Corporation. (2008). Risk Assessment for Alternative Refrigerant HFO-1234yf. (Phase I) Prepared for the Society of Automotive Engineers (SAE) Cooperative Research Project 150.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Gradient Corporation. (2008). Risk Assessment for Alternative Refrigerant HFO-1234yf. Confidential report prepared for SAE International Cooperative Research Program 1234.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         Gradient Corporation. (2009). Risk Assessment for Alternative Refrigerants HFO-1234yf and R-744 (CO
                        <E T="52">2</E>
                        ). Confidential report prepared for SAE International Cooperative Research Program 1234.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See</E>
                         76 FR 17491 (March 29, 2011).
                    </P>
                </FTNT>
                <P>
                    SAE revised its assessment of HFO-1234yf and released a supplemental report in 2013 that contained two new fault tree analyses that included additional “worst-case scenarios.” 
                    <SU>31</SU>
                    <FTREF/>
                     The report revised the probability of a vehicle fire due to ignition of HFO-1234yf in a system featuring no design changes compared to an HFC-134a system to about 3 × 10
                    <E T="51">−12</E>
                     events per hour of vehicle operation.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         Gradient Corporation. (2013a). Additional Risk Assessment of Alternative Refrigerant R-1234yf. Confidential report prepared for SAE International Cooperative Research Program 1234-4.
                    </P>
                </FTNT>
                <P>
                    The submitter of HFO-1234yf in the MVAC end-use for retrofit of LMDVs and HD pickup trucks and complete HD vans provided an updated fault tree analysis that evaluated the additional risk associated with use of HFO-1234yf specifically in retrofit applications and the EPA considered this new analysis in our review of HFO-1234yf.
                    <SU>32</SU>
                    <FTREF/>
                     The analysis only considered scenarios that increased the flammability risk in a retrofit (such as increased risk of mechanical fan failure and electrical fires and less consistent presence and deployment of airbags) and did not 
                    <PRTPAGE P="17182"/>
                    consider scenarios that reduced the flammability risk in a retrofit (such as the larger cabin size in older vehicles that would be retrofit). The overall estimated risk was about 8 × 10
                    <E T="51">−12</E>
                     events per operating hour, which is similar to the risk of vehicle fire due to HFO-1234yf ignition in new MVAC equipment (5 × 10
                    <E T="51">−12</E>
                     events per operating hour).
                    <SU>33</SU>
                    <FTREF/>
                     The actual increased risk is likely lower than this, as the evaluation only considered circumstances that would increase the probability of a vehicle fire and did not consider circumstances that would reduce the probability.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         Gradient Corporation. (2023a). Retrofit Analysis Letter. Prepared for Honeywell International.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Gradient Corporation. (2009).
                    </P>
                </FTNT>
                <P>
                    The MVAC systems, vehicle designs, and the potential for exposure for the HD vehicle types for which the EPA is proposing HFO-1234yf for retrofit use as acceptable, subject to use conditions, in this supplemental action are identical or very similar to those of LD vehicles.
                    <SU>34</SU>
                    <FTREF/>
                     In 2016, the EPA evaluated how the risks of using HFO-1234yf in new HD pickup trucks and complete HD vans compare to the risks of using HFO-1234yf in new LD vehicles.
                    <SU>35</SU>
                    <FTREF/>
                     The EPA presented information on the highest refrigerant charge to passenger compartment volume ratios for different vehicle types and the highest ratio for all HD pickup truck and HD van vehicle types was 410 g/m
                    <SU>3</SU>
                     in HD pickup trucks, which was less than the maximum ratio identified in the analysis for HFO-1234yf in LD vehicles in two seaters, which was 641 g/m
                    <SU>3</SU>
                    .
                    <SU>36</SU>
                    <FTREF/>
                     The EPA concluded that the available assessments on the use of HFO-1234yf in LD vehicles were sufficiently conservative to account for all possible flammability risks from the use of HFO-1234yf in HD pickup trucks and complete HD vans.
                    <SU>37</SU>
                    <FTREF/>
                     Consistent with the approach taken in SNAP Rule 21 when the EPA listed HFO-1234yf in new HD pickup trucks and complete HD vans and relied on analysis for the use of HFO-1234yf in LD vehicles, the EPA proposes to find it appropriate to rely on the same analysis included in this section related to the use of HFO-1234yf in LD vehicle types.
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         81 FR 86778 (Dec. 1, 2016).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         ICF. (2016b). Technical Support Document for Acceptability Listing of HFO-1234yf for Motor Vehicle Air Conditioning in Limited Heavy-Duty Applications.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         ICF. (2016b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         81 FR 22810 (April 16, 2016).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See</E>
                         81 FR 86778 (December 1, 2016).
                    </P>
                </FTNT>
                  
                <P>
                    The EPA conducted a risk screen in 2026 for HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans to support the proposed listing in this supplemental action. The risk screen found that concentrations of HFO-1234yf did exceed the LFL in the passenger compartment of a HD pickup truck under the modeled worst-case scenario. For the HD pickup truck and HD van vehicle types evaluated in this risk screen, the highest refrigerant charge to passenger compartment ratio was 390 g/m
                    <SU>3</SU>
                     in HD pickup trucks.
                    <SU>39</SU>
                    <FTREF/>
                     This ratio is substantially less than the maximum ratio identified for many vehicle types mentioned in the risk screen for HFO-1234yf use in retrofit LMDVs including two seaters (640.75 g/m
                    <SU>3</SU>
                    ), small pickup trucks (633.27 g/m
                    <SU>3</SU>
                    ), sport utility vehicles (414.96 g/m
                    <SU>3</SU>
                    ), and standard pickup trucks (397.84 g/m
                    <SU>3</SU>
                    ).
                    <SU>40</SU>
                    <FTREF/>
                     The lower ratio indicates a relatively lower risk.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         ICF. (2026b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         ICF. (2025k). Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Light-Duty and Medium-Duty Vehicles) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf).
                    </P>
                </FTNT>
                <P>
                    As discussed in the 2025 NPRM, the risk screen for HFO-1234yf use for retrofit of LMDVs found that concentrations of HFO-1234yf did exceed the LFL in the passenger compartment under certain worst-case scenarios but remained well below the LFL in more realistic industry consortium field testing. For example, using a simple box model, combining the highest ratio of refrigerant charge to observed passenger compartment size with a catastrophic release of 60 percent of the charge in 60 seconds, resulted in a maximum instantaneous charge of 172,000 ppm, compared to an LFL of 62,000 ppm. However, analysis using the more accurate technique of computational fluid dynamics modeling found the instantaneous concentration of HFO-1234yf to vary from 65,000 ppm to 34,000 ppm. The industry consortium field testing found a maximum instantaneous concentration of HFO-1234yf of 29,774 ppm when a vehicle's full charge was released.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         ICF. (2025k).
                    </P>
                </FTNT>
                <P>
                    The EPA's original 2009 risk analysis of HFO-1234yf for use in new LMDVs also identified scenarios in which concentrations exceeded the LFL.
                    <SU>42</SU>
                    <FTREF/>
                     The EPA listed HFO-1234yf as acceptable, subject to use conditions, in new LMDVs leveraging this risk analysis. In the EPA's original listing, the Agency stated that it found that the use of HFO-1234yf in the MVAC end-use for new passenger vehicle and LD trucks, subject to the use conditions adopted in that listing, does not present a greater overall risk to human health and the environment compared to the currently approved MVAC alternatives or as compared to R-744.
                    <SU>43</SU>
                    <FTREF/>
                     The EPA has also subsequently listed R-744 as acceptable, subject to use conditions, in new LMDVs. Finally, HFO-1234yf in new LMDVs has been widely adopted since being listed in 2012. In MY2023, the share of new LMDVs sold in the United States with HFO-1234yf reached 97 percent.
                    <SU>44</SU>
                    <FTREF/>
                     HFO-1234yf has also been adopted for use in new HD pickup trucks and complete HD vans. Even with its broad use, the EPA is not aware of any real-world instances in which HFO-1234yf has ignited and caused a vehicle fire, which further augments the record for this refrigerant.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         ICF. (2009). Risk Screen on Substitutes for CFC-12 in Motor Vehicle Air Conditioning: Substitute: HFO-1234yf.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See</E>
                         SNAP Rule 16, 76 FR 17488 (March 29, 2011).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         U.S. Environmental Protection Agency. (2024). EPA Automotive Trends Report: Greenhouse Gas Emissions, Fuel Economy, and Technology since 1975: 
                        <E T="03">https://nepis.epa.gov/Exe/ZyPDF.cgi?Dockey=P101CUU6.pdf.</E>
                    </P>
                </FTNT>
                <P>SAE J1660 currently provides guidance on how to retrofit a vehicle originally charged with CFC-12 to HFC-134a. The EPA anticipates that SAE would develop an analogous standard or revise this standard for retrofitting vehicles using newer refrigerants, including HFO-1234yf. Following such standards may further reduce the flammability risk associated with retrofitting MVACs, which is already expected to be extremely small in magnitude.</P>
                <P>Given the findings of the evaluation materials available in the docket, that the environmental, flammability, and toxicity information about HFO-1234yf does not differ between MVAC end-use for LMDVs and HD pickup trucks and complete HD vans, that the MVACs used in the original analysis for HFO-1234yf in new vehicles were analogous to vehicles that would be retrofit, and the widespread adoption of HFO-1234yf without documented flammability issues, the EPA is proposing that HFO-1234yf may be safely used in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans.</P>
                <P>
                    <E T="03">Toxicity information:</E>
                     Toxicity risk, determined by the likelihood of exceeding the exposure limits in these end-uses, are evaluated in the previously referenced risk screen. HFO-1234yf is a lower toxicity (ASHRAE toxicity group A) refrigerant. ASHRAE has adopted an OEL for this refrigerant of 500 ppm. The toxicity risks of using HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans are comparable to or lower than that of other available substitutes in the same end-use, 
                    <PRTPAGE P="17183"/>
                    including HFC-134a.
                    <SU>45</SU>
                    <FTREF/>
                     Toxicity risks of the proposed refrigerant can be mitigated by use consistent with applicable industry safety standards, recommendations in the manufacturers' SDS, and other safety precautions common in the refrigeration and AC industry.
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">See</E>
                         previous listing decisions for information regarding the toxicity of other available alternatives. (
                        <E T="03">https://www.epa.gov/snap/substitutes-motor-vehicle-air-conditioning</E>
                        ).
                    </P>
                </FTNT>
                <P>HFO-1234yf is subject to a significant new use rule (SNUR) under 40 CFR 721.10182(a). Significant new uses under this requirement include: use other than as a refrigerant: in MVAC systems in new passenger cars and vehicles (as defined in 40 CFR 82.32(c) and (d)), in stationary and transport refrigeration, or in stationary AC, commercial use other than in passenger cars and vehicles in which the original charging of MVAC systems with the pre-manufacture notice (PMN) substance was done by the motor vehicle original equipment manufacturer (OEM), in stationary and transport refrigeration, or in stationary AC., and use in consumer products other than products used to recharge the MVAC systems in passenger cars and vehicles in which the original charging of MVAC systems with the PMN substance was done by the motor vehicle OEM.</P>
                <P>Use in all MVAC end-uses, except for when originally charged with HFO-1234yf, would fall under (B) or (C) as commercial or consumer use to recharge an MVAC in which the original charging of the MVAC was with a substance other than HFO-1234yf. The EPA considers retrofitting a vehicle to use HFO-1234yf that was not originally charged by the OEM with HFO-1234yf to be a significant new use of HFO-1234yf under this SNUR. Significant new uses require the chemical producer to submit a significant new use notice to the EPA for review of a substance before introducing the substance into interstate commerce in the significant new use.</P>
                <P>
                    <E T="03">Comparison to other substitutes in these end-uses:</E>
                     The Agency understands that this substitute will be marketed as a retrofit option for different refrigerants, including HFC-134a. HFC-134a is the only available refrigerant listed as acceptable for retrofit of MVACs in HD pickup trucks and complete HD vans.
                </P>
                <P>
                    The specific atmospheric effects values can be found in the individual risk screen for HFO-1234yf. These were determined consistent with the source information noted in section III.D. of the 2025 NPRM. The atmospheric effects for HFO-1234yf are overall better than or comparable to many of the substitutes currently listed as acceptable in this end-use, such as HFC-134a. The EPA acknowledges that the atmospheric effects of HFO-1234yf are relatively lower than the three blends, R-444A, R-456A, and R-480A, that were proposed as acceptable, subject use conditions, in the MVAC end-use for retrofit of HD pickup trucks and HD vans in the 2025 NPRM. The EPA's analysis found that the effects on human health and the environment associated with retrofitting HD pickup trucks and complete HD vans with HFO-1234yf are comparable to the other alternatives proposed for this use in the 2025 NPRM, and lower than that of HFC-134a.
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         The EPA is aware that the submitter of HFO-1234yf is likely to market this substitute to retrofit MVACs originally charged with HFC-134a.
                    </P>
                </FTNT>
                <P>
                    The EPA's risk screen for HFO-1234yf in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans found that this substitute can be used without exceeding the recommended OEL of 500 ppm (8-hr OEL); thus, the toxicity risks of this refrigerant are comparable to those of other acceptable substitutes in MVACs, which also are used without exceeding their OELs.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         ICF. (2026b).
                    </P>
                </FTNT>
                  
                <P>
                    The flammability of HFO-1234yf may be greater than that of other available substitutes in the same end-use that have an ASHRAE flammability classification of 1. The EPA's analysis of the flammability risks of HFO-1234yf found that when used in accordance with the proposed use conditions, this A2L refrigerant may be safely used in this end-use without presenting additional adverse effects to human health and the environment than other alternatives. HFO-1234yf was listed as acceptable, subject to use conditions, in MVAC end-use for new HD pickup trucks and complete HD vans in 2016. Since then, no reports of harm or incidences of fire were recorded. We note that flammability risk can be minimized by use consistent with applicable industry safety standards as well as recommendations in the manufacturers' SDS and other safety precautions common in the MVAC industry and any difference in flammability can be addressed by the existing labeling requirements in appendix D of 40 CFR part 82, subpart G.
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         Described in section IV.E of this supplemental proposal.
                    </P>
                </FTNT>
                <P>This proposed refrigerant provides an additional retrofit option and would not pose additional adverse effects to human health or the environment when used in accordance with existing and proposed requirements and as intended by the submitter. To provide additional options for the full range of MVACs, the EPA is proposing this listing for HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans.</P>
                <HD SOURCE="HD2">E. What use conditions is the EPA proposing for HFO-1234yf for retrofit of MVACs in this end-use and what existing requirements apply to this refrigerant?</HD>
                <P>The EPA is proposing the use condition that unique service port fittings specific to HFO-1234yf must be used in retrofit applications for this end-use. Service port fittings for HFO-1234yf were previously established and are identified in appendix B of 40 CFR part 82, subpart G.</P>
                <P>Appendix D of 40 CFR part 82, subpart G specifies requirements for unique fittings for new and retrofit MVAC listings and specifies information that must appear on a new label when a retrofit is performed, and outlines requirements for how the retrofit is completed including specifications for how unique fittings must be applied when performing a retrofit. The requirements for labeling, unique fittings, and the performance of the retrofit would apply to this proposed acceptability listing for MVAC retrofits. In the case of HFO-1234yf, the requirement to include a label would mitigate risk by ensuring that technicians are aware that the MVAC refrigerant is flammable. In the 2025 NPRM, the EPA proposed minor adjustments to these retrofit specifications and labeling requirements that would also apply to the proposed listing of HFO-1234yf in this supplemental action. The existing requirements and proposed amendments are described fully in section VIII.G. of the 2025 NPRM. While the proposed changes to section VIII.G. of the 2025 NPRM are relevant to the proposed listing of HFO-1234yf in this supplemental action, the EPA is not reopening comment on the proposed changes since the changes are broadly applicable to all MVAC retrofits, is not specific to this end-use, and is not specific to the proposed listing of HFO-1234yf in this supplemental proposal.</P>
                <P>
                    In the 2025 NRPM, the EPA also proposed to amend appendix B of 40 CFR part 82, subpart G. This provision currently states that flammable refrigerants in MVACs, both new and retrofit are unacceptable, except for HFO-1234yf and HFC-152a when used in new MVAC equipment. The 2025 NPRM proposed to amend this provision so that unacceptability also 
                    <PRTPAGE P="17184"/>
                    would not apply to HFO-1234yf used in retrofit MVACs. This proposed amendment is described fully in section VIII.F. of the 2025 NPRM and this supplemental proposal does not adjust or change those proposed revisions. However, the proposed revisions are relevant to this listing in that they would allow for use of HFO-1234yf in retrofits not only in LMDVs but also in HD pickup trucks and complete HD vans.
                </P>
                <P>
                    The EPA's SNAP program has a longstanding approach of requiring unique fittings for use with each refrigerant in MVACs. Appendix D of 40 CFR part 82, subpart G requires that each refrigerant be used with a set of fittings that is unique to that refrigerant. This is intended to prevent cross contamination of different refrigerants, preserve the purity of recycled refrigerants, and ultimately to avoid venting of refrigerant consistent with requirements under CAA section 608(c).
                    <SU>49</SU>
                    <FTREF/>
                     In the 1996 SNAP Rule requiring the use of unique fittings on all refrigerants submitted for use in MVACs, the EPA urged industry to develop mechanisms to ensure that the venting prohibition under CAA section 608(c) and the implementing regulations at 40 CFR 82.154 are observed.
                    <SU>50</SU>
                    <FTREF/>
                     The EPA has issued multiple SNAP rules requiring the use of fittings unique to a refrigerant for use on “containers of the refrigerant, on can taps, on recover, recycle, and recharge equipment, and on all [motor vehicle] air conditioning system service ports.” 
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         Codified at 40 CFR 82.154(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See</E>
                         61 FR 54032 (October 16, 1996).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See</E>
                         appendix D of 40 CFR part 82, subpart G.
                    </P>
                </FTNT>
                <P>The EPA expects that the companies selling refrigerants intended to be used as retrofits would make appropriate unique fittings and refrigerant labels available to certified technicians and do-it-yourselfers (DIYers) to allow them to conduct a retrofit in a manner that meets requirements under the CAA.</P>
                <HD SOURCE="HD1">V. Clarification of Intended Scope of the 2025 NPRM and Other Clarifications</HD>
                <P>The EPA is supplementing the 2025 NPRM to clarify the intended scope of that proposal. In the 2025 NPRM, the EPA proposed a listing for R-444A as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and HD vans (both complete and incomplete). The Agency included incomplete HD vans in error and is clarifying that we intended for this proposed listing to apply to HD pickup trucks and complete HD vans only.</P>
                <P>See sections VIII.B., VIII.D., and VIII.E. of the 2025 NPRM for a full discussion of the EPA's basis for proposing to list R-444A in this end-use. This discussion only provided a basis for the proposed listing of R-444A in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans. The EPA's risk screen of R-444A was for HD pickup trucks and complete HD vans. The risk screen did not include a scenario for reviewing risk of R-444A in incomplete HD vans. The SNAP program has thus far not listed any A2L refrigerant as acceptable for either new or retrofit use in incomplete HD vans due to lack of sufficient information on the appropriate risk scenarios for use of flammable refrigerants in incomplete HD vans.</P>
                <P>
                    In 2016, when the EPA listed HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for new HD pickup trucks and complete HD vans, the EPA did not finalize a listing for HFO-1234yf in any incomplete HD vans, stating that we did not have sufficient information on the potential for modifications to OEM-installed MVAC systems of incomplete HD vans by secondary manufacturers and the impact of those modifications on the safe use of HFO-1234yf. At the time of the 2025 NPRM, the same limitation applied and the EPA did not have sufficient information on the potential for modifications to OEM-installed MVAC systems of incomplete HD vans by secondary manufacturers and the impact of those modifications on the safe use of R-444A. For this reason and to remain consistent with our previous approach in SNAP Rule 21, the EPA is clarifying that the intended scope of the proposed listing for R-444A does not include incomplete HD vans and is requesting comment on the proposed listing as clarified.
                    <SU>52</SU>
                    <FTREF/>
                     The Agency will consider the comments received during the comment period for the 2025 NPRM on this proposed listing and will review any additional comments regarding the clarification to the scope of the listing made in this supplemental action.
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         SNAP Rule 21, 81 FR 86778 (December 1, 2016).
                    </P>
                </FTNT>
                <P>The clarification in this supplemental action does not impact any of the other MVAC end-uses in the 2025 NPRM where R-444A was proposed as acceptable, subject to use conditions, including as a retrofit in LMDVs, HD pickup trucks, and complete HD vans.</P>
                <P>
                    In this supplemental action, the EPA is also clarifying language in the 2025 NPRM and associated proposed regulatory text document related to HD pickup trucks. In the 2025 NPRM, the EPA proposed listings for R-444A, R-456A, and R-480A in the MVAC end-use for retrofit of HD pickup trucks (complete and incomplete). The Agency differentiated between complete and incomplete HD pickup trucks in error and is clarifying that we intended for the proposed listings for R-444A, R-456A, and R-480A to apply to HD pickup trucks generally. In contrast to HD vans, the EPA does not see complete and incomplete HD pickup trucks as two separate applications with unique risk profiles and has previously treated complete and incomplete HD pickup trucks the same. For purposes of consistency, the EPA is clarifying the regulatory language for the proposed listings of R-444A, R-456A, and R-480A to use the term “HD pickup trucks” rather than HD pickup trucks (complete and incomplete). From a practical perspective, this clarification does not change the types of vehicles that the proposed listings apply to; it is simply a clarification of terminology. The proposed regulatory text related to the clarifications addressed in this section may be found in the docket for this rulemaking.
                    <SU>53</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See</E>
                         Docket ID No. EPA-HQ-OAR-2024-0503 in documents titled “Proposed Changes to Appendix B for SNAP 27 Supplemental Proposal” and “Proposed Regulatory Text for SNAP Rule 27—Supplemental Proposal.”
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VI. On which topics is the EPA specifically requesting comment?</HD>
                <P>1. The EPA is requesting comment on the proposed listing of HFO-1234yf as acceptable, subject to use conditions, in the MVAC end-use for retrofit of HD pickup trucks and complete HD vans. Specifically, retrofitting MVACs designed for a nonflammable refrigerant such as HFC-134a to use a flammable refrigerant may present new risks. The EPA seeks comment on whether additional strategies to mitigate the flammability risk of A2L refrigerants beyond those required by appendix D to part 82, subpart G are necessary and suggestions of what those strategies may be.</P>
                <P>2. The EPA is requesting comment on the clarifications described in section V. of this supplemental action, including the clarification of the intended scope of the 2025 NPRM as it relates to the proposed listing of R-444A in the MVAC end-use for retrofit of complete HD vans and the clarification of terminology related to HD pickup trucks.</P>
                <HD SOURCE="HD1">VII. Statutory and Executive Order Reviews</HD>
                <P>
                    Additional information about these statutes and Executive Orders can be 
                    <PRTPAGE P="17185"/>
                    found at 
                    <E T="03">https://www.epa.gov/laws-regulations/laws-and-executive-orders.</E>
                </P>
                <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
                <P>This action is not a significant regulatory action and was therefore not submitted to the Office of Management and Budget (OMB) for review.</P>
                <HD SOURCE="HD2">B. Executive Order 14192: Unleashing Prosperity Through Deregulation</HD>
                <P>This action is expected to be an Executive Order 14192 deregulatory action. This proposed rule is expected to provide burden reduction by proposing to list more alternatives that would be available for use by industry.  </P>
                <HD SOURCE="HD2">C. Paperwork Reduction Act (PRA)</HD>
                <P>This action does not impose any new information collection burden under the PRA. OMB has previously approved the information collection activities contained in the existing regulations and has assigned OMB control number 2060-0226. This rule contains no new requirements for reporting or recordkeeping.</P>
                <HD SOURCE="HD2">D. Regulatory Flexibility Act (RFA)</HD>
                <P>I certify that this action will not have a significant economic impact on a substantial number of small entities under the RFA. In making this determination, the EPA concludes that the impact of concern for this rule is any significant adverse economic impact on small entities and that the Agency is certifying that this rule will not have a significant economic impact on a substantial number of small entities because the rule has no net burden on the small entities subject to the rule. This action proposes to add the additional options under SNAP of HFO-1234yf in the specified end-uses but does not mandate such use. Thus, if the rule were finalized as proposed, it would not impose new costs on small entities. We have therefore concluded that this action will have no net regulatory burden for all directly regulated small entities.</P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act (UMRA)</HD>
                <P>This action does not contain an unfunded mandate as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. The action imposes no enforceable duty on any state, local or Tribal governments or the private sector.</P>
                <HD SOURCE="HD2">F. Executive Order 13132: Federalism</HD>
                <P>This action does not have federalism implications. It will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">G. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This action does not have Tribal implications as specified in Executive Order 13175. It will not have substantial direct effects on Tribal governments, on the relationship between the Federal government and Indian Tribes, or on the distribution of power and responsibilities between the Federal government and Indian Tribes, as specified in Executive Order 13175. Thus, Executive Order 13175 does not apply to this action.</P>
                <HD SOURCE="HD2">H. Executive Order 13045: Protection of Children From Environmental Health and Safety Risks</HD>
                <P>
                    Executive Order 13045 directs Federal agencies to include an evaluation of the health and safety effects of the planned regulation on children in Federal health and safety standards and explains why the regulation is preferable to potentially effective and reasonably feasible alternatives. This action is not subject to Executive Order 13045 because it is not a significant regulatory action under section 3(f)(1) of Executive Order 12866, and because the EPA does not believe the environmental health or safety risks addressed by this action present a disproportionate risk to children. While the EPA has not conducted a separate analysis of risks to infants and children associated with this rule, the rule does contain use conditions that would reduce exposure risks to the general population, with the reduction of exposure being most important to the most sensitive individuals. This action's health and risk assessments are contained in the comparison of toxicity for the proposed substitute in section IV.D. of this supplemental action, as well as in the risk screen for the substitute that is listed in this supplemental proposed rule. The risk screen is in the docket under the title “Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Heavy-Duty Pickup Trucks and Complete Heavy-Duty Vans) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf),”at Docket ID No. EPA-HQ-OAR-2024-0503. However, the EPA's 
                    <E T="03">Policy on Children's Health</E>
                     applies to this action. Information on how the Policy was applied is available under “Children's Environmental Health” in the General Information section of this preamble.
                </P>
                <HD SOURCE="HD2">I. Executive Order 13211: Actions That Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>This action is not subject to Executive Order 13211, because it is not a significant regulatory action under Executive Order 12866.</P>
                <HD SOURCE="HD2">J. National Technology Transfer and Advancement Act</HD>
                <P>This supplemental rulemaking does not involve technical standards.</P>
                <HD SOURCE="HD1">VIII. References</HD>
                <P>
                    Unless specified otherwise, all documents are available electronically at 
                    <E T="03">https://regulations.gov,</E>
                     docket number EPA-HQ-OAR-2024-0503.
                </P>
                <EXTRACT>
                    <FP SOURCE="FP-2">ASHRAE. (2024). ANSI/ASHRAE Standard 34-2024: Designation and Safety Classification of Refrigerants.</FP>
                    <FP SOURCE="FP-2">
                        EEAP. (2023). Environmental Effects of Stratospheric Ozone Depletion, UV Radiation, and Interactions with Climate Change. 2022 Assessment Report. UNEP, Environmental Effects Assessment Panel. 
                        <E T="03">https://ozone.unep.org/system/files/documents/EEAP-2022-Assessment-Report-May2023.pdf.</E>
                    </FP>
                    <FP SOURCE="FP-2">Gradient Corporation. (2008). Risk Assessment for Alternative Refrigerant HFO-1234yf. Confidential report prepared for SAE International Cooperative Research Program 1234.</FP>
                    <FP SOURCE="FP-2">Gradient Corporation. (2008). Risk Assessment For Alternative Refrigerant HFO-1234yf. (Phase I) Prepared for the Society of Automotive Engineers (SAE) Cooperative Research Project 150.</FP>
                    <FP SOURCE="FP-2">
                        Gradient Corporation. (2009). Risk Assessment for Alternative Refrigerants HFO-1234yf and R-744 (CO
                        <E T="52">2</E>
                        ). Confidential report prepared for SAE International Cooperative Research Program 1234.
                    </FP>
                    <FP SOURCE="FP-2">Gradient Corporation. (2013a). Additional Risk Assessment of Alternative Refrigerant R-1234yf. Confidential report prepared for SAE International Cooperative Research Program 1234-4.</FP>
                    <FP SOURCE="FP-2">Gradient Corporation. (2023a). Retrofit Analysis Letter. Prepared for Honeywell International.</FP>
                    <FP SOURCE="FP-2">ICF. (2009). Risk Screen on Substitutes for CFC-12 in Motor Vehicle Air Conditioning: Substitute: HFO-1234yf.</FP>
                    <FP SOURCE="FP-2">ICF. (2016b). Technical Support Document for Acceptability Listing of HFO-1234yf for Motor Vehicle Air Conditioning in Limited Heavy-Duty Applications.</FP>
                    <FP SOURCE="FP-2">
                        ICF. (2025k). Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Light-Duty and Medium-Duty Vehicles) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf).
                        <PRTPAGE P="17186"/>
                    </FP>
                    <FP SOURCE="FP-2">ICF. (2026a). Technical Support Document for Motor Vehicle Air Conditioning in Limited Heavy-Duty Applications.</FP>
                    <FP SOURCE="FP-2">ICF. (2026b). Risk Screen on Substitutes in Motor Vehicle Air Conditioning (Heavy-Duty Pickup Trucks and Complete Heavy-Duty Vans) (Retrofit Equipment); Substitute: HFO-1234yf (Solstice® yf or Solstice® 1234yf).</FP>
                    <FP SOURCE="FP-2">
                        Metghalchi, M. &amp; Keck, J.C. (1980). Laminar Burning Velocity of Propane-Air Mixtures at High Temperature and Pressure. 
                        <E T="03">Combustion And Flame</E>
                         38: 143-154: 
                        <E T="03">https://james-keck-memorial-collection.unibs.it/JCKeck-papers/MetghalchiKeck-CombustionFlame-38-143-1980.pdf.</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        Minor, B. et al. (2009). (111g) Flammability Characteristics of Low GWP Refrigerant HFO-1234yf. 
                        <E T="03">AIChE 2009 Spring Meeting &amp; 5th Global Congress on Process Safety. https://proceedings.aiche.org/conferences/aiche-spring-meeting-and-global-congress-on-process-safety/2009/proceeding/paper/111g-flammability-characteristics-low-gwp-refrigerant-hfo-1234yf.</E>
                    </FP>
                    <FP SOURCE="FP-2">SAE. (2011). J1660 “Fittings and Labels for Retrofit of CFC-12 (R-12) Mobile Air-Conditioning Systems to HFC-134a (R-134a).”</FP>
                    <FP SOURCE="FP-2">
                        Takizawa, K. et al. (2005). Burning velocity measurement of fluorinated compounds by the spherical-vessel method, 
                        <E T="03">Combustion and Flame,</E>
                         Volume 141, Issue 3, Pages 298-307: 
                        <E T="03">https://doi.org/10.1016/j.combustflame.2005.01.009.</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        U.S. Environmental Protection Agency. (2024). EPA Automotive Trends Report: Greenhouse Gas Emissions, Fuel Economy, and Technology since 1975: 
                        <E T="03">https://nepis.epa.gov/Exe/ZyPDF.cgi?Dockey=P101CUU6.pdf.</E>
                    </FP>
                </EXTRACT>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 82</HD>
                    <P>Environmental protection, Administrative practice and procedure, Air pollution control, Chemicals.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Lee Zeldin,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06665 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 141</CFR>
                <DEPDOC>[EPA-HQ-OW-2022-0946; FRL-10773-01-OW]</DEPDOC>
                <SUBJECT>Drinking Water Contaminant Candidate List 6—Draft</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Environmental Protection Agency (EPA) is publishing a draft list of contaminants that are currently not subject to any proposed or promulgated national primary drinking water regulations for public review and comment. These contaminants are known or anticipated to occur in public water systems and may require regulation under the Safe Drinking Water Act (SDWA) in the future. The draft list provided in this document is the sixth Contaminant Candidate List (CCL) published by the Agency since the SDWA amendments of 1996. The draft Sixth Contaminant Candidate List (CCL 6 or the list) includes 75 chemicals, 4 chemical groups (disinfection byproducts (DBPs), microplastics, per- and polyfluoroalkyl substances (PFAS), and pharmaceuticals) and 9 microbes. The EPA seeks public comment on the draft CCL 6 and the process used to develop the draft CCL 6. The EPA will consider all information and comments received in response to this notice of availability for determining the final CCL 6.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 5, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, identified by Docket ID Number EPA-HQ-OW-2022-0946, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: https://www.regulations.gov</E>
                         (our preferred method). Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Environmental Protection Agency, EPA Docket Center, Water Docket, Environmental Protection Agency, Mail code: 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         EPA Docket Center, WJC West Building, Room 3334, 1301 Constitution Ave. NW, Washington, DC 20004. The Docket Center's hours of operations are 8:30 a.m.-4:30 p.m., Monday through Friday (except Federal Holidays).
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID No. EPA-HQ-OW-2022-0946 for this rulemaking. Comments received may be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided. For detailed instructions on sending comments and additional information on the rulemaking process, see the “Public Participation” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas Lombardi, Standards and Risk Management Division, Office of Ground Water and Drinking Water; email: 
                        <E T="03">lombardi.thomas@epa.gov;</E>
                         telephone: (202) 564-7653.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. General Information</FP>
                    <FP SOURCE="FP1-2">A. Does this action impose any requirements on public water systems?</FP>
                    <FP SOURCE="FP1-2">B. Public Participation</FP>
                    <FP SOURCE="FP1-2">C. What should I consider as I prepare my comments for the EPA?</FP>
                    <FP SOURCE="FP-2">II. Purpose, Background, and Statutory Requirements of This Action</FP>
                    <FP SOURCE="FP1-2">A. What is the purpose of this action?</FP>
                    <FP SOURCE="FP1-2">B. Background and Statutory Requirements for the CCL</FP>
                    <FP SOURCE="FP1-2">C. Interrelationship of the CCL and Related SDWA Programs, Regulatory Determinations, and Unregulated Contaminant Monitoring Rule</FP>
                    <FP SOURCE="FP1-2">D. Summary of the Most Recent CCL</FP>
                    <FP SOURCE="FP1-2">E. What is included on the draft CCL 6?</FP>
                    <FP SOURCE="FP-2">III. Developing the Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">A. Approach Used To Identify Chemical Candidates for the Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">1. Building the Chemical Universe</FP>
                    <FP SOURCE="FP1-2">2. Screening the Chemical Universe to a Preliminary Contaminant Candidate List (PCCL)</FP>
                    <FP SOURCE="FP1-2">3. Classification of PCCL Chemical Contaminants To Select a Draft CCL</FP>
                    <FP SOURCE="FP1-2">a. Supplemental Data Collection Used in Classification</FP>
                    <FP SOURCE="FP1-2">b. Evaluation Team Listing Recommendation Process</FP>
                    <FP SOURCE="FP1-2">c. Additional Refinement for Contaminants With Previous Negative Regulatory Determinations</FP>
                    <FP SOURCE="FP1-2">d. Chemical Groups on the Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">i. Disinfection Byproducts</FP>
                    <FP SOURCE="FP1-2">ii. Microplastics</FP>
                    <FP SOURCE="FP1-2">iii. Per- and Polyfluoroalkyl Substances</FP>
                    <FP SOURCE="FP1-2">iv. Pharmaceuticals</FP>
                    <FP SOURCE="FP1-2">B. Approach Used To Identify Microbial Candidates for the Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">1. Building the Microbial Universe</FP>
                    <FP SOURCE="FP1-2">2. Screening the Microbial Universe to a Preliminary Contaminant Candidate List (PCCL 6)</FP>
                    <FP SOURCE="FP1-2">3. Review of PCCL 6 Microbial Contaminants To Select a Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">a. Selection of the Draft CCL 6 Microbes</FP>
                    <FP SOURCE="FP1-2">C. Summary of Nominated Candidates for the Draft CCL 6</FP>
                    <FP SOURCE="FP1-2">D. Data Needs for the Draft CCL 6</FP>
                    <FP SOURCE="FP-2">IV. Request for Comments</FP>
                    <FP SOURCE="FP-2">V. The EPA's Next Steps</FP>
                    <FP SOURCE="FP-2">VI. References</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action impose any requirements on public water systems?</HD>
                <P>The draft CCL 6 and the final CCL 6, when published, will not impose any requirements on regulated entities.</P>
                <HD SOURCE="HD2">B. Public Participation</HD>
                <P>
                    Submit your comments, identified by Docket ID No. EPA-HQ-OW-2022-0946, at 
                    <E T="03">https://www.regulations.gov,</E>
                     (our preferred method), or the other methods identified in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. Once submitted, comments cannot be edited or removed from the docket. The EPA may publish any comment received to its public docket. Do not submit 
                    <PRTPAGE P="17187"/>
                    electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                    <E T="03">i.e.,</E>
                     on the web, cloud, or other file sharing system). For additional submission methods, the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                </P>
                <HD SOURCE="HD2">C. What should I consider as I prepare my comments for the EPA?</HD>
                <P>You may find the following suggestions helpful for preparing your comments:</P>
                <FP SOURCE="FP-1">—Explain your views as clearly as possible.</FP>
                <FP SOURCE="FP-1">—Describe any assumptions that you used.</FP>
                <FP SOURCE="FP-1">—Provide any technical information, alternative scientific analyses, and/or data you used that support your views.</FP>
                <FP SOURCE="FP-1">—Provide full references for any peer reviewed publication you used that support your views.</FP>
                <FP SOURCE="FP-1">—Provide specific examples to illustrate your concerns.</FP>
                <FP SOURCE="FP-1">—Offer alternatives.</FP>
                <P>
                    Make sure to submit your comments by the comment period deadline. To ensure proper receipt by the EPA, identify the appropriate docket identification number in the subject line on the first page of your response. It would also be helpful if you provided the name, date, and 
                    <E T="04">Federal Register</E>
                     citation related to your comments.
                </P>
                <HD SOURCE="HD1">II. Purpose, Background, and Statutory Requirements of This Action</HD>
                <P>This section briefly summarizes the purpose of this action, the statutory requirements, previous activities related to the CCL and the approach used to develop the draft CCL 6.</P>
                <HD SOURCE="HD2">A. What is the purpose of this action?</HD>
                <P>The purpose of this action is to present and seek comment upon the EPA's draft CCL 6 and the selection process used to make the list. When finalized, CCL 6 will be used to prioritize research and data collection efforts for drinking water contaminants. In a future, separate action the EPA will make regulatory determinations on whether to regulate at least five contaminants from the CCL with National Primary Drinking Water Regulations (NPDWRs) under the SDWA, section 1412(b)(1)(B)(ii).</P>
                <HD SOURCE="HD2">B. Background and Statutory Requirements for the CCL</HD>
                <P>SDWA section 1412(b)(1)(B)(i), as amended in 1996, requires the EPA to publish the CCL every five years. SDWA specifies that the list must include contaminants that are not subject to any proposed or promulgated NPDWRs, are known or anticipated to occur in public water systems (PWSs), and may require regulation under the SDWA. The statute provides that the unregulated contaminants considered for listing shall include, but not be limited to, hazardous substances identified in section 101(14) of the Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA) of 1980, and substances registered as pesticides under the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). SDWA section 1412(b)(1)(C) directs the EPA to identify those contaminants that present the greatest public health concern related to exposure from drinking water, and, in making such selection, to take into consideration the human health effects after exposure to a contaminant specifically to sensitive subgroups that comprise a meaningful portion of the general population (such as infants, children, pregnant women, the elderly, and individuals with a history of serious illness or other subpopulations) that are identifiable as being at greater risk of adverse health effects due to exposure to contaminants in drinking water than the general population.</P>
                <HD SOURCE="HD2">C. Interrelationship of the CCL and Related SDWA Programs, Regulatory Determinations, and Unregulated Contaminant Monitoring Rule</HD>
                <P>The CCL is the first step in the SDWA regulatory framework, serving as the initial screening of contaminants to identify those which may require regulation under SDWA. The CCL informs future Unregulated Contaminant Monitoring Rules (UCMR) and Regulatory Determinations. The inclusion of a contaminant on the CCL, whether as an individual or in a group, does not mean that any particular contaminant will necessarily be regulated in the future. Rather, the CCL serves as a first level of evaluation for unregulated drinking water contaminants that may need further investigation of potential health effects and the levels at which they are found in drinking water. Contaminants from the CCL with sufficient health effects and occurrence information are considered for regulatory determination and rulemaking under SDWA.</P>
                <P>SDWA section 1445(a)(2) as amended in 1996, requires that once every five years the EPA issues a UCMR with a list of no more than 30 unregulated contaminants to be monitored in drinking water by PWSs. The UCMR provides nationally representative occurrence data for unregulated contaminants in drinking water. The UCMR is related to the CCL in two ways. First, EPA considers contaminants from the CCL in selecting contaminants for the UCMR. Second, the contaminant occurrence data collected under the UCMR can inform EPA's consideration of contaminants for future CCLs.</P>
                <P>The CCL is also related to the regulatory determinations process. Following the publication of a final CCL, the EPA evaluates those CCL contaminants with sufficient information to make a regulatory determination, using the three statutory criteria listed in SDWA section 1412(b)(1)(A):</P>
                <P>1. The contaminant may have an adverse effect on the health of persons;</P>
                <P>2. The contaminant is known to occur or there is a substantial likelihood that the contaminant will occur in public water systems with a frequency and at levels of public health concern; and</P>
                <P>3. In the sole judgment of the Administrator, regulation of such contaminant presents a meaningful opportunity for health risk reduction for persons served by public water systems.</P>
                <P>Based upon this evaluation, the EPA determines whether a regulation is appropriate (positive determination) or not appropriate (negative determination). The EPA is required by SDWA to make regulatory determinations for at least five contaminants listed on the CCL every five years.</P>
                <HD SOURCE="HD2">D. Summary of the Most Recent CCL</HD>
                <P>
                    The EPA has published five CCLs since 1996. The EPA published its most recent CCL, CCL 5, in the 
                    <E T="04">Federal Register</E>
                     (87 FR 68060, USEPA 2022a) on November 14, 2022. The final CCL 5 included 81 contaminants or groups. The list is comprised of 66 chemicals, 3 chemical groups (cyanotoxins, disinfection byproducts (DBPs), and per- and polyfluoroalkyl substances (PFAS)) and 12 microbial contaminants.
                </P>
                <HD SOURCE="HD2">E. What is included on the draft CCL 6?  </HD>
                <P>
                    The draft CCL 6 includes 88 contaminants (Exhibits 1a, 1b, and 1c of this document). The list is comprised of 
                    <PRTPAGE P="17188"/>
                    75 chemicals, four chemical groups, and nine microbes.
                </P>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
                <GPH SPAN="3" DEEP="622">
                    <GID>EP06AP26.077</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17189"/>
                    <GID>EP06AP26.078</GID>
                </GPH>
                <GPH SPAN="3" DEEP="320">
                    <PRTPAGE P="17190"/>
                    <GID>EP06AP26.079</GID>
                </GPH>
                <GPH SPAN="3" DEEP="256">
                    <GID>EP06AP26.080</GID>
                </GPH>
                <BILCOD>BILLING CODE 6560-50-C</BILCOD>
                <HD SOURCE="HD1">III. Developing the Draft CCL 6</HD>
                <P>
                    In developing the draft CCL 6, the EPA followed a 3-step process that is illustrated in Exhibit 2 of this document. The EPA applied this process separately to both chemical and microbial contaminants to develop the draft CCL 6. In the first step, the Agency developed the CCL 6 Chemical Universe and the CCL 6 Microbial Universe by compiling available health and occurrence data. In the second step, the EPA developed subsets of the Chemical Universe and Microbial Universe, called the Chemical and Microbial Preliminary Contaminant Candidate Lists (PCCLs), by prioritizing contaminants using a 
                    <PRTPAGE P="17191"/>
                    points-based screening system. Finally in the third step, the EPA selected the contaminants from the Chemical and Microbial PCCLs that are most likely to occur in public water systems and that pose the greatest potential public health concern in drinking water. Exhibit 2 of this document lists the number of chemicals, chemical groups and microbes the EPA considered at each step of the process.
                </P>
                <HD SOURCE="HD1">Exhibit 2—Overall Draft CCL 6 Development Process and Contaminant Counts</HD>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
                <GPH SPAN="3" DEEP="297">
                    <GID>EP06AP26.081</GID>
                </GPH>
                <BILCOD>BILLING CODE 6560-50-C</BILCOD>
                <P>
                    The draft CCL 6 technical support documents provide comprehensive details about the draft CCL 6 chemical and microbial processes: 
                    <E T="03">Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Chemical Contaminants</E>
                     (USEPA, 2026a) and the 
                    <E T="03">Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Microbial Contaminants</E>
                     (USEPA, 2026c), hereafter referred to as the 
                    <E T="03">Chemical Technical Support Document</E>
                     and 
                    <E T="03">Microbial Technical Support Document,</E>
                     respectively.
                </P>
                <HD SOURCE="HD2">A. Approach Used To Identify Chemical Candidates for the Draft CCL 6</HD>
                <HD SOURCE="HD3">1. Building the Chemical Universe</HD>
                <P>In the first step of the CCL 6 development process for chemical candidates, the EPA identified a broad universe of potential drinking water contaminants. The EPA began the development process by compiling data sources to identify chemicals for inclusion in the CCL 6 Chemical Universe. The EPA identified data sources from previous CCLs, the Science Advisory Board (SAB), and scientific literature searches.</P>
                <P>
                    The EPA assessed data sources for their potential use in the CCL 6 development process based on four assessment factors; relevancy, completeness, redundancy, and retrievability. The EPA identified 20 sources of health effects data and 41 sources of occurrence data, including 18 new data sources. In total, 25,305 chemicals were identified from the main data sources and comprise the CCL 6 Chemical Universe. This is the largest universe of chemicals and the greatest number of data sources that the EPA has evaluated for any CCL. For more information about building the CCL 6 Chemical Universe and data sources used, see Chapter 2 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a).
                </P>
                <HD SOURCE="HD3">2. Screening the Chemical Universe to a Preliminary Contaminant Candidate List (PCCL)</HD>
                <P>
                    In the second step of the CCL 6 development process, the EPA screened chemicals from the CCL 6 Chemical Universe to identify the list of chemicals that should be further evaluated, namely the PCCL 6. The EPA applied a points-based screening system to determine which contaminants are placed onto the PCCL. The EPA assigned cumulative points to contaminants across health effects and occurrence data elements. The scoring is described in Section 3.2 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a). The EPA used these screening scores, along with statistical models and analyses described in Section 4.6 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a), to prioritize chemicals to inform the PCCL 6.
                </P>
                <P>
                    The EPA identified the highest scoring chemicals for inclusion on the PCCL 6 and validated the selection of the top scoring chemicals and the screening score framework using a statistical modeling approach. As a result of screening the CCL 6 Chemical Universe, the PCCL 6 started with 274 chemicals. From this pool, the protocol excluded 34 chemicals from the PCCL: nine chemicals were excluded due to 
                    <PRTPAGE P="17192"/>
                    recent regulatory determinations made for contaminants on CCL 5 (90 FR 3830, USEPA, 2025) or a pending Agency action. An additional 25 chemicals were excluded because they were canceled pesticides with no reported alternative uses that break down quickly in the environment and are therefore not anticipated to occur in public water systems.
                </P>
                <P>
                    The EPA also excluded chemicals from the base PCCL 6 that were within chemical groups that the Agency had determined to list (see Exhibit 1b and section III.A.3.d of this document). Eight chemicals were excluded because EPA had determined to include them in the DBP group, 15 chemicals were excluded because EPA had identified them for inclusion under the pharmaceutical group, and four other chemicals were excluded because EPA found they met the structural definition requirements for inclusion within the PFAS group (see Exhibit 1b for more details). In total, 213 chemicals remained on the PCCL 6 to be evaluated individually in the classification step. A more detailed summary of the PCCL 6 is included in Section 3.8 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a).
                </P>
                <HD SOURCE="HD3">3. Classification of PCCL Chemical Contaminants To Select a Draft CCL</HD>
                <P>
                    In the third step of the CCL process, the EPA narrowed down the PCCL 6 to determine the draft CCL 6 through a classification process. For the purposes of CCL 6, classification refers to the process by which, first, the Agency incorporated the knowledge and evaluation by the EPA scientists, referred to as “chemical evaluators,” to recommend contaminants for listing for the draft CCL. To facilitate the classification process, the EPA conducted literature and assessment searches to gather supplemental health and occurrence data for the PCCL 6 chemicals. The main and supplemental data were compiled by chemical, and relevant health effects and occurrence data metrics were imported into a standardized document format, called the Contaminant Information Sheet (CIS) that are provided in the 
                    <E T="03">Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Contaminant Information Sheets</E>
                     (USEPA, 2026b). The chemical evaluators reviewed the health effects and occurrence information provided on the CISs to inform consensus listing recommendations for the PCCL chemicals.
                </P>
                <HD SOURCE="HD3">a. Supplemental Data Collection Used in Classification</HD>
                <P>
                    During classification, the EPA gathered supplemental data to better evaluate the PCCL 6 chemicals and determine which contaminants were more likely to be present in drinking water at levels that may require regulation. These supplemental data were used to inform more specific evaluations of the PCCL 6 chemicals. For example, supplemental health data was gathered to calculate health concentrations, which are non-regulatory health-based toxicity values at or below which no adverse effects are expected to occur. The EPA compares occurrence data to the health concentrations to characterize the likelihood that the contaminant may be in drinking water at levels of health concern that may require regulation. Information on supplemental data used in the draft CCL 6 is in Section 4.2 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a).
                </P>
                <HD SOURCE="HD3">b. Evaluation Team Listing Recommendation Process</HD>
                <P>
                    Chemical evaluators reviewed the health effects and occurrence data on the CIS for each chemical, and the evaluation teams provided consensus listing recommendations. A detailed description of the chemical evaluation team listing process can be found in Section 4.5 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a).
                </P>
                <HD SOURCE="HD3">c. Additional Refinement for Contaminants With Previous Negative Regulatory Determinations</HD>
                <P>
                    The Agency developed an additional step for the CCL 6 process to further analyze a subset of the chemicals recommended for listing by the evaluators that had previous negative regulatory determinations. This was done to provide clarity regarding chemicals that have previously received decisions not to regulate under SDWA as well as to be consistent with the purpose of CCL as an iterative process that aims to improve each time. The CCL 6 chemical evaluators recommended twelve chemicals for listing that EPA had previously determined not to regulate under the separate SDWA regulatory determination process, which like CCL, occurs in 5-year cycles. For this subset of chemicals, the EPA examined whether any new health and/or occurrence information available since the time of the original determinations indicate the contaminant is of greater public health concern now and could potentially result in a different (
                    <E T="03">i.e.,</E>
                     positive) decision under a future cycle of regulatory determination. For nine of these contaminants the currently available data do not indicate a greater public health concern at this time and these chemicals were consequently removed from consideration for the draft CCL 6. A description of the refinement can be found in Section 4.7 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a).
                </P>
                <HD SOURCE="HD3">d. Chemical Groups on the Draft CCL 6</HD>
                <P>In addition to the 75 chemicals proposed for listing on the draft CCL 6, the EPA proposes listing four chemical groups (disinfection byproducts, microplastics, PFAS, and pharmaceuticals) (see Exhibit 1b). These chemical groups have been identified as Agency priorities and contaminants of concern for drinking water by public stakeholders and under other EPA actions. Listing these four chemical groups on the draft CCL 6 does not mean that the EPA will make subsequent regulatory decisions for the entire group. The EPA will evaluate available scientific data on the listed groups, subgroups, and individual contaminants, as appropriate, included in the group to inform any regulatory determinations for the group, subgroup, or individual contaminants in the group.</P>
                <HD SOURCE="HD3">i. Disinfection Byproducts</HD>
                <P>DBPs are formed when disinfectants, used for purposes of antimicrobial treatment in drinking water, react with naturally occurring or man-made materials in water. The EPA is proposing to list DBPs as a group on the draft CCL 6, acknowledging this as an Agency priority for drinking water. The DBP group includes 27 unregulated DBPs, twenty-three of these were listed under the DBP chemical group published under the CCL 5 process (87 FR 68060, USEPA, 2022a); the other four unregulated DBPs (bromochloroacetonitrile, chloral hydrate, chloronitramide anion, and trichloroacetonitrile) are being added to the group based on consultation with the Agency microbial and disinfection byproduct subject matter experts.</P>
                <HD SOURCE="HD3">ii. Microplastics</HD>
                <P>
                    The EPA acknowledges the concern for microplastics in sources of drinking water and also received a public nomination for including microplastics on CCL 6 that was accompanied by three data sources (Miller et al., 2021; Ragusa et al., 2021; and Zarus et al., 2021), all indicating potential concern for exposure to microplastics. In the Science Advisory Board's 
                    <PRTPAGE P="17193"/>
                    recommendations for the draft CCL 5, the SAB also encouraged the EPA to consider the assessment and inclusion of microplastics on future CCLs (USEPA, 2022b). Therefore, the Agency is including microplastics as a group on the draft CCL 6 as a first step toward defining and better understanding potential public health risk from exposure via drinking water.
                </P>
                <P>As of the publication of the draft CCL 6, there remain significant data gaps for microplastics that will require further research before the Agency can fully understand the risks associated with microplastics in drinking water. The known data gaps requiring further research include (but are not limited to) the following:  </P>
                <P>
                    1. 
                    <E T="03">A health-based definition:</E>
                     the need to determine the characteristics of the microplastics (
                    <E T="03">i.e.,</E>
                     colors, polymers, shapes, sizes, etc.) most associated with adverse health effects in humans from exposure in drinking water.
                </P>
                <P>
                    2. 
                    <E T="03">Detection technology:</E>
                     the need for a validated analytical method with the proper quality control data, accuracy, and precision that will allow the EPA to be able to detect and analyze the concentrations of microplastics occurring in drinking water reliably.
                </P>
                <P>
                    3. 
                    <E T="03">Microplastics combined with other substances:</E>
                     the need to better understand how microplastics occurring in mixtures may impact detecting specific microplastics and identifying their associated health risks.
                </P>
                <P>
                    4. 
                    <E T="03">Sources:</E>
                     the need to better understand all potential sources of plastic pollution that contribute to the formation of microplastics in sources of drinking water.
                </P>
                <P>
                    In summary, research is needed to determine the adverse health effects from ingesting microplastics and to determine the characteristics of the microplastics (
                    <E T="03">i.e.,</E>
                     size, type of plastic, etc.) that are associated with the adverse health effects posing the greatest potential health risk from exposure via drinking water. This research will also assist in the development of robust and validated analytical methods for microplastics in drinking water that may be used to standardize data collection and analysis in the future.
                </P>
                <HD SOURCE="HD3">iii. Per- and Polyfluoroalkyl Substances</HD>
                <P>PFAS are a class of synthetic chemicals that are most commonly used to make products resistant to water, heat, and stains and are consequently found in industrial and consumer products like clothing, food packaging, cookware, cosmetics, carpeting, and fire-fighting foam (Cohen, 2020; USEPA, 2018). Over 4,000 PFAS have been manufactured and used globally since the 1940s (USEPA, 2019), and data are scarce for the majority of the PFAS, which would make evaluating PFAS individually for the draft CCL 6 impractical. The Agency is proposing to list a PFAS group to the draft CCL 6 inclusive of all PFAS that meet the structural definition developed for the final CCL 5 (87 FR 68060, USEPA, 2022a), excluding those that are subject to national drinking water regulations at the time of publication of final CCL 6 (National Primary Drinking Water Regulations, 40 CFR part 141 subpart Z—Control of Per- and Polyfluoroalkyl Substances (PFAS), n.d.)). For the purposes of CCL, the structural definition of PFAS remains the same as the definition utilized in CCL 5 and includes chemicals that contain at least one of these three structures:</P>
                <EXTRACT>
                    <P>1. R-(CF2)-CF(R′)R′′, where both the CF2 and CF moieties are saturated carbons, and none of the R groups can be hydrogen;</P>
                    <P>2. R-CF2OCF2-R′, where both the CF2 moieties are saturated carbons, and none of the R groups can be hydrogen; and</P>
                    <P>3. CF3C(CF3)RR′, where all the carbons are saturated, and none of the R groups can be hydrogen.</P>
                </EXTRACT>
                <P>This proposal to list PFAS as a chemical group is responsive to public nominations and is consistent with the approach taken for CCL 5 and is in keeping with the Agency's commitment to better understand and ultimately reduce the potential risks caused by this broad class of chemicals. Including the group of PFAS on the draft CCL 6 demonstrates the Agency's commitment to prioritizing and building a strong foundation of science on PFAS.</P>
                <HD SOURCE="HD3">iv. Pharmaceuticals</HD>
                <P>For over a decade, public concern about the presence of pharmaceutical substances in sources of drinking water has been a recurring topic of discussion for the Agency's prioritization of contaminants under SDWA. Since 2012, the EPA has led a Federal workgroup on pharmaceuticals in water alongside USDA, FDA, and USGS to exchange information on pharmaceuticals in the environment and to support the coordination of joint studies.</P>
                <P>
                    The EPA committed to understanding contaminants in drinking water and has identified pharmaceuticals as an Agency priority. This priority is further reinforced by feedback received through the public nominations process. For CCL 6, the Agency incorporated new data sources (Schaider et al., 2014 and Battaglin et al., 2018) that provided additional information about the occurrence of pharmaceutical products in water; for health data on pharmaceuticals, the EPA added a source used to help identify chemicals with estrogenic activity (USEPA, 2023b). The Agency also completed the 
                    <E T="03">Human Health Benchmarks for Pharmaceuticals (HHB-Rx) in Drinking Water</E>
                     (visit the EPA website for more information at 
                    <E T="03">https://www.epa.gov/sdwa/human-health-benchmarks</E>
                    ). Human health benchmarks are non-enforceable drinking water levels that provide information about adverse health effects from drinking water exposure to contaminants that have no drinking water standards or health advisories. The benchmarks, based on potential health effects from exposure via drinking water, informed the screening of pharmaceuticals and identification of the top scoring pharmaceuticals. Furthermore, the application of the benchmarks for pharmaceuticals in the CCL screening process informed the EPA about the current research needs for this broad class of chemicals.
                </P>
                <P>The Agency is proposing the inclusion of a pharmaceuticals group on the draft CCL 6 to further prioritize research and information needed to identify which specific pharmaceuticals are occurring in drinking water and may be of greatest public health concern. For the purposes of the draft CCL 6, the EPA considers pharmaceuticals to include any substances defined as a “drug” under the Federal Food, Drug, And Cosmetic Act (1938).</P>
                <HD SOURCE="HD2">B. Approach Used To Identify Microbial Candidates for the Draft CCL 6</HD>
                <HD SOURCE="HD3">1. Building the Microbial Universe</HD>
                <P>
                    The EPA defines the CCL Microbial Universe as microbial contaminants known to cause human disease. For CCL 6, the EPA conducted a literature search for newly identified microbes and reviewed the public nominations for additional pathogens to add to the CCL 6 Microbial Universe. The full CCL 6 Microbial Universe list is available in Appendix B of the 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c).
                </P>
                <HD SOURCE="HD3">2. Screening the Microbial Universe to a Preliminary Contaminant Candidate List (PCCL 6)</HD>
                <P>
                    The EPA uses screening criteria to narrow the Microbial Universe to only those pathogens that have the potential to be transmitted through drinking water. The pathogens that are not excluded by any of the screening criteria are moved to the microbial PCCL 6. The screening criteria restricts the microbial PCCL 6 to human pathogens that may cause drinking water-related diseases resulting from ingestion, inhalation, or dermal contact with drinking water. In 
                    <PRTPAGE P="17194"/>
                    addition, any pathogen documented to cause disease transmitted through drinking water, regardless of the screening criteria, is also considered for the PCCL.
                </P>
                <P>
                    After applying the screening criteria to the CCL 6 Microbial Universe, 36 pathogens advanced to the PCCL 6. The screening criteria and results of the screening process are discussed in greater detail in Chapter 3 of the 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c).
                </P>
                <HD SOURCE="HD3">3. Review of PCCL 6 Microbial Contaminants to Select a Draft CCL 6</HD>
                <P>Each pathogen on the PCCL 6 is evaluated for their occurrence in water and their ability to produce adverse health effects in humans. The EPA used a scoring system to assign a numerical value to each pathogen on the PCCL 6. Each pathogen on the PCCL 6 was scored based upon protocols developed to consider waterborne disease outbreaks, occurrence, and health risks. For details on the three protocols used to score the PCCL 6 microbial contaminants and the process by which the scores are combined see Chapter 4 in the Microbial Support Document (USEPA, 2026c).</P>
                <HD SOURCE="HD3">a. Selection of the Draft CCL 6 Microbes</HD>
                <P>For CCL 6, the CCL selection process for listing placed emphasis on the PCCL 6 microbial contaminants with confirmed (versus suspected) outbreak(s) that have occurred in U.S. PWSs during the timeframe evaluated for CCL 6. This approach to select contaminants for the CCL 6 prioritizes the pathogens that provide the best opportunities to advance public health protection through potential regulation.</P>
                <HD SOURCE="HD2">C. Summary of Nominated Candidates for the Draft CCL 6</HD>
                <P>
                    The EPA sought public nominations in a 
                    <E T="04">Federal Register</E>
                     publication on February 17, 2023 for chemicals, microbes, or other substances that are not currently regulated to be considered for possible inclusion in the CCL 6 (88 FR 10316, USEPA, 2023a).
                </P>
                <P>
                    The EPA received nominations for six chemicals and/or chemical groups (lithium, manganese, microplastics, perchlorate, PFAS, pharmaceutical waste (specifically estrogenic compounds)) and five microbes and/or microbial groups (
                    <E T="03">Legionella pneumophila, Listeria monocytogenes,</E>
                     Nontuberculous Mycobacteria (NTM), pathogenic waterborne mycobacteria group, 
                    <E T="03">Pseudomonas aeruginosa).</E>
                     All public nomination letters and supporting information can be viewed in the EPA docket at 
                    <E T="03">https://www.regulations.gov</E>
                     (Docket ID No. EPA-HQ-OW-2022-0946). A detailed summary of the nomination process, including how each nominated contaminant was considered for inclusion on the draft CCL 6, is provided in Section 3.6 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a) and in Section 2.2 of the 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c).
                </P>
                <HD SOURCE="HD2">D. Data Needs for the Draft CCL 6</HD>
                <P>
                    In previous CCLs, the SAB and other commenters have recommended additional prioritization of contaminants to communicate research needs and inform future regulatory decision-making. The EPA acknowledges that multiple contaminants on the draft CCL 6 (and considered in the PCCL 6) have data and information needs to fulfill in order for the Agency to make a regulatory determination in accordance with SDWA 1412 (b)(1)(A). By identifying additional research and information needs, the EPA is communicating to stakeholders both research priorities and gaps for these contaminants. The EPA provides summary tables in Chapter 5 of the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a) and Chapter 6 in the 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c) identifying chemicals and microbial contaminants (respectively) categorized into four groups depending upon the availability of occurrence data and health assessments. This list is a starting point for identifying the data needs of the CCL 6 contaminants.
                </P>
                <HD SOURCE="HD1">IV. Request for Comments</HD>
                <P>The EPA is seeking comment and supporting data on the following:</P>
                <P>A. The chemical and microbial contaminants selected for the draft CCL 6.</P>
                <P>
                    B. The data sources the EPA obtained and evaluated for identifying the CCL 6 Chemical Universe and the CCL 6 Microbial Universe, that are provided in the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a) and 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c) located in the docket for this document and also on the EPA's website for CCL 6 (
                    <E T="03">https://www.epa.gov/ccl/draft-contaminant-candidate-list-6-ccl-6</E>
                    ).
                </P>
                <P>
                    C. The process the EPA used to screen the CCL 6 Chemical Universe and the CCL 6 Microbial Universe and develop the PCCL 6, that are described in the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a) and 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c).  
                </P>
                <P>
                    D. The process and supplemental data sources the EPA used for classification to select individual chemicals and microbes for the CCL 6 from the PCCL 6, that are described in the 
                    <E T="03">Chemical Technical Support Document</E>
                     (USEPA, 2026a) and 
                    <E T="03">Microbial Technical Support Document</E>
                     (USEPA, 2026c).
                </P>
                <P>E. The listing of the disinfection byproducts group on the draft CCL 6.</P>
                <P>F. The listing of the microplastics group on the draft CCL 6.</P>
                <P>G. The listing of the PFAS group on the draft CCL 6.</P>
                <P>H. The listing of the pharmaceuticals group on the draft CCL 6.</P>
                <HD SOURCE="HD1">V. The EPA's Next Steps</HD>
                <P>The EPA will evaluate comments received during the public comment period for this document. The EPA also plans to consult with the EPA's SAB. The EPA will consider the public comments and the SAB input to prepare the final CCL 6.</P>
                <HD SOURCE="HD1">VI. References</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        Battaglin, W.A., Bradley, P.M., Iwanowicz, L., Journey, C.A., Walsh, H.L. and Blazer, V.S. “Pharmaceuticals, hormones, pesticides, and other bioactive contaminants in water, sediment, and tissue from Rocky Mountain National Park, 2012-2013.” 
                        <E T="03">Science of the Total Environment,</E>
                         Volume 643, 1 December 2018.
                    </FP>
                    <FP SOURCE="FP-2">
                        Cohen, A.D. “Summit briefs policy-makers on drinking water safety.” 
                        <E T="03">American Association for the Advancement of Science—Sciencemag.org,</E>
                         Volume 368 Issue 6489, 24 April 2020.
                    </FP>
                    <FP SOURCE="FP-2">Federal Food, Drug, and Cosmetic Act. 21 U.S.C 321. 1938.</FP>
                    <FP SOURCE="FP-2">
                        Miller E., Sedlak, M., Lin, D., Box, C., Holleman, C., Rochman, C.M., and Sutton, R. “Recommended best practices for collecting, analyzing, and reporting microplastics in environmental media: Lessons learned from comprehensive monitoring of San Francisco Bay.” 
                        <E T="03">Journal of Hazardous Materials,</E>
                         Volume 409, 5 May 2021.
                    </FP>
                    <FP SOURCE="FP-2">
                        National Primary Drinking Water Regulations. Subpart Z—Control of Per- and Polyfluoroalkyl Substances (PFAS), 40 CFR 141.900 through 141.905. Available on the internet at: 
                        <E T="03">https://www.ecfr.gov/current/title-40/chapter-I/subchapter-D/part-141/subpart-Z</E>
                        .
                    </FP>
                    <FP SOURCE="FP-2">
                        Ragusa, A., Svelato, A., Criselda, S., Catalano, P., Notarstefano, V., Carnevali, O., Papa, F., Rongioletti, M.C.A., Baiocco, F., Draghi, S., D'Amore, E., Rinaldo, D., Matta, M., and Giorgini, E. “Plasticenta: First evidence of microplastics in human placenta.” 
                        <E T="03">Environment International,</E>
                         Volume 146, January 2021.
                    </FP>
                    <FP SOURCE="FP-2">
                        Schaider, L.A., Rudel, R.A., Ackerman, J.M., Dunagan, S.C., and Brody, J.G. “Pharmaceuticals, perfluorosurfactants, and other organic wastewater compounds in public drinking water wells in a shallow sand and gravel 
                        <PRTPAGE P="17195"/>
                        aquifer.” 
                        <E T="03">Science of the Total Environment,</E>
                         Volumes 468-469, Pages 384-393, 15 January 2014.
                    </FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2018. Basic Information on PFAS. Available at: 
                        <E T="03">https://www.epa.gov/pfas/basic-information-pfas.</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2019. EPA's Per- and Polyfluoroalkyl Substances (PFAS) Action Plan. EPA 823-R-18-004, February 2019. Available at: 
                        <E T="03">https://www.epa.gov/sites/production/files/2019-02/documents/pfas_action_plan_021319_508compliant_1.pdf.</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2022a. Drinking Water Contaminant Candidate List 5-Final. 
                        <E T="04">Federal Register</E>
                        . Vol. 87, No. 218. P. 68060, November 14, 2022.
                    </FP>
                    <FP SOURCE="FP-2">USEPA. 2022b. Review of the EPA's Draft Fifth Contaminant Candidate List (CCL 5). EPA-SAB-22-007, August 19, 2022.</FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2023a. Drinking Water Contaminant Candidate List 6-Nominations. 
                        <E T="04">Federal Register</E>
                        . Vol. 88, No. 33. P. 10316, February 17, 2023.
                    </FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2023b. Endocrine Disruptor Screening Program (EDSP) Estrogen Receptor Bioactivity. 
                        <E T="03">https://www.epa.gov/endocrine-disruption/endocrine-disruptor-screening-program-edsp-estrogen-receptor-bioactivity.</E>
                         Accessed June 2023.
                    </FP>
                    <FP SOURCE="FP-2">
                        USEPA. 2025. Announcement of Preliminary Regulatory Determinations for Contaminants on the Fifth Drinking Water Contaminant Candidate List. 
                        <E T="04">Federal Register</E>
                         Vol 90 Number 9 Page 3830. January 15, 2025.
                    </FP>
                    <FP SOURCE="FP-2">USEPA. 2026a. Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Chemical Contaminants. EPA 815-R-26-004, February 2026.</FP>
                    <FP SOURCE="FP-2">USEPA. 2026b. Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Contaminant Information Sheets. EPA 815-R-26-005, February 2026.</FP>
                    <FP SOURCE="FP-2">USEPA. 2026c. Technical Support Document for the Draft Sixth Contaminant Candidate List (CCL 6)—Microbial Contaminants. EPA 815-R-26-006, February 2026.</FP>
                    <FP SOURCE="FP-2">
                        Zarus, G.M., Muianga, C., Hunter, C.M., and Pappas, R.S. “A Review of Data for Quantifying Human Exposures to Micro and Nanoplastics and Potential Health Risks.” 
                        <E T="03">Science of the Total Environment,</E>
                         Volume 756, 20 February 2021.
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jessica L. Kramer,</NAME>
                    <TITLE>Assistant Administrator. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06662 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <CFR>42 CFR Parts 412 and 414</CFR>
                <DEPDOC>[CMS-1845-P]</DEPDOC>
                <RIN>RIN 0938-AV76</RIN>
                <SUBJECT>Medicare Program; Inpatient Rehabilitation Facility Prospective Payment System for Federal Fiscal Year 2027 and Updates to the IRF Quality Reporting Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This proposed rule would update the prospective payment rates for inpatient rehabilitation facilities (IRFs) for Federal fiscal year (FY) 2027. As required by statute, this proposed rule includes the classification and weighting factors for the IRF prospective payment system's case-mix groups and a description of the methodologies and data used in computing the prospective payment rates for FY 2027. It also continues the third year of the 3-year phaseout of the rural adjustment, which began in FY 2025. This proposed rule includes a solicitation for public comments on alternative data sources for the IRF PPS wage index; proposes to require all therapy treatments or therapy evaluations to begin within 36-hours from midnight on the day of admission; proposes to require a patient's current functional status be documented on the preadmission screening; proposes requirements for the initial Interdisciplinary Team meeting; and includes a request for information on potential future IRF PPS payment reform. Additionally, the proposed rule includes updates to the IRF Quality Reporting Program. Furthermore, the proposed rule includes changes to the Durable Medical Equipment, Prosthetics, Orthotics, and Supplies Competitive Bidding Program.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>To be assured consideration, comments must be received at one of the addresses provided below by June 1, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>In commenting, please refer to file code CMS-1845-P.</P>
                    <P>Comments, including mass comment submissions, must be submitted in one of the following three ways (please choose only one of the ways listed):</P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may submit electronic comments on this regulation to 
                        <E T="03">http://www.regulations.gov/docket/CMS-2026-1024.</E>
                         Follow the “Submit a comment” instructions.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1845-P, P.O. Box 8016, Baltimore, MD 21244-8016.
                    </P>
                    <P>Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>
                    <P>
                        3. 
                        <E T="03">By express or overnight mail.</E>
                         You may send written comments to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1845-P, Mail Stop C4-26-05, 7500 Security Boulevard, Baltimore, MD 21244-1850.
                    </P>
                    <P>
                        For information on viewing public comments, see the beginning of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">IRFcoverage@cms.hhs.gov,</E>
                         for general information.
                    </P>
                    <P>Kimberly Schwartz, (410) 786-2571, for information about the IRF payment policies, payment rates and coverage policies.</P>
                    <P>
                        Patricia Taft, 
                        <E T="03">Patricia.Taft@cms.hhs.gov,</E>
                         for readers who experience problems accessing online IRF-PPS documents.
                    </P>
                    <P>Ariel Cress, (410) 786-8571, for information about the IRF quality reporting program.</P>
                    <P>Austin Gutoski, (410) 786-1643, for information about the DMEPOS CBP.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Inspection of Public Comments:</E>
                     All comments received before the close of the comment period are available for viewing by the public, including any personally identifiable or confidential business information that is included in a comment. We post all comments received before the close of the comment period on the following website as soon as possible after they have been received: 
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the search instructions on that website to view public comments. CMS will not post on 
                    <E T="03">Regulations.gov</E>
                     public comments that make threats to individuals or institutions or suggest that the commenter will take actions to harm an individual. CMS continues to encourage individuals not to submit duplicative comments. We will post acceptable comments from multiple unique commenters even if the content is identical or nearly identical to other comments.
                </P>
                <P>
                    <E T="03">Plain Language Summary:</E>
                     In accordance with 5 U.S.C. 553(b)(4), a plain language summary of this rule 
                    <PRTPAGE P="17196"/>
                    may be found at 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <HD SOURCE="HD1">Availability of Certain Information Through the Internet on the CMS Website</HD>
                <P>
                    The IRF prospective payment system (IRF PPS) Addenda, along with other supporting documents and tables referenced in this proposed rule, are available on the CMS website at 
                    <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/InpatientRehabFacPPS.</E>
                     The technical reports that describe the analyses CMS conducted referenced in the payment reform RFI (Section VIII. of this proposed rule) can be found at 
                    <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/inpatient-rehabilitation/research.</E>
                </P>
                <P>
                    We note that prior to 2020, each rule or notice issued under the IRF PPS included a detailed reiteration of the various regulatory provisions that have affected the IRF PPS over the years. That discussion, which has been updated to reflect subsequent years, along with detailed background information for various other aspects of the IRF PPS, is now available on the CMS website at 
                    <E T="03">https://www.cms.gov/files/document/irf-regulatory-and-legislative-history.pdf.</E>
                </P>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <HD SOURCE="HD2">A. Purpose</HD>
                <P>This proposed rule would update the prospective payment rates for inpatient rehabilitation facilities (IRFs) for Fiscal Year (FY) 2027 (that is, for discharges occurring on or after October 1, 2026, and on or before September 30, 2027) under section 1886(j)(3)(C) of the Social Security Act (the Act). As required by section 1886(j)(5) of the Act, this proposed rule includes the classification and weighting factors for the IRF prospective payment system (PPS) case-mix groups (CMGs), and a description of the methodologies and data used in computing the prospective payment rates for FY 2027. In addition, the proposed rule includes a solicitation for public comments on alternative data sources for the IRF PPS wage index; proposes requirements by revising § 412.622(a)(3)(ii) to require all therapy treatments and/or therapy evaluations to begin within 36-hours from midnight on the day of admission (hereafter referred to as the 36-hour rule); proposes to revise § 412.622(a)(4)(i)(B) to require documentation of a patient's current functional status in the preadmission screening; proposes requirements for the initial Interdisciplinary Team (IDT) by revising § 412.622(a)(5) to require the meeting to occur by the 4th day of admission to align with the Plan of Care (POC) timeframe; and includes a Request for Information (RFI) on options to modernize and revise the primary diagnosis and comorbidity score methodology under the Skilled Nursing Facility Patient Driven Payment Model (PDPM) for the IRF PPS.</P>
                <P>For the IRF Quality Reporting Program (QRP), this proposed rule proposes the revision of the IRF QRP data submission deadlines beginning with the FY 2029 IRF QRP. We are also soliciting public comments through one RFI on future measure concepts for the IRF QRP.</P>
                <P>For the Durable Medical Equipment, Prosthetics, Orthotics, and Supplies (DMEPOS) Competitive Bidding Program (CBP), this rule proposes a higher bid surety bond amount for a bidding entity submitting a bid in Remote Item Delivery (RID) competitive bidding area.</P>
                <HD SOURCE="HD2">B. Summary of Major Provisions</HD>
                <P>In this proposed rule, we use the methods described in the FY 2026 IRF PPS final rule (90 FR 37678) to update the prospective payment rates for FY 2027 using the most current and complete data available at this time, which is FY 2025 IRF claims and FY 2024 IRF cost report data, as discussed in section VI. of this proposed rule. In addition, the proposed rule includes a proposal to revise the 36-Hour Rule at § 412.622(a)(3)(ii) to require all therapy treatments or therapy evaluations to begin within 36-hours from midnight on the day of admission, proposal to revise § 412.622(a)(4)(i)(B) to require documentation of a patient's current functional status in the preadmission screening and a proposal for an initial IDT meeting policy (§ 412.622(a)(5)(ii)) to occur by the 4th day of admission to align with the POC timeframe.</P>
                <P>The IRF proposed rule also provides an RFI on options to modernize the IRF PPS by leveraging and revising the primary diagnosis model and comorbidity score model used under the Skilled Nursing Facility Patient Driven Payment Model (PDPM). Additionally, we are soliciting comments on whether we should consider using alternative data sources to construct an IRF-specific wage index for potential use in future years to align with other CMS payment systems.</P>
                <P>For the IRF QRP, this proposed rule would propose a revision to the IRF QRP data submission deadlines beginning with the FY 2029 IRF QRP. We are also soliciting public comments through one RFI on future measure concepts for the IRF QRP.</P>
                <HD SOURCE="HD2">C. Summary of Impact</HD>
                <GPH SPAN="3" DEEP="105">
                    <GID>EP06AP26.055</GID>
                </GPH>
                <HD SOURCE="HD1">II. Background</HD>
                <HD SOURCE="HD2">A. Statutory Basis and Scope for IRF PPS Provisions</HD>
                <P>
                    Section 1886(j) of the Act provides for the implementation of a per-discharge PPS for inpatient rehabilitation hospitals and inpatient rehabilitation units of a hospital (collectively, hereinafter referred to as IRFs). Payments under the IRF PPS encompass inpatient operating and capital costs of furnishing covered rehabilitation services (that is, routine, ancillary, and capital costs), but not direct graduate medical education costs, costs of approved nursing and allied health education activities, bad debts, and other services or items outside the scope of the IRF PPS. A complete discussion of the IRF PPS provisions appears in the 
                    <PRTPAGE P="17197"/>
                    original FY 2002 IRF PPS final rule (66 FR 41316) and the FY 2006 IRF PPS final rule (70 FR 47880) and we provided a general description of the IRF PPS for FYs 2007 through 2019 in the FY 2020 IRF PPS final rule (84 FR 39055 through 39057). A general description of the IRF PPS for FYs 2020 through 2026, along with detailed background information for various other aspects of the IRF PPS, is now available on the CMS website at 
                    <E T="03">https://www.cms.gov/files/document/irf-regulatory-and-legislative-history.pdf.</E>
                      
                </P>
                <P>Under the IRF PPS from FYs 2002 through 2005, the prospective payment rates were computed across 100 distinct CMGs, as described in the FY 2002 IRF PPS final rule (66 FR 41316). We constructed 95 CMGs using rehabilitation impairment categories (RICs), functional status (both motor and cognitive), and age (in some cases, cognitive status and age may not be a factor in defining a CMG). In addition, we constructed five special CMGs to account for very short stays and for patients who expire in the IRF.</P>
                <P>For each of the CMGs, we developed relative weighting factors to account for a patient's clinical characteristics and expected resource needs. Thus, the weighting factors accounted for the relative difference in resource use across all CMGs. Within each CMG, we created tiers based on the estimated effects that certain comorbidities would have on resource use.</P>
                <P>We established the Federal PPS rates using a standardized payment conversion factor (formerly referred to as the budget-neutral conversion factor). For a detailed discussion of the budget-neutral conversion factor, please refer to our FY 2004 IRF PPS final rule (68 FR 45684 and 45685). In the FY 2006 IRF PPS final rule (70 FR 47880), we discussed in detail the methodology for determining the standard payment conversion factor.</P>
                <P>We applied the relative weighting factors to the standard payment conversion factor to compute the unadjusted prospective payment rates under the IRF PPS from FYs 2002 through 2005. Within the structure of the payment system, we then made adjustments to account for interrupted stays, transfers, short stays, and deaths. Finally, we applied the applicable adjustments to account for geographic variations in wages (wage index), the percentage of low- income patients, location in a rural area (if applicable), and outlier payments (if applicable) to the IRFs' unadjusted prospective payment rates.</P>
                <P>For cost reporting periods that began on or after January 1, 2002, and before October 1, 2002, we determined the final prospective payment amounts using the transition methodology prescribed in section 1886(j)(1) of the Act. Under this provision, IRFs transitioning into the PPS were paid a blend of the Federal IRF PPS rate and the payment that the IRFs would have received had the IRF PPS not been implemented. This provision also allowed IRFs to elect to bypass this blended payment and immediately be paid 100 percent of the Federal IRF PPS rate. The transition methodology expired as of cost reporting periods beginning on or after October 1, 2002 (FY 2003), and payments for all IRFs now consist of 100 percent of the Federal IRF PPS rate.</P>
                <P>Section 1886(j) of the Act confers broad statutory authority upon the Secretary to propose refinements to the IRF PPS. In the FY 2006 IRF PPS final rule (70 FR 47880) and in correcting amendments to the FY 2006 IRF PPS final rule (70 FR 57166), we finalized a number of refinements to the IRF PPS case-mix classification system (the CMGs and the corresponding relative weights) and the case-level and facility-level adjustments. These refinements included the adoption of the Office of Management and Budget's (OMB's) Core-Based Statistical Area market definitions; modifications to the CMGs, tier comorbidities; and CMG relative weights, implementation of a new teaching status adjustment for IRFs; rebasing and revising the market basket used to update IRF payments, and updates to the rural, low-income percentage (LIP), and high-cost outlier adjustments. Beginning with the FY 2006 IRF PPS final rule (70 FR 47908 through 47917), the market basket used to update IRF payments was a market basket reflecting the operating and capital cost structures for freestanding IRFs, freestanding inpatient psychiatric facilities (IPFs), and long-term care hospitals (LTCHs). Any reference to the FY 2006 IRF PPS final rule in this proposed rule also includes the provisions effective in the correcting amendments. For a detailed discussion of the final key policy changes for FY 2006, please refer to the FY 2006 IRF PPS final rule.</P>
                <P>
                    The regulatory history previously included in each rule or notice issued under the IRF PPS, including a general description of the IRF PPS for FYs 2007 through 2026, is available on the CMS website at 
                    <E T="03">https://www.cms.gov/files/document/irf-regulatory-and-legislative-history.pdf.</E>
                </P>
                <HD SOURCE="HD2">B. Provisions of the Affordable Care Act and the Medicare Access and CHIP Reauthorization Act of 2015 (MACRA) Affecting the IRF PPS in FY 2012 and Beyond</HD>
                <P>The Patient Protection and Affordable Care Act (Pub. L. 111-148) was enacted on March 23, 2010. The Health Care and Education Reconciliation Act of 2010 (Pub. L. 111-152), which amended and revised several provisions of the Patient Protection and Affordable Care Act, was enacted on March 30, 2010. In this proposed rule, we refer to the two statutes collectively as the “Affordable Care Act” or “ACA”.</P>
                <P>The ACA included several provisions that affect the IRF PPS in FYs 2012 and beyond. In addition to what was previously discussed, section 3401(d) of the ACA also added section 1886(j)(3)(C)(ii)(I) of the Act (providing for a “productivity adjustment” for FY 2012 and each subsequent FY). The productivity adjustment for FY 2027 is discussed in section VI. of this proposed rule. Section 1886(j)(3)(C)(ii)(II) of the Act provides that the application of the productivity adjustment to the market basket percentage increase may result in an update that is less than 0.0 for a FY and in payment rates for a FY being less than such payment rates for the preceding FY.</P>
                <P>
                    Section 3004(b) of the ACA and section 411(b) of the MACRA (Pub. L. 114-10, enacted on April 16, 2015) also addressed the IRF PPS. Section 3004(b) of ACA reassigned the previously designated section 1886(j)(7) of the Act to section 1886(j)(8) of the Act and inserted a new section 1886(j)(7) of the Act, which contains requirements for the Secretary to establish a QRP for IRFs. Under that program, data must be submitted in a form and manner and at a time specified by the Secretary. Beginning in FY 2014, section 1886(j)(7)(A)(i) of the Act requires the application of a 2-percentage point reduction to the IRF market basket percentage increase otherwise applicable to an IRF (after application of paragraphs (C)(iii) and (D) of section 1886(j)(3) of the Act) for a FY if the IRF does not comply with the requirements of the IRF QRP for that FY. Application of the 2-percentage point reduction may result in an update that is less than 0.0 for a FY and in payment rates for a FY being lower than payment rates for the preceding FY. Reporting-based reductions to the IRF market basket percentage increase are not cumulative; they only apply for the FY involved. Section 411(b) of the MACRA amended section 1886(j)(3)(C) of the Act by adding paragraph (iii), which required 
                    <PRTPAGE P="17198"/>
                    us to apply for FY 2018, after the application of section 1886(j)(3)(C)(ii) of the Act, an increase factor of 1.0 percent to update the IRF prospective payment rates.
                </P>
                <HD SOURCE="HD2">C. Operational Overview of the Current IRF PPS</HD>
                <P>As described in the FY 2002 IRF PPS final rule (66 FR 41316), upon the admission and discharge of a Medicare Part A fee-for-service (FFS) patient, the IRF is required to complete the appropriate sections of a Patient Assessment Instrument (PAI), designated as the IRF-PAI. In addition, beginning with IRF discharges occurring on or after October 1, 2009, the IRF is also required to complete the appropriate sections of the IRF-PAI upon the admission and discharge of each Medicare Advantage (MA) patient, as described in the FY 2010 IRF PPS final rule (74 FR 39762) and the FY 2010 IRF PPS correction notice (74 FR 50712). All required data must be electronically encoded into the IRF-PAI software product. Generally, the software product includes patient classification programming called the Grouper software. The Grouper software uses specific IRF-PAI data elements to classify (or group) patients into distinct CMGs and account for the existence of any relevant comorbidities.</P>
                <P>
                    The Grouper software produces a five-character CMG number. The first character is an alphabetic character that indicates the comorbidity tier. The last four characters are numeric characters that represent the distinct CMG number. A free download of the Grouper software is available on the CMS website at 
                    <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/InpatientRehabFacPPS/Software.html.</E>
                     The Grouper software is also embedded in the internet Quality Improvement and Evaluation System (iQIES) User tool available in iQIES at 
                    <E T="03">https://www.cms.gov/medicare/quality-safety-oversight-general-information/iqies.</E>
                </P>
                <P>Once a Medicare Part A FFS patient is discharged, the IRF submits a Medicare claim as a Health Insurance Portability and Accountability Act of 1996 (HIPAA) (Pub. L. 104-191, 110 Stat. 1936 August 21, 1996) compliant electronic claim or, if the Administrative Simplification Compliance Act of 2002 (ASCA) (Pub. L. 107-105, enacted on December 27, 2002) permits, a paper claim (a UB-04 or a CMS-1450 as appropriate) using the five-character CMG number and sends it to the appropriate Medicare Administrative Contractor (MAC). In addition, once an MA patient is discharged, in accordance with the Medicare Claims Processing Manual, chapter 3, section 20.3 (Pub. 100-04), hospitals (including IRFs) must submit to their MAC an informational-only bill (type of bill (TOB) 111) that includes Condition Code 04. This will ensure that the MA days are included in the hospital's Supplemental Security Income (SSI) ratio (used in calculating the IRF LIP adjustment) for FY 2007 and beyond. Claims submitted to Medicare must comply with both ASCA and HIPAA.</P>
                <P>
                    Section 3 of the ASCA amended section 1862(a) of the Act by adding paragraph (22), which requires the Medicare program, subject to section 1862(h) of the Act, to deny payment under Part A or Part B for any expenses for items or services for which a claim is submitted other than in an electronic form specified by the Secretary. Section 1862(h) of the Act, in turn, provides that the Secretary shall waive such denial in situations in which there is no method available for the submission of claims in an electronic form or the entity submitting the claim is a small provider. In addition, the Secretary also has the authority to waive such denial in such unusual cases as the Secretary finds appropriate. For more information, see the “Medicare Program; Electronic Submission of Medicare Claims” final rule (70 FR 71008). Our instructions for the limited number of Medicare claims submitted on paper are available at 
                    <E T="03">https://www.cms.gov/manuals/downloads/clm104c25.pdf.</E>
                </P>
                <P>
                    Section 3 of the ASCA operates in the context of the administrative simplification provisions of HIPAA, which include, among others, the requirements for transaction standards and code sets codified in 45 CFR part 160 and part 162, subparts A and I through R (generally known as the Transactions Rule). The Transactions Rule requires covered entities, including covered healthcare providers, to conduct covered electronic transactions according to the applicable transaction standards. (See the CMS program claim memoranda at 
                    <E T="03">https://www.cms.gov/ElectronicBillingEDITrans/</E>
                     and listed in the addenda to the Medicare Intermediary Manual, Part 3, section 3600).
                </P>
                <P>The MAC processes the claim through its software system. This software system includes pricing programming called the “Pricer” software. The Pricer software uses the CMG number, along with other specific claim data elements and provider-specific data, to adjust the IRF's prospective payment for interrupted stays, transfers, short stays, and deaths, and then applies the applicable adjustments to account for the IRF's wage index, percentage of low-income patients, rural location, and outlier payments. For discharges occurring on or after October 1, 2005, the IRF PPS payment also reflects the teaching status adjustment that became effective as of FY 2006, as discussed in the FY 2006 IRF PPS final rule (70 FR 47880).</P>
                <HD SOURCE="HD1">III. Summary of Provisions of the Proposed Rule</HD>
                <P>In this FY 2027 IRF PPS proposed rule, we are proposing to update the IRF PPS for FY 2027 and the IRF QRP for FY 2027 and FY 2029.</P>
                <P>The proposed policy changes and updates to the IRF prospective payment rates for FY 2027 will be as follows:</P>
                <P>• Update the CMG relative weights and average length of stay values for FY 2027 in a budget neutral manner, as discussed in section IV. of this proposed rule.</P>
                <P>• Update the IRF PPS payment rates for FY 2027 by the IRF market basket percentage increase, based upon the most current data available, with a productivity adjustment required by section 1886(j)(3)(C)(ii)(I) of the Act, as described in section V. of this proposed rule.</P>
                <P>• Update the FY 2027 IRF PPS payment rates by the FY 2027 wage index, applying the third year of the phase-out of the rural adjustment for IRFs transitioning from rural to urban, and the labor-related share in a budget-neutral manner, as discussed in section V. of this proposed rule.</P>
                <P>• Solicit public comments on alternative data sources for the wage index, as discussed in section V. of this proposed rule.  </P>
                <P>• Describe the calculation of the IRF standard payment conversion factor for FY 2027, as discussed in section V. of this proposed rule.</P>
                <P>• Update the outlier threshold amount for FY 2027, as discussed in section VI. of this proposed rule.</P>
                <P>• Update the cost-to-charge ratio (CCR) ceiling and urban/rural average CCRs for FY 2027, as discussed in section VI. of this proposed rule.</P>
                <P>• Proposal to require all therapy treatments or therapy evaluations to begin within 36-hours from midnight on the day of admission (§ 412.622(a)(3)(ii)), as discussed in section VII. of this proposed rule.</P>
                <P>• Proposal to require the patient's current functional status is documented in the preadmission screening (§ 412.622(a)(4)(i)(B)), as discussed in section VII. of this proposed rule.</P>
                <P>
                    • Proposal to require the initial IDT meeting to occur by the 4th day of 
                    <PRTPAGE P="17199"/>
                    admission and align with the POC timeframe (§ 412.622(a)(5)(ii)), as discussed in section VII. of this proposed rule.
                </P>
                <P>• The RFI on updating the IRF payment system to explore options to modernize the IRF PPS by leveraging the existing clinical classification and comorbidity score methodology used by the Skilled Nursing Facility (SNF) Patient Driven Payment Model (PDPM) to group patients by case mix, as discussed in section VIII. of this proposed rule.</P>
                <P>The proposed policy changes and updates to the IRF QRP for FY 2029 are as follows:</P>
                <P>• Revise the IRF QRP data submission deadlines.</P>
                <P>• Request for information on future measure concepts.</P>
                <P>• The proposed policy change and update to the DMEPOS Competitive Bidding Program (CBP) is as follows:</P>
                <P>• Update the bid surety bond requirement to require a higher bid surety bond amount for a bidding entity submitting a bid under a Remote Item Delivery competitive bidding program.</P>
                <HD SOURCE="HD1">IV. Proposed Updates to the CMG Relative Weights and Average Length of Stay (ALOS) Values for FY 2027</HD>
                <P>As specified in § 412.620(b)(1), we calculate a relative weight for each CMG that is proportional to the resources needed for an average inpatient rehabilitation case in that CMG. For example, cases in a CMG with a relative weight of 2, on average, will cost twice as much as cases in a CMG with a relative weight of 1. Relative weights account for the variance in cost per discharge due to the variance in resource utilization among the payment groups, and their use helps to ensure that IRF PPS payments support beneficiary access to care, as well as provider efficiency.</P>
                <P>In this proposed rule, we would update the CMG relative weights and ALOS values for FY 2027. Typically, we use the most recent available data to update the CMG relative weights and ALOS values. For FY 2027, we are using the FY 2025 IRF claims and FY 2024 IRF cost report data (CMS Form 2552-10, OMB No 0938-0050). These data are the most current and complete data available at the time of this proposed rule. Currently, only a small portion of the FY 2025 IRF cost report data is available for analysis, but the majority of the FY 2025 IRF claims data are available for analysis.</P>
                <P>In this FY 2027 IRF PPS proposed rule, we are proposing that if more recent data become available after the publication of the proposed rule and before the publication of the final rule, we would use such data to determine the FY 2027 CMG relative weights and ALOS values in the final rule.</P>
                <P>We propose to apply these data using the same methodologies that we have used to update the CMG relative weights and ALOS values each FY since we implemented an update to the methodology. The detailed CCR data from the cost reports of IRF provider units of primary acute care hospitals is used for this methodology, instead of CCR data from the associated primary care hospitals, to calculate IRFs' average costs per case, as discussed in the FY 2009 IRF PPS final rule (73 FR 46372). In calculating the CMG relative weights, we use a hospital-specific relative value method to estimate the operating (routine and ancillary services) and capital costs of IRFs. The process to calculate the CMG relative weights for this proposed rule is as follows:</P>
                <P>
                    <E T="03">Step 1.</E>
                     We estimate the effects that comorbidities have on costs.
                </P>
                <P>
                    <E T="03">Step 2.</E>
                     We adjust the cost of each Medicare discharge (case) to reflect the effects found in Step 1.
                </P>
                <P>
                    <E T="03">Step 3.</E>
                     We use the adjusted costs from Step 2 to calculate CMG relative weights, using the hospital-specific relative value method.
                </P>
                <P>
                    <E T="03">Step 4.</E>
                     We normalize the FY 2027 CMG relative weights using a normalization factor that results in the average CMG relative weights in FY 2027 being the same as the average CMG relative weights in the FY 2026 IRF PPS final rule (90 FR 37678).
                </P>
                <P>Consistent with the methodology that we have used to update the IRF classification system in each instance in the past, we are proposing to update the CMG relative weights for FY 2027 in such a way that total estimated aggregate payments to IRFs for FY 2027 are the same with or without the changes (that is, in a budget-neutral manner) by applying a budget neutrality factor to the standard payment amount. To calculate the appropriate budget neutrality factor for use in updating the FY 2027 CMG relative weights, we use the following steps:</P>
                <P>
                    <E T="03">Step 1.</E>
                     Calculate the estimated total amount of IRF PPS payments for FY 2027 (with no changes to the CMG relative weights).
                </P>
                <P>
                    <E T="03">Step 2.</E>
                     Calculate the estimated total amount of IRF PPS payments for FY 2027 by applying the proposed changes to the CMG relative weights (as discussed in this proposed rule).
                </P>
                <P>
                    <E T="03">Step 3.</E>
                     Divide the amount calculated in Step 1 by the amount calculated in Step 2 to determine the budget neutrality factor of 0.9990 that would maintain the same total estimated aggregate payments in FY 2027 with and without the proposed changes to the final CMG relative weights.
                </P>
                <P>
                    <E T="03">Step 4.</E>
                     Apply the budget neutrality factor from Step 3 to the FY 2027 IRF PPS standard payment amount after the application of the budget-neutral wage adjustment factor.
                </P>
                <P>In section V. of this proposed rule, we discuss the proposed use of the existing methodology to calculate the proposed standard payment conversion factor for FY 2027.</P>
                <P>In Table 2, “Proposed Relative Weights and Average Length of Stay Values for Case -Mix Groups,” we present the proposed CMGs, the comorbidity tiers, the corresponding relative weights, and the ALOS values for each CMG and tier for FY 2027. The ALOS for each CMG is used to determine when an IRF discharge meets the definition of a short stay transfer, which results in a per diem case level adjustment.</P>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17200"/>
                    <GID>EP06AP26.056</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17201"/>
                    <GID>EP06AP26.057</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17202"/>
                    <GID>EP06AP26.058</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="17203"/>
                    <GID>EP06AP26.059</GID>
                </GPH>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                <P>Generally, updates to the CMG relative weights result in some increases and some decreases to the CMG relative weight values. Table 3 shows how we estimate that the application of the proposed revisions for FY 2027 would affect particular CMG relative weight values, which would affect the overall distribution of payments within CMGs and tiers. We note that, because we propose to implement the CMG relative weight revisions in a budget-neutral manner (as previously described), total estimated aggregate payments to IRFs for FY 2027 would not be affected as a result of the proposed CMG relative weight revisions. However, the proposed revisions will affect the distribution of payments within CMGs and tiers.</P>
                <GPH SPAN="3" DEEP="109">
                    <PRTPAGE P="17204"/>
                    <GID>EP06AP26.060</GID>
                </GPH>
                <P>As shown in Table 3, 99.4 percent of all IRF cases are in CMGs and tiers that would experience less than a 5 percent change (either increase or decrease) in the CMG relative weight value as a result of the proposed revisions for FY 2027. The proposed changes in the ALOS values for FY 2027, compared with the FY 2026 ALOS values, are small and do not show any particular trends in IRF length of stay patterns.</P>
                <P>The methodology that we use to update the CMG relative weights uses the most recent cost data reported by IRFs to compute relative weights that reflect the relative costliness of different IRF cases in a budget neutral manner. We increase or decrease relative weights of the CMGs annually, including for those CMGs associated with the 13 conditions that qualify for the 60 percent rule, under 42 CFR 412.29(b)(2), based only on the cost data reported to us by IRFs each year. We believe that these data accurately reflect the severity of the IRF patient population and the associated costs of caring for these patients in the IRF setting. The CMG relative weights are updated each year based on the most recent available data for the full population of IRF Medicare fee-for-service beneficiaries. This ensures that the IRF case-mix system is as reflective as possible of changes in the IRF patient populations and the associated coding practices and ensures that IRF payments appropriately reflect the relative costs of caring for all types of IRF patients.  </P>
                <HD SOURCE="HD1">V. FY 2027 IRF PPS Payment Update</HD>
                <HD SOURCE="HD2">A. Background</HD>
                <P>Section 1886(j)(3)(C) of the Act requires the Secretary to establish an increase factor that reflects changes over time in the prices of an appropriate mix of goods and services for which payment is made under the IRF PPS. According to section 1886(j)(3)(A)(i) of the Act, the increase factor shall be used to update the IRF prospective payment rates for each FY. Section 1886(j)(3)(C)(ii)(I) of the Act requires the application of the productivity adjustment described in section 1886(b)(3)(B)(xi)(II) of the Act. Thus, we propose to update the IRF PPS payments for FY 2027 by a market basket percentage increase as required by section 1886(j)(3)(C) of the Act based upon the most current data available, with a productivity adjustment as required by section 1886(j)(3)(C)(ii)(I) of the Act.</P>
                <P>We have utilized various market baskets through the years in the IRF PPS. For a discussion of these market baskets, we refer readers to the FY 2016 IRF PPS final rule (80 FR 47046).</P>
                <P>Beginning with FY 2024, we finalized a rebased and revised IRF market basket to reflect a 2021 base year. The FY 2024 IRF PPS final rule (88 FR 50966 through 50988) contains a complete discussion of the development of the 2021-based IRF market basket.</P>
                <HD SOURCE="HD2">B. Proposed FY 2027 Market Basket Update and Productivity Adjustment</HD>
                <HD SOURCE="HD3">1. Proposed FY 2027 Market Basket Update</HD>
                <P>For FY 2027 (that is, beginning October 1, 2026, and ending September 30, 2027), we propose to update the IRF PPS payments by a market basket percentage increase as required by section 1886(j)(3)(C) of the Act, with a productivity adjustment as required by section 1886(j)(3)(C)(ii)(I) of the Act. For FY 2027, we propose to use the same methodology described in the FY 2026 IRF PPS final rule (90 FR 37687 through 37691).</P>
                <P>
                    Consistent with historical practice, we propose to estimate the market basket update for the IRF PPS for FY 2027 based on the most recently available data at the time of rulemaking. For this proposed rule, based on IHS Global Inc.'s (IGI) fourth quarter 2025 forecast with historical data through the third quarter of 2025, the proposed 2021-based IRF market basket percentage increase for FY 2027 is projected to be 3.2 percent. IGI is a nationally recognized economic and financial forecasting firm with which CMS contracts to forecast the components of the market baskets.
                    <SU>1</SU>
                    <FTREF/>
                     We also propose that if more recent data become available after the publication of the proposed rule and before the publication of the final rule (for example, a more recent estimate of the market basket percentage increase or productivity adjustment), we would use such data, if appropriate, to determine the FY 2027 IRF market basket update in the final rule.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">https://www.spsglobal.com/en</E>
                        .
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Proposed FY 2027 Productivity Adjustment</HD>
                <P>Section 1886(j)(3)(C)(ii) of the Act requires that, after establishing the increase factor for a FY, the Secretary shall reduce such increase factor for FY 2012 and each subsequent FY, by the productivity adjustment described in section 1886(b)(3)(B)(xi)(II) of the Act. Section 1886(b)(3)(B)(xi)(II) of the Act sets forth the definition of this productivity adjustment. The statute defines the productivity adjustment to be equal to the 10-year moving average of changes in annual economy-wide, private nonfarm business multifactor productivity (as projected by the Secretary for the 10-year period ending with the applicable FY, year, cost reporting period, or other annual period) (the “productivity adjustment”).</P>
                <P>
                    The U.S. Department of Labor's Bureau of Labor Statistics (BLS) publishes the official measures of productivity for the U.S. economy. The productivity measure referenced in section 1886(b)(3)(B)(xi)(II) of the Act is published by BLS as private nonfarm business total factor productivity (TFP) previously referred to as multifactor productivity).
                    <SU>2</SU>
                    <FTREF/>
                     We refer readers to 
                    <E T="03">https://www.bls.gov/productivity/</E>
                     for the BLS historical published TFP data. A complete description of IGI's TFP projection methodology is available on the CMS website at 
                    <E T="03">
                        https://www.cms.gov/data-research/statistics-trends-and-reports/medicare-program-
                        <PRTPAGE P="17205"/>
                        rates-statistics/market-basket-research-and-information.
                    </E>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">https://www.bls.gov/productivity/notices/2021/mfp-to-tfp-term-change.htm.</E>
                    </P>
                </FTNT>
                <P>For this FY 2027 IRF PPS proposed rule, based on IGI's fourth quarter 2025 forecast, the 10-year moving average growth of TFP for FY 2027 is projected to be 0.8 percent. In accordance with section 1886(j)(3)(C) of the Act, we propose to base the FY 2027 IRF market basket percentage increase, which is used to determine the applicable percentage increase for the IRF payments, on IGI's fourth quarter 2025 forecast of the 2021-based IRF market basket. We propose to then reduce the market basket percentage increase by the proposed productivity adjustment for FY 2027 of 0.8 percentage point (the 10-year moving average growth of TFP for the period ending FY 2027 based on IGI's fourth quarter 2025 forecast). Therefore, the proposed FY 2027 IRF market basket update is 2.4 percent (3.2 percent market basket percentage increase reduced by the 0.8 percentage point productivity adjustment). Furthermore, we propose that if more recent data become available after the publication of the proposed rule and before the publication of the final rule (for example, a more recent estimate of the market basket percentage increase and productivity adjustment), we would use such data, if appropriate, to determine the FY 2027 IRF market basket percentage increase and productivity adjustment in the final rule.</P>
                <P>
                    In its March 2026 Report to Congress, MedPAC recommended that Congress should reduce the IRF PPS base payment rate by 7 percent for FY 2027.
                    <SU>3</SU>
                    <FTREF/>
                     As discussed, and in accordance with sections 1886(j)(3)(C) and 1886(j)(3)(D) of the Act, the Secretary proposes to update the IRF PPS payment rates for FY 2027 by the proposed IRF market basket update of 2.4 percent. Section 1886(j)(3)(C) of the Act does not provide the Secretary with the authority to apply a different update factor to IRF PPS payment rates for FY 2027.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         March 2026 Report to the Congress: Medicare Payment Policy.
                    </P>
                </FTNT>
                <P>We invite public comments on our proposals for the FY 2027 market basket percentage increase and productivity adjustment.</P>
                <HD SOURCE="HD2">C. Proposed FY 2027 IRF Labor-Related Share</HD>
                <P>Section 1886(j)(6) of the Act specifies that the Secretary is to adjust the proportion (as estimated by the Secretary from time to time) of IRFs' costs that are attributable to wages and wage-related costs, of the prospective payment rates computed under section 1886(j)(3) of the Act, for area differences in wage levels by a factor (established by the Secretary) reflecting the relative hospital wage level in the geographic area of the rehabilitation facility compared to the national average wage level for such facilities. The labor-related share is determined by identifying the national average proportion of total costs that are related to, influenced by, or vary with the local labor market. We propose to continue to classify a cost category as labor-related if the costs are labor-intensive and vary with the local labor market.</P>
                <P>Based on our definition of the labor-related share and the cost categories in the 2021-based IRF market basket, we propose to calculate the labor-related share for FY 2027 as the sum of the FY 2027 relative importance of Wages and Salaries, Employee Benefits, Professional Fees: Labor-Related, Administrative and Facilities Support Services, Installation, Maintenance, and Repair Services, All Other: Labor-Related Services, and a portion of the Capital-Related relative importance from the 2021-based IRF market basket. For more details regarding the methodology for determining specific cost categories for inclusion in the 2021-based IRF labor-related share, see the FY 2024 IRF PPS final rule (88 FR 50985 through 50988).</P>
                <P>The relative importance reflects the different rates of price change for these cost categories between the base year (2021) and FY 2027. We calculate the labor-related relative importance from the IRF market basket, and it approximates the labor-related portion of the total costs after taking into account historical and projected price changes between the base year and FY 2027. The price proxies that move the different cost categories in the market basket do not necessarily change at the same rate, and the relative importance captures these changes. Based on IGI's fourth quarter 2025 forecast of the 2021-based IRF market basket, the sum of the FY 2027 relative importance for Wages and Salaries, Employee Benefits, Professional Fees: Labor-Related, Administrative and Facilities Support Services, Installation Maintenance &amp; Repair Services, and All Other: Labor-Related Services is 70.8 percent. We propose that the portion of Capital-Related costs that are influenced by the local labor market is 46 percent. Since the relative importance for Capital-Related costs is 8.1 percent of the 2021-based IRF market basket for FY 2027, we propose to take 46 percent of 8.1 percent to determine the labor-related share of Capital-Related costs for FY 2027 which is 3.7 percent. Therefore, we propose a total labor-related share for FY 2027 of 74.5 percent (the sum of 70.8 percent for the proposed labor-related share of operating costs and 3.7 percent for the proposed labor-related share of Capital-Related costs). We propose that if more recent data subsequently become available after publication of the proposed rule and before the publication of the final rule (for example, a more recent estimate of the labor-related share), we would use such data, if appropriate, to determine the FY 2027 IRF labor-related share in the final rule.</P>
                <P>Table 4 shows the current estimate of the proposed FY 2027 labor-related share and the FY 2026 final labor-related share using the 2021-based IRF market basket relative importance.</P>
                <GPH SPAN="3" DEEP="228">
                    <PRTPAGE P="17206"/>
                    <GID>EP06AP26.061</GID>
                </GPH>
                <P>We invite public comments on the proposed labor-related share for FY 2027.  </P>
                <HD SOURCE="HD2">D. Proposed Wage Adjustment for FY 2027</HD>
                <HD SOURCE="HD3">1. Background</HD>
                <P>Section 1886(j)(6) of the Act requires the Secretary to adjust the proportion of rehabilitation facilities' costs attributable to wages and wage-related costs (as estimated by the Secretary from time to time) by a factor (established by the Secretary) reflecting the relative hospital wage level in the geographic area of the rehabilitation facility compared to the national average wage level for those facilities. The Secretary is required to update the IRF PPS wage index on the basis of information available to the Secretary on the wages and wage-related costs to furnish rehabilitation services. Any adjustments or updates made under section 1886(j)(6) of the Act for a FY are made in a budget-neutral manner.</P>
                <P>In the FY 2023 IRF PPS final rule (87 FR 47054 through 47056) we finalized a policy to apply a 5-percent cap on any decrease to a provider's wage index from its wage index in the prior year, regardless of the circumstances causing the decline. We amended IRF PPS regulations at § 412.624(e)(1)(ii) to reflect this permanent cap on wage index decreases. Additionally, we finalized a policy that a new IRF would be paid the wage index for the area in which it is geographically located for its first full or partial FY with no cap applied because a new IRF would not have a wage index in the prior FY. A full discussion of the adoption of this policy is found in the FY 2023 IRF PPS final rule.</P>
                <P>For FY 2027, we propose to maintain the policies and methodologies described in the FY 2026 IRF PPS final rule (90 FR 37678 related to the labor market area definitions and the wage index methodology for areas with wage data. Thus, we use the core based statistical areas (CBSAs) labor market area definitions and the FY 2027 pre-reclassification and pre-floor hospital wage index data. In accordance with section 1886(d)(3)(E) of the Act, the FY 2027 pre-reclassification and pre-floor hospital wage index is based on data submitted for hospital cost reporting periods beginning on or after October 1, 2022, and before October 1, 2023 (that is, FY 2024 cost report data).</P>
                <P>In addition, we will continue to use the same methodology discussed in the FY 2008 IRF PPS final rule (72 FR 44299) to address those geographic areas in which there are no hospitals and, thus, no hospital wage index data on which to base the calculation for the FY 2027 IRF PPS wage index. For FY 2027, the only rural area without wage index data available is in North Dakota. For urban areas without specific hospital wage index data, we will continue using the average wage indexes of all urban areas within the State to serve as a reasonable proxy for the wage index of that urban CBSA as proposed and finalized in FY 2006 (70 FR 47927). For FY 2027, the only urban area without wage index data available is CBSA 25980, Hinesville Fort Stewart, Georgia.</P>
                <P>For FY 2027, we are proposing to continue to use the concurrent pre-floor, pre-reclassified IPPS hospital wage index as the basis for the IRF wage index. We continue to consider this an appropriate source of wage index data to estimate costs per day, consistent with our wage index policy at §  412.624(e)(1). At the same time, we routinely assess whether more recent or alternative data sources may further enhance the accuracy and representativeness of our estimates. We note that other payment systems have explored and are exploring alternative wage index methodologies under their specific programmatic and statutory circumstances. For example, CMS finalized changes to the End-Stage Renal Disease (ESRD) PPS wage index using the Bureau of Labor Statistics (BLS) occupation-level wage data in the CY 2025 ESRD PPS final rule (89 FR 89084). While this approach was developed under the specific programmatic and statutory circumstances of the ESRD PPS and may not be directly transferable to the IRF PPS, CMS is interested in exploring whether similar methodologies using publicly available wage data could be adapted to reflect the geographic variation in labor costs for inpatient rehabilitation facilities.</P>
                <P>
                    In its 2023 Report to Congress,
                    <SU>4</SU>
                    <FTREF/>
                     MedPAC discussed various conceptual approaches to Medicare wage indexes, including the use of county-level wage data from BLS with an occupational mix to construct wage indexes that are more specific to the payment setting. MedPAC has previously written about using all-employer, occupation-level 
                    <PRTPAGE P="17207"/>
                    wage data to establish different weights for setting-specific occupational labor mixes as one approach to geographic adjustments.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">https://www.medpac.gov/document/june-2023-report-to-the-congress-medicare-and-the-health-care-delivery-system/ https://www.medpac.gov/wp-content/uploads/2022/07/Wage-index-March-2023-SEC.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    We are soliciting comments on whether we should consider using alternative data sources to construct an IRF-specific wage index for potential use in future years. CMS seeks feedback to understand the potential advantages and limitations of using alternative data sources, such as BLS data and IRF cost reports, as well as other methodologies that interested parties believe could appropriately reflect the geographic variation in labor costs for IRFs. In addition, as discussed elsewhere in the 
                    <E T="04">Federal Register</E>
                    , we note that we are also considering the potential use of alternative data sources in other payment systems including the Inpatient Facilities PPS, Skilled Nursing Facilities PPS, and Hospice PPS. We seek feedback on the unique considerations applicable to IRFs that should inform how CMS considers the potential use of alternative data sources.
                </P>
                <P>We invite public comments on our proposals regarding the Wage Adjustment for FY 2027 and on the potential use of alternative data sources for the IRF PPS Wage index.</P>
                <HD SOURCE="HD3">2. Core-Based Statistical Areas (CBSAs) for the FY 2027 IRF Wage Index</HD>
                <P>
                    The wage index used for the IRF PPS is calculated using the pre-reclassification and pre-floor hospital wage index data and is assigned to the IRF on the basis of the labor market area in which the IRF is geographically located. IRF labor market areas are delineated based on the CBSAs established by the OMB. The CBSA delineations (which were implemented for the IRF PPS beginning with FY 2016) are based on revised OMB delineations issued on February 28, 2013, in OMB Bulletin No. 13-01. OMB Bulletin No. 13-01 established- revised delineations for Metropolitan Statistical Areas, Micropolitan Statistical Areas, and Combined Statistical Areas in the United States and Puerto Rico based on the 2010 Census and provided guidance on the use of the delineations of these statistical areas using standards published in the June 28, 2010, 
                    <E T="04">Federal Register</E>
                     (75 FR 37246 through 37252). We refer readers to the FY 2016 IRF PPS final rule (80 FR 47068 through 47076) for a full discussion of our implementation of the OMB labor market area delineations beginning with the FY 2016 wage index.
                </P>
                <P>Generally, OMB issues major revisions to statistical areas every 10 years, based on the results of the decennial census. Additionally, OMB occasionally issues updates and revisions to the statistical areas in between decennial censuses to reflect the recognition of new areas or the addition of counties to existing areas. In some instances, these updates merge formerly separate areas, transfer components of an area from one area to another or drop components from an area. On July 15, 2015, OMB issued OMB Bulletin No. 15-01, which provides minor updates to and supersedes OMB Bulletin No. 13-01 that was issued on February 28, 2013. The attachment to OMB Bulletin No. 15-01 provides detailed information on the update to statistical areas since February 28, 2013. The updates provided in OMB Bulletin No. 15-01 are based on the application of the 2010 Standards for Delineating Metropolitan and Micropolitan Statistical Areas to Census Bureau population estimates for July 1, 2012, and July 1, 2013.</P>
                <P>In the FY 2018 IRF PPS final rule (82 FR 36250 through 36251), we adopted the updates set forth in OMB Bulletin No. 15-01 effective October 1, 2017, beginning with the FY 2018 IRF wage index. For a complete discussion of the adoption of the updates set forth in OMB Bulletin No. 15-01, we refer readers to the FY 2018 IRF PPS final rule. In the FY 2019 IRF PPS final rule (83 FR 38527), we continued to use the OMB delineations that were adopted beginning with FY 2016 to calculate the area wage indexes, with updates set forth in OMB Bulletin No. 15-01 that we adopted beginning with the FY 2018 wage index.  </P>
                <P>On August 15, 2017, OMB issued OMB Bulletin No. 17-01, which provided updates to and superseded OMB Bulletin No. 15-01 that was issued on July 15, 2015. The attachments to OMB Bulletin No. 17-01 provide detailed information on the update to statistical areas since July 15, 2015, and are based on the application of the 2010 Standards for Delineating Metropolitan and Micropolitan Statistical Areas to Census Bureau population estimates for July 1, 2014, and July 1, 2015. In the FY 2020 IRF PPS final rule (84 FR 39090 through 39091), we adopted the updates set forth in OMB Bulletin No. 17-01 effective October 1, 2019, beginning with the FY 2020 IRF wage index.</P>
                <P>
                    On April 10, 2018, OMB issued OMB Bulletin No. 18-03, which superseded the August 15, 2017 OMB Bulletin No. 17-01, and on September 14, 2018, OMB issued OMB Bulletin No. 18-04, which superseded the April 10, 2018 OMB Bulletin No. 18-03. These bulletins established revised delineations for Metropolitan Statistical Areas, Micropolitan Statistical Areas, and Combined Statistical Areas, and provided guidance on the use of the delineations of these statistical areas. A copy of this bulletin may be obtained at 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2018/09/Bulletin-18-04.pdf.</E>
                </P>
                <P>
                    To this end, as discussed in the FY 2021 IRF PPS proposed (85 FR 22075 through 22079) and final (85 FR 48434 through 48440) rules, we adopted the revised OMB delineations identified in OMB Bulletin No. 1804 (available at 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2018/09/Bulletin-18-04.pdf</E>
                    ) beginning October 1, 2020, including a 1 year transition for FY 2021 under which we applied a 5-percent cap on any decrease in an IRF's wage index compared to its wage index for the prior fiscal year (FY 2020). The updated OMB delineations more accurately reflect the contemporary urban and rural nature of areas across the country, and the use of such delineations allows us to determine more accurately the appropriate wage index and rate tables to apply under the IRF PPS. OMB issued further revised CBSA delineations in OMB Bulletin No. 20-01, on March 6, 2020 (available on the web at 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2020/03/Bulletin-20-01.pdf</E>
                    ). However, we determined that the changes in OMB Bulletin No. 20-01 do not impact the CBSA-based labor market area delineations adopted in FY 2021. Therefore, we did not propose to adopt the revised OMB delineations identified in OMB Bulletin No. 20-01 for FY 2022 through FY 2024.
                </P>
                <P>
                    On July 21, 2023, OMB issued OMB Bulletin No. 23-01 (available at 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2023/07/OMB-Bulletin-23-01.pdf</E>
                    ) which updates and supersedes OMB Bulletin No. 20-01 based upon the 2020 Standards for Delineating Core Based Statistical Areas (“the 2020 Standards”) published by OMB on July 16, 2021 (86 FR 37770). OMB Bulletin No. 23-01 revised CBSA delineations that are comprised of counties and equivalent entities (for example, boroughs; a city and borough; and a municipality in Alaska; planning regions in Connecticut; parishes in Louisiana; municipios in Puerto Rico; and independent cities in Maryland, Missouri, Nevada, and Virginia). As discussed in the FY 2025 IRF PPS final rule (89 FR 64291 through 64304), we adopted the revised OMB delineations identified in OMB Bulletin No. 23-01.
                </P>
                <HD SOURCE="HD3">3. Final Year of the 3-Year Phase Out of the Rural Adjustment</HD>
                <P>
                    For FY 2027, CMS is continuing the 3-year budget-neutral phase-out of the 
                    <PRTPAGE P="17208"/>
                    rural adjustment for FY 2024 IRFs transitioning from rural to urban status in FY 2025 under the revised CBSA delineations. As stated in the FY 2025 IRF PPS final rule (89 FR 64276), the purpose of this gradual phase-out of the rural adjustment for these facilities is to reduce the potential negative financial impacts associated with this reclassification. In FY 2027, the final year of this phase-out, affected IRFs will receive the full FY 2027 wage index with no further FY 2024 rural adjustment. This final step is part of a gradual reduction of the 14.9 percent rural adjustment over three fiscal years FYs 2025, 2026 and 2027. Furthermore, this policy does not apply to urban IRFs transitioning to rural status, as they will receive the full rural adjustment.
                </P>
                <HD SOURCE="HD3">4. IRF Budget-Neutral Wage Adjustment Factor Methodology</HD>
                <P>
                    To calculate the wage-adjusted facility payment for the payment rates set forth in this proposed rule, we multiply the unadjusted Federal payment rate for IRFs by the FY 2027 labor-related share based on the 2021-based IRF market basket relative importance (74.5 percent) to determine the labor-related portion of the standard payment amount. (A full discussion of the calculation of the labor-related share appears in section VI. of this proposed rule.) We then multiply the labor-related portion by the applicable IRF wage index. The wage index tables are available on the CMS website at 
                    <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/InpatientRehabFacPPS/IRF-Rules-and-Related-Files.html.</E>
                </P>
                <P>Adjustments or updates to the IRF wage index made under section 1886(j)(6) of the Act must be made in a budget-neutral manner. We calculate a budget-neutral wage adjustment factor as established in the FY 2004 IRF PPS final rule (68 FR 45689) and codified at § 412.624(e)(1), as described in the steps below. We use the listed steps to ensure that the FY 2027 IRF standard payment conversion factor reflects the update to the wage indexes (based on the FY 2023 hospital cost report data) and the update to the labor-related share, in a budget-neutral manner:</P>
                <P>
                    <E T="03">Step 1.</E>
                     Calculate the total amount of estimated IRF PPS payments using the labor-related share and the wage indexes from FY 2026 (as published in the FY 2026 IRF PPS final rule (90 FR 37678).
                </P>
                <P>
                    <E T="03">Step 2.</E>
                     Calculate the total amount of estimated IRF PPS payments using the FY 2027 wage index values (based on updated hospital wage data and taking into account the permanent 5-percent cap on wage index decreases when applicable) and the FY 2027 labor-related share of 74.5 percent.
                </P>
                <P>
                    <E T="03">Step 3.</E>
                     Divide the amount calculated in Step 1 by the amount calculated in Step 2. The resulting quotient is the proposed FY 2027 budget-neutral wage adjustment factor of 1.0033.
                </P>
                <P>
                    <E T="03">Step 4.</E>
                     Apply the budget neutrality factor from Step 3 to the FY 2027 IRF PPS standard payment amount after the application of the market basket percentage increase to determine the FY 2027 standard payment conversion factor.
                </P>
                <P>We discuss the calculation of the standard payment conversion factor for FY 2027 in section VI.E. of this proposed rule.</P>
                <P>We invite public comments on our proposals regarding the wage adjustment for FY 2027.</P>
                <HD SOURCE="HD2">E. Description of the Proposed IRF Standard Payment Conversion Factor Methodology and Payment Rates for FY 2027</HD>
                <P>To calculate the proposed IRF standard payment conversion factor for FY 2027, as illustrated in Table 5, we begin by applying the IRF market basket update for FY 2027, as adjusted in accordance with sections 1886(j)(3)(C) of the Act, to the standard payment conversion factor for FY 2026 ($19,371). Applying the 2.4 percent IRF market basket update for FY 2027 to the standard payment conversion factor for FY 2026 of $19,371 yields a FY 2027 standard payment amount of $19,836. Then, we apply the budget neutrality factor for the FY 2027 wage index (taking into account the policy placing a permanent 5-percent cap on decreases to a provider's wage index), and labor-related share of 1.0033, which results in an IRF standard payment amount of $19,901. We next apply the budget neutrality factor for the CMG relative weights of 0.9990, which results in the proposed IRF standard payment conversion factor of $19,881 for FY 2027.</P>
                <GPH SPAN="3" DEEP="137">
                    <GID>EP06AP26.062</GID>
                </GPH>
                <P>We then apply the CMG relative weights described in section V.E of this rule to the proposed FY 2027 standard payment conversion factor ($19,881), to determine the unadjusted IRF prospective payment rates for FY 2027. The unadjusted IRF prospective payment rates for FY 2027 are shown in Table 6.</P>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17209"/>
                    <GID>EP06AP26.063</GID>
                </GPH>
                <GPH SPAN="3" DEEP="576">
                    <PRTPAGE P="17210"/>
                    <GID>EP06AP26.064</GID>
                </GPH>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                <HD SOURCE="HD2">F. Example of the Methodology for Adjusting the Prospective Payment Rates</HD>
                <P>Table 7 illustrates the methodology for adjusting the prospective payments (as described in section V. of this proposed rule). The following examples are based on two hypothetical Medicare beneficiaries, both classified as CMG 0104 (without comorbidities). The unadjusted prospective payment rate for CMG 0104 (without comorbidities) appears in Table 6.</P>
                <P>
                    <E T="03">Example:</E>
                     One beneficiary is in Facility A, an IRF located in rural Spencer County, Indiana, and another beneficiary is in Facility B, an IRF located in urban Harrison County, Indiana. Facility A, a rural non-teaching hospital has a Disproportionate Share Hospital (DSH) percentage of 5 percent (which would result in a LIP adjustment of 1.0156), a wage index of 0.8624, and 
                    <PRTPAGE P="17211"/>
                    a rural adjustment of 14.9 percent. Facility B, an urban teaching hospital, has a DSH percentage of 15 percent (which would result in a LIP adjustment of 1.0454), a wage index of 0.9492, and a teaching status adjustment of 0.0784.
                </P>
                <P>To calculate each IRF's labor and non-labor portion of the prospective payment, we begin by taking the FY 2027 unadjusted prospective payment rate for CMG 0104 (without comorbidities) from Table 6. Then, we multiply the labor-related share for FY 2027 (74.5 percent) described in section VI. of this proposed rule by the unadjusted prospective payment rate. To determine the non-labor portion of the prospective payment rate, we subtract the labor portion of the Federal payment from the unadjusted prospective payment.</P>
                <P>
                    To compute the wage-adjusted prospective payment, we multiply the labor portion of the Federal payment by the appropriate wage index located in the applicable wage index table. This table is available on the CMS website at 
                    <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/InpatientRehabFacPPS/IRF-Rules-and-Related-Files.html.</E>
                </P>
                <P>The resulting figure is the wage-adjusted labor amount. Next, we compute the proposed wage-adjusted Federal payment by adding the wage-adjusted labor amount to the non-labor portion of the Federal payment.</P>
                <P>Adjusting the wage-adjusted Federal payment by the facility-level adjustments involves several steps. First, we take the wage-adjusted prospective payment and multiply it by the appropriate rural and LIP adjustments (if applicable). Second, to determine the appropriate amount of additional payment for the teaching status adjustment (if applicable), we multiply the teaching status adjustment by the wage-adjusted and rural-adjusted amount (if applicable). Finally, we add the additional teaching status payments (if applicable) to the wage, rural, and LIP-adjusted prospective payment rates. Table 7 illustrates the components of the adjusted payment calculation.</P>
                <GPH SPAN="3" DEEP="264">
                    <GID>EP06AP26.065</GID>
                </GPH>
                <P>Thus, the adjusted payment for Facility A would be $31,798.41 and the adjusted payment for Facility B would be $32,829.76.  </P>
                <HD SOURCE="HD1">VI. Proposed Update to Payments for High-Cost Outliers Under the IRF PPS for FY 2027</HD>
                <HD SOURCE="HD2">A. Proposed Update to the Outlier Threshold Amount for FY 2027</HD>
                <P>Section 1886(j)(4) of the Act provides the Secretary with the authority to make payments in addition to the basic IRF prospective payments for cases incurring extraordinarily high costs. A case qualifies for an outlier payment if the estimated cost of the case exceeds the adjusted outlier threshold. We calculate the adjusted outlier threshold by adding the IRF PPS payment for the case (that is, the CMG payment adjusted by all of the relevant facility-level adjustments) and the adjusted threshold amount (also adjusted by all of the relevant facility-level adjustments). Then, we calculate the estimated cost of a case by multiplying the IRF's overall Cost-to-Charge Ratio (CCR) by the Medicare allowable covered charge. If the estimated cost of the case is higher than the adjusted outlier threshold, we make an outlier payment for the case equal to 80 percent of the difference between the estimated cost of the case and the outlier threshold.</P>
                <P>In the FY 2002 IRF PPS final rule (66 FR 41362 through 41363), we discussed our rationale for setting the outlier threshold amount for the IRF PPS so that estimated outlier payments would equal 3 percent of total estimated payments. For the FY 2002 IRF PPS final rule, we analyzed various outlier policies using 3, 4, and 5 percent of the total estimated payments, and we concluded that an outlier policy set at 3 percent of total estimated payments would optimize the extent to which we could reduce the financial risk to IRFs of caring for high-cost patients, while still providing for adequate payments for all other (non-high cost outlier) cases.</P>
                <P>
                    Subsequently, we updated the IRF outlier threshold amount in the FYs 2006 through 2026 IRF PPS final rules and the FY 2011 and FY 2013 notices 
                    <PRTPAGE P="17212"/>
                    (70 FR 47880, 71 FR 48354, 72 FR 44284, 73 FR 46370, 74 FR 39762, 75 FR 42836, 76 FR 47836, 76 FR 59256, 77 FR 44618, 78 FR 47860, 79 FR 45872, 80 FR 47036, 81 FR 52056, 82 FR 36238, 83 FR 38514, 84 FR 39054, 85 FR 48444, 86 FR 42362, 87 FR 47038, 88 FR 50956, 89 FR 64276 and 90 FR 37678, respectively) to maintain estimated outlier payments at 3 percent of total estimated payments. We also stated in the FY 2009 final rule (73 FR 46370 through 46385) that we would continue to analyze the estimated outlier payments for subsequent years and adjust the outlier threshold amount as appropriate to maintain the 3 percent target.
                </P>
                <P>To update the IRF outlier threshold amount for FY 2027, we propose to use FY 2025 claims data and the same methodology that we used to set the initial outlier threshold amount in the FY 2002 IRF PPS final rule (66 FR 41362 through 41363), which is also the same methodology that we used to update the outlier threshold amounts for FYs 2006 through 2026. The outlier threshold is calculated by simulating aggregate payments and using an iterative process to determine a threshold that results in outlier payments being equal to 3 percent of total payments under the simulation. To determine the outlier threshold for FY 2027, we estimate the amount of FY 2027 IRF PPS aggregate and outlier payments using the most recent claims available (FY 2025) and the proposed FY 2027 standard payment conversion factor, labor-related share, and wage indexes, incorporating any applicable budget-neutrality adjustment factors. The outlier threshold is adjusted either up or down in this simulation until the estimated outlier payments equal 3 percent of the estimated aggregate payments. Based on an analysis of the preliminary data used for the proposed rule, we estimate that IRF outlier payments as a percentage of total estimated payments will be approximately 2.6 percent in FY 2026. Therefore, we propose to update the outlier threshold amount from $10,141 for FY 2026 to $8,689 for FY 2027 to maintain estimated outlier payments at approximately 3 percent of total estimated aggregate IRF payments for FY 2027.</P>
                <P>We note that, with our longstanding practice when developing previous IRF PPS fiscal year rules, we update our data between the FY 2027 IRF PPS proposed and final rules to ensure that we use the most recent available data in calculating IRF PPS payments. We are proposing the outlier threshold amount of $8,689 to maintain estimated outlier payments at approximately 3 percent of total estimated aggregate IRF payments for FY 2027.</P>
                <P>We invite public comments on the proposed update to the IRF outlier threshold for FY 2027.</P>
                <HD SOURCE="HD2">B. Proposed Update to the IRF Cost-to-Charge Ratio (CCR) Ceiling and Urban/Rural Averages for FY 2027</HD>
                <P>CCRs are used to adjust charges from Medicare claims to costs and are computed annually from facility-specific data obtained from Medicare Cost Reports (MCRs). IRF-specific CCRs are used in the development of the CMG relative weights and the calculation of outlier payments under the IRF PPS. In accordance with the methodology described in the FY 2004 IRF PPS final rule (68 FR 45692 through 45694), we proposed to apply a ceiling to IRFs' CCRs. Using that methodology, we propose to update the national urban and rural CCRs for IRFs, as well as the national CCR ceiling for FY 2027, based on analysis of the most recent data available. We apply the national urban and rural CCRs to:</P>
                <P>• New IRFs that have not yet submitted their first MCR.</P>
                <P>• IRFs with an overall CCR that exceeds the national CCR ceiling for FY 2027, as discussed below in this section.</P>
                <P>• Other IRFs for which accurate data to calculate an overall CCR are not available.</P>
                <P>Specifically, for FY 2027, we propose to estimate a national average CCR of 0.461 for rural IRFs, which we calculated by taking an average of the CCRs for all rural IRFs using their most recently submitted cost report data. Similarly, we propose to estimate a national average CCR of 0.386 for urban IRFs, which we calculated by taking an average of the CCRs for all urban IRFs using their most recently submitted cost report data. We applied weights to both of these averages using the IRFs' estimated costs, meaning that the CCRs of IRFs with higher total costs factor more heavily into the averages than the CCRs of IRFs with lower total costs. For this proposed rule, we used the most recent available cost report data (FY 2024). This includes all IRFs whose cost reporting periods begin on or after October 1, 2023, and before October 1, 2024. If, for any IRF, the FY 2024 cost report was missing or had an “as submitted” status, we used the most recent FY for which a settled cost report was available (that is, from a FY between FY 2004 and FY 2023) for that IRF. We do not use cost report data from before FY 2004 for any IRF because changes in IRF utilization since FY 2004 resulting from the 60 percent rule and IRF medical review activities suggest that these older data do not adequately reflect the current cost of care. Using updated FY 2024 cost report data for this proposed rule, we estimate a national average CCR of 0.461 for rural IRFs and a national average CCR of 0.386 for urban IRFs.</P>
                <P>In accordance with past practice, we propose to set the national CCR ceiling at 3 standard deviations above the mean CCR. Using this method, we propose a national CCR ceiling of 1.54 for FY 2027. This means that, if an individual IRF's CCR were to exceed this ceiling of 1.54 for FY 2027, we will replace the IRF's CCR with the appropriate proposed national average CCR (either rural or urban, depending on the geographic location of the IRF). We calculated the national CCR ceiling by:</P>
                <P>
                    <E T="03">Step 1.</E>
                     Taking the national average CCR (weighted by each IRF's total costs, as previously discussed) of all IRFs for which we have sufficient cost report data (both rural and urban IRFs combined).
                </P>
                <P>
                    <E T="03">Step 2.</E>
                     Estimating the standard deviation of the national average CCR computed in Step 1.
                </P>
                <P>
                    <E T="03">Step 3.</E>
                     Multiplying the standard deviation of the national average CCR computed in Step 2 by a factor of 3 to compute a statistically significant reliable ceiling.
                </P>
                <P>
                    <E T="03">Step 4.</E>
                     Adding the result from Step 3 to the national average CCR of all IRFs for which we have sufficient cost report data, from Step 1.
                </P>
                <P>We also propose that if more recent data become available after the publication of the proposed rule and before the publication of the final rule, we will use such data to determine the FY 2027 national average rural and urban CCRs and the national CCR ceiling in the final rule. Using the FY 2024 cost report data for this proposed rule, we estimate a national average CCR ceiling of 1.54, using the same methodology.</P>
                <P>We invite public comments on the proposed update to the IRF CCR ceiling and urban/rural averages for FY 2027.  </P>
                <HD SOURCE="HD1">VII. Proposals To Revise the Basis of Payment Requirements</HD>
                <HD SOURCE="HD2">A. Proposal on the Initiation of Therapies Within 36-Hours From Admission</HD>
                <P>
                    In accordance with 42 CFR 412.622(a)(3)(ii), in order for an IRF claim to be considered reasonable and necessary, the patient's intensive rehabilitation therapy program must consist of at least 3 hours of therapy (physical therapy, occupational therapy, speech-language pathology, or prosthetics/orthotics therapy) per day at 
                    <PRTPAGE P="17213"/>
                    least 5 days per week. Under certain conditions, this program might consist of at least 15 hours of intensive rehabilitation therapy provided over 7 days. The required therapy treatments and/or therapy evaluations for IRF patients must begin within 36 hours from midnight of the day of admission to the IRF. Sub-regulatory guidance that was posted by CMS in 2010 may have created ambiguous policy interpretation as to whether only one therapy or all therapies must be initiated within 36 hours from the day of admission to the IRF (hereafter referred to as the 36-hour requirement). Therapy evaluations are generally considered to constitute the beginning of the required therapy services and may count towards meeting the 36-hour requirement. However, all therapies must be initiated, not just one therapy to meet the policy regulation. For example, if a patient is admitted to the IRF at 2:00 p.m. on Tuesday, therapy treatment must be initiated by 12:00 p.m. on Thursday (that is, 36 hours after Tuesday at midnight).
                </P>
                <P>For the purposes of this proposed rule, we are proposing to revise § 416.622(a)(3)(ii) to require all therapy treatments and/or therapy evaluations must begin no later than 36 hours after midnight of the day of admission. An IRF claim will not be considered reasonable and necessary (in accordance with section 1862(a)(1) of the act) if it does not comply with this coverage criteria.</P>
                <HD SOURCE="HD2">B. Proposal To Update the Documentation of Current Functional Status in the Preadmission Screening</HD>
                <P>IRFs are required to document a comprehensive preadmission screening in accordance with 42 CFR 412.622(a)(4)(i) in order to indicate a patient meets the requirements for an IRF admission to be considered reasonable and necessary and ultimately, to be reimbursed for an IRF claim. As part of this policy (42 CFR 412.622(a)(4)(i)(B)), the preadmission screening must “include a detailed and comprehensive review of each patient's condition and medical history, including the patient's level of function prior to the event or condition that led to the patient's need for intensive rehabilitation therapy, expected level of improvement, and the expected length of time necessary to achieve that level of improvement; an evaluation of the patient's risk for clinical complications; the conditions that caused the need for rehabilitation; the treatments needed (that is, physical therapy, occupational therapy, speech-language pathology, or prosthetics/orthotics); and anticipated discharge destination.”</P>
                <P>
                    While the patient's 
                    <E T="03">prior</E>
                     level of function is indicated as a requirement, we believe that in order for an appropriate plan of care to be developed for a patient, a patient's 
                    <E T="03">current</E>
                     functional status must also be documented in the preadmission screening. The patient's current level of function provides important information to build a more complete picture of their rehabilitation trajectory and expected level of improvement while in the IRF.
                </P>
                <P>For the purposes of this proposed rule, we are proposing to revise § 412.622(a)(4)(i)(B) to require that the patient's “current functional status” be documented in the patient's preadmission screening in their medical record at admission.</P>
                <HD SOURCE="HD2">C. Proposed Initial Interdisciplinary Team Meeting</HD>
                <HD SOURCE="HD3">1. Background</HD>
                <P>During the IDT meeting, all members of a patient's IRF care team review the patient's progress toward their rehabilitation goals, while making recommendations for therapy changes to support discharge goals (§ 412.622(a)(5)). These goals are part of the patient's POC which collates assessments from each therapy discipline treating the patient and includes the patient's medical prognosis, anticipated interventions, functional outcomes, and discharge destination. Per § 412.622(a)(4)(ii), the POC must be developed by a rehabilitation physician and documented in the patient's medical record or electronic health record by day 4 of the patient's admission to the IRF.</P>
                <P>The current IDT meeting policy (42 CFR 412.622(a)(5)) states that IDT meetings must occur “at least once per week throughout the duration of the patient's stay,” with a “week” defined as a period of 7 consecutive calendar days beginning with the date of admission to the IRF” (§ 412.622(c)). However, there has been guidance provided to IRFs that says the initial IDT meeting may occur on day 8 from the day of admission, which is not aligned with the current policy.</P>
                <HD SOURCE="HD3">2. Proposed Initial Interdisciplinary Team Meeting</HD>
                <P>Under the current IDT policy (§ 412.622(a)(5)), IRF patients may have only one IDT meeting occur prior to discharge, which raises concern about the level of coordinated interdisciplinary care a patient is receiving. The IDT meeting is a key aspect of the interdisciplinary care of an IRF patient as it provides the opportunity for the care team to review together the patient's care and progress, and to ensure the POC is updated as needed to accurately reflect the patient's needs. For example, and under the current policy, it is possible for an IRF patient to receive up to 7 days of care in an IRF without their full care team coordinating their treatment or discussing progress towards the patient's goals as outlined in the POC. This could be particularly concerning as the patient is likely to experience rapid improvement or decline in functioning within the first 7 days.</P>
                <P>By not providing a timely initial IDT meeting with the care team's input on the patient's progress, the team may be providing suboptimal treatment or inadvertently worsening the patient's health outcomes. Also, given the average length of stay in an IRF is typically between 12 to 14 days, for a patient who has their first IDT meeting on day 7, it is likely that the IDT meeting would focus on discharge planning rather than making timely updates to the patient's POC based on his/her progress. Per § 412.622(a)(4)(ii), an individualized overall POC must be developed by a rehabilitation physician with input from the interdisciplinary team within 4 days of the patient's admission to the IRF and documented in the patient's medical record or electronic health record. By not making more timely checks and updates within the IDT meeting on the patient's progress, and related POC updates, patients are at risk for ineffective care that may lead to delayed improvements.</P>
                <P>
                    <E T="03">Patient example:</E>
                     A 68-year-old male patient is admitted to an IRF with an ischemic stroke causing mild hemiparesis, mild aphasia, and dysphagia. His admission goals were to increase his mobility, independence with activities of daily living (ADLs), and safety with swallowing in order to be discharged home to his family. The patient's POC includes: a physical therapist (PT) to work on gait training and balance; an occupational therapist (OT) to address his independence with self-care and dressing; and a speech-language pathologist (SLP) to manage the aphasia and swallowing. During the patient's course of stay, the PT, OT and SLP have limited communication with one another. By the time the patient's interdisciplinary team meeting occurs on day 7 of his stay, the PT has noted the patient is steady with transfers using a walker and requires minimal assistance to ambulate with his walker. Despite the PT's notes, the OT is now training the patient on ADL tasks that require him to stand without support. 
                    <PRTPAGE P="17214"/>
                    The patient has been steady when performing these tasks for brief periods of time but needs to rest often by sitting down. The SLP is providing the patient with nectar-thick liquids per the swallowing plan but has not communicated the patient's fatigue levels or the patient's need for safety cues when swallowing to the rest of the team. The patient's IDT meeting on Day 7 focuses on his discharge planning with the rehabilitation physician noting the patient can safely ambulate independently with his walker and ADLs as he is unaware of the inconsistencies in the patient's presentation across the OT, SLP, and PT therapy sessions. As such, the patient returns home with his wife after 11 days in the IRF. Within two days, the patient sustains a fall while transferring from the toilet resulting in a hip fracture. He is readmitted to the acute care hospital with aspiration pneumonia due to coughing and choking during meals and hip fracture due to difficulty ambulating with his walker.
                </P>
                <P>In the example, if the initial IDT meeting had occurred earlier than day 7, the patient's POC could have been adjusted to better match his functional progress. Additionally, his care team could have discussed ongoing concerns regarding his fatigue, balance, and swallowing to coordinate treatment. An earlier IDT meeting may have prevented this patient's fall and hospital readmission.</P>
                <P>In an effort to continuously improve patient-centered care, we believe the first IDT meeting should occur earlier than day 7 of a patient's stay, which is current policy. This change will ensure patients are receiving coordinated, interdisciplinary care aligned with their POC and tailored in its intensity to the patient's recovery progress. We propose to revise § 412.622(a)(5)(ii) to specify that the first IDT meeting shall occur on or before the fourth day from midnight on the date the patient is admitted to implement appropriate treatment services; establish or review the patient's stated rehabilitation goals; and identify any problems that could impede goals. The initial IDT would be in coordination with the development and timing of the patient's start of therapy (per the 36-hour rule) and the POC. Following the initial IDT meeting, we are proposing that a patient's subsequent IDT meetings occur weekly (for example, within 7 days from the prior IDT meeting). See Figure 1 and Table 8 for examples of when IDT meetings occur based on the date the prior IDT was conducted. In addition to the revisions to § 412.622(a)(5)(ii), we propose to redesignate paragraph (a)(5)(iii) as paragraph (a)(5)(iv) and add a new paragraph (a)(5)(iii) to clarify that the initial IDT meeting shall determine the cadence of patient's subsequent IDT meetings. We also propose to revise the definition of “Week” that appears in § 412.622(c) to specify that, for purposes of § 412.622, a “week” means a period of 7 consecutive calendar days.</P>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                <HD SOURCE="HD1">Figure 1: Proposed Initial Interdisciplinary Team Meeting Policy</HD>
                <GPH SPAN="3" DEEP="258">
                    <GID>EP06AP26.066</GID>
                </GPH>
                <GPH SPAN="3" DEEP="278">
                    <PRTPAGE P="17215"/>
                    <GID>EP06AP26.067</GID>
                </GPH>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                <P>In requiring the patient's first IDT meeting to occur by Day 4, we believe the interdisciplinary team can coordinate care and provide treatment updates more frequently than once during a patient's stay, which may lead to improved quality of care and health outcomes. As discussed in the FY 2010 rule (74 FR 39762), conducting the IDT meeting “for each IRF patient within the first 4 days of admission to develop the overall plan of care would be good practice.”</P>
                <P>To assess the impact of this proposal, we conducted a simulation exercise. If we assume that IRFs hold a formal IDT meeting on a weekly basis (per the current policy) to address their caseload and the prognoses of their patients, an estimated range of 2.1 to 3.8 percent of IRF patients discharged between FY 2015 through FY 2023 experience zero IDT meetings during their stay. If we account for patients who were admitted on the day of the IDT meeting but too late to be discussed at the meeting, the number of cases with zero IDT meetings during the stay will increase from 4.2 to 4.8 percent. By CMS implementing a policy requiring that the patient's first IDT meeting occurs by Day 4 of their stay, the percentage of cases that did not have an IDT meeting would decrease to 1 percent. After the initial IDT meeting, IRFs will need to conduct subsequent IDT meetings beginning on the 7th day from when the last meeting occurred.</P>
                <P>We conducted an estimated impact of the proposed initial IDT policy on IRFs. To determine the resources needed for one IRF meeting, we first identified the salaries of the key personnel who attend IDT meetings using the 2024 Bureau of Labor Statistics' (BLS) national average wages per hour. For conservative estimation purposes, we assumed one of each of the following disciplines attend IDT meetings: rehabilitation physician, PT, OT, SLP, nurse coordinator (filled by an RN), social worker, and rehabilitation unit manager (filled by an NP). If the proposed initial IDT meeting policy is finalized, we assume that most IRFs (depending on the volume of patients) will increase the frequency of meetings to meet this change. For example, if an IRF has a patient admitted on a Tuesday, but the team's usual IDT meetings occur on Mondays, then the IRF will have to meet again by the patient's Day 4 (Friday in this example) to comply with the new policy. We approximated that a 1-hour IDT meeting would cover approximately 12 IRF patients (5 minutes per patient), resulting in $399.06 per 60-minute IDT meeting. Assuming the IDT meetings would be 1-hour in duration, for IRFs that move from once to the twice weekly IDT meeting frequency will face an additional approximate cost of $399.06 per week.  </P>
                <HD SOURCE="HD1">VIII. Request for Information Regarding Future IRF Payment Reform</HD>
                <P>CMS is exploring opportunities to modernize the IRF Prospective Payment System (PPS) established in 2002 (66 FR 41316) to better reflect evolving clinical practice and align more closely with other post-acute care settings. This includes potential refinements to clinical categories and comorbidity groupings. Below, we provide an overview of the current IRF PPS patient classification system and request input on future payment reforms to enhance and modernize the IRF payment structure.</P>
                <HD SOURCE="HD2">A. Background</HD>
                <P>Under the IRF PPS, providers report an Impairment Group Code (IGC) in Item 21A of the IRF Patient Assessment Instrument (IRF-PAI) to identify the primary reason the patient requires IRF care. Each IGC maps to a single Rehabilitation Impairment code (RIC), which serves as the first level of classification in the payment system. The CMS grouper uses the RIC to assign the patient to a CMG based primarily on functional status at admission and, for certain CMGs, age.</P>
                <P>
                    Functional status is a key predictor of resource use under the IRF PPS. From FY 2002 through FY 2019, CMG assignment relied on motor and cognitive scores derived from the FIM
                    <E T="51">TM</E>
                     instrument. In the FY 2019 final rule (83 FR 38514), CMS removed the FIM
                    <E T="51">TM</E>
                      
                    <PRTPAGE P="17216"/>
                    instrument and associated Function Modifiers and adopted IRF-PAI Quality Indicator items to reduce provider burden. Beginning in FY 2020, CMGs have been assigned using functional scores derived from these IRF-PAI assessment items.
                </P>
                <P>CMGs are further refined to account for clinical complexity. Patients may be assigned to comorbidity tiers that adjust payment to reflect higher expected resource use. Additional payment adjustments apply for special circumstances, such as very short stays or death.</P>
                <P>The IRF PPS currently includes 21 Rehabilitation Impairment Categories and 17 associated Impairment Group Codes, as established in the FY 2002 final rule (66 FR 41316). IGCs are represented by one or two-digit codes, sometimes extended with decimals to identify more specific subgroups.</P>
                <P>Additional information is available in the FY 2002 (66 FR 41316), FY 2006 (70 FR 47880), FY 2007 (71 FR 48354), and FY 2021 (85 FR 48424) IRF PPS final rules.</P>
                <HD SOURCE="HD2">B. The Need for IRF Payment Reform</HD>
                <P>Experience from other Medicare payment reforms demonstrates the importance of aligning payment with patient characteristics and expected resource use, rather than service volume, while maintaining strong safeguards against unintended coding or behavioral responses. These reforms highlight the need for regular recalibration using current data, thoughtful and phased implementation of structural changes, and monitoring to protect beneficiary access. Applying these principles to IRF payment reform supports continued refinement of CMGs, functional scores, and comorbidity adjustments to improve payment accuracy and ensure program integrity.</P>
                <P>CMS believes refinements to the IRF clinical categories and comorbidity groupings are necessary to support continued payment reform under section 1886(j) of the Act, which would contribute to overall payment reform. CMS must ensure that the IRF PPS reflects changes in patient complexity and advances in rehabilitation care since the system's implementation in 2002. These refinements are intended to better align payment with patient characteristics and resource use, strengthen the relationship between spending and value, and support CMS's broader goal of a more consistent and coordinated approach to post-acute care (PAC) payment and delivery.</P>
                <P>As with any case-mix methodology, shifts in documentation, coding practices, or assessment completion may influence measured case-mix independent of true changes in patient acuity. By adopting more standardized, diagnosis-based classification approaches across PAC settings, CMS aims to improve consistency, support care delivery reform, and position the IRF PPS for future payment reforms that better reflect patient complexity and value. Furthermore, these potential refinements would move the IRF PPS toward diagnosis-driven grouping methods similar to those used in other Medicare payment systems, including the Inpatient Psychiatric Facility PPS (IPF PPS) and the SNF Patient-Driven Payment Model (PDPM) finalized in the FY 2019 SNF PPS final rule (83 FR 39162).</P>
                <P>MedPAC's recent analyses further support the need for refinement. In multiple Reports to the Congress on Medicare Payment Policy (March 2023, March 2024, March 2025, and March 2026), MedPAC identified persistent differences in profitability across clinical categories, which could provide incentives for admitting specific diagnoses to improve profitability. MedPAC also found that within RICs, higher patient severity—measured by functional status and comorbidities—is associated with higher payment-to-cost ratios, and that case mix varies meaningfully by IRF ownership and type, particularly for high-volume conditions such as stroke, other neurological conditions, and debility. These findings underscore the importance of refining IRF clinical categories and comorbidity groupings to better reflect patient severity and improve alignment between payments and resource use. In this RFI, we seek interested parties' input on potential approaches to ensure that payments under a revised IRF PPS appropriately reflect underlying patient severity and costs, particularly in the event of systematic changes in coding or documentation that are not accompanied by corresponding changes in clinical complexity or resource utilization.</P>
                <HD SOURCE="HD3">1. Potential Changes to IRF Patient Clinical Classification</HD>
                <P>As previously discussed, the IRF PPS currently relies on 17 major category IGCs, comprising 85 specific IGCs, finalized in the FY 2002 IRF PPS final rule (66 FR 41316) to classify each patient into one of 21 distinct Rehabilitation Impairment Categories (RICs). Under this framework, up to three ICD-10-CM etiologic diagnosis codes are mapped through a multi-step process—from IGCs to RICs to CMGs—to determine payment. Over time, this layered classification approach has created opportunities for misalignment among the patient's primary reason for IRF admission, the clinical care delivered, and the resulting payment, particularly as diagnostic coding practices and patient complexity have evolved.</P>
                <P>To address these limitations, CMS is considering a fundamental refinement to IRF patient classification by modifying how primary diagnoses are mapped to clinical categories. Specifically, CMS has leveraged the existing clinical categories recently implemented under the SNF PDPM to develop a preliminary set of IRF-specific clinical categories. These proposed categories would modernize IRF patient classification by replacing the current mapping of etiologic diagnoses to IGCs and RICs with a comprehensive and exhaustive crosswalk from ICD-10-CM diagnosis codes directly to IRF PPS clinical categories. This approach would strengthen alignment between diagnosis, patient severity, and payment; improve consistency across post-acute care settings; and support CMS's broader objectives of payment accuracy, transparency, and value-based care.</P>
                <P>Table 9 provides the 15 valid IRF clinical categories for consideration. Using a complete ICD-10-CM to clinical category crosswalk, patients are classified into clinical categories by the ICD-10-CM code reflecting the primary reason for the IRF stay.</P>
                <GPH SPAN="3" DEEP="292">
                    <PRTPAGE P="17217"/>
                    <GID>EP06AP26.068</GID>
                </GPH>
                <P>
                    We are soliciting public comments on the potential use of these clinical category assignments under the IRF PPS to classify a patient for payment purposes. CMS is exploring alternatives to how primary diagnoses are mapped to clinical categories in the current IRF PPS, which is documented in a technical report available at: 
                    <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/inpatient-rehabilitation/research.</E>
                </P>
                <HD SOURCE="HD3">2. Potential Changes to IRF PPS Comorbidities</HD>
                <P>Drawing on the comorbidity scoring methodology used by the SNF PDPM Non-Therapy Ancillary (NTA) component, CMS developed a preliminary comorbidity scoring and binning approach for the IRF PPS accounting for both the severity and the number of comorbid conditions. This would also support alignment across post-acute care payment systems. Under this framework, CMS identifies comorbidities associated with higher IRF costs using multiple sources, including Hierarchical Condition Categories (HCCs), Prescription HCCs (RxHCCs), IRF-PAI items, and selected custom conditions. Each comorbidity would contribute to a weighted score reflecting its relative impact on resource use, similar to the methodology applied under the SNF PDPM NTA system.</P>
                <P>As shown in Table 10, comorbidity scores would then be grouped into one of 6 comorbidity score bins: a comorbidity score of 0, 1, 2, 3, 4-5, and 6 or higher. Each bin groups IRF stays by corresponding comorbidity score based on estimated similarities in costs. These scoring and grouping refinements would align spending and value through improved accuracy while also aligning IRF PPS more closely with other PAC payment systems.</P>
                <GPH SPAN="3" DEEP="135">
                    <GID>EP06AP26.069</GID>
                </GPH>
                <P>
                    We are soliciting public comments on the potential use of comorbidity scores and score bins under the IRF PPS to categorize comorbidities for payment purposes. CMS is exploring alternatives to the tier comorbidity methodology of the current IRF PPS and relative performance to the current system, which is documented in a technical 
                    <PRTPAGE P="17218"/>
                    report. For more details, including a list of the selected comorbidities and corresponding scores, this technical report is available at 
                    <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/inpatient-rehabilitation/research.</E>
                </P>
                <HD SOURCE="HD1">IX. Inpatient Rehabilitation Facility (IRF) Quality Reporting Program (QRP)</HD>
                <HD SOURCE="HD2">A. Background and Statutory Authority</HD>
                <P>The Inpatient Rehabilitation Facility Quality Reporting Program (IRF QRP) is authorized by section 1886(j)(7) of the Act, and it applies to freestanding IRFs, as well as inpatient rehabilitation units of hospitals or Critical Access Hospitals (CAHs) paid by Medicare under the IRF PPS. Section 1886(j)(7)(A)(i) of the Act requires the Secretary to reduce by 2 percentage points the annual increase factor for discharges occurring during a FY for any IRF that does not submit data in accordance with the IRF QRP requirements set forth in subparagraphs (C) and (F) of section 1886(j)(7) of the Act. We have codified our program requirements in our regulations at § 412.634.</P>
                <P>In this proposed rule, we are proposing to revise the IRF QRP data submission deadlines beginning with the FY 2029 IRF QRP, as described in section IX.D.2 of this proposed rule. Finally, we are soliciting public comments on one RFI on future measure concepts for the IRF QRP in section IX.C. of this proposed rule.</P>
                <HD SOURCE="HD2">B. General Considerations Used for the Selection of Measures for the IRF QRP</HD>
                <P>For a detailed discussion of the considerations we use for the selection of IRF QRP quality, resource use, or other measures, we refer readers to the FY 2016 IRF PPS final rule (80 FR 47083 and 47084).</P>
                <HD SOURCE="HD3">1. Quality Measures Currently Adopted for the IRF QRP</HD>
                <P>The IRF QRP currently has 15 adopted measures, which are listed in Table 11.</P>
                <P>For a discussion of the factors we use to evaluate whether a measure should be removed from the IRF QRP, we refer readers to our regulations at § 412.634(b)(2). We refer readers to the CY 2013 OPPS/ASC PPS final rule (77 FR 68502 and 68503) for discussion of our policy that allows any quality measure adopted for use in the IRF QRP to remain in effect until the measure is removed, suspended, or replaced; the FY 2018 IRF PPS final rule (82 FR 36276) which applied this policy to standardized patient assessment data we adopt for the IRF QRP; and the FY 2019 IRF PPS final rule (83 FR 38556 and 38557) for more information on the factors we consider for removing measures and standardized patient assessment data.</P>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                <GPH SPAN="3" DEEP="419">
                    <PRTPAGE P="17219"/>
                    <GID>EP06AP26.070</GID>
                </GPH>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                <HD SOURCE="HD2">C. IRF QRP Measure Concepts Under Consideration for Future Years—RFI</HD>
                <P>In the FY 2024 IRF PPS proposed rule (88 FR 21000 through 21003), we included an RFI on a set of principles for selecting and prioritizing IRF QRP measures, identifying measurement gaps and suitable measures for filling these gaps. We refer readers to the FY 2024 IRF PPS final rule (88 FR 51036 and 51037) for a summary of the public comments we received in response to the RFI.</P>
                <P>
                    We are seeking input on the importance, relevance, appropriateness, and applicability of the quality measure concepts related to advanced care planning. Advance care planning is a continuous process that supports people in understanding and communicating their goals, values, and preferences regarding future medical decisions.
                    <SU>5</SU>
                    <FTREF/>
                     The Patient Self Determination Act of 1990 
                    <SU>6</SU>
                    <FTREF/>
                     supports this process by requiring healthcare facilities to inform patients of their rights regarding medical decisions, including advance directives and end of life care.
                    <SU>7</SU>
                    <FTREF/>
                     In-post acute care (PAC) settings, where patients recover from acute illness, injury, or major procedures, their needs and goals may evolve as their condition changes. Factors such as clinical stability, functional status, therapy tolerance, cognition function, prognosis, and personal preferences can all shift during recovery. Regular reassessment and transparent communication are essential to maintaining person-centered care, while advance care planning facilitates shared decision-making by documenting patient preferences and ensuring goal-concordant care throughout care transitions.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         McMahan, R.D., Tellez, I., &amp; Sudore, R.L. (2021). Deconstructing the Complexities of Advance Care Planning Outcomes: What Do We Know and Where Do We Go? A Scoping Review.
                        <E T="03">Journal of the American Geriatrics Society,</E>
                          
                        <E T="03">69</E>
                        (1), 234-244. 
                        <E T="03">https://doi.org/10.1111/jgs.16801.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Public Law 101-508, § 4206, 4751.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">https://www.congress.gov/bill/101st-congress/house-bill/4449. https://www.congress.gov/bill/101st-congress/house-bill/5835.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         McMahan RD, Tellez I, Sudore RL. Deconstructing the Complexities of Advance Care Planning Outcomes: What Do We Know and Where Do We Go? A Scoping Review. J Am Geriatr Soc. 2021 Jan;69(1):234-244. doi: 10.1111/jgs.16801. Epub 2020 Sep 7. PMID: 32894787; PMCID: PMC7856112.
                    </P>
                </FTNT>
                <P>
                    As we review new measure concepts, we would prioritize evidence-based outcome measures that promote person-centered care practices. We are seeking input on the relevant aspects of advanced care planning and measures appropriate for the IRF setting.
                    <PRTPAGE P="17220"/>
                </P>
                <HD SOURCE="HD2">D. Form, Manner, and Timing of Data Submission Under the IRF QRP</HD>
                <HD SOURCE="HD3">1. Background</HD>
                <P>We refer readers to the regulatory text at §  412.634(b)(1) for information regarding the current policies for reporting specified data for the IRF QRP.</P>
                <HD SOURCE="HD3">2. Proposal To Revise IRF QRP Data Submission Deadlines Beginning With the FY 2029 IRF QRP</HD>
                <HD SOURCE="HD3">(a) Background  </HD>
                <P>Sections 1886(j)(7)(E), and 1899B(f) and (g) of the Act require CMS to provide feedback to IRFs and to publicly report their performance on IRF quality measures specified under section 1899B(c)(1) of the Act and resource use and other measures specified under 1899B(d)(1) of the Act. More specifically, section 1899B(f)(1) of the Act requires the Secretary to provide confidential feedback reports to IRFs on their performance on the quality, resource use, and other measures specified under sections 1899B(c)(1) and (d)(1) of the Act. Section 1899B(f)(2) of the Act provides that, to the extent feasible, the Secretary must make these confidential feedback reports available, not less frequently than on a quarterly basis, except in the case of measures reported on an annual basis, in which case confidential feedback reports may be made available annually. Additionally, sections 1886(j)(7)(E) and 1899B(g)(1) of the Act require the Secretary to provide for the public reporting of each IRF's performance on the quality measures, resource use, and other measures specified under section 1899B(c)(1) and (d)(1) of the Act by establishing procedures for making the performance data available to the public. Section 1899B(g)(2) of the Act specifically requires that such procedures must ensure that IRFs can review and submit corrections to the data and other information before it is made public.</P>
                <P>Section 1886(j)(7)(C) of the Act provides the Secretary with discretion to prescribe the form and manner and the timeframes for IRFs to submit data as specified for reporting for the IRF QRP.</P>
                <P>For IRF-PAI assessment-based measures, in the FY 2016 IRF PPS final rule (80 FR 47122), we finalized submission deadlines for IRFs to submit their data approximately 4.5 months (135 days) after the end of each quarter. We did not receive any comments on the 4.5-month data submission timeframe at that time. We also finalized data submission deadlines for IRF QRP measures that are submitted via the Centers for Disease Control and Prevention's (CDC) National Healthcare Safety Network (NHSN). In the FY 2014 IRF PPS final rule (78 FR 47917), we finalized that for the NHSN Catheter Associated Urinary Tract Infection (CAUTI) and the Facility-wide Inpatient Hospital-onset Clostridium difficile Infection (CDI) Outcome Measures, each facility's data must be entered into NHSN no later than 4.5 months after the end of the reporting quarter. We also finalized that the data collection period for the Influenza Vaccination Coverage among Healthcare Personnel (HCP) measure would be October 1 through March 31, with a data submission deadline of May 15th for each influenza season (78 FR 47917).</P>
                <P>
                    Public reporting of data collected under quality programs, such as the IRF QRP, is designed to provide consumers and their families with the most current information to empower them to make quality-informed decisions about where to receive their care. We have identified that the time between when data on measures is submitted to us and when those data are publicly reported (approximately nine months) may be too long to provide the most accurate and up to date information for the public. For example, we have heard from interested parties that the IRF QRP measure results are not useful for their quality improvement efforts due to the aged data and the delay in when they receive these reports.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         IRF Listening Session: Revising the Transmission Schedule for the IRF-PAI. Available in the Downloads section on the IRF QRP Measures Information web page: 
                        <E T="03">https://www.cms.gov/medicare/quality/inpatient-rehabilitation-facility/irf-quality-reporting-measures-information.</E>
                    </P>
                </FTNT>
                <P>Currently, the largest contributing factor to the nine-month lag between the end of the data collection period and when measures are publicly reported is the 4.5-month timeframe for data submission. Reducing the data submission timeframe from 4.5 months to require data submission the 15th day of the second month after the end of the calendar quarter could reduce this lag by up to three months, resulting in more timely public reporting of data for consumers and increasing the value of publicly reported data. Additionally, this timeframe provides IRFs with more recent data in support of their quality improvement activities.</P>
                <P>In the FY 2026 IRF PPS proposed rule, we included a request for information (RFI) on reducing the assessment data submission deadline from 4.5 months to 45 days (90 FR 18554). We refer readers to the FY 2026 IRF PPS final rule (90 FR 37712) for a full summary of the public comments received.</P>
                <HD SOURCE="HD3">(b) Proposal To Revise the IRF QRP Assessment Data Submission Deadline</HD>
                <P>Beginning with the FY 2029 IRF QRP, we are proposing that IRFs must complete their data submissions and make corrections to their IRF-PAI assessment data where necessary no later than the 15th day of the second month after the end of the calendar quarter. However, if the 15th day of the second month falls on a Friday, weekend, or Federal holiday, the date is delayed until 11:59 p.m. EST on the next business day. We are proposing that IRFs would follow the deadlines presented in Table 12 for the FY 2029 IRF QRP. We are also proposing that similar calendar year data submission deadlines would apply to future years' payment determinations.</P>
                <GPH SPAN="3" DEEP="183">
                    <PRTPAGE P="17221"/>
                    <GID>EP06AP26.071</GID>
                </GPH>
                <P>We believe that requiring IRFs to submit IRF-PAI assessment data by the 15th day of the second month after the end of the calendar quarter is reasonable. We conducted an analysis on the potential impact of reducing the timeframe by determining how many assessments are currently being submitted by this deadline, which is approximately within 45 days of the end of the quarter. Using 2024 data, we identified that 99.08 percent of all IRF-PAI assessments were submitted to CMS within a 45-day timeframe. Of the remaining 0.92 percent submitted beyond 45 days, 0.20 percent were submitted after the current 4.5-month data submission deadline and would not be further impacted by a change in the data submission deadline. Therefore, only 0.72 percent of IRF-PAI assessments would be impacted by changing the data submission deadline from 4.5 months to require data submission by the 15th day of the second month after the end of the calendar quarter.</P>
                <HD SOURCE="HD3">(c) Proposal To Revise the CDC NHSN Data Submission Deadlines</HD>
                <P>Beginning with the FY 2029 IRF QRP, we are proposing that IRFs must complete their data submissions and make corrections to their CDC NHSN data where necessary no later than the 15th day of the second month after the end of the calendar quarter. However, if the 15th day of the second month falls on a Friday, weekend, or Federal holiday, the date is delayed until 11:59 p.m. EST on the next business day. We are proposing that IRFs would follow the deadlines presented in Table 13 for the FY 2029 IRF QRP. We are also proposing that similar calendar year data submission deadlines would apply to future years' payment determinations.</P>
                <GPH SPAN="3" DEEP="196">
                    <GID>EP06AP26.072</GID>
                </GPH>
                <P>We believe that requiring IRFs to submit CDC NHSN data by the 15th day of the second month after the end of the calendar quarter is a reasonable amount of time. In the FY 2014 IRF PPS final rule (78 FR 47917), we noted that the CDC recommends that a facility report Healthcare Acquired Infection (HAI) events such as CAUTI as close to the time of the event as possible, and certainly within 30 days after the event. We note that there would be no change in the data submission deadline for the Influenza Vaccination Coverage among HCP measure, as the previously finalized data submission date is May 15th for each influenza season.</P>
                <P>
                    We conducted an analysis on the potential impact of reducing the timeframe by determining how many IRFs are currently reporting data by this deadline, which is approximately within 45 days of the end of the quarter. Using FY 2025 data, we identified that 
                    <PRTPAGE P="17222"/>
                    88.5 percent of all IRFs submitted CDC NHSN data within a 45-day timeframe.
                </P>
                <P>On these bases, we believe revising the IRF QRP data submission deadline for IRF-PAI and CDC NHSN data to require IRFs to submit CDC NHSN data by the 15th day of the second month after the end of the calendar quarter would improve the timeliness of public reporting by three months, which is beneficial to both consumers and IRFs, with no change in burden to IRFs.</P>
                <P>We invite comment on this proposal to require that IRFs complete their data submissions and make corrections to their IRF-PAI assessment and CDC NHSN data where necessary no later than the 15th day of the second month after the end of the calendar quarter beginning with the FY 2029 IRF QRP.</P>
                <HD SOURCE="HD2">E. Policies Regarding Public Display of Measure Data for the IRF QRP</HD>
                <P>We are not proposing any new policies regarding the public display of measure data in this proposed rule. For a more detailed discussion about our policies regarding public display of IRF QRP measure data and procedures for the opportunity to review and correct data and information, we refer readers to the FY 2017 IRF PPS final rule (81 FR 52128 through 52131).  </P>
                <HD SOURCE="HD1">X. Proposed Change to the DMEPOS Competitive Bidding Program (CBP)</HD>
                <HD SOURCE="HD2">A. Bid Surety Bond Amount</HD>
                <HD SOURCE="HD3">1. Background</HD>
                <P>
                    Section 522(a) of the Medicare Access and CHIP Reauthorization Act of 2015 (Pub. L. 114-10) (MACRA) added a requirement under section 1847(a)(1)(G) of the Act requiring bidding entities to obtain a bid surety bond for each competitive acquisition area in which the entity submits the bid in a form specified by the Secretary and in an amount not less than $50,000 and not more than $100,000. CMS implemented this requirement as part of the final rule titled, “Medicare Program; End-Stage Renal Disease Prospective Payment System, Coverage and Payment for Renal Dialysis Services Furnished to Individuals With Acute Kidney Injury, End-Stage Renal Disease Quality Incentive Program, Durable Medical Equipment, Prosthetics, Orthotics and Supplies Competitive Bidding Program Bid Surety Bonds, State Licensure and Appeals Process for Breach of Contract Actions, Durable Medical Equipment, Prosthetics, Orthotics and Supplies Competitive Bidding Program and Fee Schedule Adjustments, Access to Care Issues for Durable Medical Equipment; and the Comprehensive End-Stage Renal Disease Care Model,” published in the 
                    <E T="04">Federal Register</E>
                     on November 4, 2016 (81 FR 77834) (hereinafter referred to as the “2016 ESRD PPS &amp; DMEPOS final rule”). Pursuant to the CY 2016 ESRD PPS and DMEPOS final rule, and as codified at 42 CFR 414.412(g), a bidding entity may not submit a bid(s) and be awarded a contract for a competition unless it obtains, in the amount of $50,000, a bid surety bond for the CBA (as defined at 42 CFR 414.402) from an authorized surety on the Department of the Treasury's Listing of Certified Companies and provides proof of having obtained the bond by submitting a copy to CMS by the deadline for bid submission. These requirements first applied to Round 2021, the first round of competitive bidding following the passage of MACRA.
                </P>
                <P>Section 1847(a)(1)(H)(i) of the Act provides that in the event that a bidding entity is offered a contract for any product category for a CBA, and its composite bid for such product category and area is at or below the median composite bid rate for all bidding entities included in the calculation of the single payment amount (SPA) for the product category and CBA, and the entity does not accept the contract offered, the bid surety bond(s) for the applicable CBA(s) will be forfeited and the Secretary will collect on the bid surety bond(s). As implemented in regulation at § 414.412(g) (redesignated from § 414.412(h) (see 83 FR 57025)), CMS will collect on the bid surety bond via Electronic Funds Transfer from the respective bonding company. In instances where a bidding entity does not meet the bid surety bond forfeiture conditions for any product category for a CBA as specified in section 1847(a)(1)(H)(i) of the Act, section 1847(a)(1)(H)(ii) of the Act requires that the bid surety bond liability submitted by the entity for the CBA will be returned to the bidding entity within 90 days of the public announcement of the contract suppliers for such product category and area.</P>
                <P>The bid surety bond requirement deters bidding entities from submitting a low, disingenuous bid amount in order to increase the probability that they will be offered a DMEPOS contract, as they will forfeit the bid surety bond if the bid is at or below the median composite bid rate and the bidding entity does not accept the offered contract.</P>
                <HD SOURCE="HD3">2. Current Issues</HD>
                <P>
                    In the Calendar Year (CY) 2026 Home Health Prospective Payment System (PPS) Final Rule (see 90 FR 55342-55620) published in the 
                    <E T="04">Federal Register</E>
                     on December 2, 2025, CMS established the Remote Item Delivery (RID) Competitive Bidding Program (CBP). The term “remote item delivery competitive bidding program” is defined under § 414.402 to mean a competitive bidding program wherein contract suppliers are responsible for furnishing remote item delivery items under a product category to all Medicare beneficiaries regardless of where they live in the CBA. The CBA could be one nationwide CBA that includes all areas (all States, territories, and the District of Columbia) or a CBA covering a specific region of the country.
                </P>
                <P>The term “remote item delivery item is defined under § 414.402 to mean an item falling under a remote item delivery competitive bidding program that may be shipped or delivered to a beneficiary's home, regardless of the method of delivery, or picked up at a local pharmacy or supplier storefront if the beneficiary or caregiver for the beneficiary chooses to pick the item up in person.</P>
                <P>
                    In the CY 2026 Home Health PPS Final Rule (see 90 FR 55342-55620), we stated that we plan to implement remote item delivery (RID) competitive bidding programs (CBPs) for certain items designated under the DMEPOS CBP, and further explained that competitions for RID items may involve larger competitive bidding areas (CBAs), including nationwide CBAs. To discourage DMEPOS suppliers from submitting non-serious or disingenuous bids and to ensure genuine commitment from suppliers awarded contracts under a RID CBP, we propose requiring one bid surety bond at the maximum allowable amount of $100,000 for any and all bids submitted by a bidding entity for RID CBAs in a round of the DMEPOS CBP. This maximum bond amount is justified because a RID CBA, even when structured as a regional competition, can span multiple States and serve beneficiaries across a vast geographic footprint, far exceeding the scope of a traditional CBA, which is typically confined to a single metropolitan statistical area (MSA) within one state. The significantly greater scale, complexity, and beneficiary population associated with a RID CBA warrant is the highest available level of financial commitment from bidders. This higher amount would also provide a stronger incentive for suppliers bidding on a RID CBA to submit bona fide bids and accept contract offers, thereby supporting the core objective of the DMEPOS CBP to reduce the amount Medicare pays for competitively bid DMEPOS and bring payment amounts more in line with those of a competitive market. A higher 
                    <PRTPAGE P="17223"/>
                    bid surety bond amount is further supported by section 1847(b)(4)(A) of the Act, which directs CMS to consider whether bidders can furnish sufficient items or services to meet the anticipated needs of individuals within the contract's geographic area on a timely basis—a standard that is particularly demanding given the broad, multi-state reach of a RID CBA.
                </P>
                <P>We propose to maintain the bid surety bond amount of $50,000 for all non-RID competitions.</P>
                <P>Rather than implementing hundreds of separate local CBPs and CBAs—which would impose unnecessary administrative burden on both the bidding program and suppliers—we believe the most practical approach is to consolidate RID competitions into one nationwide RID CBP or several large regional RID CBPs, covering all areas where a beneficiary resides or receives covered items under the applicable product categories, with limited exceptions as described in the CY 2026 Home Health PPS Final Rule (90 FR 29254). This approach is consistent with longstanding Federal guidance from a September 2004 GAO report (GAO-04-765), which recommended that CMS explore mail delivery as a viable competitive bidding strategy for items provided directly to beneficiaries in the home, and noted that the Medicare Modernization Act (MMA) authorizes CMS to designate the entire country as a single competitive area for select items. The GAO further emphasized that a consolidated nationwide approach would allow CMS to implement competitive bidding more quickly and efficiently than a piecemeal strategy, enabling companies with nationwide mail-order capability to compete for Medicare beneficiaries' business. The maximum bond requirement, combined with this consolidated RID CBP framework, promotes accountability, reduces administrative complexity, and ensures that only capable and committed suppliers participate in RID competitive bidding.</P>
                <HD SOURCE="HD2">B. Provisions of the Proposed Regulation</HD>
                <P>At § 414.412(g)(2)(i)(H), we are proposing that for future rounds of the DMEPOS CBP, the bid surety bond amount would remain at $50,000, and we propose to revise § 412(g)(2)(i)(H) to no longer use the term “bid bond value” and instead use the more common term “bid surety bond amount.” However, to submit a bid(s) and be awarded a contract for a RID CBP, we propose under § 414.412(g)(2)(iii) that the bidding entity must obtain a bid surety bond of $100,000. Additionally, we propose under § 414.412(g)(2)(iii) that if submitting bids for multiple competitions under a RID CBP, only one bid surety bond is required, regardless of whether the RID CBP competitions have different CBAs bid. We are soliciting comments on these proposals.</P>
                <HD SOURCE="HD1">XI. Collection of Information Requirements</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501-3520, we are required to provide notice in the 
                    <E T="04">Federal Register</E>
                     and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. To fairly evaluate whether an information collection should be approved by OMB, 44 U.S.C. 3506(c)(2)(A) requires that we solicit comment on the following issues:
                </P>
                <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency.</P>
                <P>• The accuracy of our estimate of the information collection burden.</P>
                <P>• The quality, utility, and clarity of the information to be collected.</P>
                <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques.</P>
                <P>We are soliciting public comments on each of these issues for the following sections of this document that contain information collection requirements (ICRs):</P>
                <HD SOURCE="HD3">ICRs for Proposed Updates Related to the IRF QRP</HD>
                <P>An IRF that does not meet the requirements of the IRF QRP for a fiscal year will receive a 2-percentage point reduction to its otherwise applicable annual increase factor for that fiscal year. We estimate that the burden associated with the IRF QRP is the time and effort associated with complying with the requirements of the IRF QRP. The IRF-PAI, in its current form, has been approved under OMB control number 0938-0842 (expiration 10/31/2027). In section IX.D.2 of this proposed rule, we are proposing to revise the data submission deadlines beginning with the FY 2029 IRF QRP. If finalized, this requirement would not result in additional collection burden for the IRF QRP or revisions to the currently approved IRF-PAI.</P>
                <P>
                    If you comment on this information collection, that is, reporting, recordkeeping or third-party disclosure requirements, please submit your comments electronically as specified in the 
                    <E T="02">ADDRESSES</E>
                     section of this proposed rule.
                </P>
                <P>
                    Comments must be received by the date and time specified in the 
                    <E T="02">DATES</E>
                     section of this rule.
                </P>
                <HD SOURCE="HD1">XII. Response to Comments</HD>
                <P>
                    Because of the large number of public comments we normally receive on 
                    <E T="04">Federal Register</E>
                     documents, we are not able to acknowledge or respond to them individually. We will consider all comments we receive by the date and time specified in the 
                    <E T="02">DATES</E>
                     section of this preamble, and, when we proceed with a subsequent document, we will respond to the comments in the preamble to that document.  
                </P>
                <HD SOURCE="HD1">XIII. Regulatory Impact Analysis</HD>
                <HD SOURCE="HD2">A. Statement of Need</HD>
                <P>
                    This proposed rule would update the IRF prospective payment rates for FY 2027 as required under section 1886(j)(3)(C) of the Act and in accordance with section 1886(j)(5) of the Act, which requires the Secretary to publish in the 
                    <E T="04">Federal Register</E>
                     on or before August 1 before each FY, the classification and weighting factors for CMGs used under the IRF PPS for such FY and a description of the methodology and data used in computing the prospective payment rates under the IRF PPS for that FY. This proposed rule would also implement section 1886(j)(3)(C) of the Act, which requires the Secretary to apply a productivity adjustment to the market basket percentage increase for FY 2012 and subsequent years.
                </P>
                <P>Furthermore, this proposed rule proposes to adopt policy changes to the IRF QRP under the statutory discretion afforded to the Secretary under section 1886(j)(7) of the Act.</P>
                <HD SOURCE="HD2">B. Overall Impact</HD>
                <P>We have examined the impacts of this rule as required by Executive Order 12866, “Regulatory Planning and Review”; Executive Order 13132, “Federalism”; Executive Order 13563, “Improving Regulation and Regulatory Review”; Executive Order 14192, “Unleashing Prosperity Through Deregulation”; the Regulatory Flexibility Act (RFA) (Pub. L. 96-354); section 1102(b) of the Social Security Act; section 202 of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                <P>
                    Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select those regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, 
                    <PRTPAGE P="17224"/>
                    and other advantages; and distributive impacts). Section 3(f) of Executive Order 12866 defines a “significant regulatory action” as any regulatory action that is likely to result in a rule that may: (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or Tribal governments or communities; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, or the President's priorities.
                </P>
                <P>We estimate the total impact of the policy updates described in this proposed rule by comparing the estimated payments in FY 2027 with those in FY 2026. This analysis results in an estimated $355 million increase for FY 2027 IRF PPS payments. Based on our estimates, OMB's Office of Information and Regulatory Affairs has determined this rulemaking is significant per section 3(f)(1) of E.O. 12866 because it will have an effect on the economy of $100 million or more in any 1 year. Accordingly, we have prepared an RIA that, to the best of our ability, presents the costs and benefits of the rulemaking. In accordance with the provisions of Executive Order 12866, this regulation was reviewed by OMB.</P>
                <P>Executive Order 14192, entitled “Unleashing Prosperity Through Deregulation” was issued on January 31, 2025, and requires that “any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations.” We estimated that this proposed rule would only generate approximately $0.02 million annualized costs at a 7 percent discount rate, discounted relative to year 2024, over a perpetual time horizon. This proposed rule, if finalized as proposed, is not expected to be an E.O. 14192 regulatory action because it would not impose any more than de minimis regulatory costs.</P>
                <HD SOURCE="HD2">C. Anticipated Effects on IRFs</HD>
                <P>
                    The RFA requires agencies to analyze options for regulatory relief of small entities, if a rule has a significant impact on a substantial number of small entities. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most IRFs and most other providers and suppliers are small entities, either by having revenues of $9.0 million to $47.0 million or less in any 1 year depending on industry classification, or by being nonprofit organizations that are not dominant in their markets. The SBA defines small specialty hospitals (except Psychiatric and Substance Abuse) as businesses having less than $47 million in total annual revenue. (For more details, see the Small Business Administration's final rule that set forth size standards for healthcare industries, at 65 FR 69432 and see 
                    <E T="03">https://www.sba.gov/sites/default/files/2023-06/Table%20of%20Size%20Standards_Effective%20March%2017%2C%202023%20%282%29.pdf,</E>
                     effective January 1, 2022, and updated on March 17, 2023.) We believe NAICS code 622310 (Specialty Hospitals, except Psychiatric and Substance Abuse) is a reasonable proxy for inpatient rehabilitation facilities (IRFs) for purposes of contextualizing industry structure where 40 percent of entities are small business (127 out of 327 entities) according to SUSB data.
                </P>
                <P>
                    According to the MedPAC 2026 Report to Congress,
                    <SU>10</SU>
                    <FTREF/>
                     only 51 percent of IRF stays are Medicare fee-for-service stays. Therefore, we estimate that Medicare constitutes approximately 51 percent of total revenue for all 1,175 IRFs. We invite feedback regarding this assumption.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">https://www.medpac.gov/wp-content/uploads/2026/03/Mar26_MedPAC_Report_To_Congress_SEC.pdf.</E>
                    </P>
                </FTNT>
                <P>As shown in Table 14, according to the 2022 Economic Census, all Specialty (except Psychiatric and Substance Abuse) Hospitals earned approximately $59.7 billion, while the small entities earned approximately $1.73 billion in total. The regulatory review cost is $341 per entity. Table 15 presents the distribution of $355 million increase in total annualized monetized transfers from the Federal Government and States to IRF providers in FY2027.</P>
                <P>The Department of Health and Human Services' (HHS) uses a change in revenue of more than 3 to 5 percent as a measure of economic significant impact. The agency considers the rule to have a significant impact on a substantial number of small businesses when more than 5 percent of impacted small entities meet the significant impact threshold. This proposed rule, if finalized as proposed, would have impact on a substantial number of small businesses. But the impact should not be significant. Table 15 presents the detailed annual transfer payment change from FY 2026 to FY 2027. Taking into account Medicare revenue accounts for around 51 percent of IRFs revenue, the change would be less than 3 percent. As such, we believe even though substantial number of small businesses might be affected, the impact would not be significant. Finally, the impact implies the increase of payment which is welcomed by small businesses.</P>
                <GPH SPAN="3" DEEP="295">
                    <PRTPAGE P="17225"/>
                    <GID>EP06AP26.073</GID>
                </GPH>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-04, enacted March 22, 1995) (UMRA) also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. In 2026, that threshold was approximately $193 million. This proposed rule does not mandate any requirements for State, local, or Tribal governments, or for the private sector.</P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it issues a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has federalism implications. As stated, this proposed rule will not have a substantial effect on State and local governments, preempt State law, or otherwise have a Federalism implication.</P>
                <P>Section 1102(b) of the Act requires us to prepare an RIA if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 603 of the RFA. For the purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. As shown in Table 15, we estimate that the net revenue impact of this proposed rule on rural IRFs is to increase estimated payments by approximately 3.3 percent based on the data of the 127 rural units and 14 rural hospitals in our database of 1,175 IRFs for which data were available. Considering Medicare revenue accounts for 51 percent of the total revenue, we estimate an overall impact for rural IRFs in all areas between 1.2 percent and 2.8 percent of total revenue. Therefore, the Secretary has determined that this proposed rule will not have a significant impact on the operations of a substantial number of small rural IRFs.</P>
                <HD SOURCE="HD2">
                    <E T="03">D. Detailed Economic Analysis</E>
                </HD>
                <P>We have estimated the impact of the proposed rule. This proposed rule updates the IRF PPS rates contained in the FY 2026 IRF PPS final rule (90 FR 37678). Specifically, this proposed rule proposes updates to the CMG relative weights and ALOS values, the wage index, and the outlier threshold for high-cost cases. This proposed rule would apply a productivity adjustment to the FY 2027 IRF market basket percentage increase in accordance with section 1886(j)(3)(C)(ii)(I) of the Act.</P>
                <HD SOURCE="HD3">1. Impact on IRFs</HD>
                <P>We estimate that the impact of the changes and updates described in this proposed rule will be a net estimated increase of $355 million in payments to IRFs for FY 2027. The impact analysis in Table 14 of this proposed rule represents the projected effects of the proposed updates to IRF PPS payments for FY 2027 compared with the estimated IRF PPS payments in FY 2026. We determine the effects by estimating payments while holding all other payment variables constant. We use the best data available, but we do not attempt to predict behavioral responses to these changes, and we do not make adjustments for future changes in such variables as number of discharges or case-mix.</P>
                <P>
                    We note that certain events may combine to limit the scope or accuracy of our impact analysis, because such an analysis is future-oriented and, thus, susceptible to forecasting errors because of other changes in the forecasted impact time period. Some examples could be legislative changes made by the Congress to the Medicare program that would impact program funding, or changes specifically related to IRFs. Although some of these changes may not necessarily be specific to the IRF PPS, the nature of the Medicare program is such that the changes may interact, and the complexity of the interaction of these changes could make it difficult to predict accurately the full scope of the impact upon IRFs.
                    <PRTPAGE P="17226"/>
                </P>
                <P>In updating the rates for FY 2027, we are proposing to implement the standard annual revisions described in this proposed rule (for example, the update to the wage index and market basket percentage increase used to adjust the Federal rates). We are also proposing to reduce the FY 2027 IRF market basket percentage increase by a productivity adjustment in accordance with section 1886(j)(3)(C)(ii)(I) of the Act. We estimate that the total increase in payments to IRFs in FY 2027, relative to FY 2026, will be approximately $355 million.</P>
                <P>This estimate is derived from the application of the FY 2027 IRF market basket percentage increase, reduced by a productivity adjustment in accordance with section 1886(j)(3)(C)(ii)(I) of the Act, which yields an estimated increase in aggregate payments to IRFs of $300 million. In addition, there is an estimated $55 million increase in aggregate payments to IRFs due to the update to the outlier threshold amount. We estimate that these updates would result in a net increase in estimated payments of $355 million from FY 2026 to FY 2027.  </P>
                <P>The effects of the proposed updates that impact IRF PPS payment rates are shown in Table 15. The following updates that affect the IRF PPS payment rates are discussed separately below:</P>
                <P>• The effects of the proposed update to the outlier threshold amount, from approximately 2.6 percent to 3.0 percent of total estimated payments for FY 2027, consistent with section 1886(j)(4) of the Act.</P>
                <P>• The effects of the proposed annual market basket update (using the 2021-based IRF market basket) to IRF PPS payment rates, as required by sections 1886(j)(3)(A)(i) and (j)(3)(C) of the Act, including a productivity adjustment in accordance with section 1886(j)(3)(C)(ii)(I) of the Act.</P>
                <P>• The effects of applying the proposed budget-neutral labor-related share and wage index adjustment, as required under section 1886(j)(6) of the Act, accounting for the permanent cap on wage index decreases when applicable.</P>
                <P>• The effects of the proposed budget-neutral changes to the CMG relative weights and ALOS values under the authority of section 1886(j)(2)(C)(i) of the Act.</P>
                <P>• The total proposed change in estimated payments based on the FY 2027 payment changes relative to the estimated FY 2026 payments.</P>
                <HD SOURCE="HD3">2. Description of Table 15</HD>
                <P>Table 15 shows the overall impact on the 1,175 IRFs included in the analysis. The next 12 rows of Table 15 contain IRFs categorized according to their geographic location, designated as either a freestanding hospital or a unit of a hospital, and by type of ownership; all urban, which is further divided into urban units of a hospital, urban freestanding hospitals, and by type of ownership; and all rural, which is further divided into rural units of a hospital, rural freestanding hospitals, and by type of ownership. There are 1,034 IRFs located in urban areas included in our analysis. Among these, there are 644 IRF units of hospitals located in urban areas and 390 freestanding IRF hospitals located in urban areas. There are 141 IRFs located in rural areas included in our analysis. Among these, there are 127 IRF units of hospitals located in rural areas and 14 freestanding IRF hospitals located in rural areas. There are 539 for-profit IRFs. Among these, there are 500 IRFs in urban areas and 39 IRFs in rural areas. There are 541 non-profit IRFs. Among these, there are 457 urban IRFs and 84 rural IRFs. There are 95 government-owned IRFs. Among these, there are 77 urban IRFs and 18 rural IRFs.</P>
                <P>The remaining four parts of Table 15 show IRFs grouped by geographic location within a region, by teaching status, and by DSH patient percentage (PP). First, IRFs located in urban areas are categorized for their location within a particular one of the nine Census geographic regions. Second, IRFs located in rural areas are categorized for their location within a particular one of the nine Census geographic regions. In some cases, especially for rural IRFs located in the New England, Mountain, and Pacific regions, the number of IRFs represented is small. IRFs are then grouped by teaching status, including non-teaching IRFs, IRFs with an intern and resident to average daily census (ADC) ratio less than 10 percent, IRFs with an intern and resident to ADC ratio greater than or equal to 10 percent and less than or equal to 19 percent, and IRFs with an intern and resident to ADC ratio greater than 19 percent. Finally, IRFs are grouped by DSH PP, including IRFs with zero DSH PP, IRFs with a DSH PP less than 5 percent, IRFs with a DSH PP between 5 and less than 10 percent, IRFs with a DSH PP between 10 and 20 percent, and IRFs with a DSH PP greater than 20 percent.</P>
                <P>The estimated impacts of each policy described in this proposed rule to the facility categories listed are shown in the columns of Table 15. The description of each column is as follows:</P>
                <P>• Column (1) shows the facility classification categories.</P>
                <P>• Column (2) shows the number of IRFs in each category in our FY 2027 analysis file.</P>
                <P>• Column (3) shows the number of cases in each category in our FY 2027 analysis file.</P>
                <P>• Column (4) shows the estimated effect of the adjustment to the outlier threshold amount.</P>
                <P>• Column (5) shows the estimated effect of the FY 2027 update to the IRF labor-related share, wage index with the 5-percent cap on wage index decreases when applicable, and final year of the 3-year phase-out of the rural adjustment finalized in the FY 2026 IRF PPS final rule, in a budget-neutral manner.</P>
                <P>• Column (6) shows the estimated effect of the update to the CMG relative weights and ALOS values, in a budget-neutral manner.</P>
                <P>• Column (7) compares our estimates of the payments per discharge, incorporating all of the policies reflected in this proposed rule for FY 2027 to our estimated payments per discharge in FY 2026.</P>
                <P>The average estimated increase in payments for all IRFs is approximately 2.8 percent. This estimated net increase includes the effects of the IRF market basket update for FY 2027 of 2.4 percent, which is based on an IRF market basket percentage increase of 3.2 percent, less a 0.8 percentage point productivity adjustment, as required by section 1886(j)(3)(C)(ii)(I) of the Act. It also includes the approximate 0.4 percent overall increase in estimated IRF outlier payments from the update to the outlier threshold amount. Since we are updating the IRF wage index, labor-related share and the CMG relative weights in a budget-neutral manner, we estimate there is no expected impact to total estimated IRF payments in aggregate from these changes. However, as described in more detail in each section, we estimate there will be expected impacts to the estimated distribution of payments among providers.</P>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="17227"/>
                    <GID>EP06AP26.074</GID>
                </GPH>
                <GPH SPAN="3" DEEP="214">
                    <PRTPAGE P="17228"/>
                    <GID>EP06AP26.075</GID>
                </GPH>
                <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                <HD SOURCE="HD3">3. Impact of the Update to the Outlier Threshold Amount</HD>
                <P>The estimated effects of the update to the outlier threshold adjustment from FY 2026 to FY 2027 are presented in column 4 of Table 15.</P>
                <P>For this FY 2027 proposed rule, we used preliminary FY 2025 IRF claims data and based on that preliminary analysis, we estimated that IRF outlier payments as a percentage of total estimated IRF payments would be 2.6 percent in FY 2026. Thus, we are adjusting the outlier threshold amount in this proposed rule from $10,141 in FY 2026 to $8,689 in FY 2027 to maintain total estimated outlier payments equal to 3 percent of total estimated payments in FY 2027. The estimated change in total IRF payments for FY 2027, therefore, includes an approximate 0.4 percentage point increase in payments because the estimated outlier portion of total payments is estimated to increase from approximately 2.6 percent to 3.0 percent. The impact of this update to the outlier threshold amount (as shown in column 4 of Table 15) is to increase estimated overall payments to IRFs by 0.4 percentage point.</P>
                <HD SOURCE="HD3">4. Impact of the Wage Index, Labor-Related Share, and Wage Index Cap</HD>
                <P>In column 5 of Table 15, we present the effects of the budget-neutral update of the wage index and labor-related share, taking into account the permanent 5-percent cap on wage index decreases when applicable. The changes to the wage index and the labor-related share are discussed together because the wage index is applied to the labor-related portion of payments, so the changes in the two have a combined effect on payments to providers. As discussed in section V.C. of this proposed rule, the FY 2027 labor-related share is 74.5 percent, 0.1 percentage point higher than the labor-related share for FY 2026.</P>
                <P>In the aggregate, since these proposed updates to the wage index and the labor-related share are applied in a budget-neutral manner as required under section 1886(j)(6) of the Act, we do not estimate that these updates will affect overall estimated payments to IRFs. However, we estimate that these changes will have distributional effects. For example, we estimate the largest increase in payments of 5.6 percent for rural IRFs in the New England region. We estimate the largest decrease in payments from the update to the wage index and labor-related share to be a 0.8 percent decrease for urban IRFs in the East South Central region.</P>
                <HD SOURCE="HD3">5. Impact of the Update to the CMG Relative Weights and ALOS Values</HD>
                <P>In column 6 of Table 15, we present the effects of the proposed budget-neutral update of the CMG relative weights and ALOS values. In the aggregate, we do not estimate that these proposed updates will affect overall estimated payments of IRFs. However, we do expect these updates to have small distributional effects between -0.3 percent to 0.1 percent.</P>
                <HD SOURCE="HD3">6. Effects of Requirements for the IRF QRP</HD>
                <P>In accordance with section 1886(j)(7)(A) of the Act, the Secretary must reduce by 2 percentage points the annual market basket increase factor otherwise applicable to an IRF for a fiscal year if the IRF does not comply with the requirements of the IRF QRP for that fiscal year. In section IX.A. of this proposed rule, we discussed the method for applying the 2-percentage points reduction to IRFs that fail to meet the IRF QRP requirements. In section IX.D.2. of this proposed rule, we are proposing to revise the data submission deadlines beginning with the FY 2029 IRF QRP. If finalized, this requirement would not result in additional collection burden for the IRF QRP.</P>
                <HD SOURCE="HD3">7. DMEPOS Competitive Bidding Program  </HD>
                <P>
                    This rule proposes a change to the DMEPOS CBP to further enhance its effectiveness in achieving the objectives of the program as mandated by section 1847(a) of the Act. Specially, we are proposing to increase the bid surety bond amount from $50,000 to $100,000 for any and all bids submitted by a bidding entity for remote item delivery (RID) competitive bidding program areas (CBAs) in a round of the DMEPOS CBP while maintaining $50,000 for all other CBAs. The primary factor for surety bond premiums is the bidder's credit score, with premiums typically ranging from 1 percent to 10 percent of the bid surety bond amount. However, there is no reliable way to estimate how program changes or market conditions because the last round may have impacted bidders' credit profiles. Importantly, the overall financial burden may be reduced for many suppliers because Round 2021 included 130 competitive bidding areas (CBAs) requiring separate bid surety bonds for each CBA, whereas Round 2028 will include a nationwide RID CBA requiring one bid surety bond. While the cost of 
                    <PRTPAGE P="17229"/>
                    one RID bid surety bond would increase because of a $50,000 increase in the bid surety bond amount, suppliers that previously bid in multiple CBAs would likely experience net savings by needing only one bid surety bond instead of multiple bid surety bonds. The actual cost impact will vary significantly based on individual credit scores, past performance, and the number of CBAs a supplier would have participated in under a prior round of the DMEPOS CBP. Given these variables, the true impact cannot be precisely quantified and cost estimates should present a range using a 1 percent to 10 percent premium rate framework with caveats about individual variation and the offsetting effect of requiring fewer bid surety bonds.
                </P>
                <HD SOURCE="HD2">E. Alternatives Considered</HD>
                <HD SOURCE="HD3">1. IRF PPS</HD>
                <P>The following is a discussion of the alternatives considered for the IRF PPS updates contained in this proposed rule. As noted previously in this proposed rule, section 1886(j)(3)(C) of the Act requires the Secretary to update the IRF PPS payment rates by an increase factor that reflects changes over time in the prices of an appropriate mix of goods and services included in the covered IRF services and section 1886(j)(3)(C)(ii)(I) of the Act requires the Secretary to apply a productivity adjustment to the market basket percentage increase for FY 2027. Thus, in accordance with section 1886(j)(3)(C) of the Act, we are proposing to update the IRF prospective payments in this proposed rule by 2.4 percent (which equals the proposed 3.2 percent IRF market basket percentage increase for FY 2027 reduced by a proposed 0.8 percentage point productivity adjustment as determined under section 1886(b)(3)(B)(xi)(II) of the Act (as required by section 1886(j)(3)(C)(ii)(I) of the Act)).</P>
                <P>We also considered making no changes to the current IDT meeting policy (42 CFR 412.622(a)(5)) and allow the initial IDT meetings to occur within 7 consecutive calendar days beginning with the date of admission to the IRF (42 CFR 412.622(c)). However, we declined to take this approach given the importance of the IDT meetings for coordinated patient care early in their stay and in shaping revisions to the plan of care if there are problems that could impede the patient's progress toward their rehabilitation goals.</P>
                <HD SOURCE="HD3">2. IRF QRP</HD>
                <P>Regarding the proposal to revise the IRF QRP assessment data submission deadline from 4.5 months to no later than the 15th day of the second month after the end of each quarter, we considered keeping the deadline unchanged. We determined that the revised timeframe is a reasonable amount of time for IRFs to submit data and make any necessary corrections, and that the benefits of this shortened timeframe include making the data timelier and more actionable which increases the value of publicly reported data both for consumers and their families and for IRFs to use in their quality improvement activities.</P>
                <HD SOURCE="HD2">F. Regulatory Review Costs</HD>
                <P>If regulations impose administrative costs on private entities, such as the time needed to read and interpret this proposed rule, we should estimate the cost associated with regulatory review. Due to the uncertainty involved with accurately quantifying the number of entities that will review the rule, we assume at least one staff in IRFs would read the rule. The total number of IRFs would be the proxy of number of reviewers for this rule. We acknowledge that this assumption may understate or overstate the costs of reviewing the proposed rule. We also assume that each reviewer reads 100 percent of the rule.</P>
                <P>
                    Using the national median hourly wage data from the May 2024 BLS for Occupational Employment and Wage Statistics (OEWS) for medical and health service managers (SOC 11-9111), we estimate that the cost of reviewing this rule is $113.42 per hour, including other indirect costs and fringe benefits (
                    <E T="03">https://www.bls.gov/oes/current/oes_nat.htm</E>
                    ). Assuming an average reading speed, we estimate that it will take approximately 3 hours for the staff to review the proposed rule. For each reviewer of the rule, the estimated cost is $340.26 (3 hours × $113.42). Therefore, we estimated that the total cost of reviewing this regulation is $399,805.5 ($340.26 × 1,175 reviewers).
                </P>
                <HD SOURCE="HD2">G. Accounting Statement and Table</HD>
                <P>
                    Consistent with OMB Circular A-4 (available at 
                    <E T="03">https://www.reginfo.gov/public/jsp/Utilities/a-4.pdf</E>
                    ), in Table 16, we have prepared an accounting statement showing the classification of the expenditures associated with the provisions of the proposed rule. Table 15 provides our best estimate of the increase in Medicare payments under the IRF PPS as a result of the updates presented in this proposed rule based on the data for IRFs in our database.
                </P>
                <GPH SPAN="3" DEEP="96">
                    <GID>EP06AP26.076</GID>
                </GPH>
                <HD SOURCE="HD2">H. Conclusion</HD>
                <P>Overall, the estimated payments per discharge for IRFs in FY 2027 are projected to increase by 2.8 percent, compared with the estimated payments in FY 2026, as reflected in column 7 of Table 15.</P>
                <P>IRF payments per discharge are estimated to increase by 2.8 percent in urban areas and 3.3 percent in rural areas, compared with estimated FY 2026 payments. Payments per discharge to rehabilitation units are estimated to increase 3.5 percent in urban areas and 3.4 percent in rural areas. Payments per discharge to freestanding rehabilitation hospitals are estimated to increase 2.5 percent in urban areas and 3.2 percent in rural areas.</P>
                <P>
                    Overall, IRFs are estimated to experience a net increase in payments as a result of the policies in this proposed rule. The largest payment increase is estimated to be 5.6 percent for IRFs in Rural New England. The analysis above, together with the remainder of this preamble, provides an RIA.
                    <PRTPAGE P="17230"/>
                </P>
                <P>Mehmet Oz, Administrator of the Centers for Medicare &amp; Medicaid Services, approved this document on March 31, 2026.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>42 CFR Part 412</CFR>
                    <P>Administrative practice and procedure, Health facilities, Medicare, Puerto Rico, Reporting and recordkeeping requirements.</P>
                    <CFR>42 CFR Part 414</CFR>
                    <P>Administrative practice and procedure, Biologics, Diseases, Drugs, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                  
                <P>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services proposes to amend 42 CFR chapter IV as set forth below:</P>
                <PART>
                    <HD SOURCE="HED">PART 412—PROSPECTIVE PAYMENT SYSTEMS FOR INPATIENT HOSPITAL SERVICES</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 412 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>42 U.S.C. 1302 and 1395hh.</P>
                </AUTH>
                <AMDPAR>2. Section 412.622 is amended—</AMDPAR>
                <AMDPAR>a. By revising paragraphs (a)(3)(ii), (a)(4)(i)(B), and (a)(5)(ii);</AMDPAR>
                <AMDPAR>b. By redesignating paragraph (a)(5)(iii) as paragraph (a)(5)(iv);</AMDPAR>
                <AMDPAR>c. By adding new paragraph (a)(5)(iii); and</AMDPAR>
                <AMDPAR>d. In paragraph (c) by revising the definition of “Week”.</AMDPAR>
                <P>The revisions and addition read as follows:</P>
                <SECTION>
                    <SECTNO>§ 412.622</SECTNO>
                    <SUBJECT>Basis of Payment.</SUBJECT>
                    <P>(a) * * *</P>
                    <P>(3) * * *</P>
                    <P>(ii) Except during the emergency period described in section 1135(g)(1)(B) of the Act, generally requires and can reasonably be expected to actively participate in, and benefit from, an intensive rehabilitation therapy program. Under current industry standards, this intensive rehabilitation therapy program generally consists of at least 3 hours of therapy (physical therapy, occupational therapy, speech-language pathology, or prosthetics/orthotics therapy) per day at least 5 days per week. In certain well-documented cases, this intensive rehabilitation therapy program might instead consist of at least 15 hours of intensive rehabilitation therapy per week. Benefit from this intensive rehabilitation therapy program is demonstrated by measurable improvement that will be of practical value to the patient in improving the patient's functional capacity or adaptation to impairments. All required therapy treatments and/or therapy evaluations ordered must begin no later than 36 hours from midnight the day of admission to the IRF.</P>
                    <STARS/>
                    <P>(4) * * *</P>
                    <P>(i) * * *</P>
                    <P>(B) It includes a detailed and comprehensive review of each patient's condition and medical history, including the patient's level of function prior to the event or condition that led to the patient's need for intensive rehabilitation therapy, current functional status, the expected level of improvement, and the expected length of time necessary to achieve that level of improvement; an evaluation of the patient's risk for clinical complications; the conditions that caused the need for rehabilitation; the treatments needed (that is, physical therapy, occupational therapy, speech language pathology, or prosthetics/orthotics); and anticipated discharge destination.</P>
                    <STARS/>
                    <P>(5) * * *</P>
                    <P>(ii) The initial interdisciplinary team meeting must occur on or before the fourth day from midnight of the date the patient is admitted to implement appropriate treatment services; establish or review the patient's stated rehabilitation goals; and identify any problems that could impede goals.</P>
                    <P>(iii) The date of the initial interdisciplinary team meeting shall be used to determine the patient's subsequent team meetings. The remaining IDT meetings must occur at least once per week after the date of the prior team meeting to implement appropriate treatment services; review the patient's progress toward stated rehabilitation goals; identify any problems that could impede progress towards those goals; and, where necessary, reassess previously established goals in light of impediments, revise the treatment plan in light of new goals, and monitor continued progress toward those goals.</P>
                    <STARS/>
                    <P>(c) * * *</P>
                    <STARS/>
                    <P>
                        <E T="03">Week</E>
                         means a period of 7 consecutive calendar days.
                    </P>
                </SECTION>
                <PART>
                    <HD SOURCE="HED">PART 414—PAYMENT FOR PART B MEDICAL AND OTHER HEALTH SERVICES</HD>
                </PART>
                <AMDPAR>3. The authority citation for part 414 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>42 U.S.C. 1302, 1395hh, and 1395rr(b)(l).</P>
                </AUTH>
                <AMDPAR>4. Section 414.412 is amended by—</AMDPAR>
                <AMDPAR>a. Revising paragraph (g)(2)(i)(H); and</AMDPAR>
                <AMDPAR>b. Adding paragraph (g)(2)(iii).</AMDPAR>
                <P>The revision and addition read as follows:</P>
                <SECTION>
                    <SECTNO>§ 414.412</SECTNO>
                    <SUBJECT>Submission of bids under a competitive bidding program.</SUBJECT>
                    <STARS/>
                    <P>(g) * * *</P>
                    <P>(2) * * *</P>
                    <P>(i) * * *</P>
                    <P>(H) The bid surety bond amount of $50,000.</P>
                    <STARS/>
                    <P>(iii) Notwithstanding the above, to submit a bid(s) and be awarded a contract for a RID CBP, the bidding entity must obtain a bid surety bond of $100,000. If submitting bids for multiple competitions under a RID CBP, only one bid surety bond is required, regardless of whether the RID CBP competitions have different CBAs.</P>
                    <STARS/>
                </SECTION>
                <SIG>
                    <NAME>Robert F. Kennedy, Jr.,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06642 Filed 4-2-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <CFR>45 CFR Part 261</CFR>
                <RIN>RIN 0970-AD07</RIN>
                <SUBJECT>Work Participation Rate Calculation Changes: Recalibration of the Caseload Reduction Credit and Prohibition of Small Checks in Work Participation Rate Calculation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Family Assistance (OFA), Administration for Children and Families (ACF), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        ACF proposes to make changes to the Temporary Assistance for Needy Families (TANF) program regulations to reset the base year of the caseload reduction credit from fiscal year (FY) 2005 to the new year established by Congress, which is currently FY 2015, and to exclude from the TANF work participation rate calculations certain cases that receive assistance payments benefits of less than $35 for a month. These changes are required by the Fiscal Responsibility Act (FRA) of 2023. The docket on 
                        <E T="03">https://www.regulations.gov</E>
                         will include a plain language summary of 
                        <PRTPAGE P="17231"/>
                        the NPRM as required by 5 U.S.C. 553(b)(4).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>ACF encourages the public to submit comments electronically to ensure they are received in a timely manner. You may submit comments, identified by docket number ACF-2026-0265 or Regulatory Information Number (RIN) 0970-AD07, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email comments to: TANFquestions@acf.hhs.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number (ACF-2026-0265) or RIN 0970-AD07 for this rulemaking. All comments received will be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided. For further information concerning submitting comments, see “Comments Invited” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Deborah List, Office of Family Assistance, ACF, at 
                        <E T="03">TANFquestions@acf.hhs.gov</E>
                         or 202-401-9275. Deaf and hard of hearing individuals may call 202-401-9275 through their chosen relay service or 711 between 8 a.m. and 7 p.m. Eastern Time.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Summary</HD>
                <P>In response to statutory changes in the Fiscal Responsibility Act of 2023 (FRA), ACF is proposing to amend the Temporary Assistance for Needy Families (TANF) program regulations to make changes to the caseload reduction credit and work participation rate calculations. More specifically, the FRA resets the base year for the caseload reduction credit that is part of TANF's work participation rate calculations from FY 2005 to FY 2015, effective October 1, 2025. Second, the FRA requires HHS to exclude from the TANF work participation rate calculations cases that receive assistance payments benefits of less than $35 for a month funded with separate state program (SSP) funds. This statutory provision also takes effect October 1, 2025.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>The Personal Responsibility and Work Opportunity Reconciliation Act of 1996 created the TANF program, repealing the Aid to Families with Dependent Children program and related programs. The TANF program provides a fixed block grant of about $16.5 billion annually to states, certain territories (Guam, the Virgin Islands, and Puerto Rico), and the District of Columbia (hereafter “states”). Additionally, federally recognized American Indian tribes and Alaska Native organizations may elect to operate their own TANF programs.</P>
                <P>The regulatory changes proposed in this rulemaking are applicable to the TANF programs of states. Tribal TANF programs are not impacted by these proposed changes.</P>
                <P>
                    States use federal TANF funds to provide cash assistance to low-income families, as well as to provide a wide range of services (
                    <E T="03">e.g.,</E>
                     work-related activities, child care, and refundable tax credits) designed to accomplish the program's four broad purposes. These statutory purposes are to:
                </P>
                <FP SOURCE="FP-2">1. Provide assistance to needy families so that children can be cared for in their own homes or in the homes of relatives</FP>
                <FP SOURCE="FP-2">2. End the dependence of needy parents on government benefits by promoting job preparation, work, and marriage</FP>
                <FP SOURCE="FP-2">3. Prevent and reduce the incidence of out-of-wedlock pregnancies</FP>
                <FP SOURCE="FP-2">4. Encourage the formation and maintenance of two-parent families </FP>
                <P>The statute provides some eligibility requirements for families that receive TANF benefits, such as that the benefits can only go to US citizens and certain qualified aliens, that cash assistance in which an adult receives federally funded assistance generally has a five-year time limit, and that families receiving federal cash assistance must assign their child support rights to the state. However, states have flexibility to set economic and other eligibility requirements for their cash assistance and other TANF-funded benefits and services.</P>
                <P>In order to receive their full federal block grant, states must meet a maintenance-of-effort (MOE) requirement, which means that, consistent with Subpart A of 45 CFR 263, they must expend state funds on “eligible families” for benefits and services related to TANF purposes in amounts based on historical spending in TANF's predecessor programs. States may spend their MOE funds in three different ways:</P>
                <P>
                    • 
                    <E T="03">Commingled with federal funds</E>
                     and expended in the state's TANF program. These expenditures are subject to federal funding restrictions, all TANF requirements, and MOE limitations.
                </P>
                <P>
                    • 
                    <E T="03">Segregated from federal funds</E>
                     but spent in the state's TANF program. These expenditures are subject to many TANF requirements, but not all.
                </P>
                <P>
                    • 
                    <E T="03">Separate State Programs (SSPs)</E>
                     are operated outside of the state's TANF program. These expenditures are somewhat more flexible, although they must be consistent with the goals of the TANF statute and other MOE requirements. Families receiving assistance through SSPs are not subject to federal requirements regarding child support assignment, the federal five-year time limit, and various other federal rules. However, the Deficit Reduction Act of 2005 (DRA) that reauthorized the TANF program extended work participation requirements to SSP families with a work-eligible individual, beginning in FY 2007.
                </P>
                <P>
                    The TANF statute at 
                    <E T="03">42 U.S.C. 607</E>
                     requires HHS to calculate and issue TANF work participation rates for states. Work participation rates measure the degree to which a state engages families with a work-eligible individual receiving assistance in work activities specified under federal law. Each state must meet both an overall (or “all families”) work participation rate and a separate two-parent work participation rate or face a potential financial penalty to their annual TANF block grant imposed by HHS. The statutorily required work participation rate performance levels are a rate of 50 percent for “all families” and a rate of 90 percent for two-parent families; however, states may receive credits for reducing their caseload of families receiving assistance, and these credits can be applied to a state's target for each of the statutory rates.
                </P>
                <P>
                    A state's caseload reduction credit for a fiscal year equals the percentage point decline in its average monthly caseload of families receiving assistance between the previous fiscal year and a base fiscal year established by Congress. For a caseload reduction credit toward the two-parent work participation rate, the state has the option of using its overall caseload reduction credit or a separate one calculated using the decline in its two-parent caseload. In calculating the caseload reduction credit, HHS excludes any caseload reduction resulting from changes in state or federal eligibility requirements since the base year established by Congress. In addition, TANF regulations allow a state that is investing state MOE funds in excess of the required basic MOE amount to only include the pro rata share of caseloads receiving assistance that is required to meet basic MOE requirements. In other words, it may exclude from its comparison-year caseload the share of cases funded with “excess MOE” in 
                    <PRTPAGE P="17232"/>
                    order to reward states for spending their own funds on benefits and services to eligible families beyond what is required.
                </P>
                <P>We also note that some states provide assistance to low-income families through solely state-funded (SSF) programs, which are not funded by either TANF or MOE funds. Families that receive assistance from SSF programs are not subject to any TANF requirements, including federal work participation requirements. Many states serve all two-parent families that apply for assistance through a SSF program so that they do not have to achieve the 90 percent WPR target for those families, which many states find difficult to meet even after reductions from the caseload reduction credit and “excess MOE.”</P>
                <P>The FRA changes the base year for the caseload reduction credit calculation and institutes a new requirement for HHS to exclude from the TANF work participation rate calculations cases that receive assistance payments benefits of less than $35 for a month funded with SSP funds.</P>
                <HD SOURCE="HD1">Statutory Authority</HD>
                <P>We publish this notice of proposed rulemaking (NPRM) under the authority granted to the Secretary of Health and Human Services by 42 U.S.C. 607(b)(3)(A) and (i)(1)(A). This proposed rule implements sections 301 and 303 of the FRA. Section 301 recalibrates the caseload reduction base year and the Secretary has authority to prescribe regulations implementing the caseload reduction credit. See 42 U.S.C. 607(b)(3)(A) (providing that the Secretary shall prescribe regulations for reducing the minimum participation rate by the caseload reduction credit). Section 303 of the FRA requires HHS to exclude from the TANF work participation rate calculations certain cases that receive monthly benefits of less than $35. The Secretary has authority to prescribe regulations governing the work participation rate. See 42 U.S.C. 607(i)(A)(1) (providing that the Secretary promulgate regulations for determining whether activities may be counted as work activities, how to count and verify reported hours of work, and determine who is a work-eligible individual).</P>
                <P>Note that here and below we use the term “we” in the regulatory text and preamble. The term “we” is synonymous with the Secretary of the Department of Health and Human Services or any of the following individuals or agencies acting on his behalf: the Assistant Secretary for Children and Families, the Department of Health and Human Services (HHS), and the Administration for Children and Families.</P>
                <HD SOURCE="HD1">Section-by-Section Discussion of the Proposed Regulatory Provisions</HD>
                <HD SOURCE="HD2">1. Recalibration of the Caseload Reduction Credit</HD>
                <P>As required by section 301 of the FRA, we propose to change the base year for purposes of calculating a state's caseload reduction credit from FY 2005 to the year that has been established by Congress, which as of October 1, 2025, is FY 2015. As described above, the statutory requirement for work participation rates for states are 50 percent for all families (the overall rate) and 90 percent for two-parent families. However, a state's work participation rate targets equal the statutory rates minus a credit for reducing its caseload. A state's caseload reduction credit for a fiscal year equals the percentage point decline in its average monthly caseload between the previous fiscal year (the comparison year) and a base year established by Congress, net of caseload declines due to changes in eligibility criteria. This means that we exclude the impact of eligibility changes made after the base year from the credit calculation.</P>
                <HD SOURCE="HD2">2. Elimination of the Small Checks Scheme</HD>
                <P>Section 303 of the FRA requires HHS to exclude from the TANF work participation rate calculations certain cases that receive monthly benefits of less than $35. Specifically, the law provides that we must determine work participation rates “without regard to any individual engaged in work in a family that receives no assistance under this part and less than $35 in assistance funded with qualified State expenditures (as defined in section 409(a)(7)(B)(i) [of the Social Security Act]).” We interpret this wording to mean that we must exclude from both the numerator and denominator of the work participation rate calculation a family receiving a benefit of less than $35 for the month only if it is funded with SSP funds. We come to this conclusion by considering the two types of funding described in the provision, “assistance under this part” and “qualified State expenditures.”</P>
                <P>
                    There is a longstanding interpretation of the phrase “under this part” to mean the TANF program, which includes benefits funded with federal funds and with segregated state MOE, 
                    <E T="03">i.e.,</E>
                     MOE claimed under the TANF program, as well as comingled funds. The preamble discussion of the original TANF final rule made this clear: “Requirements in the statute that use the terms `under the program,' `under the program funded under this part,' and `under the State program funded under this part' apply to the State's TANF program, regardless of the funding source. That is, they apply to segregated Federal programs, commingled State/Federal programs, and segregated State programs.” (64 FR 17816, April 12, 1999)
                </P>
                <P>“Qualified state expenditures” are the state funds expended during a fiscal year that count for MOE purposes. We refer to them as broadly as MOE spending. As discussed above, state expenditures can be part of the TANF program in the form of segregated MOE expenditures or commingled with federal funds, or they can be expended in a SSP, meaning a program operated outside of TANF in which the expenditures of state funds count for MOE purposes. We have already discussed the fact that the term “under this part” covers segregated MOE and commingled funds, therefore the only form of qualified state expenditures not covered by that term is SSP.</P>
                <P>Thus, under section 303 of the FRA, we must exclude from the work participation rate calculation a family that receives no assistance funded with TANF—be it from federal, commingled, or segregated MOE funds—and receives less than $35 funded with SSP for a month. Since the work participation rate only includes families receiving assistance, the calculation already excludes families receiving no assistance funded with TANF (unless they receive assistance from SSP funds). That means that the only families the new provision excludes are ones receiving less than $35 in SSP for the month.</P>
                <P>The “small checks scheme” noted in the title of Section 303 refers to a strategy some states have used to help meet their work participation rate targets. In this strategy, states provide a very low (around $10) monthly benefit of SSP-funded assistance to families where a work-eligible individual is working full-time in unsubsidized employment. Because of that monthly benefit, the state includes them in the work participation rate calculations. This strategy allows a state to count individuals already in the workforce toward its WPR target, even if they were not previously part of the TANF caseload, thus inflating a state's official work numbers without effectively helping families move toward self-sufficiency.</P>
                <P>
                    After October 1, 2025, when Section 303 goes into effect, states using this strategy will have to revise their assistance payment structures or will no 
                    <PRTPAGE P="17233"/>
                    longer be able to count the families receiving these “small checks” for work participation rate purposes. Depending on the individual state characteristics and choices, there may be an interaction between how the state response to the provisions of Section 303 and the impact of Section 301 on the state's work participation target. For example, if a state had the “small checks” program prior to FY 2016, and chooses to eliminate it in FY 2026, the elimination would be considered an eligibility change and the state would not receive credit for that caseload decline. If the state created the “small checks” program after FY 2015, these cases would not be in the base year caseload but likely would have increased the caseload over time. If the state chooses to raise the “small checks” payment to $35, there would be no adjustment to caseloads as only the amount of the payment changed, not eligibility.
                </P>
                <P>We propose to implement the requirement of Section 303 of the FRA by adding a provision to the regulatory sections that describe the overall and two-parent work participation rate calculations. The proposed additional paragraph would make clear that cases receiving less than $35 in assistance funded exclusively with SSP funds would not be included in the applicable rate calculation for the month.</P>
                <HD SOURCE="HD1">Severability</HD>
                <P>The provisions of this proposed rule are intended to be severable, such that, in the event a court were to invalidate any particular provision or deem it to be unenforceable, HHS intends for all other parts of the final rule that are capable of operating in the absence of the specific portion that has been invalidated to remain in effect. None of the provisions in the final rule contained herein are central to an overall intent of the final rule, nor are any provisions dependent on the validity of other, separate provisions. For example, OFA expects that if a court were to invalidate the elimination of the small checks scheme, the recalibration of the caseload reduction credit may continue to operate and should remain operative independently of the invalidated subpart.</P>
                <HD SOURCE="HD1">Regulatory Impact Analysis</HD>
                <HD SOURCE="HD2">Introduction</HD>
                <P>We have examined the impacts of this proposed rule under Executive Order 12866, Executive Order 13563, Executive Order 14192, the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                <P>Executive Orders 12866 and 13563 direct us to assess all benefits and costs of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits. This rule was determined to be significant under Section 3(f) of Executive Order 12866. Rules determined to be significant under Section 3(f) of Executive Order 12866 are subject to review by the Office of Management and Budget (OMB). This proposed rule, if finalized as proposed, is not expected to be a regulatory action under Executive Order 14192 because it results in income transfers and does not impose any more than de minimis regulatory costs.</P>
                <P>The Unfunded Mandates Reform Act of 1995 (UMRA) generally requires that each agency conduct a cost-benefit analysis; identify and consider a reasonable number of regulatory alternatives; and select the least costly, most cost-effective, or least burdensome alternative that achieves the objectives of the rule before promulgating any proposed or final rule that includes a Federal mandate that may result in expenditures of more than $100 million (adjusted for inflation) in at least one year by State, local, and tribal governments, in the aggregate, or by the private sector. Each agency issuing a rule with relevant effects over that threshold must also seek input from State, local, and tribal governments. The current threshold after adjustment for inflation using the Implicit Price Deflator for the Gross Domestic Product is $187 million, reported in 2024 dollars. The proposed rule would not result in an unfunded mandate in any year that meets or exceeds this amount.</P>
                <HD SOURCE="HD2">Statement of Need</HD>
                <P>This NPRM would fulfill requirements of statutory provisions in the Fiscal Responsibility Act of 2023.</P>
                <HD SOURCE="HD2">Summary of Impacts</HD>
                <P>In a previous analysis of the federal fiscal impacts of policies addressed in this proposed rule, the Congressional Budget Office (CBO) reported the following:</P>
                <P>“Title I of division C would set the benchmark year for the caseload reduction to 2015 (rather than 2005) and would prevent people who receive less than $35 in state funding within a period determined by the Secretary of HHS from being included in a state's accounting for the work requirement. CBO estimates that HHS would reduce state grants slightly because some states would not meet the work requirement and would not comply with a corrective plan, and HHS would not approve their reason for not meeting the standard.</P>
                <P>
                    CBO estimates that the resulting reduction in block grants would reduce direct spending by $5 million over the 2023-2033 period.” 
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">https://www.cbo.gov/system/files/2023-05/hr3746_Letter_McCarthy.pdf.</E>
                    </P>
                </FTNT>
                <P>The CBO cost analysis reports economic impacts over a decade that are far below the monetary threshold for significance under section 3(f)(1) of Executive Order 12866. HHS estimates that the economic impacts may be even less than CBO describes. Based on the latest data and assumptions consistent with that data, we do not expect the statutory changes to affect a state's ability to meet its work participation rate target. In other words, we do not expect more states to be subject to a financial penalty as a direct result of these statutory changes. Further, if any state were to be subject to a financial penalty due to failing to meet their WPR target, it may enter corrective compliance and still avoid a penalty if the state meets the terms of its corrective compliance plan. HHS's experience has been that states typically comply with corrective compliance plans: of the approximately 85 instances a penalty was assessed for the period of FY 2013 to FY 2019, fewer than 15 have resulted in a financial penalty for the state to date.</P>
                <P>We anticipate most states will continue to meet their work participation rate targets even after these statutory changes take effect. As discussed below, in response to these changes, states may focus on better strategies for engaging WEIs in work, invest more in each case, and/or incur costs to train staff and amend systems, but overall, we expect the impact of implementing any of these changes to be minimal.</P>
                <P>The recalibration of the caseload reduction credit's base year may raise work participation rate targets for some states because they will receive a smaller caseload reduction credit, but most states will likely still receive some amount of credit, as there has been a significant decline in TANF/SSP caseloads since FY 2015, and HHS does not have reason to expect current caseload levels to increase. Higher work participation rate targets may encourage states to undertake better strategies for engaging WEIs in work activities.</P>
                <P>
                    States do not report on the use of the “small checks” approach directly, but we believe about five states currently use it to meet their WPR target and about a dozen states have used the 
                    <PRTPAGE P="17234"/>
                    strategy at one point. States currently relying on this strategy have typically provided nominal payments of less than $35. They may respond to the statutory change by increasing the amount of the “small checks” (
                    <E T="03">i.e.,</E>
                     the cost-per-case) to $35. Alternatively, these states may respond by discontinuing this practice, and instead choosing to focus their efforts on engaging WEIs in work activities. Any of these changes will require minimal adoption costs to train staff on the changes and possibly amend systems.
                </P>
                <HD SOURCE="HD2">Federal TANF Spending</HD>
                <P>There is no direct impact on Federal spending.</P>
                <HD SOURCE="HD2">MOE Spending</HD>
                <P>Some states may report additional MOE expenditures to increase the “excess MOE” component of the caseload reduction credit formula in order to counteract the impact of the change in base year. MOE spending could feasibly increase or decrease in response to the elimination of the “small checks scheme,” depending on whether states opt to eliminate that portion of their caseload or increase their benefit amounts.</P>
                <HD SOURCE="HD2">Administrative Costs to States and Other Jurisdictions Administering TANF Programs</HD>
                <P>The recalibration of the caseload reduction credit's base year will reduce administrative costs for states, as the number of eligibility changes that they have to account for will be reduced. Some of these calculations are extremely complicated and require considerable staff time. By changing the base year, states will no longer have to account for all eligibility changes between FY 2006 and FY 2015, therefore reducing staff time.</P>
                <HD SOURCE="HD2">Analysis of Regulatory Alternatives</HD>
                <P>There are no regulatory alternatives as the FRA specifically requires the two proposed changes.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (5 U.S.C. 601-612) requires Agencies to analyze the impact of rulemaking on small entities and consider alternatives that would minimize any significant impacts on a substantial number of small entities. For purposes of the RFA, states and individuals are not considered small entities. As the rule directly and primarily impacts states and indirectly impacts families, it has been determined, and the Secretary certifies that this proposed rule would not have a significant impact on a substantial number of small entities.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>
                    Under the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     as amended), all Departments are required to submit to OMB for review and approval any reporting or recordkeeping requirements inherent in a proposed or final rule. As required by this Act, we will submit any proposed revised data collection requirements to OMB for review and approval.
                </P>
                <HD SOURCE="HD1">Executive Order 13132</HD>
                <P>Executive Order 13132 requires federal agencies to consult with state and local government officials if they develop regulatory policies with federalism implications. Federalism is rooted in the belief that issues that are not national in scope or significance are most appropriately addressed by the level of government closest to the people. While the Department has not identified this rule to have federalism implications as defined in the Executive Order, consistent with Executive Order 13132, the Department specifically solicits and welcomes comments from state and local government officials on this proposed rule.</P>
                <HD SOURCE="HD1">Assessment of Federal Regulation and Policies on Families</HD>
                <P>Assessment of Federal Regulations and Policies on Families Section 654 of the Treasury and General Government Appropriations Act of 2000 requires Federal agencies to determine whether a policy or regulation may negatively affect family well-being. If the agency determines a policy or regulation negatively affects family well-being, then the agency must prepare an impact assessment addressing seven criteria specified in the law. ACF believes it is not necessary to prepare a family policymaking assessment (see Pub. L. 105-277) because the action it takes in this NPRM would not have any impact on the autonomy or integrity of the family as an institution.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 45 CFR Part 261</HD>
                    <P>Administrative practice and procedure, Employment, Grant programs—social programs, Public assistance programs, Reporting and record keeping requirements.</P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, we propose to amend 45 CFR subtitle B, chapter II, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 261—ENSURING THAT RECIPIENTS WORK</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 261 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>42 U.S.C. 601, 602, 607, and 609; Pub. L. 109-171.</P>
                </AUTH>
                <AMDPAR>2. Amend § 261.22, by revising the introductory text in paragraph (b) and adding paragraph (b)(4) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.22 </SECTNO>
                    <SUBJECT>How will we determine a State's overall work rate?</SUBJECT>
                    <STARS/>
                    <P>(b) Subject to paragraph (4), we determine a State's overall participation rate for a month as follows:</P>
                    <STARS/>
                    <P>(4) We will determine the overall work participation rate without regard to any work-eligible individual engaged in work in a family that receives less than $35 in assistance funded exclusively with SSP-MOE funds.</P>
                </SECTION>
                <AMDPAR>3. Amend § 261.24, by revising the introductory text in paragraph (b) and adding paragraph (b)(4) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.24 </SECTNO>
                    <SUBJECT>How will we determine a State's two-parent work rate?</SUBJECT>
                    <STARS/>
                    <P>(b) Subject to paragraph (4), we determine a State's two-parent participation rate for a month as follows:</P>
                    <STARS/>
                    <P>(4) We will determine the two-parent work participation rate without regard to any work-eligible individual engaged in work in a two-parent family that receives less than $35 in assistance funded exclusively with SSP-MOE funds.</P>
                </SECTION>
                <AMDPAR>4. Amend § 261.40 by revising paragraph (a) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.40</SECTNO>
                    <SUBJECT> Is there a way for a State to reduce the work participation rates?</SUBJECT>
                    <P>(a)(1) If the average monthly number of cases receiving assistance, including assistance under a separate State program (as provided at § 261.42(b)), in a State in the preceding fiscal year was lower than the average monthly number of cases that received assistance, including assistance under a separate State program in that State in the base year established by Congress, the minimum overall participation rate the State must meet for the fiscal year (as provided at § 261.21) decreases by the number of percentage points the prior-year caseload fell in comparison to the caseload in the base year established by Congress.</P>
                    <P>(2) * * *</P>
                    <P>
                        (i) The number of percentage points the prior-year two-parent caseload, including two-parent cases receiving assistance under a separate State program (as provided at § 261.42(b)), fell in comparison to the two-parent 
                        <PRTPAGE P="17235"/>
                        caseload in the base year established by Congress, including two-parent cases receiving assistance under a separate State program; or
                    </P>
                    <P>(ii) The number of percentage points the prior-year overall caseload, including assistance under a separate State program (as provided at § 261.42(b)), fell in comparison to the overall caseload in the base year established by Congress, including cases receiving assistance under a separate State program.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>5. Revise paragraph (b)(1) of § 261.40 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.40 </SECTNO>
                    <SUBJECT>Is there a way for a State to reduce the work participation rates?</SUBJECT>
                    <STARS/>
                    <P>(b)(1) The calculations in paragraph (a) of this section must disregard caseload reductions due to requirements of Federal law and to changes that a State has made in its eligibility criteria in comparison to its criteria in effect in the base year established by Congress.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>6. Revise paragraph (c) of § 261.40 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.40 </SECTNO>
                    <SUBJECT>Is there a way for a State to reduce the work participation rates?</SUBJECT>
                    <STARS/>
                    <P>(c)(1) To establish the caseload base and to determine the comparison-year caseload, we will use the combined TANF and separate State program caseload figures reported on Form ACF-199, TANF Data Report, and Form ACF-209, SSP-MOE Data Report, respectively.</P>
                    <P>(2) To qualify for a caseload reduction, a State must have reported monthly caseload information, including cases in separate State programs, for the base year and the comparison year for cases receiving assistance as defined at § 261.43.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>7. Revise paragraphs (d)(2) and (e) of § 261.40 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.40</SECTNO>
                    <SUBJECT> Is there a way for a State to reduce the work participation rates?</SUBJECT>
                    <STARS/>
                    <P>(d) * * *</P>
                    <P>(2) We will adjust both the baseline and the comparison-year caseload information, as appropriate, based on these State submissions.</P>
                    <P>(e) We refer to the number of percentage points by which a caseload falls, disregarding the cases described in paragraph (b) of this section and cases described in paragraph (b) of § 261.43, as a caseload reduction credit.</P>
                </SECTION>
                <AMDPAR>8. Amend § 261.42(a)(1) by revising the first sentence to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.42 </SECTNO>
                    <SUBJECT>Which reductions count in determining the caseload reduction credit?</SUBJECT>
                    <P>(a)(1) A State's caseload reduction credit must not include caseload decreases due to Federal requirements or State changes in eligibility rules since the base year that directly affect a family's eligibility for assistance.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>9. Revise §§ 261.42(a)(2) and (3) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.42 </SECTNO>
                    <SUBJECT>Which reductions count in determining the caseload reduction credit?</SUBJECT>
                    <STARS/>
                    <P>(a) * * *</P>
                    <P>(2) At State option, a State's caseload reduction credit may include caseload increases due to Federal requirements or State changes in eligibility rules since the base year if used to offset caseload decreases in paragraph (a)(1) of this section.</P>
                    <P>(3) A State may not receive a caseload reduction credit that exceeds the actual caseload decline between the base year and the comparison year, other than as a result of § 261.43(b).</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>10. Amend § 261.42(b) by revising the first sentence to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.42</SECTNO>
                    <SUBJECT> Which reductions count in determining the caseload reduction credit?</SUBJECT>
                    <P>(b) A State must include cases receiving assistance in separate State programs as part of its base year caseload and comparison-year caseload.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>11. Revise § 261.43(b)(2)(iv) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 261.43</SECTNO>
                    <SUBJECT> What is the definition of a “case receiving assistance” in calculating the caseload reduction credit?</SUBJECT>
                    <STARS/>
                    <P>(b) * * *</P>
                    <P>(2) * * *</P>
                    <P>(iv) All financial data must agree with data reported on the TANF Financial Report (form ACF-196R) and all caseload data must agree with data reported on the TANF Data and SSP-MOE Data Reports (forms ACF-199 and ACF-209).</P>
                    <STARS/>
                </SECTION>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Robert F. Kennedy, Jr.,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06632 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-36-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <CFR>45 CFR Part 1351</CFR>
                <RIN>RIN 0970-AD37</RIN>
                <SUBJECT>Reducing Bureaucracy and Burden for Children, Youth, and Family Programs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Family and Youth Services Bureau (FYSB), Administration on Children, Youth and Families (ACYF), Administration for Children and Families (ACF), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Health and Human Services, Administration for Children and Families proposes to remove duplicative or unnecessary sections from the Runaway and Homeless Youth Program regulations (45 CFR part 1351). These amendments will streamline the Runaway and Homeless Youth Program regulations to make them more accessible to the public. The docket on 
                        <E T="03">https://www.regulations.gov</E>
                         will include a plain language summary of the NPRM.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>In order to be considered, written comments on this proposed rule must be received on or before May 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit written comments, identified by docket number ACF-2026-0397 and/or RIN number 0970-AD37, by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: Deregulation@acf.hhs.gov.</E>
                         Include the docket number ACF-2026-0397 and/or RIN number 0970-AD37 in the subject line of the message.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number or RIN number for this rulemaking. All comments received are a part of the public record and will be posted for public viewing on 
                        <E T="03">www.regulations.gov,</E>
                         without change. Please be advised that the substance of the comments and the identity of individuals or entities submitting the comments will be subject to public disclosure. Anonymous comments are accepted.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Adam N. Jones, Deputy Chief of Staff, Immediate Office of the Assistant Secretary, Administration for Children and Families, Department of Health and 
                        <PRTPAGE P="17236"/>
                        Human Services, Washington, DC 202-417-0115 or 
                        <E T="03">Deregulation@acf.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Statutory Authority</HD>
                <P>This proposed NPRM is being issued under the authority granted to the Secretary of Health and Human Services by the Runaway and Homeless Youth Act of 1974, as amended, hereafter referred to as the “Act,” at 34 U.S.C. 11202.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>
                    The Runaway and Homeless Youth (RHY) Program, authorized under the Runaway and Homeless Youth Act (34 U.S.C. 11201 
                    <E T="03">et seq.</E>
                    ), enables HHS to provide grants to public and nonprofit private entities to deliver services to runaway and homeless youth and youth at risk of homelessness. The RHY program includes the Basic Center Program, the Transitional Living Program (including the Maternity Group Home Program), and the Street Outreach Program, which together support emergency shelter, transitional housing, outreach, counseling, and related services to promote youth safety, well-being, and long-term stability. The RHY program also funds a national communications system, grants for training and technical assistance, and grants for research, evaluation, training, and service projects. HHS has issued regulations for the RHY Program at 45 CFR part 1351.
                </P>
                <P>
                    HHS initially published regulations for the RHY Program on November 20, 1978. Office of Human Development Services, Department of Health, Education, and Welfare, 43 FR 55634 (Nov. 20, 1978) (codified at 45 CFR pt. 1351). The regulations were most recently amended in 2016. Runaway and Homeless Youth, 81 FR 93030 (Dec. 20, 2016). The most recent revisions added program performance standards and provided additional updates to reflect changes in the RHY Act made through the Reconnecting Homeless Youth Act of 2008 (Pub. L. 110-378). 
                    <E T="03">See</E>
                     Runaway and Homeless Youth, 81 FR 93030, 93030 (Dec. 20, 2016). HHS now proposes revisions to 45 CFR part 1351 to clarify program requirements, reduce unnecessary administrative burden, and better align the regulations with current statutory authority and language, while maintaining program operations and effective management of grant funds.
                </P>
                <HD SOURCE="HD1">III. Executive Summary</HD>
                <P>This NPRM proposes to rescind multiple regulation sections that are either duplicative or unnecessary. The regulation sections contained in this NPRM to be removed and reserved can be designated into two categories: those that are duplicative and those that are unnecessary because they are better suited for a different format other than regulation.</P>
                <P>The sections of the RHY regulations proposed for removal because they are duplicative are 45 CFR 1351.11, 45 CFR 1351.12, 45 CFR 1351.13, and 45 CFR 1351.20. Duplicative regulations impose no new obligations and offer no new guidance because the authority and requirements are pulled directly from other statutes and regulations.</P>
                <P>
                    45 CFR 1351.11 is duplicative because it merely restates RHY grant eligibility requirements articulated in the Act at 34 U.S.C. 11211(a)(1), 34 U.S.C. 11221, and 34 U.S.C. 11261(a). The regulation section offers no information or clarification that is not otherwise found in the statute. Similarly, 45 CFR 1351.12 explains how the Secretary prioritizes awards for RHY grants but does not extend discussion beyond the associated statutory language. 45 CFR 1351.13 addresses grant matching requirements that are also found in the statute; here, the statute includes even more detail than the regulation, leaving the regulation section without purpose. 
                    <E T="03">Compare</E>
                     34 U.S.C. 11274 
                    <E T="03">with</E>
                     45 CFR 1351.13. Finally, 45 CFR 1351.20 lists Government-wide and HHS-wide regulations that apply to RHY grant programs. The cited regulations apply to grant recipients and subrecipients regardless of whether they are listed in the RHY regulations, so their inclusion in the RHY regulations creates no additional authority. Further, the list of authorities included at 45 CFR 1351.20 is not an exhaustive list of all Federal regulations that apply to grant recipients and subrecipients, making its inclusion in the RHY regulations not merely duplicative but potentially confusing. 
                    <E T="03">See</E>
                     Runaway and Homeless Youth, 81 FR 93030, 93044-45 (Dec. 20, 2016).
                </P>
                <P>Several sections of the RHY regulations are proposed for removal because they are unnecessary and better suited for a different format, such as a Notice of Funding Opportunity (NOFO). The RHY regulation sections proposed as unnecessary are 45 CFR 1351.10, 45 CFR 1351.14, 45 CFR 1351.15, 45 CFR 1351.17, 45 CFR 1351.24, 45 CFR 1351.25, and 45 CFR 1351.27.</P>
                <P>45 CFR 1351.10 articulates the general purpose of the RHY Program. This section merely summarizes the programs funded by the RHY Act and outlines ACF's goals for the RHY Program. It imposes no obligations on grant recipients or applicants, nor does it give any guidance on how to interpret relevant statutory language. We propose removal because the content in this regulation section could assist grant applicants and recipients more effectively in the introduction to a NOFO or in fact sheets distributed by ACF.</P>
                <P>45 CFR 1351.14 is proposed for removal because its sole purpose is to provide RHY grant applicants recipients with information about project periods. NOFOs routinely provide grant applicants and recipients with identical information about grant project periods, making this regulation section unnecessary.</P>
                <P>
                    45 CFR 1351.15-16 include descriptions of allowable costs (45 CFR 1351.15) and unallowable costs (45 CFR 1351.16) and are also better suited for NOFOs than for regulations. The language in these sections also appears elsewhere in the RHY regulations, making such content duplicative as well as unnecessary. See, 
                    <E T="03">e.g.,</E>
                     45 CFR 1351.16(b) (prohibiting activities already listed as unallowable at 45 CFR 1351.1 under the definition of “counseling services”).
                </P>
                <P>45 CFR 1351.17 purports to address RHY grant application requirements but includes no guidance on application requirements other than referral to NOFO content (referenced as a “funding opportunity announcement” in regulation). This regulation section serves no purpose for grant applicants seeking clarity on application requirements other than to point them to a document that they already understood that they would need to follow. As such, it is unnecessary, and we propose removal.</P>
                <P>
                    45 CFR 1351.24, 45 CFR 1351.25, and 45 CFR 1351.27 are unnecessary for the same reasons as the regulation sections described above. These three sections include a list of additional requirements for the Basic Center Program (45 CFR 1351.24), the Transitional Living Program and Maternity Group Home Program (45 CFR 1351.25), and the Street Outreach Program (45 CFR 1351.27). Each section discussed here includes a subsection indicating that the NOFOs (referenced in regulation as “funding opportunity announcement”) will include additional program requirements. 
                    <E T="03">See</E>
                     45 CFR 1351.24(f), 45 CFR 1351.25(b), 45 CFR 1351.27(c). Grant applicants and recipients will therefore need to rely on the NOFO to gain a full understanding of grant requirements already, so removing these sections of the RHY regulations promotes clarity and reduces burdensome materials.
                    <PRTPAGE P="17237"/>
                </P>
                <HD SOURCE="HD2">Severability</HD>
                <P>The purpose of this section is to clarify ACF's intent with respect to the severability of the provisions of this NPRM. As explained above, ACF proposes removing sections of the RHY regulations because it is determined that doing so would make the regulations clearer, less burdensome, and more accessible to the public. To the extent that any portion of the proposed removals are declared invalid by a court, ACF intends for all other provisions of this proposed rule to remain in effect to the greatest extent possible to ensure that the RHY regulations remain as concise and accessible as possible. None of the provisions proposed for removal in this NPRM are dependent on the validity of other, separate provisions.</P>
                <HD SOURCE="HD1">IV. Discussion of Proposed Changes</HD>
                <HD SOURCE="HD2">45 CFR Part 1351 Runaway and Homeless Youth Program</HD>
                <HD SOURCE="HD2">Subpart B—Runaway and Homeless Youth Program Grants</HD>
                <HD SOURCE="HD3">Section 1351.10 What is the purpose of Runaway and Homeless Youth Program grants?</HD>
                <P>This Section is proposed for removal because it is unnecessary. This Section explains the general purpose of Runaway and Homeless Youth Program grants but provides no instructions to grant applicants or recipients, nor does it impose any new obligations. Thus, this Section is not needed in regulation and would better serve grant applicants and recipients if it were moved into the opening of a Notice of Funding Opportunity (NOFO) and described elsewhere in sub-regulatory guidance.</P>
                <HD SOURCE="HD3">Section 1351.11 Who is eligible to apply for a Runaway and Homeless Youth Program grant?</HD>
                <P>This Section discusses eligibility for RHY Program grants. It is proposed for removal because it generally duplicates statutory language. This Section is not needed in regulation because the statute that authorizes this Section (Sections 11211(a)(1), 11222, and 11261(a) of the RHY Act) is already prescriptive in terms of eligibility for grant funds and the regulatory language does not provide additional clarification.</P>
                <HD SOURCE="HD3">Section 1351.12 Who gets priority for the award of a Runaway and Homeless Youth Program grant?</HD>
                <P>
                    This Section discusses which applicants receive priority for the RHY Program grant awards. This Section is proposed for removal because it is largely duplicative of statutory text from the RHY Act. In most cases, the language used in this regulation section is identical to the language describing grant eligibility requirements in the statute. 
                    <E T="03">See</E>
                     34 U.S.C. 11213(b) (priority requirements for the Basic Center Program); 34 U.S.C. 11222(b) (priority requirements for the Transitional Living Program); 34 U.S.C. 11261(b) (priority requirements for the Street Outreach Program); 34 U.S.C. 11231 (priority requirements for the national communications system) 34 U.S.C. 11243(b) (priority requirements for research, evaluation, demonstration and service projects).
                </P>
                <P>Where the regulatory language has modified statutory language slightly, such as at 45 CFR 1351(d) (expanding the statutory requirement for the national communications grant to prioritize applicants with experience providing telephonic services to runaway and homeless youth to prioritize applicants who have experience providing “electronic communication services”), distinctions can be explained via NOFO. NOFOs can likewise appropriately articulate 45 CFR 1351.12(f), which requires the Secretary to incorporate program performance standards listed at 45 CFR 1351.30-32 into grantmaking, monitoring, and evaluation. This subsection already states that NOFOs will include such content.</P>
                <HD SOURCE="HD3">Section 1351.13 What are the Federal and non-Federal match requirements under a Runaway and Homeless Youth Program grant?</HD>
                <P>
                    This Section discusses match requirements for RHY Program grants. This Section is proposed for removal because it duplicates statutory match requirements almost exactly. 
                    <E T="03">Compare</E>
                     34 U.S.C. 11274 
                    <E T="03">with</E>
                     45 CFR 1351.13. This section adds nothing to assist the public understand the statutory match requirement better than the statute and therefore serves no purpose.
                </P>
                <HD SOURCE="HD3">Section 1351.14 What is the period for which a grant will be awarded?</HD>
                <P>This Section discusses the grant period for RHY Program grants. This Section is proposed for removal because it is unnecessary. Information about grant periods already appears in NOFOs and is better suited there. Furthermore, this Section is ambiguous because it states, “generally the grant will initially be for one year.” Corresponding language in NOFOs is therefore already necessary to inform grant applicants and recipients about the specific period of their grants.</P>
                <HD SOURCE="HD3">Section 1351.15 What costs are supportable under a Runaway and Homeless Youth Program grant?</HD>
                <P>This Section discusses allowable costs for RHY Program grants. This Section is proposed for removal because grant terms and conditions, including allowable expenditures of a grant, are best suited for NOFOs and other grant documents and in most cases, already appear in those documents. Including them in regulation is unnecessary.</P>
                <HD SOURCE="HD3">Section 1351.16 What costs are not allowable under a Runaway and Homeless Youth Program grant?</HD>
                <P>This Section discusses non-allowable costs for RHY Program grants. As with 45 CFR 1351.15, this Section is proposed for removal because grant terms and conditions, including lists of unallowable expenditures of a grant, are best suited for NOFOs and other grant documents. NOFOs already include lists of unallowable expenses, including those listed in this Section.</P>
                <P>This Section is also duplicative in part. 45 CFR 1351.1 already prohibits the activities described in 45 CFR 1351.16(b); there is no need to include the same expense prohibition twice in the RHY regulations.</P>
                <HD SOURCE="HD3">Section 1351.17 How is application made for a Runaway and Homeless Youth Program grant?</HD>
                <P>This Section discusses the process of applying for RHY Program grants. We propose removal because this section is unnecessary; it merely directs grant applicants to follow the instructions in the NOFO (references in regulation as “funding opportunity announcements”) without further detail or clarification.</P>
                <HD SOURCE="HD2">Subpart C—Additional Requirements</HD>
                <HD SOURCE="HD3">Section 1351.20 What Government-wide and HHS-wide regulations apply to these programs?</HD>
                <P>
                    This Section is proposed for removal because it is duplicative. The Section restates a list of Federal regulations applicable to RHY grant recipients and subrecipients without explanation of why each regulation is flagged yet excludes other Federal regulations that apply to all grant recipients and subrecipients. 
                    <E T="03">See</E>
                     Runaway and Homeless Youth, 81 FR 93030, 93044-45 (Dec. 20, 2016) (“This new list does not attempt to list all of the Federal laws and regulations . . . that pertain to organizations that may be grant awardees.”). The listed regulations apply to RHY grant recipients and subrecipients (and in many cases, all HHS or Federal agency grant recipients and subrecipients) regardless of whether 
                    <PRTPAGE P="17238"/>
                    they are included in the RHY regulations, and the arbitrary nature by which the listed regulations were selected for inclusion demonstrates further that this section serves no purpose.
                </P>
                <HD SOURCE="HD3">Section 1351.24 What are the additional requirements that the Basic Center Program grantees must meet?</HD>
                <P>
                    This Section discusses requirements for the Basic Center Program. This Section is proposed for removal because it is unnecessary. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. Further, this Section already directs grant applicants and recipients to the NOFO (referred to as the “funding opportunity announcement”) for additional requirements, making any guidance provided by the regulation incomplete. 
                    <E T="03">See</E>
                     45 CFR 1351.24(f).
                </P>
                <HD SOURCE="HD3">Section 1351.25 What are the additional requirements that the Transitional Living Program and Maternity Group Home grantees must meet?</HD>
                <P>
                    This Section discusses requirements for the Transitional Living Program and Maternity Group Home grant. This Section is proposed for removal because it is unnecessary. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. Further, this Section already directs grant applicants and recipients to the NOFO (referred to as the “funding opportunity announcement”) for additional requirements, making any guidance provided by the regulation incomplete. 
                    <E T="03">See</E>
                     45 CFR 1351.25(b).
                </P>
                <HD SOURCE="HD3">Section 1351.27 What are the additional requirements that the Street Outreach Program grantees must meet?</HD>
                <P>
                    This Section discusses requirements for Street Outreach Program. This Section is proposed for removal because it is unnecessary. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. Further, this Section already directs grant applicants and recipients to the NOFO (referred to as the “funding opportunity announcement”) for additional requirements, making any guidance provided by the regulation is incomplete. 
                    <E T="03">See</E>
                     45 CFR 1351.27(c).
                </P>
                <HD SOURCE="HD1">V. Regulatory Process Matters</HD>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>
                    Under the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     as amended) (PRA), all Departments are required to submit to the Office of Management and Budget (OMB) for review and approval any reporting or recordkeeping requirements inherent in a proposed or final rule. This NPRM does not contain any information requiring OMB approval under the PRA and, therefore, will not create any new paperwork burdens or modify existing burdens subject to OMB review.
                </P>
                <HD SOURCE="HD2">Executive Order 13132</HD>
                <P>Executive Order 13132 requires federal agencies to consult with State and local government officials if they develop regulatory policies with federalism implications. Federalism is rooted in the belief that issues that are not national in scope or significance are most appropriately addressed by the level of government close to the people. This proposed rule would not have substantial direct impact on the States, on the relationship between the federal government and the States, or on the distribution of power and responsibilities among the various levels of government. This NPRM would not pre-empt State law. The changes proposed in the NPRM are removing duplicative and unnecessary regulations from the Family and Youth Services Bureau rules. Therefore, in accordance with Section 6 of Executive Order 13132, it is determined that this action does not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement.</P>
                <HD SOURCE="HD2">Assessment of Federal Regulations and Policies on Families</HD>
                <P>Assessment of Federal Regulations and Policies on Families Section 654 of the Treasury and General Government Appropriations Act of 1999 (Pub. L. 105-277) requires federal agencies to determine whether a policy or regulation may negatively affect family well-being. If the agency determines a policy or regulation negatively affects family well-being, then the agency must prepare an impact assessment addressing seven criteria specified in the law. HHS believes it is not necessary to prepare a family policymaking assessment because the actions proposed in this NPRM will not have any impact on the autonomy or integrity of the family as an institution.</P>
                <HD SOURCE="HD1">VI. Regulatory Impact Analysis</HD>
                <P>We have examined the impacts of the proposed rule under Executive Order 12866, Executive Order 13563, Executive Order 14192, the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                <P>Executive Orders 12866 and 13563 direct us to assess all benefits and costs of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits. Rules are “significant” under Executive Order 12866 Section 3(f)(1) if they “have an annual effect on the economy of $100 million or more; or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local or tribal governments or communities.” Executive Order 14192 requires that any new incremental costs associated with significant new regulations “shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least ten prior regulations.” The Office of Information and Regulatory Affairs (OIRA) has determined that this proposed rule is not a significant action under Executive Order 12866 Section 3(f). This analysis indicates that the proposed rule, if finalized would be a deregulatory action as defined by Section 3 of Executive Order 14192.</P>
                <P>The Regulatory Flexibility Act (RFA) requires agencies to consider the impact of their regulatory proposals on small entities. Because this is simply repealing obsolete and unnecessary language, we propose to certify that the proposed rule would not have a significant economic impact on a substantial number of small entities.  </P>
                <P>The Unfunded Mandates Reform Act of 1995 (UMRA) generally requires that each agency conduct a cost-benefit analysis; identify and consider a reasonable number of regulatory alternatives; and select the least costly, most cost effective, or least burdensome alternative that achieves the objectives of the rule before promulgating any proposed or final rule that includes a Federal mandate that may result in expenditures of more than $100 million (adjusted for inflation) in at least one year by State, local, and tribal governments, in the aggregate, or by the private sector. Each agency issuing a rule with relevant effects over that threshold must also seek input from State, local, and tribal governments. The current threshold after adjustment for inflation is $193 million, using the most current (2005) Implicit Price Deflator for the Gross Domestic Product. This proposed rule would not result in an expenditure in any year that meets or exceeds this amount.</P>
                <HD SOURCE="HD1">VII. Tribal Consultation Statement</HD>
                <P>
                    Executive Order 13175, 
                    <E T="03">Consultation and Coordination with Indian Tribal Governments,</E>
                     requires agencies to 
                    <PRTPAGE P="17239"/>
                    consult with Indian Tribes when regulations have “substantial direct effects on one or more Indian Tribes, on the relationship between the Federal Government and Indian Tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes.” Similarly, ACF's Tribal Consultation Policy says that consultation is triggered for any legislative proposal, new rule adoption, or other policy change that significantly affects Tribes, meaning there exists a reasonable presumption that it has or may have substantial direct effects on one or more Indian Tribes, on the relationship between the Federal Government and Indian tribes, on the amount or duration of ACF program funding, on the delivery of ACF programs or services to one or more Indian Tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes. However, as this is a deregulatory action, per OMB M-25-36, 
                    <E T="03">Streamlining the Review of Deregulatory Actions,</E>
                     this action presumptively does not trigger the Tribal Consultation requirements of Executive Order 13175 nor does it meet ACF's standard for consultation.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 45 CFR Part 1351</HD>
                    <P>Administrative practice and procedure, Grant programs-social programs, Homeless, Reporting and recordkeeping requirements, Technical assistance, Youth.</P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, ACF proposes to amend 45 CFR part 1351 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1351—RUNAWAY AND HOMELESS YOUTH PROGRAM</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 1351 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                         34 U.S.C. 11201 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1351.10</SECTNO>
                    <SUBJECT> [Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>2. Remove and reserve § 1351.10.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.11</SECTNO>
                    <SUBJECT> [Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>3. Remove and reserve § 1351.11.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.12 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>4. Remove and reserve § 1351.12.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.13 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>5. Remove and reserve § 1351.13.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.14</SECTNO>
                    <SUBJECT> [Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>6. Remove and reserve § 1351.14.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.15 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>7. Remove and reserve § 1351.15.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.16 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>8. Remove and reserve § 1351.16.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.17</SECTNO>
                    <SUBJECT> [Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>9. Remove and reserve § 1351.17.</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1351.20 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>10. Remove and reserve § 1351.20.</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1351.24 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>11. Remove and reserve § 1351.24.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1351.25 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>12. Remove and reserve § 1351.25.</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1351.27 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>13. Remove and reserve § 1351.27.</AMDPAR>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Robert F. Kennedy, Jr.,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06646 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-33-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <CFR>45 CFR Part 1370</CFR>
                <RIN>RIN 0970-AD42</RIN>
                <SUBJECT>Reducing Bureaucracy and Burden in Family Violence and Prevention Services</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Family Violence Prevention and Services (OFVPS), Administration for Children and Families (ACF), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Health and Human Services, Administration for Children and Families, proposes to remove duplicative or unnecessary Sections from the Family Violence Prevention and Services program regulations (45 CFR part 1370). These amendments will streamline the Family Violence Prevention and Services regulations and make them more accessible to the public. The docket on 
                        <E T="03">https://www.regulations.gov</E>
                         will include a plain language summary of the NPRM.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>In order to be considered, written comments on this proposed rule must be received on or before May 6, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES: </HD>
                    <P>You may submit written comments, identified by docket number ACF-2026-0430 and/or RIN number 0970-AD42, by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: Deregulation@acf.hhs.gov.</E>
                         Include the docket number ACF-2026-0430 and/or RIN number 0970-AD42 in the subject line of the message.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number or RIN number for this rulemaking. All comments received are a part of the public record and will be posted for public viewing on 
                        <E T="03">www.regulations.gov,</E>
                         without change. Please be advised that the substance of the comments and the identity of individuals or entities submitting the comments will be subject to public disclosure.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Adam N. Jones, Deputy Chief of Staff, Immediate Office of the Assistant Secretary, Administration for Children and Families, Department of Health and Human Services, Washington, DC, 202-417-0115 or 
                        <E T="03">Deregulation@acf.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Statutory Authority</HD>
                <P>This proposed NPRM is being issued under the authority granted to the Secretary of Health and Human Services by the Family Violence Prevention and Services Act (FVPSA) at 42 U.S.C. 10404(a)(4).</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>
                    45 CFR part 1370, “Family Violence Prevention and Services Programs” is a regulatory package established under FVPSA, as amended (42 U.S.C. 10401 
                    <E T="03">et seq.</E>
                    ), that governs the administration of multiple federal grants implemented for the purposes of increasing public awareness about and preventing family violence, domestic violence, and dating violence; providing immediate shelter and supportive services for victims of family violence, domestic violence, and dating violence and their dependents; providing for technical assistance and training relating to family violence, domestic violence, and dating violence programs; providing for State Domestic Violence Coalitions; providing specialized services for abused parents and their children; and operating a national domestic violence hotline.
                </P>
                <P>
                    The FVPSA regulations were initially published on February 22, 1996 (Family Violence Prevention and Services Programs, 61 FR 6791 (Feb. 22, 1996) (codified at 45 CFR pt. 1370)). They were amended on November 2, 2016. Family Violence and Prevention Services Program, 81 FR 76446 (Nov. 2, 2016) (codified at 45 CFR pt. 1370). The amended regulations reflected FVPSA's 
                    <PRTPAGE P="17240"/>
                    most recent reauthorization under the Child Abuse Prevention and Treatment (CAPTA) Reauthorization Act of 2010 (Pub. L. 111-320). 
                    <E T="03">See</E>
                     81 FR 76446, 76446. FVPSA has not been amended since 2010 and the FVPSA regulations have not been amended since 2016.
                </P>
                <HD SOURCE="HD1">III. Executive Summary</HD>
                <P>This NPRM proposes to rescind two Sections of the FVPSA regulations that are duplicative or unnecessary. These rescissions would impact States, Territories, Tribes, and nongovernmental entities. The regulation Sections to be removed and reserved can be designated into two categories: those that are duplicative and those that are unnecessary because they are better suited for a different format other than regulation.</P>
                <P>45 CFR 1370.1 is proposed for removal because it is unnecessary. This regulation Section articulates the general purpose of FVPSA grants but merely summarizes the programs funded by the Act. It imposes no obligations on grant recipients or applicants, not does it give any guidance on how to interpret relevant statutory language. We propose removal because the content in this regulation Section could assist grant applicants and recipients more effectively in the introduction to a Notice of Funding Opportunity (“NOFO”) or in fact sheets distributed by ACF.</P>
                <P>
                    45 CFR 1370.3 is proposed for removal because it is duplicative. It imposes no new obligations and offers no new guidance because the authority and requirements are pulled directly from other statutes and regulations. 45 CFR 1370.3 lists Government-wide and HHS-wide regulations that apply to FVPSA grant recipients and subrecipients. The cited regulations apply to grant recipients and subrecipients regardless of whether they are listed in the FVPSA regulations, so their inclusion in the FVPSA regulations creates no additional authority. We propose removal of this Section because it serves no purpose other than to repeat requirements that are available elsewhere. Further, the list of authorities included at 45 CFR 1370.3 is not an exhaustive list of all Federal regulations that apply to grant recipients and subrecipients, making its inclusion in the FVPSA regulations not merely duplicative but potentially confusing. 
                    <E T="03">See</E>
                     Family Violence Prevention and Services Program, 80 FR 61890, 61896 (proposed Oct. 14, 2015).
                </P>
                <P>45 CFR 1370.6 is proposed for removal because it is unnecessary and better suited to a different format such as sub-regulatory guidance or inclusion in a NOFO. 45 CFR 1370.6 addresses requirements for reports and evaluations for FVPSA formula grants. The first part of the regulation merely restates the reporting requirement listed in the FVPSA statute at 42 U.S.C. 10406(d). The rest of the regulation does not impose an obligation on grant recipients, but rather, clarifies that Territorial governments must also submit a performance report unless they consolidate FVPSA funds with other HHS funds in a Consolidated Block Grant under 45 CFR part 97, in which case they do not need to submit a performance report. ACF initially added this clarifying language to address earlier questions about reporting requirements for Territorial grantees. See Family Violence Prevention and Services Program, 80 FR 61890, 61899 (proposed Oct. 14, 2015). Territories that have consolidated FVPSA funds with other HHS funds in a Consolidated Block Grant are bound by 48 U.S.C. 1469a and 45 CFR part 97 and are already on notice that they do not need to submit a separate performance report for FVPSA compliance. This Section of the regulation is unnecessary because grant recipients and subrecipients are already informed about reporting requirements through existing NOFOs, the FVPSA statute itself, and other applicable law and regulations. Grant documents and sub-regulatory guidance are better suited than regulation to answer questions from any grant recipient, including Territories, about reporting obligations.</P>
                <P>
                    45 CFR 1370.30, 45 CFR 1370.31, and 45 CFR 1370.32 are proposed for removal because they are in part duplicative of statutory language and in part unnecessary. These three Sections address requirements for National Resource Center and Training and Technical Assistance grants (45 CFR 1370.30), requirements for specialized services for abused parents and their children (“SSAPC”) grants (45 CFR 1370.31), and requirements for National Domestic Violence Hotline grants (45 CFR 1370.32). Most of the language in these Sections repeats requirements articulated clearly in statute and serves no purpose in regulation. 
                    <E T="03">Compare</E>
                     42 U.S.C. 10410 
                    <E T="03">with</E>
                     45 CFR 1370.30; 42 U.S.C. 10412 
                    <E T="03">with</E>
                     45 CFR 1370.32; 42 U.S.C. 10411 
                    <E T="03">with</E>
                     45 CFR 1370.31.
                </P>
                <P>
                    Although much of the FVPSA regulation restates statutory language in these three Sections, even language that diverges from statutory requirements is not necessary to include in regulation. Conversely, other Sections of the FVPSA regulation restate the authorizing statute in part but also include additional requirements not found in statute that are necessary for program operation. See, 
                    <E T="03">e.g.,</E>
                     45 CFR 1370.10 (outlining requirements for State and Indian Tribal grants and describing consultation requirements for Tribes), 45 CFR 1370.20 (describing requirements for State Domestic Violence Coalitions and detailing the process through which ACF designates entities to serve as State Domestic Violence Coalitions). In 45 CFR 1370.30-32, where regulatory language expands on or diverges from statutory language, such as SSAPC grant application requirements listed in 45 CFR 1371.31(b), content can be shifted from regulatory text to NOFOs and other grant documents without negative consequences. Indeed, all NOFOs must include all application requirements already, and agency expectations that differ from those listed in the statute are especially important to explain via grant application documents regardless of whether they are already located in regulation.
                </P>
                <HD SOURCE="HD2">Severability</HD>
                <P>The purpose of this Section is to clarify ACF's intent with respect to the severability of the provisions of this NPRM. As explained above, ACF proposes removing Sections of the FVPSA regulations because we determined that doing so would make the regulations clearer, less burdensome, and more accessible to the public. To the extent that any portion of the proposed removals are declared invalid by a court, ACF intends for all other provisions of this proposed rule to remain in effect to the greatest extent possible to ensure that FVPSA regulations remain as concise and accessible as possible. None of the provisions contained herein are central to an overall intent of the proposed rule, nor are any provisions dependent on the validity of other, separate provisions.</P>
                <HD SOURCE="HD1">IV. Discussion of Proposed Changes</HD>
                <HD SOURCE="HD2">45 CFR Part 1370 Family Violence Prevention and Services Programs</HD>
                <HD SOURCE="HD2">Subpart A—General Provisions</HD>
                <HD SOURCE="HD3">Section 1370.1 What are the purposes of the Family Violence Prevention and Services Act Programs?</HD>
                <P>
                    This Section is proposed for removal because it is unnecessary. This Section explains the general purpose of FVPSA grants but provides no instructions to grant applicants or recipients, nor does it impose any new obligations. Thus, this Section is not needed in regulation and would better serve grant applicants and recipients if it were moved to the 
                    <PRTPAGE P="17241"/>
                    opening of a NOFO and described elsewhere in sub-regulatory guidance.
                </P>
                <HD SOURCE="HD3">Section 1370.3 What Government-Wide and HHS-Wide regulations apply to these programs?</HD>
                <P>This Section is proposed for removal because it is duplicative. The Section restates a list of Federal regulations applicable to FVPSA grant recipients and subrecipients without explanation of why each regulation is flagged yet excludes other Federal regulations that apply to all grant recipients and subrecipients. See Family Violence Prevention and Services Program, 80 FR 61890, 61896 (proposed Oct. 14, 2015) (“This new list does not attempt to list all of the Federal laws and regulations . . . that pertain to organizations that may be grant awardees.”). The listed regulations apply to FVPSA grant recipients and subrecipients (and in many cases, all HHS or Federal agency grant recipients and subrecipients) regardless of whether they are included in FVPSA regulations, and the arbitrary nature by which the listed regulations were selected for inclusion demonstrates further that this Section serves no purpose.</P>
                <HD SOURCE="HD3">Section 1370.6 What requirements for reports and evaluations apply to these programs?</HD>
                <P>This Section is proposed for removal because it is part duplicative and in part unnecessary. This Section merely restates formula grant reporting requirements found in the FVPSA statute at 42 U.S.C. 10406(d) and reporting requirements for Consolidated Block Grants in 45 CFR part 97. While this Section was added to the FVPSA regulations to “clarify requirements that have been questioned in the past,” the FVPSA statute, Standing NOFOs, and existing program instructions are sufficiently clear about reporting requirements to make this Section unnecessary. Any remaining questions about FVPSA performance reports for Territory grant recipients are best addressed in sub-regulatory guidance which would also allow for more detail than the regulatory language includes.</P>
                <HD SOURCE="HD2">Subpart D—Discretionary Grants and Contracts</HD>
                <HD SOURCE="HD3">Section 1370.30 What National Resource Center and Training and Technical Assistance grant programs are available and what additional requirements apply?</HD>
                <P>
                    This Section describes national resource center and training and technical assistance grants authorized in the FVPSA Program at 42 U.S.C. 10410 and lists additional requirements for the grants. This Section is proposed for removal because it is unnecessary. Most of this Section merely summarizes the statutory language, which is already prescriptive in its description of available grants, allowable activities, and eligibility requirements. While the terminology in the regulation Section sometimes differs slightly from the statutory language, this Section includes no new obligations or necessary clarifications. Where the regulation Section provides a more detailed description of program requirements than the statute, such description should be relocated to NOFOs. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. For example, the term “Culturally-Specific Special Issue Resource Centers” appears in the regulation at 45 CFR 1370.30(a)(4) but not in statute, but using this term over the corresponding statutory language at 42 U.S.C. 10410(b)(2)(E) has no impact on grant applicants or recipients. Where the regulation section provides a more detailed description of program requirements than the statute, such description should be relocated to NOFOs. Indeed, this Section already directs grant applicants and recipients to refer to the NOFO (here called a “Funding Opportunity Announcement”) for more information about application requirements, making any guidance provided by this Section incomplete. 
                    <E T="03">See</E>
                     45 CFR 1370.30(b).
                </P>
                <HD SOURCE="HD3">Section 1370.31 What additional requirements apply to grants for specialized services for abused parents and their children?</HD>
                <P>
                    This Section is proposed for removal because it is unnecessary. Most of this Section summarizes authorizing statutory language from 42 U.S.C. 10412, which is already prescriptive in its description of available grants, allowable activities, and eligibility requirements. Where the regulation Section provides a more detailed description of program requirements than the statute, such as in 45 CFR 1370.31(b), such description should be relocated to NOFOs. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. As with 45 CFR 1370.30 cited above, this Section already directs grant applicants and recipients to refer to the NOFO (here called a “Funding Opportunity Announcement”) for more information about application requirements, making any guidance provided by this Section incomplete. 
                    <E T="03">See</E>
                     45 CFR 1370.30(b)(4).
                </P>
                <HD SOURCE="HD3">Section 1370.32 What additional requirements apply to the National Domestic Violence Hotline grants?</HD>
                <P>
                    This Section is proposed for removal because it is unnecessary. Most of this Section summarizes the statutory language at 42 U.S.C. 10411, which is already prescriptive in its description of allowable activities, and eligibility requirements for National Domestic Violence Hotline grants. Where the regulation Section provides a more detailed description of program requirements than the statute or differs from the statute, such as including a definition of “telephone” at 45 CFR 1370.32(b) that incorporates a broader use than the term initially held, such clarifications should be relocated to NOFOs. Grant requirements are better suited for NOFOs or other grant documents, such as supplemental terms and conditions. Indeed, this Section already directs grant applicants and recipients to refer to the NOFO (here called a “Funding Opportunity Announcement”) for more information about application requirements, making any guidance provided by this Section incomplete. 
                    <E T="03">See</E>
                     45 CFR 1370.32(c)(7).
                </P>
                <HD SOURCE="HD1">V. Regulatory Process Matters</HD>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>
                    Under the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     as amended) (PRA), all Departments are required to submit to the Office of Management and Budget (OMB) for review and approval any reporting or recordkeeping requirements inherent in a proposed or final rule. This NPRM does not contain any information requiring OMB approval under the PRA and, therefore, will not create any new paperwork burdens or modify existing burdens subject to OMB review.
                </P>
                <HD SOURCE="HD2">Executive Order 13132</HD>
                <P>
                    Executive Order 13132 requires federal agencies to consult with State and local government officials if they develop regulatory policies with federalism implications. Federalism is rooted in the belief that issues that are not national in scope or significance are most appropriately addressed by the level of government close to the people. This proposed rule would not have substantial direct impact on the States, on the relationship between the federal government and the States, or on the distribution of power and responsibilities among the various levels of government. This NPRM would not pre-empt State law. The changes proposed in the NPRM are removing duplicative and unnecessary regulations from the Office of Family Violence 
                    <PRTPAGE P="17242"/>
                    Prevention and Services regulations. Therefore, in accordance with Section 6 of Executive Order 13132, it is determined that this action does not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement.
                </P>
                <HD SOURCE="HD2">Assessment of Federal Regulations and Policies on Families</HD>
                <P>Assessment of Federal Regulations and Policies on Families Section 654 of the Treasury and General Government Appropriations Act of 1999 (Pub. L. 105-277) requires federal agencies to determine whether a policy or regulation may negatively affect family well-being. If the agency determines a policy or regulation negatively affects family well-being, then the agency must prepare an impact assessment addressing seven criteria specified in the law. HHS believes it is not necessary to prepare a family policymaking assessment because the actions proposed in this NPRM will not have any impact on the autonomy or integrity of the family as an institution.</P>
                <HD SOURCE="HD1">VI. Regulatory Impact Analysis</HD>
                <P>We have examined the impacts of the proposed rule under Executive Order 12866, Executive Order 13563, Executive Order 14192, the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                <P>Executive Orders 12866 and 13563 direct us to assess all benefits and costs of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits. Rules are “significant” under Executive Order 12866 Section 3(f)(1) if they “have an annual effect on the economy of $100 million or more; or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local or tribal governments or communities.” Executive Order 14192 requires that any new incremental costs associated with significant new regulations “shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least ten prior regulations.” The Office of Information and Regulatory Affairs (OIRA) has determined that this proposed rule is not a significant action under Executive Order 12866 Section 3(f). This analysis indicates that the proposed rule, if finalized would be a deregulatory action as defined by Section 3 of Executive Order 14192.</P>
                <P>The Regulatory Flexibility Act (RFA) requires agencies to consider the impact of their regulatory proposals on small entities. Because this NPRM proposes repealing duplicative and unnecessary language, we propose to certify that the proposed rule would not have a significant economic impact on a substantial number of small entities.</P>
                <P>The Unfunded Mandates Reform Act of 1995 (UMRA) generally requires that each agency conduct a cost-benefit analysis; identify and consider a reasonable number of regulatory alternatives; and select the least costly, most cost effective, or least burdensome alternative that achieves the objectives of the rule before promulgating any proposed or final rule that includes a Federal mandate that may result in expenditures of more than $100 million (adjusted for inflation) in at least one year by State, local, and tribal governments, in the aggregate, or by the private sector. Each agency issuing a rule with relevant effects over that threshold must also seek input from State, local, and tribal governments. The current threshold after adjustment for inflation is $193 million, using the most current (2025) Implicit Price Deflator for the Gross Domestic Product. This proposed rule would not result in an expenditure in any year that meets or exceeds this amount.</P>
                <HD SOURCE="HD1">VII. Tribal Consultation Statement</HD>
                <P>
                    Executive Order 13175, 
                    <E T="03">Consultation and Coordination with Indian Tribal Governments,</E>
                     requires agencies to consult with Indian Tribes when regulations have “substantial direct effects on one or more Indian tribes, on the relationship between the Federal government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes.” 
                    <E T="03">Consultation and Coordination With Indian Tribal Governments,</E>
                     65 FR 67249. Similarly, ACF's Tribal Consultation Policy says that consultation is triggered for any legislative proposal, new rule adoption, or other policy change that significantly affects Tribes, meaning there exists a reasonable presumption that it has or many have substantial direct effects on one on more Indian tribes, on the relationship between the Federal Government and Indian Tribes, on the amount or duration of ACF program funding, on the delivery of ACF programs or services to one or more Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. However, as this is a deregulatory action, per OMB M-25-36, 
                    <E T="03">Streamlining the Review of Deregulatory Actions,</E>
                     this action presumptively does not trigger the consultation requirements of Executive Order 13175. ACF is nevertheless committed to consulting with Indian Tribes and Tribal leadership on this action to the extent practicable and permitted by law.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 45 CFR Part 1370</HD>
                    <P>Administrative practice and procedure, Child welfare, Domestic violence, Grant programs—Indians, Grant programs—social programs, Public assistance programs, Reporting and recordkeeping requirements, Technical assistance. </P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, ACF proposes to amend 45 CFR part 1370 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1370—FAMILY VIOLENCE PREVENTION AND SERVICES PROGRAMS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 1370 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        42 U.S.C. 10401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1370.1 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>2. Remove and reserve § 1370.1</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1370.3 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>3. Remove and reserve § 1370.3.</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1370.6 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>4. Remove and reserve § 1370.6.</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1370.30 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>5. Remove and reserve § 1370.30.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1370.31 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>6. Remove and reserve § 1370.31.</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1370.32 </SECTNO>
                    <SUBJECT>[Removed and Reserved]</SUBJECT>
                </SECTION>
                <AMDPAR>7. Remove and reserve § 1370.32.</AMDPAR>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Robert F. Kennedy, Jr.,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06633 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-32-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="17243"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments are requested regarding: whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    Comments regarding this information collection received by May 6, 2026. Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Natural Resources and Conservation Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Reinstatement: Urban Agriculture and Innovation Production Grant Program.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0578-0032.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Agriculture Improvement Act of 2018 (2018 Farm Bill, Pub. L. 115-334) authorized the Farm Production and Conservation (FPAC) mission area and the Natural Resources Conservation Service (NRCS) to award competitive grants to local units of government, school districts, and tribal communities to support the development of urban agriculture and innovative production with the goal of improving access to local foods in areas where access to fresh, healthy food is limited or unavailable.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     The information is utilized by NRCS to determine whether participants meet the eligibility requirements to be a recipient of grant funds. Lack of adequate information to make the determination could result in the improper administration and appropriation of Federal grant funds.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Farms.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     100.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Semi-annually.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     300.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06591 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-16-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments are requested regarding; whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    Comments regarding this information collection received by May 6, 2026 will be considered. Written comments and recommendations for the proposed information collection should be submitted within 30 days of the publication of this notice on the following website 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.
                </P>
                <HD SOURCE="HD1">Food and Nutrition Service</HD>
                <P>
                    <E T="03">Title:</E>
                     WIC Tribal Organizations and U.S. Territories Study.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0584-NEW.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The U.S. Department of Agriculture's (USDA) Food and Nutrition Service (FNS) is conducting a study titled WIC Tribal Organizations and U.S. Territories. This study aims to inform FNS about variations in operations for the Special Supplemental Nutrition Program for Women, Infants, and Children (WIC) among Tribal Organizations, U.S. territories, and geographic States administering the program as local and State agencies.
                </P>
                <P>
                    Congress authorized WIC in 1972 in an amendment to the Child Nutrition Act of 1966 (42 U.S.C. 1786, Sec. 17), which included “Indian tribes” and “intertribal councils” recognized by the Department of the Interior in the definition of State and local agencies. Legislation in 1975 (Pub. L. 94-105) formally established WIC as a permanent national health and nutrition program. Section 28 of the Richard B. 
                    <PRTPAGE P="17244"/>
                    Russell National School Lunch Act as amended by the Healthy, Hunger-Free Kids Act of 2010 (Pub. L. 111-296, Sec. 305) provides general statutory authority for this planned data collection.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     This data collection will inform FNS about WIC operations among 32 Tribal Organizations and 5 U.S. territories administering the program as State agencies and 5 Tribally operated local agencies (collectively referred to as “case study agencies”). Although limited information is available about the experiences of Tribal Organizations and U.S. territories operating WIC, previous research shows that WIC programs in Tribal Organizations and U.S. territories have unique funding and administrative issues and typically have the highest costs across all State agencies. This study will help fill those knowledge gaps and improve FNS's understanding of the strengths and challenges these agencies face when administering and implementing the program. Insights from this study can inform efforts to enhance the effectiveness of WIC program operations and services. This study will also provide FNS with the necessary information to determine WIC coverage rates (
                    <E T="03">i.e.,</E>
                     the share of eligible people who receive WIC benefits). Currently, no other effort can address the research objectives of the proposed study.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     State, local, and tribal governments, Individuals/households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     210.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Once.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     268.47.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06590 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-30-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Rural Business-Cooperative Service</SUBAGY>
                <DEPDOC>[Docket No. RBS-26-BUSINESS-0232]</DEPDOC>
                <SUBJECT>Notice of Funding Opportunity for the Delta Health Care Services Grant (DHCS) for Fiscal Year 2026</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Business-Cooperative Service, U.S. Department of Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of funding opportunity.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Rural Business-Cooperative Service (RBCS or the Agency), a Rural Development (RD) agency of the United States Department of Agriculture (USDA) is issuing a Notice of Funding Opportunity (NOFO) to announce acceptance of grant applications under the Delta Health Care Services Grant Program (DHCS).</P>
                    <P>
                        In future years this funding opportunity will only be announced on the Agency website and 
                        <E T="03">grants.gov</E>
                        , without a 
                        <E T="04">Federal Register</E>
                         notice. Therefore, in future years, neither the funding opportunity nor reference to the funding opportunity in 
                        <E T="03">grants.gov</E>
                         will appear in the 
                        <E T="04">Federal Register</E>
                        . Please make note of this change in location of the funding announcement in your records.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>April 1, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Full funding notice is available on 
                        <E T="03">grants.gov</E>
                        . Program guidance and application forms may be obtained at 
                        <E T="03">https://www.rd.usda.gov/programs-services/business-programs/delta-health-care-services-grant.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ann Stahl, Business Loan and Grant Analyst, USDA, RBCS, Program Management Division, Business Programs, by email 
                        <E T="03">ann.stahl@usda.gov</E>
                         or call (567) 245-3383. For further information on this notice, please contact the RD State Office in the State where the project is located. A list of RD State Office contacts is provided at the following link: 
                        <E T="03">rd.usda.gov/about-rd/offices/state-offices.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The full text of the Notice of Funding Opportunity (NOFO) is available on the Agency website and on 
                    <E T="03">grants.gov</E>
                     using Funding Opportunity Number RDBCP-DHCS-2026 or Assistance Listing Number 10.874—Delta Health Care Services Grant Program.
                </P>
                <SIG>
                    <NAME>Jeremy Claeys,</NAME>
                    <TITLE>Administrator, Rural Business-Cooperative Service, USDA Rural Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06623 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-XY-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meeting of the West Virginia Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the West Virginia Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold a public business meeting via Zoom. The purpose of the meeting is to discuss matters related to the Committee's civil rights project.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Thursday, April 30, 2026, from 1:00 p.m.-2:00 p.m. Eastern Time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held via Zoom Webinar.</P>
                    <P>
                        <E T="03">Registration Link (Audio/Visual): https://www.zoomgov.com/webinar/register/WN_ySdE4A9tRBG1R5yH5XPXoA</E>
                        .
                    </P>
                    <P>
                        <E T="03">Join by Phone (Audio Only):</E>
                         (833) 435-1820 USA Toll-Free; Meeting ID: 160 127 8894.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David Barreras, Designated Federal Officer, at 
                        <E T="03">dbarreras@usccr.gov</E>
                         or (202) 656-8937.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Agenda: (Note: a final meeting agenda will be available prior to the meeting date).</E>
                </P>
                <P>
                    This committee meeting is available to the public through the registration link above. Any interested members of the public may listen to the meeting. An open comment period will be provided to allow members of the public to make oral comments as time allows. Per the Federal Advisory Committee Act, public minutes of the meeting will include a list of persons who are present at the meeting. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Callers will incur no charge for calls they initiate over land-line connections to the toll-free telephone number. Closed captioning will be available by selecting “CC” in the meeting platform. To request additional accommodations, please email 
                    <E T="03">csanders@usccr.gov</E>
                     at least 10 business days prior to the meeting.
                </P>
                <P>
                    Members of the public are entitled to submit written comments; the comments must be received within 30 days following the meeting. Written comments may be emailed to David Barreras 
                    <E T="03">dbarreras@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at (202) 656-8937.
                </P>
                <P>
                    Records generated from this meeting may be inspected and reproduced at the Regional Programs Coordination Unit, as they become available, both before and after the meeting. Records of the meeting will be available via the file sharing website, 
                    <E T="03">https://bit.ly/4d5LbpG.</E>
                     Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">www.usccr.gov,</E>
                     or may contact the Regional Programs 
                    <PRTPAGE P="17245"/>
                    Coordination Unit at the above phone number.
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06639 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Notice of Public Meetings of the New Jersey Advisory Committee to the U.S. Commission on Civil Rights</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of virtual business meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the provisions of the rules and regulations of the U.S. Commission on Civil Rights (Commission) and the Federal Advisory Committee Act, that the New Jersey Advisory Committee (Committee) to the U.S. Commission on Civil Rights will hold public meetings via Zoom. The purpose is for the committee to begin the implementation stage on the committee's chosen topic of antisemitism and civil rights.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>• Monday, April 13, 2026, at 12:00 p.m. Eastern Time.</P>
                    <P>• Thursday, April 30, 2026, at 2:00 p.m. Eastern Time.</P>
                    <P>• Tuesday, May 12, 2026, at 3:00 p.m. Eastern Time.</P>
                </DATES>
                <HD SOURCE="HD1">Registration Links</HD>
                <P>
                    <E T="03">Registration Link (Audio/Visual):</E>
                </P>
                <P>
                    • 
                    <E T="03">4/13: https://www.zoomgov.com/webinar/register/WN_OdgUBPX4QLihlMuT1HdMQA.</E>
                </P>
                <P>
                    ○ 
                    <E T="03">Join by Phone (Audio Only):</E>
                     1-833-435-1820 USA Toll Free; Webinar ID: 160 749 1948#.
                </P>
                <P>
                    • 
                    <E T="03">4/30: https://www.zoomgov.com/webinar/register/WN_9zPNNabKSBy5evljrfndBQ.</E>
                </P>
                <P>
                    ○ 
                    <E T="03">Join by Phone (Audio Only):</E>
                     1-833-435-1820 USA Toll Free; Webinar ID: 161 208 3376 #.
                </P>
                <P>
                    • 
                    <E T="03">5/12: https://www.zoomgov.com/webinar/register/WN_GjX9s-9wRymbPbtFlLzMAA.</E>
                </P>
                <P>
                    ○ 
                    <E T="03">Join by Phone (Audio Only):</E>
                     1-833-435-1820 USA Toll Free; Webinar ID: 160 578 8406 #.
                </P>
                <P>
                    <E T="03">Agenda Links final agendas will be available prior to each meeting date:</E>
                </P>
                <P>
                    • 
                    <E T="03">4/13: https://usccr.box.com/s/b3nhyqwioolup6jdjjp2ulk5q68ah1wo.</E>
                </P>
                <P>
                    • 
                    <E T="03">4/30: https://usccr.box.com/s/4ydfja7x0khrzo4l71cejez641vo68hu.</E>
                </P>
                <P>
                    • 
                    <E T="03">5/12: https://usccr.box.com/s/4hetq4jh7w4jo7kxxizl7hnf5l22i07z.</E>
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Victoria Moreno, Designated Federal Officer, at 
                        <E T="03">vmoreno@usccr.gov</E>
                         or 1-434-515-0204.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee meetings are available to the public through registration links (above). Any interested members of the public may attend committee meetings. An open comment period will be provided to allow members of the public to make oral statements as time allows. Pursuant to the Federal Advisory Committee Act, public minutes of each meeting will include a list of persons who are present. If joining via phone, callers can expect to incur regular charges for calls they initiate over wireless lines, according to their wireless plan. The Commission will not refund any incurred charges. Callers will incur no charge for calls they initiate over land-line connections to the toll-free telephone number. Closed captioning is available by selecting “CC” in the meeting platform. To request additional accommodations, please email 
                    <E T="03">ebohor@usccr.gov</E>
                     at least 10 business days prior to meetings.
                </P>
                <P>
                    Members of the public are entitled to submit written comments; the comments must be received in the regional office within 30 days following the scheduled meeting. Written comments may be emailed to Evelyn Bohor at 
                    <E T="03">ebohor@usccr.gov.</E>
                     Persons who desire additional information may contact the Regional Programs Coordination Unit at 1-202-656-8937.
                </P>
                <P>
                    Records generated from meetings may be inspected and reproduced at the Regional Programs Coordination Unit Office, as they become available, both before and after meetings. Records of the meetings will be available via the file sharing website, 
                    <E T="03">https://tinyurl.com/3ev8d9n9</E>
                     as well as at: 
                    <E T="03">www.facadatabase.gov</E>
                     under the Commission on Civil Rights, selecting the Advisory Committee of interest. Persons interested in the work of this Committee are directed to the Commission's website, 
                    <E T="03">http://www.usccr.gov,</E>
                     or may contact the Regional Programs Coordination Unit at 
                    <E T="03">ebohor@usccr.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06659 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[B-37-2026]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone (FTZ) 21, Notification of Proposed Production Activity; Turbocam Inc.; (Turbine System Components); Ladson, South Carolina</SUBJECT>
                <P>The South Carolina Ports Authority, grantee of FTZ 21, submitted a notification of proposed production activity to the FTZ Board (the Board) on behalf of Turbocam Inc. (Turbocam) for Turbocam's facility in Ladson, South Carolina within FTZ 21. The notification conforming to the requirements of the Board's regulations (15 CFR 400.22) was received on March 30, 2026.</P>
                <P>
                    Pursuant to 15 CFR 400.14(b), FTZ production activity would be limited to the specific foreign-status material(s)/component(s) and specific finished product(s) described in the submitted notification (summarized below) and subsequently authorized by the Board. The benefits that may stem from conducting production activity under FTZ procedures are explained in the background section of the Board's website—accessible via 
                    <E T="03">www.trade.gov/ftz.</E>
                </P>
                <P>The proposed finished products include: turbocharger sliding nozzle ring assemblies (duty rate is duty free).</P>
                <P>The proposed foreign-status materials/components include: actuator rods, steel spacers, rivets, and nozzle rings (duty rates are duty free).</P>
                <P>The request indicates that certain materials/components are subject to duties under section 122 of the Trade Act of 1974 (Section 122), section 232 of the Trade Expansion Act of 1962 (section 232), or section 301 of the Trade Act of 1974 (section 301), depending on the country of origin. The applicable section 122, section 232, and section 301 decisions require subject merchandise to be admitted to FTZs in privileged foreign status (19 CFR 146.41).</P>
                <P>
                    Public comment is invited from interested parties. Submissions shall be addressed to the Board's Executive Secretary and sent to: 
                    <E T="03">ftz@trade.gov.</E>
                     The closing period for their receipt is May 18, 2026.
                </P>
                <P>A copy of the notification will be available for public inspection in the “Online FTZ Information System” section of the Board's website.</P>
                <P>
                    For further information, contact Christopher Williams at 
                    <E T="03">christopher.williams@trade.gov.</E>
                </P>
                <SIG>
                    <PRTPAGE P="17246"/>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Elizabeth Whiteman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06562 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-489-829]</DEPDOC>
                <SUBJECT>Steel Concrete Reinforcing Bar From the Republic of Türkiye: Final Results of the Antidumping Duty Administrative Review; 2023-2024</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) determines that certain producers/exporters of steel concrete reinforcing bar (rebar) from the Republic of Türkiye (Türkiye) subject to this administrative review made sales of subject merchandise at less than normal value during the period of review (POR) July 1, 2023, through June 30, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable April 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Samuel Evans, AD/CVD Operations, Office IX, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-2420.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 12, 2025, Commerce published the 
                    <E T="03">Preliminary Results</E>
                     in the 
                    <E T="04">Federal Register</E>
                     and invited comments from interested parties.
                    <SU>1</SU>
                    <FTREF/>
                     On September 2, 2025, the Rebar Trade Action Coalition (the petitioner) and Colakoglu Metalurji A.S. and Colakoglu Dis Ticaret A.S. (collectively, Colakoglu) submitted case briefs.
                    <SU>2</SU>
                    <FTREF/>
                     On September 11, 2025, the petitioner and Colakoglu submitted rebuttal briefs.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Steel Concrete Reinforcing Bar from the Republic of Türkiye: Preliminary Results and Rescission, in Part, of Antidumping Duty Administrative Review;</E>
                         2023-2024, 90 FR 38743 (August 12, 2025) (
                        <E T="03">Preliminary Results</E>
                        ), and accompanying Preliminary Decision Memorandum (PDM).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         Petitioner's Letter, “RTAC's Case Brief,” dated September 2, 2025; 
                        <E T="03">see also</E>
                         Colakoglu's Letter, “Colakoglu's Case Brief,” dated September 2, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Petitioner's Letter, “RTAC's Rebuttal Brief,” dated September 11, 2025; 
                        <E T="03">see also</E>
                         Colakoglu's Letter, “Colakoglu's Rebuttal Case Brief,” dated September 11, 2025.
                    </P>
                </FTNT>
                <P>
                    Due to the lapse in appropriations and Federal Government shutdown, on November 14, 2025, Commerce tolled all deadlines in administrative proceedings by 47 days.
                    <SU>4</SU>
                    <FTREF/>
                     Additionally, due to a backlog of documents that were electronically filed via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS) during the Federal Government shutdown, on November 24, 2025, Commerce tolled all deadlines in administrative proceedings by an additional 21 days.
                    <SU>5</SU>
                    <FTREF/>
                     On February 10, 2026, Commerce extended the final results of this review by 15 days.
                    <SU>6</SU>
                    <FTREF/>
                     On March 2, 2026, Commerce extended the final results of this review by an additional 14 days.
                    <SU>7</SU>
                    <FTREF/>
                     Finally, on March 17, 2026, Commerce extended the final results until March 31, 2026.
                    <SU>8</SU>
                    <FTREF/>
                     Accordingly, the deadline for these final results is now March 31, 2026.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Deadlines Affected by the Shutdown of the Federal Government,” dated November 14, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Tolling of all Case Deadlines,” dated November 24, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Extension of Deadline for Final Results of 2023-2024 Antidumping Duty Administrative Review,” dated February 10, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Extension of Deadline for Final Results of 2023-2024 Antidumping Duty Administrative Review,” dated March 2, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Extension of Deadline for Final Results of 2023-2024 Antidumping Duty Administrative Review,” dated March 17, 2026.
                    </P>
                </FTNT>
                <P>
                    For a complete description of the events that occurred since the 
                    <E T="03">Preliminary Results, see</E>
                     the Issues and Decision Memorandum.
                    <SU>9</SU>
                    <FTREF/>
                     The Issues and Decision Memorandum is a public document and is on file electronically via ACCESS. ACCESS is available to registered users at 
                    <E T="03">https://access.trade.gov.</E>
                     In addition, a complete version of the Issues and Decision Memorandum can be accessed directly at 
                    <E T="03">https://access.trade.gov/public/FRNoticesListLayout.aspx.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Issues and Decision Memorandum for the Final Results of the Antidumping Duty Administrative Review of Steel Concrete Reinforcing Bar from the Republic of Türkiye; 2023-2024,” dated concurrently with, and hereby adopted by, this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <P>
                    Commerce conducted this administrative review in accordance with section 751 of the Tariff Act of 1930, as amended (the Act).
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Steel Concrete Reinforcing Bar from the Republic of Türkiye and Japan: Amended Final Affirmative Antidumping Duty Determination for the Republic of Türkiye and Antidumping Duty Orders,</E>
                         82 FR 32532 (July 14, 2017), as amended by 
                        <E T="03">Notice of Court Decision Not in Harmony with the Amended Final Determination in the Less-Than-Fair-Value Investigation; Notice of Amended Final Determination,</E>
                         87 FR 934 (January 22, 2022) (
                        <E T="03">Amended Final</E>
                        ) (collectively, 
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">
                    Scope of the Order 
                    <E T="51">10</E>
                </HD>
                <P>
                    The merchandise covered by the 
                    <E T="03">Order</E>
                     is steel concrete reinforcing bar from Türkiye. For a full description of the scope of the 
                    <E T="03">Order, see</E>
                     the Issues and Decision Memorandum.
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>All issues raised in the case and rebuttal briefs are listed in the appendix to this notice and addressed in the Issues and Decision Memorandum.</P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>
                    Based on a review of the record and comments received from interested parties regarding our 
                    <E T="03">Preliminary Results,</E>
                     we made no changes to the margin calculation for Colakoglu. For further discussion, 
                    <E T="03">see</E>
                     the Issues and Decision Memorandum.
                </P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>As a result of this review, we determine the following estimated weighted-average dumping margin exists for the period July 1, 2023, through June 30, 2024:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,9C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Producer or exporter</CHED>
                        <CHED H="1">
                            Weighted-
                            <LI>average</LI>
                            <LI>dumping</LI>
                            <LI>margin</LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Colakoglu Metalurji A.S.; Colakoglu Dis Ticaret A.S</ENT>
                        <ENT>18.87</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Disclosure</HD>
                <P>
                    Normally, Commerce will disclose to the parties in a proceeding the calculations performed in connection with the final results within five days of any public announcement or, if there is no public announcement, within five days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , in accordance with 19 CFR 351.224(b). However, because Commerce made no changes to the 
                    <E T="03">Preliminary Results</E>
                     calculations, there are no new calculations to disclose.
                </P>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>Pursuant to section 751(a)(2)(C) of the Act, and 19 CFR 351.212(b)(1), Commerce has determined, and U.S. Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries of subject merchandise in accordance with the final results of this review.</P>
                <P>
                    Pursuant to 19 CFR 351.212(b)(1), because Colakoglu reported the entered value for its U.S. sales, we calculated importer-specific 
                    <E T="03">ad valorem</E>
                     antidumping duty assessment rates based on the ratio of the total amount of antidumping duties calculated for the examined sales to the total entered value of those same sales. Where an importer-specific assessment rate is zero or 
                    <E T="03">de minimis,</E>
                     we will instruct CBP to 
                    <PRTPAGE P="17247"/>
                    liquidate the appropriate entries without regard to antidumping duties.
                </P>
                <P>
                    Commerce's “automatic assessment” practice will apply to entries of subject merchandise during the POR produced by Colakoglu for which it did not know that the merchandise it sold to an intermediary (
                    <E T="03">e.g.,</E>
                     a reseller, trading company, or exporter) was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the all-others rate (
                    <E T="03">i.e.,</E>
                     3.90 percent),
                    <SU>11</SU>
                    <FTREF/>
                     if there is no rate for the intermediate company(ies) involved in the transaction.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Amended Final,</E>
                         87 FR at 935.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties,</E>
                         68 FR 23954 (May 6, 2003).
                    </P>
                </FTNT>
                <P>
                    Commerce intends to issue assessment instructions to CBP no earlier than 35 days after the date of publication of the final results of this review in the 
                    <E T="04">Federal Register</E>
                    . If a timely summons is filed at the U.S. Court of International Trade, the assessment instructions will direct CBP not to liquidate relevant entries until the time for parties to file a request for a statutory injunction has expired (
                    <E T="03">i.e.,</E>
                     within 90 days of publication).
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following cash deposit requirements will be effective for all shipments of the subject merchandise entered, or withdrawn from warehouse, for consumption on or after the publication date of the final results of this administrative review, as provided by section 751(a)(2)(C) of the Act: (1) the cash deposit rate for Colakoglu will be equal to the weighted-average dumping margin that is established in the final results of this review; (2) for previously investigated or reviewed companies not covered in this review, the cash deposit rate will continue to be the company-specific rate published for the most recently completed segment of this proceeding in which the company participated; (3) if the exporter is not a firm covered in this review, or the less-than-fair-value (LTFV) investigation, but the manufacturer is, the cash deposit rate will be the cash deposit rate established for the most recently completed segment for the producer of the subject merchandise; and (4) the cash deposit rate for all other producers or exporters will continue to be 3.90 percent, the all-others rate established in the LTFV investigation.
                    <SU>13</SU>
                    <FTREF/>
                     These deposit requirements, when imposed, shall remain in effect until further notice.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Amended Final,</E>
                         87 FR at 935.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties and/or countervailing duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in Commerce's presumption that reimbursement of antidumping and/or countervailing duties occurred and the subsequent assessment of double antidumping duties, and/or increase in the amount of antidumping duties by the amount of the countervailing duties.</P>
                <HD SOURCE="HD1">Administrative Protective Order (APO)</HD>
                <P>This notice serves as the only reminder to parties subject to APO of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3), which continues to govern business proprietary information in this segment of the proceeding. Timely written notification of return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Act.</P>
                <SIG>
                    <DATED>Dated: March 30, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance. </TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Topics Discussed in the Issues and Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">
                        III. Scope of the 
                        <E T="03">Order</E>
                    </FP>
                    <FP SOURCE="FP-2">IV. Discussion of the Issues</FP>
                    <FP SOURCE="FP1-2">Comment 1: Differential Pricing Analysis</FP>
                    <FP SOURCE="FP1-2">Comment 2: Whether Commerce Should Include Reported Inward Processing Certificates (IPC) in Colakoglu's Duty Drawback Calculation</FP>
                    <FP SOURCE="FP1-2">Comment 3: Whether Commerce Used the Appropriate Date of Sale for Colakoglu's U.S. Sales</FP>
                    <FP SOURCE="FP1-2">Comment 4: Whether Commerce Should Recalculate Medtrade Incorporated's (Medtrade) Indirect Selling Expense (ISE) Ratio</FP>
                    <FP SOURCE="FP1-2">Comment 5: Whether Commerce Should Grant Colakoglu a Scrap Offset</FP>
                    <FP SOURCE="FP-2">V. Recommendation</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06559 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-886]</DEPDOC>
                <SUBJECT>Polyethylene Retail Carrier Bags From the People's Republic of China: Preliminary Results and Partial Rescission of Antidumping Administrative Review; 2024-2025</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) preliminarily determines that that Crown Polyethylene Products (International) Ltd. (Crown) is not eligible for a separate rate and is part of the China-wide entity. Further, Commerce is rescinding, in part, the administrative review of the antidumping duty order on polyethylene retail carrier bags from the People's Republic of China (China) for the period of review (POR) August 1, 2024, through July 31, 2025, with respect to Dongguan Nozawa Plastics Products Co., Ltd., and United Power Packaging, Ltd. (collectively Nozawa). Interested parties are invited to comment on these preliminary results.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable April 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Yang Jin Chun, AD/CVD Operations, Office I, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-5760.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 9, 2004, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the antidumping duty order on polyethylene retail carrier bags from China.
                    <SU>1</SU>
                    <FTREF/>
                     On August 1, 2025, Commerce published in the 
                    <E T="04">Federal Register</E>
                     a notice of opportunity to request an administrative review of the 
                    <E T="03">Order.</E>
                    <SU>2</SU>
                    <FTREF/>
                     On August 29, 2025, Hilex Poly Co., LLC and Superbag Corporation (collectively, the petitioners) submitted timely requests that Commerce conduct an administrative review of the 
                    <E T="03">Order</E>
                     with respect to Nozawa and Crown.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Antidumping Duty Order: Polyethylene Retail Carrier Bags from the People's Republic of China,</E>
                         69 FR 48201 (August 9, 2004) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation; Opportunity to Request Administrative Review and Join Annual Inquiry Service List,</E>
                         90 FR 36141 (August 1, 2025).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Petitioners Letter, “Request for Administrative Review,” dated August 29, 2025.
                    </P>
                </FTNT>
                <P>
                    On September 25, 2025, Commerce published in the 
                    <E T="04">Federal Register</E>
                     a notice of initiation of an administrative 
                    <PRTPAGE P="17248"/>
                    review with respect to imports of polyethylene retail carrier bags exported and/or produced by Nozawa and Crown in accordance with section 751(a) of the Tariff Act of 1930, as amended (the Act), and 19 CFR 351.221(c)(1)(i).
                    <SU>4</SU>
                    <FTREF/>
                     In the “Respondent Selection” section of the 
                    <E T="03">Initiation Notice,</E>
                     we indicated that, in the event that we limited the number of respondents selected for individual examination in accordance with section 777A(c)(2) of the Act, we intended to select respondents based on U.S. Customs and Border Protection (CBP) data.
                    <SU>5</SU>
                    <FTREF/>
                     Therefore, on September 25, 2025, we placed on the record CBP data for entries of subject merchandise from China during the POR, showing suspended entries during the POR and invited interested parties to comment.
                    <SU>6</SU>
                    <FTREF/>
                     No parties filed any comments by the deadline, October 2, 2025.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         90 FR 46173, 46181 (September 25, 2025) (
                        <E T="03">Initiation Notice</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                         at 46173.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Release of U.S. Customs and Border Protection Data Release,” dated September 25, 2025 (CBP Data Memorandum).
                    </P>
                </FTNT>
                <P>
                    Due to the lapse in appropriations and Federal Government shutdown, on November 14, 2025, Commerce tolled all deadlines in administrative proceedings by 47 days.
                    <SU>7</SU>
                    <FTREF/>
                     Additionally, due to a backlog of documents that were electronically filed via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS) during the Federal Government shutdown, on November 24, 2025, Commerce tolled all deadlines in administrative proceedings by an additional 21 days.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Deadlines Affected by the Shutdown of the Federal Government,” dated November 14, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Tolling of all Case Deadlines,” dated November 24, 2025.
                    </P>
                </FTNT>
                <P>
                    On December 11, 2025, Commerce notified interested parties of its intent to rescind this administrative review in part with respect to Nozawa because it had no reviewable, suspended entries.
                    <SU>9</SU>
                    <FTREF/>
                     No party submitted comments regarding out notice of intent to rescind the review with respect to Nozawa.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Notice of Intent to Rescind Review, in Part,” dated December 11, 2025.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The products covered by the 
                    <E T="03">Order</E>
                     are polyethylene retail carrier bags which may be referred to as t-shirt sacks, merchandise bags, grocery bags, or checkout bags. The full description of the scope of the 
                    <E T="03">Order</E>
                     is provided in the appendix to this notice.
                </P>
                <HD SOURCE="HD1">Rescission of Review, in Part</HD>
                <P>
                    Pursuant to 19 CFR 351.213(d)(3), it is Commerce's practice to rescind an administrative review of an antidumping duty order when there are no reviewable entries of subject merchandise during the POR for which liquidation is suspended.
                    <SU>10</SU>
                    <FTREF/>
                     Normally, upon completion of an administrative review, the suspended entries are liquidated at the antidumping duty assessment rate calculated for the review period.
                    <SU>11</SU>
                    <FTREF/>
                     Therefore, for an administrative review to be conducted, there must be a reviewable, suspended entry that Commerce can instruct CBP to liquidate at the antidumping duty assessment rate calculated for the review period.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g., Dioctyl Terephthalate from the Republic of Korea: Rescission of Antidumping Administrative Review; 2021-2022,</E>
                         88 FR 24758 (April 24, 2023); 
                        <E T="03">see also Certain Carbon and Alloy Steel Cut- to Length Plate from the Federal Republic of Germany: Recission of Antidumping Administrative Review; 2020-2021,</E>
                         88 FR 4157 (January 24, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.212(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.213(d)(3).
                    </P>
                </FTNT>
                <P>
                    The record indicates there were no entries of subject merchandise for Nozawa during the POR.
                    <SU>13</SU>
                    <FTREF/>
                     In particular, CBP data placed on the record at the outset of this administrative review indicate no entries of merchandise from this company.
                    <SU>14</SU>
                    <FTREF/>
                     Accordingly, in the absence of suspended entries of subject merchandise during the POR, we are hereby rescinding this administrative review with respect to this company in accordance with 19 CFR 351.213(d)(3).
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         CBP Data Memorandum.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">China-Wide Entity</HD>
                <P>
                    Because Crown did not file a separate rate application or certification in this administrative review, it is ineligible for a separate rate and we are unable to select it for individual examination.
                    <SU>15</SU>
                    <FTREF/>
                     Accordingly, Commerce finds that Crown, a company under review, has not established eligibility for a separate rate and is considered to be part of the China-wide entity for these preliminary results.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See Initiation Notice,</E>
                         90 FR at 46173.
                    </P>
                </FTNT>
                <P>
                    Commerce's policy regarding conditional review of the China-wide entity applies to this administrative review.
                    <SU>16</SU>
                    <FTREF/>
                     Under this policy, the China-wide entity will not be under review unless a party specifically requests, or Commerce self-initiates, a review of the entity. Because no party requested a review of the China-wide entity, the entity is not under review and the entity's rate of 77.57 percent is not subject to change.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See Antidumping Proceedings: Announcement of Change in Department Practice for Respondent Selection in Antidumping Duty Proceedings and Conditional Review of the Nonmarket Economy Entity in NME Antidumping Duty Proceedings,</E>
                         78 FR 65963 (November 4, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See Order,</E>
                         69 FR at 48203.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Disclosure</HD>
                <P>
                    Normally, Commerce will disclose the calculations used in its analysis to parties in an administrative review within five days of the date of publication of the notice of preliminary results in the 
                    <E T="04">Federal Register</E>
                    , in accordance with 19 CFR 351.224(b). However, here Commerce preliminarily found Crown ineligible for a separate rate and treated it part of the China-wide entity.
                    <SU>18</SU>
                    <FTREF/>
                     Thus, there are no calculations to disclose, and no decision memorandum accompanies this notice.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See, e.g., Polyethylene Retail Carrier Bags from the People's Republic of China: Final Results of Antidumping Duty Administrative Review,</E>
                         74 FR 6857 (February 11, 2009).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Public Comment</HD>
                <P>
                    Case briefs or other written comments may be submitted to the Assistant Secretary for Enforcement and Compliance. Pursuant to 19 CFR 351.309(c)(1)(ii), we have modified the deadline for interested parties to submit case briefs to Commerce to no later than 21 days after the date of the publication of this notice.
                    <SU>19</SU>
                    <FTREF/>
                     Rebuttal briefs, limited to issues raised in the case briefs, may be filed not later than five days after the date for filing case briefs.
                    <SU>20</SU>
                    <FTREF/>
                     Interested parties who submit case briefs or rebuttal briefs in this proceeding must submit: (1) a table of contents listing each issue; and, (2) a table of authorities.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.309.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.309(d); 
                        <E T="03">see also Administrative Protective Order, Service, and Other Procedures in Antidumping and Countervailing Duty Proceedings,</E>
                         88 FR 67069, 67077 (September 29, 2023) (
                        <E T="03">APO and Service Final Rule</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.309(c)(2) and (d)(2).
                    </P>
                </FTNT>
                <P>
                    As provided under 19 CFR 351.309(c)(2)(iii) and (d)(2)(iii), we request that interested parties provide at the beginning of their briefs a public executive summary for each issue raised in their briefs.
                    <SU>22</SU>
                    <FTREF/>
                     Further, we request that interested parties limit their public executive summary of each issue to no more than 450 words, not including citations. We intend to use the public executive summaries as the basis of the comment summaries included in the issues and decision memorandum that will accompany the final results in this administrative review. We request that 
                    <PRTPAGE P="17249"/>
                    interested parties include footnotes for relevant citations in the public executive summary of each issue.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         We use the term “issue” here to describe an argument that Commerce would normally address in a comment of the Issues and Decision Memorandum.
                    </P>
                </FTNT>
                <P>
                    Pursuant to 19 CFR 351.310(c), interested parties who wish to request a hearing must submit a written request to the Assistant Secretary for Enforcement and Compliance, filed electronically via ACCESS. Requests should contain: (1) the party's name, address, and telephone number; (2) the number of participants and whether any participant is a foreign national; and (3) a list of issues to be discussed. Issues raised in the hearing will be limited to those raised in the respective case briefs. An electronically filed hearing request must be received successfully in its entirety via ACCESS by 5:00 p.m. Eastern Time within 30 days after the date of publication of this notice. If a request for a hearing is made, parties will be notified of the date, time, and location of the hearing.
                    <SU>23</SU>
                    <FTREF/>
                     Parties should confirm the date, time, and location of the hearing two days before the scheduled hearing date.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.310(d).
                    </P>
                </FTNT>
                <P>
                    All submissions, including case and rebuttal briefs, as well as hearing requests, must be filed via ACCESS.
                    <SU>24</SU>
                    <FTREF/>
                     An electronically filed document must be received successfully in its entirety in ACCESS by 5:00 p.m. Eastern Time on the established deadline. Note that Commerce has amended certain of its requirements pertaining to the service of documents in 19 CFR 351.303(f).
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.303.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See APO and Service Final Rule.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    For the company for which this review is being rescinded Commerce will instruct CBP to assess antidumping duties on all appropriate entries. Antidumping duties shall be assessed at rates equal to the cash deposit rate for estimated antidumping duties required at the time of entry, or withdrawal from warehouse, for consumption, in accordance with 19 CFR 351.212(c)(1)(i). With respect to the recission of this review, in part, Commerce intends to issue assessment instructions to CBP no earlier than 35 days after the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    When Commerce determines that an exporter under review made no shipments of subject merchandise during the POR, upon issuing the final results, Commerce will instruct CBP to liquidate any suspended entries of subject merchandise that entered under that exporter's cash deposit requirement, 
                    <E T="03">i.e.,</E>
                     under the exporter's CBP case number, during the POR at the weighted-average dumping margin for the China-wide entity, 
                    <E T="03">i.e.,</E>
                     77.57 percent.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         For a full discussion of this practice, 
                        <E T="03">see Non-Market Economy Antidumping Proceedings: Assessment of Antidumping Duties,</E>
                         76 FR 65694 (October 24, 2011).
                    </P>
                </FTNT>
                <P>
                    With respect to Crown, Commerce intends to issue assessment instructions to CBP no earlier than 35 days after the date of publication of the final results of this review in the 
                    <E T="04">Federal Register</E>
                    . If a timely summons is filed at the U.S. Court of International Trade, the assessment instructions will direct CBP not to liquidate relevant entries until the time for parties to file a request for a statutory injunction has expired (
                    <E T="03">i.e.,</E>
                     within 90 days of publication).
                </P>
                <P>
                    For the final results, if we continue to treat Crown as part of the China-wide entity, we will instruct CBP to apply an 
                    <E T="03">ad valorem</E>
                     assessment rate of 77.57 percent to all entries of subject merchandise during the POR which were produced and/or exported by this company. The final results of this review shall be the basis for the assessment of antidumping duties on entries of merchandise covered by the final results of this review and for future deposits of estimated duties, where applicable.
                </P>
                <HD SOURCE="HD1">Cash Deposit Rates</HD>
                <P>The following cash deposit requirements will be effective upon publication of the final results of this administrative review for shipments of the subject merchandise from China entered, or withdrawn from warehouse, for consumption on or after the publication date, as provided by sections 751(a)(2)(C) of the Act: (1) for all Chinese exporters of subject merchandise that have not been found to be entitled to a separate rate, the cash deposit rate will be the existing rate for the China-wide entity of 77.57 percent.; and (2) for all non-China exporters of subject merchandise which have not received their own rate, the cash deposit rate will be the rate applicable to the China exporter that supplied that non-Chinese exporter. These cash deposit requirements, when imposed, shall remain in effect until further notice.</P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>
                    Unless otherwise extended, Commerce intends to issue the final results of this administrative review, including the results of its analysis of issues raised by the parties in the written comments, within 120 days of publication of these preliminary results in the 
                    <E T="04">Federal Register</E>
                    , no later than 120 days after the date of publication of this notice, unless otherwise extended.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         section 751(a)(3)(A) of the Act; and 19 CFR 351.213(h).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice also serves as a preliminary reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in Commerce's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Act, and 19 CFR 351.213(d)(4).</P>
                <SIG>
                    <DATED>Dated: March 30, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">Scope of the Order</HD>
                    <P>
                        The merchandise subject to this antidumping duty 
                        <E T="03">Order</E>
                         are polyethylene retail carrier bags (PRCBs), which also may be referred to as t-shirt sacks, merchandise bags, grocery bags, or checkout bags. The subject merchandise is defined as non-sealable sacks and bags with handles (including drawstrings), without zippers or integral extruded closures, with or without gussets, with or without printing, of polyethylene film having a thickness no greater than 0.035 inch (0.889 mm) and no less than 0.00035 inch (0.00889 mm), and with no length or width shorter than 6 inches (15.24 cm) or longer than 40 inches (101.6 cm). The depth of the bag may be shorter than 6 inches (15.24 cm) but not longer than 40 inches (101.6 cm).
                    </P>
                    <P>
                        PRCBs are typically provided without any consumer packaging and free of charge by retail establishments, 
                        <E T="03">e.g.,</E>
                         grocery, drug, convenience, department, specialty retail, discount stores, and restaurants to their customers to package and carry their purchased products. The scope of this antidumping duty 
                        <E T="03">Order</E>
                         excludes (1) PRCBs that are not printed with logos or store names and that are closeable with drawstrings made of polyethylene film and (2) PRCBs that are packed in consumer packaging with printing that refers to specific end-uses other than packaging and carrying merchandise from retail establishments, 
                        <E T="03">e.g.,</E>
                         garbage bags, lawn bags, trash-can liners.
                    </P>
                    <P>
                        Imports of merchandise included within the scope of this antidumping duty 
                        <E T="03">Order</E>
                         are currently classifiable under statistical 
                        <PRTPAGE P="17250"/>
                        category 3923.21.0085 of the Harmonized Tariff Schedule of the United States (HTSUS). This subheading may also cover products that are outside the scope of this antidumping duty 
                        <E T="03">Order.</E>
                         Although the HTSUS subheading is provided for convenience and customs purposes, the written description of the scope of this antidumping duty 
                        <E T="03">Order</E>
                         is dispositive.
                    </P>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06560 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-188]</DEPDOC>
                <SUBJECT>Float Glass Products From the People's Republic of China: Antidumping Duty Order</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Based on affirmative final determination by the U.S. Department of Commerce (Commerce) and the U.S. International Trade Commission (ITC), Commerce is issuing the antidumping duty (AD) order on float glass products from the People's Republic of China (China).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable April 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dmitry Vladimirov at (202) 482-0665, AD/CVD Operations, Office I, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On February 9, 2026, Commerce published its affirmative final determination in the investigation of sales at less than fair value (LTFV) of float glass products from China in accordance with sections 735(d) and 777(i) of the Tariff Act of 1930, as amended (the Act).
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Float Glass Products from the People's Republic of China: Final Affirmative Determination of Sales at Less Than Fair Value,</E>
                         91 FR 5713 (February 9, 2026).
                    </P>
                </FTNT>
                <P>
                    On March 26, 2026, pursuant to section 735(d) of the Act, the ITC notified Commerce of its final affirmative determination that an industry in the United States is materially injured within the meaning of section 735(b)(1)(A)(i) of the Act by reason of dumped imports of float glass products from China.
                    <SU>2</SU>
                    <FTREF/>
                     On March 31, 2026, the ITC published its final determination in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         ITC's Letter, “ITC Notification,” dated March 26, 2026. The ITC also determined that imports of float glass products from Malaysia found by Commerce to be sold in the United States at LTFV are negligible and terminated the antidumping duty investigation concerning Malaysia. 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Float Glass Products from China and Malaysia; Determinations,</E>
                         91 FR 16014 (March 31, 2026) (
                        <E T="03">ITC Final Determination</E>
                        ).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The products covered by this order are float glass products from China. For a complete description of the scope of the order, 
                    <E T="03">see</E>
                     the appendix to this notice.
                </P>
                <HD SOURCE="HD1">AD Order</HD>
                <P>Based on the above-referenced affirmative final determination by the ITC, in accordance with sections 735(c)(2) and 736 of the Act, Commerce is issuing this AD order. Because the ITC determined that an industry in the United States is materially injured by reason of imports of float glass products from China, unliquidated entries of such merchandise from China, entered or withdrawn from warehouse for consumption, are subject to the assessment of antidumping duties.</P>
                <P>
                    Therefore, in accordance with section 736(a)(1) of the Act, Commerce will direct U.S. Customs and Border Protection (CBP) to assess, upon further instruction by Commerce, antidumping duties equal to the amount by which the normal value of the merchandise exceeds the export price (or constructed export price) of the merchandise on all relevant entries of float glass products from China. Antidumping duties will be assessed on unliquidated entries of float glass products from China entered, or withdrawn from warehouse, for consumption on or after July 15, 2025, the date of publication of the 
                    <E T="03">Preliminary Determination,</E>
                    <SU>4</SU>
                    <FTREF/>
                     but will not include entries occurring after the expiration of the provisional measures period and before publication of the ITC's final injury determination, as further described below.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Float Glass Products from the People's Republic of China: Preliminary Affirmative Determination of Sales at Less Than Fair Value, Postponement of Final Determination, and Extension of Provisional Measures,</E>
                         90 FR 31602 (July 15, 2025) (
                        <E T="03">Preliminary Determination</E>
                        ).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Suspension of Liquidation and Cash Deposits</HD>
                <P>
                    In accordance with section 736 of the Act, Commerce intends to instruct CBP to reinstitute the suspension of liquidation and continue the suspension of liquidation, as applicable, on all relevant entries of float glass products from China, effective on the date of publication of the ITC's final affirmative injury determination in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    Commerce also intends to instruct CBP to require cash deposits equal to the estimated weighted-average dumping margins indicated in the tables below, adjusted by the relevant subsidy offsets. Accordingly, effective on the date of publication in the 
                    <E T="04">Federal Register</E>
                     of the notice of the ITC's final affirmative injury determination, CBP will require, at the same time as importers would normally deposit estimated customs duties on subject merchandise, a cash deposit equal to the rates listed in the tables below. The rate for the China-wide entity applies to all producers or exporters not specifically listed, as appropriate.
                </P>
                <HD SOURCE="HD1">Estimated Weighted-Average Dumping Margins</HD>
                <P>
                    The estimated weighted-average dumping margins are as follows:
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Float Glass Products from the People's Republic of China: Preliminary Affirmative Countervailing Duty Determination and Alignment of Final Determination With Final Antidumping Duty Determination,</E>
                         90 FR 21281 (May 19, 2025), and accompanying Preliminary Decision Memorandum at 40-41, for the total of 0.02 percent for export subsidies, unchanged in 
                        <E T="03">Float Glass Products from The People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>
                         91 FR 5708 (February 9, 2026).
                    </P>
                </FTNT>
                <GPOTABLE COLS="4" OPTS="L2,nj,tp0,i1" CDEF="s50,r50,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter</CHED>
                        <CHED H="1">Producer</CHED>
                        <CHED H="1">
                            Weighted-
                            <LI>average</LI>
                            <LI>dumping</LI>
                            <LI>margin</LI>
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="1">
                            Cash deposit
                            <LI>rate</LI>
                            <LI>(adjusted for</LI>
                            <LI>subsidy</LI>
                            <LI>offsets)</LI>
                            <LI>
                                (percent) 
                                <SU>5</SU>
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Benxi Fuyao Float Glass Co., Ltd</ENT>
                        <ENT>Benxi Fuyao Float Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Changshu Chenming High-Tech International Trading Co., Ltd</ENT>
                        <ENT>Changshu High-Tech Energy-Saving Dorwin Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dong Guan City Bathnology Industrial Co., Ltd</ENT>
                        <ENT>Dong Guan City Bathnology Industrial Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="17251"/>
                        <ENT I="01">Dongguan Gongying Supply Chain Management Co., Ltd</ENT>
                        <ENT>Lamxon Technology Building Materials Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Guangdong Guang Yi Import and Export Co., Ltd</ENT>
                        <ENT>Lamxon Technology Building Materials Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Guangdong Rosery Bath Science and Technology Co., Ltd</ENT>
                        <ENT>Guangdong Rosery Bath Science and Technology Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Orient Resource Corporation Limited</ENT>
                        <ENT>Orient Resource Corporation Limited</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Qingdao Apis Glass Industries Co., Ltd</ENT>
                        <ENT>Qingdao Apis Glass Industries Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Qingdao Oriental Brother New Energy Technology Co., Ltd</ENT>
                        <ENT>Qingdao Oriental Brother New Energy Technology Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Qinhuangdao Xinhua Glass Processing Co., Ltd</ENT>
                        <ENT>Qinhuangdao Xinhua Glass Processing Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shandong Jinjing Science and Technology Stock Co., Ltd. Boshan Branch</ENT>
                        <ENT>Shandong Jinjing Science and Technology Stock Co., Ltd. Boshan Branch</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Eternal Glass Co., Ltd</ENT>
                        <ENT>Tengzhou Fenghua Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Haolong Glass Co., Ltd</ENT>
                        <ENT>Tengzhou Haolong Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Jingcheng Mirror Co., Ltd</ENT>
                        <ENT>Tengzhou Jingcheng Mirror Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Jinjing Glass Co., Ltd</ENT>
                        <ENT>Tengzhou Jinjing Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Jinjing Glass Co., Ltd</ENT>
                        <ENT>Langfang Jinbiao Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tengzhou Yichuang Commercial Trading Co., Ltd</ENT>
                        <ENT>Tengzhou Yichuang Commercial Trading Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Xiamen Guorui Hengsheng Advanced Materials Co., Ltd</ENT>
                        <ENT>Xiamen Guorui Hengsheng Advanced Materials Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Xiamen Guorui Hengsheng Advanced Materials Co., Ltd</ENT>
                        <ENT>Xiamen Shiner Glass Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Xinyi Group (Glass) Co., Ltd</ENT>
                        <ENT>Xinyi Glass (Tianjin) Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Xinyi Group (Glass) Co., Ltd</ENT>
                        <ENT>Xinyi Glass (Wuhu) Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Zhongshan Neptum Sanitary Ware Co., Ltd</ENT>
                        <ENT>Zhongshan Neptum Sanitary Ware Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW RUL="s,s,n,n">
                        <ENT I="01">Zhongshan Ninghe Intelligent Kitchen and Bath Co., Ltd</ENT>
                        <ENT>Zhongshan Ninghe Intelligent Kitchen and Bath Co., Ltd</ENT>
                        <ENT>151.29</ENT>
                        <ENT>151.27</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="03">China-Wide Entity</ENT>
                        <ENT>* 181.54</ENT>
                        <ENT>181.52</ENT>
                    </ROW>
                    <TNOTE>* Rate based on facts available with adverse inferences.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Provisional Measures</HD>
                <P>
                    Section 733(d) of the Act states that suspension of liquidation pursuant to an affirmative preliminary determination may not remain in effect for more than four months, except where exporters representing a significant proportion of exports of the subject merchandise request that Commerce extend the four-month period to no more than six months. At the request of exporters that account for a significant proportion of float glass products from China, Commerce extended the four-month period to six months.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Preliminary Determination.</E>
                    </P>
                </FTNT>
                <P>
                    In the underlying investigation, Commerce published the 
                    <E T="03">Preliminary Determination</E>
                     on July 15, 2025. The six-month period beginning on the date of the publication of the 
                    <E T="03">Preliminary Determination</E>
                     ended on January 10, 2026. Therefore, in accordance with section 733(d) of the Act and its practice, Commerce instructed CBP to terminate the suspension of liquidation and to liquidate, without regard to antidumping duties, unliquidated entries of float glass products from China entered, or withdrawn from warehouse, for consumption on or after January 11, 2026, the first day provisional measures were no longer in effect, until and through the day preceding the date of publication of the ITC's final injury determination in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>7</SU>
                    <FTREF/>
                     Suspension of liquidation and the collection of cash deposits will resume on the date of publication of the ITC's final determination in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         CBP Message 6014409, “Discontinuation of suspension of liquidation in the antidumping duty investigation of float glass products from the People's Republic of China (A-570-188),” dated January 14, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See ITC Final Determination.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Establishment of the Annual Inquiry Service Lists</HD>
                <P>
                    On September 20, 2021, Commerce published the 
                    <E T="03">Final Rule</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>9</SU>
                    <FTREF/>
                     On September 27, 2021, Commerce also published the 
                    <E T="03">Procedural Guidance</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>10</SU>
                    <FTREF/>
                     The 
                    <E T="03">Final Rule</E>
                     and 
                    <E T="03">Procedural Guidance</E>
                     provide that Commerce will maintain an annual inquiry service list for each order or suspended investigation, and any interested party submitting a scope ruling application or request for circumvention inquiry shall serve a copy of the application or request on the persons on the annual inquiry service list for that order, as well as any companion order covering the same merchandise from the same country of origin.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Regulations to Improve Administration and Enforcement of Antidumping and Countervailing Duty Laws,</E>
                         86 FR 52300 (September 20, 2021) (
                        <E T="03">Final Rule</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Scope Ruling Application; Annual Inquiry Service List; and Informational Sessions,</E>
                         86 FR 53205 (September 27, 2021) (
                        <E T="03">Procedural Guidance</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    In accordance with the 
                    <E T="03">Procedural Guidance,</E>
                     for orders published in the 
                    <E T="04">Federal Register</E>
                     after November 4, 2021, Commerce will create an annual inquiry service list segment in Commerce's online e-filing and document management system, Antidumping and Countervailing Duty Electronic Service System (ACCESS), available at 
                    <E T="03">https://access.trade.gov,</E>
                     within five business days of publication of the notice of the order. Each annual inquiry service list will be saved in ACCESS, under each case number, and under a specific segment type called “AISL—Annual Inquiry Service List.” 
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         This segment will be combined with the ACCESS Segment Specific Information (SSI) field which will display the month in which the notice of the order or suspended investigation was published in the 
                        <E T="04">Federal Register</E>
                        , also known as the anniversary month. For example, for an order 
                        <PRTPAGE/>
                        under case number A-000-000 that was published in the 
                        <E T="04">Federal Register</E>
                         in January, the relevant segment and SSI combination will appear in ACCESS as “AISL—January Anniversary.” Note that there will be only one annual inquiry service list segment per case number, and the anniversary month will be pre-populated in ACCESS.
                    </P>
                </FTNT>
                <PRTPAGE P="17252"/>
                <P>
                    Interested parties who wish to be added to the annual inquiry service list for an order must submit an entry of appearance to the annual inquiry service list segment for the order in ACCESS within 30 days after the date of publication of the order. For ease of administration, Commerce requests that law firms with more than one attorney representing interested parties in an order designate a lead attorney to be included on the annual inquiry service list. Commerce will finalize the annual inquiry service list within five business days thereafter. As mentioned in the 
                    <E T="03">Procedural Guidance,</E>
                    <SU>12</SU>
                    <FTREF/>
                     the new annual inquiry service list will be in place until the following year, when the 
                    <E T="03">Opportunity Notice</E>
                     for the anniversary month of the order is published.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See Procedural Guidance,</E>
                         86 FR at 53206.
                    </P>
                </FTNT>
                <P>
                    Commerce may update an annual inquiry service list at any time as needed based on interested parties' amendments to their entries of appearance to remove or otherwise modify their list of members and representatives, or to update contact information. Any changes or announcements pertaining to these procedures will be posted to the ACCESS website at 
                    <E T="03">https://access.trade.gov.</E>
                </P>
                <HD SOURCE="HD1">Special Instructions for the Petitioner and Foreign Governments</HD>
                <P>
                    In the 
                    <E T="03">Final Rule,</E>
                     Commerce stated that, “after an initial request and placement on the annual inquiry service list, both petitioners and foreign governments will automatically be placed on the annual inquiry service list in the years that follow.” 
                    <SU>13</SU>
                    <FTREF/>
                     Accordingly, as stated above, the petitioner and foreign governments should submit their initial entries of appearance after publication of this notice in order to appear in the first annual inquiry service lists for this order. Pursuant to 19 CFR 351.225(n)(3), the petitioner and foreign governments will not need to resubmit their entries of appearance each year to continue to be included on the annual inquiry service list. However, the petitioner and foreign governments are responsible for making amendments to their entries of appearance during the annual update to the annual inquiry service list in accordance with the procedures described above.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Final Rule,</E>
                         86 FR at 52335.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>
                    This notice constitutes the AD order with respect to float glass products from China, pursuant to section 736(a) of the Act. Interested parties can find a list of AD and countervailing duty orders currently in effect at 
                    <E T="03">https://enforcement.trade.gov/stats/iastats1.html.</E>
                </P>
                <P>This AD order is published in accordance with section 736(a) of the Act and 19 CFR 351.211(b).</P>
                <SIG>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">Scope of the Order</HD>
                    <P>The scope of this order covers float glass products, which are articles of soda-lime-silica glass that are manufactured by floating a continuous strip of molten glass over a smooth bath of tin (or another liquid metal with a density greater than molten glass), cooling the glass in an annealing lehr, and cutting it to appropriate dimensions. For purposes of the order, float glass products have an actual thickness of at least 2.0 mm (0.0787 inches) and an actual surface area of at least 0.37 square meters (4.0 square feet).</P>
                    <P>The country of origin of each float glass product is determined by the location where the soda-lime-silica glass is first manufactured by floating a continuous strip of molten glass over a smooth bath of tin and cooling the glass in an annealing lehr, regardless of the location of any downstream finishing or fabrication operations.</P>
                    <P>Prior to being subjected to further treatment, finishing, or fabrication, float glass products meet the requirements of Type I under ASTM-C1036 of the American Society for Testing and Materials (ASTM).</P>
                    <P>
                        Float glass products may be clear, stained, tinted, or coated with one or more materials. Examples of coated float glass products include Low-E architectural glass (
                        <E T="03">i.e.,</E>
                         glass with a low emissivity coating to limit the penetration of radiant heat energy) and frameless mirrors (
                        <E T="03">i.e.,</E>
                         flat glass with a silver, aluminum, or other reflective layer) such as mirror stock sheet.
                    </P>
                    <P>Float glass products may be annealed, chemically strengthened, heat strengthened, or tempered to achieve a desired surface compression, pursuant to ASTM-C1048, ASTM-C1422/C1422M, or other similar specifications.</P>
                    <P>
                        Float glass products include tub and shower enclosures (
                        <E T="03">i.e.,</E>
                         doors and panels) made of tempered glass, which may be sold with attached or unattached hardware. In such cases, the scope covers only the tempered glass, to the exclusion of any non-glass hardware.
                    </P>
                    <P>
                        The only float glass product assemblies included within the scope are: (1) articles consisting of two of more sheets of float glass that are bonded together using a polymer interlayer (
                        <E T="03">i.e.,</E>
                         laminated glass); (2) insulating glass units (IGUs), which consist of two or more sheets of float glass separated by a spacer material and hermetically sealed together at the edge in order to create a thermal barrier using air or one or more gases but excluding any non-float glass components (other than the spacer and insulating materials) that may be mounted within the space between sheets of float glass (
                        <E T="03">e.g.,</E>
                         blinds, wrought iron cores, and camed patterned glass), as such non-float glass components are deemed outside the scope and not subject to duties; and (3) LED mirrors (
                        <E T="03">i.e.,</E>
                         float glass mirrors with one or more light-emitting diodes attached to or integrated with the mirror, as well as framed float glass mirrors with one or more light-emitting diodes attached to or integrated with the mirror or the mirror frame, but without other electronic functionality such as digital or video displays or audio circuitry).
                    </P>
                    <P>Float glass products covered by the scope may meet one or more of the ASTM-C162, ASTM-C1036, ASTM-C1048, ASTM-C1172, ASTM-C1349, ASTM-C1376, ASTM-C1422/C1422M, ASTM-C1464, ASTM-C1503, ASTM-C1651, ASTM-E1300, and ASTM-E2190 specifications, definitions, and/or standards.</P>
                    <P>
                        Float glass products may be further worked, including, but not limited to, operations such as: cutting; beveling; edging; notching; drilling; etching; bending; curving; chipping; embossing; engraving; surface grinding; or polishing; and sandblasting (
                        <E T="03">i.e.,</E>
                         using high velocity air to stream abrasive particles and thereby impart a frosted aesthetic to the glass surface). A float glass product which undergoes further work remains within the scope so long as the soda-lime-silica glass originally satisfied the requirements of ASTM-C1036 Type I and was first manufactured in a subject country, regardless of where it is further worked.
                    </P>
                    <P>
                        Excluded from the scope are: (1) wired glass (
                        <E T="03">i.e.,</E>
                         glass with a layer of wire mesh embedded within); (2) patterned flat glass (
                        <E T="03">i.e.,</E>
                         rolled glass with a pattern impressed on one or both sides) meeting the requirements of Type II under ASTM-C1036, including greenhouse glass and patterned solar glass (
                        <E T="03">i.e.,</E>
                         photovoltaic glass with a textured surface); (3) safety glazing materials for vehicles certified to American National Standards Institute (ANSI) Standard Z26.1; (4) vacuum insulating glass (VIG) units, which consist of two or more sheets of float glass separated by a spacer material, with at least one hermetically sealed compartment that uses a gas-free vacuum as a thermal barrier; (5) framed mirrors without any LEDs integrated with the mirror or the mirror frame; (6) unframed “over-the-door” mirrors that are ready for use as imported without undergoing after importation any processing, finishing, or fabrication; and (7) heat-strengthened washing machine lid glass with an actual surface area less than 6.0 square feet (0.56 square meters).
                    </P>
                    <P>
                        Also excluded from the scope of the order are: (1) soda-lime-silica glass containing less than 0.01 percent iron oxide by weight, annealed with a surface compression less 
                        <PRTPAGE P="17253"/>
                        than 3,500 pounds per square inch (PSI), having a transparent conductive oxide base coating (
                        <E T="03">e.g.,</E>
                         tin oxide), and with an actual thickness less than or equal to 4.0 mm (0.1575 inches) (
                        <E T="03">i.e.,</E>
                         “coated solar glass”); and (2) heat treated soda-lime-silica glass with a surface compression between 3,500 and 10,000 PSI, containing two or more drilled holes, and having an actual thickness less than 2.5 mm (0.0984 inches) (
                        <E T="03">i.e.,</E>
                         “clear back solar glass”). Solar glass products (also known as photovoltaic glass) are designed to facilitate the conversion of solar energy into electricity.
                    </P>
                    <P>
                        Also excluded are metal-camed glass products (
                        <E T="03">i.e.,</E>
                         panels of glass joined together with metal banding) where the constituent glass panels would otherwise be excluded by reason of their size (
                        <E T="03">e.g.,</E>
                         an actual surface area less than 0.37 square meters, or 4.0 square feet) and/or by reason of consisting of patterned flat glass (
                        <E T="03">i.e.,</E>
                         rolled glass with a pattern impressed on one or both sides) meeting the requirements of Type II under ASTM-C1036.
                    </P>
                    <P>
                        Also excluded from the scope of the order are any products already covered by the scope of any extant antidumping and/or countervailing duty orders, including 
                        <E T="03">Aluminum Extrusions from the People's Republic of China: Antidumping Duty Order,</E>
                         76 FR 30650 (May 26, 2011), and 
                        <E T="03">Aluminum Extrusions from the People's Republic of China: Countervailing Duty Order,</E>
                         76 FR 30653 (May 26, 2011).
                    </P>
                    <P>The products subject to the order are currently classifiable under subheadings 7005.10.8000, 7005.21.1010, 7005.21.1030, 7005.21.2000, 7005.29.1810, 7005.29.1850, 7005.29.2500, 7007.29.0000, 7008.00.0000, 7009.91.5010, 7009.91.5095, and 7009.92.5010 of the Harmonized Tariff Schedule of the United States (HTSUS). Products subject to the order may also enter under HTSUS subheadings 7006.00.4010, 7006.00.4050, 7007.19.0000, 7013.99.2000, 7013.99.9090, 7610.10.0030, and 7610.90.0080. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the scope of the order is dispositive.</P>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06647 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[C-533-907]</DEPDOC>
                <SUBJECT>Sodium Nitrite From India: Final Results of Countervailing Duty Administrative Review; 2022-2023; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Department of Commerce (Commerce) published notice in the 
                        <E T="04">Federal Register</E>
                         of February 24, 2026, for the final results of the 2022-2023 countervailing duty administrative review of sodium nitrite from India. This notice corrects the inadventent omission of the final partial rescission of this review.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Joshua Jacobson, AD/CVD Operations, Office IV, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-0266.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On February 24, 2026, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the final results of the 2022-2023 countervailing duty administrative review of sodium nitrite from India.
                    <SU>1</SU>
                    <FTREF/>
                     In this notice, we inadvertently omitted the partial rescission of this review with respect to three companies.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Sodium Nitrite from India: Final Results of Countervailing Duty Administrative Review; 2022-2023,</E>
                         91 FR 8826 (February 24, 2026).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 24, 2026, in FR Doc 2026-03611, on page 8826, in the first column, correct the title of the notice to read “Sodium Nitrite from India: Final Results and Partial Rescission of Countervailing Duty Administrative Review; 2022-2023.”
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 24, 2026, in FR Doc 2026-03611, on page 8826, in the first column, correct the “Summary” section by adding the following language: “In addition, Commerce is rescinding this review, in part, with respect to Kutch Chemical Industries, Palvi Industries Limited, and Lotus Global Pvt. Ltd.”
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 24, 2026, in FR Doc 2026-03611, on page 8826, in the third column, correct the omission of the “Rescission” section by adding the following section below the “Scope of the Order” section:
                </P>
                <HD SOURCE="HD1">Rescission of Administrative Review, in Part</HD>
                <P>
                    As noted in the 
                    <E T="03">Preliminary Results,</E>
                     based on our analysis of U.S. Customs and Border Protection (CBP) data, we determined that Kutch Chemical Industries, Palvi Industries Limited, and Lotus Global Pvt. Ltd. had no reviewable entries of subject merchandise during the period of review (POR).
                    <SU>2</SU>
                    <FTREF/>
                     We received no comments or additional information from interested parties regarding these companies. Therefore, absent evidence of suspended entries of subject merchandise during the POR, we are rescinding the administrative review of the above companies, pursuant to 19 CFR 351.213(d)(3).
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Sodium Nitrite from India: Preliminary Results and Intent To Rescind, in Part, of Countervailing Duty Administrative Review; 2022-23,</E>
                         90 FR 24577 (June 11, 2025).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Tariff Act of 1930, as amended, and 19 CFR 351.213(d)(4) and 351.221(b)(5).</P>
                <SIG>
                    <DATED>Dated: March 30, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06561 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[C-570-189, C-557-833]</DEPDOC>
                <SUBJECT>Float Glass Products From the People's Republic of China and Malaysia: Countervailing Duty Orders</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Based on affirmative final determinations by the U.S. Department of Commerce (Commerce) and U.S. International Trade Commission (ITC), Commerce is issuing countervailing duty (CVD) orders on float glass products (float glass) from the People's Republic of China (China) and Malaysia.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable April 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nathan James at (202) 482-5305 and Kelsie Hohenberger at (202) 482-2517 (China), and Benjamin Nathan at (202) 482-3834 and Mira Warrier (202) 482-8031 (Malaysia), AD/CVD Operations, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    In accordance with sections 705(d) and 777(i) of the Tariff Act of 1930, as amended (the Act) on February 9, 2026, Commerce published in the 
                    <E T="04">Federal Register</E>
                     its affirmative final determinations in the countervailing duty investigations of float glass from 
                    <PRTPAGE P="17254"/>
                    China and Malaysia.
                    <SU>1</SU>
                    <FTREF/>
                     On March 26, 2026, the ITC notified Commerce of its final affirmative determinations, pursuant to sections 705(b)(1)(A)(i) and 705(d) of the Act, that an industry in the United States is materially injured by reason of subsidized imports of float glass from China and Malaysia.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Float Glass Products from the People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>
                         91 FR 5708 (February 9, 2026) (
                        <E T="03">China Final Determination</E>
                        ); 
                        <E T="03">see also Float Glass Products from Malaysia: Final Affirmative Countervailing Duty Determination,</E>
                         91 FR 5720 (February 9, 2026) (
                        <E T="03">Malaysia Final Determination</E>
                        ); and 
                        <E T="03">Float Glass Products from Malaysia: Final Affirmative Countervailing Duty Determination; Correction,</E>
                         91 FR 9239 (February 25, 2026).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         ITC's Letter, “Notification of ITC Final Determinations,” dated March 26, 2026 (ITC Notification Letter).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Orders</HD>
                <P>
                    The product covered by these orders is float glass from China and Malaysia. For a full description of the scope of these orders, 
                    <E T="03">see</E>
                     the appendix to this notice.
                </P>
                <HD SOURCE="HD1">Countervailing Duty Orders</HD>
                <P>
                    Based on the above-referenced affirmative final determinations by the ITC that an industry in the United States is materially injured by reason of subsidized imports of float glass from China and Malaysia,
                    <SU>3</SU>
                    <FTREF/>
                     in accordance with section 705(c)(2) and 706 of the Act, Commerce is issuing these CVD orders. Because the ITC determined that imports of float glass from China and Malaysia are materially injuring a U.S. industry, unliquidated entries of such merchandise entered, or withdrawn from warehouse, for consumption, are subject to the assessment of countervailing duties.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Therefore, in accordance with section 706(a) of the Act, Commerce will direct U.S. Customs and Border Protection (CBP) to assess, upon further instruction by Commerce, countervailing duties on unliquidated entries of float glass from China and Malaysia. With the exception of entries occurring after the expiration of the provisional measures period and before the publication of the ITC's final affirmative injury determinations, as further described below, countervailing duties will be assessed on unliquidated entries of float glass from China and Malaysia entered, or withdrawn from warehouse, for consumption on or after May 19, 2025, the date of publication of the 
                    <E T="03">Preliminary Determinations</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Float Glass Products from the People's Republic of China: Preliminary Affirmative Countervailing Duty Determination and Alignment of Final Determination with Final Antidumping Duty Determination,</E>
                         90 FR 21281 (May 19, 2025), and accompanying Preliminary Decision Memorandum (PDM); and 
                        <E T="03">Float Glass Products from Malaysia: Preliminary Affirmative Countervailing Duty Determination and Alignment of Final Determination with Final Antidumping Duty Determination,</E>
                         90 FR 21278 (May 19, 2025), and accompanying PDM (collectively, 
                        <E T="03">Preliminary Determinations</E>
                        ).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Suspension of Liquidation and Cash Deposits</HD>
                <P>
                    In accordance with section 706 of the Act, Commerce will direct CBP to reinstitute the suspension of liquidation of float glass from China and Malaysia, effective the date of publication of the ITC's notice of final determinations in the 
                    <E T="04">Federal Register</E>
                    , and to assess, upon further instruction by Commerce pursuant to section 706(a)(1) of the Act, countervailing duties for each entry of the subject merchandise in an amount based on the net countervailable subsidy rates for the subject merchandise. On or after the date of publication of the ITC's final injury determinations in the 
                    <E T="04">Federal Register</E>
                    , CBP must require, at the same time as importers would normally deposit estimated duties on this merchandise, a cash deposit equal to the rates noted below. These instructions suspending liquidation will remain in effect until further notice.
                </P>
                <HD SOURCE="HD1">Estimated Countervailable Subsidy Rates</HD>
                <P>
                    The estimated countervailable subsidy rates are as follows; the all-others rate applies to all producers or exporters not specifically listed below:
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Commerce has found the following companies to be cross-owned with Xinyi Group (Glass) Company Limited: (1) Xinyi Special Glass (Jiangmen) Company Limited; (2) Xinyi Glass (Chongqing) Company Limited; (3) Xinyi Glass (Guangxi) Company Limited; (4) Xinyi Ultrathin Glass (Dongguan) Co., Ltd; (5) Xinyi Electronic Glass (Wuhu) Co., Ltd.; (6) Xinyi Glass (Hainan) Co., Ltd.; (7) Xinyi Glass (Yingkou) Co., Ltd.; (8) Xinyi Energy Smart (Sichuan) Co., Ltd; (9) Xinyi Glass (Wuhu) Company Limited; (10) Xinyi Glass (Tianjin) Co., Ltd.; (11) Xinyi Glass (Jiangsu) Co., Ltd.; (12) Xinyi Glass Engineering (Dongguan) Co., Ltd; and (13) Xinyi Glass (Bozhou) Co., Ltd. 
                        <E T="03">See China Final Determination,</E>
                         91 FR at 5709, n.15.
                    </P>
                    <P>
                        <SU>6</SU>
                         Commerce has found the following company to be cross-owned with Jinjing Technology Malaysia Sdn. Bhd: Jinjing Silicon Technology Sdn. Bhd. 
                        <E T="03">See Malaysia Final Determination,</E>
                         91 FR at 5721, n.12.
                    </P>
                    <P>
                        <SU>7</SU>
                         Commerce has found the following company to be cross-owned with Xinyi Energy Smart (M) Sdn. Bhd: Xin Yun Logistics (Malaysia) Sdn. Bhd. 
                        <E T="03">See Malaysia Final Determination,</E>
                         91 FR at 5721, n.13.
                    </P>
                </FTNT>
                <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s200,20">
                    <TTITLE>China</TTITLE>
                    <BOXHD>
                        <CHED H="1">Company</CHED>
                        <CHED H="1">
                            Subsidy rate
                            <LI>
                                (percent 
                                <E T="03">ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Xinyi Group (Glass) Company Limited 
                            <SU>5</SU>
                        </ENT>
                        <ENT>19.75</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shandong Jinjing Science and Technology Stock Co., Ltd</ENT>
                        <ENT>* 113.34</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hubei Sanxia New Building Materials Co., Ltd</ENT>
                        <ENT>* 113.34</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shanghai Yaohua Pilkington Glass Group Co., Ltd. (SYP)</ENT>
                        <ENT>* 113.34</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>19.75</ENT>
                    </ROW>
                    <TNOTE>* This rate is based on facts available with adverse inferences.</TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s200,20">
                    <TTITLE>Malaysia</TTITLE>
                    <BOXHD>
                        <CHED H="1">Company</CHED>
                        <CHED H="1">
                            Subsidy rate
                            <LI>
                                (percent 
                                <E T="03">ad valorem</E>
                                )
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Jinjing Technology Malaysia Sdn. Bhd 
                            <SU>6</SU>
                        </ENT>
                        <ENT>17.25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Xinyi Energy Smart (M) Sdn. Bhd 
                            <SU>7</SU>
                        </ENT>
                        <ENT>28.45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NSG (Malaysian Sheet Glass)</ENT>
                        <ENT>* 101.99</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>27.32</ENT>
                    </ROW>
                    <TNOTE>* This rate is based on facts available with adverse inferences.</TNOTE>
                </GPOTABLE>
                <PRTPAGE P="17255"/>
                <HD SOURCE="HD1">Provisional Measures</HD>
                <P>
                    Section 703(d) of the Act states that the suspension of liquidation pursuant to an affirmative preliminary determination may not remain in effect for more than four months. In the underlying investigations, Commerce published the 
                    <E T="03">Preliminary Determinations</E>
                     on May 19, 2025.
                    <SU>8</SU>
                    <FTREF/>
                     Therefore, entries of float glass from China and Malaysia made on or after September 16, 2025, and prior to the date of publication of the ITC's final determinations in the 
                    <E T="04">Federal Register</E>
                    , are not subject to the assessment of countervailing duties due to Commerce's discontinuation of the suspension of liquidation.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Preliminary Determinations.</E>
                    </P>
                </FTNT>
                <P>
                    In accordance with section 703(d) of the Act, Commerce instructed CBP to terminate the suspension of liquidation and to liquidate, without regard to countervailing duties, certain unliquidated entries of float glass from China and Malaysia entered, or withdrawn from warehouse, for consumption on or after September 16, 2025, the date on which the provisional CVD measures expired, until and through the day preceding the date of publication of the ITC's final injury determinations in the 
                    <E T="04">Federal Register</E>
                    . Suspension of liquidation and the collection of cash deposits will resume on the date of publication of the ITC final injury determinations in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Establishment of the Annual Inquiry Service List</HD>
                <P>
                    On September 20, 2021, Commerce published the 
                    <E T="03">Final Rule</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>9</SU>
                    <FTREF/>
                     On September 27, 2021, Commerce also published the 
                    <E T="03">Procedural Guidance</E>
                     in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>10</SU>
                    <FTREF/>
                     The 
                    <E T="03">Final Rule</E>
                     and 
                    <E T="03">Procedural Guidance</E>
                     provide that Commerce will maintain an annual inquiry service list for each order or suspended investigation, and any interested party submitting a scope ruling application or request for circumvention inquiry shall serve a copy of the application or request on the persons on the annual inquiry service list for that order, as well as any companion order covering the same merchandise from the same country of origin.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Regulations to Improve Administration and Enforcement of Antidumping and Countervailing Duty Laws,</E>
                         86 FR 52300 (September 20, 2021) (
                        <E T="03">Final Rule</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Scope Ruling Application; Annual Inquiry Service List; and Informational Sessions,</E>
                         86 FR 53205 (September 27, 2021) (
                        <E T="03">Procedural Guidance</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    In accordance with the Procedural Guidance, for orders published in the 
                    <E T="04">Federal Register</E>
                     after November 4, 2021, Commerce will create an annual inquiry service list segment in Commerce's online e-filing and document management system, Antidumping and Countervailing Duty Electronic Service System (ACCESS), available at 
                    <E T="03">https://access.trade.gov,</E>
                     within five business days of publication of the order. Each annual inquiry service list will be saved in ACCESS, under each case number, and under a specific segment type called “AISL—Annual Inquiry Service List.” 
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         This segment will be combined with the ACCESS Segment Specific Information (SSI) field which will display the month in which the notice of the order or suspended investigation was published in the 
                        <E T="04">Federal Register</E>
                        , also known as the anniversary month. For example, for an order under case number A-000-000 that was published in the 
                        <E T="04">Federal Register</E>
                         in January, the relevant segment and SSI combination will appear in ACCESS as “AISL—January Anniversary.” Note that there will be only one annual inquiry service list segment per case number, and the anniversary month will be pre-populated in ACCESS.
                    </P>
                </FTNT>
                <P>
                    Interested parties who wish to be added to the annual inquiry service list for an order must submit an entry of appearance to the annual inquiry service list segment for the order in ACCESS within 30 days after the date of publication of the order. For ease of administration, Commerce requests that law firms with more than one attorney representing interested parties in an order designate a lead attorney to be included on the annual inquiry service list. Commerce will finalize the annual inquiry service list within five business days thereafter. As mentioned in the 
                    <E T="03">Procedural Guidance,</E>
                     the new annual inquiry service list will be in place until the following year, when the 
                    <E T="03">Opportunity Notice</E>
                     for the anniversary month of the order is published.  
                </P>
                <P>Commerce may update an annual inquiry service list at any time as needed based on interested parties' amendments to their entries of appearance to remove or otherwise modify their list of members and representatives, or to update contact information. Any changes or announcements pertaining to these procedures will be posted to the ACCESS website.</P>
                <HD SOURCE="HD1">Special Instructions for Petitioners and Foreign Governments</HD>
                <P>
                    In the 
                    <E T="03">Final Rule,</E>
                     Commerce stated that, “after an initial request and placement on the annual inquiry service list, both petitioners and foreign governments will automatically be placed on the annual inquiry service list in the years that follow.” 
                    <SU>13</SU>
                    <FTREF/>
                     Accordingly, as stated above, the petitioners and foreign governments should submit their initial entry of appearance after publication of this notice in order to appear in the first annual inquiry service list. Pursuant to 19 CFR 351.225(n)(3), the petitioners and foreign governments will not need to resubmit their entries of appearance each year to continue to be included on the annual inquiry service list. However, the petitioners and foreign governments are responsible for making amendments to their entries of appearance during the annual update to the annual inquiry service list in accordance with the procedures described above.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Final Rule,</E>
                         86 FR at 52335.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>
                    This notice constitutes the CVD orders with respect to float glass from China and Malaysia pursuant to section 706(a) of the Act. Interested parties can find a list of CVD orders currently in effect at 
                    <E T="03">https://www.trade.gov/data-visualization/adcvd-proceedings.</E>
                </P>
                <P>These CVD orders are published in accordance with section 706(a) of the Act and 19 CFR 351.211(b).</P>
                <SIG>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">Scope of the Orders</HD>
                    <P>The scope of the orders covers float glass products (FGP), which are articles of soda-lime-silica glass that are manufactured by floating a continuous strip of molten glass over a smooth bath of tin (or another liquid metal with a density greater than molten glass), cooling the glass in an annealing lehr, and cutting it to appropriate dimensions. For purposes of the orders, float glass products have an actual thickness of at least 2.0 mm (0.0787 inches) and an actual surface area of at least 0.37 square meters (4.0 square feet).</P>
                    <P>The country of origin of each float glass product is determined by the location where the soda-lime-silica glass is first manufactured by floating a continuous strip of molten glass over a smooth bath of tin and cooling the glass in an annealing lehr, regardless of the location of any downstream finishing or fabrication operations.</P>
                    <P>Prior to being subjected to further treatment, finishing, or fabrication, float glass products meet the requirements of Type I under ASTM-C1036 of the American Society for Testing and Materials (ASTM).</P>
                    <P>
                        Float glass products may be clear, stained, tinted, or coated with one or more materials. Examples of coated float glass products include Low-E architectural glass (
                        <E T="03">i.e.,</E>
                         glass 
                        <PRTPAGE P="17256"/>
                        with a low emissivity coating to limit the penetration of radiant heat energy) and frameless mirrors (
                        <E T="03">i.e.,</E>
                         flat glass with a silver, aluminum, or other reflective layer) such as mirror stock sheet.
                    </P>
                    <P>Float glass products may be annealed, chemically strengthened, heat strengthened, or tempered to achieve a desired surface compression, pursuant to ASTM-C1048, ASTM-C1422/C1422M, or other similar specifications.</P>
                    <P>
                        Float glass products include tub and shower enclosures (
                        <E T="03">i.e.,</E>
                         doors and panels) made of tempered glass, which may be sold with attached or unattached hardware. In such cases, the scope covers only the tempered glass, to the exclusion of any non-glass hardware.
                    </P>
                    <P>
                        The only float glass product assemblies included within the scope are: (1) articles consisting of two of more sheets of float glass that are bonded together using a polymer interlayer (
                        <E T="03">i.e.,</E>
                         laminated glass); (2) insulating glass units (IGUs), which consist of two or more sheets of float glass separated by a spacer material and hermetically sealed together at the edge in order to create a thermal barrier using air or one or more gases but excluding any non-float glass components (other than the spacer and insulating materials) that may be mounted within the space between sheets of float glass (
                        <E T="03">e.g.,</E>
                         blinds, wrought iron cores, and camed patterned glass), as such non-float glass components are deemed outside the scope and not subject to duties; and (3) LED mirrors (
                        <E T="03">i.e.,</E>
                         float glass mirrors with one or more light-emitting diodes attached to or integrated with the mirror, as well as framed float glass mirrors with one or more light-emitting diodes attached to or integrated with the mirror or the mirror frame, but without other electronic functionality such as digital or video displays or audio circuitry).
                    </P>
                    <P>Float glass products covered by the scope may meet one or more of the ASTM-C162, ASTM-C1036, ASTM-C1048, ASTM-C1172, ASTM-C1349, ASTM-C1376, ASTM-C1422/C1422M, ASTM-C1464, ASTM-C1503, ASTM-C1651, ASTM-E1300, and ASTM-E2190 specifications, definitions, and/or standards.</P>
                    <P>
                        Float glass products may be further worked, including, but not limited to, operations such as: cutting; beveling; edging; notching; drilling; etching; bending; curving; chipping; embossing; engraving; surface grinding; or polishing; and sandblasting (
                        <E T="03">i.e.,</E>
                         using high velocity air to stream abrasive particles and thereby impart a frosted aesthetic to the glass surface). A float glass product which undergoes further work remains within the scope so long as the soda-lime-silica glass originally satisfied the requirements of ASTM-C1036 Type I and was first manufactured in a subject country, regardless of where it is further worked.
                    </P>
                    <P>
                        Excluded from the scope are: (1) wired glass (
                        <E T="03">i.e.,</E>
                         glass with a layer of wire mesh embedded within); (2) patterned flat glass (
                        <E T="03">i.e.,</E>
                         rolled glass with a pattern impressed on one or both sides) meeting the requirements of Type II under ASTM-C1036, including greenhouse glass and patterned solar glass (
                        <E T="03">i.e.,</E>
                         photovoltaic glass with a textured surface); (3) safety glazing materials for vehicles certified to American National Standards Institute (ANSI) Standard Z26.1; (4) vacuum insulating glass (VIG) units, which consist of two or more sheets of float glass separated by a spacer material, with at least one hermetically sealed compartment that uses a gas-free vacuum as a thermal barrier; (5) framed mirrors without any LEDs integrated with the mirror or the mirror frame; (6) unframed “over-the-door” mirrors that are ready for use as imported without undergoing after importation any processing, finishing, or fabrication; and (7) heat-strengthened washing machine lid glass with an actual surface area less than 6.0 square feet (0.56 square meters).
                    </P>
                    <P>
                        Also excluded from the scope of the orders are: (1) soda-lime-silica glass containing less than 0.01 percent iron oxide by weight, annealed with a surface compression less than 3,500 pounds per square inch (PSI), having a transparent conductive oxide base coating (
                        <E T="03">e.g.,</E>
                         tin oxide), and with an actual thickness less than or equal to 4.0 mm (0.1575 inches) (
                        <E T="03">i.e.,</E>
                         “coated solar glass”); and (2) heat treated soda-lime-silica glass with a surface compression between 3,500 and 10,000 PSI, containing two or more drilled holes, and having an actual thickness less than 2.5 mm (0.0984 inches) (
                        <E T="03">i.e.,</E>
                         “clear back solar glass”). Solar glass products (also known as photovoltaic glass) are designed to facilitate the conversion of solar energy into electricity.
                    </P>
                    <P>
                        Also excluded are metal-camed glass products (
                        <E T="03">i.e.,</E>
                         panels of glass joined together with metal banding) where the constituent glass panels would otherwise be excluded by reason of their size (
                        <E T="03">e.g.,</E>
                         an actual surface area less than 0.37 square meters, or 4.0 square feet) and/or by reason of consisting of patterned flat glass (
                        <E T="03">i.e.,</E>
                         rolled glass with a pattern impressed on one or both sides) meeting the requirements of Type II under ASTM-C1036.
                    </P>
                    <P>
                        Also excluded from the scope of the orders are any products already covered by the scope of any extant antidumping and/or countervailing duty orders, including 
                        <E T="03">Aluminum Extrusions from the People's Republic of China: Antidumping Duty Order,</E>
                         76 FR 30650 (May 26, 2011), and 
                        <E T="03">Aluminum Extrusions from the People's Republic of China: Countervailing Duty Order,</E>
                         76 FR 30653 (May 26, 2011).
                    </P>
                    <P>The products subject to the orders are currently classifiable under subheadings 7005.10.8000, 7005.21.1010, 7005.21.1030, 7005.21.2000, 7005.29.1810, 7005.29.1850, 7005.29.2500, 7007.29.0000, 7008.00.0000, 7009.91.5010, 7009.91.5095, and 7009.92.5010 of the Harmonized Tariff Schedule of the United States (HTSUS). Products subject to the orders may also enter under HTSUS subheadings 7006.00.4010, 7006.00.4050, 7007.19.0000, 7013.99.2000, 7013.99.9090, 7610.10.0030, and 7610.90.0080. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the scope of the orders is dispositive.</P>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06649 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <DEPDOC>[RTID 0648-XF630]</DEPDOC>
                <SUBJECT>Fisheries of the South Atlantic; Southeast Data, Assessment, and Review; Public Meeting </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service, National Oceanic and Atmospheric Administration, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Southeast Data Assessment and Review 90 Assessment Webinar 5 for south atlantic red snapper.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Southeast Data Assessment and Review (SEDAR) 90 assessment process of South Atlantic Red Snapper will consist of a Data Workshop, a series of Assessment Webinars, and a Review Workshop. See 
                        <E T="02">SUPPLEMENTARY INFORMATION.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The SEDAR 90 Assessment Webinar 5 will be held from 1 p.m. until 4 p.m. EDT April 28, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">SEDAR address:</E>
                         4055 Faber Place Drive, Suite 201, North Charleston, SC 29405. 
                        <E T="03">www.sedarweb.org. Meeting address:</E>
                         The SEDAR 90 Assessment Webinar 5 will be held via webinar. The webinar is open to members of the public. The established times may be adjusted as necessary to accommodate the timely completion of discussion relevant to the assessment process. Such adjustments may result in the meeting being extended from or completed prior to the time established by this notice.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Emily Ott, SEDAR Coordinator; (843) 302-8434. Email: 
                        <E T="03">Emily.Ott@safmc.net.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Gulf, South Atlantic, and Caribbean Fishery Management Councils, in conjunction with the National Marine Fisheries Service and the Atlantic and Gulf States Marine Fisheries Commissions have implemented the SEDAR process. SEDAR is a participatory process for developing, evaluating and reviewing information used for fisheries management advice. This multi-step process for determining the status of fish stocks in the Southeast Region may include (1) a Data stage, and (2) an Assessment stage, and (3) a Review stage. Each stage produces a report summarizing decisions made during that stage. A final stock assessment report is produced at the end of a SEDAR process documenting data sets used, model configurations and the opinions from the independent peer 
                    <PRTPAGE P="17257"/>
                    review. Participants for SEDAR projects are appointed by the Gulf, South Atlantic, and Caribbean Fishery Management Councils and National Marine Fisheries Service Southeast Regional Office, HMS Management Division, and Southeast Fisheries Science Center. Participants may include data collectors and database managers; stock assessment scientists, biologists, and researchers; constituency representatives including fishermen, environmentalists, and non-governmental organizations (NGO's); International experts; and staff of Councils, Commissions, and state and Federal agencies.
                </P>
                <P>The items of discussion in the SEDAR 90 Assessment Webinar 5 are as follows:</P>
                <P>Participants will Review recommendations made on assessment webinar 4, continue discussion of new modeling topics. Although non-emergency issues not contained in this agenda may come before this group for discussion, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically identified in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the intent to take final action to address the emergency.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to the Council office (see 
                    <E T="02">ADDRESSES</E>
                    ) at least 5 business days prior to each workshop.
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The times and sequence specified in this agenda are subject to change.</P>
                </NOTE>
                <EXTRACT>
                    <FP>
                        (Authority: 16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                        )
                    </FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06613 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XF637]</DEPDOC>
                <SUBJECT>Mid-Atlantic Fishery Management Council (MAFMC); Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Mid-Atlantic and New England Fishery Management Councils will hold a public meeting of their joint Northeast Trawl Advisory Panel (NTAP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The meeting will be held on Thursday, April 23, 2026, from 12 p.m.-2 p.m. For agenda details, see 
                        <E T="02">SUPPLEMENTARY INFORMATION.</E>
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will be held via webinar. Connection information will be posted to the Council's calendar prior to the meeting at 
                        <E T="03">https://www.mafmc.org.</E>
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         Mid-Atlantic Fishery Management Council, 800 N State Street, Suite 201, Dover, DE 19901; telephone: (302) 674-2331; 
                        <E T="03">https://www.mafmc.org.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christopher M. Moore, Ph.D., Executive Director, Mid-Atlantic Fishery Management Council, telephone: (302) 526-5255.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Mid-Atlantic and New England Fishery Management Councils' NTAP will meet to discuss the Operational Manual and Orientation Document. The intent of this meeting is to discuss NTAP in detail, including background, organization, purpose, and member expectation. This meeting will be an opportunity for new and existing NTAP members to discuss and learn about the goals and purposes of NTAP.</P>
                <P>The meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Shelley Spedden, (302) 526-5251 at least 5 days prior to the meeting date.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1801 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2026. </DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06612 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <SUBJECT>Initiation of Review of Management Plan for Flower Garden Banks National Marine Sanctuary; Request for Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of National Marine Sanctuaries (ONMS), National Ocean Service (NOS), National Oceanic and Atmospheric Administration (NOAA), Department of Commerce (DOC).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Initiation of review of management plan; request for information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Oceanic and Atmospheric Administration is initiating a review of the Flower Garden Banks National Marine Sanctuary management plan, to evaluate progress toward implementing the goals of the sanctuary and to revise the management plan as necessary to fulfill the purposes and policies of the National Marine Sanctuaries Act (NMSA). NOAA is requesting information from individuals, companies, organizations, Tribes, and government agencies on the scope, types, and significance of issues that NOAA should address in its process to revise the management plan. In addition to receiving written comments, NOAA will hold public meetings to provide information on the management plan review process and to gather oral comments.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>All comments should be received on or before 11:59 p.m. Eastern Daylight Time (EDT) on May 21, 2026.</P>
                    <P>Comments will also be accepted during public meetings. Public meetings will be held on:</P>
                    <P>
                        (1) 
                        <E T="03">Date:</E>
                         April 20, 2026. 
                    </P>
                    <P>
                        <E T="03"> Location:</E>
                         Virtual. Registration is required to attend; to register and for additional meeting details, visit: 
                        <E T="03">https://flowergarden.noaa.gov/management/mpr.html.</E>
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6-8 p.m. Central Daylight Time (CDT).
                    </P>
                    <P>
                        (2) 
                        <E T="03">Date:</E>
                         May 19, 2026.
                    </P>
                    <P>
                        <E T="03">Location:</E>
                         Flower Garden Banks National Marine Sanctuary, 4700 Avenue U, Building 216, Galveston, Texas 77551. Registration is not required to attend.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         2-4 p.m. CDT.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Date:</E>
                         May 19, 2026.
                    </P>
                    <P>
                        <E T="03">Location:</E>
                         Flower Garden Banks National Marine Sanctuary, 4700 Avenue U, Building 216, Galveston, Texas 77551. Registration is not required to attend.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6-8 p.m. CDT.
                    </P>
                    <P>NOAA may take audio recordings of the public meetings, including the public comment portion of the meetings. NOAA may end a meeting before the time noted above if all those participating have completed their oral comments.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be submitted by the following methods:</P>
                    <P>
                        (1) 
                        <E T="03">Electronic Submission:</E>
                         Federal eRulemaking Portal 
                        <E T="03">https://www.regulations.gov/docket/NOAA-NOS-2025-0009.</E>
                         To submit electronic 
                        <PRTPAGE P="17258"/>
                        comments via the Federal eRulemaking Portal, visit 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket Number NOAA-NOS-2025-0009.
                    </P>
                    <P>
                        (2)
                        <E T="03"> Mail:</E>
                         Written comments may also be mailed to Flower Garden Banks National Marine Sanctuary (Management Plan Review), at 4700 Avenue U, Building 216, Galveston, Texas 77551.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Public Meetings:</E>
                         Provide oral comments during public meetings, listed in the 
                        <E T="02">DATES</E>
                         section above. Registration is not required to attend in-person meetings. Registration is required to attend the virtual meeting. Upon registration, NOAA will send a confirmation email with a link to the virtual meeting. Registration will remain open until the virtual meeting concludes, and any participant in attendance may provide oral comment. Registration details for the virtual meeting and additional information about how to participate in these public meetings are available at 
                        <E T="03">https://flowergarden.noaa.gov/management/mpr.html.</E>
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All comments received are a part of the public record. The entirety of each comment, including the name of the commenter, email address, attachments, and other supporting materials will be publicly accessible. Do not submit confidential business information or otherwise sensitive or protected information such as account numbers or Social Security numbers. NOAA will accept anonymous comments through 
                        <E T="03">regulations.gov</E>
                         (enter N/A in the required fields to remain anonymous).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Michelle Johnston, Superintendent, Flower Garden Banks National Marine Sanctuary, 4700 Avenue U, Building 216, Galveston, Texas 77551, or see: 
                        <E T="03">https://flowergarden.noaa.gov/management/mpr.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    Flower Garden Banks National Marine Sanctuary (sanctuary or FGBNMS) is located 80 to 125 miles off of the coasts of Texas and Louisiana, encompassing approximately 160 square miles of marine ecosystems across 17 separate banks. These banks are made up of a combination of small underwater mountains, ridges, troughs, and hard bottom patches along the continental shelf. Together, they compose a chain of nationally significant habitats for recreationally and economically important species along the continental shelf. The ecosystems of the sanctuary include thriving shallow water coral reefs, algal-sponge communities, and deeper mesophotic reefs of black coral, octocoral, and algal nodule habitats. NOAA first designated the sanctuary in 1992 (56 FR 63634). At that time, the sanctuary consisted of East and West Flower Garden Banks. Stetson Bank was added to the sanctuary in 1996 through an act of Congress (Pub. L. 104-283). In 2021, NOAA expanded the sanctuary to include portions of 14 more banks and applied the existing 2012 management plan to the expansion areas (86 FR 4937). These include Horseshoe, MacNeil, Rankin, 28 Fathom, Bright, Geyer, Elvers, McGrail, Bouma, Sonnier, Rezak, Sidner, Parker, and Alderdice Banks. The sanctuary provides ecosystem services for recreational and commercial uses, including opportunities for scuba diving, fishing, advancing scientific understanding, and associated education and outreach. NOAA manages FGBNMS as part of the National Marine Sanctuary System under the National Marine Sanctuaries Act of 1972, 16 U.S.C. 1431 
                    <E T="03">et seq.,</E>
                     which comprises 18 national marine sanctuaries.
                </P>
                <P>In addition to NOAA, several other Federal agencies share jurisdiction over the FGBNMS area and its resources including: the U.S. Department of the Interior's Bureau of Ocean Energy Management and Bureau of Safety and Environmental Enforcement, which share primary jurisdiction over offshore energy exploration and development; the U.S. Environmental Protection Agency, which is responsible for protecting the quality of the nation's waters; and the Gulf Council, which jointly manages the U.S. fisheries along with NOAA. Additionally, U.S. Department of Defense and U.S. Coast Guard operations, as well as commercial shipping and other marine activities, occur in and around the waters of FGBNMS.</P>
                <P>
                    Subsection 304(e) of the NMSA requires NOAA to periodically review sanctuary management plans to evaluate progress toward implementing the management plan and goals for the sanctuary, and to revise the plans as necessary. This review ensures that national marine sanctuaries continue to best conserve and enhance their nationally significant resources (16 U.S.C. 1434(e)). The current FGBNMS management plan was published in 2012, and is available at 
                    <E T="03">https://flowergarden.noaa.gov/management/2012mgmtplan.html.</E>
                     With this management plan review, NOAA is interested in public input on the adequacy of existing management actions for the expansion areas as well as the pre-expansion areas.
                </P>
                <P>The FGBNMS management plan review process is composed of four major stages: (1) information collection including through this request for information; (2) preparation and release of a draft management plan and a draft environmental review conducted under the National Environmental Policy Act (NEPA) and any proposed amendments to sanctuary regulations; (3) public review and comment on the draft documents; and (4) preparation and release of a final management plan and environmental review document, and any final amendments to sanctuary regulations, if applicable. NOAA will also, as applicable, address other statutory and regulatory requirements pursuant to the Endangered Species Act, Marine Mammal Protection Act, Essential Fish Habitat provisions of the Magnuson-Stevens Fishery Conservation and Management Act, Coastal Zone Management Act, National Historic Preservation Act, and Tribal consultation responsibilities under Executive Order 13175.</P>
                <HD SOURCE="HD1">II. Condition Report</HD>
                <P>
                    To inform the FGBNMS management plan review, NOAA recently published the FGBNMS Condition Report. The Condition Report, released in November 2024, assessed the period from 2009-2021 and presents summary information describing the status and trends of sanctuary resources, covering the broad categories of human activities and pressures, water quality, habitat, living resources, and maritime heritage resources. This report also included the status and trends of ecosystem services—the ways that humans benefit from the natural and cultural resources of the sanctuary. The report is available to the public online at 
                    <E T="03">https://sanctuaries.noaa.gov/media/docs/2024-fgbnms-condition-report.pdf.</E>
                </P>
                <HD SOURCE="HD1">III. Preliminary Topics of Focus</HD>
                <P>NOAA is particularly interested in receiving public comment on the following topics as they relate to the management plan review. This list does not preclude or in any way limit the consideration of additional topics raised through public comments, and discussions with partner agencies.</P>
                <HD SOURCE="HD2">Education and Community Outreach</HD>
                <P>
                    NOAA is seeking input on the effectiveness of its current education and outreach programs and new ideas for expanding public awareness, including new applications of technologies, new engagement spaces, and additional partnerships.
                    <PRTPAGE P="17259"/>
                </P>
                <P>• What additional formal and informal educational partnerships should NOAA pursue?</P>
                <P>• How can the application of new technologies enhance sanctuary education programs?</P>
                <P>• How can development of partnerships and external funding sources complement and supplement NOAA's programs to advance progress toward the sanctuary's goals and objectives?</P>
                <HD SOURCE="HD2">Responding to Environmental Pressures and Long-Term Trends</HD>
                <P>NOAA is seeking input on the effectiveness of the sanctuary's management responses to pressures.</P>
                <P>
                    • How can the new management plan effectively address issues for both shallow coral and deep mesophotic habitats, as identified in the 2009-2021 Condition Report (
                    <E T="03">https://sanctuaries.noaa.gov/media/docs/2024-fgbnms-condition-report.pdf</E>
                    ) and the 2023 Vulnerability Assessment (
                    <E T="03">https://sanctuaries.noaa.gov/media/docs/20231201-fgnms-cva-final-report.pdf</E>
                    )?
                </P>
                <P>• What emergency response and restoration plans are necessary to address potential increases in occurrences of acute environmental stressors, such as coral bleaching events?</P>
                <P>• How can NOAA better address invasive species?</P>
                <P>• What collaboration and coordination among government agencies and jurisdictions is necessary or helpful to advance effective stewardship of sanctuary resources?</P>
                <HD SOURCE="HD2">Research and Monitoring</HD>
                <P>NOAA is seeking input on critical research needs for effective management and new research partnerships.</P>
                <P>
                    • What research and monitoring activities are necessary to address topics identified in the 2024 Science Needs assessment (
                    <E T="03">https://sanctuaries.noaa.gov/science/assessment/flower-garden-banks/</E>
                    ) across the multiple habitats at all 17 banks of the sanctuary?
                </P>
                <P>• What new partnerships could potentially address research gaps in a resource-constrained environment, including sharing of federal and non-federal data, platforms, and equipment?</P>
                <P>• What research and monitoring activities are necessary to adequately monitor and understand mesophotic habitats?</P>
                <P>• What new or emerging technologies could cost-effectively enhance support for research and monitoring efforts?</P>
                <HD SOURCE="HD2">Resource Use</HD>
                <P>NOAA is seeking input on how to effectively monitor resource use and visitation, improve access, and ensure that uses are compatible with ecosystem health. Consistent with the policies and principles of Executive Order 14313 (July 3, 2025) NOAA aims to prioritize responsible conservation, restore our lands and waters, and protect our Nation's outdoor heritage for the enjoyment of the American people.</P>
                <P>• What actions are or could be effective to ensure visitor safety, facilitate visitor access, and support compatible use of sanctuary resources?</P>
                <P>• How can NOAA improve monitoring and understanding of resource use, regulation compliance, and regulation enforcement in the remotely located sanctuary?</P>
                <P>• What strategic partnerships should NOAA pursue to maintain and enhance infrastructure for access, such as mooring buoys, in a resource-constrained program environment?</P>
                <HD SOURCE="HD1">IV. Boundaries and Regulations</HD>
                <P>At this time NOAA also does not expect to undertake any major rulemaking actions as part of this management plan review process.</P>
                <P>
                    <E T="03">Authority:</E>
                     16 U.S.C. 1431 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <NAME>John Armor,</NAME>
                    <TITLE>Director, Office of National Marine Sanctuaries, National Ocean Service, National Oceanic and Atmospheric Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06587 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-NK-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XF631]</DEPDOC>
                <SUBJECT>South Atlantic Fishery Management Council—Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Meeting of the South Atlantic Fishery Management Council's Outreach and Communications Advisory Panel.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The South Atlantic Fishery Management Council (Council) will hold a meeting of the Outreach and Communications Advisory Panel (AP) May 5-6, 2026.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Outreach and Communications AP will meet May 5, 2026, 9 a.m. to 5 p.m. and May 6, 2026, 9 a.m. to 12 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Meeting address:</E>
                         The Meeting will be held at Hilton Garden Inn Charleston, 5265 International Blvd., N Charleston, SC 29418; phone (843) 308-9330.
                    </P>
                    <P>
                        <E T="03">Council address:</E>
                         South Atlantic Fishery Management Council, 4055 Faber Place Drive, Suite 201, N Charleston, SC 29405. The meeting will also be available via webinar. See 
                        <E T="02">SUPPLEMENTARY INFORMATION.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ashley Oliver, Outreach Coordinator, SAFMC; phone (843) 302-8442 or toll free (866) SAFMC-10; FAX (843) 769-4520; email: 
                        <E T="03">ashley.oliver@safmc.net.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Meeting information, including the agenda, overview, briefing book materials, and an online public comment form will be posted on the Council's website at: 
                    <E T="03">https://safmc.net/advisory-panel-meetings/</E>
                     2 weeks prior to the meeting. The meeting is open to the public and available via webinar as it occurs. The webinar registration link will be available from the Council's website. Public comment will also be taken during the meeting.
                </P>
                <P>The agenda for the Outreach and Communications AP meeting includes updates from AP members on recent outreach and communication efforts; review of the Council's draft outreach and communication goals; and an update on digital communications efforts. AP members will also receive updates on the Sea Grant Reef Fish Fellowship; the Council's Citizen Science Program; state outreach efforts for the potential South Atlantic Red Snapper Exempted Fishing Permits; and commemorationefforts for the 50th anniversaryof the Magnuson-Stevens Fishery Conservation and Management Act. The AP will receive an update on the Lines of Communication: Conversations with the Council; review the habitat and ecosystem FAQ; discuss how to engage graduates of the Marine Resource Education Program; and discuss ways to increase public attendance and accessibility at Council hosted meetings. The AP will address other business as needed and provide recommendations for Council consideration.</P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>
                    The meeting is physically accessible to people with disabilities. Requests for auxiliary aids should be directed to the Council office (see 
                    <E T="02">ADDRESSES</E>
                    ) 3 days prior to the meeting.
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The times and sequence specified in this agenda are subject to change.</P>
                </NOTE>
                <EXTRACT>
                    <FP>
                        (Authority: 16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                        )
                    </FP>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="17260"/>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Rey Israel Marquez,</NAME>
                    <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06615 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">U.S. INTERNATIONAL DEVELOPMENT FINANCE CORPORATION</AGENCY>
                <DEPDOC>[DFC-006]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comments Request; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Development Finance Corporation (DFC).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        DFC published a document in the 
                        <E T="04">Federal Register</E>
                         on March 30, 2026, concerning requests for comments on this notice to allow an additional thirty (30) days for public comments to be submitted. The 60-day date was an error.
                    </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of March 30, 2026, in FR Doc. 2026-06119 on page 15605, in the first column, correct the 
                    <E T="02">Dates</E>
                     caption to read:
                </P>
                <FP>
                    <E T="02">DATES:</E>
                     Comments must be received by May 6, 2026.
                </FP>
                <SIG>
                    <NAME>Heather Carroll,</NAME>
                    <TITLE>Corporate Secretary, Office of the General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06626 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Army</SUBAGY>
                <DEPDOC>[Docket ID: USA-2026-HQ-0265]</DEPDOC>
                <SUBJECT>Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day information collection notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the 
                        <E T="03">Paperwork Reduction Act of 1995,</E>
                         the Department of the Army announces a proposed public information collection and seeks public comment on the provisions thereof. Comments are invited on: whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; the accuracy of the agency's estimate of the burden of the proposed information collection; ways to enhance the quality, utility, and clarity of the information to be collected; and ways to minimize the burden of the information collection on respondents, including through the use of automated collection techniques or other forms of information technology.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all comments received by June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
                    <P>
                        <E T="03">Federal eRulemaking Portal:</E>
                          
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Department of Defense, Office of the Director of Administration and Management, Privacy, Civil Liberties, and Transparency Directorate, Regulatory Division, 4800 Mark Center Drive, Mailbox #24, Suite 05F16, Alexandria, VA 22350-1700.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name, docket number and title for this 
                        <E T="04">Federal Register</E>
                         document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the internet at 
                        <E T="03">http://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>To request more information on this proposed information collection or to obtain a copy of the proposal and associated collection instruments, please write to Department of the Army, Army Safety Office, Chief of Staff, DACS-SF, 9351 Hall Rd., Fort Belvoir, VA 22060, ATTN: Mr. Timothy Mikulski at (703) 697-1321.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title; Associated Form; and OMB Number:</E>
                     Application for Army Radiation Permit; OMB Control Number 0702-0109.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Department of the Army must collect information to process applications for Army Radiation Permits (ARPs). This collection is necessary to ensure the safe use, storage, or possession of ionizing radiation sources by non-Army entities on an Army installation, as required by 32 CFR 655.10. The permit system is essential for protecting military personnel, civilian employees, and the public from potential radiation exposure.
                </P>
                <P>The information is used by the garrison commander to evaluate an applicant's request for an ARP. The application requires the entity to describe the purpose of the radiation source, provide qualifications of operating personnel, submit safety and storage procedures, and show evidence of a valid use authorization. This allows the commander to ensure the applicant can handle the radioactive materials safely and in accordance with all regulations.</P>
                <P>The respondents are non-Army entities, including civilian contractors, seeking to bring ionizing radiation sources onto an Army installation for a DoD-related activity. Without this information collection, the Army would be unable to maintain cognizance over radioactive sources on its installations, hindering the ability to prepare emergency responders and ensure the overall safety and security of the installation.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     470.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     235.
                </P>
                <P>
                    <E T="03">Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Annual Responses:</E>
                     235.
                </P>
                <P>
                    <E T="03">Average Burden per Response:</E>
                     2 hours.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <SIG>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06579 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Docket ID: DOD-2026-HA-0760]</DEPDOC>
                <SUBJECT>Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>The Office of the Assistant Secretary of Defense for Health Affairs (OASD(HA)), Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day information collection notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the 
                        <E T="03">Paperwork Reduction Act of 1995,</E>
                         the Defense Health Agency announces a proposed public information collection and seeks public comment on the provisions thereof. Comments are invited on: whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; the accuracy of the agency's estimate of the burden of the proposed information collection; ways to enhance the quality, utility, and 
                        <PRTPAGE P="17261"/>
                        clarity of the information to be collected; and ways to minimize the burden of the information collection on respondents, including through the use of automated collection techniques or other forms of information technology.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all comments received by June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
                    <P>
                        <E T="03">Federal eRulemaking Portal:</E>
                          
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Department of Defense, Office of the Director of Administration and Management, Privacy, Civil Liberties, and Transparency Directorate, Regulatory Division, 4800 Mark Center Drive, Mailbox #24, Suite 05F16, Alexandria, VA 22350-1700.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name, docket number and title for this 
                        <E T="04">Federal Register</E>
                         document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the internet at 
                        <E T="03">http://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>To request more information on this proposed information collection or to obtain a copy of the proposal and associated collection instruments, please write to Defense Health Agency, 7700 Arlington Blvd., Falls Church, VA 22042, Amanda Grifka, 703-681-1771.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title; Associated Form; and OMB Number:</E>
                     Community Strengths and Themes Assessment (CSTA); OMB Control Number 0720-CSTA.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     Regular completion of comprehensive community health assessments (CHAs) that identify community strengths and needs from the perspective of those living, working, and using services is essential to achieve military health and readiness goals. These CHAs support data-informed decision-making and evidence-based community health improvement plans (CHIPs) to guide military community and command-based action. While a variety of data describing health, readiness, resilience, and perceptions of Active Duty Service Members are available for inclusion in military CHAs, limited sources examine Service Members' perspectives on current health and quality of life priorities and the experiences and perceptions of Family members, Civilian personnel, and military Retirees.
                </P>
                <P>The Community Strengths and Themes Assessment (CSTA) is a standardized assessment tool for military installation communities and geographically dispersed commands to assess community-level health issues and perceptions of health- and quality of life-related needs with the goal of improving Force and Family readiness to meet the obligations and challenges of military life.</P>
                <P>The CSTA is designed to collect data from participating Active-Duty Service Members, their adult Family members, Civilian personnel, and military Retirees. The CSTA helps identify priorities to assist commanders, other senior leaders, and community stakeholders in developing a responsive and comprehensive CHIP for action.</P>
                <P>Current Department of Defense Instructions (DoDIs) direct completion of assessments of military communities for health and readiness risk factors and needs, and use of these activities to inform priorities and program planning, including DoDI 1010.10, Health Promotion and Disease Prevention, DoDI 1342.22, Military Family Readiness, and DoDI 6400.11, DoD Integrated Primary Prevention Policy for Prevention Workforce and Leaders.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     2,325.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     9,300.
                </P>
                <P>
                    <E T="03">Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Annual Responses:</E>
                     9,300.
                </P>
                <P>
                    <E T="03">Average Burden per Response:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Every two to five years at each participating location.
                </P>
                <SIG>
                    <DATED> Dated: April 1, 2026.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06582 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Department of Defense Wage Committee (DoD Wage Committee); Notice of Federal Advisory Committee Meetings </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Under Secretary of Defense for Personnel and Readiness (USD(P&amp;R)), Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of closed Federal Advisory Committee meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The DoD is publishing this notice to announce that the following Federal Advisory Committee meetings of the DoD Wage Committee will take place. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>Tuesday, March 17, 2026, from 10:00 a.m. to 12:00 p.m. and was closed to the public.</P>
                    <P>Tuesday, March 31, 2026, from 10:00 a.m. to 11:00 a.m. and was closed to the public.</P>
                    <P>Tuesday, April 14, 2026, from 10:00 a.m. to 11:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, April 28, 2026, from 10:00 a.m. to 10:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, May 12, 2026, from 10:00 a.m. to 11:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, May 26, 2026, from 10:00 a.m. to 10:30 a.m. and will be closed to the public.</P>
                    <P>Tuesday, June 9, 2026, from 10:00 a.m. to 11:00 a.m. and will be closed to the public.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Meetings will be held via Microsoft Teams. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Karl Fendt, Designated Federal Officer (DFO) (571) 372-1618 (voice), 
                        <E T="03">karl.h.fendt.civ@mail.mil.</E>
                         (email), 4800 Mark Center Drive, Suite 05G21, Alexandria, Virginia 22350 (mailing address). Any agenda updates can be found at the DoD Wage Committee's official website: 
                        <E T="03">https://wageandsalary.dcpas.osd.mil/BWN/DODWAGECOMMITTEE/.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>These meetings are held under the provisions of chapter 10 of title 5, United States Code (U.S.C.) (commonly known as the “Federal Advisory Committee Act” or “FACA”), subsection 552b(c) of title 5, U.S.C., and 41 Code of Regulation (CFR) 102-3.140 and 102-3.155.</P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The purpose of these meetings is to provide independent advice and recommendations on matters relating to the conduct of wage surveys and the establishment of wage schedules for all appropriated fund and non-appropriated fund areas of blue-collar employees within the DoD.
                </P>
                <P>
                    Due to circumstances beyond the control of the DFO and Department of War, the Department of Defense Wage Committee was unable to provide public notification required by 41 CFR 102-3.150 (a) concerning its March 17, 2026 and March 31, 2026 meetings. Accordingly, the Advisory Committee Management Officer for the Department of War, pursuant to 41 CFR 102-3.150(b), waived the 15-calendar day notification requirement.
                    <PRTPAGE P="17262"/>
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">March 17, 2026 (Already Held)</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Washoe-Churchill, Nevada wage area (AC-011).</P>
                <P>3. Wage Schedule (Full Scale) for the Orange, Florida wage area (AC-062).</P>
                <P>4. Wage Schedule (Full Scale) for the Bay, Florida wage area (AC-063).</P>
                <P>5. Wage Schedule (Full Scale) for the Escambia, Florida wage area (AC-064).</P>
                <P>6. Wage Schedule (Full Scale) for the Okaloosa, Florida wage area (AC-065).</P>
                <P>7. Wage Schedule (Full Scale) for the Clark, Nevada wage area (AC-140).</P>
                <P>8. Wage Schedule (Wage Change) for the Brevard, Florida wage area (AC-061).</P>
                <P>9. Wage Schedule (Wage Change) for the Hillsborough, Florida wage area (AC-119).</P>
                <P>10. Wage Schedule (Wage Change) for the Miami-Dade, Florida wage area (AC-158).</P>
                <P>11. Wage Schedule (Wage Change) for the Duval, Florida wage area (AC-159).</P>
                <P>12. Wage Schedule (Wage Change) for the Monroe, Florida wage area (AC-160).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>13. Wage Schedule (Full Scale) for the Birmingham, Alabama wage area (AC-002).</P>
                <P>14. Wage Schedule (Full Scale) for the Southern Colorado wage area (AC-023).</P>
                <P>15. Wage Schedule (Full Scale) for the New York-Newark, New York wage area (AC-094).</P>
                <P>16. Wage Schedule (Full Scale) for the Dayton, Ohio wage area (AC-107).</P>
                <P>17. Wage Schedule (Full Scale) for the Harrisburg-York-Lebanon, Pennsylvania wage area (AC-114).</P>
                <P>18. Wage Schedule (Full-Scale) for the Wyoming wage area (AC-150).</P>
                <P>19. Wage Schedule (Wage Change) for the Denver, Colorado wage area (AC-022).</P>
                <P>20. Wage Schedule (Wage Change) for the Jacksonville, Florida wage area (AC-030).</P>
                <P>21. Wage Schedule (Wage Change) for the Miami-Port St. Lucie-Fort Lauderdale, Florida wage area (AC-031).</P>
                <P>22. Wage Schedule (Wage Change) for the Detroit-Warren-Ann Arbor, Michigan wage area (AC-070).</P>
                <P>23. Wage Schedule (Wage Change) for the Southeastern North Carolina wage area (AC-101).</P>
                <P>24. Wage Schedule (Wage Change) for the Cincinnati, Ohio wage area (AC-104).</P>
                <P>25. Wage Schedule (Wage Change) for the Columbus-Marion-Zanesville, Ohio wage area (AC-106).</P>
                <P>26. Survey Specifications for the Hawaii wage area (AC-044).</P>
                <P>27. Survey Specifications for the Asheville, North Carolina wage area (AC-098).</P>
                <P>28. Survey Specifications for the Austin, Texas wage area (AC-129).</P>
                <P>29. Survey Specifications for the Southwestern, Wisconsin wage area (AC-149).</P>
                <P>30. Special Pay—Jacksonville, Florida Special Rates.</P>
                <P>31. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">March 31, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>2. Survey Specifications for the New Orleans, Louisiana wage area (AC-061).</P>
                <P>3. Survey Specifications for the Central and Northern Maine wage area (AC-064).</P>
                <P>4. Survey Specifications for the Southwestern Oregon wage area (AC-113).</P>
                <P>5. Survey Specifications for the Corpus Christi-Kingsville-Alice, Texas wage area (AC-130).</P>
                <P>6. Special Pay—Southeast Power Rate.</P>
                <P>7. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">April 14, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Survey Specifications for the Washington, District of Columbia wage area (AC-124).</P>
                <P>3. Survey Specifications for the Alexandria-Arlington-Fairfax, Virginia wage area (AC-125).</P>
                <P>4. Survey Specifications for the Prince William, Virginia wage area (AC-126).</P>
                <P>5. Survey Specifications for the Prince George's-Montgomery, Maryland wage area (AC-127).</P>
                <P>6. Survey Specifications for the Charles-St. Mary's, Maryland wage area (AC-128).</P>
                <P>7. Survey Specifications for the Anne Arundel, Maryland wage area (AC-147).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>8. Wage Schedule (Full Scale) for the Lexington, Kentucky wage area (AC-058).</P>
                <P>9. Wage Schedule (Full Scale) for the Northern Mississippi wage area (AC-096).</P>
                <P>10. Wage Schedule (Full Scale) for the Memphis, Tennessee wage area (AC-124).</P>
                <P>11. Wage Schedule (Full Scale) for the Nashville, Tennessee wage area (AC-125).</P>
                <P>12. Wage Schedule (Wage Change) for the Fresno, California wage area (AC-012).</P>
                <P>13. Wage Schedule (Wage Change) for the Sacramento-Roseville, California wage area (AC-014).</P>
                <P>14. Wage Schedule (Wage Change) for the Louisville, Kentucky wage area (AC-059).</P>
                <P>15. Wage Schedule (Wage Change) for the Jackson, Mississippi wage area (AC-078).</P>
                <P>16. Wage Schedule (Wage Change) for the Meridian, Mississippi wage area (AC-079).</P>
                <P>17. Wage Schedule (Wage Change) for the Eastern Tennessee wage area (AC-123).</P>
                <P>18. Survey Specifications for the Alaska wage area (AC-007).</P>
                <P>19. Special Pay—Fresno, California Special Rate.</P>
                <P>20. Special Pay—Northern Mississippi Special Rate.</P>
                <P>21. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">April 28, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Oklahoma, Oklahoma wage area (AC-104).</P>
                <P>
                    3. Wage Schedule (Full Scale) for the Harrison, Mississippi wage area (AC-104).
                    <PRTPAGE P="17263"/>
                </P>
                <P>4. Wage Schedule (Full Scale) for the Hardin-Jefferson, Kentucky wage area (AC-104).</P>
                <P>5. Wage Schedule (Full Scale) for the Wayne, North Carolina wage area (AC-104).</P>
                <P>6. Wage Schedule (Full Scale) for the Cumberland, North Carolina wage area (AC-104).</P>
                <P>7. Wage Schedule (Full Scale) for the Richland, South Carolina wage area (AC-104).</P>
                <P>8. Wage Schedule (Full Scale) for the Wichita, Texas wage area (AC-104).</P>
                <P>9. Wage Schedule (Full Scale) for the Comanche, Oklahoma wage area (AC-104).</P>
                <P>10. Wage Schedule (Full Scale) for the Craven, North Carolina wage area (AC-104).</P>
                <P>11. Wage Schedule (Wage Change) for the Lauderdale, Mississippi wage area (AC-001).</P>
                <P>12. Wage Schedule (Wage Change) for the Lowndes, Mississippi wage area (AC-104).</P>
                <P>13. Wage Schedule (Wage Change) for the Rapides, Louisiana wage area (AC-104).</P>
                <P>14. Wage Schedule (Wage Change) for the Caddo-Bossier, Louisiana wage area (AC-025).</P>
                <P>15. Wage Schedule (Wage Change) for the Chatham, Georgia wage area (AC-037).</P>
                <P>16. Wage Schedule (Wage Change) for the Dougherty, Georgia wage area (AC-046).</P>
                <P>17. Wage Schedule (Wage Change) for the Lowndes, Georgia wage area (AC-047).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>18. Survey Specifications for the Montana wage area (AC-083).</P>
                <P>19. Survey Specifications for the Charleston, South Carolina wage area (AC-119).</P>
                <P>20. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">May 12, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Survey Specifications for the Los Angeles, California wage area (AC-130).</P>
                <P>3. Survey Specifications for the Orange, California wage area (AC-131).</P>
                <P>4. Survey Specifications for the Ventura, California wage area (AC-132).</P>
                <P>5. Survey Specifications for the Riverside, California wage area (AC-133).</P>
                <P>6. Survey Specifications for the San Bernardino, California wage area (AC-134).</P>
                <P>7. Survey Specifications for the Santa Barbara, California wage area (AC-135).</P>
                <P>8. Survey Specifications for the Guam wage area (AC-150).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>9. Wage Schedule (Full Scale) for the Reno, Nevada wage area (AC-086).</P>
                <P>10. Wage Schedule (Full Scale) for the Syracuse-Utica-Rome, New York wage area (AC-097).</P>
                <P>11. Wage Schedule (Full Scale) for the North Dakota wage area (AC-103).</P>
                <P>12. Wage Schedule (Full Scale) for the Houston-Galveston-Texas City, Texas wage area (AC-133).</P>
                <P>13. Wage Schedule (Wage Change) for the Northeastern Arizona wage area (AC-008).</P>
                <P>14. Wage Schedule (Wage Change) for the Phoenix, Arizona wage area (AC-009).</P>
                <P>15. Wage Schedule (Wage Change) for the Tucson, Arizona wage area (AC-010).</P>
                <P>16. Wage Schedule (Wage Change) for the Minneapolis-St. Paul, Minnesota wage area (AC-075).</P>
                <P>17. Wage Schedule (Wage Change) for the Albany-Schenectady, New York wage area (AC-091).</P>
                <P>18. Wage Schedule (Wage Change) for the Northern New York wage area (AC-095).</P>
                <P>19. Wage Schedule (Wage Change) for the West Virginia wage area (AC-146).</P>
                <P>20. Survey Specifications for the Little Rock, Arkansas wage area (AC-011).</P>
                <P>21. Survey Specifications for the Cedar Rapids-Iowa City, Iowa wage area (AC-052).</P>
                <P>22. Survey Specifications for the Portland-Vancouver-Salem, Oregon wage area (AC-112).</P>
                <P>23. Survey Specifications for the Wichita Falls, Texas-Southwestern Oklahoma wage area (AC-138).</P>
                <P>24. Survey Specifications for the Madison, Wisconsin wage area (AC-147).</P>
                <P>25. Special Pay—Pacific Northwest Power Rate.</P>
                <P>26. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">May 26, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Wage Schedule (Full Scale) for the Calhoun, Alabama wage area (AC-104).</P>
                <P>3. Wage Schedule (Full Scale) for the Lake, Illinois wage area (AC-145).</P>
                <P>4. Wage Schedule (Full Scale) for the Douglas-Sarpy, Nebraska wage area (AC-149).</P>
                <P>5. Wage Schedule (Full Scale) for the Leavenworth, Kansas/Jackson-Johnson, Missouri wage area (AC-151).</P>
                <P>6. Wage Schedule (Full Scale) for the St. Clair, Illinois wage area (AC-157).</P>
                <P>7. Wage Schedule (Wage Change) for the Richmond, Georgia wage area (AC-035).</P>
                <P>8. Wage Schedule (Wage Change) for the Houston, Georgia wage area (AC-036).</P>
                <P>9. Wage Schedule (Wage Change) for the Pulaski, Arkansas wage area (AC-045).</P>
                <P>10. Wage Schedule (Wage Change) for the Montgomery, Alabama wage area (AC-048).</P>
                <P>11. Wage Schedule (Wage Change) for the Sedgwick, Kansas wage area (AC-078).</P>
                <P>12. Wage Schedule (Wage Change) for the Montgomery-Greene, Ohio wage area (AC-166).</P>
                <P>Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:</P>
                <P>13. Wage Schedule (Full Scale) for the Los Angeles, California wage area (AC-013).</P>
                <P>14. Survey Specifications for the Boston-Worcester-Providence, Massachusetts wage area (AC-068).</P>
                <P>15. Special Pay—Los Angeles, California Special Rate.</P>
                <P>16. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <HD SOURCE="HD2">June 9, 2026</HD>
                <P>Opening Remarks by Chair, Mr. Eric Clayton, and DFO, Mr. Karl Fendt.</P>
                <P>Reviewing survey results and/or survey specifications for the following Non-appropriated Fund areas:</P>
                <P>1. Any items needing further clarification or action from the previous meeting.</P>
                <P>2. Survey Specifications for the Maricopa, Arizona wage area (AC-012).</P>
                <P>3. Survey Specifications for the Pima, Arizona wage area (AC-013).</P>
                <P>4. Survey Specifications for the Yuma, Arizona wage area (AC-055).</P>
                <P>5. Survey Specifications for the Kings-Queens, New York wage area (AC-091).</P>
                <P>
                    Reviewing survey results and/or survey specifications for the following Appropriated Fund areas:
                    <PRTPAGE P="17264"/>
                </P>
                <P>6. Wage Schedule (Full Scale) for the Lake Charles-Alexandria, Louisiana wage area (AC-060).</P>
                <P>7. Wage Schedule (Full Scale) for the Rochester, New York wage area (AC-096).</P>
                <P>8. Wage Schedule (Full Scale) for the El Paso, Texas wage area (AC-132).</P>
                <P>9. Wage Scheule (Wage Change) for the Albuquerque-Santa Fe-Los Alamos, New Mexico wage area (AC-089).</P>
                <P>10. Survey Specifications for the Chicago-Naperville, Illinois wage area (AC-047).</P>
                <P>11. Survey Specifications for the Las Vegas, Nevada wage area (AC-085).</P>
                <P>12. Any items needing further clarification from this agenda may be discussed during future scheduled meetings.</P>
                <P>Closing Remarks by Chair, Mr. Eric Clayton.</P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     Pursuant to 5 U.S.C. 552b(c)(4), the DoD has determined that the meetings shall be closed to the public. The USD (P&amp;R), in consultation with the DoD Office of General Counsel, has determined in writing that each of these meetings is likely to disclose trade secrets and commercial or financial information obtained from a person and privileged or confidential.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 5 U.S.C. 1009(a)(3) and 41 CFR 102-3.140, interested persons may submit written statements to the DFO for the DoD Wage Committee at any time. Written statements should be submitted to the DFO at the email or mailing address listed above in 
                    <E T="02">FOR FUTHER INFORMATION CONTACT</E>
                    . If statements pertain to a specific topic being discussed at a planned meeting, then these statements must be submitted no later than five (5) business days prior to the meeting in question. Written statements received after this date may not be provided to or considered by the DoD Wage Committee until its next meeting. The DFO will review all timely submitted written statements and provide copies to all the committee members before the meetings that are the subject of this notice.
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Stephanie J. Bost,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06645 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Energy Information Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Extension</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Energy Information Administration (EIA), U.S. Department of Energy (DOE).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        DOE submitted an information collection request for extension as required by the Paperwork Reduction Act of 1995. The information collection requests a three-year extension of its Form GC-859 
                        <E T="03">Nuclear Fuel Data Survey,</E>
                         OMB Control Number 1901-0287. Form GC-859 collects data on spent nuclear fuel from all utilities that operate commercial nuclear reactors and from all others that possess irradiated fuel from commercial nuclear reactors. This notice amends a 30-day 
                        <E T="04">Federal Register</E>
                         notice published on February 20, 2026.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments on this information collection must be received no later than May 6, 2026. If you anticipate any difficulties in submitting comments by the deadline, contact the person listed in 
                        <E T="02">ADDRESSES</E>
                         section of this notice as soon as possible.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you need additional information, contact Debra Coaxum, EIA Clearance Officer, at (202) 586-7876. The current and proposed Form GC-859 and instructions are available on EIA's website at 
                        <E T="03">https://www.eia.gov/survey/#gc-859.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This information collection request contains</P>
                <P>
                    (1) 
                    <E T="03">OMB No.:</E>
                     1901-0287;
                </P>
                <P>
                    (2) 
                    <E T="03">Information Collection Request Title:</E>
                     Nuclear Fuel Data Survey;
                </P>
                <P>
                    (3) 
                    <E T="03">Type of Request:</E>
                     Three-year extension with changes;
                </P>
                <P>
                    (4) 
                    <E T="03">Purpose:</E>
                     This notice amends a 30-day 
                    <E T="04">Federal Register</E>
                     notice published on February 20, 2026 (91 FR 8212) by reinstating section C.2, Projected Assembly Discharges, and requiring reporting of at least three cycles to account for the five-year gap between survey collections.
                </P>
                <P>
                    The Nuclear Waste Policy Act of 1982 (42 U.S.C. 10101 
                    <E T="03">et seq.</E>
                    ) required that DOE enter into Standard Contracts with all generators or owners of spent nuclear fuel and high-level radioactive waste of domestic origin. Form GC-859 (formerly Form RW-859) originated from an appendix to this Standard Contract.
                </P>
                <P>
                    Form GC-859 
                    <E T="03">Nuclear Fuel Data Survey</E>
                     collects information on nuclear fuel use and spent fuel discharges from all utilities that operate commercial nuclear reactors and from all others that possess irradiated fuel from commercial nuclear reactors. The data collection provides stakeholders with detailed information concerning the spent nuclear fuel generated by the respondents (commercial utility generators of spent nuclear fuel and other owners of spent nuclear fuel within the U.S.).
                </P>
                <P>Data collected from the survey are used by personnel from DOE Office of Nuclear Energy (NE), DOE Office of Environmental Management (EM), and the national laboratories to meet their research objectives of developing a range of options and supporting analyses that facilitate informed choices about how best to manage spent nuclear fuel (SNF);</P>
                <P>
                    (4a) 
                    <E T="03">Proposed Changes to Information Collection:</E>
                </P>
                <P>• Clarified instructions, definitions, and tables based on the feedback received from the last survey collection. This lessens the burden on respondents by avoiding unnecessary need for clarifications.</P>
                <P>
                    • 
                    <E T="03">Section B.2:</E>
                     Reactor License Data. Section B.2 is being discontinued because the license status and other data is publicly available on the Nuclear Regulatory Commission's website. Section B.2 now indicates “Discontinued” to preserve the subsection numbering in Section B.
                </P>
                <P>
                    • 
                    <E T="03">Section C.1.1:</E>
                     Data on Discharged Fuel Assemblies and Non-Fuel Components Integral to the Assembly—Addition of an optional data field for Assembly-Average Initial Enrichment. The form currently includes a data field only for Maximum Planar-Average Initial Enrichment. Assembly-Average Initial Enrichment is critical for evaluating decay heat and dose rates, while Maximum Planar-Average Initial Enrichment accounts for axial and radial variations in enrichment, essential for criticality safety assessments. Having data for both enrichment values allows DOE to apply the appropriately conservative parameter to each discipline—maximum planar-average for criticality, assembly-average for shielding and thermal—thus reducing unnecessary 
                    <PRTPAGE P="17265"/>
                    conservativism and uncertainty while maintaining safety margins which enables DOE to have the information necessary for effective planning of future spent nuclear fuel transport and storage while maintaining compliance with thermal, radiological, and criticality safety requirements.
                </P>
                <P>
                    • 
                    <E T="03">Reinstating section C.2:</E>
                     Projected Assembly Discharges. DOE paused collection of projected assembly discharge data in section C.2 starting with the survey covering the July 1, 2013-December 31, 2017 period. However, reinstating this section is now necessary to provide insight on planned changes in reactor operations, particularly power uprates and the introduction of high-assay low-enriched uranium fuel. These developments will directly impact spent fuel characteristics, including enrichment levels and burnup rates. Section C.2 originally called for projections of discharged assemblies to be reported for five cycles. This has been reduced to three cycles as reporting a minimum of three cycles will be sufficient to cover the five-year gap in between survey collections. By collecting data on projected assembly discharges, DOE can ensure that it has the necessary information to manage and plan spent fuel storage, disposal strategies, and infrastructure investments in light of these anticipated changes. Section C.2 includes improvements for clarity of data requested, including an updated description and example of Projected Final Average Discharge Burnup of the Group.
                </P>
                <P>
                    • 
                    <E T="03">Non-Fuel Components (NFC).</E>
                     The 3 NFC columns in Table C.1.1 will be removed (NFC, NFC Identifier, and Estimated Total Weight) and added to the D.3.3 (Assemblies in Dry Storage) table. The NFC stored in the pool is already captured in Section E: Non-Fuel Data and the text was modified in E.2: Non-Fuel Components—Integral to an Assembly. This change was made to simplify the reporting of non-fuel components in the spent fuel pool. For these components, DOE does not require tracking of their current location in the spent fuel pool, only the tentative amount of hardware delivered to DOE. This reduces the burden on respondents by not requiring them to track and report the location of hardware components in the pool.
                </P>
                <P>
                    • 
                    <E T="03">D.3.3: Assemblies in Dry Storage.</E>
                     An additional column for Damaged Fuel Canister (DFC) will be added to the D.3.3 table. This eases the burden on respondents because this change improves clarity by avoiding confusion between a single assembly canister in section C.3.1 and a DFC reported in D.3.3. Additionally, it enhances clarity during canister unloading, ensuring it is clear which assemblies are damaged and whether additional hardware is present in the cask. This information is also used to verify compliance with the Certificate of Compliance when accepting the cask for transportation.
                </P>
                <P>
                    • 
                    <E T="03">Appendix C: Reactor and Spent Fuel Storage Site Identification Codes.</E>
                     Appendix C has been updated to remove numeric ID numbers for reactors or storage locations. These have been replaced with easily recognizable names, consistent with the choices in the web-application. Pools that no longer exist or that are no longer planned for storage have been removed from the list. Appendix C has been renamed to Reactor or Facility and Spent Fuel Storage Site. The form has been revised to remove references to numeric IDs, so the form now contains only user friendly, easily recognizable names.
                </P>
                <P>
                    • 
                    <E T="03">Appendix E: Fuel Assembly Type Codes.</E>
                     Appendix E has been modified to include codes submitted on the 2023 data collection that were not already on the list and to remove codes that are not in use, for the convenience of the respondents.
                </P>
                <P>
                    (5) 
                    <E T="03">Annual Estimated Number of Respondents:</E>
                     126;
                </P>
                <P>
                    (6) 
                    <E T="03">Annual Estimated Number of Total Responses:</E>
                     42;
                </P>
                <P>
                    (7) 
                    <E T="03">Annual Estimated Number of Burden Hours:</E>
                     3,707;
                </P>
                <P>
                    (8) 
                    <E T="03">Annual Estimated Reporting and Recordkeeping Cost Burden:</E>
                     The information is maintained in the normal course of business. The cost of the burden hours is estimated to be $352,128 (3,707 burden hours times $94.99 per hour). DOE estimates that respondents will have no additional costs associated with the surveys other than the burden hours and the maintenance of the information during the normal course of business.
                </P>
                <P>
                    <E T="03">Comments are invited on whether or not:</E>
                     (a) The proposed collection of information is necessary for the proper performance of agency functions, including whether the information will have a practical utility; (b) DOE's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used, is accurate; (c) DOE can improve the quality, utility, and clarity of the information it will collect; and (d) DOE can minimize the burden of the collection of information on respondents, such as automated collection techniques or other forms of information technology.
                </P>
                <P>
                    <E T="03">Statutory Authority:</E>
                     Section 13(b) of the Federal Energy Administration Act of 1974, Public Law 93-275, codified as 15 U.S.C. 772(b) and the DOE Organization Act of 1977, Public Law 95-91, codified at 42 U.S.C. 7101 
                    <E T="03">et seq.,</E>
                     The Nuclear Waste Policy Act of 1982 codified at 42 U.S.C. 10222 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on April 1, 2026.</DATED>
                    <NAME>Debra Coaxum,</NAME>
                    <TITLE>Acting Director, Office of Statistical Methods and Research, U.S. Energy Information Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06593 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">Department of Energy</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     PR26-48-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Gas Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 284.123(g) Rate Filing: Amended SOC for Blanket Certificate to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5299.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">§ 284.123(g) Protest:</E>
                     5 p.m. ET 6/1/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-704-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     El Paso Natural Gas Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rate Agreements Update (Pioneer April-June 2026) to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5246.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-705-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pine Needle LNG Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: 2026 Annual Fuel and Electric Power Tracker Filing to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5249.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-706-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Cheyenne Connector, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: CC 2026-03-31 Annual L&amp;U Report to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5271.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-707-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Trailblazer Pipeline Company LLC.
                    <PRTPAGE P="17266"/>
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TPC 2026-03-31 Fuel and L&amp;U Reimbursement and Power Cost Tracker to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5274.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-708-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Trailblazer Pipeline Company LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TPC 2026-03-31 Negotiated Rate Agreement Amendments to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5275.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-709-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     East Tennessee Natural Gas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: ETNG 2026 Annual EPC Filing to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5280.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-710-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Eastern Transmission, LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rates—Sequent 911825 &amp; 911941 &amp; 911942 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5282.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-711-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bison Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Company Use Gas Annual Report 2026 to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5303.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-712-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Ozark Gas Transmission, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Annual Fuel Use Report for 2025 of Ozark Gas Transmission, L.L.C. under RP26-712.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5306.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-713-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Great Lakes Gas Transmission Limited Partnership.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: GLGT April 1 2026 Negotiated Rate Agreements to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5323.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-714-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wyoming Interstate Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Bakken xPress Leased Capacity Implementation Compliance in Docket No. CP23-545 to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5325.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-715-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Northern Natural Gas Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: 20260331 Negotiated Rate Filing to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5328.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-716-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southern Star Central Gas Pipeline, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Vol. 2—Non-Conforming Discount and Neg Rate Agreements—Evergy and Tenaska to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5351.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-717-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wyoming Interstate Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Non Conforming Negotiated Rate Agreements (Hess_ONEOK) to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5387.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-718-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     El Paso Natural Gas Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rate Agreements Update and Housekeeping (Shell May-July 2026) to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5399.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-719-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Eastern Transmission, LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rates—Squarepoint NRAs eff 04.01.2026 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5410.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-720-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     WBI Energy Transmission, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: 2026 Negotiated Rate Non-Conforming Service Agreement Kentex (IT-839) to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5436.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-721-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Rockies Express Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: REX 2026-03-31 Negotiated Rate Agreements and Amendments to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5441.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-722-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alliance Pipeline L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Negotiated Rates—New NRA, one Release and GT&amp;C 34—2026-04-01 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5448.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-723-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wyoming Interstate Company, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Tariff Record Update Related to Transportation Service Agreements (Anadarko_NRG) to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5459.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-724-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Spotlight Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Petition for Limited Waiver of Capacity Release Regulations, et al. of Spotlight Energy, LLC under RP26-724.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5485.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-725-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Columbia Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: OTRA Summer 2026 to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5006.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-726-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hardy Storage Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: RAM 2026 to be effective 5/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5162.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-727-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Eastern Transmission, LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: TETLP Non-Conforming Agreements Filing eff 4-1-26 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5163.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-728-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Columbia Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: NR Agmts Citadel &amp; Sequent, Eff 4.1.26 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5188.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/13/26.
                </P>
                <P>
                    Any person desiring to intervene, to protest, or to answer a complaint in any 
                    <PRTPAGE P="17267"/>
                    of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.  The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED> Dated: April 1, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06634 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC25-99-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Burgess Biopower, LLC, White Mountain Power, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Notice of Non-Material Change in Circumstances of Burgess BioPower, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5560.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-81-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     AEP Generation Resources Inc., Wolf Hills Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of AEP Generation Resources Inc., et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260330-5432.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-82-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Indiana Michigan Power Company, Big Sandy Peaker Plant, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of Big Sandy Peaker Plant, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260330-5434.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 5/29/26.
                </P>
                <P>Take notice that the Commission received the following exempt wholesale generator filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG26-194-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     SR Quincy Valley, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     SR Quincy Valley, LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5369.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG26-195-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hornet Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Hornet Solar, LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5496.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG26-196-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     USS Hampden Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     USS Hampden Solar LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5525.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG26-197-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     USS Tallgrass Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     USS Tallgrass Solar LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5530.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-1781-009; ER10-1781-010; ER10-1781-012; ER10-1781-013; ER23-2321-005; ER23-2321-006; ER22-381-016; ER22-381-019; ER22-381-021; ER21-2715-009; ER21-2715-010; ER25-2081-000; ER25-1272-001; ER25-1272-002; ER21-714-012; ER21-714-013; ER21-714-015; ER21-714-016; ER22-399-007; ER22-399-008; ER22-399-010; ER22-399-011; ER19-2626-011; ER19-2626-012; ER19-2626-014; ER19-2626-015; ER22-381-015.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Rosewater Wind Farm LLC, Meadow Lake Solar Park LLC, Indiana Crossroads Wind Farm LLC, Gibson Solar, LLC, Fairbanks Solar Energy Center LLC, Dunns Bridge Solar Center, LLC, Dunns Bridge Energy Storage, LLC, Northern Indiana Public Service Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to 04/18/2025, and 01/29/2026, Notice of Non-Material Change in Status of Dunns Bridge Energy Storage, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260330-5429.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER14-1193-009.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     West Deptford Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Refund Report: Refund Report to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5299.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER16-915-010; ER13-291-011; ER10-2861-015; ER16-2520-008; ER16-612-004; ER10-2201-012; ER12-1308-018; ER15-1952-016; ER19-8-008; ER13-1504-016; ER17-318-008.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Three Peaks Power, LLC, SWG Arapahoe, LLC, Sweetwater Solar, LLC, Pavant Solar LLC, Palouse Wind, LLC, Marina Energy, LLC, Greeley Energy Facility, LLC, Grand View PV Solar Two LLC, Fountain Valley Power, L.L.C. EnergyMark, LLC, Comanche Solar PV, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Response to 12/31/2025, Deficiency Letter of Comanche Solar PV LLC et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260330-5430.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/20/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-588-001; ER18-1155-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Summer Energy Northeast, LLC, Horizon Power and Light, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to 02/20/2025, Notice of Non-Material Change in Status of Horizon Power and Light LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5557.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-895-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     BOCA bn, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to 01/30/2026, Notice of Change in Status of BOCA bn, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/27/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260327-5365.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/17/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-1335-004.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Elwood Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing of Tariff Record to Implement Settlement Rate to be effective 4/21/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5263.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-1335-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Elwood Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing of Tariff Records to Implement Settlement Rate to be effective 12/1/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5273.
                    <PRTPAGE P="17268"/>
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-1720-005; ER10-1838-017; ER19-2231-015; ER19-2232-015; ER18-552-012; ER24-762-009; ER10-1967-018; ER10-1968-017; ER22-2188-009; ER18-1150-015; ER17-2558-004; ER22-1402-012; ER22-1404-012; ER22-2713-010; ER26-862-002; ER10-1990-018; ER18-1821-017; ER10-1993-017.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Waymart Wind Farm, L.P., Walleye Power, LLC, Somerset Windpower, LLC, Prospect Power, LLC, Parkway Generation Sewaren Urban Renewal Entity LLC, Parkway Generation Operating LLC, Parkway Generation Keys Energy Center LLC,NTE Ohio, LLC, Trishe Wind Ohio, LLC, Northwest Ohio IA, LLC, Mill Run Windpower, LLC, Meyersdale Windpower LLC, Elevate Renewables F7, LLC, Clean Energy Future-Lordstown, LLC, Chief Keystone Power II, LLC, Chief Conemaugh Power II, LLC, Backbone Mountain Windpower, LLC, Alpha Generation, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Notice of Non-Material Change in Status of Alpha Generation, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/27/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260327-5366.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/17/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1256-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to Pending Original GIA No. 7809; Project Identifier No. AE2-283 to be effective 1/5/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5245.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1315-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to Filing of Original GIA No. 7841; Project Identifier No. AF2-081 to be effective 1/14/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5194.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1628-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 4654 Kay Wind Replacement GIA to be effective 2/23/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5016.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1773-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to Pending Filing of Original NSA 7943; Project Identifier No. AE2-285 to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5131.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1991-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hornet Solar LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Application for Market Based Rate Authority to be effective 5/15/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5417.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1992-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Entergy Arkansas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Chalk Bluff Solar LLC LBA Agreement to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5444.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1993-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Entergy Texas, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: SHECO LBA Agreement to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5452.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1994-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New England Power Pool Participants Committee.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Apr 2025 Membership Filing to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5454.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1995-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of New Mexico.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2026 Annual Real Power Loss Factor to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5000.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1996-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Campbell County Wind Farm 2, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Request for Limited and Prospective Waiver, et al. of Campbell County Wind Farm 2, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/31/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260331-5532.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/21/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1997-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PacifiCorp.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: UAMPS Construction Agreement—Brigham BTM (RS No. 808) to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5117.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1998-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 4697 Grand Reserve Energy GIA to be effective 3/5/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5119.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1999-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Entergy Services, LLC, Entergy Arkansas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Entergy Arkansas, LLC submits tariff filing per 35.13(a)(2)(iii: 2026-04-01_Entergy Companies Revisions Related to Order 898 to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5230.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2000-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc., Entergy Services, LLC, Entergy Arkansas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Entergy Arkansas, LLC submits tariff filing per 35.13(a)(2)(iii: 2026-04-01_Entergy OpCo Company Specific Attachment GG to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5235.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-2001-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to Rate Schedule FERC No. 32 to be effective 6/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260401-5323.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/22/26.
                </P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>
                    Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.  eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <PRTPAGE P="17269"/>
                    <DATED> Dated: April 1, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06636 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP25-547-000; Docket No. CP25-549-000]</DEPDOC>
                <SUBJECT>Gulf South Pipeline Company, LLC, Texas Gas Transmission, LLC; Notice of Availability of the Draft Environmental Impact Statement for the Proposed Kosciusko Junction Pipeline Project</SUBJECT>
                <P>Any person wishing to comment on the draft EIS may do so. To ensure consideration of your comments on the proposal in the final EIS, it is important that the Commission receive your comments on or before 5:00 p.m. Eastern Time on May 25, 2026. Instructions for filing comments are provided on page 4.</P>
                <P>
                    FERC is the lead federal agency for authorizing interstate natural gas transmission facilities under the Natural Gas Act of 1938 (NGA) and the lead federal agency for preparation of the draft EIS. The draft EIS assesses the potential environmental effects of the construction and operation of the Project in accordance with the requirements of the National Environmental Policy Act (NEPA) 
                    <SU>1</SU>
                    <FTREF/>
                     and the Commission's implementing regulations.
                    <SU>2</SU>
                    <FTREF/>
                     The principal purposes of the draft EIS are to: identify and assess the potential effects on the natural and human environment; describe and evaluate reasonable alternatives; identify and recommend mitigation measures; and facilitate public involvement in the environmental review process. The EIS concludes that approval of the proposed Project would have some limited adverse environmental effects; however, with implementation of the Applicants' avoidance, minimization, and mitigation measures, as well as adherence to Commission staff's mitigation measures recommended in the EIS, these effects would be less than significant.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         National Environmental Policy Act of 1969, as amended (Public Law [Pub. L.] 91-190. 42 USC 4321-4347, as amended by Pub. L. 94-52, July 3, 1975; Pub. L. 94-83, August 9, 1975; Pub. L. 97-258, 4(b), September 13, 1982; Pub. L. 118-5, June 3, 2023; Pub. L. 119-21, July 4, 2025).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 Code of Federal Regulations (CFR) 380.
                    </P>
                </FTNT>
                <P>The US Army Corps of Engineers, the US Environmental Protection Agency, and the US Fish and Wildlife Service participated as cooperating agencies in the preparation of the draft EIS. Cooperating agencies have jurisdiction by law or special expertise with respect to resources potentially affected by the proposal and participate in the NEPA analysis. Although the cooperating agencies provided input towards the conclusions and recommendations presented in the draft EIS, the agencies will present their own conclusions and recommendations in their respective records of decision (where applicable) for the Project.</P>
                <P>The draft EIS addresses the potential environmental effects of the abandonment, construction, modification, and operation of the following facilities in Mississippi.</P>
                <P>Texas Gas proposes to do the following:</P>
                <P>
                    • abandon by sale to Gulf South the existing Greenville Lateral (GL) and axillary and appurtenant facilities; 
                    <SU>3</SU>
                    <FTREF/>
                     and the existing Isola CS;
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The sale would include three 36-inch-diameter natural gas pipelines totaling 97.74 miles and one 0.37-mile 20-inch-diameter pipeline.
                    </P>
                </FTNT>
                <P>• install a new gas-fired compressor unit within the existing Greenville CS totaling 24,160 horsepower (hp); and</P>
                <P>• modify existing check meters within the Greenville CS to establish custody transfer measurement between Texas Gas and Gulf South.</P>
                <P>Gulf South proposes to do the following:</P>
                <P>• acquire the GL and Isola CS from Texas Gas;</P>
                <P>• install two new natural gas-fired compressor units totaling 24,615 hp at the Isola CS;</P>
                <P>• construct two new pipelines: the 8.1-mile-long, 36-inch-diameter Columbia Gulf Lateral and 102.9-mile-long, 36-inch-diameter Kosciusko Junction (KJ) Pipeline;</P>
                <P>• construct two new compressor stations: the Holmes CS with a natural gas-fired compressor unit totaling 23,984 hp along the existing GL, and the Kosciusko CS with three natural gas-fired compressor units totaling 61,293 hp along the new KJ Pipeline; and</P>
                <P>
                    • construct four new meter stations: the Columbia Gulf, Destin Check, SONAT, and Kosciusko Meter Stations; 
                    <SU>4</SU>
                    <FTREF/>
                     four mainline valves; and associated tie-ins, launcher/receiver facilities, and appurtenances.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Destin Check Meter Station would also require installation of about 50 feet of 36-inch-diameter interconnecting pipe to connect the KJ Pipeline.
                    </P>
                </FTNT>
                  
                <P>
                    The Commission mailed a copy of the 
                    <E T="03">Notice of Availability</E>
                     of the draft EIS to federal, state, and local government representatives and agencies; elected officials; environmental and public interest groups; Native American tribes; potentially affected landowners and other interested individuals and groups; and newspapers and libraries in the Project area. The draft EIS is only available in electronic format. It may be viewed and downloaded from the FERC's website (
                    <E T="03">www.ferc.gov</E>
                    ), on the natural gas environmental documents page (
                    <E T="03">https://www.ferc.gov/industries-data/natural-gas/environment/environmental-documents</E>
                    ). In addition, the draft EIS may be accessed by using the eLibrary link on the FERC's website. Click on the eLibrary link (
                    <E T="03">https://elibrary.ferc.gov/eLibrary/search</E>
                    ) select “General Search” and enter the docket number in the “Docket Number” field, excluding the last three digits (
                    <E T="03">i.e.,</E>
                     CP25-547 or CP25-549). Be sure you have selected an appropriate date range. For assistance, please contact FERC Online Support at 
                    <E T="03">FercOnlineSupport@ferc.gov</E>
                     or toll free at (866) 208-3676, or for TTY, contact (202) 502-8659.
                </P>
                <P>The draft EIS is not a decision document. It presents Commission staff's independent analysis of the environmental issues for the Commission to consider when addressing the merits of all issues in this proceeding. Under section 7(c) of the NGA, the Commission determines whether interstate natural gas transportation facilities are in the public convenience and necessity and, if so, grants a Certificate of Public Convenience and Necessity to construct and operate them. Section 7(b) of the NGA specifies that no natural gas company shall abandon any portion of its facilities subject to the Commission's jurisdiction without the Commission first finding that the abandonment will not negatively affect the present or future public convenience and necessity. The Commission bases its decisions on both economic issues, including need, and environmental effects.</P>
                <P>
                    Your comments should focus on draft EIS's disclosure and discussion of potential environmental effects, measures to avoid or lessen environmental effects, and the completeness of the submitted alternatives, information and analyses. In addition, landowner comments are encouraged on the site-specific construction plans that the Applicants developed for residences within 25 feet of construction work areas, available via 
                    <PRTPAGE P="17270"/>
                    FERC's eLibrary.
                    <SU>5</SU>
                    <FTREF/>
                     For your convenience, there are four methods you can use to submit your comments to the Commission. The Commission encourages electronic filing of comments and has staff available to assist you at (866) 208-3676 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                     Please carefully follow these instructions so that your comments are properly recorded.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The Applicants' Appendix 8G—Site-specific Residential Construction Plans, FERC Accession no. 20260116-5091. These plans are also included as appendix E of the EIS for this Project.
                    </P>
                </FTNT>
                <P>
                    (1) You can file your comments electronically using the eComment feature on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to FERC Online. This is an easy method for submitting brief, text-only comments on a project;
                </P>
                <P>
                    (2) You can file your comments electronically by using the eFiling feature on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to FERC Online. With eFiling, you can provide comments in a variety of formats by attaching them as a file with your submission. New eFiling users must first create an account by clicking on “eRegister.” If you are filing a comment on a particular project, please select “Comment on a Filing” as the filing type; or
                </P>
                <P>(3) You can file a paper copy of your comments by mailing them to the Commission. Be sure to reference the project docket number (CP25-547 or CP25-549) on your letter. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.</P>
                <P>(4) In lieu of sending written or electronic comments, the Commission invites you to attend one of the public comment sessions its staff will conduct in the Project area to receive comments on the draft EIS, scheduled as follows:</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date and time</CHED>
                        <CHED H="1">Location</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">April 28, 2026, 5:00 p.m. to 7:00 p.m. CDT</ENT>
                        <ENT>The Azalea, 707 Azalea Drive, Waynesboro, MS 39367.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 29, 2026, 5:00 p.m. to 7:00 p.m. CDT</ENT>
                        <ENT>MacMillan Park Center, 515 Hwy. 16 East, Carthage, MS 39051.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 30, 2026, 5:00 p.m. to 7:00 p.m. CDT</ENT>
                        <ENT>City Hall Multipurpose Building, 22521 Depot Street, Lexington, MS 39095.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The primary goal of these comment sessions is to have you identify the specific environmental issues and concerns with the draft EIS. Individual oral comments will be taken on a one-on-one basis with a court reporter. This format is designed to receive the maximum amount of comments, in a convenient way during the timeframe allotted.</P>
                <P>
                    Each comment session is scheduled from 5:00 p.m. to 7:00 p.m. (local time zone where meeting is held). You may arrive at any time after 5:00 p.m. There will not be a formal presentation by Commission staff when the session opens. If you wish to speak, the Commission staff will hand out numbers in the order of your arrival. Comments will be taken until 7:00 p.m. However, if no additional numbers have been handed out and all individuals who wish to provide comments have had an opportunity to do so, staff may conclude the session at 6:30 p.m. Please see appendix 1 for additional information on the session format and conduct.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The appendices referenced in this notice will not appear in the 
                        <E T="04">Federal Register</E>
                        . Copies of the appendices were sent to all those receiving this notice in the mail and are available at 
                        <E T="03">www.ferc.gov</E>
                         using the link called “eLibrary.” For assistance, contact FERC at 
                        <E T="03">FERCOnlineSupport@ferc.gov</E>
                         or call toll free, (866) 208-3676 or TTY (202) 502-8659.
                    </P>
                </FTNT>
                <P>Your oral comments will be recorded by the court reporter (with FERC staff or representative present) and become part of the public record for this proceeding. Transcripts will be publicly available on FERC's eLibrary system (see page 3 for instructions on using eLibrary). If a significant number of people are interested in providing oral comments in the one-on-one settings, a time limit of 5 minutes may be implemented for each commentor. Although there will not be a formal presentation, Commission staff will be available throughout the comment session to answer your questions about the environmental review process.</P>
                <P>It is important to note that the Commission provides equal consideration to all comments received, whether filed in written form or provided orally at a comment session.</P>
                <P>
                    Any person seeking to become a party to the proceeding must file a motion to intervene pursuant to Rule 214 of the Commission's Rules of Practice and Procedures (18 CFR part 385.214). Motions to intervene are more fully described at 
                    <E T="03">https://www.ferc.gov/how-intervene.</E>
                     Only intervenors have the right to seek rehearing or judicial review of the Commission's decision. Simply filing environmental comments will not give you intervenor status, but you do not need intervenor status to have your comments considered.
                </P>
                <HD SOURCE="HD1">Questions?</HD>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                     Additional information about the Project is available from the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ) using the eLibrary link. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription that allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. Go to 
                    <E T="03">https://www.ferc.gov/ferc-online/overview</E>
                     to register for eSubscription.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06635 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="17271"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 3407-088]</DEPDOC>
                <SUBJECT>Big Wood Canal Company; Notice of Application Accepted for Filing and Soliciting Motions To Intervene and Protests</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection.</P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     New Major License.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     P-3407-088.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     April 9, 2025.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Big Wood Canal Company.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Magic Dam Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located on the Big Wood River in Blaine and Camas Counties, Idaho. The project occupies federal land managed by the US Bureau of Land Management.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act 16 U.S.C. 791 (a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant's Authorized Agent:</E>
                     Peter Josten, 2742 Saint Charles Ave., Idaho Falls, ID 83404; telephone at (208) 339-3542; email at 
                    <E T="03">peter.gsense@gmail.com.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Ingrid Brofman, Project Coordinator, Northwest Branch, Division of Hydropower Licensing; telephone at (202) 502-8347; email at 
                    <E T="03">ingrid.brofman@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing motions to intervene and protests:</E>
                     on or before 5:00 p.m. Eastern Time on June 1, 2026.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Commission's Rules of Practice and Procedure provide that if a deadline falls on a Saturday, Sunday, holiday, or other day when the Commission is closed for business, the deadline does not end until the close of business on the next business day. 18 CFR 385.2007(a)(2). Because the 60-day filing deadline falls on Sunday (
                        <E T="03">i.e.,</E>
                         May 31, 2026), the filing deadline is extended until on or before 5:00 p.m. Eastern Time on Monday, June 1, 2026.
                    </P>
                </FTNT>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, motions to intervene, and protests using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 10,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, MD 20852. All filings must clearly identify the project name and docket number on the first page: Magic Dam Hydroelectric Project (P-3407-088).
                </P>
                <P>The Commission's Rules of Practice and Procedure require all interveners filing documents with the Commission to serve a copy of that document on each person on the official service list for the project. Further, if an intervener files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>k. This application has been accepted for filing, but is not ready for environmental analysis at this time.</P>
                <P>
                    l. 
                    <E T="03">Project Description:</E>
                     The existing project consists of: (1) a 3,100-foot-long dam comprised of an earth-filled section, a dike, and a concrete spillway section; (2) a 3,740-acre reservoir with a storage capacity of approximately 191,500 acre-feet at an elevation of 4,798 feet; (3) a 36.5-foot-high intake tower; (4) a 620-foot-long, 132-inch-diameter outlet conduit leading to a 170-foot-long, 132-inch-diameter penstock connecting to a powerhouse; (5) a powerhouse containing three generating units with a combined capacity of 9.0 megawatts; (6) a 9.2-mile-long, 4.16 kilovolt transmission line; and (7) appurtenant facilities. Big Wood Canal Company proposes to continue to operate the project in a run-of-release mode using flows that are seasonally released into the Big Wood River for irrigation.
                </P>
                <P>
                    m. A copy of the application is available for review via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ), using the “eLibrary” link. Enter the docket number, excluding the last three digits in the docket number field, to access the document.
                </P>
                <P>
                    You may also register online at 
                    <E T="03">https://ferconline.ferc.gov/FERCOnline.aspx</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll free, (886) 208-3676 or TTY (202) 502-8659.
                </P>
                <P>
                    n. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>o. Anyone may submit a protest or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, 385.211, and 385.214. In determining the appropriate action to take, the Commission will consider all protests filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any protests or motions to intervene must be received on or before the specified deadline date for the particular application.</P>
                <P>All filings must (1) bear in all capital letters the title “PROTEST” or “MOTION TO INTERVENE;” (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name of the person protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. Agencies may obtain copies of the application directly from the applicant. A copy of any protest or motion to intervene must be served upon each representative of the applicant specified in the particular application.</P>
                <P>When the application is ready for environmental analysis, the Commission will issue a public notice requesting comments, recommendations, terms and conditions, or prescriptions.</P>
                <P>
                    p. 
                    <E T="03">Procedural Schedule:</E>
                     The application will be processed according to the following schedule. Revisions to the schedule will be made as appropriate.
                </P>
                <FP SOURCE="FP-1">Issue Scoping Document Notice—May 2026</FP>
                <FP SOURCE="FP-1">Scoping Comments due—June 2026</FP>
                <FP SOURCE="FP-1">Issue Notice of Ready for Environmental Analysis—September 2026</FP>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: April 1, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06637 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="17272"/>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OW-2008-0150; FRL-13241-01-OW]</DEPDOC>
                <SUBJECT>Proposed Information Collection Request; Comment Request; Establishing No-Discharge Zones (NDZs) Under Clean Water Act Section 312 (Renewal)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency (EPA) is planning to submit an information collection request (ICR), Establishing No-Discharge Zones (NDZs) Under Clean Water Act Section 312 (Renewal) (EPA ICR Number 1937.10, OMB Control Number 2040-0187) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act (PRA). Before doing so, EPA is soliciting public comments on specific aspects of the proposed information collection as described below. This is a proposed extension of the ICR, which is currently approved through September 30, 2026. This notice allows for 60 days for public comments.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, referencing Docket ID Number EPA-HQ-OW-2008-0150, to EPA online using 
                        <E T="03">www.regulations.gov</E>
                         (our preferred method) or by mail to: EPA Docket Center, Environmental Protection Agency, Mail Code 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460. EPA's policy is that all comments received will be included in the public docket without change including any personal information provided, unless the comment includes profanity, threats, information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Catherine Brady, Oceans, Wetlands and Communities Division, Office of Wetlands, Oceans and Watersheds, 4504T, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460; telephone number: 202-566-2424; email address: 
                        <E T="03">brady.catherine@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a proposed extension of the ICR, which is currently approved through September 30, 2026. An agency may not conduct, or sponsor and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    This notice allows 60 days for public comments. Supporting documents, which explain in detail the information that the EPA will be collecting, are available in the public docket for this ICR. The docket can be viewed online at 
                    <E T="03">www.regulations.gov</E>
                     or in person at the EPA Docket Center, WJC West, Room 3334, 1301 Constitution Ave. NW, Washington, DC. The telephone number for the Docket Center is 202-566-1744. For additional information about EPA's public docket, visit 
                    <E T="03">http://www.epa.gov/dockets.</E>
                </P>
                <P>
                    Pursuant to section 3506(c)(2)(A) of the PRA, EPA is soliciting comments and information to enable it to: (i) evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility; (ii) evaluate the accuracy of the Agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (iii) enhance the quality, utility, and clarity of the information to be collected; and (iv) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate forms of information technology. EPA will consider the comments received and amend the ICR as appropriate. The final ICR package will then be submitted to OMB for review and approval. At that time, EPA will issue another 
                    <E T="04">Federal Register</E>
                     notice to announce the submission of the ICR to OMB and the opportunity to submit additional comments to OMB.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Pursuant to Clean Water Act (CWA) section 312, states are authorized to petition EPA for more stringent requirements to apply within state waters for sewage discharges from all vessels, as well as certain discharges from vessels of the Armed Forces.
                </P>
                <P>
                    (A) 
                    <E T="03">Sewage No-Discharge Zones:</E>
                     CWA section 312(f) and the implementing regulations in 40 CFR part 140 identify the information that must be included in a state's application to EPA to establish a no-discharge zone (NDZ) for vessel sewage for some or all of the state's waters. In designated vessel sewage NDZs, the discharge of both treated and untreated sewage from vessels is prohibited.
                </P>
                <P>
                    (B) 
                    <E T="03">Uniform National Discharge Standards NDZs and Review of Discharge Determination or Standards:</E>
                     CWA section 312(n), the Uniform National Discharge Standards (UNDS), requires EPA and the Department of War to establish uniform national discharge standards to control discharges incidental to the normal operation of a vessel of the Armed Forces. CWA section 312(n)(7) and the implementing regulations in 40 CFR part 1700 identify the information that a state must submit to EPA in the state's application to establish an NDZ for one or more UNDS discharges. A state may seek an NDZ designation for any UNDS discharge for which EPA and the Department of War have promulgated national standards of performance and corresponding implementing regulations, respectively. Additionally, CWA section 312(n)(5) provides that the governor of any state may petition EPA and the Department of War to review any discharge determination or standard promulgated under CWA section 312(n) if there is significant new information that could reasonably result in a change to the discharge determination or standard.
                </P>
                <P>The proposed collection of information is intended to capture the burden on state respondents to develop petitions that include the required information, as well as the burden on EPA to review the petitions. This ICR is necessary to fulfill EPA's obligations under the statute to receive and respond to state petitions; however, development and submission of a petition by a state is not required. Instead, a state must develop and submit a petition only when the state wishes to designate an NDZ either for sewage or for an UNDS discharge, or to request a review of an UNDS discharge determination or standard. The information collection activities discussed in this ICR do not require the submission of any confidential information.</P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents/affected entities:</E>
                     States.
                </P>
                <P>
                    <E T="03">Respondent's obligation to respond:</E>
                     Responses to this collection of information are required to obtain the benefit of a vessel sewage NDZ (CWA section 312(f)), an UNDS NDZ (CWA section 312(n)(7)(A)-(B)) or a review of an UNDS discharge determination or standard (CWA section 312(n)(5)(D)).
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     8 (total).
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     One time.
                </P>
                <P>
                    <E T="03">Total estimated burden:</E>
                     408 hours (per year). Burden is defined at 5 CFR 1320.03(b).
                </P>
                <P>
                    <E T="03">Total estimated cost:</E>
                     $28,910 (per year), which includes $400 annualized capital or operation &amp; maintenance costs.
                </P>
                <P>
                    <E T="03">Changes in the Estimates:</E>
                     There is a decrease of 169 hours in the total estimated respondent burden compared with the ICR currently approved by 
                    <PRTPAGE P="17273"/>
                    OMB. This decrease is due to an adjustment to the number of petitions EPA expects to receive pursuant to CWA section 312(f), as EPA overestimated in the last renewal. The current estimate is also informed by information available to EPA regarding the number of states that are considering, or are in the process of, developing petitions.
                </P>
                <SIG>
                    <NAME>Brian Frazer,</NAME>
                    <TITLE>Director, Office of Wetlands, Oceans and Watersheds. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06588 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPP-2025-0027; FRL-13244-01-OCSPP]</DEPDOC>
                <SUBJECT>Deaf Access Solutions, Inc.; Access to Confidential Business Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces that pesticide related information submitted to EPA's Office of Pesticide Programs (OPP) pursuant to the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA) and the Federal Food, Drug, and Cosmetic Act (FFDCA), including information that may have been claimed as Confidential Business Information (CBI) by the submitted, will provide access to Deaf Access Solutions, Inc., in accordance with the CBI regulations. Deaf Access Solutions, Inc. has been awarded a contract to perform interpreting services to the deaf and hard-of-hearing (D/HH) OPP staff and access to this information will enable Deaf Access Solutions, IInc.to fulfill the obligations of the contract.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Deaf Access Solutions, Inc., will be given access to this information no sooner than 5 days after date of publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Aida Abdul-wali, Office of Mission Critical Operations (66210MM), Office of Chemical Safety and Pollution Prevention, Environmental Protection Agency, 1200 Pennsylvania Avenue NW, Washington, DC 20460; telephone number: 202-566-9988; email address: 
                        <E T="03">Abdul-wali.Aida@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action applies to the public in general. As such, the Agency has not attempted to describe all the specific entities that may be affected by this action.</P>
                <HD SOURCE="HD2">B. How can I get copies of this document and other related information?</HD>
                <P>
                    EPA has established a docket for this action under Docket ID No. EPA-HQ-OPP-2025-0027. Publicly available docket materials are available either electronically through 
                    <E T="03">www.regulations.gov</E>
                     or in hard copy at the EPA Docket Center, West William Jefferson Clinton Bldg., Room 3334, 1301 Constitution Ave. NW, Washington, DC. The Docket Center's hours of operations are 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the OPP Docket is (703) 305-5805. Please review the visitor instructions and additional information about the docket available at 
                    <E T="03">https://www.epa.gov/dockets.</E>
                </P>
                <HD SOURCE="HD1">II. Contractor Requirements</HD>
                <P>Under GSA/FEDSIM solicitation number GS-10F-0168X, task order number 68HERF26F0012, contractor Deaf Access Solutions, Inc. of 6900 Wisconsin Ave. #31111, Bethesda, MD, is assisting OPP by attending meetings discussing FIFRA and FFDCA CBI and interpreting for staff requiring American Sign Language (ASL) interpretation. The contractors are American Sign Language interpreters.</P>
                <P>In accordance with 40 CFR 2.307(h)(3), EPA has determined that disclosure of CBI submitted to EPA under all sections of FIFRA and the FFDCA is necessary in order for Deaf Access Solutions, Inc. to carry out the work required by the contract. Deaf Access Solutions, Inc., personnel will be given access to information submitted to EPA under all sections of FIFRA and the FFDCA. Some of the information may be claimed or determined to be CBI.</P>
                <P>EPA is issuing this notice to inform all submitters of information under all sections of FIFRA and the FFDCA that EPA has provided Deaf Access Solutions, Inc.-access to these CBI materials on a need-to-know basis only. All access to FIFRA and FFDCA CBI under this contract takes place for all EPA Headquarters Deaf/Hard of Hearing employees in accordance with EPA's FIFRA CBI Protection Manual.</P>
                <P>Access to FIFRA and FFDCA data, including CBI, will continue until December 31, 2030. If the contract is extended, this access will also continue for the duration of the extended contract without further notice. In accordance with the requirements of 40 CFR 2.307(h)(3), the contract prohibits use of the information for any purpose not specified in the contract and prohibits disclosure of the information to a third party without prior written approval from the Agency. No information will be provided to Deaf Access Solutions, Inc., until the requirements in this document have been fully satisfied. Deaf Access Solutions, Inc.'s personnel will sign nondisclosure agreements and will be briefed on appropriate security procedures before they are permitted access to FIFRA CBI. Records of information provided to Deaf Access Solutions, Inc., will be maintained by EPA project officers for this contract. All information supplied to Deaf Access Solutions, Inc., by EPA, for use in connection with the contract will be returned to EPA when Deaf Access Solutions, Inc., has completed its work.</P>
                <P>
                    <E T="03">Authority:</E>
                     7 U.S.C. 136 
                    <E T="03">et seq.;</E>
                     21 U.S.C. 301 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 25, 2026.</DATED>
                    <NAME>Randolph L. Hill,</NAME>
                    <TITLE>Associate General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06585 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPPT-2003-0004; FRL-13240-01-OCSPP]</DEPDOC>
                <SUBJECT>Access to Confidential Business Information: Deaf Access Solutions, Inc.</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>EPA has authorized its contractor, Deaf Access Solutions, Inc. of Bethesda, MD, to access information which has been submitted to EPA under all sections of the Toxic Substances Control Act (TSCA). Some of the information may be claimed or determined to be Confidential Business Information (CBI).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Access to the confidential data will occur no sooner than April 13, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">For technical information contact:</E>
                         Warren Fortune, AO-OCRA-AD, 1200 Pennsylvania Avenue NW, 6416AA—WJC Building East, Washington, DC 20460; telephone number: (202) 566-0921; email address: 
                        <E T="03">fortune.warren@epa.gov.</E>
                    </P>
                    <P>
                        <E T="03">For general information contact: TSCA-hotline@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">
                    SUPPLEMENTARY INFORMATION:
                    <PRTPAGE P="17274"/>
                </HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action is directed to the public in general. This action may, however, be of interest to all who manufacture, process, or distribute industrial chemicals. Since other entities may also be interested, the Agency has not attempted to describe all the specific entities that may be affected by this action.</P>
                <HD SOURCE="HD2">B. How can I get copies of this document and other related information?</HD>
                <P>
                    The docket for this action, identified by docket identification (ID) number EPA-HQ-OPPT-2003-0004, is available online at 
                    <E T="03">http://www.regulations.gov.</E>
                     Additional information about dockets generally, along with instructions for visiting the docket in person, is available at 
                    <E T="03">https://www.epa.gov/dockets.</E>
                </P>
                <HD SOURCE="HD1">II. What action is the Agency taking?</HD>
                <P>Under GSA/FEDSIM solicitation number GS-10F-0168X, task order number 68HERF26F0012, contractor Deaf Access Solutions, Inc. of 6900 Wisconsin Ave., #31111, Bethesda, MD, is assisting the OCSPP by attending meetings, including meets discussing TSCA CBI, in order to interpret for staff requiring American Sign Language (ASL) interpretation. The contractors are American Sign Language interpreters.</P>
                <P>In accordance with 40 CFR 2.306(j), EPA has determined that under GSA/FEDSIM solicitation number GS-10F-0168X, task order number 68HERF26F0012, Deaf Access Solutions, Inc. required access to CBI submitted to EPA under all sections of TSCA to perform successfully the duties specified under the contract. Deaf Access Solutions, Inc. personnel are given access to information submitted to EPA under all sections of TSCA. Some of the information may be claimed or determined to be CBI.</P>
                <P>EPA is issuing this notice to inform all submitters of information under all sections of TSCA that EPA has provided Access Interpreting, Inc., access to these CBI materials on a need-to-know basis only. All access to TSCA CBI under this contract covers support for all EPA Headquarters Deaf/Hard of Hearing employees in discussions of CBI material in accordance with EPA's TSCA CBI Protection Manual.</P>
                <P>Access to TSCA data, including CBI, will continue until December 31, 2030. If the contract is extended, this access will also continue for the duration of the extended contract without further notice.</P>
                <P>Deaf Access Solutions, Inc.'s personnel have signed nondisclosure agreements and were briefed on appropriate security procedures before they were permitted access to TSCA CBI.</P>
                <P>
                    <E T="03">Authority:</E>
                     15 U.S.C. 2601 
                    <E T="03">et seq.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 30, 2026.</DATED>
                    <NAME>Douglas M. Troutman,</NAME>
                    <TITLE>Assistant Administrator, Office of Chemical Safety and Pollution Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06586 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-0589; FR ID 339063]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written PRA comments should be submitted on or before June 5, 2026. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Nicole Ongele, FCC, via email 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">nicole.ongele@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Nicole Ongele, (202) 418-2991.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid Office of Management and Budget (OMB) control number.</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0589.
                </P>
                <P>
                    <E T="03">Title:</E>
                     FCC Remittance Advice Forms, FCC Form 159/159-C, 159-B, 159-E, and 159-W.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     FCC Form 159 Remittance Advice, 159-C Remittance Advice Continuation Sheet, 159-B Remittance Advice Bill for Collection, 159-E Remittance Voucher, and 159-W Interstate Telephone Service Provider Worksheet.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit entities; Individuals or households; Not-for-profit institutions; and State, Local, or Tribal Governments.
                </P>
                <P>
                    <E T="03">Number of Respondent and Responses:</E>
                     238,044 respondents; 238,044 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     15 minutes (0.25 hours).
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion and annual reporting requirements; third party disclosure requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory Authority for this information collection is contained in the Communications Act of 1934, as amended; Section 8 (47 U.S.C. 158) for Application Fees; Section 9 (47 U.S.C. 159) for Regulatory Fees; Section 309(j) for Auction Fees; and the Debt Collection Improvement Act of 1996, Public Law 104-134, Chapter 10, Section 31001.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     59,511 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     None.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The FCC supports a series of remittance advice forms and a remittance voucher form that may be submitted in lieu of a remittance advice form when entities or individuals electronically submit a payment. A remittance advice form (or a remittance voucher form in lieu of an advice form) must accompany any payment to the Federal Communications Commission (
                    <E T="03">e.g.</E>
                     payments for regulatory fees, application filing fees, auctions, fines, forfeitures, Freedom of Information Act (FOIA) billings, or any other debt due to the FCC. Information is collected on these forms to ensure credit for full payment, to ensure entities and individuals receive any refunds due, to 
                    <PRTPAGE P="17275"/>
                    service public inquiries, and to comply with the Debt Collection Improvement Act of 1996. On August 12, 2013, the Commission released a Report and Order (R&amp;O), In the Matter Assessment and Collection of Regulatory Fee for Fiscal Year 2013 and Procedures for Assessment and Collection of Regulatory Fees, MD Docket Nos. 13-140 and 12-201, FCC 13-110. In this R&amp;O, the Commission requires that beginning in FY 2014, all regulatory fee payments be made electronically and that the Commission will no longer mail out initial regulatory fee assessments to CMRS providers.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Aleta Bowers,</NAME>
                    <TITLE>Federal Register Liaison Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06656 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[PSHSB &amp; OET: PS Docket No. 26-72; DA 26-294; FR ID 339368]</DEPDOC>
                <SUBJECT>Seeking Comment on Prohibiting Importation and Marketing of Previously Authorized Covered Communications Equipment Added to the Covered List in 2024 or Earlier</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Public Safety and Homeland Security Bureau (PSHSB) and the Office of Engineering and Technology (OET) seek comment on proposing to prohibit the continued importation and marketing of certain previously authorized equipment that has been determined to pose an unacceptable risk to the national security of the United States or the security and safety of United States persons. Through Public Notice, acting pursuant to § 2.939 of the Federal Communications Commission's rules, PSHSB and OET propose to apply such prohibitions to communications equipment added to the Covered List in 2024 or earlier.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are due on or before May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments on or before the dates indicated on the first page of this document. You may submit comments, identified by PS Docket No. 26-72, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Communications Commission's Website: https://www.fcc.gov/ecfs.</E>
                         Follow the instructions for submitting comments. 
                        <E T="03">Electronic Filers:</E>
                         Comments may be filed electronically using the internet by accessing the ECFS: 
                        <E T="03">https://www.fcc.gov/ecfs.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Paper Filers:</E>
                         Parties who choose to file by paper must file an original and one copy of each filing.
                    </P>
                    <P>
                        • Filings can be sent by hand or messenger delivery, by commercial courier, or by the U.S. Postal Service. 
                        <E T="03">All filings must be addressed to the Secretary, Federal Communications Commission.</E>
                    </P>
                    <P>• Hand-delivered or messenger-delivered paper filings for the Commission's Secretary are accepted between 8:00 a.m. and 4:00 p.m. by the FCC's mailing contractor at 9050 Junction Drive, Annapolis Junction, MD 20701. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of before entering the building.</P>
                    <P>• Commercial courier deliveries (any deliveries not by the U.S. Postal Service) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701.</P>
                    <P>• Filings sent by U.S. Postal Service First-Class Mail, Priority Mail, and Priority Mail Express must be sent to 45 L Street NE, Washington, DC 20554.</P>
                    <P>
                        • 
                        <E T="03">People With Disabilities:</E>
                         Contact the FCC to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by email: 
                        <E T="03">FCC504@fcc.gov</E>
                         or phone: 202-418-0530.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information, please contact Chris Smeenk at 202-418-1630 or 
                        <E T="03">Chris.Smeenk@fcc.gov,</E>
                         or Rebecca Clinton at 202-418-7815 or 
                        <E T="03">Rebecca.Clinton@fcc.gov,</E>
                         Attorney Advisors, Operations and Emergency Management Division, Public Safety and Homeland Security Bureau.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Public Notice released on March 27, 2026 in PS Docket No. 26-72, DA 26-294. The full text of this document is available at: 
                    <E T="03">https://docs.fcc.gov/public/attachments/DA-26-294A1.pdf.</E>
                </P>
                <P>
                    In October 2025, the Commission adopted the 
                    <E T="03">EA Security Second R&amp;O</E>
                     which established a procedure to limit the scope of an existing authorization of covered equipment to prohibit continued importation or marketing of such equipment, without revoking the underlying authorization. The Commission directed PSHSB and OET to “institute proceedings to determine whether to apply these prohibitions to some or all of the equipment currently on the Covered List” and it delegated authority to PSHSB and OET to apply such prohibitions pursuant to the framework and process outlined in the 
                    <E T="03">EA Security Second R&amp;O.</E>
                    <SU>1</SU>
                    <FTREF/>
                     Under § 2.939(e), PSHSB and OET “may place limitations on an existing authorization for covered equipment authorizations to prohibit continued importation or marketing” of such equipment.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">Id.</E>
                         at paras. 45, 48.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         47 CFR 2.939(e).
                    </P>
                </FTNT>
                <P>Through this Public Notice, the PSHSB and OET propose to prohibit the continued importation and marketing of equipment added to the Covered List in 2024 or earlier but was authorized before the adoption of our 2022 rules. We initially focus on this equipment because it has been on our Covered List for years. While importation and marketing would be prohibited, this prohibition would not affect continued use or operation of already-purchased communications equipment or equipment added to the Covered List after 2024. We seek comment on these proposals.</P>
                <P>Below we provide a brief analysis of the relevant factors, including national security and economic and supply chain considerations, that would justify prohibiting the continued importation and marketing of such previously authorized covered equipment and tentatively conclude that prohibiting the importation and marketing of this previously authorized covered equipment serves the public interest.</P>
                <P>
                    <E T="03">National security impacts.</E>
                     In the 
                    <E T="03">EA Security Second R&amp;O,</E>
                     the Commission stated that older models of covered equipment, which are still widely sold in the U.S., pose an unacceptable risk to national security when imported or marketed in the United States, “not only when such equipment is new to the market.” 
                    <SU>3</SU>
                    <FTREF/>
                     The Commission agreed with commenters who pointed out that certain previously authorized devices that are now considered covered equipment “likely remain marketable in the United States” and “may present continuing national security threats.” 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">EA Security 2d R&amp;O,</E>
                         FCC 25-71, para. 40.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    The Commission's initial, 2021 additions to the Covered List were pursuant to a specific national security determination made by Congress in Section 2(c) of the Secure and Trusted Communications Networks Act of 2019 (Secure Networks Act).
                    <SU>5</SU>
                    <FTREF/>
                     This directive constitutes a specific determination that such equipment poses an “unacceptable risk to the national security of the United States or the security and safety 
                    <PRTPAGE P="17276"/>
                    of United States persons.” 
                    <SU>6</SU>
                    <FTREF/>
                     Separately, the addition of “equipment with integrated Kaspersky Lab, (or any of its successors and assignees) cybersecurity or anti-virus software” was based on a specific determination by the Department of Commerce that “Kaspersky's provision of cybersecurity and anti-virus software to U.S. persons, including through third-party entities that integrate Kaspersky cybersecurity or anti-virus software into commercial hardware or software, poses undue and unacceptable risks to U.S. national security and to the security and safety of U.S. persons.” 
                    <SU>7</SU>
                    <FTREF/>
                     Accordingly, we tentatively conclude that prohibiting the continued importation and marketing of previously authorized equipment added at that time is necessary to protect national security by mitigating risks to the U.S. communications sector. We seek comment on this proposed analysis.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         47 U.S.C. 1601(c)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Protecting Against National Security Threats to the Communications Supply Chain Through FCC Programs,</E>
                         WC Docket No. 18-89, Second Report and Order, 35 FCC Rcd 14284, 14315-14316 (2020).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Department of Commerce, Final Determination, Case No. ICTS-2021-002, Kaspersky Lab, Inc., 89 FR 52434 (June 24, 2024) (Final Determination), 
                        <E T="03">https://www.federalregister.gov/documents/2024/06/24/2024-13532/final-determination-case-no-icts-2021-002-kaspersky-lab-inc.</E>
                    </P>
                </FTNT>
                <P>
                    <E T="03">Economic and supply chain impacts</E>
                    . We seek comment on the potential economic and supply chain impacts of prohibiting the continued importation and marketing of already-authorized covered equipment that was added to the Covered List in 2024 or earlier. How would this proposed action affect the financial interests of consumers, providers, and manufacturers in the communications sector?
                </P>
                <P>
                    We tentatively conclude that our proposed action would not have substantial economic and supply chain impacts. First, devices added to the Covered List as part of the Kaspersky listing in 2024 are already prohibited from importation or marketing under Department of Commerce rules.
                    <SU>8</SU>
                    <FTREF/>
                     Second, equipment added to the Covered List in the initial 2021 listing has not received authorization since November 11, 2022, over three years ago. Moreover, a significant amount of this equipment has been removed from U.S. communications networks in recent years.
                    <SU>9</SU>
                    <FTREF/>
                     Do commenters agree that economic and supply chain impacts are relatively minor?
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Final Determination at 52437.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Wireline Competition Bureau, Secure and Trusted Communications Networks Reimbursement Program Sixth Report (June 30, 2025), 
                        <E T="03">https://www.fcc.gov/document/supply-chain-reimbursement-program-sixth-report.</E>
                    </P>
                </FTNT>
                <P>
                    <E T="03">Other Considerations.</E>
                     We also note that certain equipment is only on the Covered List “to the extent it is used for the purpose of public safety, security of government facilities, physical security surveillance of critical infrastructure, and other national security purposes.” 
                    <SU>10</SU>
                    <FTREF/>
                     How, if at all, should we consider this use-based limitation on what qualifies as covered equipment? Should we exempt any equipment subject to this use-based limitation from any prohibition on importation and marketing? Or should we subject all such equipment to any prohibition?
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         See Covered List; 2019 NDAA.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Public interest analysis.</E>
                     We tentatively conclude that prohibiting the importation and marketing of previously authorized covered equipment that was added to the Covered List in 2024 or earlier is consistent with the public interest, because it protects American communications networks from devices specifically determined by Congress or a national security agency to “pose an unacceptable risk to the national security of the United States or the security and safety of United States persons.” 
                    <SU>11</SU>
                    <FTREF/>
                     We also tentatively conclude that there are no public interest factors that outweigh our tentative conclusion regarding the proposed ban on import and marketing of this previously equipment. We seek comment on this public interest analysis.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         47 U.S.C. 1601(b); 
                        <E T="03">see also EA Security R&amp;O and FNPRM,</E>
                         37 FCC Rcd at 13511-13513, paras. 40-43.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Existing authorizations.</E>
                     We clarify that, if this prohibition is adopted, the continued use or operation of covered equipment that is already in the hands of users would remain authorized.
                </P>
                <P>
                    <E T="03">Implementation timeline.</E>
                     We propose that all parties must cease all importation and marketing activities within 30 days of the effective date of the prohibition. We seek comment on the proposed timeline from the responsible parties and relevant manufacturers, importers, distributors, retailers, and other interested entities on such questions as the quantity of devices that have already been imported into the U.S. and are available for or being held for marketing or sale, new or recently updated device models that are en route to the U.S. or pending shipment, and devices that are subject to executed distribution, marketing, or sales agreements, but have not yet entered the supply chain. Should the Commission's prohibition on importation take immediate effect, while the marketing prohibition would take effect within 30 days, to avoid a rush to import new devices?
                </P>
                <P>
                    <E T="03">Permit-but-disclose proceeding.</E>
                     The proceeding this Public Notice initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's ex parte rules.
                    <SU>12</SU>
                    <FTREF/>
                     Persons making ex parte presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral ex parte presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the ex parte presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during ex parte meetings are deemed to be written ex parte presentations and must be filed consistent with rule 1.1206(b). In proceedings governed by rule 1.49(f) or for which the Commission has made available a method of electronic filing, written ex parte presentations and memoranda summarizing oral ex parte presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (
                    <E T="03">e.g.,</E>
                     .doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's ex parte rules.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         47 CFR. 1.1200 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Zenji Nakazawa,</NAME>
                    <TITLE>Chief, Public Safety and Homeland Security Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06653 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="17277"/>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1256; FR ID 339074]</DEPDOC>
                <SUBJECT>Information Collection Being Submitted for Review and Approval to Office of Management and Budget</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Pursuant to the Small Business Paperwork Relief Act of 2002, the FCC seeks specific comment on how it might further reduce the information collection burden for small business concerns with fewer than 25 employees. The Commission may not conduct or sponsor a collection of information unless it displays a currently valid Office of Management and Budget (OMB) control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments and recommendations for the proposed information collection should be submitted on or before May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be sent to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. Your comment must be submitted into 
                        <E T="03">www.reginfo.gov</E>
                         per the above instructions for it to be considered. In addition to submitting in 
                        <E T="03">www.reginfo.gov</E>
                         also send a copy of your comment on the proposed information collection to Nicole Ongele, FCC, via email to 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Nicole.Ongele@fcc.gov.</E>
                         Include in the comments the OMB control number as shown in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For additional information or copies of the information collection, contact Nicole Ongele at (202) 418-2991. To view a copy of this information collection request (ICR) submitted to OMB: (1) go to the web page 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain,</E>
                         (2) look for the section of the web page called “Currently Under Review,” (3) click on the downward-pointing arrow in the “Select Agency” box below the “Currently Under Review” heading, (4) select “Federal Communications Commission” from the list of agencies presented in the “Select Agency” box, (5) click the “Submit” button to the right of the “Select Agency” box, (6) when the list of FCC ICRs currently under review appears, look for the Title of this ICR and then click on the ICR Reference Number. A copy of the FCC submission to OMB will be displayed.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>As part of its continuing effort to reduce paperwork burdens, as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the FCC invited the general public and other Federal Agencies to take this opportunity to comment on the following information collection. Comments are requested concerning: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology. Pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), the FCC seeks specific comment on how it might further reduce the information collection burden for small business concerns with fewer than 25 employees.</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1256.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Connect America Fund Phase II and Rural Digital Opportunity Fund Auction Support.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, Not-for-profit institutions, and State, Local or Tribal governments.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     530 respondents and 530 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     2 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annual reporting requirements.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. Statutory authority for this information collection 47 U.S.C. 154, 214, 254 and 303(r) of the Communications Act of 1934, as amended.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     1,060 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No Cost.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                </P>
                <HD SOURCE="HD1">Connect America Fund Phase II Auction</HD>
                <P>The Commission is requesting the Office of Management and Budget (OMB) approval for this revised information collection. On November 18, 2011, the Commission released the USF/ICC Transformation Order and Further Notice of Proposed Rulemaking, WC Docket No. 10-90 et al., FCC 11-161 (USF/ICC Transformation Order and/or FNPRM), which comprehensively reformed and modernized the high-cost program within the universal service fund to focus support on networks capable of providing voice and broadband services. Among other things, the Commission created the CAF and concluded that support in price cap areas would be provided through a combination of “a new forward-looking model of the cost of constructing modern multi-purpose networks” and a competitive bidding process (CAF Phase II auction or Auction 903). The Commission also sought comment in the accompanying USF/ICC Transformation FNPRM on proposed rules governing the CAF Phase II auction, including basic auction design and the application process.</P>
                <P>
                    In the CAF Phase II auction, service providers competed to receive support of up to $1.98 billion over 10 years to offer voice and broadband service in unserved high-cost areas. The information collection requirements reported under this collection are the result of several Commission decisions to implement the reform adopted in the 
                    <E T="03">USF/ICC Transformation Order</E>
                     and move forward with conducting the CAF Phase II auction. In the 
                    <E T="03">April 2014 Connect America Order,</E>
                     WC Docket No. 10-90 et al., FCC 14-54, the Commission adopted various rules regarding participation in the CAF Phase II auction, the term of support, and the eligible telecommunications carrier (ETC) designation process. In the 
                    <E T="03">Phase II Auction Order,</E>
                     WC Docket No. 10-90 et al., FCC 16-64, the Commission adopted rules to govern the CAF Phase II auction, including the adoption of a two-stage application process, which includes a pre-auction short-form application to be submitted by parties interested in bidding in the CAF Phase II auction and a post-auction long-form application that must be submitted by winning bidders seeking to become authorized to receive CAF Phase II auction support. The Commission concluded, based on its experience with auctions and consistent 
                    <PRTPAGE P="17278"/>
                    with the record, that this two-stage application process balances the need to collect information essential to conducting a successful auction and authorizing CAF Phase II support with administrative efficiency.
                </P>
                <P>
                    On January 30, 2018, the Commission adopted a public notice that established the final procedures for the CAF Phase II auction, including the long-form application disclosure and certification requirements for winning bidders seeking to become authorized to receive CAF Phase II auction support. 
                    <E T="03">See Phase II Auction Procedures Public Notice,</E>
                     WC Docket No. 17-182 et al., FCC 18-6. The Commission also adopted the 
                    <E T="03">Phase II Auction Order on Reconsideration,</E>
                     WC Docket No. 10-90 et al., FCC 18-5, which modified the Commission's letter of credit rules to provide some additional relief for CAF Phase II auction support recipients by reducing the costs of maintaining a letter of credit. On January 19, 2023, WCB released a public notice announcing that the Commission had concluded its review of CAF Phase II auction long-form applications. 
                    <E T="03">See WCB Concludes CAF II Application Review, Long-Forms Made Public,</E>
                     AU Docket No. 17-182 et al., DA 23-49.
                </P>
                <P>The Commission eliminated the information collection requirements related to the CAF Phase II auction FCC Form 683 now that its review of CAF Phase II auction long-form applications has concluded.</P>
                <HD SOURCE="HD1">Rural Digital Opportunity Fund Auction</HD>
                <P>
                    On February 7, 2020 the Commission released the 
                    <E T="03">Rural Digital Opportunity Fund Order,</E>
                     WC Docket Nos. 19-126, 10-90, FCC 20-5 which will commit up to $20.4 billion over the next decade to support up to gigabit speed broadband networks in rural America. Funding was allocated through a multi-round, reverse, descending clock auction that favored faster services with lower latency and encouraged intermodal competition in order to ensure that the greatest possible number of Americans will be connected to the best possible networks, all at a competitive cost.
                </P>
                <P>To implement the Rural Digital Opportunity Fund auction (or Auction 904), the Commission adopted new rules for the Rural Digital Opportunity Fund auction, including the adoption of a two-stage application process. Like with the CAF Phase II auction, this process included a pre-auction short-form application submitted by parties interested in bidding in the Rural Digital Opportunity Fund auction (FCC Form 183) and a post-auction long-form application that must be submitted by winning bidders (or their designees) seeking to become authorized to receive Rural Digital Opportunity Fund support (FCC Form 683). The Commission received approval for the short-form application (FCC Form 183) in a separate collection under the OMB control number 3060-1252.</P>
                <P>
                    On September 30, 2025, the Commission adopted an order that conducted a comprehensive review of legacy requirements and determined that certain high-cost program rules no longer serve any operational purpose. 
                    <E T="03">Delete, Delete Delete; Removal of Obsolete Regulations;</E>
                     GN Docket No. 25-133, FCC 25-68 (rel. September 30, 2025) (
                    <E T="03">Delete, Delete, Delete</E>
                    ). This requested change results from the Commission's decision in that proceeding. The Commission determined that 47 CFR 54.315(a) and (b) and 47 CFR 54.804(a) and (b) are outdated and obsolete, and unnecessary because all associated proposals using FCC Form 683 have concluded.
                </P>
                <P>Therefore, the Commission proposes to remove the application requirement and retains only the limited ongoing requirements related to the annual maintenance of letters of credit under 47 CFR 54.315(c) CAF Phase II and 54.804(c) RDOF.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Aleta Bowers,</NAME>
                    <TITLE>Federal Register Liaison Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06655 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company; Correction</SUBJECT>
                <P>This corrects notice FR Doc. 2026-06545 scheduled to be published on April 3, 2026. In paragraph B. Federal Reserve Bank of Kansas City, entry 1. is corrected to read:</P>
                <P>
                    1. 
                    <E T="03">James N. Carson, Prairie Grove, Arkansas;</E>
                     to retain voting shares of Carson Financial Holding Company, Inc., and thereby indirectly retain voting shares of Carson Community Bank, both of Stilwell, Oklahoma.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Associate Secretary of the Board. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06643 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>
                <P>
                    The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.
                </P>
                <P>
                    The public portions of the applications listed below, as well as other related filings required by the Board, if any, are available for immediate inspection at the Federal Reserve Bank(s) indicated below and at the offices of the Board of Governors. This information may also be obtained on an expedited basis, upon request, by contacting the appropriate Federal Reserve Bank and from the Board's Freedom of Information Office at 
                    <E T="03">https://www.federalreserve.gov/foia/request.htm.</E>
                     Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)).
                </P>
                <P>Comments received are subject to public disclosure. In general, comments received will be made available without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure.</P>
                <P>Comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors, Benjamin W. McDonough, Secretary of the Board, 20th Street and Constitution Avenue NW, Washington, DC 20551-0001, not later than May 6, 2026.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Atlanta</E>
                     (Erien O. Terry, Assistant Vice President) 1000 Peachtree Street NE, Atlanta, Georgia 30309. Comments can also be sent electronically to 
                    <E T="03">Applications.Comments@atl.frb.org.</E>
                </P>
                <P>
                    1. 
                    <E T="03">Compass Sub Northwest, Inc., Birmingham, Alabama;</E>
                     to become a bank holding company by acquiring Green Dot Corporation, and thereby indirectly acquiring Green Dot Bank, both of Provo, Utah. In addition, Compass Sub North, Inc., Birmingham, Alabama, to become a bank holding 
                    <PRTPAGE P="17279"/>
                    company by acquiring Compass Sub Northwest, Inc., and by acquiring CommerceOne Financial Corporation and thereby indirectly acquiring CommerceOne Bank, both of Birmingham, Alabama. Compass Sub Northwest, Inc., and Compass Sub North, Inc., are currently subsidiaries of CommerceOne Financial Corporation, Birmingham, Alabama.
                </P>
                <P>
                    Finally, 
                    <E T="03">Compass Sub North, Inc.,</E>
                     to merge with CommerceOne Financial Corporation.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Associate Secretary of the Board. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06644 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <SUBJECT>Advisory Committee on Immunization Practices (ACIP); Notice of Charter Renewal</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of charter renewal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, in accordance with the Federal Advisory Committee Act of October 6, 1972, that the Advisory Committee on Immunization Practices (ACIP), Centers for Disease Control and Prevention, Department of Health and Human Services, has been renewed for a 2-year period through April 1, 2028.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        ACIP Secretariat, Advisory Committee on Immunization Practices, Centers for Disease Control and Prevention, 1600 Clifton Road NE, Mailstop H21-12, Atlanta, Georgia 30329-4027. Email: 
                        <E T="03">ACIP@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the Federal Advisory Committee Act, as amended, CDC is providing notice of the renewal of the charter of the Advisory Committee on Immunization Practices, Centers for Disease Control and Prevention, Department of Health and Human Services. This charter has been renewed for a two-year period through April 1, 2028.</P>
                <HD SOURCE="HD1">Public Interest Determination</HD>
                <P>Pursuant to 41 CFR 102-3.60(a), to establish, renew, reestablish, or merge a discretionary (agency discretion) advisory committee, an agency must first consult with the General Services Administration's Committee Management Secretariat (the Secretariat) and, as part of the consultation, provide a written public interest determination approved by the head of the agency to the Secretariat with a copy to the Office of Management and Budget. In addition, pursuant to 41 CFR 102-3.35, an agency shall follow the same consultation process and document in writing the same determination of need before creating a subcommittee under a discretionary committee that is not made up entirely of members of a parent advisory committee.</P>
                <P>Information on the following factors for the committee is provided to the Secretariat to demonstrate that renewing the committee is in the public interest:</P>
                <P>1. Annual budget: The ACIP's estimated annual costs for operating the Committee, including (i) Federal personnel and other Federal internal costs; (ii) proposed payments for up to 19 members; and (iii) reimbursable costs are as follows: a. Federal personnel on a full-time equivalent (FTE) basis, $940,313; b. Other Federal internal costs, $140,027; c. Proposed payments to members, $42,750; d. Proposed number of members: The anticipated number of members for ACIP is up to 19; e. Reimbursable costs, $83,106;</P>
                <P>2. If applicable, the total dollar value of grants expected to be recommended during the fiscal year, $0.</P>
                <P>3. Criteria for selecting members to ensure the committee has the necessary expertise and fairly balanced membership: Departmental policy provides that Committee membership be fairly balanced in terms of points of view represented, and the Committee's function. Consideration is also given to representation from diverse geographic areas and diverse viewpoints. Preference is given to candidates who are citizens of the United States. Aspects that are considered at the time of candidate screening and review for inclusion in nomination packages forwarded to the Secretary, DHHS, include:</P>
                <P>• Geographical balance. Efforts are made to ensure that voting members come from states representing a diversity of geographic locations within the U.S.</P>
                <P>
                    • Balance of specialty areas (
                    <E T="03">e.g.,</E>
                     biostatistics, toxicology, immunology, epidemiology, pediatrics, internal medicine, family medicine, nursing, consumer issues, state and local health department perspective, academic perspective, public health perspective, etc.).
                </P>
                <P>The ACIP Secretariat, including the DFO, solicits candidate names through the following channels:</P>
                <P>
                    • Procedures for application for ACIP membership are detailed on the ACIP website at 
                    <E T="03">https://www.cdc.gov/acip/membership/index.html.</E>
                     The ACIP Secretariat accepts applications as part of a continuous process throughout the year.
                </P>
                <P>
                    • Solicitation of potential candidates is posted annually in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>• Applications are solicited at ACIP meetings. A web link URL is provided on a meeting slide, and procedures for application are announced at the opening of meetings, which are broadcast via the internet (“webcast”) to an audience that can exceed 10,000 viewers.</P>
                <P>Members, including the Chair and Vice Chair, shall be selected and appointed by the HHS Secretary and shall be invited to serve for overlapping terms of up to four years, except that any member appointed to fill a vacancy for an unexpired term shall be appointed for the remainder of that term. A member may serve 180 days after the expiration of that member's term if a successor has not taken office.</P>
                <P>4. List of all other Federal advisory committees of the agency:</P>
                <FP SOURCE="FP-2">• Advisory Board on Radiation and Worker Health</FP>
                <FP SOURCE="FP-2">• Advisory Committee for the Elimination of Tuberculosis</FP>
                <FP SOURCE="FP-2">• Advisory Committee on Breast Cancer in Young Women</FP>
                <FP SOURCE="FP-2">• Advisory Committee to the Director, CDC</FP>
                <FP SOURCE="FP-2">• Board of Scientific Counselors, National Center for Injury Prevention and Control</FP>
                <FP SOURCE="FP-2">• Lead Exposure and Prevention Advisory Committee</FP>
                <FP SOURCE="FP-2">• Mine Safety and Health Research Advisory Committee</FP>
                <FP SOURCE="FP-2">• National Committee on Vital and Health Statistics</FP>
                <FP SOURCE="FP-2">• World Trade Center Health Program Scientific/Technical Advisory Committee</FP>
                <P>
                    5. Justification that the information or advice provided by the Federal advisory committee or subcommittee is not available from another Federal advisory committee, another Federal Government source, or any other more cost-effective and less burdensome source: The ACIP has been given statutory roles under subsections 1928(c)(2)(B)(i) and 1928(e) of the Social Security Act (42 U.S.C. 1396s(c)(2)(B)(i) and 1396s(e)) and subsection 2713(a)(2) of the Public Health Service Act (42 U.S.C. 300gg-13(a)(2)). In accordance with Section 
                    <PRTPAGE P="17280"/>
                    1928 of the Social Security Act, the ACIP shall establish and periodically review and, as appropriate, revise the list of vaccines for administration to children and adolescents eligible to receive vaccines through the Vaccines for Children Program, along with schedules regarding the appropriate dose and dosing interval, and contraindications to administration of the pediatric vaccines. The Secretary, and as delegated the CDC Director, shall use the list established by the ACIP for the purpose of the purchase, delivery, and administration of pediatric vaccines in the Vaccines for Children Program. Further, under provisions of the Affordable Care Act (Section 2713 of the Public Health Service Act, as amended), immunization recommendations of the Committee that have been adopted by the Director of the Centers for Disease Control and Prevention must be covered by applicable health plans. Therefore, the advice provided by the ACIP is not available from another Federal advisory committee or Federal Government source, or any other more cost-effective and less burdensome source.
                </P>
                <P>6. If the consultation is a committee renewal, a summary of the previous accomplishments of the committee and the reasons it needs to continue:</P>
                <P>
                    Summary of the previous accomplishments: Over the past two years, the Committee met over six times during calendar years 2024 and 2025. The Committee deliberated, offered recommendations, and/or revised over 15 recommendations during January 1, 2024, through December 31, 2025. The Committee also recommended updated child/adolescent and adult immunization schedules which CDC adopted and published in 2024 and 2025. Current information about ACIP activities can be found at: 
                    <E T="03">https://www.cdc.gov/acip/index.html</E>
                    .
                </P>
                <P>Reasons for the continuation: During the next two years, the ACIP is anticipated to work on and/or advise on the following initiatives:</P>
                <P>• convene new work groups as needed in response to new vaccine development, emerging evidence, and/or the review of existing vaccine-related data);</P>
                <P>• ensure publication of the child/adolescent and adult immunization schedules in professional society journals/websites, in addition to MMWR publication and posting on the CDC website;</P>
                <P>• continue to implement consistent procedures across the ACIP work groups;</P>
                <P>• continue to refine the evidence-based process for development of ACIP vaccine recommendations;</P>
                <P>• continue to improve processes to ensure transparency and opportunity for public comment during deliberations; and</P>
                <P>• conduct continuing education activities for ACIP members to enhance their understanding of the role of health economic evaluations, and the evidence-based recommendations process, in development of vaccine recommendations.</P>
                <P>7. Explanation of why the committee/subcommittee is essential to the conduct of agency business: The Secretary, Department of Health and Human Services (HHS), and by delegation the Director, Centers for Disease Control and Prevention (CDC), are authorized under Section 311 and Section 317 of the Public Health Service Act, [42 U.S.C. 243 and 42 U.S.C. 247b], as amended, to assist states and their political subdivisions in the prevention and control of communicable diseases; to advise the states on matters relating to the preservation and improvement of the public's health; and to make grants to states and, in consultation with the state health authorities, to agencies and political subdivisions of states to assist in meeting the costs of communicable disease control programs. Vaccines have played an important role in public health around the globe. The Advisory Committee on Immunization Practices (ACIP) provides recommendations to the Director of the Centers for Disease Control and Prevention (CDC) on the use of vaccines and immunization program strategies to inform individuals, clinicians, and broader public health efforts. This committee convenes scientific and medical experts to provide recommendations based on the best available evidence of vaccine risks and benefits, and efficacy. The ACIP shall provide advice and guidance to the CDC Director regarding use of vaccines and related agents for effective control of vaccine-preventable diseases and/or decrease symptomatology in the civilian population of the United States including identifying areas where additional data or evaluation would be useful to inform future recommendations. Recommendations made by the ACIP are initially reviewed by the CDC Director, and if adopted, become official CDC/HHS recommendations, and may be published in the Morbidity and Mortality Weekly Report (MMWR). The CDC Director informs the HHS Secretary, and Assistant Secretary for Health, of immunization recommendations provided by ACIP. Upon the licensure or authorization of any vaccine or any new indication for a vaccine, the Committee shall, as appropriate, consider the use of the vaccine at its next regularly scheduled meeting. If the Committee does not make a recommendation at the Committee's first regularly scheduled meeting, the Committee shall provide an update on the status of such for the Committee's review.</P>
                <P>In conclusion, this public interest determination documents that renewing the committee is in the public interest, essential to the conduct of agency business, and that the information to be obtained is not already available through another advisory committee or source within the Federal Government.</P>
                <P>
                    The Director, Office of Strategic Business Initiatives, Office of the Chief Operating Officer, Centers for Disease Control and Prevention, has been delegated the authority to sign 
                    <E T="04">Federal Register</E>
                     notices pertaining to announcements of meetings and other committee management activities, for both the Centers for Disease Control and Prevention and the Agency for Toxic Substances and Disease Registry.
                </P>
                <SIG>
                    <NAME>Kalwant Smagh,</NAME>
                    <TITLE>Director, Office of Strategic Business Initiatives, Office of the Chief Operating Officer, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06577 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-R-5]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Centers for Medicare &amp; Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. Under the Paperwork Reduction Act of 1995 (PRA), federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information (including each proposed extension or reinstatement of an existing collection of information) and to allow 60 days for public comment on the proposed action. Interested persons are invited to send comments regarding our burden estimates or any other aspect of this collection of information, including 
                        <PRTPAGE P="17281"/>
                        the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>When commenting, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in any one of the following ways:</P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may send your comments electronically to 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) that are accepting comments.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier: __/OMB Control Number: __, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.
                    </P>
                    <P>
                        To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, please access the CMS PRA website by copying and pasting the following web address into your web browser: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William N. Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Contents</HD>
                <P>
                    This notice sets out a summary of the use and burden associated with the following information collections. More detailed information can be found in each collection's supporting statement and associated materials (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <P>
                    Under the PRA (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA requires federal agencies to publish a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice.
                </P>
                <HD SOURCE="HD1">Information Collection</HD>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Physician Certifications/Recertifications in Skilled Nursing Facilities Manual Instruction; 
                    <E T="03">Use:</E>
                     Section 1814(a) of the Social Security Act (the Act) requires specific certifications in order for Medicare payments to be made for certain services. Before the enactment of the Omnibus Budget Reconciliation Act of 1989 (OBRA1989, Pub. L. 101-239), section 1814(a)(2) of the Act required that, in the case of posthospital extended care services, a physician certify that the services are or were required to be given because the individual needs or needed, on a daily basis, skilled nursing care (provided directly by or requiring the supervision of skilled nursing personnel) or other skilled rehabilitation services that, as a practical matter, can only be provided in a SNF on an inpatient basis.
                </P>
                <P>
                    The Medicare program requires, as a condition for Medicare Part A payment for posthospital skilled nursing facility (SNF) services, that a physician or other authorized practitioner must certify and periodically recertify that a beneficiary requires an SNF level of care. The physician certification and recertification is intended to ensure that the beneficiary's need for services has been established and then reviewed and updated at appropriate intervals. The documentation is a condition for Medicare Part A payment for post-hospital SNF care. 
                    <E T="03">Form Number:</E>
                     CMS-R-5 (OMB control number 0938-0454); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     Private Sector (Business or other for-profits); 
                    <E T="03">Number of Respondents:</E>
                     3,882,413; 
                    <E T="03">Number of Responses:</E>
                     3,882,413; 
                    <E T="03">Total Annual Hours:</E>
                     480,957. (For policy questions regarding this collection contact Patricia Taft at 410-786-4561).
                </P>
                <SIG>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06573 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <SUBJECT>Notice of Public Data Asset Release Under the Open, Public, Electronic, and Necessary (OPEN) Government Data Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with Title II of the Foundations for Evidence-Based Policymaking Act of 2018, known as the Open, Public, Electronic, and Necessary (OPEN) Government Data Act, CMS announces the forthcoming release of public data assets in open, machine-readable formats under an open license. These data are intended to support public engagement in identifying and preventing fraud, waste, and abuse, and to promote transparency and accountability. CMS has taken steps to ensure that the release of these data appropriately furthers transparency objectives consistent with the protection of sensitive information.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For questions regarding the data release, please send an email to 
                        <E T="03">data.support@cms.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The OPEN Government Data Act requires Federal agencies to make public data assets available in open formats and under open licenses, consistent with applicable law. CMS has advanced the release of provider prices and negotiated rates through its positions on provider price transparency, most recently promulgated through the Calendar Year 2026 Hospital Outpatient Prospective Payment System (OPPS) and Ambulatory Surgical Center Final Rule (CMS-1834-FC). CMS is committed to advancing transparency while ensuring compliance with all applicable legal requirements and privacy considerations governing the disclosure of Federal data.</P>
                <P>CMS has made available the following public data assets with utilization and payment data aggregated by provider and service:</P>
                <FP SOURCE="FP-1">• Original Medicare Physician &amp; Other Practitioners—By Provider and Service</FP>
                <FP SOURCE="FP-1">• Original Medicare Inpatient Hospitals—By Provider and Service</FP>
                <FP SOURCE="FP-1">• Original Medicare Outpatient Hospitals—By Provider and Service</FP>
                <FP SOURCE="FP-1">
                    • Medicare Part D Prescribers—By Provider and Drug
                    <PRTPAGE P="17282"/>
                </FP>
                <FP SOURCE="FP-1">• Original Medicare Durable Medical Equipment, Devices and Supplies (DMEPOS)—By Referring Provider and Service</FP>
                <FP SOURCE="FP-1">• Original Medicare Durable Medical Equipment, Devices and Supplies (DMEPOS)—By Supplier and Service</FP>
                <FP SOURCE="FP-1">• Medicaid Provider Spending—By Provider and Service (including aggregated managed care payment data elements, with disclosure avoidance techniques applied)</FP>
                <P>CMS has evaluated prior Agency statements and the disclosure of the datasets included in this notice consistent with applicable legal requirements. CMS considered applicable privacy protections under the Health Insurance Portability and Accountability Act of 1996, as amended by the Health Information Technology for Economic and Clinical Health Act, and relevant provisions of the 21st Century Cures Act. Where applicable, CMS also considered confidentiality requirements for substance use disorder information under 42 CFR part 2. Based on this assessment, CMS has determined that the datasets have been de-identified and appropriately limited to mitigate the risk of re-identification, do not disclose protected trade secret or confidential commercial information and are appropriate for public release.</P>
                <P>CMS will continue to evaluate additional datasets, as well as applicable governing laws and regulations, as it prepares future data releases.</P>
                <P>
                    The Administrator of the Centers for Medicare &amp; Medicaid Services (CMS), Mehmet Oz, having reviewed and approved this document, authorizes Vanessa Garcia, who is the Federal Register Liaison, to electronically sign this document for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Vanessa Garcia,</NAME>
                    <TITLE>Federal Register Liaison, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06618 Filed 4-2-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[CMS-5056-N2]</DEPDOC>
                <SUBJECT>Medicare Program; Delayed Implementation of Certain Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction (WISeR) Model</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces a delay in the implementation of two services from the list of Wasteful and Inappropriate Services Reduction (WISeR) model items and services.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The notice is effective April 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kate Blackwell (844) 711-2664, Option 8 or 
                        <E T="03">WISeR@cms.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    In the July 1, 2025, 
                    <E T="04">Federal Register</E>
                     (90 FR 28749), we published a notice titled “Medicare Program; Implementation of Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction (WISeR) Model”. The notice announced a 6-year model focused on reducing fraud, waste (including low-value care), and abuse in Medicare fee-for-service (FFS) via the implementation of technology-enabled prior authorization processes for select services. For more detailed information regarding the WISeR Model, see the July 2025 notice (90 FR 28749).
                </P>
                <HD SOURCE="HD1">II. Delayed Implementation of Select Services</HD>
                <P>
                    In the July 2025 notice (90 FR 28751), we specified that the prior authorization process under the model will be implemented in the selected states for the listed items and services with affiliated national coverage decisions (NCDs) or local coverage decisions (LCDs) beginning January 1, 2026. We are delaying implementation of two of the services announced in the July 2025 notice to allow additional time for operational readiness. Implementation of the prior authorization or pre-payment review process for these two services is delayed until a future date that will be announced in a subsequent 
                    <E T="04">Federal Register</E>
                     notice. Until the future implementation date is announced, neither the prior authorization nor the pre-payment review processes described in our earlier notice will be available for these services. The two services for which we are delaying implementation of the prior authorization or pre-payment review process are as follows:
                </P>
                <P>• Deep Brain Stimulation for Essential Tremor and Parkinson's Disease (NCD 160.24).</P>
                <P>• Percutaneous Image-Guided Lumbar Decompression for Spinal Stenosis (NCD 150.13).</P>
                <P>
                    The Administrator of the Centers for Medicare &amp; Medicaid Services (CMS), Dr. Mehmet Oz, having reviewed and approved this document, authorizes Chyana Woodyard, who is the Federal Register Liaison, to electronically sign this document for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Chyana Woodyard,</NAME>
                    <TITLE>Federal Register Liaison, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06616 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[CMS-5056-CN]</DEPDOC>
                <SUBJECT>Medicare Program; Implementation of Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction (WISeR) Model; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document corrects typographical and technical errors in the notice that appeared in the July 1, 2025, 
                        <E T="04">Federal Register</E>
                         titled “Medicare Program; Implementation of Prior Authorization for Select Services for the Wasteful and Inappropriate Services Reduction (WISeR) Model”.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The corrections in this notice are effective April 6, 2026.</P>
                    <P>
                        <E T="03">Applicability date:</E>
                         The corrections in section II.1.a. of this notice are applicable to the list of WISeR items and services and their affiliated local coverage determinations (LCDs) for which prior authorization and pre-payment review processes were implemented on January 1, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kate Blackwell (844) 711-2664, Option 8 or 
                        <E T="03">WISeR@cms.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">
                    SUPPLEMENTARY INFORMATION:
                    <PRTPAGE P="17283"/>
                </HD>
                <HD SOURCE="HD1">I. Background and Summary of Errors</HD>
                <P>In FR Doc. 2020-12195 of July 1, 2025 (90 FR 28749), there were typographical and technical errors. This document corrects those errors.</P>
                <HD SOURCE="HD1">II. Correction of Errors</HD>
                <P>In FR Doc. 2025-122195 of July 1, 2025 (90 FR 28749), make the following corrections:</P>
                <P>1. On page 28751,</P>
                <P>a. Second column,</P>
                <P>(1) Third bulleted paragraph, lines 1 through 5, the paragraph “• Epidural Steroid Injections for Pain Management excluding facet joint injections (L39015, L33906, L39036, L39240, L39242, L36920, L38994, L39054)” is corrected to read “• Epidural Steroid Injections for Pain Management (L39015, L39240, L36920) excluding Facet Joint Interventions”.</P>
                <P>(2) Fourth bulleted paragraph, lines 2 through 5, the phrase “Vertebral Compression Fracture (VCF) (L33569, L34106, L34228, L38201, L34976, L35130, L38737, L38213)” is corrected to read “Vertebral Compression Fracture (VCF) (L38201, L34228, L35130)”.</P>
                <P>(3) Fifth bulleted paragraph, lines 1 through 3, the phrase “Fusion (L39741, L39799, L39770, L39758, L39762, L39793, L39773, L39788)” is corrected to read “Fusion (L39741, L39758, L39793)”.</P>
                <P>(4) Seventh bulleted paragraph, lines 2 through 4, the phrase “Apnea (L38276, L38307, L38398, L38387, L38310, L38312, L38385, L38528)” is corrected to read “Apnea (L38307, L38310, L38385)”.</P>
                <P>(5) Eleventh bulleted paragraph, lines 1 through 4, the paragraph “• Skin and Tissue Substitutes (LCDs below)—only applicable to MAC jurisdictions and states that have an active LCD in place” is corrected to read “• Skin and Tissue Substitutes (LCDs below): Only applicable to selected WISeR MAC jurisdictions and states with an active LCD in place during the WISeR performance years starting on January 1, 2026.”</P>
                <P>b. Third column, first full paragraph, lines 23 and 24, the phrase “Additional information about the WISeR model is available” is corrected to read “Additional information about the WISeR model and the most current WISeR items and services and their affiliated NCDs and LCDs are available”.</P>
                <P>
                    The Administrator of the Centers for Medicare &amp; Medicaid Services (CMS), Dr. Mehmet Oz, having reviewed and approved this document, authorizes Chyana Woodyard, who is the Federal Register Liaison, to electronically sign this document for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Chyana Woodyard,</NAME>
                    <TITLE>Federal Register Liaison, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06617 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-416 and CMS-10628]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services, Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Centers for Medicare &amp; Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. Under the Paperwork Reduction Act of 1995 (PRA), federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, and to allow a second opportunity for public comment on the notice. Interested persons are invited to send comments regarding the burden estimate or any other aspect of this collection of information, including the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the collection(s) of information must be received by the OMB desk officer by May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                    <P>
                        To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, please access the CMS PRA website by copying and pasting the following web address into your web browser: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires federal agencies to publish a 30-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice that summarizes the following proposed collection(s) of information for public comment.
                </P>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Annual Early and Periodic Screening, Diagnostic and Treatment (EPSDT) Participation Report; 
                    <E T="03">Use:</E>
                     The collected baseline data is used to assess the effectiveness of state early and periodic screening, diagnostic and treatment (EPSDT) programs in reaching eligible children (by age group and basis of Medicaid eligibility) who are provided initial and periodic child health screening services, referred for corrective treatment, and receiving dental, hearing, and vision services. This assessment is coupled with the state's results in attaining the participation goals set for the state. The information gathered from this report permits federal and state managers to evaluate the effectiveness of the EPSDT law on the basic aspects of the program. 
                    <E T="03">Form Number:</E>
                     CMS-416 (OMB control number 0938-0354); 
                    <E T="03">Frequency:</E>
                     Yearly; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     56; 
                    <E T="03">Total Annual Responses:</E>
                     56; 
                    <E T="03">Total Annual Hours:</E>
                     1,128. (For policy questions regarding this collection 
                    <PRTPAGE P="17284"/>
                    contact Deirdra Stockmann at 410-786-2433.)
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Revision of a previously approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Initial Request for State Implemented Moratorium Form; 
                    <E T="03">Use:</E>
                     Congress has enacted section 1866 (j)(7) of the Social Security Act, which allows for the imposition of temporary moratorium. CMS promulgated 42 CFR 424.570 in order to comply with that statute, which requires that prior to implementing state Medicaid moratoria the state Medicaid agency must notify the Secretary in writing, including all of the details of the moratoria, and obtain the Secretary's concurrence with the imposition of the moratoria.
                </P>
                <P>
                    The Initial Request for State Medicaid Implemented Moratorium, named the “Initial Request for State Medicaid Implemented Moratorium” has been created to collect that data, in a uniform manner, which the states report to CMS when they request a moratorium. Currently, CMS is collecting this data on an ad-hoc basis, however this process needs to be standardized so that moratoria decisions are being made based on the same criteria each time. The form may be used by states and territories who wish to impose a Medicaid or Children's Health Insurance Program moratorium. CMS will use this information as a standardized method to collect and track state-imposed moratoria requests. 
                    <E T="03">Form number:</E>
                     CMS-10628 (OMB control number: 0938-1328); 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     5; 
                    <E T="03">Number of Responses:</E>
                     5; 
                    <E T="03">Total Burden Hours:</E>
                     25. (For questions regarding this collection contact Alisha Sanders at 410-786-0671).
                </P>
                <SIG>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Division of Information Collections and Regulatory Impacts, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06570 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2016-D-1280]</DEPDOC>
                <SUBJECT>Electronic Submission of Postmarketing Individual Case Safety Reports to the Food and Drug Administration Adverse Event Monitoring System Using International Council of Harmonisation E2B(R3) Data Standards; Regional Data Elements and Implementation Schedule</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or we) is announcing an updated data standard requirement for the submission of postmarketing individual case safety report (ICSR) submissions for human drug products, biological products, and drug- or biologic-led combination products to the FDA Adverse Event Monitoring System (AEMS) database (formerly FDA Adverse Event Reporting System (FAERS)) via the Electronic Submissions Gateway Next Generation (ESG NextGen). Starting October 1, 2026, postmarketing ICSRs must be reported using the data standards adopted by FDA in the International Council for Harmonisation (ICH) guidance for industry entitled “E2B(R3) Electronic Transmission of Individual Case Safety Reports (ICSRs) Implementation Guide—Data Elements and Message Specification” (ICH E2B(R3) Implementation Guidance), which incorporates by reference regional implementation guides (collectively ICH E2B(R3) data standards).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>For postmarketing ICSRs for human drug products, biological products, and drug- or biologic-led combination products submitted via ESG NextGen, beginning October 1, 2026, the ICSRs must be submitted to the AEMS database using ICH E2B(R3) data standards.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information concerning drug products and biological products regulated by the Center for Drug Evaluation and Research: Quocbao Pham, Center for Drug Evaluation and Research (HFD-430), Food and Drug Administration, 10903 New Hampshire Ave., Building 22, Rm. 4491, Silver Spring, MD 20993-0002, (301)-796-5384, 
                        <E T="03">aemsesub@fda.hhs.gov.</E>
                    </P>
                    <P>For information concerning biological products regulated by the Center for Biologics Evaluation and Research: Phillip Kurs, Center for Biologics Evaluation and Research, Food and Drug Administration, (240)-402-7911.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    FDA is announcing an updated data standard requirement for the submission of postmarketing ICSR submissions for human drug products, biological products, and drug- or biologic-led combination products to the AEMS database via the ESG NextGen. Starting October 1, 2026, postmarketing ICSR submissions for human drug products, biological products, and drug- and biologic-led combination products to the AEMS database via ESG NextGen must be reported using the data standards provided in the ICH E2B(R3) Implementation Guidance (available at 
                    <E T="03">https://www.fda.gov/media/81904/download</E>
                    ), which incorporates by reference the guidance for industry and technical specifications document entitled “FDA Regional Implementation Guide for E2B(R3) Electronic Transmission of Individual Case Safety Reports for Drug and Biological Products” (ICH E2B(R3) FDA Regional Implementation Guidance) (available at 
                    <E T="03">https://www.fda.gov/media/180748/download</E>
                    ). The ICH E2B(R3) Implementation Guidance and ICH E2B(R3) FDA Regional Implementation Guidance were issued to improve the quality of data in ICSR submissions and to enable improved handling and analyses of ICSRs. Differences between ICH E2B(R2) and ICH E2B(R3) include, for example: new, changed, and expanded data elements; assessment of seriousness at the event level, rather than the case level; and embedding of attachments in the ICSR rather than providing separately.
                </P>
                <P>
                    FDA postmarketing safety reporting regulations for human drug and biological products require that persons subject to mandatory postmarketing reporting requirements for human drug products, biological products, and drug- or biologic-led combination products submit ICSRs in an electronic format that FDA can process, review, and archive. See 21 CFR 4.102, 230.220(c)(1), 310.305(e)(1), 314.80(g)(1), 314.81(b)(3)(v)(F)(
                    <E T="03">1</E>
                    ), 314.98, 329.100(c)(1), and 600.80(h)(1). The regulations explain that FDA will issue guidance on how to provide the electronic submission of safety reports, including ICSRs and ICSR attachments.
                </P>
                <P>
                    In the guidance for industry entitled “Providing Submissions in Electronic Format—Postmarketing Safety Reports” (eSRR Guidance) (available at 
                    <E T="03">https://www.fda.gov/media/71176/download</E>
                    ), FDA provides two options for electronic 
                    <PRTPAGE P="17285"/>
                    submission of ICSRs and ICSR attachments to AEMS: (1) direct submission through the ESG NextGen, or (2) submission through the Safety Reporting Portal (SRP). The SRP enables submission of ICSRs and ICSR attachments by applicants, specified nonapplicants, and responsible persons for companies with reporting requirements who do not have ICH E2B(R3) data standards capability. This notice regarding the use of ICH E2B(R3) data standards applies only to submission of ICSRs and ICSR attachments through the ESG NextGen. The eSRR Guidance incorporates by reference the technical specifications described in the ICH E2B(R3) FDA Regional Implementation Guidance, which addresses topics such as data elements, electronic transport format, and types of ICSR attachments and is periodically updated. To ensure that you have the most recent version of the technical specifications document and for additional information on electronic submissions to AEMS, check the FDA Adverse Event Monitoring System (AEMS) Electronic Submissions web page at 
                    <E T="03">https://www.fda.gov/drugs/fda-adverse-event-monitoring-system-aems/fda-adverse-event-monitoring-system-aems-electronic-submissions.</E>
                </P>
                <P>
                    The technical specifications document entitled “Specifications for Preparing and Submitting Electronic ICSRs and ICSR Attachments” (available at 
                    <E T="03">https://www.fda.gov/media/132096/download</E>
                    ) discusses how ICSRs and ICSR attachments should be electronically prepared in accordance with the ICH E2B(R2) data standards, which are the data standards that FDA will continue to accept through September 30, 2026.
                </P>
                <P>In January 2024, FDA began accepting electronic submissions of postmarketing ICSRs for human drug products, biological products, and drug- or biologic-led combination products submitted to AEMS in electronic format using the ICH E2B(R3) data standards and announced that submitters could continue to submit using E2B(R2) standards for an additional two years during the E2B(R3) implementation period. To facilitate implementation and enhance efficiency and alignment with internationally harmonized data standards, FDA is requiring that ICSRs submitted through ESG NextGen must be in the ICH E2B(R3) data standards beginning on October 1, 2026, unless earlier transition to ICH E2B(R3) data standards is needed to accommodate reporting requirements (see, for example, 21 CFR 314.81(b)(3)(v), added by the final rule entitled “Nonprescription Drug Product With an Additional Condition for Nonprescription Use” (89 FR 105288, December 26, 2024)).</P>
                <P>
                    We intend to no longer accept postmarketing ICSRs using ICH E2B(R2) data standards for human drug products, biological products, and drug- or biologic-led combination products after September 30, 2026. Once an applicant, specified nonapplicant, or responsible person for a company with reporting requirements has begun submitting ICSRs in the ICH E2B(R3) data standards format, all ICSR submissions are expected to use this data standard. For general questions or assistance, see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     or contact 
                    <E T="03">aemsesub@fda.hhs.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 21 CFR 4.102, 230.220(c)(1), 310.305(e)(1), 314.80(g)(1), 314.81(b)(3)(v)(F)(1), 314.98, 329.100(c)(1), and 600.80(h)(1))</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06660 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2025-P-6868]</DEPDOC>
                <SUBJECT>Determination That STRATTERA (Atomoxetine Hydrochloride) Capsules 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams, Were Not Withdrawn From Sale for Reasons of Safety or Effectiveness</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or Agency) has determined that STRATTERA (atomoxetine hydrochloride) capsules 5 milligrams, 10 milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams, were not withdrawn from sale for reasons of safety or effectiveness. This determination means that FDA will not begin procedures to withdraw approval of abbreviated new drug applications (ANDAs) that refer to this drug product, and it will allow FDA to continue to approve ANDAs that refer to the product as long as they meet relevant legal and regulatory requirements.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rana Carroll, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6218, Silver Spring, MD 20993-0002, 301-796-6135, 
                        <E T="03">Rana.Carroll@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 505(j) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(j)) allows the submission of an ANDA to market a generic version of a previously approved drug product. To obtain approval, the ANDA applicant must show, among other things, that the generic drug product: (1) has the same active ingredient(s), dosage form, route of administration, strength, conditions of use, and (with certain exceptions) labeling as the listed drug, which is a version of the drug that was previously approved, and (2) is bioequivalent to the listed drug. ANDA applicants do not have to repeat the extensive clinical testing otherwise necessary to gain approval of a new drug application (NDA).</P>
                <P>Section 505(j)(7) of the FD&amp;C Act requires FDA to publish a list of all approved drugs. FDA publishes this list as part of the “Approved Drug Products With Therapeutic Equivalence Evaluations,” which is known generally as the “Orange Book.” Under FDA regulations, drugs are removed from the list if the Agency withdraws or suspends approval of the drug's NDA or ANDA for reasons of safety or effectiveness or if FDA determines that the listed drug was withdrawn from sale for reasons of safety or effectiveness (21 CFR 314.162).</P>
                <P>A person may petition the Agency to determine, or the Agency may determine on its own initiative, whether a listed drug was withdrawn from sale for reasons of safety or effectiveness. This determination may be made at any time after the drug has been withdrawn from sale, but must be made prior to approving an ANDA that refers to the listed drug (§ 314.161 (21 CFR 314.161)). FDA may not approve an ANDA that does not refer to a listed drug.</P>
                <P>STRATTERA (Atomoxetine Hydrochloride) Capsules 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams, is the subject of NDA 021411, held by Eli Lilly and Co, and initially approved on November 26, 2022. STRATTERA is indicated for the treatment of Attention-Deficit/Hyperactivity Disorder (ADHD).</P>
                <P>
                    In a letter dated August 5, 2025, Eli Lilly and Company notified FDA that STRATTERA (Atomoxetine 
                    <PRTPAGE P="17286"/>
                    Hydrochloride) Capsules 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligram, was being discontinued, and FDA moved the drug product to the “Discontinued Drug Product List” section of the Orange Book.
                </P>
                <P>Rosemont Pharmaceuticals Holdings, Inc submitted a citizen petition dated December 4, 2025 (Docket No. FDA-2025-P-6868), under 21 CFR 10.30, requesting that the Agency determine whether STRATTERA (Atomoxetine Hydrochloride) 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams capsules were withdrawn from sale for reasons of safety or effectiveness. Although the citizen petition did not address the 5 Milligrams strength, that strength has also been discontinued. On our own initiative, we have also determined whether that strength was withdrawn for safety or effectiveness reasons.</P>
                <P>After considering the citizen petition and reviewing Agency records and based on the information we have at this time, FDA has determined under § 314.161 that STRATTERA (Atomoxetine Hydrochloride) 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams capsules, were not withdrawn for reasons of safety or effectiveness. The petitioner has identified no data or other information suggesting that STRATTERA (Atomoxetine Hydrochloride) 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams capsules were withdrawn for reasons of safety or effectiveness. We have carefully reviewed our files for records concerning the withdrawal of STRATTERA (Atomoxetine Hydrochloride) 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams capsules, from sale. We have also independently evaluated relevant literature and data for possible postmarketing adverse events. We have reviewed the available evidence and determined that this drug product was not withdrawn from sale for reasons of safety or effectiveness.</P>
                <P>Accordingly, the Agency will continue to list STRATTERA (Atomoxetine Hydrochloride) 5 Milligrams, 10 Milligrams, 18 Milligrams, 25 Milligrams, 40 Milligrams, 60 Milligrams, 80 Milligrams, and 100 Milligrams capsules, in the “Discontinued Drug Product List” section of the Orange Book. The “Discontinued Drug Product List” delineates, among other items, drug products that have been discontinued from marketing for reasons other than safety or effectiveness. FDA will not begin procedures to withdraw approval of approved ANDAs that refer to this drug product. Additional ANDAs for this drug product may also be approved by the Agency as long as they meet all other legal and regulatory requirements for the approval of ANDAs. If FDA determines that labeling for this drug product should be revised to meet current standards, the Agency will advise ANDA applicants to submit such labeling.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06661 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Submission for OMB Review; 30-Day Comment Request; Hazardous Waste Worker Training—42 CFR Part 65, National Institute of Environmental Health Sciences (NIEHS)</SUBJECT>
                <HD SOURCE="HD2">Correction</HD>
                <P>In notice document 2026-05238 appearing on pages 13043-13044 in the issue of Wednesday, March 18, 2026, make the following correction:</P>
                <P>
                    On page 13043, in the third column, in the 
                    <E T="02">DATES</E>
                     section, “March 18, 2026” should read “April 17, 2026”.
                </P>
            </PREAMB>
            <FRDOC>[FR Doc. C1-2026-05238 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 0099-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Special: Integrative Myocardial Physiology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 28, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Sara Ahlgren, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Rm. 4136, Bethesda, MD 20892, 301-435-0904, 
                        <E T="03">sara.ahlgren@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Fellowships: Ruth L. Kirschstein National Research Service Award.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29-30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Anita T. Tandle, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (240) 204-0329, 
                        <E T="03">tandlea@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Understanding Mechanistic Impacts of Micro- and Nanoplastics in Organ/Tissue Dysfunction.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 2:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Leroy Worth, Ph.D., Scientific Review Officer, Scientific Review Branch, Division of Extramural Research and Training Nat. Institute of Environmental Health Sciences, P.O. Box 12233, MD EC-30/Room 3171, Research Triangle Park, NC 27709, (984) 287-3340, 
                        <E T="03">worth@niehs.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Fellowships: Auditory, Sensory-Motor, Language, Communication and Related Neuroscience.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kausik Ray, Ph.D., Scientific Review Officer, Center for 
                        <PRTPAGE P="17287"/>
                        Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20852, (301) 402-3587, 
                        <E T="03">rayk@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Bacterial Innate Immunomodulation and Pathogenesis.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mairi Noverr, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20852, (240) 747-7530, 
                        <E T="03">mairi.noverr@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Career Development Grants in Clinical Care, Disease Management and Health Outcomes.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Cheryl K. Nordstrom, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20852, 301-402-6711, 
                        <E T="03">cheryl.nordstrom@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Cellular Mechanisms of Aging and Development.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mirela Milescu, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, 
                        <E T="03">mirela.milescu@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Topics on Autoimmunity, Immunology and Transplantation.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 2:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Philip Owens, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Dr., Bethesda, MD 20892, (301) 594-7394, 
                        <E T="03">owensp2@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 2, 2026,</DATED>
                    <NAME>Rosalind M. Niamke, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06651 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Health Services Research: Aging and Optimization of the Workforce.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 28-29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Keary A. Cope, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 209-A, Bethesda, MD 20892-7924, (301) 594-5976, 
                        <E T="03">copeka@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Basic and Translational Cancer Research.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 28, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         David G. Ransom, Ph.D., Scientific Review Officer, Special Review Branch, Division of Extramural Activities, 9609 Medical Center Drive, Room 7W124, National Cancer Institute, NIH Rockville, MD 20850, (240) 276-6351, 
                        <E T="03">david.ransom@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR Panel: Academic Industrial Partnerships for Translation of Medical Technologies.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 28, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Weihua Luo, MD, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5114, MSC 7854, Bethesda, MD 20892, 301-435-1170, 
                        <E T="03">luow@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Mentored Career Development Award Applications.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 6:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Srihari Seshadri, Ph.D., Scientific Review Officer, Center for Scientific Review—EMS Review Branch, National Institutes of Health, 6701 Rockledge Dr. (RK2), Bethesda, MD 20817, (301) 594-4738, 
                        <E T="03">srihari.seshadri@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; S15/R24 Shared-Use Biomedical Research Equipment.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 6:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Stephanie Nicole Hicks, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 480-5710, 
                        <E T="03">hickssn@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in cellular and molecular mechanisms of the nervous system.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29-30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Ipolia R. Ramadan, Ph.D., Scientific Review Officer, Scientific Review Branch, Division of Extramural Research, National Institute on Drug Abuse, NIH, Bethesda, MD 20892, (301) 827-4471, 
                        <E T="03">ramadanir@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR Panel: Rare Diseases Clinical Research Consortia (RDCRC).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                        <PRTPAGE P="17288"/>
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 4:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Zhihong Shan, Ph.D., MD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 827-7085, 
                        <E T="03">zhihong.shan@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Alcohol, Neurotoxicology and Motivated Behavior.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kirk Thompson, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5184, MSC 7844, Bethesda, MD 20892, 301-435-1242, 
                        <E T="03">kgt@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR Panel: Topics in HIV/AIDS: Health Interventions, Clinical Care, and Treatment.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12:31 p.m. to 2:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Xinli Nan, MD, Ph.D., Scientific Review Officer, National Institute on Minority Health and Health Disparities, National Institutes of Health, Scientific Review Branch, OERA, 6707 Democracy Boulevard, Suite 800, Bethesda, MD 20892, (301) 594-7784, 
                        <E T="03">Xinli.Nan@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Denise M. Santeufemio, </NAME>
                    <TITLE>Supervisory Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06654 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Communication and Language.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Andrea B. Kelly, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 451-6339, 
                        <E T="03">kellya2@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; RFA-AI-25-013: UC7 National Biocontainment Laboratories.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 1:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting,
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Stephanie Nicole Hicks, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 480-5710, 
                        <E T="03">hickssn@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Special Topics in Biomaterials, Nanoscience, and gene and drug delivery.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Poonam Tewary, Ph.D., Scientific Review Officer, BBBT Review Branch, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Dr., Bethesda, MD 20852, (240) 532-9777, 
                        <E T="03">tewaryp@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Career Development Grants in Clinical Care and Health Interventions.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Christiane M Robbins, Ph.D., Scientific Review Officer, Scientific Review Branch, Eunice Kennedy Shriver National Institute of Child Health and Human Development, NIH, DHHS, 6710B Rockledge Drive, Rm. 2121B, Bethesda, MD 20817, (301) 451-4989, 
                        <E T="03">crobbins@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Fellowships: Oncology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Leila Bahadori Toulabi, Ph.D., Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH, 9609 Medical Center Drive, Room 7W334, Rockville, MD 20850, (240) 276-6611, 
                        <E T="03">leila.toulabi@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; AD Research Centers.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 7:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rekha Dhanwani, Ph.D., Scientific Review Officer, Scientific Review Program, DEA/NIAID/NIH/DHHS, 5601 Fishers Lane, MSC-9823, Rockville, MD 20892, (240) 627-3076, 
                        <E T="03">rekha.dhanwani@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Health Services Research: Developmental Disabilities, Mental Health, and Substance Use.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                        National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Shiv A. Prasad, Ph.D., Scientific Review Officer, Scientific Review Program, Division of Extramural Activities, National Institutes of Health, NIAID Rockville, MD 20892, 
                        <E T="03">shiv.prasad@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Special Topics in Social Influences and Environmental Determinants of Health.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                        <PRTPAGE P="17289"/>
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Sandhya Sanghi, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 496-2879, 
                        <E T="03">sandhya.sanghi@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Topics in HIV Comorbidities and Clinical Studies.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Milene L Brownlow, Ph.D., Scientific Review Officer, The Center for Scientific Review, The National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (984) 287-3209, 
                        <E T="03">milene.brownlow@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR-25-438: Rare Diseases Clinical Research Consortia (RDCRC) for the Rare Diseases Clinical Research Network (RDCRN) (U54 Clinical Trial Optional).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Cynthia Chioma McOliver, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1007G, Bethesda, MD 20892, (301) 594-2081, 
                        <E T="03">mcolivercc@csr.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Dermatological Sciences.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kan Ma, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 451-4838, 
                        <E T="03">mak2@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; RFA Panel: Neurotherapeutic Agent Identification with Innovation Grants to Nurture Initial Translational Efforts (IGNITE).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:30 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Elizabeth Litvina, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1010E, Bethesda, MD 20892, (301) 272-0774, 
                        <E T="03">liza.litvina@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Pain and Somatosensation.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Myongsoo Matthew Oh, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1011F, Bethesda, MD 20892, (301) 435-1042, 
                        <E T="03">ohmm@csr.nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Denise M. Santeufemio, </NAME>
                    <TITLE>Supervisory Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06657 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Program Projects: Claude D. Pepper Older Americans Independence Centers.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 29-30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kathryn Partlow, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1016D, Bethesda, MD 20892, (301) 594-2138, 
                        <E T="03">partlowkc@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR Panel: Musculoskeletal, Skin and Oral Sciences.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 6:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Sushmita Purkayastha, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 451-1138, 
                        <E T="03">sushmita.purkayastha@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; R21/R03 Special Emphasis Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Shakeel Ahmad, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (240) 276-6442, 
                        <E T="03">ahmads@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Clinical, Behavioral and Environmental Epidemiology, Special Emphasis Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gianina R. Dumitrescu, Ph.D., MPH, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20817, (301) 827-0696, 
                        <E T="03">ramona.dumitrescu@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in basic Neuroscience: Glia in Health and Disease.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                        <PRTPAGE P="17290"/>
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Marta Veronica Hamity, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institute of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 451-1664, 
                        <E T="03">marta.hamity@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR-23-145: Maximizing Investigators' Research Award for Early Stage Investigators.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 2:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Karin Garabed Jegalian, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Dr., Room 712R, Bethesda, MD 20892, (301) 867-5309, 
                        <E T="03">jegaliak@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Cancer Care, Prevention and Control.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 4:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Preethy Nayar, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20817, (301) 402-0302, 
                        <E T="03">preethy.nayar@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Fellowships: Biophysical, Physiological, Pharmacological and Bioengineering Neuroscience.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30-May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Soyoun Cho, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Rm. 1011-G, Bethesda, MD 20892, (301) 594-6593, 
                        <E T="03">Soyoun.cho@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Cardiovascular and Respiratory Sciences Integrated Review Group; Therapeutic Development and Preclinical Studies Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 30, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 7:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Imoh Sunday Okon, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20817, (301) 347-8881, 
                        <E T="03">imoh.okon@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Special Topics in Psychosocial Risk and Interpersonal Processes of Health.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rochelle Francine Hentges, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1000C, Bethesda, MD 20892, (301) 402-8720, 
                        <E T="03">hentgesrf@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>Denise M. Santeufemio, </NAME>
                    <TITLE>Supervisory Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06650 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-7106-N-13]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Housing and Urban Development (HUD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a modified systems of records; correction; supplemental solicitation of public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On January 16, 2026, HUD published a 
                        <E T="04">Federal Register</E>
                         Notice to modify certain HUD system of records notices under the Privacy Act of 1974. The Notice announced HUD's intent to modify the HUD system of records notices in two regards. The Notice unintentionally omitted relevant information with respect to the second modification. Based on this substantive omission, HUD is publishing a Notice providing a correction to the second modification and reopening the public comment period for thirty days on the corrected language for the second modification.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments will be accepted on or before May 6, 2026. This proposed action will be effective on the date following the end of the comment period unless comments are received which result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number by one method:</P>
                    <P>
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions provided on that site to submit comments electronically.
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         202-485-9531.
                    </P>
                    <P>
                        <E T="03">Email: privacy@hud.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Attention: Privacy Office; Shalanda Capehart, Acting Chief Privacy Officer; The Executive Secretariat; 451 7th Street SW, Room 10139; Washington, DC 20410-0001.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number for this notice. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov</E>
                         including any personal information provided.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received go to 
                        <E T="03">http://www.regulations.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Shalanda Capehart, Acting Chief Privacy Officer, 451 7th Street SW, Room 10139; Washington, DC 20410-0001; telephone (202) 402-5085 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech or communication disabilities. To learn more about how to make an accessible telephone call, please visit 
                        <E T="03">https://www.fcc.gov/consumers/guides/telecommunications-relay-service-trs</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On March 25, 2025, President Trump issued Executive Order (E.O.) 14249, “Protecting America's Bank Account Against Fraud, Waste, and Abuse.” In the E.O., President Trump directed agency heads to review and modify relevant System of Records Notices (SORNs) under the Privacy Act of 1974 to include a routine use that allows for the disclosure of records to the Department of Treasury for the purpose of identifying, preventing, or recouping fraud and improper payments, to the extent permissible by law.</P>
                <P>On January 16, 2026, HUD published a Notice to modify certain HUD system of records notices under the Privacy Act of 1974 at 91 FR 2137. The notice listed HUD's intent to modify the HUD SORNs in two specific ways:</P>
                <P>(1) Adding a new routine use to the end of the routine use section of the HUD system of records notices listed in a table published at 91 FR 2137.</P>
                <P>
                    (2) Removing the Do Not Pay routine use for the SORN titled “Single Family Mortgage Insurance Origination System” published at 90 FR 36173 
                    <PRTPAGE P="17291"/>
                    (August 1, 2025). The public comment period ended on February 17, 2026.
                </P>
                <P>With respect to the first modification, no relevant information was omitted. HUD did not receive public comments on this modification. Accordingly, HUD will not revisit this matter. The modification became effective on February 18, 2026, the date following the end of the comment period.</P>
                <P>With respect to the second modification, HUD identified an error and is not implementing the second modification as published for public comment at 91 FR 2137. In that Notice, HUD identified its intent to remove the routine use “P” for the System of Records Notice titled “Single Family Mortgage Insurance Origination System” but did not identify the routine use information that would serve as the replacement.</P>
                <P>Through this Notice, HUD intends to remedy this error and replace the second modification found in the Supplementary Information section of the Notice published at 91 FR 2137 with: “(2) modifies the SORN titled `Single Family Mortgage Insurance Origination System' last published at 90 FR 36173 (August 1, 2025), to remove and replace routine use `P: To the US Department of Treasury through a computer matching program interface between CHUMS and Treasury's Do Not Pay (DNP) system for the purposes of preventing and recovering improper payments and to verify borrower eligibility to participate in FHA's mortgage insurance programs per the Payments Integrity Information Act of 2019' with the routine use below, which is required by the Office of Management and Budget (OMB) Memorandum M-25-32, `Preventing Improper Payments and Protecting Privacy Through Do Not Pay' (August 20, 2025).”</P>
                <P>HUD is reopening the deadline for public comments on the second modification until May 6, 2026. The action will be effective on the date following the end of the comment period unless comments are received which result in a contrary determination.</P>
                <PRIACT>
                    <HD SOURCE="HD1">SYSTEM NAME AND NUMBER:</HD>
                    <P>Single Family Mortgage Insurance Origination System (SFMIOS), HUD/HSNG-03.</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>The core CHUMS system is in HUD Headquarters, 451 7th Street SW, Washington, DC 20410-1000, and Microsoft Azure Federal Cloud US East Data Center in One Microsoft Way, Redmond, Washington, 98052-6399. The Technology Open to Approved Lenders (TOTAL) Scorecard and CHUMS, FHAC and LAMS remain at the National Center for Critical Information Processing and Storage located at NASA's Shared Services Center, Building 1111, Stennis Space Center, MS 39529-6000.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>Brian Faux, Director, Office of Single-Family Program Development, HUD Headquarters, 451 7th Street SW, Washington, DC 20410; telephone (800) 225-5342.</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>(P) To the U.S. Department of the Treasury when disclosure of the information is relevant to review payment and award eligibility through the Do Not Pay Working System for the purposes of identifying, preventing, or recouping improper payments to an applicant for, or recipient of, Federal funds, including funds disbursed by a state (meaning a state of the United States, the District of Columbia, a territory or possession of the United States, or a federally recognized Indian tribe) in a state-administered, federally funded program.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>Docket No. FR-7104-N-09, 90 FR 36173, (August 1, 2025).</P>
                </PRIACT>
                <SIG>
                    <NAME>Shalanda L. Capehart,</NAME>
                    <TITLE>Acting Chief Privacy Officer, Office of Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06606 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-6571-N-01]</DEPDOC>
                <SUBJECT>Notification of Withdrawal of Fair Housing and Equal Opportunity Guidance Documents</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Fair Housing and Equal Opportunity, U.S. Department of Housing and Urban Development (HUD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice informs the public that the Office of Fair Housing and Equal Opportunity (FHEO) has withdrawn the guidance documents identified below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective date of withdrawal:</E>
                         September 17, 2025.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Trey Tagert, Senior Advisor, Office of Fair Housing and Equal Opportunity, Department of Housing and Urban Development, 451 Seventh Street SW, Room 5100, Washington, DC 20410. Telephone number (202) 402-4252 (This is not a toll-free number.) HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as from individuals with speech or communication disabilities. To learn more about how to make an accessible telephone call, please visit 
                        <E T="03">https://www.fcc.gov/consumers/guides/telecommunications-relay-service-trs.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    Consistent with ongoing regulatory reform efforts and in accordance with Executive Order 14192 (“
                    <E T="03">Unleashing Prosperity Through Deregulation”</E>
                    ) 
                    <SU>1</SU>
                    <FTREF/>
                     and Executive Order 14219 (“
                    <E T="03">Ensuring Lawful Governance and Implementing the President's `Department of Government Efficiency' Deregulatory Initiative”</E>
                    ),
                    <SU>2</SU>
                    <FTREF/>
                     HUD is undertaking a comprehensive review of its sub-regulatory guidance to reduce unnecessary compliance burdens, enhance the effectiveness of guidance documents, and promote principles underlying the rule of law. Equal treatment under the law is a bedrock principle of the United States that guarantees equality of opportunity, not equality of outcome. Historical guidance, policies, and interpretive rules of the Office of Fair Housing and Equal Opportunity inconsistent with this principle are subject to review, revision, and/or rescission.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         90 FR 9065 (January 31, 2025).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         90 FR 10583 (February 19, 2025).
                    </P>
                </FTNT>
                <P>Agencies often issue statements that, unlike rules promulgated pursuant to legislation, do not carry the force and effect of law. These statements include interpretative rules, which advise the public of an agency's interpretation of the statutes and regulations it administers as well as general statements of policy, which advise the public about an agency's intended use of its discretionary authority. These non-binding guidance documents are a common tool for agencies to advise the public; however, they can sometimes be used by agencies to attempt to bind the regulated public without adequate accountability.</P>
                <P>
                    HUD has issued non-binding policy guidance in myriad forms over its history. In some instances, guidance promulgated by the Office of Fair Housing and Equal Opportunity may 
                    <PRTPAGE P="17292"/>
                    have adopted interpretations that are inconsistent with the statutory text and purport to impose compliance burdens on regulated parties outside of the strictures of notice-and-comment rulemaking. Even where the guidance might advance a permissible interpretation of the relevant statute or regulation or has afforded the public an opportunity to weigh in, it is the Department's current policy to issue such guidance only when necessary and only when issuance of such guidance would reduce compliance burdens. As such, FHEO has determined to withdraw all existing guidance documents that fail one or more of the following three criteria: (1) the guidance is statutorily prescribed, (2) the interpretation set forth is consistent with the relevant statute or regulation, and/or (3) the guidance decreases compliance burdens.
                </P>
                <P>
                    Additionally, no reliance interests compel retention of the guidance being withdrawn. As a threshold matter, parties understand that guidance is non-binding and does not create substantive rights. To the extent guidance materials or portions thereof go beyond the relevant statute or regulation, they are unlawful, undermining any purported reliance interest in retaining such guidance. Even where guidance is not 
                    <E T="03">per se</E>
                     unlawful, this consideration is outweighed by FHEO's policy that guidance should be withdrawn unless it is necessary and reduces compliance burdens.
                </P>
                <HD SOURCE="HD1">II. Guidance Withdrawn</HD>
                <P>
                    For the reasons set forth above, FHEO is notifying the public that it has withdrawn the guidance documents identified in the table below, effective September 17, 2025. These documents have been removed from active use and should not be relied upon as authoritative. Handbooks and internal training materials referencing these guidance documents are being revised. New internal and external guidance will be issued where necessary and appropriate. All these guidance documents have been removed from the 
                    <E T="03">HUD.gov</E>
                     website and should not be relied upon by internal or external parties.
                </P>
                <P>FHEO is continuing to review its need for existing guidance. Guidance that is determined to be necessary will be reissued.</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s200,xs72">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Title</CHED>
                        <CHED H="1">Date Issued</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Guidance on Application of the Fair Housing Act to the Advertising of Housing, Credit, and Other Real Estate-Related Transactions through Digital Platforms</ENT>
                        <ENT>April 29, 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FHEO 2020-01: Assessing a Person's Request to Have an Animal as a Reasonable Accommodation Under the Fair Housing Act</ENT>
                        <ENT>January 28, 2020.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FHEO Memorandum on Source of Income Testing Activities under the Fair Housing Assistance Program</ENT>
                        <ENT>February 12, 2024.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FHEO Notice 2013-01: Service Animals and Assistance Animals for People with Disabilities in Housing and HUD-funded Programs</ENT>
                        <ENT>April 25, 2013.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FHEO Statement on the Fair Housing Act and Special Purpose Credit Programs</ENT>
                        <ENT>December 7, 2021.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Final Guidance to Federal Financial Assistance Recipients Regarding Title VI Prohibition Against National Origin Discrimination Affecting Limited English Proficient Persons</ENT>
                        <ENT>January 22, 2007.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Implementation of Executive Order 13988 on the Enforcement of the Fair Housing Act</ENT>
                        <ENT>February 11, 2021.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Implementation of OGC Guidance on Application of Fair Housing Act Standards to the Use of Criminal Records</ENT>
                        <ENT>June 10, 2022.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Any actions that do not comply with the text of the Fair Housing Act continue to be subject to enforcement by the Department. HUD encourages parties whose prior conduct may have been violative of the Fair Housing Act, while in conformance with the previous guidance and during the period in which that guidance was in effect, to take immediate actions to address any such potential violation. In cases where an entity meaningfully engages in such responsible conduct, HUD intends to favorably consider such conduct, along with other relevant factors, in considering whether and in what manner to pursue redress for potential violations. HUD retains, without limitation, its discretion and responsibility to evaluate individual cases of potential violations, while taking into account the specific facts and circumstances of any given case. Notwithstanding an enforcement determination by HUD, the Fair Housing Act provides that complainants may file a civil action in an appropriate Federal district court or state court within two years after the occurrence or termination of the alleged discriminatory housing practice. Nothing in this memo affects the rights of parties to seek redress in the proper court.</P>
                <SIG>
                    <NAME>Craig W. Trainor,</NAME>
                    <TITLE>Assistant Secretary for Fair Housing and Equal Opportunity.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06624 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-7106-N-14]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Chief Information Officer (OCIO), and Infrastructure and Operations (IOO), HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a new system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the provisions of the Privacy Act of 1974, as amended, the Department of Housing and Urban Development (HUD), Office of Chief Information Officer (OCIO) and Infrastructure and Operations (IOO) is issuing a public notice of its intent to establish a Privacy Act System of Records Notice (SORN) titled “ServiceNow (SerNow).”</P>
                    <P>
                        ServiceNow (SerNow) includes core components and related modules that work together to support key HUD operations. It facilitates helpdesk operations, Information Technology (IT) management, software and asset tracking, facilities management operations, Human Resources activities, and limited financial planning functions. HUD utilizes multiple ServiceNow instances, with distinct environments tailored to specific purposes such as development, testing, and production, each of which maintains detailed information regarding users and network objects. This structure makes it easier for employees to efficiently locate and utilize required resources while ensuring system integrity across operations. ServiceNow collects and processes information from users either through submitted forms, internal workflows, or integrated systems via structured data repositories. The information maintained within ServiceNow is sourced from HUD systems such as Active Directory (AD)/LAN File Server (LFS), and Digital 
                        <PRTPAGE P="17293"/>
                        Identity and Access Management System (DIAMS).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments will be accepted on or before May 6, 2026. This proposed action will be effective on the date following the end of the comment period unless comments are received which result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by docket number or by one of the following methods:</P>
                    <P>
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions provided on that site to submit comments electronically.
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         202-619-8365.
                    </P>
                    <P>
                        <E T="03">Email: privacy@hud.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Attention: Privacy Office; Shalanda Capehart, Acting Chief Privacy Officer; The Executive Secretariat; 451 7th Street SW, Room 10139; Washington, DC 20410-0001.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number for this rulemaking. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov</E>
                         including any personal information provided.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received go to 
                        <E T="03">http://www.regulations.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Shalanda Capehart; 451 7th Street SW, Room 10139; Washington, DC 20410-0001; telephone number (202) 402-5085 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech or communication disabilities. To learn more about how to make an accessible telephone call, please visit 
                        <E T="03">https://www.fcc.gov/consumers/guides/telecommunications-relay-service-trs</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department of Housing and Urban Development (HUD), Office of Chief Information Officer (OCIO), and Infrastructure and Operations (IOO), uses the ServiceNow Software as a Service (SaaS) Platform to streamline operations and centralize data management. ServiceNow helps HUD manage its data and services in one central system, and it's built around a tool called the Configuration Management Database (CMDB). This database stores important records about users, facilities, and shared resources like meeting rooms, servers, computers, printers, and accounts used to log in. The ServiceNow platform simplifies account management and integrates with HUD's existing technology to allow secure sign-ins using Personal Identity Verification (PIV) cards. It follows a clear management structure to help HUD keep track of network tools, protect user data, and keep systems working the same way across the agency. All ServiceNow programs use the CMDB within HUD's core platform. The system also includes specialized financial management tools, called Proven Optics, that help manage costs, optimize resources, and improve operational efficiency. These tools run in a secure government community cloud environment (GCC) and meet strict federal rules for safety and privacy. HUD's main goals in using ServiceNow are to reduce costs, eliminate manual processes, and improve productivity through automated workflows.</P>
                <PRIACT>
                    <HD SOURCE="HD1">SYSTEM NAME AND NUMBER:</HD>
                    <P>ServiceNow (SerNow), HUD/OCIO-04.</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>Records are maintained at the following locations: HUD Headquarters, 451 7th Street SW, Washington, DC 20410-0001, and Bowhead UIC Government Services, LLC, 6564 Loisdale Court, Suite 900 Springfield, VA 22150-1812.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>George Hurley, Infrastructure and Operations (IOO), HUD HQ, 451 7th Street SW, Washington, DC 20410-0001; telephone (202) 475-8662.</P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>
                        The Information Technology Management Reform Act of 1996 (Pub. L. 104-106, 40 U.S.C. 11101 
                        <E T="03">et seq.</E>
                        ); E-Government Act (Pub. L. 107-347, sec. 203, 44 U.S.C. 3501 note); Federal Information Security Management Act, as amended (Pub. L. 107-347, 44 U.S.C. 3554); Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ); Government Paperwork Elimination Act (Pub. L. 105-277, Title XVII, 44 U.S.C. 3504); Homeland Security Presidential Directive 12 (HSPD-12), Policy for a Common Identification Standard for Federal Employees and Contractors, August 27, 2004; OMB Circular No. A-130, Managing Information as a Strategic Resource (7/28/2016); OMB Memo M-05-24, and Executive Order 13636—Improving Critical Infrastructure Cyber Security (February 12, 2013); Department of Housing and Urban Development Act of 1965, Section 7(d) (Pub. L. 89-174, 42 U.S.C. 3535(d)—“Administrative provisions”); and 5 U.S.C. 3301—“Civil service; generally”.
                    </P>
                    <HD SOURCE="HD2">PURPOSES OF THE SYSTEM:</HD>
                    <P>The purpose of ServiceNow is to help HUD employees efficiently track and manage all service requests for help from start to finish. The system serves as the central repository for HUD policies, procedures, and frequently asked questions (FAQs), empowering employees to quickly find answers independently. It also provides a digital foundation that supports HUD's internal systems across the agency, streamlining operations through automated workflows and replacing manual processes. ServiceNow's functions as a centralized platform for managing HUD assets, giving administrators and employees easy access to critical tools and information, reducing mistakes, and enhancing productivity.</P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>Current HUD employees and contractors.</P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>Full Name, Phone Number, Email address, User Verification PIN, Device Identifier, internet Protocol (IP)/Media Access Control (MAC) Address of assigned Device Identifier (if applicable), Work Address, Home Address, Employee Identification Number and Employment Status/History.</P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
                    <P>Individuals, Digital Identity and Access Management System (DIAMS), and Active Directory (AD)/LAN File Server (LFS).</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>(1) To a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of that individual.</P>
                    <P>(2) To contractors, grantees, experts, consultants, and their agents, or others performing or working under a contract, service, grant, cooperative agreement, or other agreement with HUD or under contract to another agency when necessary to accomplish an agency function related to a system of records. Disclosure requirements are limited to only those data elements considered relevant to accomplishing an agency function.</P>
                    <P>
                        (3) To appropriate agencies, entities, and persons when: (1) HUD suspects or has confirmed that there has been a 
                        <PRTPAGE P="17294"/>
                        breach of the system of records; (2) HUD has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, HUD (including its information systems, programs, and operations), the Federal Government, or national security; and (3) The disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with HUD's efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.
                    </P>
                    <P>(4) To another Federal agency or Federal entity, when HUD determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.</P>
                    <P>(5) To appropriate Federal, State, local, tribal, or governmental agencies or multilateral governmental organizations responsible for investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, or license where HUD determines that the information would assist in the enforcement of civil or criminal laws and when such records, either alone or in conjunction with other information, indicate a violation or potential violation of law.</P>
                    <P>(6) To a court, magistrate, administrative tribunal, or arbitrator while presenting evidence, including disclosures to opposing counsel or witnesses during civil discovery, litigation, mediation, or settlement negotiations; or in connection with criminal law proceedings; when HUD determines that use of such records is relevant and necessary to the litigation and when any of the following is a party to the litigation or have an interest in such litigation: (1) HUD, or any component thereof; or (2) any HUD employee in his or her official capacity; or (3) any HUD employee in his or her individual capacity where HUD has agreed to represent the employee; or (4) the United States, or any agency thereof, where HUD determines that litigation is likely to affect HUD or any of its components.</P>
                    <P>(7) To any component of the Department of Justice or other Federal agency conducting litigation or in proceedings before any court, adjudicative, or administrative body, when HUD determines that the use of such records is relevant and necessary to the litigation and when any of the following is a party to the litigation or have an interest in such litigation: (1) HUD, or any component thereof; or (2) any HUD employee in his or her official capacity; or (3) any HUD employee in his or her individual capacity where the Department of Justice or agency conducting the litigation has agreed to represent the employee; or (4) the United States, or any agency thereof, where HUD determines that litigation is likely to affect HUD or any of its components.</P>
                    <P>(8) To officials of labor organizations recognized under the Civil Service Reform Act when relevant and necessary to their duties of exclusive representation concerning personnel policies, practices, and matters affecting work conditions.</P>
                    <P>(9) To the Office of Personnel Management (OPM), the Merit Systems Protection Board (and its office of the Special Counsel), the Federal Labor Relations Authority (and its General Counsel), or the Equal Employment Opportunity Commission when requested in performance of their authorized duties of exclusive representation concerning personnel policies, practices, and matters affecting work conditions.</P>
                    <P>(10) To the National Archives and Records Administration, Office of Government Information Services (OGIS), to the extent necessary to fulfill its responsibilities in 5 U.S.C. 552(h), to review administrative agency policies, procedures and compliance with the Freedom of Information Act (FOIA), and to facilitate OGIS' offering of mediation services to resolve disputes between persons making FOIA requests and administrative agencies.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORAGE OF RECORDS:</HD>
                    <P>Electronic.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:</HD>
                    <P>Full Name, Email Address, and Employee Identification Number.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:</HD>
                    <P>Under General Records Schedule 3.2, System Access Records, items 030 and 031. Item 030 applies to systems not requiring special accountability for access. Item 030 records can be destroyed when the business use ceases. Item 031 applies to systems requiring special accountability for access. Item 031 requires records to be destroyed/deleted 6 years after the user account is terminated or password is altered, or when no longer required for business us, whichever is later. Backup and Recovery digital media will be destroyed or otherwise rendered irrecoverable per NIST SP 800-88, Rev. 1 “Guidelines for Media Sanitization” (December 2014). The records used within the budgeting application are “temporary” and their destroy clauses are listed in the following disposition instructions: General Record Schedule (GRS) 1.3: Budgeting Records. The records used for facilities management are “temporary” and their destroy clauses are listed in the following disposition instructions: General Record Schedule (GRS) 5.4 Facility, Equipment, Vehicle, Property, and Supply Records. The records for the IT Service Desk and IT Asset Management modules are “temporary” and their destroy clauses are listed in the following disposition instructions: General Record Schedule (GRS) 3.1 General Technology Management Records and General Record Schedule (GRS) 5.8 Administrative Help Desk Records.</P>
                    <HD SOURCE="HD2">ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:</HD>
                    <P>
                        <E T="03">For Electronic Records:</E>
                         Comprehensive electronic records are maintained and stored in an electronic encryption database system. These records can only be accessed based on the user's rights and privileges to the system. Electronic records are stored in the “ServiceNow Enterprise” environment on the department's network (HUD). This environment complies with the security and privacy controls and procedures as described in the Federal Information Security Management Act (FISMA), National Institute of Standards and Technology (NIST) Special Publications, and Federal Information Processing Standards (FIPS). A valid HSPD-12 ID Credential, access to HUD's LAN, a valid User ID and Password, and a Personalized Identification Number (PIN) are required to access the HR Service Delivery, ServiceNow system. These records are restricted to only those stakeholders needing to access the system to perform their official duties.
                    </P>
                    <P>
                        <E T="03">For Electronic Records (cloud-based):</E>
                         Comprehensive electronic records are secured and maintained on a cloud-based software server and operating system that resides in the Federal Risk and Authorization Management Program (FedRAMP) and Federal Information Security Management Act (FISMA) Moderate dedicated hosting environment. All data in the cloud-based server is firewalled and encrypted at rest and in transit. PII is secured in cipher locks, combination locks, key cards, security guards, closed circuit TV 
                        <PRTPAGE P="17295"/>
                        and safes. Identification badges are required to ensure the records are not accessed and strict access controls are governed for electronic records using a user ID and password that require multi-factor authentication before access is granted to ServiceNow. The security mechanisms for handing data at rest and in transit are in accordance with HUD encryption standards.
                    </P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
                    <P>Individuals requesting records of themselves should address written inquiries to the Department of Housing Urban and Development 451 7th Street SW, Washington, DC 20410-0001. For verification, individuals should provide their full name, current address, and telephone number. In addition, the requester must provide either a notarized statement or an unsworn declaration made under 24 CFR 16.4.</P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
                    <P>The HUD rule for contesting the content of any record pertaining to the individual by the individual concerned is published in 24 CFR 16.8 or may be obtained from the system manager.</P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
                    <P>Individuals requesting notification of records of themselves should address written inquiries to the Department of Housing Urban Development, 451 7th Street SW, Washington, DC 20410-0001. For verification purposes, individuals should provide their full name, office or organization where assigned, if applicable, and current address and telephone number. In addition, the requester must provide either a notarized statement, or an unsworn declaration made under 24 CFR 16.4.</P>
                    <HD SOURCE="HD2">EXEMPTIONS PROMULGATED FOR THE SYSTEM:</HD>
                    <P>None.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>None.</P>
                </PRIACT>
                <SIG>
                    <NAME>Shalanda Capehart,</NAME>
                    <TITLE>Acting Chief Privacy Officer, Office of Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06607 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-7106-N-15]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Field Policy and Management, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a modified system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the provisions of the Privacy Act of 1974, as amended, the Department of the Housing and Urban Development (HUD), Office of Field Policy and Management (FPM) is issuing a public notice of its intent to modify the Privacy Act system of records titled, “Customer Relationship Management (CRM)”, to include all Customer Relationship Management systems in use by HUD. This notice incorporates the One Stop Customer Service, HUD Central, and Microsoft Dynamics systems. HUD's Customer Relationship Management systems are designed to track, organize, route, and respond to inquiries from HUD's customers, which include members of the public, individuals and organizations doing business with HUD, and other stakeholders who have an interest in how HUD operates. The reason for this revised notice is to make clarifying changes within: System Manager, and Categories of Records to update description of data collection activities performed by the One Stop Customer Service, HUD Central, and Microsoft Dynamics systems, and Policies and Practices for Retention and Disposal for Records to add context. These updates are explained in the “Supplementary Section” of this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments will be accepted on or before May 6, 2026. This proposed action will be effective on the date following the end of the comment period unless comments are received which result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by the docket number or by one of the following methods:</P>
                    <P>
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions provided on that site to submit comments electronically.
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         202-619-8365.
                    </P>
                    <P>
                        <E T="03">Email: privacy@hud.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Attention: Privacy Office; Shalanda Capehart, Acting Chief Privacy Officer; Office of the Executive Secretariat; 451 7th Street SW, Room 10139; Washington, DC 20410-0001.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number for this rulemaking. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov</E>
                         including any personal information provided.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received go to 
                        <E T="03">http://www.regulations.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Shalanda Capehart; 451 7th Street SW, Room 10139; Washington, DC 20410-0001; telephone number (202) 402-5085 (this is not a toll-free number). HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech or communication disabilities. To learn more about how to make an accessible telephone call, please visit 
                        <E T="03">https://www.fcc.gov/consumers/guides/telecommunications-relay-service-trs</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department of Housing and Urban Development (HUD), Office of Field Policy and Management (FPM), is revising the Customer Relationship Management (CRM) Systems SORN. This CRM Systems SORN combines the “One Stop Customer Service, HUD Central, and Microsoft Dynamics” documenting the use of Customer Relationship Management systems to manage, track, route, and respond to interactions with all customers, stakeholders, partners, and organizations who initiate a customer service interaction with the Department. These Customer Relationship Management systems are covered under one SORN because they serve the same purpose, have the same authorization language, and function to provide customer service to HUD's customers. The Office of Field Policy and Management uses Microsoft Dynamics CRM to interact with all of HUD's customers, as it represents HUD's primary presence in field offices. The Federal Housing Administration (FHA), using HUD Central, focuses on Single-family FHA lenders and borrowers, HUD subsidized multifamily residents, and hospital, skilled nursing, and assisted living developers and lenders. One Stop Customer Service, housed within the Office of Public and Indian Housing's Real Estate Assessment Center, focuses on technical assistance and program protocols for inspectors of HUD funded assets.</P>
                <P>
                    HUD is publishing this revised notice to reflect updates to the data collection activities performed by HUD Central, specifically revisions to the “Categories of Records in the system” section. These updates include the collection of additional Personally Identifiable Information (PII) to support the processing of inquiries from program participants and citizens. For Microsoft Dynamics, the “Categories of Records in the system” section has been updated to include record categories that were previously omitted from the published SORN. This modification also updates contact information in the “System Manager(s)” section to reflect recent personnel changes and revises the 
                    <PRTPAGE P="17296"/>
                    “Policies and Practices for Retention and Disposal for Records” to provide additional context and ensure the section reflects the most current information.
                </P>
                <P>Microsoft Dynamics has the ability to tie in artificial intelligence (AI) features to support staff in managing and responding to customer inquiries more efficiently. The AI features would use existing case/service request information and the organization's internal knowledge base to generate draft case summaries and suggested email responses. All record categories will support resolving a contact's issue by enabling AI to summarize cases, assign priority levels, and generate draft email responses from internal knowledgebase content, with all AI-produced drafts reviewed by staff before sending. It is designed to reduce administrative burden, improve consistency in communications, and help staff quickly identify relevant information when resolving customer issues. The feature is intended to support tasks and does not independently make determinations about individuals.</P>
                <PRIACT>
                    <HD SOURCE="HD1">SYSTEM NAME AND NUMBER:</HD>
                    <P>Customer Relationship Management (CRM) Systems, HUD/FPM-01.</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION: </HD>
                    <P>The files are maintained at the following locations: Microsoft Dynamics CRM-Microsoft AzureGov Virginia datacenter, 101 Herbert Drive, Boydton, VA, 23917; HUD Central—HUD Salesforce General Support System (GSS) in the Salesforce Government Cloud environment; One Stop Customer Service—HUD Headquarters, 451 7th Street SW, Washington, DC 20410-0001.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>Customer Relationship Management (Microsoft Dynamics), Office of Field Policy and Management, Michael Lawyer, Director of Customer Service, (317) 957-7318; HUD Indianapolis Field Office, 575 North Pennsylvania St., RM 665, Indianapolis, IN 46204.</P>
                    <P>HUD Central, Federal Housing Administration, Walter Ouzts, System Manager, (202) 402-2286; HUD Headquarters, 451 7th Street SW, Washington, DC 20410-0001.</P>
                    <P>One Stop Customer Service, Office of Public and Indian Housing (PIH), Shylon Ferry, Deputy Assistant Secretary, (202) 402-2654; HUD Headquarters, 451 7th Street SW, Washington, DC 20410-0001.</P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>Section 2 of The Department of Housing and Urban Development Act of 1965, 42 U.S.C. 3531, Executive Order 12160 and the Housing and Community Development Act of 1974, Public Law 93-383; Executive Order 14058; Executive Order 13571; Executive Order 12862.</P>
                    <HD SOURCE="HD2">PURPOSE(S) OF THE SYSTEM:</HD>
                    <P>The purpose of these systems is to manage, track, route, and respond to interactions the Department has with the public, stakeholders, partners, and other organizations interested in how HUD does business, such as advocacy groups, professional organizations, Congress, and the media.</P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>Individuals, public stakeholders, partners, and individuals acting on behalf of, or affiliated with, other organizations interested in how HUD does business.</P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>Microsoft Dynamics CRM collects name, phone number, secondary phone number(s), email address(es), secondary email address(es), home/work address(es), client type, client's company (if they are associated with HUD grantees or with external stakeholder entities), and service request categorization, which includes primary and sub-category, along with case modifiers such as disabled, elderly, or veteran.</P>
                    <P>HUD Central collects full name, email address(es), phone number(s), fax number, user ID(s), taxpayer ID, home/work address(es), investigation report or database IP/MAC address, case number(s), property zip code(s), and speech-to-text.</P>
                    <P>One Stop Customer Service collects name, phone number(s), secondary phone number, email address(es), secondary email address(es), home address, and account number.</P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
                    <P>Members of the public for all three systems.</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>(1) To public and private counseling agencies; building associations; developers; financial institutions holding HUD-insured mortgages; Federal, State and local government offices; Consumer Protection agencies; Public Housing Agencies; and State and local real estate and planning Commissions for the purpose of assisting in the resolution of a complaint.</P>
                    <P>(2) To the National Archives and Records Administration, Office of Government Information Services (OGIS), to the extent necessary to fulfill its responsibilities in 5 U.S.C. 552(h), to review administrative agency policies, procedures and compliance with the Freedom of Information Act (FOIA), and to facilitate OGIS' offering of mediation services to resolve disputes between persons making FOIA requests and administrative agencies.</P>
                    <P>(3) To a congressional office from the record of an individual, in response to an inquiry from the congressional office made at the request of that individual.</P>
                    <P>(4) To contractors, grantees, experts, consultants, Federal agencies, and non-Federal entities, including, but not limited to, State and local governments and other research institutions or their parties, and entities and their agents with whom HUD has a contract, service agreement, grant, cooperative agreement, or other agreement for the purposes of statistical analysis and research in support of program operations, management, performance monitoring, evaluation, risk management, and policy development, to otherwise support the Department's mission, or for other research and statistical purposes not otherwise prohibited by law or regulation. Records under this routine use may not be used in whole or in part to make decisions that affect the rights, benefits, or privileges of specific individuals. The results of the matched information may not be disclosed in identifiable form.</P>
                    <P>(5) To contractors, grantees, experts, consultants and their agents, or others performing or working under a contract, service, grant, cooperative agreement, or other agreement with HUD, when necessary to accomplish an agency function related to a system of records. Disclosure requirements are limited to only those data elements considered relevant to accomplishing an agency function.</P>
                    <P>(6) To contractors, experts and consultants with whom HUD has a contract, service agreement, assignment or other agreement with the Department, when necessary to utilize relevant data for the purpose of testing new technology and systems designed to enhance program operations and performance.</P>
                    <P>
                        (7) To appropriate agencies, entities, and persons when (1) HUD suspects or has confirmed that there has been a breach of the system of records; (2) HUD has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, HUD 
                        <PRTPAGE P="17297"/>
                        (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with HUD's efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.
                    </P>
                    <P>(8) To another Federal agency or Federal entity, when HUD determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to suspected or confirmed breach, or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.</P>
                    <P>(9) To appropriate Federal, State, local, tribal, or other governmental agencies or multilateral governmental organizations responsible for investigating or prosecuting the violations of, or for enforcing or implementing, a statute, rule, regulation, order, or license, where HUD determines that the information would assist in the enforcement of civil or criminal laws and when such records, either alone or in conjunction with other information, indicate a violation or potential violation of law.</P>
                    <P>(10) To a court, magistrate, administrative tribunal, or arbitrator in the course of presenting evidence, including disclosures to opposing counsel or witnesses in the course of civil discovery, litigation, mediation, or settlement negotiations, or in connection with criminal law proceedings; when HUD determines that use of such records is relevant and necessary to the litigation and when any of the following is a party to the litigation or have an interest in such litigation: (1) HUD, or any component thereof; or (2) any HUD employee in his or her official capacity; or (3) any HUD employee in his or her individual capacity where HUD has agreed to represent the employee; or (4) the United States, or any agency thereof, where HUD determines that litigation is likely to affect HUD or any of its components.</P>
                    <P>(11) To any component of the Department of Justice or other Federal agency conducting litigation or in proceedings before any court, adjudicative, or administrative body, when HUD determines that the use of such records is relevant and necessary to the litigation and when any of the following is a party to the litigation or have an interest in such litigation: (1) HUD, or any component thereof; or (2) any HUD employee in his or her official capacity; or (3) any HUD employee in his or her individual capacity where the Department of Justice or agency conducting the litigation has agreed to represent the employee; or (4) the United States, or any agency thereof, where HUD determines that litigation is likely to affect HUD or any of its components.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORAGE OF RECORDS:</HD>
                    <P>Electronic.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:</HD>
                    <P>Individual records for all three systems can be retrieved by name, phone number(s), or home/work email address(es).</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RENTENTION AND DISPOSAL OF RECORDS:</HD>
                    <P>Public Customer Service records the system's disposition instructions: Automated records are maintained for five years. Complaints pending response will remain open and active until the final response is sent. Dispose of in accordance with the approved disposition instructions for the related subject individual's records, or five years after the disclosure for which the accountability was made, whichever is later. Obsolete records will be disposed of in accordance with the General Records Schedule (GRS) Schedule 4.2 Item 50 (NC1-64-77-1 item 27).</P>
                    <HD SOURCE="HD2">ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:</HD>
                    <P>The systems can only be accessed through HUD's Office 365 environment, using all the security safeguards the Department uses for its current operating system. Users must have a HUD authorized account, which HUD authorizes with employment and deactivates once the employee leaves the Department. Customer Relationship Management data is available to employees on a need-to-know basis, and systems use role-based security to restrict access to this data. Access to data is granted by an Administrative Security Officer through the Department's secure application access system. Role-based security limits the amount of accessible data to only that permissible by the security role. Dynamics 365 CRM will limit future AI capabilities to summarize a contact's case history, assigning priority or triage levels based on the urgency of the issue, and generating draft email responses drawn from internal knowledgebase content. All AI-generated outputs, including email drafts, will require human review before being sent.</P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
                    <P>Individuals requesting records of themselves should address written inquiries to the Department of Housing Urban and Development 451 7th Street SW, Washington, DC 20410-0001. For verification, individuals should provide their full name, current address, and telephone number. In addition, the requester must provide either a notarized statement, or an unsworn declaration made under 24 CFR 16.4.</P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
                    <P>The HUD rule for contesting the content of any record pertaining to the individual by the individual concerned is published in 24 CFR 16.8 or may be obtained from the system manager.</P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
                    <P>Individuals requesting notification of records of themselves should address written inquiries to the Department of Housing Urban Development, 451 7th Street SW, Washington, DC 20410-0001. For verification purposes, individuals should provide their full name, office or organization where assigned, if applicable, and current address and telephone number. In addition, the requester must provide either a notarized statement, or an unsworn declaration made under 24 CFR 16.4.</P>
                    <HD SOURCE="HD2">EXEMPTIONS PROMULGATED FOR THE SYSTEM:</HD>
                    <P>None.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>Docket No. FR-7092-N-39, 89 FR 86352, October 30, 2024.</P>
                </PRIACT>
                <SIG>
                    <NAME>Shalanda Capehart,</NAME>
                    <TITLE>Acting Chief Privacy Officer, Office of Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06609 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[Docket No. FWS-R6-ES-2026-0958, FXGO166009DR000-267-FF09D00000]</DEPDOC>
                <SUBJECT>Endangered and Threatened Wildlife and Plants; Request for Information on Implementation of the Gray Wolf (Canis Lupus) Nonessential Experimental Population Rule in Colorado</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for information and comments.</P>
                </ACT>
                <SUM>
                    <PRTPAGE P="17298"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Fish and Wildlife Service (Service) requests information regarding the implementation of the Endangered Species Act (ESA) section 10(j) nonessential experimental population rule (10(j) Rule) for gray wolves (
                        <E T="03">Canis lupus</E>
                        ) in the State of Colorado, 88 FR 77014 (Nov. 8, 2023). Over the past few years, many wolf-livestock depredation events have been verified in Colorado and the total number of verified depredations and associated claims has vastly exceeded the funds currently available under Colorado's existing livestock compensation scheme. The Service is seeking information on how the State of Colorado (State), including Colorado Parks and Wildlife (CPW) and partner agencies, is implementing the 10(j) Rule and addressing conflicts between wolves and livestock. Specifically, the Service seeks information on the State's implementation of the 10(j) Rule, as published. On December 12, 2023, the Service signed a Memorandum of Agreement (MOA) with CPW in order to “facilitate and enable active participation in wolf conservation and management by CPW personnel.” Of the several listed objectives, CPW committed to “. . . share timely information, as appropriate and necessary, with partners and stakeholders (including the public) regarding the Colorado Gray Wolf Restoration Program to foster transparent and effective communications regarding the goals and commitments under the MOA.” Moreover, the MOA stated that the CPW would “conduct public outreach and provide information about gray wolves and gray wolf management in Colorado” and “implement proactive strategies and conduct or direct non-lethal and lethal control actions to reduce and/or resolve gray wolf-livestock conflict and human safety concerns . . .” The MOA also states that CPW will “communicate regularly (at a minimum, quarterly) with the Service's Wolf Coordinator or appropriate Service representative” as well as “Assist the Service by providing data as needed to allow the Service to carry out its responsibilities under the ESA and to facilitate coordination of management responses to wolf conflicts in Colorado . . .” The Service seeks comment on implementation of the aspects of this MOA, including but not limited to: conflict prevention and response, stakeholder engagement, and recommendations for improving outcomes. The Service also seeks information regarding the impact, if any, that the experimental wolf population is having on wild ungulate herds or populations, including on Tribal lands, as discussed in the final rule, as well as implementation of associated procedures to allow nonlethal and lethal management of gray wolves that are having an unacceptable impact. The Service also solicits feedback on CPWs tracking of wolf conflict risk, activities taken to minimize wolf conflict risk, and the allowable forms of take for gray wolves as outlined in the 10(j) rule, including: “the taking of wolves in the act of attacking livestock” on both private and public land as well as the “agency take of wolves that depredate livestock.” Finally, the Service seeks information regarding implementation of the State's livestock loss compensation program as a means to achieve minimization of conflict risk as outlined in the Colorado Wolf Restoration and Management Plan incorporated by reference in the MOA.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments will be accepted on or before June 5, 2026. Comments submitted electronically using the Federal eRulemaking Portal (see 
                        <E T="02">ADDRESSES</E>
                        , below) must be received by 11:59 p.m. eastern time on the closing date.
                    </P>
                    <P>
                        To ensure your comment is received and considered, you must submit it using one of the methods identified in the 
                        <E T="02">ADDRESSES</E>
                         section of this document. Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Comment submission:</E>
                         All submissions must include the docket FWS-R6-ES-2026-0958 this document. You must submit comments using one of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Electronic submission:</E>
                         Federal eRulemaking Portal at: 
                        <E T="03">https://www.regulations.gov.</E>
                         In the Search box, enter FWS-R6-ES-2026-0958, which is the docket number for this action. Then click the Search button. On the resulting page, you may submit a comment by clicking on “Comment.” Please ensure that you have found the correct document before submitting your comments.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail:</E>
                         Public Comments Processing, Attn: Docket No. FWS-R6-ES-2026-0958, Policy and Regulations Branch, U.S. Fish and Wildlife Service, MS: PRB (JAO/3W), 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                    </P>
                    <P>Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered. We will not accept comments via email, fax, or hand delivery. We are not required to consider comments that are submitted after the comment period ends or that are submitted via a method outside of these instructions. Comments containing profanity, vulgarity, threats, or other inappropriate content will not be considered.</P>
                    <P>
                        We will post all comments at 
                        <E T="03">https://www.regulations.gov.</E>
                         You may request that we withhold personal identifying information from public review; however, we cannot guarantee that we will be able to do so. See Request for Public Comments for more information. You may submit comments by one of the following methods:
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Marjorie Nelson, Assistant Regional Director for Ecological Services, Mountain-Prairie Region, U.S. Fish and Wildlife Service, 1 Denver Federal Center, Building 53—Room FW100, Denver, CO 80225; telephone: 303-236-4258; email: 
                        <E T="03">marjorie_nelson@fws.gov.</E>
                         Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>Section 10(j) of the ESA authorizes the designation of certain reintroduced populations of listed species as nonessential experimental populations (NEPs), allowing for greater management flexibility and helping reduce conflicts with human activities while contributing to conservation goals (16 U.S.C. 1539(j)). On November 8, 2023, the Service published a final rule establishing a NEP for gray wolves in Colorado (88 FR 77014, November 11, 2023; hereafter 10(j) Rule). The State of Colorado requested that the Service establish an NEP in conjunction with their State-led gray wolf reintroduction effort. Establishment of the NEP provided management flexibilities for the gray wolf within the NEP area, which can reduce negative interactions with livestock producers and communities, while concurrently providing for the conservation of the species.  </P>
                <P>
                    Over the past few years, multiple livestock depredations by wolves have been verified in Colorado on both private and leased grazing lands. The number of verified depredations have exceeded available compensation funds in Colorado, leading to concerns among livestock producers regarding 
                    <PRTPAGE P="17299"/>
                    timeliness, adequacy, and accessibility of compensation.
                </P>
                <P>The Service recognizes the importance of collecting information from producers, landowners, Tribes, State and local governments, conservation organizations, and other stakeholders with regard to 10(j) Rule implementation. This request for information (RFI) solicits data, observations, and recommendations related to 10(j) Rule implementation, including information about conflict response, nonlethal deterrence, coordination and communication, and other related topics. This RFI also solicits feedback on the State of Colorado's compensation program for livestock producers who experience livestock losses caused by wolves.</P>
                <HD SOURCE="HD1">Purpose of This Request for Information</HD>
                <P>The purpose of this RFI is to gather information on how the 10(j) Rule framework is being implemented in Colorado and the outcomes associated with that implementation. The Service especially invites information regarding:</P>
                <P>• Trends and patterns in livestock depredation since implementation of the 10(j) Rule;</P>
                <P>• Practical experiences with incident response, conflict mitigation, and verification of depredations;</P>
                <P>• Effectiveness of nonlethal and other preventative tools and strategies;</P>
                <P>• Coordination among Federal, State, Tribal, and local entities;</P>
                <P>• Communication and outreach regarding wolf management, risk, and prevention;</P>
                <P>• Recommendations to improve 10(j) Rule implementation to reduce conflict while supporting conservation objectives.</P>
                <P>While not governed by the 10(j) Rule framework, the Service also invites information regarding Colorado's livestock loss compensation program, including the sufficiency, timeliness, and accessibility of compensation funds and related processes in the State.</P>
                <HD SOURCE="HD1">Request for Information</HD>
                <P>The Service invites the public to provide information on any aspect of the State of Colorado's implementation of the 10(j) Rule. Commenters may respond to the following questions, or provide other relevant information:</P>
                <P>• Based on your observations or data, what trends in wolf-livestock interactions have occurred in Colorado since 10(j) Rule implementation on December 8, 2023?</P>
                <P>• What nonlethal deterrence or preventive measures have been employed in Colorado, and how effective have they been?</P>
                <P>• How has the process of verifying depredations and documenting claims in Colorado functioned in your experience?</P>
                <P>• How would you characterize coordination among agencies, producers, Tribes, and local communities in addressing conflicts?</P>
                <P>• What improvements, in your view, would make 10(j) Rule implementation more effective in reducing conflict and improving outcomes for producers and wolf conservation in Colorado?</P>
                <P>While the 10(j) Rule did not authorize and/or govern the State of Colorado's livestock loss compensation program, the Service also invites commenters to respond to the following questions about the State of Colorado's livestock loss compensation program:</P>
                <P>• To what extent have the state's available compensation funds met the need for indemnity and associated costs?</P>
                <P>• What barriers exist to obtaining compensation from the state or implementing mitigation strategies?</P>
                <P>Submitters are encouraged to provide specific examples, geographies, dates, and any relevant supporting materials.</P>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>
                    All information received in response to this RFI will be posted on 
                    <E T="03">https://www.regulations.gov</E>
                     and may include personal identifying information. Do not include information you do not wish to make publicly available.
                </P>
                <HD SOURCE="HD1">Authority</HD>
                <P>
                    The authority for this RFI is the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) including section 10(j), and other applicable laws.
                </P>
                <SIG>
                    <NAME>Brian R. Nesvik,</NAME>
                    <TITLE>Director, U.S. Fish and Wildlife Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06638 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[A2407-014-004-065516; #O2412-014-004-047181.1; LLHQ220000]</DEPDOC>
                <SUBJECT>National Environmental Policy Act Implementing Procedures for the Bureau of Land Management</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces a proposed revision to the National Environmental Policy Act (NEPA) implementing procedures for the Bureau of Land Management (BLM) at DOI Handbook of NEPA Implementing Procedures (DOI NEPA Handbook) that supplements Chapter 1 of Part 516 of the Department of the Interior's (Department or DOI) Departmental Manual (516 DM 1). The proposed revision would add a new categorical exclusion (CE) for forest and woodland density management in the 
                        <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments on or before May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on this Notice or the associated Substantiation report may be submitted electronically to 
                        <E T="03">BLM National NEPA Register: https://eplanning.blm.gov</E>
                         and search for DOI-BLM-HQ-2000-2026-0001-OTHER_NEPA, or by mail to Wade Salverson, Forestry Lead, Division of Forest, Rangeland and Vegetation Resources, at the Idaho State Office, 1387 S Vinnell Way, Boise, ID 83709.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Wade Salverson, Forestry Lead, Division of Forest, Rangeland and Vegetation Resources, at (202) 849-0990, or 
                        <E T="03">wsalvers@blm.gov.</E>
                         Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The BLM manages roughly 248 million surface acres of public land predominantly in the West, of which an estimated 58 million acres are forested/woodlands. A significant portion of these lands are managed under an active forest and woodland management approach, as guided by individual BLM land use plans (LUPs). Active management is often necessary for long-term sustainability due to widespread disruptions to natural disturbance regimes—particularly fire. Over the past several decades, forest structure and species composition on BLM-managed acres has significantly changed because of insect outbreaks, disease, drought, and forest density. As a result, BLM faces increased fuel loading that has contributed to the increasing frequency of complex fires on public lands and their threat to human life and property. This has prompted BLM to review 
                    <PRTPAGE P="17300"/>
                    existing programs and identify measures that would better enable wildfire preparedness to protect human life and property in the wildland urban interface.
                </P>
                <P>
                    In 2007, BLM administratively established CE C.7 (harvesting of live trees ≤70 acres with ≤0.5 of a mile of temporary road) at section 11.9 of the DOI NEPA Handbook. CE C.7 covers similar activities to this new CE. At that time, BLM stated it would continue to compile and review evidence to determine if additional actions should be categorically excluded and may propose additional CEs or larger treatment areas in the future (72 FR 45504). In addition, CE C.7 was only based on U.S. Forest Service environmental assessments (EAs) from prior to 2003 while the underlying verification report for this proposed CE uses BLM data and more contemporary projects and conditions. The existing CE for density management: (1) limited the BLM to 70 acres or less of total disturbance; (2) limited the BLM to no more than 0.5 mile of temporary road construction for the thinning operation; and (3) and had not been revised in over 18 years. Since 2007, (a) BLM has developed a broader empirical record of forest and woodland density management proposals and outcomes (Timber Sale Information System (TSIS) queries and ePlanning NEPA records), (b) the agency has documented substantial loss of and damage to forest resources from severe disturbances exacerbated by forest or woodland density, and (c) Congress has encouraged increasing the pace/scale of risk-reduction activities via new statutory CEs for the U.S. Forest Service (
                    <E T="03">e.g.,</E>
                     Healthy Forests Restoration Act sections 602, 603, and 605).
                </P>
                <P>
                    Upon review of the use of the existing CE, supporting information, and its environmental assessment information, the Department is proposing to establish this new CE to further support actions for forest and woodland density management. The proposed CE covers modification of tree density up to 5,000 acres of treatment area. Active management through thinning can help development of desired habitat and forest structure and composition, enhance resilience to insect and disease, contribute to rural economies, and reduce future wildfire fuel loads and hazards to wildland firefighters, the public, and infrastructure. This proposed CE would also allow the BLM more flexibility to quickly respond to high-risk conditions across larger areas to provide for public and infrastructure safety, reduce the potential for active crown fires that impact firefighter and public safety, and contribute to one of the six principal or major uses of the public lands identified in the Federal Land Policy and Management Act of 1976, which recognizes “the Nation's need for domestic sources of timber and fiber.” Further, this CE will provide an additional tool to facilitate increased timber production and sound forest management in accordance with Executive Order 14225, 
                    <E T="03">Immediate Expansion of American Timber Production,</E>
                     90 FR 11365 (March 1, 2025). As noted, the BLM already uses its existing CE (C.7) that addresses density management not to exceed 70 acres and intends to retain that CE; the BLM is proposing this additional CE to increase its flexibility to respond to forest management needs across larger areas. Based on review of the use of the existing CE C.7 as part of this process, BLM does not intend to pursue removal of the 70-acre CE nor revise that CE to encompass the proposed scope of actions described in this proposal. The BLM sees a need for both CE categories. The 70-acre CE provides a more limited scope of actions that are useful. The BLM expects existing CE C.7 would still be used for smaller areas where BLM has no need for the additional tools this proposed CE would provide.
                </P>
                <P>Following years of experience in conducting forest thinning without significant effects, BLM has identified that establishing a CE for the action is necessary to increase BLM's flexibility to respond to forest health and wildfire concerns across larger areas, while keeping the tailored focus of the action. The BLM notes that the existing 70-acre limitation for categorically excluded timber density management operations has proved insufficient to address the growing need for BLM to authorize additional density management over greater acreage. One 5,000-acre density management sale represents 0.0000862 (or 1/116 of 1%) of the estimated 58 million acres of BLM forest and woodlands managed by BLM today. The BLM manages 58 million acres of forests/woodlands. Allowing BLM this tool to contract for more acres would allow the agency to be more effective in its management. Given the vast amount of BLM-managed acres requiring treatment to promote better forest health and reduce fuel loading and wildfire risk, the BLM is proposing to revise the 70-acre limit established nearly 20 years ago to better adapt it to BLM's needs in managing those acres. Furthermore, evaluating the more than 1,800 thinning-based timber sales conducted by the agency since 1990 under EAs and associated Findings of No Significant Impact (FONSIs) show that these treatment methods do not significantly affect the quality of the human environment. BLM data from the TSIS show that more than 325,000 acres have been commercially thinned between 1990 and 2025. The BLM has evaluated its records and has determined that the environmental review and implementation records of these routine management actions demonstrate that this category of actions normally do not significantly affect the quality of the human environment and that establishment of a CE is warranted.</P>
                <P>
                    Establishing the proposed CE would enable BLM to ensure a timely process for a density management project prior to a new fire season and in preparation for the subsequent fire seasons. Wildfire trends show a need to reduce fire severity and improve forest (or stand) resilience. Between 2000 and 2024, the U.S. averaged 7.3 million acres burned annually. According to National Interagency Fire Center (NIFC) data (National Centers for Environmental Information [NCEI], 2026, 
                    <E T="03">https://www.ncei.noaa.gov/access/monitoring/wildfires/12/6</E>
                    ), in 2021 the United States hit the highest number of acres burned since 2006, with a total of 10,325,514 acres burned. On BLM-managed lands, wildfire burned an average of 236,530 acres of forest annually between 2009 and 2024. High-profile events such as the 2018 Camp Fire in California—which burned 153,336 acres (including 4,070 acres of BLM land), resulted in 85 fatalities, and caused billions of dollars in damages—highlighting the urgent need for proactive management. Further, between January 1, 2025, and November 28, 2025, 4,927,904 acres burned due to wildfires on federal land. Establishing this CE for use by the BLM will assist in reducing fire severity to battle these unprecedented and destructive fires and will aid in keeping the American people safe.
                </P>
                <P>Further, establishing the proposed CE would enable the BLM to ensure the efficient usage of government resources in serving the American public. While EAs have long been used to analyze density management projects, the NEPA statute and agency implementing regulations allow for the development of CEs—a tool to reduce protracted, repetitive analysis for actions that normally do not have significant environmental impacts.</P>
                <P>
                    Additionally, on June 3, 2023, the Fiscal Responsibility Act of 2023 was enacted into law, revising NEPA for the first time in over 50 years. The revisions included codification of deadlines and page limits for the preparation of NEPA 
                    <PRTPAGE P="17301"/>
                    documents by federal agencies, procedures for determining level of review and adoption of categorical exclusions, as well as a number of other reforms that further demonstrate that the goal of NEPA is to “inform agency decision-making, not to paralyze it.” 
                    <E T="03">Seven County Infrastructure Coalition</E>
                     v 
                    <E T="03"> Eagle County., Colo.,</E>
                    605 U.S. 168, 173 (2025). The Fiscal Responsibility Act codified in law the definition of a Categorical Exclusion as “. . . a category of actions that a Federal agency has determined normally does not significantly affect the quality of the human environment within the meaning of section 102(2)(C).” 42 U.S.C. 4336e(1). The cost and time associated with repeated analysis can hinder the BLM's ability to respond effectively to fire risk and other forest management needs. EA processes can be time-consuming. For example, the Marys Peak field office in BLM-Oregon began an EA titled Central Boulder Forest Management on a 400-acre timber sale in January 2019 that was not completed until July of 2021 even when it found that there would not be significant impacts. Because forest thinning improves the overall forest health, increases stand resilience to wildfire, and enhances firefighter safety and effectiveness, contracting larger treatment areas will improve operational efficiency and reduce per-acre costs for the agency.
                </P>
                <P>
                    As noted, the ability to determine that an action is excluded pursuant to a CE from the requirement to prepare an environmental document under NEPA, thus forestalling the need to prepare an EA or environmental impact statement (EIS), can streamline project authorization. The increased efficiency in project authorization can help the BLM address the wildfire crisis and protect communities, habitat, and forest resources from high severity wildfire and other stressors, apply proven, science-informed treatment methods more efficiently, and be more effective with time and public resources by avoiding redundant environmental reviews that do not yield new information. This proposed CE would provide an additional tool to facilitate sound forest management and is in direct response to Section (f) of Executive Order 14225, 
                    <E T="03">Immediate Expansion of American Timber Production,</E>
                     90 FR 11365 (March 1, 2025).
                </P>
                <P>
                    NEPA, 42 U.S.C. 4321 
                    <E T="03">et seq.,</E>
                     requires Federal agencies to consider the environmental effects of their proposed actions in their decision-making processes and inform and engage the public in that process.
                </P>
                <P>To comply with NEPA, agencies determine the appropriate level of review of any major Federal action—an EIS, EA, or a CE. See generally, 42 U.S.C. 4336(b); 43 CFR part 46; DOI NEPA Handbook section 1.2 (2025). Where it is reasonably foreseeable that significant environmental effects are likely, the agency must prepare an EIS and document its decision. See generally, 42 U.S.C. 4336(b)(1); DOI NEPA Handbook section 1.2(a)(5)(ii). Where appropriate, an agency may prepare an environmental assessment, and if it reaches a FONSI, it need not prepare an EIS. See generally, 42 U.S.C. 4336(b)(2); DOI NEPA Handbook section 1.6; section 1.2(a)(4).</P>
                <P>Under NEPA, agencies may establish categorical exclusions—categories of actions that the agency has determined normally do not significantly affect the quality of the human environment—in their agency NEPA implementing procedures (42 U.S.C. 4336e(1)). An agency may also adopt a CE listed in another agency's NEPA procedures consistent with section 109 of NEPA (42 U.S.C. 4336c).</P>
                <P>Under the Department's NEPA procedures, if a bureau determines that a CE covers a proposed action, it then evaluates the proposed action for the presence of extraordinary circumstances, which are factors or circumstances that indicate a normally categorically excluded action may have a significant effect (43 CFR 46.205, 46.215). If the bureau cannot categorically exclude the proposed action following review for extraordinary circumstances, it will prepare an EA or EIS, as appropriate, before issuing any decision to authorize the action (43 CFR 46.205(c), 42 U.S.C. 4336(b)).</P>
                <P>
                    The BLM is proposing to establish this new CE by substantiating the proposed new CE with sufficient information to conclude that the actions included in the category do not have a significant effect on the quality of the human environment and provides this substantiation in a written record that is made publicly available (see 
                    <E T="02">Addresses</E>
                    ). In developing this new CE, the Department consulted with CEQ in accordance with 42 U.S.C. 4332(2)(B) and is providing notification to the public about the proposed establishment of the CE through this notice.
                </P>
                <HD SOURCE="HD1">II. Categorical Exclusion Justification</HD>
                <P>The BLM finds that the type of actions described in this proposed CE do not normally have a significant effect on the human environment. This finding is based on the BLM's analysis of these types of actions as documented in the BLM's Substantiation Report for this proposed new CE and supporting documents and the relevant scientific literature. The Substantiation Report explains that because the restrictions on the actions included in the CE limit surface disturbance and access road construction, the Department and the BLM conclude that the types of actions included in this proposed CE do not normally result in significant environmental effects and therefore warrant establishment of the CE. The Substantiation Report summarizes the review of 84 EAs that analyzed density management actions in forests or woodlands that supported FONSIs to demonstrate the finding that actions included in the proposed CE would not normally result in significant effects to the human environment. The Substantiation Report documents evaluation of the BLM NEPA analyses and post-implementation observations as well as available scientific research on the effects of routine actions included in the new proposed CE over time and over different geographic areas.</P>
                <P>
                    The Department and the BLM consulted with CEQ on the Substantiation Report for the proposed CE consistent with section 102(2)(B) of NEPA, 42 U.S.C. 4332(2)(B). If finalized, the Department would add this CE to the BLM's NEPA procedures, in its 
                    <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions.</E>
                     As with other administratively developed CEs for Department bureaus, when applying this CE, Responsible Officials would evaluate proposed actions eligible for this CE to determine whether any extraordinary circumstances are present in accordance with the requirements in the Department's NEPA implementing procedures at 43 CFR 46.205 and 46.215. The Responsible Official would document this review and, for BLM, include this documentation in the information posted on the BLM's NEPA register website. If the Responsible Official cannot use this CE to support a decision to authorize density management in forests or woodlands due to the presence of extraordinary circumstances, the Responsible Official will prepare an EA or EIS before authorizing such activities, consistent with 43 CFR 46.205(c) and 42 U.S.C. 4336(b).
                </P>
                <HD SOURCE="HD1">III. Text for the Departmental Handbook of NEPA Implementing Procedures</HD>
                <P>
                    The Department's NEPA procedures are proposed to be modified as follows. 
                    <PRTPAGE P="17302"/>
                    The 
                    <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions</E>
                     would include the following language:
                </P>
                <EXTRACT>
                    <HD SOURCE="HD1">* * * Bureau of Land Management</HD>
                    <HD SOURCE="HD2">11.9 Actions Eligible for a Categorical Exclusion (CE)</HD>
                    <STARS/>
                    <HD SOURCE="HD3">C. Forestry</HD>
                    <P>
                        <E T="03">(11) *Modification of tree density up to 5,000 acres of treatment area. Does not include silvicultural methods that are intended to regenerate whole stands, such as even-aged regeneration harvest, clearcutting, or variable retention harvest, or vegetation management intended to convert forest or woodlands to non-forest vegetation cover.</E>
                    </P>
                    <P>
                        <E T="03">(a) Covered actions include:</E>
                    </P>
                    <P>
                        <E T="03">(i) Cutting, yarding, and the use of landings and skid trails to facilitate the removal of commercial and non-commercial trees.</E>
                    </P>
                    <P>
                        <E T="03">(ii) Chipping/grinding or removal of residual slash.</E>
                    </P>
                    <P>
                        <E T="03">(iii) Group selection silvicultural treatment to promote regeneration of shade intolerant species and early successional habitat in an uneven-aged context not to exceed 2-acre individual patches and 10 percent of the treatment area. Group selection openings will retain overstory legacy elements consistent with the applicable land use plan (e.g., large fire resilient trees, snags).</E>
                    </P>
                    <P>
                          
                        <E T="03">(iv) Pile burning or underburning of fuels created by covered actions described in subparagraphs (i)-(iii) of this paragraph and fuels within or in close proximity to those actions' treatment boundaries whether created by those actions or not.</E>
                    </P>
                    <P>
                        <E T="03">(v) Seeding or planting necessary to accelerate native species re-establishment.</E>
                    </P>
                    <P>
                        <E T="03">(b) Such actions:</E>
                    </P>
                    <P>
                        <E T="03">(i) Must not exceed 5 miles of new permanent road construction to facilitate the covered actions and all segments must conform to applicable land use planning decisions with route-specific designations disclosed where travel management planning has been completed.</E>
                    </P>
                    <P>
                        <E T="03">(ii) May include maintenance and renovation of existing roads as needed.</E>
                    </P>
                    <P>
                        <E T="03">(iii) May include construction of temporary roads not to exceed a ratio of 2.5 miles per 1,000 acres of treatment area as needed, provided they are not part of the bureau's permanent transportation system, are designed to standards appropriate for their intended use (safety, erosion control, sedimentation prevention, and resource protection), are not needed for long-term resource management, and are decommissioned and stabilized after use to minimize erosion and protect water quality.</E>
                    </P>
                    <P>
                        <E T="03">(iv) Must disclose design features in documentation of finding that an action is excluded pursuant to the use of this categorical exclusion that address the following resource considerations, consistent with applicable land use plan decisions, or, where no plan requirements apply, and specify how these considerations are addressed:</E>
                    </P>
                    <P>
                        <E T="03">(1) Snag and downed wood—amount to be created or retained;</E>
                    </P>
                    <P>
                        <E T="03">(2) Erosion control—specifications or measures (e.g., water bars, dispersed slash);</E>
                    </P>
                    <P>
                        <E T="03">(3) Soil compaction—criteria for avoidance, minimization, or remediation;</E>
                    </P>
                    <P>
                        <E T="03">(4) Logging systems—types and scope of constraints e.g., seasonal, location, extent, etc.);</E>
                    </P>
                    <P>
                        <E T="03">(5) Seasonal operations—purpose and extent of operating restrictions;</E>
                    </P>
                    <P>
                        <E T="03">(6) Invasive species—measures to prevent or limit spread;</E>
                    </P>
                    <P>
                        <E T="03">(7) Riparian areas—buffer widths and/or operating restrictions;</E>
                    </P>
                    <P>
                        <E T="03">(8) Prescribed fire—operating constraints for underburning or pile burning; and</E>
                    </P>
                    <P>
                        <E T="03">(9) Temporary roads—decommissioning standards.</E>
                    </P>
                    <P>
                          
                        <E T="03">(c) Definitions:</E>
                    </P>
                    <P>
                        <E T="03">(i) Permanent road: A road constructed or reconstructed and managed as part of the bureau's permanent transportation system.</E>
                    </P>
                    <P>
                        <E T="03">(ii) Temporary road: A road authorized by contract, permit, lease, written authorization, or emergency operation, not added to the permanent system, and decommissioned after use.</E>
                    </P>
                    <P>
                        <E T="03">(iii) Group selection: An uneven-aged harvest method where groups of trees are removed to promote spatial heterogeneity, regeneration of desired tree species, or the establishment of new cohorts.</E>
                    </P>
                    <STARS/>
                </EXTRACT>
                <P>
                    <E T="03">Authority:</E>
                     NEPA, the National Environmental Policy Act of 1969, as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Stephen G. Tryon,</NAME>
                    <TITLE>Director, Director, Office of Environmental Policy and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06602 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-27-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[A2407-014-004-065516; #O2412-014-004-047181.1; LLHQ220000]</DEPDOC>
                <SUBJECT>National Environmental Policy Act Implementing Procedures for the Bureau of Land Management</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces a proposed revision to the National Environmental Policy Act (NEPA) implementing procedures for the Bureau of Land Management (BLM) at DOI Handbook of NEPA Implementing Procedures (DOI NEPA Handbook) that supplements Chapter 1 of Part 516 of the Department of the Interior's (Department or DOI) Departmental Manual (516 DM 1). The proposed revision would both restore and amend a previously finalized categorical exclusion (CE) for timber salvage harvest in the 
                        <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments on or before May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on this Notice or the associated substantiation report may be submitted electronically to 
                        <E T="03">BLM National NEPA Register: https://eplanning.blm.gov</E>
                         and search for 
                        <E T="03"> DOI-BLM-HQ-2000-2026-0002-OTHER_NEPA,</E>
                         or by mail to Wade Salverson, Forestry Lead, Division of Forest, Rangeland and Vegetation Resources, at the Idaho State Office 1387 S Vinnell Way Boise, ID 83709. The substantiation report for the previously published CE can be found at 85 FR 79517 published on December 10, 2020.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Wade Salverson, Forestry Lead, Division of Forest, Rangeland and Vegetation Resources, at (202) 849-0990, or 
                        <E T="03">wsalvers@blm.gov.</E>
                         Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The BLM manages roughly 248 million surface acres of public land predominantly in the West, of which an estimated 58 million acres are forested/woodlands. The BLM estimates that roughly 2 million acres of dead or dying timber is on BLM-managed lands. According to Black's Law Dictionary, the word “salvage” refers to the rescue of property from loss, such as from a wreck, fire, or other destruction. Salvage timber operations pertain to the harvesting of dead or dying trees suffering from destruction by fire, insects, disease, drought or other disturbances. Black's Law Dictionary 1610 (12th ed. 2024). Consistent with that definition, BLM has long used the practice of harvesting dead or dying trees impacted by biotic or abiotic disturbances, commonly referred to as “salvage harvest” to improve forest conditions by accelerating reestablishment of native resilient forest tree species, reducing wildfire fuel loads, as well as helping recover economic value from timber to contribute to rural economies. The increasing frequency of complex fires on public lands and their threat to human life and property in the wildland urban interface has prompted BLM to review existing programs and identify measures that would better enable wildfire 
                    <PRTPAGE P="17303"/>
                    preparedness. On June 2, 2020, BLM published a proposal for a new CE for authorization of the salvage harvest of dead or dying trees, 85 FR 79517. The 2020 proposed CE expanded the acreage of dead timber that could be harvested from an existing salvage CE that had been promulgated in 2003 by the United States Forest Service and had been administratively established by BLM in 2007. The existing CE for salvage harvest limited BLM to 250 acres or less of total disturbance, and limited BLM to no more than 0.5 mile of temporary road construction for the salvage operations. The 2020 proposed CE increased the threshold to harvest areas of up to 5,000 acres and increased permanent roads to not exceed 1 mile to facilitate the proposed salvage operations. The 2020 Verification report stated that from 2000 to 2017, an average of 6.8 million acres burned annually in the United States, with fire affecting on average 279,630 acres of BLM-managed forests annually from 2009 through 2018 (85 FR 33697, 33699). The BLM provided 30 days of public review and comment on the proposed CE and the associated Verification Report and received a total of 318 comments. On December 10, 2020, BLM finalized this CE for the salvage harvest of dead or dying trees, 85 FR 79,517. The final CE decreased the upper limit of the harvest size from 5,000 acres to 3,000 acres and made several other minor revisions. According to National Interagency Fire Center (NIFC) data (National Centers for Environmental Information [NCEI], 2026, 
                    <E T="03">https://www.ncei.noaa.gov/access/monitoring/wildfires/12/6</E>
                    ), in 2021 the United States hit the highest number of acres burned since 2006, with a total of 10,325,514 acres burned. However, in August 2022, BLM issued an Instruction Memorandum (IM) instructing BLM offices to discontinue the use of the 2020 CE for salvage timber sales due to the “complexity of land management and other matters.” The BLM subsequently removed the 2020 CE from the Department's NEPA procedures in 2024 for similar reasons. 89 FR 84928 (Oct. 24, 2024). Neither the 2022 IM nor the 2024 Notice asserted that it was used incorrectly or other than as intended. On June 3, 2023, the Fiscal Responsibility Act of 2023 was enacted into law, revising NEPA for the first time in over 50 years. The revisions included codification of deadlines and page limits for the preparation of NEPA documents by federal agencies, procedures for determining level of review and adoption of categorical exclusions, as well as a number of other reforms that further demonstrate that the goal of NEPA is to “inform agency decisionmaking, not to paralyze it.” 
                    <E T="03">Seven County Infrastructure Coalition</E>
                     v. 
                    <E T="03">Eagle County., Colo.,</E>
                     605 U.S. 168, 173 (2025). The Fiscal Responsibility Act codified in law the definition of a categorical exclusion as “. . . a category of actions that a Federal agency has determined normally does not significantly affect the quality of the human environment within the meaning of section 102(2)(C).” 42 U.S.C. 4336e(1).
                </P>
                <P>
                    Upon further review and in recognition of the increasing frequency, acreage, and complexity of wildfires in the United States, and as explained in more detail in this notice, the Department has determined it is appropriate to restore and revise the December 2020 categorical exclusion. Proposed CE number C (10) would cover harvest of dead or dying trees impacted by biotic or abiotic disturbances commonly referred to as “salvage harvest” on harvest areas of up to 5,000 acres. The use of the CE will enable land managers to more promptly conduct salvage harvest operations on a greater amount of acreage. This, in turn, will enable land managers to reduce timeframes and conduct more salvage timber operations that will reduce future wildfire fuel loads and hazards to wildland firefighters, the public, and infrastructure from dead and dying trees while also recovering economic value from timber, and contributing to rural economies. The current BLM Verification report notes that from 2000 to 2024, the average acres burned annually has grown to 7.3 million acres in the United States, with wildfire affecting an annual average of 236,530 acres of BLM-managed lands between 2009 and 2025. The BLM notes that the existing 250-acre limitation for categorically excluded salvage timber operations has proved insufficient to address the growing need for BLM to authorize greater salvage harvests over greater acreage. One 5,000-acre salvage timber sale represents 0.0025 (or 
                    <FR>1/4</FR>
                     of 1%) of the estimated 2,000,000 acres of dead or dying timber managed by BLM today. BLM needs to address the 2,000,000 acres of dead or dying timber in BLM lands, and larger-acre projects would allow the agency to achieve this goal more effectively. The BLM's NEPA records show that timber salvage projects of up to 5,000 acres normally do not significantly affect the quality of the human environment. Moreover, BLM records show that from 1986 through 2024 the BLM awarded approximately 982 timber sales where at least 30 percent of the volume consisted of salvage from dead or dying trees, and 936 of those timber sales had at least 50 percent salvage volume. The BLM approved these timber sales in reliance on environmental assessments (EAs) that supported Findings of No Significant Impact (FONSIs) or on CEs. This data together indicate that salvage implementation with no significant environmental impacts is routine for BLM.
                </P>
                <P>
                    This proposed CE would also allow BLM more flexibility to quickly respond to disturbances across larger areas to provide for public and infrastructure safety, reduce hazardous fuel loads that impact firefighters and public safety, and contribute to one of the six principal or major uses of the public lands identified in the Federal Land Policy and Management Act of 1976, which recognizes “the Nation's need for domestic sources of timber and fiber.” In addition to analysis through EAs and environmental impact statements (EISs), BLM already relies upon its existing CE (C.8) that addresses salvage harvest not to exceed 250 acres and intends to retain that CE; BLM is proposing this additional CE to increase its flexibility to respond to disturbances across larger areas. Based on review of BLM's use of the existing CE C.8 as part of this process, BLM does not intend to remove the 250-acre CE nor revise that CE to encompass the proposed scope of actions described in this proposal. The BLM sees a need for both CE categories. The 250-acre CE provides a more limited scope of actions that are useful, and the BLM has used the CE about 10 times a year for the last 10 years. The BLM expects existing CE C.8 would still be used for smaller areas where BLM has no need for the additional tools this proposed CE would provide. Following years of experience in conducting salvage harvest without significant effects, BLM has identified that establishing a CE for the action is necessary to increase BLM's flexibility to respond to disturbances across larger areas, while keeping the tailored focus of the action. Further, this CE will provide an additional tool to facilitate sound forest management in accordance with Executive Order 14225, 
                    <E T="03">Immediate Expansion of American Timber Production,</E>
                     90 FR 11365 (March 1, 2025).
                </P>
                <P>
                    Establishing the proposed CE would enable BLM to ensure a timely process for a timber salvage project prior to a new fire season and in preparation for the subsequent fire season. Since the similar CE originally took effect in December 2020, from 2021 to 2024, a total of 249,450 fires took place, burning 26,321,620 acres of land with a federal 
                    <PRTPAGE P="17304"/>
                    nexus. Further, between January 1, 2025, and November 28, 2025, 4,927,904 acres burned due to wildfires on federal land. Establishing this CE for use by BLM will assist in reducing fuel loads to battle these unprecedented and destructive fires, and will aid in keeping the American people safe.
                </P>
                <P>
                    NEPA, 42 U.S.C. 4321 
                    <E T="03">et seq.,</E>
                     requires Federal agencies to consider the environmental effects of their proposed actions in their decision-making processes and inform and engage the public in that process.
                </P>
                <P>To comply with NEPA, agencies determine the appropriate level of review of any major Federal action—an EIS, EA, or a CE. See generally, 42 U.S.C. 4336 (b); 43 CFR part 46; DOI NEPA Handbook section 1.2 (2025). Where it is reasonably foreseeable that significant environmental effects are likely, the agency must prepare an EIS and document its decision. See generally, 42 U.S.C. 4336 (b)(1); DOI NEPA Handbook section 1.2(a)(5)(ii). Where appropriate, an agency may prepare an environmental assessment, and if it reaches a FONSI, it need not prepare an EIS. See generally, 42 U.S.C. 4336(b)(2); DOI NEPA Handbook section 1.6; section 1.2(a)(4).</P>
                <P>Under NEPA, agencies may establish categorical exclusions—categories of actions that the agency has determined normally do not significantly affect the quality of the human environment—in their agency NEPA implementing procedures (42 U.S.C. 4336e(1)). An agency may also adopt a CE listed in another agency's NEPA procedures consistent with section 109 of NEPA (42 U.S.C. 4336c).</P>
                <P>Under the Department's NEPA procedures, if a bureau determines that a CE covers a proposed action, it then evaluates the proposed action for extraordinary circumstances, which are factors or circumstances that indicate a normally categorically excluded action may have a significant effect (43 CFR 46.205, 46.215). If the bureau cannot categorically exclude the proposed action following review for extraordinary circumstances, it will prepare an EA or EIS, as appropriate, before issuing any decision to authorize the action (43 CFR 46.205(c), 42 U.S.C. 4336(b)).</P>
                <P>
                    The BLM is proposing to establish this new CE by substantiating the proposed new CE with sufficient information to conclude that the actions included in the category normally do not significantly affect the quality of the human environment and provides this substantiation in a written record that is publicly available (see 
                    <E T="02">Addresses</E>
                    ). In developing this proposed CE, the BLM consulted with CEQ in accordance with 42 U.S.C. 4332(2)(B) and is providing notification to and soliciting comment from the public about the proposed establishment of the CE through this notice.
                </P>
                <HD SOURCE="HD1">II. Categorical Exclusion Justification</HD>
                <P>The BLM finds that the type of actions described in this proposed CE normally do not significantly affect the quality of the human environment. This finding is based on the BLM's analysis of these types of actions as documented in the BLM's Substantiation Report for this new CE and supporting documents. The Substantiation Report explains that because the restrictions on the actions included in the CE limit surface disturbance and access road construction, the BLM concludes that the types of actions included in this proposed CE normally do not result in significant environmental effects and therefore warrant establishment of the CE. The Substantiation Report summarizes the review of 34 timber salvage harvest EAs that supported FONSIs to demonstrate the finding that actions included in the proposed CE normally would not significantly affect the quality of the human environment. The Substantiation Report documents evaluation of the BLM NEPA analyses and post-implementation observations as well as available scientific research on the effects of routine actions included in the new proposed CE over time and over different geographic areas.</P>
                <P>
                    The Department and the BLM consulted with CEQ on the Substantiation Report for the proposed CE consistent with section 102(2)(B) of NEPA, 42 U.S.C. 4332(2)(B). If finalized, the Department would add this CE to the BLM's NEPA procedures, in its 
                    <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions.</E>
                     As with other administratively established CEs for Department bureaus, when applying this CE, Responsible Officials would evaluate proposed actions eligible for this CE to determine whether any extraordinary circumstances are present in accordance with the requirements in the Department's NEPA implementing procedures at 43 CFR 46.205 and 46.215. The Responsible Official would document this review and, for BLM, include this documentation in the information posted on the BLM's NEPA register website. If the Responsible Official cannot use this CE to support a decision to authorize timber salvage harvest activities due to extraordinary circumstances, the Responsible Official will prepare an EA or EIS before authorizing such activities, consistent with 43 CFR 46.205(c) and 42 U.S.C. 4336(b).
                </P>
                <HD SOURCE="HD1">III. Text for the Departmental Handbook of NEPA Implementing Procedures</HD>
                <P>
                    The Department's NEPA procedures are proposed to be modified as follows. The 
                    <E T="03">DOI Handbook of NEPA Implementing Procedures, Appendix 2: Bureau Categorical Exclusions</E>
                     would include the following language:
                </P>
                <EXTRACT>
                    <STARS/>
                    <HD SOURCE="HD1">Bureau of Land Management</HD>
                    <HD SOURCE="HD2">11.9 Actions Eligible for a Categorical Exclusion (CE)</HD>
                    <STARS/>
                    <HD SOURCE="HD3">C. Forestry</HD>
                    <P>
                        <E T="03">
                            (10) * Salvage harvesting of dead and dying trees resulting from fire, insects, disease, drought, or other disturbances, not to exceed 1,000 acres where the disturbance affects 3,000 acres of bureau-managed lands or less, and not to exceed the lesser of 5,000 acres or 
                            <FR>1/3</FR>
                             of the disturbance area where the disturbance exceeds 3,000 acres of bureau-managed lands. All actions must be in conformance with applicable land use planning decisions.
                        </E>
                    </P>
                    <P>
                        <E T="03">(a) Covered actions:</E>
                    </P>
                    <P>
                        <E T="03">(i) Cutting, yarding, and removal of dead or dying trees.</E>
                    </P>
                    <P>
                        <E T="03">(ii) Cutting, yarding, and removal of live trees needed for operations, landings, skid trails, or road clearing,</E>
                    </P>
                    <P>
                        <E T="03">(iii) Chipping/grinding or removal of residual slash.</E>
                    </P>
                    <P>
                        <E T="03">(iv) Jackpot burning, pile burning, and underburning.</E>
                    </P>
                    <P>
                        <E T="03">(v) Seeding or planting necessary to accelerate native species re-establishment.</E>
                    </P>
                    <P>
                        <E T="03">(b) Such actions:</E>
                    </P>
                    <P>
                        <E T="03">(i) Must not exceed 1 mile of permanent road construction to facilitate the covered actions, and all segments must conform to applicable land use planning decisions with route-specific designations disclosed where travel management planning has been completed.</E>
                    </P>
                    <P>
                        <E T="03">(ii) May include maintenance and renovation of existing roads as needed.</E>
                    </P>
                    <P>
                        <E T="03">(iii) May include construction of temporary roads not to exceed a ratio of 2.25 miles per 1,000 acres of harvest area as needed, provided they are not part of the bureau's permanent transportation system, are designed to standards appropriate for their intended use (safety, erosion control, sedimentation prevention, and resource protection), are not needed for long-term resource management, and are decommissioned and stabilized after use to minimize erosion and protect water quality.</E>
                    </P>
                    <P>
                        <E T="03">(iv) Must disclose design features in documentation for use of this categorical exclusion that address the following resource considerations, consistent with applicable land use plan decisions, or where no plan requirements apply, and specify how these considerations are addressed:</E>
                    </P>
                    <P>
                        <E T="03">(1) Snag and downed wood—amount to be created or retained;</E>
                        <PRTPAGE P="17305"/>
                    </P>
                    <P>
                        <E T="03">(2) Erosion control—specifications or measures (e.g., water bars, dispersed slash);</E>
                    </P>
                    <P>
                        <E T="03">(3) Soil compaction—criteria for avoidance, minimization, or remediation;</E>
                    </P>
                    <P>
                        <E T="03">(4) Logging systems—types and scope of constraints (e.g., seasonal, location, extent, etc.);</E>
                    </P>
                    <P>
                        <E T="03">(5) Seasonal operations—purpose and extent of operating restrictions;</E>
                    </P>
                    <P>
                        <E T="03">(6) Invasive species—measures to prevent or limit spread;</E>
                    </P>
                    <P>
                        <E T="03">(7) Riparian areas—buffer widths and/or operating restrictions;</E>
                    </P>
                    <P>
                        <E T="03">(8) Prescribed fire—operating constraints for underburning or pile burning; and</E>
                    </P>
                    <P>
                        <E T="03">(9) Temporary roads—decommissioning standards.</E>
                    </P>
                    <P>
                        <E T="03">(c) Definitions:</E>
                    </P>
                    <P>
                        <E T="03">(i) Dying tree: A standing tree severely damaged by disturbance (e.g., fire, wind, insects, disease, drought) and, in the judgment of a forestry professional or someone technically trained for the work, is likely to die within two years.</E>
                    </P>
                    <P>
                        <E T="03">(ii) Permanent road: A road constructed or reconstructed for use, as part of the bureau's permanent transportation system.</E>
                    </P>
                    <P>
                        <E T="03">(iii) Temporary road: A road authorized by contract, permit, lease, written authorization, or emergency operation, not added to the permanent system, and decommissioned after use.</E>
                    </P>
                    <STARS/>
                </EXTRACT>
                <P>
                    <E T="03">Authority:</E>
                     NEPA, the National Environmental Policy Act of 1969, as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <NAME>Stephen G. Tryon,</NAME>
                    <TITLE>Director, Director, Office of Environmental Policy and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06603 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-27-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[NM-106385733]</DEPDOC>
                <SUBJECT>Notice of Cancellation of Withdrawal Application for the Upper Pecos River Watershed Protection Area, New Mexico</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Land Management (BLM) and the U.S. Department of Agriculture, Forest Service (USFS) announce the cancellation of their joint Upper Pecos River Watershed Area withdrawal application for 163,483 acres of National Forest System lands and 1,327.16 acres of public lands in northern New Mexico. The segregation initiated by publication of notice of the withdrawal application will terminate by operation of law 30 days after publication of this Notice at the time listed below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This segregation terminated by this Notice will occur at 8 a.m., local time, on May 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jillian Aragon, Project Manager, BLM New Mexico State Office by email at 
                        <E T="03">jgaragon@blm.gov.</E>
                         Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services for contacting Ms. Aragon. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A Notice of Proposed Withdrawal was published in the 
                    <E T="04">Federal Register</E>
                     on December 16, 2024 (89 FR 101621), announcing the agencies' joint application requesting a withdrawal of 164,810.16 acres of National Forest System lands and public lands in New Mexico from location and entry under the United States mining laws, and leasing under the mineral and geothermal leasing laws, subject to valid existing rights, for a period of 20 years. In accordance with 43 CFR 2310.1-4(a), the agencies have canceled their withdrawal application. The agencies have reviewed the proposal in accordance with Department of the Interior's Secretary's Order 3418 implementing Executive Order 14154 
                    <E T="03">Unleashing American Energy</E>
                     and have determined that the withdrawal application area would be better managed to achieve evolving national policy objectives under existing authorities and land management plans, as both agencies have established provisions to address and minimize impacts to the landscape from both leasing mineral and geothermal resources and from mining. Pursuant to 43 CFR 2310.2-1(d), the temporary segregation for the lands described in 89 FR 101621 is terminated by operation of law and the lands will be opened to location and entry under the United States mining laws and leasing under the mineral and geothermal leasing laws, subject to valid existing rights, the provision of existing withdrawals, other segregations of record, and the requirements of applicable law at 8 a.m., local time, on May 6, 2026. This cancellation notice was processed in accordance with the regulations set forth in 43 CFR part 2300.
                </P>
                <EXTRACT>
                    <FP>(Authority: 43 U.S.C. 1714).</FP>
                </EXTRACT>
                <SIG>
                    <NAME>William F. Groffy,</NAME>
                    <TITLE>Principal Deputy Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06658 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1496]</DEPDOC>
                <SUBJECT>Certain Display Devices, Streaming Players, and Components Thereof; Notice of Institution of Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that a complaint was filed with the U.S. International Trade Commission on March 2, 2026, under section 337 of the Tariff Act of 1930, as amended, on behalf of InnoTV Labs, LLC of Las Vegas, Nevada. A supplement to the complaint was filed on March 17, 2026. The complaint, as supplemented, alleges violations of section 337 based upon the importation into the United States, the sale for importation, and the sale within the United States after importation of certain display devices, streaming players, and components thereof by reason of the infringement of certain claims of U.S. Patent No. 7,965,918 (“the '918 patent”); U.S. Patent No. 12,096,066 (“the '066 patent”); U.S. Patent No. 10,018,863 (“the '863 patent”); U.S. Patent No. RE50,251 (“the '251 patent”); U.S. Patent No. 11,714,306 (“the '306 patent”); and U.S. Patent No. 12,038,636 (“the '636 patent”). The complaint further alleges that an industry in the United States exists as required by the applicable Federal Statute. The complainant requests that the Commission institute an investigation and, after the investigation, issue a limited exclusion order and cease and desist orders.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The complaint, except for any confidential information contained therein, may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         Hearing impaired individuals are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at (202) 205-2000. General information concerning 
                        <PRTPAGE P="17306"/>
                        the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Susan Orndoff, The Office of the Secretary, Docket Services Division, U.S. International Trade Commission, telephone (202) 205-1802.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Authority:</E>
                     The authority for institution of this investigation is contained in section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, and in section 210.10 of the Commission's Rules of Practice and Procedure, 19 CFR 210.10 (2025).
                </P>
                <P>
                    <E T="03">Scope of Investigation:</E>
                     Having considered the complaint, the U.S. International Trade Commission, on April 1, 2026, 
                    <E T="03">ordered that</E>
                    —
                </P>
                <P>(1) Pursuant to subsection (b) of section 337 of the Tariff Act of 1930, as amended, an investigation be instituted to determine whether there is a violation of subsection (a)(1)(B) of section 337 in the importation into the United States, the sale for importation, or the sale within the United States after importation of certain products identified in paragraph (2) by reason of infringement of one or more of claims 3-8, 10-20, 22, and 24 of the '918 patent; claims 1, 4-8, 10, and 11 of the '066 patent; claims 1-8, 11-16, and 21 of the '863 patent; claims 1-3, 10, 25-27, 31, 32, and 36-39 of the '251 patent; claims 1-5, 10-13, and 16-20 of the '306 patent; and claims 1-5, 9, 11, 12, 17-20, 22, and 28 of the '636 patent, and whether an industry in the United States exists as required by subsection (a)(2) of section 337;</P>
                <P>(2) Pursuant to section 210.10(b)(1) of the Commission's Rules of Practice and Procedure, 19 CFR 210.10(b)(1), the plain language description of the accused products or category of accused products, which defines the scope of the investigation, is “smart televisions, LED televisions, streaming devices, and hardware and software components thereof”;</P>
                <P>(3) For the purpose of the investigation so instituted, the following are hereby named as parties upon which this notice of investigation shall be served:</P>
                <P>(a) The complainant is:</P>
                <FP SOURCE="FP-1">InnoTV Labs, LLC, 732 S 6th St # 8058, Las Vegas, NV 89101</FP>
                <P>(b) The respondents are the following entities alleged to be in violation of section 337, and are the parties upon which the complaint is to be served:</P>
                <FP SOURCE="FP-1">Hisense Co., Ltd., 17 Donghai West Road, Shinan, Qingdao, 266071, China</FP>
                <FP SOURCE="FP-1">Hisense International Co., Ltd., 218 Qianwangang Road, Economic and Technological Development Zone, Qingdao, 266555, China</FP>
                <FP SOURCE="FP-1">Hisense Visual Technology Co., Ltd., 218 Qianwangang Road, Economic and Technological Development Zone, Qingdao, 266555, China</FP>
                <FP SOURCE="FP-1">Hisense USA Corporation, 7310 McGinnis Ferry Road, Suwanee, GA 30024</FP>
                <FP SOURCE="FP-1">Hisense Electronics Manufacturing Company of America Corporation, 7310 McGinnis Ferry Rd., Suwanee, GA 30024</FP>
                <FP SOURCE="FP-1">Hisense Monterrey Home Appliance Manufacturing, S. de R.L. de C.V., Av. Puerta Grande No. 1301, Hofusan Industrial Park, Salinas Victoria, Nuevo Leon, 65330 Mexico</FP>
                <FP SOURCE="FP-1">Roku, Inc., 1173 Coleman Avenue, San Jose, CA 95110</FP>
                <FP SOURCE="FP-1">Purple Tag Media Technology (Shanghai) Ltd., 10/F, Central Park Jing'an, 329 Hengfeng Road, Shanghai, China</FP>
                <FP SOURCE="FP-1">Purple Tag Media Technology (Shanghai) Ltd.—Shenzhen Branch, 5F, China Energy Storage Tower, No. 3099, South Keyuan Road, Nanshan District, Shenzhen, Guangdong, China</FP>
                <FP SOURCE="FP-1">Purple Tag Mexico, S.A. de C.V., Av. P.º de la Reforma 483, Cuauhtémoc, 06500 Ciudad de México, CDMX, Mexico</FP>
                <P>(4) For the investigation so instituted, the Chief Administrative Law Judge, U.S. International Trade Commission, shall designate the presiding Administrative Law Judge.</P>
                <P>The Office of Unfair Import Investigations will not participate as a party in this investigation.</P>
                <P>Responses to the complaint and the notice of investigation must be submitted by the named respondents in accordance with section 210.13 of the Commission's Rules of Practice and Procedure, 19 CFR 210.13. Pursuant to 19 CFR 201.16(e) and 210.13(a), such responses will be considered by the Commission if received not later than 20 days after the date of service by the Commission of the complaint and the notice of investigation. Extensions of time for submitting responses to the complaint and the notice of investigation will not be granted unless good cause therefor is shown.</P>
                <P>Failure of a respondent to file a timely response to each allegation in the complaint and in this notice may be deemed to constitute a waiver of the right to appear and contest the allegations of the complaint and this notice, and to authorize the administrative law judge and the Commission, without further notice to the respondent, to find the facts to be as alleged in the complaint and this notice and to enter an initial determination and a final determination containing such findings, and may result in the issuance of an exclusion order or a cease and desist order or both directed against the respondent.</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: April 1, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06580 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation Nos. 701-TA-506 and 508 and 731-TA-1238-1243 (Second Review)]</DEPDOC>
                <SUBJECT>Non-Oriented Electrical Steel From China, Germany, Japan, South Korea, Sweden, and Taiwan; Scheduling of Expedited Five-Year Reviews</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P> United States International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P> The Commission hereby gives notice of the scheduling of expedited reviews pursuant to the Tariff Act of 1930 (“the Act”) to determine whether revocation of the antidumping duty and countervailing duty orders on non-oriented electrical steel (“NOES”) from China, Germany, Japan, South Korea, Sweden, and Taiwan would be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> March 6, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         Camille Bryan (202-205-2811), Office of Investigations, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436. Hearing-impaired persons can obtain information on this matter by contacting the Commission's TDD terminal on 202-205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at 202-205-2000. General information concerning the Commission may also be obtained by accessing its internet server (
                        <E T="03">https://www.usitc.gov</E>
                        ). The public record for this proceeding may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Background.</E>
                    —On March 6, 2026, the Commission determined that the domestic interested party group response to its notice of institution (90 
                    <PRTPAGE P="17307"/>
                    FR 55159, December 1, 2025) of the subject five-year reviews was adequate and that the respondent interested party group response was inadequate. The Commission did not find any other circumstances that would warrant conducting full reviews.
                    <SU>1</SU>
                    <FTREF/>
                     Accordingly, the Commission determined that it would conduct expedited reviews pursuant to section 751(c)(3) of the Act (19 U.S.C. 1675(c)(3)).
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         A record of the Commissioners' votes, the Commission's statement on adequacy, and any individual Commissioner's statements will be available from the Office of the Secretary and at the Commission's website.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Commissioner Johanson voted to conduct full reviews.
                    </P>
                </FTNT>
                <P>For further information concerning the conduct of these reviews and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A and B (19 CFR part 201), and part 207, subparts A, D, E, and F (19 CFR part 207).</P>
                <P>
                    <E T="03">Staff report.</E>
                    —A staff report containing information concerning the subject matter of the reviews has been placed in the nonpublic record, and will be made available to persons on the Administrative Protective Order service list for these reviews on April 2, 2026. A public version will be issued thereafter, pursuant to § 207.62(d)(4) of the Commission's rules.
                </P>
                <P>
                    <E T="03">Written submissions.</E>
                    —As provided in § 207.62(d) of the Commission's rules, interested parties that are parties to the reviews and that have provided individually adequate responses to the notice of institution,
                    <SU>3</SU>
                    <FTREF/>
                     and any party other than an interested party to the reviews may file written comments with the Secretary on what determination the Commission should reach in the reviews. Comments are due on or before April 15, 2026 and may not contain new factual information. Any person that is neither a party to the five-year reviews nor an interested party may submit a brief written statement (which shall not contain any new factual information) pertinent to the reviews by April 15, 2026. However, should the Department of Commerce (“Commerce”) extend the time limit for its completion of the final results of its reviews, the deadline for comments (which may not contain new factual information) on Commerce's final results is three business days after the issuance of Commerce's results. If comments contain business proprietary information (BPI), they must conform with the requirements of §§ 201.6, 207.3, and 207.7 of the Commission's rules. The Commission's 
                    <E T="03">Handbook on Filing Procedures,</E>
                     available on the Commission's website at 
                    <E T="03">https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf,</E>
                     elaborates upon the Commission's procedures with respect to filings.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Commission has found the responses submitted on behalf of Cleveland-Cliffs Inc. (“Cleveland-Cliffs”) and United States Steel Corporation (“U.S. Steel”) to be individually adequate. Comments from other interested parties will not be accepted (
                        <E T="03">see</E>
                         19 CFR 207.62(d)(2)).
                    </P>
                </FTNT>
                <P>In accordance with §§ 201.16(c) and 207.3 of the rules, each document filed by a party to the reviews must be served on all other parties to the reviews (as identified by either the public or BPI service list), and a certificate of service must be timely filed. The Secretary will not accept a document for filing without a certificate of service.</P>
                <P>
                    <E T="03">Determination.</E>
                    —The Commission has determined these reviews are extraordinarily complicated and therefore has determined to exercise its authority to extend the review period by up to 90 days pursuant to 19 U.S.C. 1675(c)(5)(B).
                </P>
                <P>
                    <E T="03">Authority:</E>
                     These reviews are being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to § 207.62 of the Commission's rules.
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: April 1, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06576 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 337-TA-1452]</DEPDOC>
                <SUBJECT>Certain Ink Cartridges and Components Thereof II; Notice of Request for Submissions on the Public Interest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that on March 24, 2026, the presiding administrative law judge (“ALJ”) issued a Summary Determination on Violation of Section 337. The ALJ also issued a Recommended Determination on remedy and bonding should a violation be found in the above-captioned investigation. The Commission is soliciting submissions on public interest issues raised by the recommended relief should the Commission find a violation. This notice is soliciting comments from the public and interested government agencies only.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Namo Kim, Esq., Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW, Washington, DC 20436, telephone (202) 205-3459. Copies of non-confidential documents filed in connection with this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                         For help accessing EDIS, please email 
                        <E T="03">EDIS3Help@usitc.gov.</E>
                         General information concerning the Commission may also be obtained by accessing its internet server at 
                        <E T="03">https://www.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 337 of the Tariff Act of 1930 provides that, if the Commission finds a violation, it shall exclude the articles concerned from the United States unless, after considering the effect of such exclusion upon the public health and welfare, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, and United States consumers, it finds that such articles should not be excluded from entry. (19 U.S.C. 1337(d)(1)). A similar provision applies to cease and desist orders. (19 U.S.C. 1337(f)(1)).</P>
                <P>The Commission is soliciting submissions on public interest issues raised by the recommended relief should the Commission find a violation, specifically: a general exclusion order directed to certain ink cartridges and components thereof imported, sold for importation, and/or sold after importation; and cease and desist orders directed to respondents Mountain Peak, Inc. and Straightouttaink, LP. Parties are to file public interest submissions pursuant to 19 CFR 210.50(a)(4).</P>
                <P>
                    The Commission is interested in further development of the record on the public interest in this investigation. Accordingly, members of the public and interested government agencies are invited to file submissions of no more than five (5) pages, inclusive of attachments, concerning the public interest in light of the ALJ's Recommended Determination on Remedy and Bonding issued in this investigation on March 24, 2026. Comments should address whether issuance of the recommended remedial orders in this investigation, should the Commission find a violation, would affect the public health and welfare in the United States, competitive conditions in the United States economy, the production of like or 
                    <PRTPAGE P="17308"/>
                    directly competitive articles in the United States, or United States consumers.
                </P>
                <P>In particular, the Commission is interested in comments that:</P>
                <P>(i) explain how the articles potentially subject to the recommended remedial orders are used in the United States;</P>
                <P>(ii) identify any public health, safety, or welfare concerns in the United States relating to the recommended orders;</P>
                <P>(iii) identify like or directly competitive articles that complainant, its licensees, or third parties make in the United States which could replace the subject articles if they were to be excluded;</P>
                <P>(iv) indicate whether complainant, complainant's licensees, and/or third-party suppliers have the capacity to replace the volume of articles potentially subject to the recommended orders within a commercially reasonable time; and</P>
                <P>(v) explain how the recommended orders would impact consumers in the United States.</P>
                <P>Written submissions must be filed no later than by close of business on April 30, 2026.</P>
                <P>
                    Persons filing written submissions must file the original document electronically on or before the deadlines stated above pursuant to 19 CFR 210.4(f). Submissions should refer to the investigation number (“Inv. No. 337-TA-1452”) in a prominent place on the cover page and/or the first page. (
                    <E T="03">See</E>
                     Handbook for Electronic Filing Procedures, 
                    <E T="03">https://www.usitc.gov/secretary/fed_reg_notices/rules/handbook_on_electronic_filing.pdf</E>
                    ). Persons with questions regarding filing should contact the Secretary (202-205-2000).
                </P>
                <P>Any person desiring to submit a document to the Commission in confidence must request confidential treatment by marking each document with a header indicating that the document contains confidential information. This marking will be deemed to satisfy the request procedure set forth in Rules 201.6(b) and 210.5(e)(2) (19 CFR 201.6(b) &amp; 210.5(e)(2)). Documents for which confidential treatment by the Commission is properly sought will be treated accordingly. Any non-party wishing to submit comments containing confidential information must serve those comments on the parties to the investigation pursuant to the applicable Administrative Protective Order. A redacted non-confidential version of the document must also be filed simultaneously with any confidential filing and must be served in accordance with Commission Rule 210.4(f)(7)(ii)(A) (19 CFR 210.4(f)(7)(ii)(A)). All information, including confidential business information and documents for which confidential treatment is properly sought, submitted to the Commission for purposes of this investigation may be disclosed to and used: (i) by the Commission, its employees and Offices, and contract personnel (a) for developing or maintaining the records of this or a related proceeding, or (b) in internal investigations, audits, reviews, and evaluations relating to the programs, personnel, and operations of the Commission including under 5 U.S.C. Appendix 3; or (ii) by U.S. government employees and contract personnel, solely for cybersecurity purposes. All contract personnel will sign appropriate nondisclosure agreements. All nonconfidential written submissions will be available for public inspection on EDIS.</P>
                <P>This action is taken under the authority of section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and in Part 210 of the Commission's Rules of Practice and Procedure (19 CFR part 210).</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: April 1, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06575 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Pre-Implementation Planning Checklist for State Unemployment Insurance Information Technology Modernization Projects</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Labor's (DOL) Employment and Training Administration (ETA) is soliciting comments concerning a proposed extension for the authority to conduct the information collection request (ICR) titled, “Pre-Implementation Planning Checklist for State Unemployment Insurance Information Technology Modernization Projects.” This comment request is part of continuing Departmental efforts to reduce paperwork and respondent burden in accordance with the Paperwork Reduction Act of 1995 (PRA).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all written comments received by June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of this ICR with applicable supporting documentation, including a description of the likely respondents, proposed frequency of response, and estimated total burden, may be obtained free by contacting Jagruti Patel by email at 
                        <E T="03">OUI-PRA@dol.gov.</E>
                    </P>
                    <P>
                        Submit written comments about, or requests for a copy of, this ICR by mail or courier to the U.S. Department of Labor, Employment and Training Administration, Office of Unemployment Insurance, Room S-4524, 200 Constitution Avenue NW, Washington, DC 20210; by email: 
                        <E T="03">OUI-PRA@dol.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Contact Jagruti Patel by email at 
                        <E T="03">OUI-PRA@dol.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>DOL, as part of continuing efforts to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies an opportunity to comment on proposed and/or continuing collections of information before submitting them to the Office of Management and Budget (OMB) for final approval. This program helps to ensure requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements can be properly assessed.</P>
                <P>
                    Building on lessons learned from previous State Workforce Agency (SWA) implementations of modernized Unemployment Insurance (UI) Information Technology (IT) systems, ETA facilitated the development of a UI IT Modernization Pre-Implementation Planning Checklist in 2018, and revised again in 2020 and 2023, for SWAs to use prior to launching a new system. The checklist is intended to function as a validation that all necessary system functions will be available and/or that alternative workarounds have been developed prior to the production launch of a new UI IT system. The goal of the checklist is to help SWAs avoid major disruption of services to UI customers and to prevent delays in making UI benefit payments when due. This comprehensive checklist denotes critical functional areas that SWAs must certify prior to launching new UI IT systems including, but not limited to, technical IT functions and UI business processes that interface with the new system. In this revision, ETA has revised 4 sub-elements of the checklist 
                    <PRTPAGE P="17309"/>
                    to meet administration's priorities. The list of critical areas identified in the checklist includes:
                </P>
                <P>• Functionality and Workarounds;</P>
                <P>• External Alternate Access Options and Usability Issues Addressed;</P>
                <P>• Policies and Procedures;</P>
                <P>• Technical Preparation for System Implementation;</P>
                <P>• Call Center/Customer Service Operations;</P>
                <P>• Business Process;</P>
                <P>• Help Desk;</P>
                <P>• Management Oversight;</P>
                <P>• Vendor Support/Communications;</P>
                <P>• Communication Processes and Procedures; and</P>
                <P>• Labor Market Information Federal Reporting Functions.</P>
                <P>
                    This information includes the UI IT Modernization project title (
                    <E T="03">e.g.,</E>
                     SWA project or Consortium name) and the associated report on Pre-Implementation Planning Checklist results. For each sub-element identified in the ETA 9177 report, the SWA is to provide:
                </P>
                <P>• An overall status report;</P>
                <P>• A brief report explaining the status of the project as it relates to the particular sub-element;</P>
                <P>• Attached explanations of any workarounds concerning the processes in the sub-element;</P>
                <P>• Attached explanations if implementation of the new system concerning specific processes for the sub-element will be delayed or deferred;</P>
                <P>• Attached explanations for added clarity and/or to support a narrative;</P>
                <P>• Mitigation proposals for addressing any problems;</P>
                <P>• New project timelines if applicable; and/or</P>
                <P>• Any discussion of identified technical assistance needs for the successful completion of the project.</P>
                <P>
                    ETA requires the use of this checklist report to help SWAs ensure the availability of mission critical functions as the SWA prepares for the launch of a new system and following the launch of a new system. In addition, the collection will enable ETA to identify and provide appropriate technical assistance on issues in the checklist and ensure SWAs have plans for addressing critical issues prior to launching a new UI IT system. DOL continues to engage with SWAs on possible improvements to the UI IT Modernization Pre-Implementation Planning Checklist. This proposed revision does not reflect that work. Should any changes be proposed as part of that effort, an additional 
                    <E T="04">Federal Register</E>
                     Notice will be published. Section 303(a)(6) of the Social Security Act, codified at 42 U.S.C. 503(a)(6), authorizes this information collection.
                </P>
                <P>
                    This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number. 
                    <E T="03">See</E>
                     5 CFR 1320.5(a) and 1320.6.
                </P>
                <P>
                    Interested parties are encouraged to provide comments to the contact shown in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments must be written to receive consideration, and they will be summarized and included in the request for OMB approval of the final ICR. In order to help ensure appropriate consideration, comments should mention OMB control number 1205-0527.
                </P>
                <P>Submitted comments will also be a matter of public record for this ICR and posted on the internet, without redaction. DOL encourages commenters not to include personally identifiable information, confidential business data, or other sensitive statements/information in any comments.</P>
                <P>DOL is particularly interested in comments that:</P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the Agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, (
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses).
                </P>
                <P>
                    <E T="03">Agency:</E>
                     DOL-ETA.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Pre-Implementation Planning Checklist for State Unemployment Insurance Information Technology Modernization Projects.
                </P>
                <P>
                    <E T="03">Form:</E>
                     ETA 9177.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1205-0527.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, Local, and Tribal Governments.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     71.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Once per incident.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Responses:</E>
                     24.
                </P>
                <P>
                    <E T="03">Estimated Average Time per Response:</E>
                     Varies.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     540 hours.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Other Cost Burden:</E>
                     $0.
                </P>
                <EXTRACT>
                    <FP>(Authority: 44 U.S.C. 3506(c)(2)(A))</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Henry Maklakiewicz,</NAME>
                    <TITLE>Assistant Secretary for Employment and Training, Labor.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06595 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <DEPDOC>[OMB Control No. 1225-0087]</DEPDOC>
                <SUBJECT>Proposed Extension of Information Collection; Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Administration and Management, Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Labor (DOL), as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance request for comment to provide the public and Federal agencies with an opportunity to comment on proposed collections of information in accordance with the Paperwork Reduction Act of 1995. This request helps to ensure that: requested data can be provided in the desired format; reporting burden (time and financial resources) is minimized; collection instruments are clearly understood; and the impact of collection requirements on respondents can be properly assessed. Currently, the Office of the Assistant Secretary for Administration and Management (OASAM) is soliciting comments on the information collection for Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>All comments must be received on or before June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Electronic submission:</E>
                         You may submit comments and attachments electronically at 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. A copy of this ICR with applicable supporting documentation; including a 
                        <PRTPAGE P="17310"/>
                        description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free by contacting Nora Hernandez by telephone at (202) 693-8633 (this is not a toll-free number), or by email at 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov.</E>
                         Submit written comments about, or requests for a copy of, this ICR by mail or courier to the U.S. Department of Labor, Office of the Assistant Secretary for Administration and Management, Room N1301, 200 Constitution Avenue NW, Washington, DC 20210; by email: 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov.</E>
                    </P>
                    <P>All submissions received must include the agency name and OMB Control Number 1225-0087.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nora Hernandez, Departmental Clearance Officer by telephone at 202-693-8633 (this is not a toll-free number), or by email at 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Consistent with 40 U.S.C. 581(h)(2), Federal Management Regulation (FMR) Part 102, Public Law 102-74, Subpart D, and the GSA Delegation under which the Department of Labor (DOL) operates the Frances Perkins Building (FPB), DOL allows the use of public space within the FPB for non-commercial purposes. As provided by FMR 102-74, Subpart D, (41 CFR 102-74-460) any person or entity that wishes to use public space in a Federal building is required to submit an application for a permit. To capture the nature of the request, information such as the requester, description of event, date, time, and approvals are collected in order to review the appropriateness of the request and make a determination of the availability of the requested public space.</P>
                <P>
                    DOL experience shows that the agency receives fewer than 10 non-DOL Agency requests to use FPB public space in any given year; however, as the information is contained in a rule of general applicability, the information collection is deemed to involve 10 or more persons. 
                    <E T="03">See</E>
                     5 CFR 1320.3(c)(4)(ii). DOL, consequently, must maintain PRA authority to conduct this information collection.
                </P>
                <HD SOURCE="HD1">II. Desired Focus of Comments</HD>
                <P>OASAM is soliciting comments concerning the proposed information collection related to the Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building. OASAM is particularly interested in comments that:</P>
                <P>• Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information has practical utility;</P>
                <P>• Evaluate the accuracy of OASAM's estimate of the burden related to the information collection, including the validity of the methodology and assumptions used in the estimate;</P>
                <P>• Suggest methods to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the information collection on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    Background documents related to this information collection request are available at 
                    <E T="03">https://regulations.gov</E>
                     and at DOL-OASAM, located at Office of the Assistant Secretary for Administration and Management, Room N1301, Washington, DC 20210. Questions about the information collection requirements may be directed to the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice.
                </P>
                <HD SOURCE="HD1">III. Current Actions</HD>
                <P>This information collection request concerns Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building. OASAM has updated the data with respect to the number of respondents, responses, burden hours, and burden costs supporting this information collection request from the previous information collection request.</P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     DOL—OASAM.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building.
                </P>
                <P>
                    <E T="03">Form:</E>
                     Application for Use of Public Space by Non-DOL Agencies in the Frances Perkins Building (Form DL1-6062B).
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1225-0087.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Private Sector, not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     10.
                </P>
                <P>
                    <E T="03">Number of Responses:</E>
                     10.
                </P>
                <P>
                    <E T="03">Annual Burden Hours:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Annual Respondent or Recordkeeper Cost:</E>
                     $0.
                </P>
                <P>
                    Comments submitted in response to this notice will be summarized in the request for Office of Management and Budget approval of the proposed information collection request; they will become a matter of public record and will be available at 
                    <E T="03">https://www.reginfo.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 44 U.S.C. 3507(a)(1)(D))</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Nora Hernandez,</NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06594 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-23-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. 50-275 and 50-323; NRC-2023-0192]</DEPDOC>
                <SUBJECT>Pacific Gas and Electric Company; Diablo Canyon Nuclear Power Plant, Units 1 and 2; License Renewal and Record of Decision</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P> Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice; issuance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P> The U.S. Nuclear Regulatory Commission (NRC) has issued Renewed Facility Operating License Nos. DPR-80 and DPR-82 to Pacific Gas and Electric Company (PG&amp;E) for Diablo Canyon Nuclear Power Plant (Diablo Canyon), Units 1 and 2, respectively. In addition, the NRC has prepared a record of decision (ROD) that supports the NRC's decision to issue Renewed Facility Operating License Nos. DPR-80 and DPR-82.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> Renewed Facility Operating License Nos. DPR-80 and DPR-82 were issued on April 2, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> Please refer to Docket ID NRC-2023-0192 when contacting the NRC about the availability of information regarding this document. You may obtain publicly available information related to this document using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2023-0192. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Bridget Curran; telephone: 301-415-1003; email: 
                        <E T="03">Bridget.Curran@nrc.gov</E>
                        . For technical questions, contact the individual listed in the 
                        <E T="02">For Further Information Contact</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                         You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">https://www.nrc.gov/reading-rm/adams.html</E>
                        . To begin the search, select “Begin ADAMS Public Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, at 301-415-4737, or by email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                        . For the convenience of the reader, instructions about obtaining materials referenced in 
                        <PRTPAGE P="17311"/>
                        this document are provided in the “Availability of Documents” section.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's PDR:</E>
                         The PDR, where you may examine and order copies of publicly available documents, is open by appointment. To make an appointment to visit the PDR, please send an email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                         or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern time (ET), Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         Vaughn Thomas, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-5897; email: 
                        <E T="03">Vaughn.Thomas@nrc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Discussion</HD>
                <P>Notice is hereby given that the NRC has issued Renewed Facility Operating License Nos. DPR-80 and DPR-82 to PG&amp;E for Diablo Canyon, Units 1 and 2, respectively. PG&amp;E is the operator of the facility. Renewed Facility Operating License Nos. DPR-80 and DPR-82 authorize PG&amp;E to operate Diablo Canyon, Units 1 and 2, respectively, at reactor core power levels not in excess of 3,411 megawatts thermal, in accordance with the provisions of the Diablo Canyon licenses and technical specifications. Notice is also given that the ROD that supports the NRC's decision to issue Renewed Facility Operating License Nos. DPR-80 and DPR-82 is available, and its location is listed in the “Availability of Documents” section of this document.</P>
                <P>As discussed in the ROD and the final supplemental environmental impact statement (SEIS), published as NUREG-1437, Supplement 62, “Generic Environmental Impact Statement for License Renewal of Nuclear Plants Regarding License Renewal of Diablo Canyon Nuclear Power Plant, Units 1 and 2, Final Report,” dated June 2025, the final SEIS documents the NRC staff's environmental review, including the recommendation that the adverse environmental impacts of license renewal (LR) for Diablo Canyon are not so great that preserving the option of LR for energy-planning decisionmakers would be unreasonable. This recommendation is based on (1) the analysis and findings in the NRC's Generic Environmental Impact Statement for License Renewal of Nuclear Plants, (2) information provided in the environmental report submitted by PG&amp;E, (3) the NRC staff's consultation with Federal, State, Tribal, and local agencies, (4) the NRC staff's independent environmental review, and (5) the NRC staff's consideration of public comments received during the scoping process and on the draft SEIS.</P>
                <P>
                    Diablo Canyon consists of two pressurized-water reactors located in San Luis Obispo County, California, approximately 12 miles west-southwest of San Luis Obispo. PG&amp;E submitted its LR application for Diablo Canyon on November 7, 2023, which it supplemented by letters through February 11, 2026 (see “Availability of Documents” section of this document). The NRC staff has detemined that PG&amp;E's LR application complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the NRC's regulations. As required by the Act and NRC regulations in title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR), the NRC has made appropriate findings, which are set forth in the renewed licenses.
                </P>
                <P>
                    A public notice of the NRC's acceptance for docketing of the LR application and an opportunity to request a hearing was published in the 
                    <E T="03">Federal Register</E>
                     on December 19, 2023 (88 FR 87817).
                </P>
                <P>For further details with respect to this action, see: (1) PG&amp;E's LR application for Diablo Canyon, dated November 7, 2023, as supplemented by letters through February 11, 2026; (2) the NRC's safety evaluation, dated June 2025; (3) the NRC's final SEIS, dated June 2025; and (4) the NRC's ROD, dated April 2, 2026.</P>
                <HD SOURCE="HD1">II. Availability of Documents</HD>
                <P>The documents identified in the following table are available to interested persons through ADAMS, as indicated.</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s200,xs100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Document description</CHED>
                        <CHED H="1">ADAMS accession No.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application, dated November 7, 2023</ENT>
                        <ENT>ML23311A154.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Record of Decision, License Renewal Application for Diablo Canyon Nuclear Power Plant, Units 1 and 2, dated April 2, 2026</ENT>
                        <ENT>ML26022A077.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Safety Evaluation Related to the License Renewal of Diablo Canyon Nuclear Power Plant, Units 1 and 2, dated June 2025</ENT>
                        <ENT>ML25153A508.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NUREG-1437, Supplement 62, “Generic Environmental Impact Statement for License Renewal of Nuclear Plants Regarding License Renewal of Diablo Canyon Nuclear Power Plant, Units 1 and 2, Final Report,” dated June 2025</ENT>
                        <ENT>ML25156A357.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NUREG-1437, Revision 2, Volumes 1, 2, and 3, Generic Environmental Impact Statement for License Renewal of Nuclear Plants, dated August 2024</ENT>
                        <ENT>ML24087A133 (Package).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Supplement 1, dated October 14, 2024</ENT>
                        <ENT>ML24289A118.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Supplement 2, dated March 6, 2025</ENT>
                        <ENT>ML25069A508.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Supplement 3, dated April 24, 2025</ENT>
                        <ENT>ML25114A242.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Supplement 4, dated May 13, 2025</ENT>
                        <ENT>ML25133A223.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Supplement 5, dated February 11, 2026</ENT>
                        <ENT>ML26042A359.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Response to Requests for Additional Information Set 1, dated October 3, 2024</ENT>
                        <ENT>ML24277A067.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Response to Requests for Additional Information Set 2, dated January 2, 2025</ENT>
                        <ENT>ML25002A050.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diablo Canyon Nuclear Power Plant, Units 1 and 2, License Renewal Application—Response to Requests for Additional Information Set 3, dated February 25, 2025</ENT>
                        <ENT>ML25056A500.</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="17312"/>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Michele Sampson,</NAME>
                    <TITLE>Director, Division of New and Renewed Licenses, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06641 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 50-615; NRC-2024-0146]</DEPDOC>
                <SUBJECT>Tennessee Valley Authority; Clinch River Nuclear Site, Unit 1; Final Supplemental Environmental Impact Statement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; issuance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC), in cooperation with the U.S. Army Corps of Engineers, is issuing a final supplemental environmental impact statement (SEIS), “Environmental Impact Statement for a Construction Permit Application at the Clinch River Nuclear Site: Final Report.” The NRC is issuing this final SEIS as part of its review of the application submitted by Tennessee Valley Authority (TVA) for a construction permit (CP) for one GE Vernova Hitachi BWRX-300 small modular reactor (SMR) at a site in Roane County, Tennessee, designated as Clinch River Nuclear Site, Unit 1 (CRN-1). TVA plans to construct and operate CRN-1 to demonstrate the feasibility of constructing and operating the BWRX-300 SMR. The final SEIS evaluates the environmental impacts of the proposed action of issuing a CP that would allow the construction of CRN-1, as well as the environmental impacts of alternatives to the proposed action.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The final SEIS is available as of April 1, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please refer to Docket ID NRC-2024-0146 when contacting the NRC about the availability of information regarding this document. You may obtain publicly available information related to this document using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2024-0146. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Bridget Curran; telephone: 301-415-1003; email: 
                        <E T="03">Bridget.Curran@nrc.gov.</E>
                         For technical questions, contact the individual listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                         You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                         To begin the search, select “Begin ADAMS Public Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, at 301-415-4737, or by email to 
                        <E T="03">PDR.Resource@nrc.gov.</E>
                         The final SEIS is available in ADAMS under Accession No. ML26035A285. The ADAMS accession number for each document referenced (if it is available in ADAMS) is provided the first time that it is mentioned in this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's PDR:</E>
                         The PDR, where you may examine and order copies of publicly available documents, is open by appointment. To make an appointment to visit the PDR, please send an email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                         or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern time, Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Project Website:</E>
                         The final SEIS will also be available online at the CRN-1 project website at 
                        <E T="03">https://www.nrc.gov/reactors/new-reactors/advanced/who-were-working-with/applicant-projects/clinch-river.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Madelyn Nagel, Office of Nuclear Material Safety and Safeguards, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-3470; email: 
                        <E T="03">Madelyn.Nagel@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    By letters dated April 28, 2025 (ADAMS Accession No. ML25118A209) and May 20, 2025 (ADAMS Package Accession No. ML25140A062), TVA submitted to the NRC, pursuant to section 103 of the Atomic Energy Act of 1954, as amended, and part 50 of title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR), “Domestic Licensing of Production and Utilization Facilities,” an application for a CP that would allow the construction of CRN-1 in Roane County, Tennessee. The proposed facility would house one GE Vernova Hitachi BWRX-300 SMR. This submission initiated the proposed Federal action of determining whether to issue the requested CP. A notice of receipt and availability of the CP application was published in the 
                    <E T="04">Federal Register</E>
                     on June 10, 2025 (90 FR 24425). A notice of acceptance for docketing of the complete application and opportunity to request a hearing was published in the 
                    <E T="04">Federal Register</E>
                     on July 15, 2025 (90 FR 31709). A notice of intent to prepare a supplement to the early site permit environmental impact statement (EIS) was published on July 18, 2025 (90 FR 34015).
                </P>
                <P>
                    As set forth in 10 CFR 51.20(b), issuance of a CP to construct a nuclear power reactor is an action that requires an EIS or a supplement to an EIS. This notice is being published in accordance with the National Environmental Policy Act of 1969, as amended (NEPA), and the NRC's regulations implementing NEPA at 10 CFR part 51, “Environmental Protection Regulations for Domestic Licensing and Related Regulatory Functions.” In addition, pursuant to section 800.8(c) of title 36 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (36 CFR), the NRC used the process and documentation for the preparation of the SEIS to comply with section 106 of the National Historic Preservation Act of 1966, as amended, in lieu of the procedures set forth in 36 CFR 800.3 through 800.6.
                </P>
                <P>
                    A notice of availability and request for comment on the draft SEIS was published in the 
                    <E T="04">Federal Register</E>
                     on November 7, 2025 (90 FR 50498). The public comment period on the draft SEIS ended on December 22, 2025, and the comments received on the draft SEIS are addressed in the final SEIS.
                </P>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>As discussed in the final SEIS, after weighing the environmental, economic, technical, and other benefits against environmental and other costs, and considering reasonable alternatives, the recommendation is, unless safety issues mandate otherwise, that the NRC issue the requested CP to TVA. This recommendation is based on the CP application, information gathered during the environmental audit, and responses to requests for clarifying information; consultation with Federal, State, Tribal, and local agencies; the independent environmental review and assessment summarized in the final SEIS; and consideration of public comments received on the draft SEIS. In addition, no environmentally preferable alternatives that meet the purpose and need for the proposed action were identified; therefore, there is no obvious superior alternative to the proposed action from an environmental perspective.</P>
                <SIG>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <PRTPAGE P="17313"/>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Jacob Zimmerman,</NAME>
                    <TITLE>Acting Director, Division of Rulemaking, Environmental, and Financial Support, Office of Nuclear Material Safety and Safeguards.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06571 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. K2025-6; MC2026-185 and K2026-185; MC2026-186 and K2026-186; MC2026-187 and K2026-187]</DEPDOC>
                <SUBJECT>New Postal Products</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission is noticing a recent Postal Service filing for the Commission's consideration concerning a negotiated service agreement. This notice informs the public of the filing, invites public comment, and takes other administrative steps.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments are due:</E>
                         April 9, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically via the Commission's Filing Online system at 
                        <E T="03">https://www.prc.gov.</E>
                         Those who cannot submit comments electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section by telephone for advice on filing alternatives.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Introduction</FP>
                    <FP SOURCE="FP-2">II. Public Proceeding(s)</FP>
                    <FP SOURCE="FP-2">III. Summary Proceeding(s)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>Pursuant to 39 CFR 3041.405, the Commission gives notice that the Postal Service filed request(s) for the Commission to consider matters related to Competitive negotiated service agreement(s). The request(s) may propose the addition of a negotiated service agreement from the Competitive product list or the modification of an existing product currently appearing on the Competitive product list.</P>
                <P>
                    The public portions of the Postal Service's request(s) can be accessed via the Commission's website (
                    <E T="03">http://www.prc.gov</E>
                    ). Non-public portions of the Postal Service's request(s), if any, can be accessed through compliance with the requirements of 39 CFR 3011.301.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Docket No. RM2018-3, Order Adopting Final Rules Relating to Non-Public Information, June 27, 2018, Attachment A at 19-22 (Order No. 4679).
                    </P>
                </FTNT>
                <P>Section II identifies the docket number(s) associated with each Postal Service request, if any, that will be reviewed in a public proceeding as defined by 39 CFR 3010.101(p), the title of each such request, the request's acceptance date, and the authority cited by the Postal Service for each request. For each such request, the Commission appoints an officer of the Commission to represent the interests of the general public in the proceeding, pursuant to 39 U.S.C. 505 and 39 CFR 3000.114 (Public Representative). The Public Representative does not represent any individual person, entity or particular point of view, and, when Commission attorneys are appointed, no attorney-client relationship is established. Section II also establishes comment deadline(s) pertaining to each such request.</P>
                <P>The Commission invites comments on whether the Postal Service's request(s) identified in Section II, if any, are consistent with the policies of title 39. Applicable statutory and regulatory requirements include 39 U.S.C. 3632, 39 U.S.C. 3633, 39 U.S.C. 3642, 39 CFR part 3035, and 39 CFR part 3041. Comment deadline(s) for each such request, if any, appear in Section II.</P>
                <P>
                    Section III identifies the docket number(s) associated with each Postal Service request, if any, to add a standardized distinct product to the Competitive product list or to amend a standardized distinct product, the title of each such request, the request's acceptance date, and the authority cited by the Postal Service for each request. Standardized distinct products are negotiated service agreements that are variations of one or more Competitive products, and for which financial models, minimum rates, and classification criteria have undergone advance Commission review. 
                    <E T="03">See</E>
                     39 CFR 3041.110(n); 39 CFR 3041.205(a). Such requests are reviewed in summary proceedings pursuant to 39 CFR 3041.325(c)(2) and 39 CFR 3041.505(f)(1). Pursuant to 39 CFR 3041.405(c)-(d), the Commission does not appoint a Public Representative or request public comment in proceedings to review such requests. The comment due date discussed below does not apply to Section III proceedings (Docket Nos. MC2026-185 and K2026-185; MC2026-186 and K2026-186; MC2026-187 and K2026-187).
                </P>
                <HD SOURCE="HD1">II. Public Proceeding(s)</HD>
                <HD SOURCE="HD3">
                    <E T="03">1. Docket No(s).:</E>
                     K2025-6; 
                    <E T="03">Filing Title:</E>
                     USPS Request Concerning Amendment One to Priority Mail &amp; USPS Ground Advantage Contract 371, with Material Filed Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     April 1, 2026; 
                    <E T="03">Filing Authority:</E>
                     39 CFR 3035.105 and 39 CFR 3041.505; 
                    <E T="03">Public Representative:</E>
                     Christopher Mohr; 
                    <E T="03">Comments Due:</E>
                     April 9, 2026.
                </HD>
                <HD SOURCE="HD1">III. Summary Proceeding(s)</HD>
                <P>
                    1. 
                    <E T="03">Docket No(s).:</E>
                     MC2026-185 and K2026-185; 
                    <E T="03">Filing Title:</E>
                     USPS Request to Add New Fulfillment Standardized Distinct Product, PM-GA Contract 948, and Notice of Filing Materials Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     April 1, 2026; 
                    <E T="03">Filing Authority:</E>
                     39 U.S.C. 3642 and 3633, 39 CFR 3035.105, and 39 CFR 3041.325.
                </P>
                <P>
                    2. 
                    <E T="03">Docket No(s).:</E>
                     MC2026-186 and K2026-186; 
                    <E T="03">Filing Title:</E>
                     USPS Request to Add New Fulfillment Standardized Distinct Product, PM-GA Contract 949, and Notice of Filing Materials Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     April 1, 2026; 
                    <E T="03">Filing Authority:</E>
                     39 U.S.C. 3642 and 3633, 39 CFR 3035.105, and 39 CFR 3041.325.
                </P>
                <P>
                    3. 
                    <E T="03">Docket No(s).:</E>
                     MC2026-187 and K2026-187; 
                    <E T="03">Filing Title:</E>
                     USPS Request to Add New Fulfillment Standardized Distinct Product, PM-GA Contract 950, and Notice of Filing Materials Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     April 1, 2026; 
                    <E T="03">Filing Authority:</E>
                     39 U.S.C. 3642 and 3633, 39 CFR 3035.105, and 39 CFR 3041.325.
                </P>
                <P>
                    This Notice will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Danielle LeFlore,</NAME>
                    <TITLE>Legal Assistant.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06598 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105136]</DEPDOC>
                <SUBJECT>Order Granting Limited Exemptions Pursuant to Rule 605(b) of Regulation NMS Under the Securities Exchange Act of 1934 From Rule 605 and Modifying and Rescinding Certain Exemptions Granted Pursuant to Rule 605 of Regulation NMS</SUBJECT>
                <DATE>April 1, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    Rule 605 of Regulation NMS 
                    <SU>1</SU>
                    <FTREF/>
                     under the Securities Exchange Act of 1934 
                    <PRTPAGE P="17314"/>
                    (“Exchange Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     requires certain market participants to make available to the public monthly electronic reports on order executions in national market system stocks (“NMS stocks”) 
                    <SU>3</SU>
                    <FTREF/>
                     that include uniform statistical measures of execution quality.
                    <SU>4</SU>
                    <FTREF/>
                     In 2024, the Commission adopted amendments that updated the disclosures required under Rule 605.
                    <SU>5</SU>
                    <FTREF/>
                     The amendments expanded the scope of entities subject to Rule 605 (including larger broker-dealers, in addition to market centers),
                    <SU>6</SU>
                    <FTREF/>
                     modified the categorization and content of order information required to be disclosed in the detailed execution quality reports published under Rule 605 (including by modifying the scope of covered orders subject to disclosures), and required reporting entities to produce a summary report of execution quality in addition to the existing detailed disclosures regarding execution quality for covered orders in NMS stocks.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         17 CFR 242.605 (formerly known as Rule 11Ac1-5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.600(b)(65) (defining “NMS stock”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 43590 (Nov. 17, 2000), 65 FR 75414 (Dec. 1, 2000) (Disclosure of Order Execution and Routing Practices).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 99679 (Mar. 6, 2024), 89 FR 26428 (Apr. 15, 2024) (Disclosure of Order Execution Information) (“Rule 605 Amendments Release”). In the Rule 605 Amendments Release, the Commission stated that the compliance date for the Rule 605 amendments would be 18 months after the effective date. Thus the compliance date was initially set as December 14, 2025. On September 30, 2025, the Commission extended the compliance date to August 1, 2026. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104147, 90 FR 47552 (Oct. 2, 2025).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The amendments to Rule 605 expanded the scope of entities that must produce monthly execution quality reports to include broker-dealers with a larger number of customer accounts and single dealer platforms. 
                        <E T="03">See</E>
                         17 CFR 242.605(a)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         17 CFR 242.605(a)(2).
                    </P>
                </FTNT>
                <P>
                    The Commission, by the Division of Trading and Markets pursuant to delegated authority, previously granted several exemptive requests from Rule 605 to market participants.
                    <SU>8</SU>
                    <FTREF/>
                     By letter dated June 24, 2024,
                    <SU>9</SU>
                    <FTREF/>
                     the Financial Information Forum (“FIF”), among other things, requests that the Commission provide an exception from Rule 605's reporting requirement for broker-dealers that execute fractional share orders in certain limited circumstances and raises interpretive issues that will require modification to exemptive relief from Rule 605 that the Commission granted previously.
                    <SU>10</SU>
                    <FTREF/>
                     As discussed below, the Commission is granting an exemption to broker-dealers subject to Rule 605 from compliance with Rule 605 for certain OTC market making activities, rescinding and replacing an exemption previously granted relating to certain orders received during a trading halt, modifying an exemption previously granted relating to inactively traded securities, rescinding and replacing an exemption previously granted relating to certain orders received during crossed markets, and rescinding an exemption previously granted relating to the exclusion of manually-received orders from reporting pursuant to Rule 605(a)(1).
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See, e.g.,</E>
                         letters from Annette L. Nazareth, Director, Division of Market Regulation, Commission, to Stuart J. Kaswell, Senior Vice President and General Counsel, Securities Industry Association (“SIA”), dated March 12, 2001, available at 
                        <E T="03">https://www.sec.gov/divisions/marketreg/mr-noaction/siaexemp.htm</E>
                         (“SIA Exemptive Letter”) and Richard Romano, Chair, Carl P. Sherr, Co-Chair, NASD Small Firms Advisory Board, dated June 22, 2001, available at 
                        <E T="03">https://www.sec.gov/divisions/marketreg/mr-noaction/smfirm062201.htm</E>
                         (“Inactively Traded Securities Exemptive Letter”). The SIA Exemptive Letter and the Inactively Traded Securities Exemptive Letter granted exemptions from Rule 11Ac1-5. As part of the adoption of Regulation NMS in 2005, Rule 11Ac1-5 was redesignated as Rule 605. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496 (June 29, 2005) (Regulation NMS) (“Regulation NMS Adopting Release”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         letter from Howard Meyerson, Managing Director, Financial Information Forum, dated June 24, 2024, to Kathleen Gross, Senior Special Counsel, and Lauren Yates, Senior Special Counsel, Division of Trading and Markets, Commission (“FIF Letter”). The Commission's Division of Trading and Markets previously published Staff Legal Bulletin No. 12R and Responses to Frequently Asked Questions Concerning Rule 605 of Regulation NMS (together, “Rule 605 FAQs”) to address frequently asked questions about then Rule 11Ac1-5 and Rule 605. 
                        <E T="03">See</E>
                         Division of Market Regulation: Staff Legal Bulletin No. 12R (Revised), Frequently Asked Questions About Rule 11Ac1-5 (revised) (June 22, 2001) (“SLB No. 12R”), available at 
                        <E T="03">https://www.sec.gov/interps/legal/slbim12a.htm;</E>
                         Responses to Frequently Asked Questions Concerning Rule 605 of Regulation NMS (Feb. 22, 2013), available at 
                        <E T="03">https://www.sec.gov/divisions/marketreg/nmsfaq605.htm.</E>
                         In the FIF Letter, FIF requested that staff of the Division of Trading and Markets update certain of the Rule 605 FAQs and posed additional questions regarding the application of Rule 605, as amended. 
                        <E T="03">See generally</E>
                         FIF Letter.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion and Exemptions From Rule 605, as Amended</HD>
                <P>
                    Rule 605(b) provides that the Commission may, by order upon application, conditionally or unconditionally exempt any person, security, or transaction, or any class or classes of persons, securities, or transactions, from any provision or provisions of this section, if the Commission determines that such exemption is necessary or appropriate in the public interest, and is consistent with the protection of investors.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 242.605(b).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Limited Exemption From Rule 605</HD>
                <P>
                    As amended, Rule 605 provides that market centers, brokers, and dealers must make publicly available detailed and summary execution quality reports pertaining to covered orders in NMS stocks that they receive for execution on a monthly basis.
                    <SU>12</SU>
                    <FTREF/>
                     The requirement that brokers or dealers prepare Rule 605 reports is limited to larger brokers or dealers that meet or exceed a specified customer account threshold,
                    <SU>13</SU>
                    <FTREF/>
                     but brokers and dealers may also be subject to Rule 605 reporting requirements if they meet the definition of a market center.
                    <SU>14</SU>
                    <FTREF/>
                     To the extent that any broker or dealer meets or exceeds the customer account threshold and is also a market center, that broker or dealer must produce separate Rule 605 reports pertaining to each function.
                    <SU>15</SU>
                    <FTREF/>
                     In response to a request for clarification, in the Rule 605 Amendments Release, the Commission stated that a broker-dealer that meets the customer account threshold for larger broker-dealers and is an OTC market maker generally should include in its Rule 605 reporting pertaining to its market center function all covered orders in NMS stock that the firm received for execution that are the type of order for which the firm serves as an OTC market maker.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.605(a). 
                        <E T="03">See also</E>
                         17 CFR 242.600(b)(27) (defining “covered order”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 242.605(a)(7). A broker or dealer meets the “customer account threshold” if it introduces or carries 100,000 or more customer accounts through which transactions are effected for the purchase or sale of NMS stocks. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Under Regulation NMS, “market center” means any exchange market maker, OTC market maker, alternative trading system, national securities exchange, or national securities association. 
                        <E T="03">See</E>
                         17 CFR 242.600(b)(55). “OTC market maker” means any dealer that holds itself out as being willing to buy from and sell to its customers, or others, in the United States, an NMS stock for its own account on a regular or continuous basis otherwise than on a national securities exchange in amounts of less than block size. 
                        <E T="03">See</E>
                         17 CFR 242.600(b)(75). 
                        <E T="03">See also</E>
                         17 CFR 242.600(b)(4), (37), (62), and (63) (defining “alternative trading system,” “exchange market maker,” “national securities association,” and “national securities exchange,” respectively).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 242.605(a)(7).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26441.
                    </P>
                </FTNT>
                <P>
                    In addition, in the Rule 605 Amendment Release, in response to a commenter's request for clarification about whether a broker-dealer that principally facilitates the trading of fractional shares must publish a separate Rule 605 report as a market center,
                    <SU>17</SU>
                    <FTREF/>
                     the Commission stated that “a reporting entity must produce a separate Rule 605 report as a market center if it meets the definition of an `OTC market maker' and receives `covered orders' for 
                    <PRTPAGE P="17315"/>
                    execution in such capacity.” 
                    <SU>18</SU>
                    <FTREF/>
                     The Commission recognized that “a firm may act as an OTC market maker for certain types of orders only” and that, as an example, a firm may act as an OTC market maker for fractional shares only.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26442.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26442.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26442, n.170.
                    </P>
                </FTNT>
                <P>
                    In the FIF Letter, FIF requests that the Commission provide an exception from Rule 605's reporting requirement for broker-dealers that execute fractional share orders only in certain circumstances.
                    <SU>20</SU>
                    <FTREF/>
                     Specifically, FIF states that the Commission should provide “an exception [from Rule 605 reporting requirements] if the customer-facing broker-dealer only executes fractional share orders in the following limited circumstances: [(1)] A customer has a fractional share position resulting from the customer's participation in a dividend reinvestment program[; or (2)] A customer has a fractional share position resulting from a stock dividend with a fractional component received after the customer has sold the position or transferred its account to another broker-dealer.” 
                    <SU>21</SU>
                    <FTREF/>
                     FIF also asked for clarification regarding broker-dealer reporting of fractional share positions in a separate market center report.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 3-4.
                    </P>
                </FTNT>
                <P>
                    Pursuant to its authority under Rule 605(b) of Regulation NMS,
                    <SU>23</SU>
                    <FTREF/>
                     for the reasons discussed below, the Commission has determined to exempt from the requirement to produce separate Rule 605 reports pertaining to its market center function 
                    <SU>24</SU>
                    <FTREF/>
                     any customer-facing broker-dealer that executes customers' fractional share orders only in circumstances in which the customer has a fractional share position resulting from (1) the customer's participation in a dividend reinvestment program; or (2) a stock dividend with a fractional component. In such circumstances, a customer-facing broker-dealer may facilitate its customer's ability to exit out of such fractional share positions by executing an order to sell the customer's fractional shares. The customer-facing broker-dealer would not be required to produce Rule 605 reports as a market center on the basis of this activity.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         17 CFR 242.605(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         A customer-facing broker-dealer that meets the customer account threshold would need to produce Rule 605 reports pertaining to its broker-dealer function.
                    </P>
                </FTNT>
                <P>The Commission has determined that such exemption is necessary or appropriate in the public interest, and is consistent with the protection of investors. In general, a broker-dealer that facilitates the trading of fractional share orders by executing those orders as principal would be acting as an OTC market maker with respect to fractional share orders and be required to prepare Rule 605 reports as a market center. This OTC market making activity in the context of a customer seeking to exit fractional share positions that the customer obtained due to the customer's participation in a dividend reinvestment program or a stock dividend with a fractional component occurs infrequently. Thus, the execution quality statistics prepared by the broker-dealer would provide a smaller amount of benefits relative to broker-dealers that execute fractional share orders as principal in a wider range of circumstances.</P>
                <P>Given this smaller amount of benefits, the cost of compliance for these broker-dealers to produce Rule 605 reports as a market center, as well as the potential costs if these broker-dealers were not willing to help their customers exit fractional share positions acquired under these limited circumstances, are not sufficient to justify the benefits of their monthly Rule 605 reports. The Commission has therefore determined to grant an exemption from the requirement to produce separate Rule 605 reports pertaining to its market center function for any customer-facing broker-dealer that executes customers' fractional share orders only in circumstances in which the customer has a fractional share position resulting from the limited circumstances discussed above. However, to the extent that a broker-dealer that helps its customers exit fractional share positions acquired as a result of their participation in a dividend reinvestment program or their receipt of a stock dividend also engages in additional OTC market making activity, the broker-dealer would not be able to rely on the exemption described herein and would still be subject to Rule 605 reporting requirements as a market center with respect to the orders related to helping its customers exit fractional share positions acquired through a dividend reinvestment program or receipt of a stock dividend with a fractional component, along with the other order types for which it acts as an OTC market maker.</P>
                <P>
                    This exemption is consistent with the Commission's determination to adopt a customer account threshold for broker-dealers' Rule 605 reporting requirements. In the Rule 605 Amendments Release, the Commission stated that “by limiting Rule 605 reporting requirements to larger-broker-dealers that meet the customer account threshold only, Rule 605 will balance the benefits of broker-dealer reporting with the costs.” 
                    <SU>25</SU>
                    <FTREF/>
                     Specifically, the Commission determined not to subject all broker-dealers to Rule 605 reporting requirements because of the lower benefits relative to costs for broker-dealers with a smaller number of customer accounts.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26438.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Modifications to Existing Exemptions</HD>
                <HD SOURCE="HD3">1. Orders Received During a Trading Halt</HD>
                <P>
                    In the SIA Exemptive Letter, the Commission exempted from the definition of “covered order” (now found in Rule 600(b)): (1) all orders that are received during the period of an “announced” trading halt, as described below; and (2) all orders that are received less than five minutes prior to an announced trading halt and that remain outstanding (in whole or in part) at the time of the trading halt.
                    <SU>26</SU>
                    <FTREF/>
                     In the SIA Exemptive Letter, SIA requested an exemption from the definition of covered order under the rule “for orders whose executions are significantly affected by trading that is halted during regular trading hours, either because they were received during the trading halt itself or had not been executed at the time of the trading halt.” 
                    <SU>27</SU>
                    <FTREF/>
                     SIA “state[d] that including these types of orders in monthly reports could result in statistics that are skewed and unrepresentative of a market center's normal trading.” 
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8 at 4.
                    </P>
                </FTNT>
                <P>
                    The FIF Letter requests that the Commission provide additional clarity related to trading halts for “orders that are not executable at the time of order receipt but subsequently become executable.” 
                    <SU>29</SU>
                    <FTREF/>
                     FIF requests that “the determinations [of whether to exclude a non-marketable order due to a trading halt] should be made as of the time that the order becomes executable.” 
                    <SU>30</SU>
                    <FTREF/>
                     FIF provides the following example: “an order is received and is not executable at the time of order receipt; a trading halt occurs one minute after receipt of the order; the trading halt ends; the order subsequently becomes executable. In this scenario, the trading halt should 
                    <PRTPAGE P="17316"/>
                    not impact whether the order is reportable.” 
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 6.
                    </P>
                </FTNT>
                <P>
                    The Commission is rescinding the exemption from the definition of “covered order” for all orders that are received during the period of an “announced” trading halt and all orders that are received less than five minutes prior to an announced trading halt and that remain outstanding at the time of the trading halt, as set forth in SIA Exemptive Letter, and is replacing this exemption with the exemption described herein. The replacement exemption accounts for non-marketable order types (defined below), which may be received when a national best bid or offer (“NBBO”) is not being disseminated, and do not fall within the scope of the rule unless they become executable. The Commission replacement exemption does not change the scope of the prior exemption with respect to marketable order types (defined below). In general, where Rule 605 requires calculation of execution quality statistics for marketable order types based on the time of order receipt, Rule 605 requires calculation of these statistics for non-marketable order types based on the time that the order becomes executable.
                    <SU>32</SU>
                    <FTREF/>
                     Consistent with this approach, the replacement exemption will treat non-marketable order types based on the time of executability in a manner similar to the treatment of marketable order types based on the time of order receipt. The replacement exemption will continue to exclude orders whose inclusion in monthly reports could result in statistics that may be skewed and unrepresentative of a reporting entity's normal trading, while helping to ensure that the group of excluded orders is not overly broad. As FIF states, for non-marketable order types that have not yet become executable at the time of the trading halt, a trading halt should not impact the treatment of the order.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Rule 605(a)(1)(i)(G)-(N) (requiring time-to-execution statistics as measured from time of order receipt or, for non-marketable limit orders or orders submitted with stop prices, from the time the order becomes executable).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 6.
                    </P>
                </FTNT>
                <P>Therefore, for the reasons discussed above, the Commission has determined that it is necessary or appropriate in the public interest, and is consistent with the protection of investors to exempt from Rule 605:</P>
                <P>(1) all market orders, marketable limit orders (excluding immediate-or-cancel orders), and marketable immediate-or-cancel orders (collectively, “marketable order types”) received during the period of an “announced” trading halt, as described below; and</P>
                <P>(2) (a) all marketable order types that are received less than five minutes prior to an announced trading halt and that remain outstanding (in whole or in part) at the time of the trading halt; and (b) all midpoint-or-better limit orders (excluding immediate-or-cancel orders), midpoint-or-better limit orders that are immediate-or-cancel, non-marketable limit orders (excluding orders submitted with stop prices, midpoint-or-better limit orders, and immediate-or-cancel orders), non-marketable orders that are immediate-or-cancel, market orders submitted with stop prices, stop marketable limit orders, and stop non-marketable limit orders (collectively, “non-marketable order types”) that become executable less than five minutes prior to an announced trading halt and that remain outstanding (in whole or in part) at the time of the trading halt.</P>
                <P>Consistent with the SIA Exemptive Letter, under the exemption provided herein, to qualify as an “announced” trading halt, the halt must be either a general regulatory halt or a trading halt that is announced by a market center in accordance with all applicable regulatory rules. Under the exemption provided herein, orders that are received prior to and during the time of an announced trading halt would be handled as follows:</P>
                <P>
                    First, 
                    <E T="03">all</E>
                     marketable order types received during the period that trading is halted must be entirely excluded from the Rule 605 monthly report.
                </P>
                <P>Second, all non-marketable order types received during the period that trading is halted may be included in the Rule 605 report if they become executable after trading resumes. In addition, regardless of when a non-marketable order type is received, a non-marketable order type should not be considered to have first become executable while trading is halted.</P>
                <P>Third, if an order that is a non-marketable order type becomes executable less than five minutes prior to the announced trading halt and remains outstanding (in whole or in part) at the time of the trading halt, the entire order is exempted from Rule 605 and must be excluded from the reporting entity's monthly report. If an order is a marketable order type, and is received less than five minutes prior to the announced trading halt and remains outstanding (in whole or in part) at the time of the trading halt, the entire order is exempted from Rule 605 and must be excluded from the reporting entity's monthly report.</P>
                <P>Fourth, for orders that are executed less than five minutes prior to the announced trading halt, the calculation of average realized spread should use the last NBBO disseminated prior to the time of the trading halt (analogous to the treatment of orders executed less than five minutes prior to the close of regular trading hours that is set forth in the definition of “average realized spread” in Rule 600(b) of Regulation NMS), to the extent that the realized spread time horizon specified in Rule 605(a)(1)(i) would otherwise fall within the time period during which trading was halted.</P>
                <P>Fifth, if a marketable order type was received or a non-marketable order type became executable five minutes or more prior to the announced trading halt and remains outstanding (in whole or in part) the order continues to be covered by Rule 605; provided, however, that for executions that occur after the end of the trading halt, a reporting entity may deduct the time period during which trading was halted from the calculations using the time of execution of the order.</P>
                <HD SOURCE="HD3">2. Inactively Traded Securities</HD>
                <P>
                    In the Inactively Traded Securities Exemptive Letter, the Commission granted an exemption from Rule 605 for very inactively traded securities.
                    <SU>34</SU>
                    <FTREF/>
                     The Commission is supplementing this existing exemption solely to explicitly cover broker-dealers in addition to market centers. The exemption, as supplemented, covers any NMS stock that did not average more than five reported transactions per trading day, as disseminated pursuant to an effective transaction reporting plan, for each of the preceding six months (or such shorter time that the security has been designated a NMS stock).
                    <SU>35</SU>
                    <FTREF/>
                     An inactive security will lose its exemption only after its average daily reported transactions have exceeded five for each of the preceding six months. Orders in exempted securities need not be included in the reporting entity's monthly Rule 605 report, but a market center, broker, or dealer is free to include them if it chooses to do so.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         Inactively Traded Securities Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         While the Inactively Traded Securities Exemptive Letter refers to a “national market system security,” when Regulation NMS was adopted, the references to “national market system security” in Rule 605 were replaced with “NMS stock” to indicate that Rule 605 would continue to be inapplicable to listed options. 
                        <E T="03">See</E>
                         Regulation NMS Adopting Release, 
                        <E T="03">supra</E>
                         note 8, at 37571.
                    </P>
                </FTNT>
                <P>
                    The Commission has determined that such action is necessary or appropriate in the public interest, and is consistent with the protection of investors, because it will supplement the exemption to include all reporting entities subject to 
                    <PRTPAGE P="17317"/>
                    Rule 605, as amended by the Rule 605 Amendments Release, within its scope. Broker-dealers were not covered within the exemption when it was originally issued in 2001, because Rule 605 at that time only applied to market centers.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         The supplemented exemption for inactively traded securities supersedes a staff FAQ. 
                        <E T="03">See</E>
                         Rule 605 FAQs, 
                        <E T="03">supra</E>
                         note 8, Question 25.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Orders Affected by Crossed Markets</HD>
                <P>
                    In the SIA Exemptive Letter, the Commission exempted from the definition of “covered order” (now found in Rule 600(b)) all orders that would require reference to a consolidated best bid and offer (“Consolidated BBO”) disseminated by an effective national market system plan that has been crossed for 30 seconds or more.
                    <SU>37</SU>
                    <FTREF/>
                     SIA stated “that when [the best bid and offer] have been crossed for a significant period of time, it raises a serious concern that the quotes may not represent a fair and reliable benchmark for a market center's statistics.” 
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 2. With the adoption of Regulation NMS, the Commission replaced the term “consolidated best bid or offer” in Rule 11Ac1-5 with the term “national best bid and national best offer.” 
                        <E T="03">See</E>
                         Regulation NMS Adopting Release, 
                        <E T="03">supra</E>
                         note 8, at 37574.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 2.
                    </P>
                </FTNT>
                <P>
                    The FIF Letter requests that the Commission provide additional clarity regarding how market centers, brokers, and dealers should report on orders whose Rule 605 statistics would be affected by an NBBO that is locked or crossed. In particular, FIF requests clarity regarding reliance by reporting entities on locked and crossed quotes as applied to “new order types and the new concept of `executability' introduced in the amended Rule 605.” 
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         FIF Letter, 
                        <E T="03">supra</E>
                         note 9, at 5.
                    </P>
                </FTNT>
                <P>When the NBBO is crossed for a significant period of time, it raises serious questions regarding whether the quotes continue to provide a reliable benchmark for the statistical measures included in Rule 605. However, the current exemption for certain orders affected by crossed markets does not clearly account for the new order types in Rule 605, as amended by the Rule 605 Amendments Release. In order to provide additional clarity, the Commission is rescinding the exemption from the definition of “covered order” for all orders that would require reference to a Consolidated BBO disseminated by an effective national market system plan that has been crossed for 30 seconds or more, as set forth in the SIA Exemptive Letter, and is replacing this exemption with the exemption described herein. For non-marketable limit orders, the determination of whether the order has become “executable” (as defined in Rule 600(b)) requires reference to the NBBO and many of the Rule 605 statistics pertaining to non-marketable limit orders are based on the NBBO at the time that the order becomes executable. Under the replacement exemption, in the context of non-marketable limit orders, the determination of whether the order has become executable should not occur when the NBBO is crossed because the NBBO may not represent a fair and reliable benchmark at such time. The replacement exemption also applies to broker-dealers, consistent with the scope of Rule 605, as amended by the Rule 605 Amendments Release.</P>
                <P>Therefore, for the reasons discussed above, the Commission has determined that it is necessary or appropriate in the public interest, and is consistent with the protection of investors to exempt from Rule 605 all orders that would require reference to an NBBO that has been crossed for 30 seconds or more.</P>
                <P>In light of this exemption, market centers, brokers, or dealers should follow the following procedure whenever a reference to the NBBO is necessary in connection with market or marketable limit orders, whether at the time of order receipt or the time of order execution:</P>
                <P>First, use the NBBO if the quotes are not crossed, or are locked.</P>
                <P>Second, if the NBBO is crossed, reject the crossed quotes and use the next-in-time uncrossed NBBO if there has been less than 30 seconds between the last-in-time uncrossed NBBO and the next-in-time uncrossed NBBO.</P>
                <P>Third, if there has been 30 seconds or more between the last-in-time uncrossed NBBO and the next-in-time uncrossed NBBO, the affected order is exempted from Rule 605 and must be excluded entirely from a market center, broker, or dealer's report (even if the crossed NBBO only affects a partial execution of the order).</P>
                <P>In addition, the determination of when a non-marketable limit order (including an order submitted with a stop price) becomes “executable,” as defined in Rule 600(b), relies on a comparison to the NBBO. A non-marketable limit order will fall within the scope of Rule 605 reporting only if it becomes executable. To avoid skewing execution quality statistics, the determination of whether a non-marketable limit order has become executable should not occur when the NBBO is crossed. Therefore, if the NBBO becomes crossed before a non-marketable limit order has become executable, a determination that such order has become executable should not be made during any period of time in which the NBBO is crossed. If the NBBO subsequently becomes uncrossed, a determination of whether the order has become executable should resume. If, instead, the NBBO becomes crossed after a non-marketable limit order has become executable, but before the order is executed, then the procedure set forth above should also apply.</P>
                <HD SOURCE="HD2">C. Rescission of Exemption for Manually-Received Orders</HD>
                <P>
                    In the SIA Exemptive Letter, the Commission exempted temporarily all market centers from the requirement to report under Rule 605 on orders that are received by the market center otherwise than through automated systems.
                    <SU>40</SU>
                    <FTREF/>
                     The SIA Exemptive Letter stated that this temporary exemption would be withdrawn, after a reasonable period of advance notice to market centers, when the Commission determines that market centers have the ability to capture all orders electronically.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See</E>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 8, at 1.
                    </P>
                </FTNT>
                <P>
                    The Commission is rescinding the temporary exemption from Rule 605, as amended by the Rule 605 Amendments Release, for manually-received orders. The Commission has determined that such action is necessary or appropriate in the public interest, and is consistent with the protection of investors. In granting the temporary exemption, the Commission had stated that the exemption of manually-received orders from the Rule “is intended to facilitate timely compliance with the Rule until market centers are able to develop automated systems that will capture all orders.” 
                    <SU>42</SU>
                    <FTREF/>
                     Over the last two decades, market centers and broker-dealers have developed automated systems that capture nearly all orders, including manual orders.
                    <SU>43</SU>
                    <FTREF/>
                     Therefore, the exemption is no longer necessary to facilitate timely compliance with Rule 605.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See</E>
                         SIA Exemptive Letter, 
                        <E T="03">supra</E>
                         note 10, at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See also</E>
                         Rule 605 Amendments Release, 
                        <E T="03">supra</E>
                         note 5, at 26430 (discussing the evolution of the equities markets from manual to highly automated trading).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Conclusion</HD>
                <P>
                    Accordingly, 
                    <E T="03">it is hereby ordered,</E>
                     pursuant to Rule 605(b) of Regulation NMS, that the above-described exemptive relief be granted, modified, or rescinded, as described above.
                </P>
                <SIG>
                    <PRTPAGE P="17318"/>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>44</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             17 CFR 200.30-3(a)(68).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06569 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105133; File No. SR-NYSEAMER-2026-11]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE American LLC; Order Approving a Proposed Rule Change To Amend Exchange Rule 915</SUBJECT>
                <DATE>April 1, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On February 6, 2026, NYSE American LLC (the “Exchange” or “NYSE American”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act” or “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to adopt listing criteria for options on Commodity-Based Trusts that hold multiple crypto assets. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on February 19, 2026.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments regarding the proposed rule change. This order approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104844 (Feb. 13, 2026), 91 FR 8405 (“Notice”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposed Rule Change</HD>
                <P>
                    Currently, Exchange Rule 915, Commentary .06(v) allows the Exchange to list options on shares that represent interests in a Commodity-Based Trust that meets the generic criteria of NYSE Arca Rule 8.201-E (Generic), except that the Commodity-Based Trust holds a single crypto asset, as defined in Exchange Rule 915, Commentary .06(c), and provided that (A) the global supply of the crypto asset held by the Commodity-Based Trust has an average daily market value of at least $700 million over the last 12 months; and (B) the crypto asset held by the Commodity-Based Trust underlies a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in the Intermarket Surveillance Group (“ISG”).
                    <SU>4</SU>
                    <FTREF/>
                     As described more fully in the Notice,
                    <SU>5</SU>
                    <FTREF/>
                     the Exchange proposes to amend Exchange Rule 915, Commentary .06(v) to allow the Exchange to list and trade options on a Commodity-Based Trust that holds multiple crypto assets. The proposal would allow the Exchange to list and trade these options without additional approval from the Commission.
                    <SU>6</SU>
                    <FTREF/>
                     Under the proposal, each crypto asset that the Commodity-Based Trust holds must meet the criteria in Exchange Rule 915, Commentary .06(c).
                    <SU>7</SU>
                    <FTREF/>
                     Accordingly, each of the Commodity-Based Trust's crypto assets must: (A) have an average daily market value of at least $700 million over the last 12 months; and (B) underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG.
                    <SU>8</SU>
                    <FTREF/>
                     The proposed Commodity-Based Trust share options also must satisfy the Exchange's initial and continued listing standards applicable to all options on exchange-traded funds (“ETFs”).
                    <SU>9</SU>
                    <FTREF/>
                     Exchange Rule 915, Commentary .06 requires the shares of an ETF underlying listed options to trade on a national securities exchange and to be an “NMS stock,” as defined in Rule 600 of Regulation NMS under the Exchange Act. In addition, Exchange Rule 915, Commentary .06 requires the shares of an ETF to meet the listing criteria in Exchange Rule 915(a) and (b) and Commentary .01 to Rule 915 
                    <SU>10</SU>
                    <FTREF/>
                     or Exchange Rule 915, Commentary .06(a)(ii).
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 915, Commentary .06(c). Exchange Rule 915, Commentary .06(c) defines the term “crypto asset” to mean “an asset that is generated, issued and/or transferred using a blockchain or similar distributive ledger technology network, including but not limited to, assets known as `tokens,' `digital assets,' `virtual currencies,' and `coins' and that relies on cryptographic protocols.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8047.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 915, Commentary .06(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 915, Commentary .06(c). The Exchange states that the market value for each crypto asset that a Commodity-Based Trust holds will be calculated by taking the total global supply of the crypto asset multiplied by the token price of that asset. The Exchange states that the total supply of a crypto asset includes all crypto assets currently issued and does not include unissued crypto assets. 
                        <E T="03">See</E>
                         Notice, 91 FR at 8046.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8048. In its proposal, the Exchange refers to Commodity-Based Trust Shares as ETFs. 
                        <E T="03">See id.</E>
                         at 8047, 8048. The Exchange's rules use the term “exchange-traded fund” to refer to several types of investment products, including Commodity-Based Trusts. 
                        <E T="03">See</E>
                         Exchange Rule 915, Commentary .06.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8046. Exchange Rule 915(a) states that underlying securities in respect of which put or call option contracts are approved for listing and trading on the Exchange must meet the following criteria: (1) the security must be duly registered and be an “NMS stock” as defined in Rule 600 of Regulation NMS under the Securities Exchange Act of 1934; and (2) the security shall be characterized by a substantial number of outstanding shares which are widely held and actively traded. Exchange Rule 915(b) states, among other things, that, absent exceptional circumstances, at the time the Exchange selects an underlying security for Exchange options transactions, the following guidelines with respect to the issuer shall be met: (1) There are a minimum of 7,000,000 shares of the underlying security which are owned by persons other than those required to report their security holdings under Section 16(a) of the Securities Exchange Act of 1934; (2) There are a minimum of 2,000 holders of the underlying security; (3) Trading volume (in all markets in which the underlying security is traded) has been at least 2,400,000 shares in the preceding twelve months; (4) (a) If the underlying security is a “covered security” as defined under Section 18(b)(1)(A) of the Securities Act of 1933: (i) the market price per share of the underlying security has been at least $3.00 for the previous three consecutive business days preceding the date on which the Exchange submits a certificate to The Options Clearing Corporation for listing and trading, as measured by the closing price reported in the primary market in which the underlying security is traded; however, (ii) the requirements set forth in (4)(a)(i) will be waived during the three days following its initial public offering day for an underlying security having a market capitalization of at least $3 billion based upon the offering price of its initial public offering, and may be listed and traded starting on or after the second business day following the initial public offering day; or (b) If the underlying security is not a “covered security,” the market price per share of the underlying security has been at least $7.50 for the majority of business days during the three calendar months preceding the date of selection, as measured by the lowest closing price reported in any market in which the underlying security traded on each of the subject days; (5) the issuer is in compliance with any applicable requirements of the Securities Exchange Act of 1934.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Exchange Rule 915, Commentary .06(a)(ii) states that the Exchange-Traded Fund Shares must be available for creation or redemption each business day in cash or in kind from or through the issuing trust, investment company, commodity pool or other issuer at a price related to the net asset value. In addition, the issuing trust, investment company, commodity pool or other issuer is obligated to issue Fund Shares in a specified aggregate number even though some or all of the investment assets needed to be deposited have not been received by the issuing trust, investment company, commodity pool, or other issuer, provided the authorized creation participant has undertaken to deliver the investment assets as soon as possible and such undertaking has been secured by the delivery and maintenance of collateral consisting of cash or cash equivalents satisfactory to the issuer of Fund Shares which underlie the option as described in the Fund Shares' prospectus.
                    </P>
                </FTNT>
                <P>
                    The continued listing criteria in proposed Exchange Rule 916, Commentary .07(3) will allow the Exchange to suspend opening transactions in options on Commodity-Based Trust shares if any crypto asset held by the Commodity-Based Trust (A) no longer has an average daily market value of at least $700 million over the last 12 months, as determined by the Exchange on a monthly basis; or (B) no longer underlies a derivatives contract that trades on a market with which the 
                    <PRTPAGE P="17319"/>
                    Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG. The Exchange states that requiring the average daily market value criterion to be met on a monthly basis is reasonable given that the Exchange believes that it is unlikely that a crypto asset with an average daily market value of at least $700 million over the previous twelve months would fail to meet that standard as a result of trading over a relatively short period of time.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8046. For example, the Exchange states that a crypto asset with market capitalization of $500 million for 15 days in a 20-day trading month could lose up to 88% of its value and continue to meet the criteria. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    Options on Commodity-Based Trust shares also will be subject to the continued listing standards in Exchange Rule 916, Commentary .07.
                    <SU>13</SU>
                    <FTREF/>
                     Under Exchange Rule 916, Commentary .07, shares of an ETF approved for options trading would not meet the requirements for continued approval if the shares were delisted from trading as provided in Exchange Rule 916, Commentary .01(5) because the underlying security was no longer an NMS stock, as defined in Rule 600 of Regulation NMS under the Exchange Act, or trading in the shares is halted or suspended from trading in their primary market.
                    <SU>14</SU>
                    <FTREF/>
                     Further, Exchange Rule 916, Commentary 07(4) (renumbered as Exchange Rule 916, Commentary .07(5)) would allow the Exchange to consider suspending opening transactions in options on Commodity-Based Trust shares if the Exchange believes that further dealing in the options on the Exchange is inadvisable.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 916, Commentary .07. 
                        <E T="03">See also</E>
                         Notice, 91 FR at 8046.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR at 8047.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that the proposed options on Commodity-Based Trust shares would trade in the same manner as other ETF options on the Exchange and will be subject to Exchange rules that currently apply to the listing and trading of ETF options, including Exchange rules governing, for example, expirations, exercise prices, minimum increments, position and exercise limits, margin requirements, customer accounts, and trading halt procedures.
                    <SU>16</SU>
                    <FTREF/>
                     The Exchange states that position and exercise limits for options on Commodity-Based Trust shares will be determined pursuant to Exchange Rules 904 and 905.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See id.</E>
                         at 8048.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See id.</E>
                         at 8047.
                    </P>
                </FTNT>
                <P>
                    The Exchange represents that the same surveillance procedures applicable to all ETF options currently listed and traded on the Exchange will apply to the trading of options on Commodity-Based Trust shares that are approved subject to proposed Exchange Rule 915, Commentary .06(v).
                    <SU>18</SU>
                    <FTREF/>
                     The Exchange states that its existing surveillance and reporting safeguards are designed to deter and detect possible manipulative behavior which might potentially arise from listing and trading options on Commodity-Based Trust shares that are approved subject to proposed Exchange Rule 915, Commentary .06(v).
                    <SU>19</SU>
                    <FTREF/>
                     The Exchange states that it may obtain information from designated contract markets that are members of the ISG related to a financial instrument that is based, in whole or in part, upon an interest in or performance of a crypto asset, as applicable.
                    <SU>20</SU>
                    <FTREF/>
                     In addition, the Exchange states that it currently lists options that would qualify for listing as on option on a Commodity-Based Trust under proposed Exchange Rule 915, Commentary .06(v).
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See id.</E>
                         at 8049. The Exchange states that it currently lists options on shares of the following funds: the iShares Bitcoin Trust, the Fidelity Wise Origin Bitcoin Fund, the ARK21 Shares Bitcoin ETF, the Grayscale Bitcoin Trust (BTC), the Grayscale Bitcoin Mini Trust BTC, and the Bitwise Bitcoin ETF. 
                        <E T="03">See</E>
                         Notice, 91 FR at 8049, footnote 30.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that it believes that both the Exchange and the Options Price Reporting Authority (“OPRA”) have the necessary systems capacity to handle the additional traffic associated with the listing of the proposed options on the Commodity-Based Trust shares.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See id.</E>
                         at 8047.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    After careful review, the Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>23</SU>
                    <FTREF/>
                     Specifically, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>24</SU>
                    <FTREF/>
                     which requires, among other things, that the rules of a national securities exchange be designed to prevent fraudulent and manipulative acts and practices, to remove impediments to and perfect the mechanism of a free and open market, and, in general, to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         In approving this proposed rule change, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to amend Exchange Rule 915, Commentary .06(v) to permit the Exchange to list options on shares of a Commodity-Based Trust that holds multiple crypto assets, provided that the Commodity-Based Trust meets certain requirements, as described above. The proposal will allow the Exchange to list options on shares of these Commodity-Based Trusts without further approval from the Commission, thereby permitting the Exchange to list these options soon after NYSE Arca lists the underlying Commodity-Based Trust shares. Permitting the listing and trading of these options on the Exchange will provide investors with an additional vehicle for gaining and hedging exposure to the underlying Commodity-Based Trust shares. The Commission recently approved a Nasdaq ISE, LLC proposal to establish listing standards for options on shares of Commodity-Based Trusts that hold multiple crypto assets.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 105072 (Mar. 24, 2026), 91 FR 14894 (Mar. 27, 2026).
                    </P>
                </FTNT>
                <PRTPAGE P="17320"/>
                <P>
                    Options on shares of Commodity-Based Trusts that hold multiple crypto assets will be subject to the same initial and continued listing requirements for options on Commodity-Based Trusts that hold a single crypto asset except that each crypto asset that a Commodity-Based Trust holds must (A) have an average daily market value of at least $700 million over the last 12 months; and (B) underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG. The requirements in proposed Exchange Rule 915, Commentary .06(c) are designed to help ensure that each of the crypto assets that a Commodity-Based Trust holds is sufficiently liquid that the creation and redemption process for shares of the Commodity-Based Trust will operate without disruption and that Commodity-Based Trust shares will be available to options market makers and other market participants that may use Commodity-Based Trust shares to hedge their positions. The Exchange will consider suspending opening transactions in Commodity-Based Trust share options if the requirements in proposed Exchange Rule 915, Commentary .06(c) are no longer satisfied.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 916, Commentary .07(3).
                    </P>
                </FTNT>
                <P>
                    The Exchange represents that the same surveillance procedures applicable to ETF options currently listed and traded on the Exchange will apply to the trading of options on Commodity-Based Trust shares.
                    <SU>27</SU>
                    <FTREF/>
                     The Exchange states that its existing surveillance and reporting safeguards are designed to deter and detect possible manipulative behavior that might arise from listing and trading options on ETFs, including the listing of options on Commodity-Based Trust shares.
                    <SU>28</SU>
                    <FTREF/>
                     As discussed above, each crypto asset held by a Commodity-Based Trust must underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG.
                    <SU>29</SU>
                    <FTREF/>
                     This requirement, in addition to the Exchange's existing surveillance procedures, should assist the Exchange in investigating suspected manipulations or other trading abuses in Commodity-Based Trust share options.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR at 8047.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 915, Commentary .06(c).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>30</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSEAMER-2026-11) is approved.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>31</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06567 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105134; File No. NYSEARCA-2026-17]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Order Approving a Proposed Rule Change To Amend Exchange Rule 5.3-O</SUBJECT>
                <DATE>April 1, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On February 6, 2026, NYSE Arca, Inc. (the “Exchange” or “NYSE Arca”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act” or “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to adopt listing criteria for options on Commodity-Based Trusts that hold multiple crypto assets. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on February 19, 2026.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments regarding the proposed rule change. This order approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104842 (Feb. 13, 2026), 91 FR 8037 (“Notice”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposed Rule Change</HD>
                <P>
                    Currently, Exchange Rule 5.3-O(g)(x) allows the Exchange to list options on shares that represent interests in a Commodity-Based Trust that meets the generic criteria of NYSE Arca Rule 8.201-E (Generic), except that the Commodity-Based Trust holds a single crypto asset, as defined in Exchange Rule 5.3-O(g)(3), and provided that (A) the global supply of the crypto asset held by the Commodity-Based Trust has an average daily market value of at least $700 million over the last 12 months; and (B) the crypto asset held by the Commodity-Based Trust underlies a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in the Intermarket Surveillance Group (“ISG”).
                    <SU>4</SU>
                    <FTREF/>
                     As described more fully in the Notice,
                    <SU>5</SU>
                    <FTREF/>
                     the Exchange proposes to amend Exchange Rule 5.3-O(g)(x) to allow the Exchange to list and trade options on a Commodity-Based Trust that holds multiple crypto assets. The proposal would allow the Exchange to list and trade these options without additional approval from the Commission.
                    <SU>6</SU>
                    <FTREF/>
                     Under the proposal, each crypto asset that the Commodity-Based Trust holds must meet the criteria in Exchange Rule 5.3-O(g)(3).
                    <SU>7</SU>
                    <FTREF/>
                     Accordingly, each of the Commodity-Based Trust's crypto assets must: (A) have an average daily market value of at least $700 million over the last 12 months; and (B) underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG.
                    <SU>8</SU>
                    <FTREF/>
                     The proposed Commodity-Based Trust share options also must satisfy the Exchange's initial and continued listing standards applicable to all options on exchange-traded funds (“ETFs”).
                    <SU>9</SU>
                    <FTREF/>
                     Exchange Rule 5.3-O(g) requires the shares of an ETF underlying listed options to trade on a national securities exchange and to be an “NMS stock,” as defined in Rule 600 of Regulation NMS under the Exchange Act. In addition, Exchange Rule 5.3-O(g) requires the shares of an ETF to meet the listing criteria in Exchange 
                    <PRTPAGE P="17321"/>
                    Rule 5.3-O(g)(1)(A) 
                    <SU>10</SU>
                    <FTREF/>
                     or Exchange Rule 5.3-O(g)(1(B).
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5.3-O(g)(3). Exchange 5.3-O(g)(3) defines the term “crypto asset” to mean “an asset that is generated, issued and/or transferred using a blockchain or similar distributive ledger technology network, including but not limited to, assets known as `tokens,' `digital assets,' `virtual currencies,' and `coins' and that relies on cryptographic protocols.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8040.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 5.3-O(g)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 5.3-O(g)(3). The Exchange states that the market value for each crypto asset that a Commodity-Based Trust holds will be calculated by taking the total global supply of the crypto asset multiplied by the token price of that asset. The Exchange states that the total supply of a crypto asset includes all crypto assets currently issued and does not include unissued crypto assets. 
                        <E T="03">See</E>
                         Notice, 91 FR at 8038.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8038. In its proposal, the Exchange refers to Commodity-Based Trust Shares as ETFs. 
                        <E T="03">See id.</E>
                         at 8038, 8039. The Exchange's rules use the term “exchange-traded fund” to refer to several types of investment products, including Commodity-Based Trusts. 
                        <E T="03">See</E>
                         Exchange Rule 5.3-O(g).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8038. Exchange Rule 5.3-O(g)(1)(A) requires an ETF to meet the criteria in Exchange Rule 5.3-O(a) and (b). Exchange Rule 5.3-O(a) states, in part, that absent exceptional circumstances, an underlying security will not be selected for options trading unless: (1) there are a minimum of 7,000,000 shares of the underlying security which shall be owned by persons other than those required to report their stock holdings under Section 16(a) of the Securities Exchange Act of 1934; (2) there are a minimum of 2,000 shareholders of the underlying security; (3) trading volume (in all markets in which the underlying security is traded) has been at least 2,400,000 shares in the preceding twelve months. In considering for approval underlying securities that have not been primarily traded on a national securities exchange or designated as national market system securities for the one year preceding such approval, the Exchange may take into account the volume of trading in such security in the over-the-counter market as reflected in the NASDAQ system. If the volume of trading in the over-the-counter market meets the requirements specified above, then the security may be deemed to have met the volume requirements set forth in the agreements between the Exchange and the Clearing Corporation; (4) (A) if the underlying security is a “covered security” as defined under Section 18(b)(1)(A) of the Securities Act of 1933 (i) the market price per share of the underlying security has been at least $3.00 for the previous three consecutive business days preceding the date on which the Exchange submits a certificate to the Clearing Corporation for listing and trading, as measured by the closing price reported in the primary market in which the underlying security is traded; however, (ii) the requirements set forth in (4)(A)(i) will be waived during the three days following its initial public offering day for an underlying security having a market capitalization of at least $3 billion based upon the offering price of its initial public offering, and may be listed and traded starting on or after the second business day following the initial public offering day; (B) if the underlying security is not a “covered security,” the market price per share of the underlying security has been at least $7.50 for the majority of business days during the three calendar months preceding the date of selection, as measured by the lowest closing price reported in any market in which the underlying security traded on each of the subject days; (5) the issuer is in compliance with any applicable requirements of the Securities Exchange Act of 1934. Exchange Rule 5.3-O(b) states that underlying securities must be registered and be an “NMS stock” as defined in Rule 600 of Regulation NMS under the Exchange Act.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Exchange Rule 5.3-O(g)(1)(B) states that the Exchange-Traded Fund Shares must be available for creation or redemption each business day in cash or in kind from or through the issuing trust, investment company, commodity pool or other issuer at a price related to the net asset value. In addition, the issuing trust, investment company, commodity pool, or other issuer is obligated to issue Fund Shares in a specified aggregate number even though some or all of the investment assets needed to be deposited have not been received by the issuing trust, investment company, commodity pool, or other issuer, provided the authorized creation participant has undertaken to deliver the investment assets as soon as possible and such undertaking has been secured by the delivery and maintenance of collateral consisting of cash or cash equivalents satisfactory to the issuer of Fund Shares which underlie the option as described in the Fund Shares' prospectus.
                    </P>
                </FTNT>
                <P>
                    The continued listing criteria in proposed Exchange Rule 5.4-O(k)(3) will allow the Exchange to suspend opening transactions in options on Commodity-Based Trust shares if any crypto asset held by the Commodity-Based Trust (A) no longer has an average daily market value of at least $700 million over the last 12 months, as determined by the Exchange on a monthly basis; or (B) no longer underlies a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG. The Exchange states that requiring the average daily market value criterion to be met on a monthly basis is reasonable given that the Exchange believes that it is unlikely that a crypto asset with an average daily market value of at least $700 million over the previous twelve months would fail to meet that standard as a result of trading over a relatively short period of time.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR 8038-9. For example, the Exchange states that a crypto asset with market capitalization of $500 million for 15 days in a 20-day trading month could lose up to 88% of its value and continue to meet the criteria. 
                        <E T="03">See id.</E>
                         at 8039.
                    </P>
                </FTNT>
                <P>
                    Options on Commodity-Based Trust shares also will be subject to the continued listing standards in Exchange Rule 5.4-O(k).
                    <SU>13</SU>
                    <FTREF/>
                     Under Exchange Rule 5.4-O(k), shares of an ETF approved for options trading would not meet the requirements for continued approval if the shares were delisted from trading as provided in Exchange Rule 5.4-O(b)(5) because the underlying security was no longer an NMS stock, as defined in Rule 600 of Regulation NMS under the Exchange Act, or trading in the shares is halted or suspended from trading in their primary market.
                    <SU>14</SU>
                    <FTREF/>
                     Further, Exchange Rule 5.4-O(k)(4) (renumbered as Exchange Rule 5.4-O(k)(5)) would allow the Exchange to consider suspending opening transactions in options on Commodity-Based Trust shares if the Exchange believes that further dealing in the options on the Exchange is inadvisable.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See id.</E>
                         at 8038.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5.3-O(k).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR at 8039.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that the proposed options on Commodity-Based Trust shares would trade in the same manner as other ETF options on the Exchange and will be subject to Exchange rules that currently apply to the listing and trading of ETF options, including Exchange rules governing, for example, expirations, exercise prices, minimum increments, position and exercise limits, margin requirements, customer accounts, and trading halt procedures.
                    <SU>16</SU>
                    <FTREF/>
                     The Exchange states that position and exercise limits for options on Commodity-Based Trust shares will be determined pursuant to Exchange Rules 6.8-O and 6.9-O.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See id.</E>
                         at 8039.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    The Exchange represents that the same surveillance procedures applicable to all ETF options currently listed and traded on the Exchange will apply to the trading of options on Commodity-Based Trust shares that are approved subject to proposed Exchange Rule 5.3-O(g)(x).
                    <SU>18</SU>
                    <FTREF/>
                     The Exchange states that its existing surveillance and reporting safeguards are designed to deter and detect possible manipulative behavior which might potentially arise from listing and trading options on Commodity-Based Trust shares that are approved subject to proposed Exchange Rule 5.3-O(g)(x).
                    <SU>19</SU>
                    <FTREF/>
                     The Exchange states that it may obtain information from designated contract markets that are members of the ISG related to a financial instrument that is based, in whole or in part, upon an interest in or performance of a crypto asset, as applicable.
                    <SU>20</SU>
                    <FTREF/>
                     In addition, the Exchange states that it currently lists options that would qualify for listing as on option on a Commodity-Based Trust under proposed Exchange Rule 5.3-O(g)(x).
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See id.</E>
                         at 8040. The Exchange states that it currently lists options on shares of the following funds: the iShares Bitcoin Trust, the Fidelity Wise Origin Bitcoin Fund, the ARK21 Shares Bitcoin ETF, the Grayscale Bitcoin Trust (BTC), the Grayscale Bitcoin Mini Trust BTC, and the Bitwise Bitcoin ETF. 
                        <E T="03">See</E>
                         Notice, 91 FR at 8040, footnote 25.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that it believes both the Exchange and the Options Price Reporting Authority (“OPRA”) have the necessary systems capacity to handle the additional traffic associated with the listing of the proposed options on the Commodity-Based Trust shares.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See id.</E>
                         at 8040.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    After careful review, the Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>23</SU>
                    <FTREF/>
                     Specifically, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>24</SU>
                    <FTREF/>
                     which requires, among other things, that the rules of a national securities exchange be designed to prevent fraudulent and 
                    <PRTPAGE P="17322"/>
                    manipulative acts and practices, to remove impediments to and perfect the mechanism of a free and open market, and, in general, to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         In approving this proposed rule change, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Exchange proposes to amend Exchange Rule 5.3-O(g)(x) to permit the Exchange to list options on shares of a Commodity-Based Trust that holds multiple crypto assets, provided that the Commodity-Based Trust meets certain requirements, as described above. The proposal will allow the Exchange to list options on shares of these Commodity-Based Trusts without further approval from the Commission, thereby permitting the Exchange to list these options soon after the Exchange lists the underlying Commodity-Based Trust shares. Permitting the listing and trading of these options on the Exchange will provide investors with an additional vehicle for gaining and hedging exposure to the underlying Commodity-Based Trust shares. The Commission recently approved a Nasdaq ISE, LLC proposal to establish listing standards for options on shares of Commodity-Based Trusts that hold multiple crypto assets.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 105072 (Mar. 24, 2026), 91 FR 14894 (Mar. 27, 2026).
                    </P>
                </FTNT>
                <P>
                    Options on shares of Commodity-Based Trusts that hold multiple crypto assets will be subject to the same initial and continued listing requirements for options on Commodity-Based Trusts that hold a single crypto asset except that each crypto asset that a Commodity-Based Trust holds must (A) have an average daily market value of at least $700 million over the last 12 months; and (B) underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG. The requirements in proposed Exchange Rule 5.3-O(g)(3) are designed to help ensure that each of the crypto assets that a Commodity-Based Trust holds is sufficiently liquid that the creation and redemption process for shares of the Commodity-Based Trust will operate without disruption and that Commodity-Based Trust shares will be available to options market makers and other market participants that may use Commodity-Based Trust shares to hedge their positions. The Exchange will consider suspending opening transactions in Commodity-Based Trust share options if the requirements in proposed Exchange Rule 5.3-O(g)(3) are no longer satisfied.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 5.4-O(k)(3).
                    </P>
                </FTNT>
                <P>
                    The Exchange represents that the same surveillance procedures applicable to ETF options currently listed and traded on the Exchange will apply to the trading of options on Commodity-Based Trust shares.
                    <SU>27</SU>
                    <FTREF/>
                     The Exchange states that its existing surveillance and reporting safeguards are designed to deter and detect possible manipulative behavior that might arise from listing and trading options on ETFs, including the listing of options on Commodity-Based Trust shares.
                    <SU>28</SU>
                    <FTREF/>
                     As discussed above, each crypto asset held by a Commodity-Based Trust must underlie a derivatives contract that trades on a market with which the Exchange has a comprehensive surveillance sharing agreement, whether directly or through common membership in ISG.
                    <SU>29</SU>
                    <FTREF/>
                     This requirement, in addition to the Exchange's existing surveillance procedures, should assist the Exchange in investigating suspected manipulations or other trading abuses in Commodity-Based Trust share options.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         Notice, 91 FR at 8039.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         proposed Exchange Rule 5.3-O(g)(3).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>30</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSEARCA-2026-17) is approved.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <P>
                    For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06568 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 12977]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Foreign Assistance Requirements</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State is seeking Office of Management and Budget (OMB) approval for the information collection described below. In accordance with the Paperwork Reduction Act of 1995, we are requesting comments on this collection from all interested individuals and organizations. The purpose of this notice is to allow 60 days for public comment preceding submission of the collection to OMB.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Department will accept comments from the public up to June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Web:</E>
                         Persons with access to the internet may comment on this notice by going to 
                        <E T="03">www.Regulations.gov.</E>
                         You can search for the document by entering “Docket Number: DOS-2026-0364” in the Search field. Then click the “Comment Now” button and complete the comment form.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: PHFFA_Comments@state.gov.</E>
                    </P>
                    <P>You must include the information collection title (Foreign Assistance Requirements).</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of supporting documents, to 
                        <E T="03">PHFFA_Comments@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    • 
                    <E T="03">Title of Information Collection:</E>
                     Foreign Assistance Recordkeeping Requirements.
                </P>
                <P>
                    • 
                    <E T="03">OMB Control Number:</E>
                     None.
                </P>
                <P>
                    • 
                    <E T="03">Type of Request:</E>
                     New Collection.
                </P>
                <P>
                    • 
                    <E T="03">Originating Office:</E>
                     Department of State, Office of Foreign Assistance Oversight.
                </P>
                <P>
                    • 
                    <E T="03">Form Number:</E>
                     No form.
                </P>
                <P>
                    • 
                    <E T="03">Respondents:</E>
                     Foreign non-governmental organizations (NGOs), U.S. NGOs, and international organizations.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Respondents:</E>
                     2,500.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Responses:</E>
                     2,500.
                </P>
                <P>
                    • 
                    <E T="03">Average Time per Response:</E>
                     240 hours.
                </P>
                <P>
                    • 
                    <E T="03">Total Estimated Burden Time:</E>
                     600,000 hours.
                </P>
                <P>
                    • 
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    • 
                    <E T="03">Obligation to Respond:</E>
                     Mandatory.
                </P>
                <P>We are soliciting public comments to permit the Department to:</P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper functions of the Department.</P>
                <P>• Evaluate the accuracy of our estimate of the time and cost burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of automated collection techniques or other forms of information technology.</P>
                <P>
                    Please note that comments submitted in response to this Notice are public 
                    <PRTPAGE P="17323"/>
                    record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review.
                </P>
                <HD SOURCE="HD1">Abstract of Proposed Collection</HD>
                <P>This information collection relates to three final rules published on January 27, 2026. 91 FR 3319, 91 FR 3332, and 91 FR 3345. These rules implement the President's Protecting Human Flourishing in Foreign Assistance (PHFFA) policy, by requiring recipients of U.S. foreign assistance funds to agree to certain terms and conditions. In summary, foreign NGOs, U.S. NGOs, and international organizations are required to comply with the policy (foreign governments and parastatals may also be required to comply with the policies, but those entities are not “persons” under the Paperwork Reduction Act, thus not covered by this notice) and agree that during the period of the award they will segregate records so that the Department can verify that they are not violating the terms of the foreign assistance grants that were provided to them. Full details are included in the three final rules.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>There is no form involved in this information collection. The final rules require recipients of U.S. foreign assistance funds to maintain records and make business records available upon request, which is a requirement governed by the Paperwork Reduction Act. Specifically, recipients of foreign assistance must maintain separate records for activities performed that are funded by federal grants, apart from activities funded from other sources, and must make the records relating to the former activities available for inspection upon request. Foreign assistance grantees must ensure that all award terms flow down to any subrecipients of such assistance, as applicable.</P>
                <SIG>
                    <NAME>Ryan E. Shrum,</NAME>
                    <TITLE>Chief of Staff, Office of the Under Secretary for Foreign Assistance, Humanitarian Affairs, and Religious Freedom, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06640 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 12984]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Brokering Prior Approval (License)</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State is seeking Office of Management and Budget (OMB) approval for the information collection described below. In accordance with the Paperwork Reduction Act of 1995, we are requesting comments on this collection from all interested individuals and organizations. The purpose of this notice is to allow 60 days for public comment preceding submission of the collection to OMB.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Department will accept comments from the public up to June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Web:</E>
                         Persons with access to the internet may comment on this notice by going to 
                        <E T="03">www.Regulations.gov.</E>
                         You can search for the document by entering “Docket Number: DOS-2026-0398” in the Search field. Then click the “Comment Now” button and complete the comment form.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: DDTCPublicComments@state.gov</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Regular Mail:</E>
                         Send written comments to: Directorate of Defense Trade Controls, Attn: Andrea Battista, 2401 E St. NW, Suite H-1205, Washington, DC 20522-0112.
                    </P>
                    <P>You must include the DS form number (if applicable), information collection title, and the OMB control number in any correspondence.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed collection instrument and supporting documents, to Andrea Battista, who may be reached at 
                        <E T="03">BattistaAL@state.gov</E>
                         or 202-992-0973.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    • 
                    <E T="03">Title of Information Collection:</E>
                     Brokering Prior Approval.
                </P>
                <P>
                    • 
                    <E T="03">OMB Control Number:</E>
                     1405-0142.
                </P>
                <P>
                    • 
                    <E T="03">Type of Request:</E>
                     Extension of a Currently Approved Collection.
                </P>
                <P>
                    • 
                    <E T="03">Originating Office:</E>
                     Directorate of Defense Trade Controls (DDTC).
                </P>
                <P>
                    • 
                    <E T="03">Form Number:</E>
                     DS-4294.
                </P>
                <P>
                    • 
                    <E T="03">Respondents:</E>
                     Respondents are U.S. and foreign persons who wish to engage in International Traffic in Arms Regulations (ITAR)-controlled brokering of defense articles and defense services.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Respondents:</E>
                     170.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Responses:</E>
                     170.
                </P>
                <P>
                    • 
                    <E T="03">Average Time per Response:</E>
                     2 hours.
                </P>
                <P>
                    • 
                    <E T="03">Total Estimated Burden Time:</E>
                     340 hours.
                </P>
                <P>
                    • 
                    <E T="03">Frequency:</E>
                     On Occasion.
                </P>
                <P>
                    • 
                    <E T="03">Obligation to Respond:</E>
                     Required to Obtain Benefit.
                </P>
                <P>We are soliciting public comments to permit the Department to:</P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper functions of the Department.</P>
                <P>• Evaluate the accuracy of our estimate of the time and cost burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of automated collection techniques or other forms of information technology.</P>
                <P>Please note that comments submitted in response to this Notice are public record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review.</P>
                <HD SOURCE="HD1">Abstract of Proposed Collection</HD>
                <P>In accordance with part 129 of the International Traffic in Arms Regulations (ITAR), U.S. and foreign persons who wish to engage in ITAR-controlled brokering activity of defense articles and defense services must first register with DDTC. Brokers must then submit a written request for approval to DDTC and must receive DDTC's consent prior to engaging in such activities unless exempted. This information is currently used in the review of the brokering request submitted for approval and to ensure compliance with defense trade statutes and regulations. It is also used to monitor and control the transfer of sensitive U.S. technology.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>Applicants may submit a Brokering Prior Approval Request electronically via DDTC's Defense Export Control and Compliance System (DECCS), using the DS-4294.</P>
                <SIG>
                    <NAME>Michael J. Vaccaro, </NAME>
                    <TITLE>Deputy Assistant Secretary for Defense Trade Controls, U.S. Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06630 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-25-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="17324"/>
                <AGENCY TYPE="S">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 12985]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Annual Brokering Report</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State is seeking Office of Management and Budget (OMB) approval for the information collection described below. In accordance with the Paperwork Reduction Act of 1995, we are requesting comments on this collection from all interested individuals and organizations. The purpose of this notice is to allow 60 days for public comment preceding submission of the collection to OMB.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Department will accept comments from the public up to June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Web:</E>
                         Persons with access to the internet may comment on this notice by going to 
                        <E T="03">www.Regulations.gov.</E>
                         You can search for the document by entering “Docket Number: DOS-2026-0399” in the Search field. Then click the “Comment Now” button and complete the comment form.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: DDTCPublicComments@state.gov</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Regular Mail:</E>
                         Send written comments to: Directorate of Defense Trade Controls, Attn: Andrea Battista, 2401 E St. NW, Suite H-1205, Washington, DC 20522-0112.
                    </P>
                    <P>You must include the DS form number (if applicable), information collection title, and the OMB control number in any correspondence.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed collection instrument and supporting documents, to Andrea Battista, who may be reached at 
                        <E T="03">battistaal@state.gov</E>
                         or 202-992-0973.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    • 
                    <E T="03">Title of Information Collection:</E>
                     Annual Brokering Report.
                </P>
                <P>
                    • 
                    <E T="03">OMB Control Number:</E>
                     1405-0141.
                </P>
                <P>
                    • 
                    <E T="03">Type of Request:</E>
                     Extension of a Currently Approved Collection.
                </P>
                <P>
                    • 
                    <E T="03">Originating Office:</E>
                     Directorate of Defense Trade Controls (DDTC).
                </P>
                <P>
                    • 
                    <E T="03">Form Number:</E>
                     No Form.
                </P>
                <P>
                    • 
                    <E T="03">Respondents:</E>
                     Respondents are any person/s who engages in the United States in the business of manufacturing or exporting or temporarily importing defense articles.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Respondents:</E>
                     1,142.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Responses:</E>
                     1,142.
                </P>
                <P>
                    • 
                    <E T="03">Average Time per Response:</E>
                     2 hours.
                </P>
                <P>
                    • 
                    <E T="03">Total Estimated Burden Time:</E>
                     2,284 hours.
                </P>
                <P>
                    • 
                    <E T="03">Frequency:</E>
                     Annually.
                </P>
                <P>
                    • 
                    <E T="03">Obligation to Respond:</E>
                     Required to Obtain or Retain Benefit.
                </P>
                <P>We are soliciting public comments to permit the Department to:</P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper functions of the Department.</P>
                <P>• Evaluate the accuracy of our estimate of the time and cost burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of automated collection techniques or other forms of information technology.</P>
                <P>Please note that comments submitted in response to this Notice are public record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review.</P>
                <HD SOURCE="HD1">Abstract of Proposed Collection</HD>
                <P>In accordance with part 129 of the ITAR, U.S. and foreign persons required to register as a broker shall provide annually a report to DDTC enumerating and describing brokering activities by quantity, type, U.S. dollar value, purchaser/recipient, and license number for approved activities and any exemptions utilized for other covered activities. This information is currently used in the review of munitions export and brokering license applications and to ensure compliance with defense trade statutes and regulations. As appropriate, such information may be shared with other U.S. Government entities.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>Brokering Reports are submitted annually with Statement of Registration renewals.</P>
                <P>Applicants are referred to ITAR part 129 for guidance on information to submit regarding proposed brokering activity.</P>
                <SIG>
                    <NAME>Michael J. Vaccaro,</NAME>
                    <TITLE>Deputy Assistant Secretary, Directorate of Defense Trade Controls, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06631 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="F">SURFACE TRANSPORTATION BOARD</AGENCY>
                <SUBJECT>Release of Waybill Data</SUBJECT>
                <P>The Surface Transportation Board has received a request from University of Wisconsin, (WB26-13-03/27/26) for permission to use select data from the Board's 1996-2025 inclusive, unmasked Carload Waybill Samples for railroad shipments of corn soybeans, and wheat. A copy of this request may be obtained from the Board's website under docket no. WB26-13.</P>
                <P>The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9.</P>
                <P>
                    Any inquiries on this request should be directed to 
                    <E T="03">waybill@stb.gov</E>
                    .
                </P>
                <SIG>
                    <NAME>Regena Smith-Bernard,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06583 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. FMCSA-2025-0787]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Approval of a New Information Collection Request: Quantifying the Benefits of Creating New Truck Parking Spaces</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FMCSA announces its plan to submit the Information Collection Request (ICR) described below to the Office of Management and Budget (OMB) for review and approval. This notice invites comments on a proposed information collection titled 
                        <E T="03">Quantifying the Benefits of Creating New Truck Parking Spaces.</E>
                         This research study will collect approximately 1,000 survey responses from truck drivers about their experiences with finding truck parking spaces to estimate the monetary benefits of creating new truck parking spaces. Eight public comments were received in response to the 60-day 
                        <E T="04">Federal Register</E>
                         notice.
                    </P>
                </SUM>
                <DATES>
                    <PRTPAGE P="17325"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this notice must be received on or before May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be submitted within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dan Britton, Office of Research and Registration, FMCSA, W58-213, 1200 New Jersey Avenue SE, Washington, DC 20590-0001; (202) 366-9980; 
                        <E T="03">dan.britton@dot.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     Quantifying the Benefits of Creating New Truck Parking Spaces.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2126-TBD.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     New ICR.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Commercial truck drivers.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     1,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     25 minutes.
                </P>
                <P>
                    <E T="03">Expiration Date:</E>
                     N/A. This is a new ICR.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Each survey participant will provide only one survey response.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     416 hours (0.416 hours per response × 1,000 respondents).
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The nationwide shortage of truck parking spaces is a significant source of frustration for truck drivers, increasing expenses for the trucking industry and decreasing t safety for all road users. The American Transportation Research Institute conducts an annual survey of trucking industry stakeholders (
                    <E T="03">Critical Issues in the Trucking Industry</E>
                    ), and the 2024 survey found that, for the second year in a row, the lack of available truck parking was the second highest industry concern overall, and the number one concern among truck drivers. The lack of truck parking often forces truck drivers to choose between violating federal hours-of-service laws and using unsafe, illegal parking spaces.
                </P>
                <P>
                    Many government, safety, and industry organizations are working to create more truck parking spaces, but there is a lack of research on the actual precise monetary benefits of new truck parking spaces. These benefits include decreasing carriers' costs, increasing drivers' well-being, and reducing the number of crashes. To help State and local policymakers make informed decisions about the construction of truck parking spaces, FMCSA is conducting a research study, titled 
                    <E T="03">Quantifying the Benefits of Creating New Truck Parking Spaces,</E>
                     which will survey truck drivers about their parking habits and experiences, gaining the exact information needed to quantify the benefits of new truck parking spaces.
                </P>
                <P>Although researchers have conducted many other surveys on truck parking, none have reliably estimated the statistics needed, including how often and how long truck drivers (a) park in unauthorized spaces, (b) stop driving early to obtain a parking space, (c) drive off their routes to find parking, and (d) drive past hours-of-service limits to find parking. The results of this survey will be combined with related research to produce estimates of the benefits of creating new truck parking spaces in different areas, which could be beneficial to the many government and private organizations that decide where to build new truck parking spaces.</P>
                <P>The main objective of this project is to estimate the benefits of new truck parking spaces, but the project will also answer four related research questions:</P>
                <P>1. How many trucks are parked in authorized and unauthorized areas per day, on average? In other words, how large is the nationwide shortage of truck parking spaces?</P>
                <P>2. What are the most cost-effective methods for increasing truck parking capacity?</P>
                <P>3. Which truck parking information management systems are used most often and are most effective?</P>
                <P>4. What percentage of drivers routinely make reservations, pay for parking, or use various other truck parking services?</P>
                <P>Several thousand truck drivers, from a wide range of sectors, will be asked to complete the 25-minute online survey, with a goal of obtaining approximately 1,000 complete responses.</P>
                <P>Title 23, United States Code (U.S.C.), Chapter 4, Section 403 authorizes the Secretary to use funds appropriated to carry out this section to conduct research and development activities, including demonstration projects and the collection and analysis of highway and motor vehicle safety data and related information with respect to all aspects of highway and traffic safety systems and conditions relating to vehicle, highway, driver, passenger, motorcyclist, bicyclist, and pedestrian characteristics; accident causation and investigations; and human behavioral factors and their effect on highway and traffic safety, including driver education, impaired driving and distracted driving; and research on, evaluations of, and identification of best practices related to driver education programs (including driver education curricula, instructor training and certification, program administration, and delivery mechanisms) and make recommendations for harmonizing driver education and multistage graduated licensing systems; and the effect of State laws on any aspects, activities, or programs described in subparagraphs (A) through (E) (see 23 U.S.C. 403(b)(1)(A)(i)-(ii), 23 U.S.C. 403(b)(1)(B)(i)-(iii), 23 U.S.C. 403(b)(1)(E), 23 U.S.C. 403(b)(1)(F)).</P>
                <P>
                    FMCSA published a notice in the 
                    <E T="04">Federal Register</E>
                     with a 60-day public comment period to announce this proposed information collection on November 28, 2025 (90 FR 54850). A total of eight comments were received from the public. Five of the comments were from truck drivers (one of whom created a truck parking business), two were from industry organizations (American Trucking Associations and Truckload Carriers Association), and one was from a private company (Samsara). Each commenter agreed that truck parking is a significant issue for the commercial trucking industry. Seven of the eight commenters were supportive of the study, while one commenter (an anonymous truck driver) was skeptical of government involvement in truck parking and preferred to let private truck stop companies solve the truck parking shortage entirely.
                </P>
                <P>Anthony Peetz and an anonymous commenter mentioned how the truck parking situation has changed over the past several decades and provided examples of how the trucking industry's needs have surpassed what infrastructure and the private sector are currently able to provide. Anthony Peetz and the American Trucking Associations mentioned the growth in paid parking spaces and the frustration truck drivers often feel when their only options are paid spaces and unauthorized spaces. FMCSA's study will focus on the benefits of truck parking spaces in general and does not intend to assess the advantages and disadvantages of paid and free spaces.</P>
                <P>
                    The American Trucking Associations, Samsara, and an anonymous commenter mentioned costs associated with the lack of truck parking spaces, including carrier operating costs, crashes involving trucks parked in unauthorized spaces, and driver well-being. FMCSA is including all of the costs mentioned by commenters in the study, as well as others not mentioned in the comments (such as the costs of travel that occurs 
                    <PRTPAGE P="17326"/>
                    when a driver goes off his/her main route to search for parking).
                </P>
                <P>Samsara mentioned the potential for telematics data to be helpful. FMCSA agrees and is indeed considering utilizing telematics data for the study.</P>
                <P>The American Trucking Associations and Gary D. Terhune mentioned the facilities that are sometimes available at truck parking locations (restrooms, trash cans, vending machines, etc.). FMCSA agrees that those amenities are important, but estimating their benefits would be beyond the scope of this study.</P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including: (1) whether the proposed collection is necessary for the performance of FMCSA's functions; (2) the accuracy of the estimated burden; (3) ways for FMCSA to enhance the quality, usefulness, and clarity of the collected information; and (4) ways that the burden could be minimized without reducing the quality of the collected information.
                </P>
                <SIG>
                    <P>Issued under the authority of 49 CFR 1.87.</P>
                    <NAME>David M. Sutula,</NAME>
                    <TITLE>Acting Associate Administrator, Office of Research and Registration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06597 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Maritime Administration</SUBAGY>
                <DEPDOC>[Docket Number MARAD-2026-0496]</DEPDOC>
                <SUBJECT>Request for Information: Icebreaker Collaboration Effort (ICE) Pact</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration (MARAD), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice requests information from the public to assist MARAD in determining which shipyards in the U.S. have the capacity to construct ships capable of operating in ice conditions and to identify what factors would be necessary to further develop and construct icebreaker ships in the U.S. Information gathered in response to the request could be used to increase the capacity of the U.S. to design, produce, and maintain polar icebreakers through trilateral collaboration with Canada and Finland, while supporting each country's shipbuilding industrial base.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>To ensure that you do not duplicate your docket submissions, please submit all comments by only one of the following ways:</P>
                    <P>
                          
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov,</E>
                         search the docket number listed above and follow the online instructions for submitting comments.
                    </P>
                    <P>
                          
                        <E T="03">Mail:</E>
                         Docket Management Facility, U.S. Department of Transportation, 1200 New Jersey Avenue SE, W12-140, Washington, DC 20590-0001.
                    </P>
                    <P>
                          
                        <E T="03">Hand Delivery:</E>
                         Suite W12-140 of the Department of Transportation, 1200 New Jersey Avenue SE, Washington, DC 20590 between 9:00 a.m. and 5:00 p.m. E.T., Monday through Friday, except Federal Holidays. The telephone number is 202-366-9329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         You must include the agency name and the docket number at the beginning of your comments. All comments received will be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided.
                    </P>
                </ADD>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>
                         Input submitted online via 
                        <E T="03">www.regulations.gov</E>
                         is not immediately posted to the site. It may take several business days before your submission is posted.
                    </P>
                </NOTE>
                <P>
                    <E T="03">Privacy Act:</E>
                     Anyone can search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). For information on DOT's compliance with the Privacy Act, please visit 
                    <E T="03">https://www.transportation.gov/privacy.</E>
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. David Heller, Deputy Associate Administrator for Shipbuilding and Industry Expansion, 202-366-1850, or via email at 
                        <E T="03">david.heller@dot.gov.</E>
                         Office hours for MARAD are from 8:00 a.m. to 4:30 p.m., E.T., Monday through Friday, except Federal holidays.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On November 19, 2025, representatives of the United States, Canada, and Finland signed a Joint Statement of Intent (JSOI) outlining their intentions for advancing the Icebreaker Collaboration Effort, or ICE Pact. This trilateral framework aims to enhance collaboration on the production of polar ice breakers and related capabilities, while fostering stronger security and economic ties among the three nations. The initiative focuses on bolstering the signatory nations' shipbuilding industries and industrial capacity, through information exchange and workforce development in the context of polar icebreaker construction and other polar capabilities.</P>
                <P>ICE Pact comprises four key components: enhanced information sharing and technical exchange between the three countries, collaboration on workforce development, an invitation for allies and partners to purchase icebreakers built in U.S., Canadian, or Finnish shipyards, and collaborating on research and development. Recognizing the capital-intensive nature of shipbuilding, the framework emphasizes the importance of long-term, multi-ship orderbooks to ensure the viability of shipyards. By leveraging their shipbuilding capacities, the United States, Canada, and Finland aim to not only meet their own needs but also support partner nations in accessing polar regions at an affordable cost.</P>
                <P>The framework also supports directly the fielding of needed polar capabilities. This is particularly important to the U.S. Coast Guard's Polar Security Cutter (PSC) and Arctic Security Cutter (ASC) programs, through which the U.S. Coast Guard seeks to build new heavy and medium icebreakers. On October 8, 2025, President Trump issued a memorandum titled “Construction of Arctic Security Cutters,” wherein he determined the current fleet of American icebreakers to be insufficient to meet operational demands. President Trump directed the leveraging of ICE Pact to inform a plan that would build a select number of ASCs abroad, in a phased manner that promotes the on-shoring of expertise necessary to build follow-on icebreakers domestically. These vessels will serve as vital national assets, ensuring access to polar regions and fulfilling crucial missions such as defense readiness, all while operating alongside the icebreakers of allied nations in the extreme environmental conditions of the high latitudes.</P>
                <P>To focus workforce development initiatives, the Department of Homeland Security, in consultation with the Departments of Transportation and Labor, developed and released in November 2025 the Icebreaker Collaboration Effort U.S. National Workforce Development Plan. This plan serves as a framework for coordinating U.S. government efforts in supporting the development of the skilled trades and occupations across various sectors, including the domestic maritime industrial base, necessary to build icebreakers domestically.</P>
                <HD SOURCE="HD1">Request for Information (RFI)</HD>
                <P>
                    MARAD requests relevant comments and information from U.S. shipyards involved in the design, manufacture, export, and research and development 
                    <PRTPAGE P="17327"/>
                    of polar icebreaker and related capabilities.
                </P>
                <P>The following information is requested; please provide as much detail as possible:</P>
                <P>(1) What economic opportunities or risks may accrue to communities from increased U.S. polar shipbuilding activity (jobs, infrastructure demands, or other potential impacts)?</P>
                <P>(2) What regional infrastructure investments (ports, utilities, transportation networks, technology, or other investments) are required to support expanded icebreaker production?</P>
                <P>(3) What barriers prevent small or mid-sized suppliers from participating in the polar shipbuilding supply chain?</P>
                <P>(4) What incentives or technical assistance would help small businesses join or scale in the shipbuilding supply chain?</P>
                <P>(5) What information-sharing mechanisms would help suppliers better anticipate demand, align production, or mitigate risk?</P>
                <P>(6) Are there critical materials or components that should be produced or stockpiled domestically?</P>
                <P>(7) How can local schools, technical colleges, and apprenticeship programs be better integrated into ICE Pact workforce development? What existing educational or training programs could contribute to ICE Pact workforce development?</P>
                <P>(8) What new curricula or certifications would help prepare workers for polar vessel design and construction, and how are trade unions involved in the development of the workforce or in recruiting and retaining workers?</P>
                <P>(9) What community-level factors (housing availability, childcare, transportation, cost of living, or other factors) influence the ability to recruit and retain workers in shipbuilding regions?</P>
                <P>(10) What innovations and advanced technologies (AI-enabled design tools, robotics, digital twins, cold-weather materials, alternative fuel systems, or other advanced technologies) should be prioritized for collaboration under ICE Pact?</P>
                <P>(11) What specific testing facilities does the U.S. need to be successful (materials labs, climate chambers, autonomous systems ranges, or other facilities)? Do these facilities currently exist in the U.S.?</P>
                <P>(12) What concerns do stakeholders have regarding intellectual property protection in multinational shipbuilding programs, and are there safeguards that should be implemented to protect these designs?</P>
                <P>(13) What national security requirements, including export controls, may pose problems for exports of U.S.-built icebreakers or construction in partner or ally shipyards?</P>
                <P>(14) What factors should guide decisions about exporting U.S.-built icebreakers to partners or allies?</P>
                <P>(15) What contract structures (block buys, multiyear procurement, public-private partnerships, or other structures) would help stabilize orderbooks?</P>
                <P>(16) What financial or policy tools (loan guarantees, grants, risk-sharing mechanisms, or other policy tools) would help shipyards modernize or expand?</P>
                <P>(17) What lessons from past U.S. or allied shipbuilding initiatives should be applied to ICE Pact to avoid cost overruns, delays, or capacity mismatches?</P>
                <P>(18) What models of multinational industrial cooperation (AUKUS, NATO, or other models) should be copied or avoided?</P>
                <P>(19) What basic research needs exist that would benefit icebreaker operations in the polar regions?</P>
                <P>(20) What factors should guide the development of U.S. planning for future icebreaker maintenance requirements and underlying supply chain needs?</P>
                <P>(21) In what statutorily established ways can MARAD best support the development of the skilled trades and occupations across the maritime industrial base to build icebreakers domestically?</P>
                <HD SOURCE="HD1">Electronic Access</HD>
                <P>
                    A copy of this Notice, all comments received on this Notice, and all background material may be viewed online at 
                    <E T="03">https://www.regulations.gov</E>
                     using the docket number listed above. Electronic retrieval help and guidelines are also available at 
                    <E T="03">https://www.regulations.gov.</E>
                     An electronic copy of this document also may be downloaded from the Office of the Federal Register's website at: 
                    <E T="03">www.FederalRegister.gov</E>
                     and the Government Publishing Office's database at: 
                    <E T="03">www.GovInfo.gov.</E>
                </P>
                <HD SOURCE="HD1">Confidential Business Information</HD>
                <P>Confidential Business Information (CBI) is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this RFI contain commercial or financial information that is customarily treated as private, that you actually treat as private, and that is relevant or responsive to this RFI, it is important that you clearly designate the submitted comments as CBI. You may ask DOT to give confidential treatment to information you give to the Department by taking the following steps: (1) Mark each page of the original document submission containing CBI as “Confidential”; (2) send DOT, along with the original document, a second copy of the original document with the CBI deleted; and (3) explain why the information you are submitting is CBI. Unless you are notified otherwise, DOT will treat such marked submissions as confidential under the FOIA, and they will not be placed in the public docket of this RFI. Submissions containing CBI should be sent to Mr. David Heller, Associate Administrator for Business and Finance Development, Room W21-318, MARAD, 1200 New Jersey Avenue SE, Washington, DC 20590. Any comment submissions that DOT receives that are not specifically designated as CBI will be placed in the public docket.</P>
                <EXTRACT>
                    <FP>(Authority: 46 U.S.C. Chapter 537; 49 CFR 1.93(a), 46 CFR part 298)</FP>
                </EXTRACT>
                <SIG>
                    <P>By order of the Maritime Administrator.</P>
                    <NAME>T. Mitchell Hudson, Jr.,</NAME>
                    <TITLE>Secretary, Maritime Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06648 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-81-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2026-0793]</DEPDOC>
                <SUBJECT>Initial Decision That Certain Frontal Driver Air Bag Inflators Manufactured by Jilin Province Detiannuo Safety Technology Co., Ltd. (DTN) Contain a Safety Defect</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of initial decision.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NHTSA has made an initial decision that certain air bag inflators manufactured by DTN contain a defect related to motor vehicle safety. Available information demonstrates that the inflators were imported into the United States by unknown importers (likely illegally). NHTSA is aware of twelve instances in which the inflators have ruptured in vehicles in the United States, resulting in ten fatalities and two severe injuries. Following this initial decision, NHTSA is required by statute to seek public comment and allow the manufacturer an opportunity to dispute 
                        <PRTPAGE P="17328"/>
                        the initial decision. After review of any comments or additional relevant information, should NHTSA makes a final determination that the subject inflators contain a defect related to motor vehicle safety, the sale of the inflators (whether separately or installed in an air bag module) in the United States would be illegal.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be submitted no later than April 17, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit written submissions to the docket number identified in the heading of this document by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Docket Management Facility: U.S. Department of Transportation, 1200 New Jersey Avenue SE, West Building Ground Floor, Room W12-140, Washington, DC 20590-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier:</E>
                         1200 New Jersey Avenue SE, West Building Ground Floor, Room W12-140, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the agency name and docket number. Note that all written submissions received will be posted without change to 
                        <E T="03">https://www.regulations.gov,</E>
                         including any personal information provided. Please see the Privacy Act discussion below. We will consider all written submissions received before the closing date indicated above.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or written submissions received, go to 
                        <E T="03">https://www.regulations.gov</E>
                         at any time or to 1200 New Jersey Avenue SE, West Building Ground Floor, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal Holidays. Telephone: 202-366-9826.
                    </P>
                    <P>
                        <E T="03">Privacy Act:</E>
                         In accordance with 49 U.S.C. 30118(b)(1), NHTSA will make a final decision only after providing an opportunity for DTN and any interested person to present information, views, and arguments. DOT posts written submissions from manufacturers and interested persons, without edit, including any personal information the submitter provides, to 
                        <E T="03">www.regulations.gov,</E>
                         as described in the system of records notice (DOT/ALL-14 Federal Docket Management System (FDMS)), which can be reviewed at 
                        <E T="03">www.transportation.gov/privacy.</E>
                    </P>
                    <P>
                        <E T="03">Confidential Business Information:</E>
                         If you wish to submit any information under a claim of confidentiality, you must submit your request directly to NHTSA's Office of the Chief Counsel. Requests for confidentiality are governed by 49 CFR part 512. NHTSA is currently treating electronic submission as an acceptable method for submitting confidential business information (CBI) to the agency under Part 512.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dylan Voneiff, Office of the Chief Counsel, National Highway Traffic Safety Administration, 1200 New Jersey Avenue SE, Washington, DC 20590; 
                        <E T="03">dylan.voneiff@dot.gov.</E>
                    </P>
                    <P>
                        The publicly available information on which this initial decision is based will be available on the agency's website at, 
                        <E T="03">https://www.nhtsa.gov/recalls?nhtsaId=EA25005,</E>
                         and on the public docket under the docket number in the heading of this document.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to 49 U.S.C. 30118(a) and 49 CFR 554.10, NHTSA has made an initial decision that certain frontal driver air bag inflators manufactured by Jilin Province Detiannuo Safety Technology Co., Ltd. (DTN) contain a defect related to motor vehicle safety. These air bag inflators have been imported into the United States by unknown importers, likely illegally. NHTSA is aware of twelve instances in which such inflators have ruptured in vehicles in the United States after the vehicle's air bag was commanded to deploy, causing metal debris to be forcefully ejected into the vehicle's occupant compartment, resulting in ten deaths and two severe injuries. NHTSA has concluded that these inflators pose an unreasonable risk of serious injury or death to vehicle occupants.</P>
                <HD SOURCE="HD1">A. Inflators Subject to This Initial Decision</HD>
                <P>
                    The inflators subject to this initial decision were manufactured by DTN in 2021 and 2022, and at or about the time of manufacture were etched or labeled with an identifier beginning “DTN60DB” 
                    <SU>1</SU>
                    <FTREF/>
                     on the face of the inflator cap. Exemplar photographs of the marking or labeling are shown below: 
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The manufacture date of the inflators is also part of the code etched onto the inflator cap. The code begins DTN60DB, is followed by four digits representing the year of manufacture, two digits representing the month of manufacture, two digits representing the day of manufacture, and ending in a part identification sequence number.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Larger photographs can be found in a docket memorandum. 
                        <E T="03">See</E>
                         60DB Inflator Photographs, Docket No. NHTSA-2026-0793, 
                        <E T="03">www.regulations.gov/documents/NHTSA-2026-0793.</E>
                    </P>
                </FTNT>
                <GPH SPAN="3" DEEP="137">
                    <GID>EN6AP26.082</GID>
                </GPH>
                <P>In addition, the inflators have a label on the electrical connector side that includes a bar code containing the number sequence “144415654 666631” or “144415654 666633.” This label remains visible when the inflator is installed in an air bag module. An exemplar photo is shown below:</P>
                <GPH SPAN="1" DEEP="167">
                    <PRTPAGE P="17329"/>
                    <GID>EN6AP26.083</GID>
                </GPH>
                <P>
                    The inflators subject to this initial decision are described as the “subject inflators.” In at least ten of the twelve incidents outlined below, the subject inflators were installed as replacement (
                    <E T="03">i.e.,</E>
                     aftermarket) equipment after the vehicle was involved in a previous crash in which a driver air bag deployed. NHTSA does not have information about how or why subject inflators were installed in the other two incidents.
                </P>
                <P>Since the subject inflators were likely imported illegally, NHTSA has been unable, despite substantial efforts, to obtain sufficient information to estimate the number of subject inflators in the United States with any confidence. The agency's investigation is continuing.</P>
                <HD SOURCE="HD1">B. Known Inflator Ruptures Resulting in Deaths and Injuries</HD>
                <P>The agency is currently aware of twelve confirmed subject inflator ruptures in the United States. At least ten of the incidents involved vehicles that had their air bags replaced following a prior crash.</P>
                <P>• On May 30, 2023, a DTN60DB inflator manufactured in December 2021ruptured in a Model Year 2018 Chevrolet Malibu during a crash in Dallas, TX. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On June 11, 2023, a DTN60DB inflator manufactured in November 2021 ruptured in a Model Year 2020 Chevrolet Malibu during a crash in Sarasota, FL. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On September 4, 2023, a DTN60DB inflator manufactured in November 2021ruptured in a Model Year 2021 Chevrolet Malibu during a crash in Philadelphia, PA. The driver was severely injured by shrapnel expelled from the ruptured inflator.</P>
                <P>• On October 25, 2023, a DTN60DB inflator with an unknown date of manufacture ruptured in a Model Year 2020 Chevrolet Malibu during a crash in Fort Worth, TX. The driver was severely injured by shrapnel expelled from the ruptured inflator.</P>
                <P>• On March 1, 2024, a DTN60DB inflator manufactured in December 2021 ruptured in a Model Year 2022 Chevrolet Malibu during a crash in Oklahoma City, OK. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On February 3, 2025, a DTN60DB inflator manufactured in June 2022 ruptured in a Model Year 2017 Hyundai Sonata during a crash in Phoenix, AZ. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On July 30, 2025, a DTN60DB inflator manufactured in March 2022 ruptured in a Model Year 2019 Hyundai Sonata during a crash in West Valley City, UT. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On September 26, 2025, a DTN60DB inflator manufactured in November 2021 ruptured in a Model Year 2020 Chevrolet Malibu during a crash in Hayward, CA. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On October 31, 2025, a DTN60DB inflator manufactured in December 2021 ruptured in a Model Year 2018 Chevrolet Malibu during a crash in Wichita, KS. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On December 16, 2025, a DTN60DB inflator manufactured in December 2021 ruptured in a Model Year 2019 Chevrolet Malibu during a crash in Toledo, OH. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On December 16, 2025, a DTN60DB inflator manufactured in January 2022 ruptured in a Model Year 2018 Hyundai Sonata during a crash in Austin, TX. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>• On February 16, 2026, a DTN60DB manufactured in June 2022 ruptured in a Model Year 2020 Chevrolet Malibu during a crash in Clarksdale, MS. The driver was killed by shrapnel expelled from the ruptured inflator.</P>
                <P>Though NHTSA is only aware of ruptures involving subject inflators installed as aftermarket equipment in Chevrolet Malibu or Hyundai Sonata vehicles, there is no information indicating the problem is limited to those vehicles.</P>
                <HD SOURCE="HD1">C. Background Regarding Air Bags</HD>
                <P>Air bags are safety equipment designed to protect vehicle occupants in the event of a crash. Air bags have been used in passenger vehicles since the 1970s and were mandated by NHTSA in 1991. All new vehicles have been required to have frontal air bags since September 1998. Paired with seat belts, air bags forcibly deploy to control the movement of the occupant's upper body and head during a moderate to severe crash. Upon such an occurrence, a signal to the air bag system's electronic control unit initiates the ignition of propellant housed within an inflator to rapidly generate gas that will fill an air bag cushion to deploy in a manner that limits forward movement by the occupant.</P>
                <P>The subject inflators are pyrotechnic gas-generators. In general, an air bag inflator is a component part of an air bag module. An air bag module typically consists of a mounting bracket, inflator (device that generates gas), cushion (bag that fills with gas), cover (decorative part that matches the vehicle interior), and connecting wires.</P>
                <P>
                    Air bags, when properly deployed, provide significant safety benefits. NHTSA estimates that frontal air bags have saved more than fifty thousand lives over the past 30 years.
                    <SU>3</SU>
                    <FTREF/>
                     The rupture of an air bag inflator during deployment is rare and extremely dangerous. Instead of remaining intact within the module and releasing gas into the cushion, the metal inflator explodes—ejecting metal shrapnel from the module in a manner likely to kill or severely injure any human with which it makes direct contact.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">https://www.nhtsa.gov/vehicle-safety/air-bags.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">D. Legal Background on Safety Defects and Legal Consequences</HD>
                <P>
                    The National Traffic and Motor Vehicle Safety Act (Safety Act), as amended, requires manufacturers (including importers) to conduct a recall for safety defects in motor vehicles and motor vehicle equipment. 
                    <E T="03">See</E>
                     49 U.S.C. 30118-20; 
                    <E T="03">see also id.</E>
                     sec. 30102(a)(6). Specifically, a manufacturer must notify NHTSA, owners, dealers, and distributors of any “defect . . . related to motor vehicle safety.” 49 U.S.C. 30118. The Safety Act defines “defect” as “includ[ing] any defect in performance, construction, a component, or material of a motor vehicle or motor vehicle equipment.” 49 U.S.C. 30102(a)(3). “Motor vehicle safety” means “the performance of a motor vehicle or motor vehicle equipment in a way that protects the public against unreasonable risk of accidents occurring because of the design, construction, or performance of a motor vehicle, and against unreasonable risk of death or injury in 
                    <PRTPAGE P="17330"/>
                    an accident, and includes nonoperational safety of a motor vehicle.” 
                    <E T="03">Id.</E>
                     sec. 30101(a)(8).
                </P>
                <P>
                    Identifying the root cause of a failure is not necessary to make a safety defect determination. 
                    <E T="03">See United States</E>
                     v. 
                    <E T="03">Gen. Motors Corp.,</E>
                     518 F.2d 420, 432 (D.C. Cir. 1975) (explaining that “a determination of `defect' does not require any predicate of a finding identifying engineering, metallurgical, or manufacturing failures”). A defect that leads to failure of a vital component, such as an air bag rupturing rather than protecting the driver, presents an unreasonable risk to safety. 
                    <E T="03">See United States</E>
                     v. 
                    <E T="03">General Motors Corp.</E>
                     561 F.2d 923, 929 (D.C. Cir. 1977) (“
                    <E T="03">Pitman Arms</E>
                    ”).
                </P>
                <P>
                    Any safety defect determination on replacement equipment,
                    <SU>4</SU>
                    <FTREF/>
                     whether made by NHTSA or by a manufacturer, results in a prohibition on the sale of the equipment for installation in a motor vehicle. 49 U.S.C. 30120(j). In addition, if NHTSA issues a final decision that there is a safety defect, no person may “sell, offer for sale, introduce or deliver for introduction in interstate commerce, or import into the United States” the equipment subject to the determination. 
                    <E T="03">Id.</E>
                     sec. 30112(a)(3). In other words, if NHTSA issues a final decision finding a safety defect, the sale by any person of either a subject inflator or a module containing a subject inflator for installation in a motor vehicle in the United States would be illegal.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Replacement equipment is “motor vehicle equipment . . . that is not original equipment” “installed on a motor vehicle at the time of delivery to the first purchaser.” 49 U.S.C. 30102(b)(1)(C), (D). Under the Safety Act, an air bag inflator used to replace a previously deployed air bag is replacement equipment. 
                        <E T="03">See id.</E>
                         § 30102(a)(8), (b)(1)(C), (D). An equipment manufacturer, including an importer, is responsible under the Safety Act for recalling replacement equipment. 
                        <E T="03">See id.</E>
                         §§ 30102(a)(6), 30118(b).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">E. The Agency's Investigation</HD>
                <P>On October 21, 2025, NHTSA's Office of Defects Investigation (ODI) opened an Engineering Analysis (EA25005) to investigate allegations of ruptures involving air bag inflators manufactured by DTN.</P>
                <P>NHTSA's investigation was prompted by reports of eight vehicle crashes in which a rupture of a DTN air bag inflator occurred during the deployment of the driver side air bag.</P>
                <P>On June 16, 2023, ODI received a Vehicle Owner Questionnaire (VOQ #11527380) alleging that the rupture of a driver side air bag inflator caused fatal injuries to the driver of a MY 2020 Chevrolet Malibu. ODI's assessment of the rupture indicated that the air bag inflator was not original equipment and was instead manufactured by DTN.</P>
                <P>From June 2023 to July 2024, ODI became aware of four additional ruptures involving substandard air bag modules equipped on Chevrolet Malibu vehicles. At the time, there was insufficient information to determine who manufactured the ruptured inflators. In March 2025, NHTSA learned of another rupture involving a suspected substandard, aftermarket inflator that was equipped in a MY 2017 Hyundai Sonata. The driver of this vehicle sustained fatal injuries that appeared related to the rupture. In August 2025, NHTSA received a similar report of a fatal air bag rupture in a MY 2019 Hyundai Sonata. In October 2025, NHTSA learned of a fatal air bag rupture in a MY 2020 Chevrolet Malibu. Photographs of the air bag components in these three crashes indicated that DTN manufactured each ruptured inflator. Further investigation of the inflator fragments in three of the prior incidents confirmed that DTN also manufactured those ruptured inflators. Photographs of the components involved in one of the other incidents also strongly suggested that the ruptured inflator was manufactured by DTN.</P>
                <P>After the investigation was opened, NHTSA learned of four additional crashes involving ruptures of DTN inflators. One rupture occurred in a crash in late October 2025, two additional ruptures occurred in December 2025, and a fourth in February 2026. Each of these inflator ruptures resulted in fatal injuries to the driver, for a total of twelve crashes involving ten deaths and two severe injuries.</P>
                <P>
                    As part of its investigation, NHTSA sent an information request to DTN on December 23, 2025 asking for information about the subject components.
                    <SU>5</SU>
                    <FTREF/>
                     DTN responded on February 3, 2026 with certain production and component data.
                    <SU>6</SU>
                    <FTREF/>
                     NHTSA sent DTN a supplemental information request on March 6, 2026 seeking additional information.
                    <SU>7</SU>
                    <FTREF/>
                     DTN failed to respond by the due date of March 23, 2023.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">https://static.nhtsa.gov/odi/inv/2025/INIM-EA25005-34958.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See https://www.nhtsa.gov/recalls?nhtsaId=EA25005.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Because of the severe risk, lives lost, and serious injuries to date, NHTSA is issuing this initial decision concluding that the subject inflators contain a defect related to motor vehicle safety posing an unreasonable risk of death or serious injury in the event of a crash.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Although NHTSA has often issued a recall request letter in advance of issuing an initial decision, that is not a required step. In consideration of the circumstances here, NHTSA is proceeding with the statutory process, which begins with issuance of an initial decision. 
                        <E T="03">See</E>
                         49 U.S.C. 30118(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">G. Additional Information on the Initial Decision of a Safety Defect</HD>
                <P>
                    Based on its investigation, NHTSA has made an initial decision, pursuant to 49 U.S.C. 30118(a) and 49 CFR 554.10, that the subject inflators contain a safety-related defect. Ruptures of the subject inflators during the deployment of the air bag in a crash have led to ten fatalities from May 30, 2023 to present. Two additional ruptures of the subject inflators during that time resulted in severe injuries. The agency preliminarily finds that this number of performance failures of air bag inflators is sufficient to establish a safety defect, since, in addition to failing to protect vehicle occupants as they should, they pose a direct risk of death or serious injury to vehicle occupants. Air bags are essential, legally-required items of motor vehicle equipment. 
                    <E T="03">See</E>
                     49 CFR 571.208. Absent a defect, an air bag inflator inflates the air bag, helping to minimize or avoid injury to occupants in a crash. When the subject inflators malfunction, they not only fail to function as a safety device, but instead actively threaten death or injury—even in crashes where vehicle occupants would otherwise likely emerge unharmed. The agency preliminarily finds that this defect poses an unreasonable risk of death or injury from metal parts forcibly propelled into the occupant compartment of a vehicle during a crash.
                </P>
                <P>
                    Pursuant to the Safety Act, NHTSA may make a final decision “only after giving the manufacturer an opportunity to present information, views, and arguments showing that there is no defect or noncompliance or that the defect does not affect motor vehicle safety. Any interested person also shall be given an opportunity to present information, views, and arguments.” 49 U.S.C. 30118(b)(1).
                    <SU>9</SU>
                    <FTREF/>
                     If NHTSA makes a final decision that the subject inflators contain a safety defect, NHTSA will issue an order requiring compliance with the Safety Act.
                    <SU>10</SU>
                      
                    <E T="03">See id.</E>
                      
                    <PRTPAGE P="17331"/>
                    § 30118(b)(2); 
                    <E T="03">see also id.</E>
                     §§ 30112(a)(3), 30120(j).
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Although NHTSA may hold a public hearing under 49 CFR 554.10, such a hearing is not required. 
                        <E T="03">See</E>
                         49 U.S.C. 30118(a)-(b);49 CFR 554.10(a). In consideration of the ten fatalities and two severe injuries, NHTSA is forgoing a public hearing and will instead seek written submissions. Given the risk of death or severe injury from a ruptured inflator, NHTSA is limiting the comment period to 15 days. 
                        <E T="03">See</E>
                         49 CFR 554.10(a).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Authority:</E>
                     49 U.S.C. 30118(a), (b); 49 CFR 554.10; delegations of authority at 49 CFR 1.50(a) and 49 CFR 501.8.
                </P>
                <SIG>
                    <DATED>Issued on: April 2, 2026.</DATED>
                    <NAME>Eileen Sullivan, </NAME>
                    <TITLE>Associate Administrator for Enforcement.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06620 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Information Collection Renewal; Submission for OMB Review; Privacy of Consumer Financial Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency (OCC), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P> The OCC, as part of its continuing effort to reduce paperwork and respondent burden, invites comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995 (PRA). In accordance with the requirements of the PRA, the OCC may not conduct or sponsor, and the respondent is not required to respond to, an information collection unless it displays a currently valid Office of Management and Budget (OMB) control number. The OCC is soliciting comment concerning the renewal of its information collection titled, “Privacy of Consumer Financial Information.” The OCC also is giving notice that it has sent the collection to OMB for review.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by May 6, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> Commenters are encouraged to submit comments by email, if possible. You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Email: prainfo@occ.treas.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Chief Counsel's Office, Attention: Comment Processing, Office of the Comptroller of the Currency, Attention: 1557-0216, 400 7th Street SW, Suite 3E-218, Washington, DC 20219.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         400 7th Street SW, Suite 3E-218, Washington, DC 20219.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (571) 293-4835.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         You must include “OCC” as the agency name and “1557-0216” in your comment. In general, the OCC will publish comments on 
                        <E T="03">www.reginfo.gov</E>
                         without change, including any business or personal information provided, such as name and address information, email addresses, or phone numbers. Comments received, including attachments and other supporting materials, are part of the public record and subject to public disclosure. Do not include any information in your comment or supporting materials that you consider confidential or inappropriate for public disclosure.
                    </P>
                    <P>
                        Written comments and recommendations for the proposed information collection should also be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         You can find this information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                    <P>You may review comments and other related materials that pertain to this information collection following the close of the 30-day comment period for this notice by the method set forth in the next bullet.</P>
                    <P>
                        • 
                        <E T="03">Viewing Comments Electronically:</E>
                         Go to 
                        <E T="03">www.reginfo.gov.</E>
                         Hover over the “Information Collection Review” tab and click on “Information Collection Review” from the drop-down menu. From the “Currently under Review” drop-down menu, select “Department of the Treasury” and then click “submit.” This information collection can be located by searching OMB control number “1557-0216” or “Privacy of Consumer Financial Information.” Upon finding the appropriate information collection, click on the related “ICR Reference Number.” On the next screen, select “View Supporting Statement and Other Documents” and then click on the link to any comment listed at the bottom of the screen.
                    </P>
                    <P>
                        • For assistance in navigating 
                        <E T="03">www.reginfo.gov,</E>
                         please contact the Regulatory Information Service Center at (202) 482-7340.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Shaquita Merritt, Clearance Officer, (202) 649-5490, Chief Counsel's Office, Office of the Comptroller of the Currency, 400 7th Street SW, Washington, DC 20219. If you are deaf, hard of hearing, or have a speech disability, please dial 7-1-1 to access telecommunications relay services.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                     Under the PRA (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), Federal agencies must obtain approval from the OMB for each collection of information that they conduct or sponsor. “Collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) to include agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. The OCC asks the OMB to extend its approval of the collection in this notice.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Privacy of Consumer Financial Information.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1557-0216.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit.
                </P>
                <P>
                    <E T="03">Description:</E>
                     The Gramm-Leach-Bliley Act (Act) (Pub. L. 106-102) requires this information collection. Regulation P (12 CFR part 1016), a regulation promulgated by the Consumer Financial Protection Board (CFPB), implements the Act's notice requirements and restrictions on a financial institution's ability to disclose nonpublic personal information about consumers to nonaffiliated third parties.
                </P>
                <P>The information collection requirements in 12 CFR part 1016 are as follows:</P>
                <FP>§ 1016.4(a) Initial privacy notice to consumers requirement—A national bank or Federal savings association must provide a clear and conspicuous notice to customers and consumers that accurately reflects its privacy policies and practices.</FP>
                <FP>§ 1016.5(a)(1) Annual privacy notice to customers requirement—A national bank or Federal savings association must provide a clear and conspicuous notice to customers that accurately reflects its privacy policies and practices not less than annually during the continuation of the customer relationship.</FP>
                <FP>§ 1016.8(a) Revised privacy notices—A national bank or Federal savings association must not disclose any nonpublic personal information to a nonaffiliated third party in a way that is inconsistent with the notices previously given to a consumer unless the institution has provided the consumer with a clear and conspicuous revised notice of the institution's policies and practices, the institution has provided the consumer with a new opt out notice, the institution has given the consumer a reasonable opportunity to opt out of the disclosure, and the consumer has not opted out.</FP>
                <FP>
                    § 1016.7(a) Form of opt out notice to consumers; opt out methods—Form of opt out notice—If a national bank or Federal savings association is required to provide an opt out notice under § 1016.10(a), it must provide to each of its consumers a clear and conspicuous notice that accurately explains the right to opt out under that section. The notice must state:
                    <PRTPAGE P="17332"/>
                </FP>
                <P>• That the national bank or Federal savings association discloses or reserves the right to disclose nonpublic personal information about its consumer to a nonaffiliated third party;</P>
                <P>• That the consumer has the right to opt out of that disclosure; and</P>
                <P>• A reasonable means by which the consumer may exercise the opt out right.</P>
                <P>A national bank or Federal savings association provides a reasonable means to exercise an opt out right if it:</P>
                <P>• Designates check-off boxes on the relevant forms with the opt out notice;</P>
                <P>• Includes a reply form with the opt out notice;</P>
                <P>• Provides an electronic means to opt out; or</P>
                <P>• Provides a toll-free number that consumers may call to opt out.</P>
                <P>§§ 1016.10(a)(1) and (2) and 1016.10(c)—Limits on disclosure of nonpublic personal information to nonaffiliated parties—A national bank or Federal savings association may not disclose any nonpublic personal information about a consumer to a nonaffiliated third party unless the institution has provided the consumer with an initial notice under § 1016.4, the institution has provided the consumer with a opt out notice, the institution has given the consumer a reasonable opportunity to opt out of the disclosure, and the consumer has not opted out. A customer may direct one of the following forms of opt out:</P>
                <P>• Opt out—Consumers may direct that the national bank or Federal savings association not disclose nonpublic personal information about them to a nonaffiliated third party, other than permitted by §§ 1016.13-1016.15.</P>
                <P>• Partial opt out—Consumers may exercise partial opt out rights by selecting certain nonpublic personal information or certain nonaffiliated third parties with respect to which the consumer wishes to opt out.</P>
                <P>§§ 1016.7(h) and 1016.7(i) Continuing right to opt out and Duration of right to opt out—A consumer may exercise the right to opt out at any time. A consumer's direction to opt out is effective until the consumer revokes it in writing or, if the consumer agrees, electronically. When a customer relationship terminates, the customer's opt out direction continues to apply to the nonpublic personal information collected during or related to that relationship. If the individual subsequently establishes a new customer relationship with the institution, the opt out direction that applied to the former relationship does not apply to the new relationship.</P>
                <HD SOURCE="HD1">Estimated Burden</HD>
                <P>
                    <E T="03">Estimated Frequency of Response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     2,451,569.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     625,291 hours.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     On October 2, 2025, the OCC published a 60-day notice for this information collection (90 FR 47905). No comments were received.
                </P>
                <P>Comments continue to be invited on:</P>
                <P>(a) Whether the collection of information is necessary for the proper performance of the functions of the OCC, including whether the information has practical utility;</P>
                <P>(b) The accuracy of the OCC's estimate of the burden of the collection of information;</P>
                <P>(c) Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>(d) Ways to minimize the burden of the collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>(e) Estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <SIG>
                    <NAME>Eden Gray,</NAME>
                    <TITLE>Assistant Director, Office of the Comptroller of the Currency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06558 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Comment Request on Rules for Certain Rental Real Estate Activities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the IRS is inviting comments on the information collection request outlined in this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 5, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Include “OMB Control No. 1545-2194” in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Requests for additional information or copies of this collection should be directed to Kerry Dennis, (202) 317-5751.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The IRS, in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the IRS assess the impact and minimize the burden of its information collection requirements. Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record, and viewable on relevant websites. For this reason, please do not include in your comments information of a confidential nature, such as sensitive personal information. Comments are invited on: (a) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>
                    <E T="03">Title:</E>
                     Rules for Certain Rental Real Estate Activities.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1545-2194.
                </P>
                <P>
                    <E T="03">Revenue Procedure Number:</E>
                     2011-34.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This revenue procedure grants relief under Section 1.469-9(g) for certain taxpayers to make late elections to treat all interests in rental real estate as a single rental real estate activity.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There is no change to the previously approved information collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individual or Households.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     2,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     30 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     1,000 hours.
                </P>
                <SIG>
                    <PRTPAGE P="17333"/>
                    <DATED>Dated: April 1, 2026.</DATED>
                    <NAME>Kerry Dennis,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06592 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4831-GV-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Comment Request on Forms 5498-QA and 1099-QA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the IRS is inviting comments on the information collection request outlined in this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 5, 2026 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Andres Garcia, Internal Revenue Service, Room 6526, 1111 Constitution Avenue NW, Washington, DC 20224, or by email to 
                        <E T="03">pra.comments@irs.gov.</E>
                         Include “OMB Control No. 1545-2262” in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        View the latest drafts of the tax forms related to the information collection listed in this notice at 
                        <E T="03">https://www.irs.gov/draft-tax-forms.</E>
                         Requests for additional information or copies of this collection should be directed to LaNita Van Dyke, 202-317-3009.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The IRS, in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the IRS assess the impact and minimize the burden of its information collection requirements. Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record, and viewable on relevant websites. For this reason, please do not include in your comments information of a confidential nature, such as sensitive personal information. Comments are invited on: (a) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>
                    <E T="03">Title:</E>
                     ABLE Account Contribution Information; Distributions from ABLE Accounts.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1545-2262.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     5498-QA; 1099-QA.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Achieving a Better Life Experience (ABLE) Act of 2014 allows states to create tax-advantaged savings programs for eligible people with disabilities (designated beneficiaries). Funds from these ABLE accounts can help designated beneficiaries pay for qualified expenses. Form 5498-QA is used by the qualified ABLE program to report contributions and rollovers to an ABLE account, as well as the fair market value of the account. Form 1099-QA is used by the qualified ABLE program to report distributions from an ABLE account.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     Form 5498-QA is being revised to capture amounts rolled over from a Trump account to an ABLE account.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals and households.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     20,000.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     11 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     3,600.
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>LaNita Van Dyke,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06611 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4831-GV-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>List of Countries Requiring Cooperation With an International Boycott</SUBJECT>
                <P>In accordance with section 999(a)(3) of the Internal Revenue Code of 1986, the Department of the Treasury is publishing a current list of countries which require or may require participation in, or cooperation with, an international boycott (within the meaning of section 999(b)(3) of the Internal Revenue Code of 1986).</P>
                <P>On the basis of the best information currently available to the Department of the Treasury, the following countries require or may require participation in, or cooperation with, an international boycott (within the meaning of section 999(b)(3) of the Internal Revenue Code of 1986).</P>
                <FP SOURCE="FP-1">Iraq</FP>
                <FP SOURCE="FP-1">Kuwait</FP>
                <FP SOURCE="FP-1">Lebanon</FP>
                <FP SOURCE="FP-1">Libya</FP>
                <FP SOURCE="FP-1">Qatar</FP>
                <FP SOURCE="FP-1">Saudi Arabia</FP>
                <FP SOURCE="FP-1">Syria</FP>
                <FP SOURCE="FP-1">Yemen</FP>
                <SIG>
                    <NAME>James Wang,</NAME>
                    <TITLE>International Tax Counsel, (Tax Policy).</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-06596 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AK-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Interest Rate Paid on Cash Deposited To Secure U.S. Immigration and Customs Enforcement Immigration Bonds</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Departmental Offices, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>For the period beginning April 1, 2026, and ending on June 30, 2026, the U.S. Immigration and Customs Enforcement Immigration Bond interest rate is 3 per centum per annum.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Rates are applicable April 1, 2026, to June 30, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments or inquiries may be mailed to Will Walcutt, Supervisor, Funds Management Branch, Funds Management Division, Fiscal Accounting, Bureau of the Fiscal Services, Parkersburg, West Virginia 26106-1328.</P>
                    <P>
                        You can download this notice at the following internet addresses: &lt;
                        <E T="03">http://www.treasury.gov</E>
                        &gt; or &lt;
                        <E T="03">http://www.federalregister.gov</E>
                        &gt;.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ryan Hanna, Manager, Funds Management Branch, Funds Management Division, Fiscal Accounting, Bureau of the Fiscal Service, Parkersburg, West Virginia 261006-1328 (304) 480-5120; Will Walcutt, Supervisor, Funds Management Branch, Funds Management Division, Fiscal Accounting, Bureau of the Fiscal Services, Parkersburg, West Virginia 26106-1328, (304) 480-5117.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Federal law requires that interest payments on cash deposited to secure immigration 
                    <PRTPAGE P="17334"/>
                    bonds shall be “at a rate determined by the Secretary of the Treasury, except that in no case shall the interest rate exceed 3 per centum per annum.” 8 U.S.C. 1363(a). Related Federal regulations state that “Interest on cash deposited to secure immigration bonds will be at the rate as determined by the Secretary of the Treasury, but in no case will exceed 3 per centum per annum or be less than zero.” 8 CFR 293.2. Treasury has determined that interest on the bonds will vary quarterly and will accrue during each calendar quarter at a rate equal to the lesser of the average of the bond equivalent rates on 91-day Treasury bills auctioned during the preceding calendar quarter, or 3 per centum per annum, but in no case less than zero. [FR Doc. 2015-18545]. In addition to this Notice, Treasury posts the current quarterly rate in Table 2b—Interest Rates for Specific Legislation on the Treasury Direct website.
                </P>
                <P>
                    The Acting Fiscal Assistant Secretary, Gary Grippo, having reviewed and approved this document, is delegating the authority to electronically sign this document to Heidi Cohen, Federal Register Liaison for the Department, for purposes of publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Heidi Cohen,</NAME>
                    <TITLE>Federal Register Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06629 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Call for Applications for Secretary Appointment to Treasury Tribal Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces that the U.S. Department of the Treasury (Treasury), pursuant to the Tribal General Welfare Exclusion Act of 2014 (TGWEA), seeks applications on behalf of the Secretary of the Treasury (Secretary) for the appointment of three members to the Treasury Tribal Advisory Committee (TTAC). Under section 3 of the TGWEA, the TTAC was established to advise the Secretary on matters related to the taxation of Indians, training and education for Internal Revenue Service (IRS) field agents who administer and enforce internal revenue laws with respect to Indian Tribes, and training and technical assistance for Tribal financial officers. Applications should describe the candidate's qualifications for TTAC membership. Submittal of an application and resume is required to be considered.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit applications for appointment by the Secretary to the TTAC by May 29, 2026 at 5:00 p.m. AKT.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Please send applications or recommendations to 
                        <E T="03">TTAC@treasury.gov,</E>
                         with a subject line “Treasury Tribal Advisory Committee member application.”
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Fatima Abbas, Designated Federal Officer for the TTAC, by emailing 
                        <E T="03">TTAC@treasury.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <HD SOURCE="HD2">I. Description and Mandate of the TTAC</HD>
                <P>Section 3 of the TGWEA, Public Law 113-68, 128 Stat. 1883 (Sept. 26, 2014), directs the Secretary of the Treasury to establish a Tribal Advisory Committee to advise the Secretary on matters related to the taxation of Indians, the training of Internal Revenue Service field agents, and the provision of training and technical assistance to Native American financial officers.</P>
                <P>
                    Pursuant to Section 3 of the TGWEA and in accordance with the provisions of the Federal Advisory Committee Act (FACA), 5 U.S.C. App. 1 
                    <E T="03">et seq.,</E>
                     the TTAC was established on February 10, 2015, as the “U.S. Department of the Treasury Tribal Advisory Committee.” The TTAC's Charter provides that it shall advise and report to the Secretary on:
                </P>
                <P>(1) Matters related to the taxation of Indians;</P>
                <P>(2) The establishment of training and education for internal revenue field agents who administer and enforce internal revenue laws with respect to Indian Tribes of Federal Indian law and the Federal Government's unique legal treaty and trust relationship with Indian Tribal governments; and</P>
                <P>(3) The establishment of training of such internal revenue field agents, and provisions of training and technical assistance to Tribal financial officers, about implementation of the TGWEA and any amendments.</P>
                <P>Section 3(c) of the TGWEA provides that the TTAC's membership is composed of seven members in total, three members appointed by the Secretary and one member appointed by each of the following four Members of Congress: the Chairman and Ranking Member of the Committee on Ways and Means of the House of Representatives and the Chairman and Ranking Member of the Committee on Finance of the Senate.</P>
                <P>This notice requests nominations for the appointment by the Secretary of three members to serve terms of four years. Recommendations for the four Congressional appointments to the TTAC expiring in 2027 and 2028 should be directed to the offices of the four Members of Congress specified in the law, whose roles are identified above.</P>
                <HD SOURCE="HD2">II. Application for TTAC Appointment</HD>
                <P>Treasury seeks applications from individuals with experience and qualifications in the subject areas identified by the TWGEA: Tribal tax, IRS field agent training, and Native American financial officer training and technical assistance. No person who is a federally-registered lobbyist may serve on the TTAC. All potential candidates must pass an IRS tax compliance check and a Federal Bureau of Investigation (FBI) background investigation. To apply, an applicant must submit an appropriately detailed resume and a cover letter that includes a description of the applicant's reasons for applying. An applicant must state in the application materials that he or she agrees to submit to a pre-appointment IRS tax compliance check and an FBI criminal background investigation in accordance with Treasury Directive 21-03.</P>
                <SIG>
                    <NAME>Rachel Miller,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06652 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AK-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[OMB Control No. 2900-0878]</DEPDOC>
                <SUBJECT>Agency Information Collection Activity: Edith Nourse Rogers STEM Scholarship Application</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans Benefits Administration, Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Veterans Benefits Administration, Department of Veterans Affairs (VA), is announcing an opportunity for public comment on the proposed collection of certain information by the agency. Under the Paperwork Reduction Act (PRA) of 1995, Federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each proposed revision of a currently approved collection, and allow 60 days for public comment in response to the notice. 
                    </P>
                </SUM>
                <DATES>
                    <PRTPAGE P="17335"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 5, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments must be submitted through 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">Program-Specific information:</E>
                         Kendra McCleave, 202-495-8241, 
                        <E T="03">kendra.mccleave@va.gov.</E>
                    </P>
                    <P>
                        <E T="03">VA PRA information:</E>
                         Dorothy Glasgow, 202-461-1084, 
                        <E T="03">VAPRA@va.gov</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Under the PRA of 1995, Federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. This request for comment is being made pursuant to Section 3506(c)(2)(A) of the PRA.</P>
                <P>With respect to the following collection of information, VBA invites comments on:  (1) whether the proposed collection of information is necessary for the proper performance of VBA's functions, including whether the information will have practical utility; (2) the accuracy of VBA's estimate of the burden of the proposed collection of information; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or the use of other forms of information technology.</P>
                <P>
                    <E T="03">Title:</E>
                     Edith Nourse Rogers STEM Scholarship Application, VA Form 22-10203.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2900-0878. 
                    <E T="03">https://www.reginfo.gov/public/do/PRASearch.</E>
                    (Once at this link, you can enter the OMB Control Number to find the historical versions of this Information Collection).
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Section 111 of Public Law 115-48, Section 3320 authorizes VA to administer the Edith Nourse Rogers STEM Scholarship Program. Under the program, VA provides up to 9 months or $30,000 of Post-9/11 GI Bill benefits to certain eligible individuals selected by the Secretary of VA. To apply for and receive the scholarship, an individual must complete the application, VA Form 22-10203. VA continues to require approval of this information collection so students can continue to apply, and for VA to continue to assess how to prioritize the awarding of the Scholarship, based on the information collected on the form. This collection renewal resulted in a decrease in burden hours due to a significant decrease in the initial number of scholarship applicants that submitted an application for the program during the periods from 2022 and 2023.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or Households.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     2,788 hours.
                </P>
                <P>
                    <E T="03">Estimated Average Burden Time per Respondent:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Once.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     11,150.
                </P>
                <EXTRACT>
                    <FP>
                        (Authority: 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        )
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Dorothy Glasgow,</NAME>
                    <TITLE>Acting, VA PRA Clearance Officer, Office of Information Technology/Data Governance Analytics, Department of Veterans Affairs. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06589 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Veterans Rural Health Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent for reestablishment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are giving notice that the Secretary of Veterans Affairs intends to reestablish the Department of Veterans Affairs Veterans Rural Health Advisory Committee for a 2-year period. The Secretary has determined that the Committee is necessary and in the public interest.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jeffrey Moragne, Committee Management Office, Department of Veterans Affairs, Advisory Committee Management Office (00AC), 811 Vermont Avenue, 4th Floor, NW, Washington, DC 20420; telephone (202) 714-1578; or email at 
                        <E T="03">Jeffrey.Moragne@va.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to the Federal Advisory Committee ACT, notice is hereby given that the Secretary of Veterans Affairs (VA) intends to reestablish the Veterans Rural Health Advisory Committee (Committee or VRHAC) for two (2) years from the filing date of the charter's reestablishment. The purpose of the Committee is to advise the Secretary of VA on rural health care issues affecting Veterans. The VHRAC examines programs and policies that impact the delivery of VA rural health care to Veterans and discusses ways to improve and enhance VA access to rural health care services for Veterans.</P>
                <P>In addition, pursuant to 41 CFR 102-3.65, the Department of Veterans Affairs provides this written notice determination stating that the Committee is in the public interest and found to be in accordance with the Federal Advisory Community Act (FACA), the 2025 FACA Final Rule, and current to the U.S. General Services Administration, Committee Management Secretariat guidance. The following factors below provide an overview of the Committee's operations and public interest intent.</P>
                <P>Annual Budget—The overall operating costs for the Committee is $184,169. All members receive travel expenses and a per diem allowance in accordance with the Federal Travel Regulation for any travel made in connection with their duties as members of the Committee. The expected costs are broken into:</P>
                <P>(i) Federal personnel (based on full-time equivalent (FTE) usage basis) is .80 with other Federal internal costs being $135,369.</P>
                <P>(ii) Proposed payments to Non-Federal Members is $3,218. Payments to Federal Members are $7,081. The Committee is composed of not more than 12 appointed members and up to 3 ex-officio members.</P>
                <P>(iii) Reimbursable costs equate to travel reimbursement for Non-Federal Members is $11,230, for Federal Members is $3,671 and for Federal Staff is $23,600.</P>
                <P>This Committee does not have any dollar value of grants expected for the fiscal year.</P>
                <P>Membership Selection—The Committee's membership includes academic experts in rural health care delivery, state and federal government professionals who focus on rural health issues, Department of Veterans Affairs officials at the state level, and selected Veterans service organization leaders. VHRAC members range from patient care advocates to medical policy strategists. Additionally, the Committee works with the Department's Advisory Committee Management Office, the Committee Chair, and the Office of Rural Health (ORD) leadership to ensure the committee is balanced, to the extent possible, diversity ethnically and geographical background representation.</P>
                <P>Existing Federal Advisory Committees—The following list are the 27 VA advisory committees includes 18 that are statute (with an asterisk *) and 9 non-statutory committees.</P>
                <FP SOURCE="FP-2">(1) VA National Academic Affiliations Council</FP>
                <FP SOURCE="FP-2">* (2) Advisory Committee on Cemeteries and Memorials</FP>
                <FP SOURCE="FP-2">(3) Cooperative Studies Scientific Evaluation Committee</FP>
                <FP SOURCE="FP-2">
                    * (4) Advisory Committee on Disability Compensation
                    <PRTPAGE P="17336"/>
                </FP>
                <FP SOURCE="FP-2">* (5) Veterans' Advisory Committee on Education</FP>
                <FP SOURCE="FP-2">* (6) Veterans' Advisory Committee on Environmental Hazards (Administratively Inactive)</FP>
                <FP SOURCE="FP-2">* (7) Advisory Committee on Former Prisoners of War</FP>
                <FP SOURCE="FP-2">* (8) Geriatrics and Gerontology Advisory Committee</FP>
                <FP SOURCE="FP-2">* (9) Research Advisory Committee on Gulf War Veterans' Illnesses</FP>
                <FP SOURCE="FP-2">(10) Health Systems Research Service Merit Review Board</FP>
                <FP SOURCE="FP-2">* (11) Advisory Committee on Homeless Veterans</FP>
                <FP SOURCE="FP-2">(12) Joint Biomedical Laboratory Research and Development and Clinical Science Research and Development Services Scientific Merit Review Board</FP>
                <FP SOURCE="FP-2">* (13) Advisory Committee on Minority Veterans</FP>
                <FP SOURCE="FP-2">(14) National Research Advisory Council</FP>
                <FP SOURCE="FP-2">* (15) Advisory Committee on U.S. Outlying Areas and Freely Associated States</FP>
                <FP SOURCE="FP-2">* (16) Advisory Committee on Prosthetics and Special Disabilities Programs</FP>
                <FP SOURCE="FP-2">* (17) Advisory Committee on the Readjustment of Veterans</FP>
                <FP SOURCE="FP-2">* (18) Veterans' Advisory Committee on Rehabilitation</FP>
                <FP SOURCE="FP-2">(19) Rehabilitation Research and Development Service Scientific Merit Review Board</FP>
                <FP SOURCE="FP-2">(20) Veterans' Rural Health Advisory Committee</FP>
                <FP SOURCE="FP-2">* (21) Special Medical Advisory Group</FP>
                <FP SOURCE="FP-2">* (22) Advisory Committee on Structural Safety of Department of Veterans Affairs Facilities</FP>
                <FP SOURCE="FP-2">* (23) Advisory Committee on Tribal and Indian Affairs</FP>
                <FP SOURCE="FP-2">(24) Veterans' Family, Caregiver, and Survivor Advisory Committee</FP>
                <FP SOURCE="FP-2">* (25) Veterans and Community Oversight and Engagement Board</FP>
                <FP SOURCE="FP-2">(26) Department of Veterans Affairs Voluntary Service National Advisory Committee</FP>
                <FP SOURCE="FP-2">* (27) Advisory Committee on Women Veterans</FP>
                <P>Justification—VRHAC continues to provide valuable external rural health stakeholder perspective regarding rural health care and the challenges of accessing and delivering services in rural and highly rural areas. Stakeholder representation of Federal, state, regional, and local organizations is good; though proposed solutions to overcoming challenges specific to rural Veterans are often limited by implementation feasibility in the VA and the Veterans Health Administration.</P>
                <P>Summary of Previous Committee Accomplishments—The Committee's standard operations entail conducting one local meeting in Washington, DC to receive updates from VA Senior Leaders, and one site visit to a VA facility with a high concentration of rural Veterans. Its meetings focus on evaluating the programs and initiatives of VHA's ORD and its VHA program office partners; and on recommending ways to improve. The Committee evaluates current VA rural health program activities and identifies existing barriers to rural health services. It recommends strategies to improve those services for Veterans to the Secretary of Veterans Affairs.</P>
                <P>Why Committee is Essential—VRHAC provides advice and recommendations to the Secretary of Veterans Affairs on health care issues that affect Veterans residing in rural areas. The Committee meets at least twice annually to discuss programs and policies that impact the provision of VA health care to Veterans. This is obtained from its committee meetings and through the valuable external rural health stakeholder perspective regarding rural health care and the challenges of accessing and delivering services in rural and highly rural areas.</P>
                <P>In conclusion, this Notice of Reestablishment states that this Committee is in the public interest, essential to the conduct of agency business and that the information provided is not available through any other advisory committee or source within the Federal Government.</P>
                <SIG>
                    <DATED>Dated: April 2, 2026.</DATED>
                    <NAME>LaTonya L. Small,</NAME>
                    <TITLE>Federal Advisory Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-06610 Filed 4-3-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="17337"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P"> Department of Health and Human Services</AGENCY>
            <SUBAGY> Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <HRULE/>
            <CFR>42 CFR Part 418</CFR>
            <TITLE>Medicare Program; FY 2027 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Program Requirements; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="17338"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                    <CFR>42 CFR Part 418</CFR>
                    <DEPDOC>[CMS-1851-P]</DEPDOC>
                    <RIN>RIN 0938-AV78</RIN>
                    <SUBJECT>Medicare Program; FY 2027 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Program Requirements</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This proposed rule would update the hospice wage index, payment rates, and aggregate cap amount for Fiscal Year (FY) 2027. This proposed rule also includes an analysis of Medicare non-hospice spending, including details regarding a hospice service and spending variation index (SSVI), and proposes to require that hospices provide the hospice election statement addendum to all Medicare beneficiaries at the time of hospice election. Additionally, this rule proposes conforming regulation text changes to discharge from hospice care regulations; regulation text changes to the face-to-face encounter regulations; and includes requests for information on community palliative care services; the construction of a hospice specific wage index; and the overlap between hospice and medical aid in dying (MAID). Finally, this rule proposes changes to the Hospice Quality Reporting Program.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>To be assured consideration, comments must be received at one of the addresses provided below by June 1, 2026.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>In commenting, refer to file code CMS-1851-P.</P>
                        <P>
                            Comments, including mass comment submissions, must be submitted in one of the following three ways (choose 
                            <E T="03">only one</E>
                             of the ways listed):
                        </P>
                        <P>
                            1. 
                            <E T="03">Electronically.</E>
                             You may submit electronic comments on this regulation to 
                            <E T="03">https://www.regulations.gov/docket/CMS-2026-1156.</E>
                             Follow the “Submit a comment” instructions.
                        </P>
                        <P>
                            2. 
                            <E T="03">By regular mail.</E>
                             You may mail written comments to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1851-P, P.O. Box 8010, Baltimore, MD 21244-1850.
                        </P>
                        <P>Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>
                        <P>
                            3. 
                            <E T="03">By express or overnight mail.</E>
                             You may send written comments to the following address ONLY: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1851-P, Mail Stop C4-26-05, 7500 Security Boulevard, Baltimore, MD 21244-1850.
                        </P>
                        <P>
                            For information on viewing public comments, see the beginning of the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <P>
                            For general questions about hospice payment policy, send your inquiry via email to: 
                            <E T="03">hospicepolicy@cms.hhs.gov.</E>
                        </P>
                        <P>For questions regarding the CAHPS® Hospice Survey, contact Lauren Fuentes at (410) 786-2290.</P>
                        <P>For questions regarding the hospice quality reporting program, contact Jermama Keys at (410) 786-7778.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <P>
                        <E T="03">Inspection of Public Comments:</E>
                         All comments received before the close of the comment period are available for viewing by the public, including any personally identifiable or confidential business information that is included in a comment. We post all comments received before the close of the comment period on the following website as soon as possible after they have been received: 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the search instructions on that website to view public comments. CMS will not post on 
                        <E T="03">Regulations.gov</E>
                         public comments that make threats to individuals or institutions or suggest that the individual will take actions to harm the individual. CMS continues to encourage individuals not to submit duplicative comments. We will post acceptable comments from multiple unique commenters even if the content is identical or nearly identical to other comments.
                    </P>
                    <P>
                        <E T="03">Plain Language Summary:</E>
                         In accordance with 5 U.S.C. 553(b)(4), a plain language summary of this proposed rule may be found at 
                        <E T="03">https://www.regulations.gov/.</E>
                    </P>
                    <HD SOURCE="HD1">I. Executive Summary</HD>
                    <HD SOURCE="HD2">A. Purpose</HD>
                    <P>This proposed rule would update the hospice wage index, payment rates, and cap amount for FY 2027 as required under section 1814(i) of the Social Security Act (the Act). This proposed rule also includes an analysis of Medicare non-hospice spending under a hospice election, including details regarding a hospice spending variation index (SSVI). The SSVI includes a scoring system that monitors nine claims-based metrics in order to comprehensively assess hospice services and yield a provider ranking that can be utilized by beneficiaries to make more informed health decisions and support program integrity efforts. This rule also proposes to require that hospices provide the hospice election statement addendum to all Medicare beneficiaries at the time of hospice election. Additionally, this proposed rule proposes conforming regulation text changes to allow a physician designee or physician member of the interdisciplinary group (IDG), in addition to the hospice medical director, to discharge a patient from hospice care. This proposed rule also proposes conforming regulation text changes to the hospice telehealth face-to-face policy for the sole purpose of hospice recertification codified at § 418.22(a)(4)(ii) to align with the end date and new requirement to include modifiers or codes for such encounters as set forth in statute at section 1814(a)(7)(D)(i)(II) of the Act, as well as a subclause that prohibits the use of telehealth to conduct the face-to-face encounter in specific situations related to moratoriums (section 1866(j)(7) of the Act), enhanced oversight (section 1866(j)(3) of the Act), or enrollment status (section 1866(j) of the Act). This proposed rule also includes requests for information (RFI) on enhancing community palliative care services under current Medicare benefits, the construction of a hospice specific wage index using Bureau of Labor Statistics (BLS) data, and the overlap between hospice and medical aid in dying (MAID). Finally, this rule proposes adding an icon to the Medicare.gov Compare Tool as part of the Hospice Quality Reporting Program (HQRP), in addition to other updates to the HQRP.</P>
                    <HD SOURCE="HD2">B. Summary of the Major Provisions</HD>
                    <P>Section III.A.1. of this proposed rule includes proposed updates to the hospice wage index and makes the application of the updated wage data budget neutral for all four levels of hospice care.</P>
                    <P>Section III.A.2. of this proposed rule includes the proposed FY 2027 hospice payment update percentage.</P>
                    <P>Section III.A.3. of this proposed rule includes the proposed FY 2027 hospice payment rates.</P>
                    <P>Section III.A.4. of this proposed rule includes the proposed update to the hospice cap amount for FY 2027 by the hospice payment update percentage.</P>
                    <P>
                        Section III.B.1. of this proposed rule includes analysis of Medicare non-
                        <PRTPAGE P="17339"/>
                        hospice spending under a hospice election.
                    </P>
                    <P>Section III.B.2. of this proposed rule includes details regarding a hospice SSVI.</P>
                    <P>Section III.C. of this proposed rule proposes to make the hospice election statement addendum mandatory for all hospice elections.</P>
                    <P>Section III.D.1. of this proposed rule proposes a clarifying regulation text change at § 418.26(b) that aligns the Conditions of Participation (CoPs) and payment regulations regarding who may discharge a patient from hospice care.</P>
                    <P>Section III.D.2. of this proposed rule proposes technical regulation text changes at § 418.22(a)(4)(ii) to extend the end date of the telehealth allowance for the face-to-face encounter until December 31, 2027, as set forth at section 1814(a)(7)(D)(i)(II) of the Act, and to include a new requirement to include modifiers or codes for such encounters, and prohibit the use of telehealth to conduct the face-to-face encounter in specific situations related to moratoriums (section 1866(j)(7) of the Act), enhanced oversight (section 1866(j)(3) of the Act), or enrollment status (section 1866(j) of the Act).</P>
                    <P>Section III. E.1. of this proposed rule includes a Request for Information (RFI) on ways to enhance the provision of community palliative care outside of hospice care.</P>
                    <P>Section III. E.2. of this proposed rule includes an RFI regarding the construction of a hospice specific wage index.</P>
                    <P>Section III. E.3. of this proposed rule includes an RFI on Medical Aid in Dying.</P>
                    <P>Section III.F. of this proposed rule proposes to provide updates to the HQRP to include public reporting timeframes, future measures and a proposal to add a data submission icon to the Care Compare tool.</P>
                    <HD SOURCE="HD2">C. Summary of Impacts</HD>
                    <P>The overall economic impact of this proposed rule is estimated to be $785 million in increased payments to hospices in FY 2027.</P>
                    <HD SOURCE="HD1">II. Background</HD>
                    <HD SOURCE="HD2">A. Hospice Care</HD>
                    <P>Hospice care is a comprehensive, holistic approach to treatment that recognizes the impending death of a terminally ill individual and warrants a change in the focus from curative care to palliative care for relief of pain and for symptom management. Medicare regulations define “palliative care” as patient and family-centered care that optimizes quality of life by anticipating, preventing, and treating suffering. Palliative care throughout the continuum of illness involves addressing physical, intellectual, emotional, social, and spiritual needs and to facilitate patient autonomy, access to information, and choice (42 CFR 418.3). Palliative care is at the core of hospice philosophy and care practices and is a critical component of the Medicare hospice benefit.</P>
                    <P>The goal of hospice care is to help terminally ill individuals continue life with minimal disruption to normal activities while remaining primarily in the home environment. A hospice uses an interdisciplinary approach to deliver medical, nursing, social, psychological, emotional, and spiritual services through a collaboration of professionals and other caregivers, with the goal of making the beneficiary as physically and emotionally comfortable as possible. Hospice is compassionate beneficiary- and family/caregiver-centered care for those who are terminally ill.</P>
                    <P>As referenced in our regulations at § 418.22(c)(1), to be certified for Medicare hospice services, the patient's attending physician (if any) and the hospice medical director, physician designee, or physician member of the hospice interdisciplinary group must certify that the individual is “terminally ill,” as defined in section 1861(dd)(3)(A) of the Act and our regulations at § 418.3; that is, the individual has a medical prognosis that the individual's life expectancy is 6 months or less if the illness runs its normal course (§ 418.22(b)(1)). The regulations at § 418.22(b)(2) require that clinical information and other documentation that support the medical prognosis accompany the certification and be filed in the medical record with the written certification. The regulations at § 418.22(b)(3) require that the certification and recertification forms, or an addendum to the certification and recertification forms, include a brief narrative explanation of the clinical findings that supports a life expectancy of 6 months or less.</P>
                    <P>Under the Medicare hospice benefit, the election of hospice care is a patient choice, and once a terminally ill patient elects to receive hospice care, a hospice interdisciplinary group is essential in the seamless provision of primarily home-based services. The hospice interdisciplinary group works with the beneficiary, family, and caregivers to develop a coordinated, comprehensive care plan; reduce unnecessary diagnostics or ineffective therapies; and maintain ongoing communication with individuals and their families about changes in their condition. The beneficiary's care plan will shift over time to meet the changing needs of the individual, family, and caregiver(s) as the individual approaches the end of life.</P>
                    <P>If, in the judgment of the hospice interdisciplinary group (as specified at § 418.56(a)(1)), which includes the hospice physician, the patient's symptoms cannot be effectively managed at home, then the patient is eligible for general inpatient care (GIP), a more medically intense level of care. GIP must be provided in a Medicare-certified hospice freestanding facility, skilled nursing facility, or hospital. GIP is provided to ensure that any new or worsening symptoms are intensively addressed so that the beneficiary can return home for hospice care (routine home care) (RHC). Limited, short-term, intermittent, inpatient respite care (IRC) is also available because of the absence or need for relief of the family or other caregivers. Additionally, an individual can receive continuous home care (CHC) during a period of crisis in which an individual requires continuous care to achieve palliation or management of acute medical symptoms so that the individual can remain at home. CHC may be covered for as much as 24 hours a day, and these periods must be predominantly nursing care, in accordance with the regulations at § 418.204. A minimum of 8 hours of nursing care or nursing and aide care must be furnished on a particular day to qualify for the CHC rate (§ 418.302(e)(4)).</P>
                    <P>
                        Hospices covered by this rule must comply with applicable civil rights laws, including section 504 of the Rehabilitation Act of 1973 (Pub. L. 93-112, September 26, 1973), the Americans with Disabilities Act (Pub. L. 101-336, July 26, 1990), and section 1557 of the Patient Protection and Affordable Care Act (Pub. L. 111-148, March 23, 2010), which prohibit covered entities from discriminating against individuals based on disability. This includes requiring covered entities to take appropriate steps to ensure that communication with applicants, participants, members of the public, and companions with disabilities are as effective as communications with others. Covered entities must also provide appropriate auxiliary aids and services when necessary to afford qualified individuals with disabilities, including applicants, participants, beneficiaries, companions, and members of the public, an equal opportunity to participate in, and enjoy 
                        <PRTPAGE P="17340"/>
                        the benefits of, a service, program, or activity of a covered entity.
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Hospices receiving Medicare Part A funds or other Federal financial assistance from the Department are also subject to additional Federal civil rights laws, including the Age Discrimination Act, and are subject to conscience and religious freedom laws where applicable. CMS must ensure that pursuant to 42 U.S.C. 1396a(w) facilities provide written information to residents of their rights to have and make advance directives and that care facilities must respect the conscience rights of providers and healthcare workers in caring for patients with respect to advance directives and under 42 U.S.C. 1396a(w)(3).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Services Covered by the Medicare Hospice Benefit</HD>
                    <P>Coverage under the Medicare hospice benefit requires that hospice services must be reasonable and necessary for the palliation and management of the terminal illness and related conditions. Section 1861(dd)(1) of the Act establishes the services that are to be rendered by a Medicare-certified hospice program. These covered services include: nursing care; physical therapy; occupational therapy; speech-language pathology services; medical social services; home health aide services (called hospice aide services); physician's services; homemaker services; medical supplies (including drugs and biologicals); medical appliances; counseling services (including dietary counseling); short-term inpatient care in a hospital, nursing facility, or hospice inpatient facility (including both respite care and procedures necessary for pain control and acute and chronic symptom management); continuous home care during periods of crisis, and only as necessary to maintain the terminally ill individual at home; and any other item or service which is specified in the plan of care and for which payment may otherwise be made under Medicare, in accordance with Title XVIII of the Act.</P>
                    <P>Section 1814(a)(7)(B) of the Act requires that a written plan for providing hospice care to a beneficiary who is a hospice patient be established before such care is provided by, or under arrangements made by, the hospice program; and that the written plan be periodically reviewed by the beneficiary's attending physician (if any), the hospice medical director, and an interdisciplinary group (section 1861(dd)(2)(B) of the Act). The services offered under the Medicare hospice benefit must be available to beneficiaries as needed, 24 hours a day, 7 days a week (section 1861(dd)(2)(A)(i) of the Act).</P>
                    <P>Upon the implementation of the hospice benefit, Congress also expected hospices to continue to use volunteer services, although Medicare does not pay for these volunteer services (section 1861(dd)(2)(E) of the Act). As stated in the Health Care Financing Administration's (now Centers for Medicare &amp; Medicaid Services (CMS)) proposed rule: Medicare Program; Hospice Care (48 FR 38149), the hospice must have an interdisciplinary group composed of paid hospice employees as well as hospice volunteers, and that “the hospice benefit with the resulting Medicare reimbursement is not intended to diminish the voluntary spirit of hospices.” This expectation supports the hospice philosophy of community based, holistic, comprehensive, and compassionate end of life care.</P>
                    <HD SOURCE="HD2">C. Medicare Payment for Hospice Care</HD>
                    <P>Sections 1812(d), 1813(a)(4), 1814(a)(7), 1814(i), and 1861(dd) of the Act, and the regulations in 42 CFR part 418, establish eligibility requirements, payment standards and procedures; define covered services; and delineate the conditions a hospice must meet to be approved for participation in the Medicare program. Part 418, subpart G, provides for a per diem payment based on one of four prospectively determined rate categories of hospice care (RHC, CHC, IRC, and GIP), based on each day a qualified Medicare beneficiary is under hospice care (once the individual has elected the benefit). This per diem payment is meant to cover all hospice services and items needed to manage the beneficiary's care, as required by section 1861(dd)(1) of the Act.</P>
                    <P>While payment made to hospices is to cover all items, services, and drugs for the palliation and management of the terminal illness and related conditions, Federal funds cannot be used for prohibited activities, even in the context of a per diem payment. For example, hospices are prohibited from playing a role in medical aid in dying (MAID) where such practices have been legalized in certain States. The Assisted Suicide Funding Restriction Act of 1997 (Pub. L. 105-12, April 30, 1997) prohibits the use of Federal funds to provide or pay for any health care item or service or health benefit coverage for the purpose of causing, or assisting to cause, the death of any individual including “mercy killing, euthanasia, or assisted suicide.” However, the prohibition does not pertain to the provision of an item or service for the purpose of alleviating pain or discomfort, even if such use may increase the risk of death, so long as the item or service is not furnished for the specific purpose of causing or accelerating death.</P>
                    <P>
                        The Medicare hospice benefit has been revised and refined since its implementation after various Acts of Congress and Medicare rules. For a historical list of changes and regulatory actions, we refer readers to the background section of previous Hospice Wage Index and Payment Rate Update rules.
                        <SU>2</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Hospice Regulations and Notices. 
                            <E T="03">https://www.cms.gov/medicare/payment/fee-for-service-providers/hospice/hospice-regulations-and-notices.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Provisions of the Proposed Rule</HD>
                    <HD SOURCE="HD2">A. Proposed FY 2027 Hospice Wage Index and Rate Update</HD>
                    <HD SOURCE="HD3">1. Proposed FY 2027 Hospice Wage Index</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>The hospice wage index is used to adjust payment rates for hospices under the Medicare program to reflect local differences in area wage levels, based on the location where services are furnished. The hospice wage index utilizes the wage adjustment factors used by the Secretary for purposes of section 1886(d)(3)(E) of the Act for hospital wage adjustments. Our regulations at § 418.306(c) require each labor market to be established using the most current hospital wage data available, including any changes made by the Office of Management and Budget (OMB) to Metropolitan Statistical Area (MSA) definitions.</P>
                    <P>
                        In general, OMB issues major revisions to statistical areas every 10 years based on the results of the decennial census. On July 21, 2023, OMB issued Bulletin No. 23-01, which updated and superseded OMB Bulletin No. 20-01, issued on March 6, 2020. OMB Bulletin No. 23-01 established revised delineations for the MSAs, Micropolitan Statistical Areas, Combined Statistical Areas (CSAs), and Metropolitan Divisions, collectively referred to as Core Based Statistical Areas (CBSAs). According to OMB, the delineations reflect the 2020 Standards for Delineating Core Based Statistical Areas (the “2020 Standards”), which appeared in the 
                        <E T="04">Federal Register</E>
                         (86 FR 37770 through 37778) on July 16, 2021, and application of those standards to Census Bureau population and journey-to-work data (for example, 2020 Decennial Census, American Community Survey, and Census Population Estimates Program data). A copy of OMB Bulletin No. 23-01 is available online at 
                        <E T="03">https://www.bls.gov/bls/omb-bulletin-23-01-revised-delineations-of-metropolitan-statistical-areas.pdf.</E>
                        <PRTPAGE P="17341"/>
                    </P>
                    <P>The July 21, 2023 OMB Bulletin No. 23-01 contained a number of significant changes. For example, it designated new CBSAs, split some existing CBSAs, and changed some urban counties to rural and some rural counties to urban. We believe it is important for the hospice wage index to use the latest OMB delineations available to maintain the most accurate and up-to-date payment system, reflecting the reality of population shifts and labor market conditions. We further believe that using the most current OMB delineations increases the integrity of the hospice wage index by creating a more accurate representation of geographic variation in wage levels. Therefore, in the FY 2025 Hospice final rule (89 FR 64208 through 64224), we finalized the implementation of new labor market areas based on the revisions in OMB Bulletin No. 23-01 beginning in FY 2025.</P>
                    <HD SOURCE="HD3">b. Hospice Floor and 5 Percent Cap Policies</HD>
                    <P>As described in the August 8, 1997 Hospice Wage Index final rule (62 FR 42860), the pre-floor and pre-reclassified hospital wage index is used as the raw wage index for the hospice benefit. These raw wage index values are subject to application of the hospice floor to compute the hospice wage index used to determine payments to hospices. The pre-floor, pre-reclassified hospital wage index values below 0.8000 are adjusted by a 15 percent increase subject to a maximum wage index value of 0.8000. For example, if CBSA “A” has a pre-floor, pre-reclassified hospital wage index value of 0.3994, we would multiply 0.3994 by 1.15, which equals 0.4593. Since 0.4593 is not greater than 0.8000, the CBSA “A's” hospice wage index would be 0.4593. In another example, if CBSA “B” has a pre-floor, pre-reclassified hospital wage index value of 0.7440, we would multiply 0.7440 by 1.15, which equals 0.8556. Because 0.8556 is greater than 0.8000, CBSA “B's” hospice wage index would be 0.8000.</P>
                    <P>In the FY 2023 Hospice Wage Index and Rate Update final rule (87 FR 45673), we finalized for FY 2023 and subsequent years the application of a permanent 5 percent cap on any decrease to a geographic area's wage index from its wage index in the prior year, regardless of the circumstances causing the decline, so that a geographic area's wage index would not be less than 95 percent of its wage index calculated in the prior FY. When calculating the 5 percent cap on wage index decreases, we start with the current FY's pre-floor, pre-reclassification hospital wage index value for a CBSA or statewide rural area, and if that wage index value is below 0.8000, we apply the hospice floor as discussed previously in this section of the proposed rule. Next, we compare the current FY's wage index value after the application of the hospice floor to the final wage index value from the previous FY. If the current FY's wage index value is less than 95 percent of the previous year's wage index value, the 5 percent cap on wage index decreases would be applied and the final wage index value would be set equal to 95 percent of the previous FY's wage index value. If the 5 percent cap is applied in one FY, then in the subsequent FY, that year's pre-floor, pre-reclassification hospital wage index would be used as the starting wage index value and adjusted by the hospice floor. The hospice floor adjusted wage index value would be compared to the previous FY's wage index which had the 5 percent cap applied. If the hospice floor adjusted wage index value for that FY is less than 95 percent of the capped wage index from the previous year, then the 5 percent cap would be applied again, and the final wage index value would be 95 percent of the capped wage index from the previous FY. Using the example previously stated, if CBSA “A” has a pre-floor, pre-reclassified hospital wage index value of 0.3994, we would multiply 0.3994 by 1.15, which equals 0.4593. If CBSA “A” had a wage index value of 0.6200 in the previous FY, then we would compare 0.4593 to the previous FY's wage index value. Since 0.4593 is less than 95 percent of 0.6200, then CBSA “A”'s hospice wage index would be 0.5890, which is equal to 95 percent of the previous FY's wage index value of 0.6200. In the next FY, the updated wage index value would be compared to the wage index value of 0.5890.</P>
                    <P>Previously, this 5 percent cap methodology was applied to all the counties that make up a CBSA or rural area. However, beginning in FY 2025, we finalized a policy that the 5 percent cap methodology also be applied to individual counties. In the FY 2025 Hospice Wage Index and Rate Update final rule (89 FR 64202), as a transition to the adoption of the revised delineations from OMB No. 23-01, we finalized a policy applying the permanent 5 percent cap on wage index decreases at the county level. Specifically, counties that were impacted by the revised designations beginning in FY 2025 would receive a 5 percent cap on any decrease in a geographic area's wage index value from the wage index value from the prior FY. Also, beginning in FY 2025, counties that have a different wage index value than the CBSA or rural area into which they are designated due to the application of the 5 percent cap (including redesignated counties that will receive the 5 percent cap and redesignated counties that move into a CBSA or rural area where all other constituent counties receive the 5 percent cap) would use a wage index transition code. These special codes are five digits in length and begin with “50”. The 50XXX wage index transition codes are used only in specific counties. Counties located in CBSAs and rural areas that do not correspond to a different transition wage index value will still use the CBSA number.</P>
                    <P>
                        Finally, we finalized a policy to apply the 5 percent cap to a county that corresponds to a different wage index value than the wage index value assigned to the CBSA or rural area in which they are designated due to a delineation change until the county's new wage index is more than 95 percent of the wage index from the previous FY. To capture the correct wage index value, the county will continue to use the assigned 50XXX transition code until the county's wage index value calculated for that FY using the new OMB delineations is not less than 95 percent of the county's capped wage index from the previous FY. Once the county's wage index value calculated using the new OMB delineation is higher than 95 percent of their previous FY's wage index, the county will no longer use their assigned transition code. Instead, these counties will use the CBSA or rural county code of the area they were redesignated into based on OMB Bulletin No. 23-01. More information regarding these special codes can be found in the FY 2025 Hospice Wage Index and Rate Update final rule (89 FR 64220 through 64224). Additionally, the list of counties that must use a 50XXX transition code for a given FY can be found as a separate tab in the hospice wage index file for that FY available on the CMS website at 
                        <E T="03">https://www.cms.gov/medicare/payment/fee-for-service-providers/hospice/hospice-wage-index.</E>
                    </P>
                    <HD SOURCE="HD3">c. Proposed FY 2027 Hospice Wage Index</HD>
                    <P>
                        In the FY 2020 Hospice Wage Index and Rate Update final rule (84 FR 38484) we finalized a policy to use the current FY's hospital wage index data to calculate the hospice wage index values. For FY 2027, we are proposing that the hospice wage index would be based on the FY 2027 hospital pre-floor, pre-
                        <PRTPAGE P="17342"/>
                        reclassified wage index for hospital cost reporting periods beginning on or after October 1, 2022 and before October 1, 2023 (FY 2023 cost report data). We note that the FY 2027 hospice wage index would not consider any geographic reclassification of hospitals, including those in accordance with sections 1886(d)(8)(B) or 1886(d)(10) of the Act. The regulations that govern hospice payment do not provide a mechanism for allowing hospices to seek geographic reclassification or to utilize the rural floor provisions that exist for Inpatient Prospective Payment System (IPPS) hospitals. The reclassification provision found in section 1886(d)(10) of the Act is specific to hospitals. Section 4410(a) of the Balanced Budget Act (BBA) of 1997 (Pub. L. 105-33, August 5, 1997) provides that the area wage index applicable to any hospital located in an urban area of a State may not be less than the area wage index applicable to hospitals located in rural areas in that State. This rural floor provision is also specific to hospitals. Because the reclassification and the hospital rural floor policies apply to hospitals only, and not to hospices, we continue to believe the use of the pre-floor and pre-reclassified hospital wage index is the most appropriate adjustment to the labor portion of the hospice payment rates. This position is longstanding and consistent with other Medicare payment systems, for example, the skilled nursing facility prospective payment system (SNF PPS), the inpatient rehabilitation facility prospective payment system (IRF PPS), and the home health prospective payment system (HH PPS). However, the hospice wage index does include the hospice floor, which is applicable to all CBSAs, both rural and urban. The hospice floor adjusts pre-floor, pre-reclassified hospital wage index values below 0.8000 by a 15 percent increase subject to a maximum wage index value of 0.8000. We propose that the FY 2027 hospice wage index would continue to include the hospice floor as well as the 5 percent cap on wage index decreases.
                    </P>
                    <P>The appropriate FY 2027 wage index value would be applied to the labor portion of the hospice payment rate based on the geographic area in which the beneficiary resides when receiving RHC or CHC. The appropriate FY 2027 wage index value would be applied to the labor portion of the payment rate based on the geographic location of the facility for beneficiaries receiving GIP or IRC.</P>
                    <P>There exist some geographic areas where there are no hospitals, and thus, no hospital wage data on which to base the calculation of the hospice wage index. In the FY 2006 Hospice Wage Index and Rate Update final rule (70 FR 45135), we adopted the policy that, for urban labor markets without a hospital from which hospital wage index data could be derived, all the CBSAs within the State would be used to calculate a statewide urban average pre-floor, pre-reclassified hospital wage index value to use as a reasonable proxy for these areas. For FY 2027, the only CBSA without a hospital from which hospital wage data can be derived is 25980, Hinesville, Georgia. As such, we are proposing that the proposed FY 2027 hospice wage index for Hinesville, Georgia would be 0.8917.</P>
                    <P>In the FY 2008 Hospice Wage Index and Rate Update final rule (72 FR 50217 through 50218), we implemented a methodology to update the hospice wage index for rural areas without hospital wage data. In cases where there is a rural area without rural hospital wage data, we use the average pre-floor, pre-reclassified hospital wage index data from all contiguous CBSAs, to represent a reasonable proxy for the rural area. The term “contiguous” means sharing a border (72 FR 50217). In the FY 2025 Hospice Wage Index and Rate Update final rule (89 FR 64207), as part of our adoption of the revised OMB delineations, rural North Dakota became a rural area without a hospital from which hospital wage data can be derived. Therefore, to calculate the proposed FY 2027 wage index for rural area 99935, North Dakota, we use as a proxy the average pre-floor, pre-reclassified hospital wage data (updated by the hospice floor and 5 percent cap) from the contiguous CBSAs: CBSA 13900-Bismark, ND, CBSA 22020-Fargo, ND-MN, CBSA 24220-Grand Forks, ND-MN and CBSA 33500, Minot, ND, which would result in a proposed FY 2027 hospice wage index of 0.8299 for rural North Dakota. Additionally, in the FY 2026 Hospice Wage Index and Rate Update final rule (90 FR 37410), using our established methodology for rural areas with no hospitals, we finalized that hospices that provide services in the Northern Mariana Islands and American Samoa should use CBSA 99965 (Guam) and should receive the wage index assigned to CBSA 99965 (Guam) of 0.9611.</P>
                    <P>Previously, the only rural area without a hospital from which hospital wage data could be derived was in Puerto Rico. However, for rural Puerto Rico, we did not apply this methodology due to the distinct economic circumstances that exist there (for example, due to the close proximity of almost all of Puerto Rico's various urban areas to non-urban areas, this methodology would produce a wage index for rural Puerto Rico that is higher than that of half of its urban areas). Instead, we used the most recent wage index previously available for that area, which was 0.4047, subsequently adjusted by the hospice floor for an adjusted wage index of 0.4654. For FY 2025, we noted as part of our adoption of the revised OMB delineations, there is now a hospital in rural Puerto Rico from which hospital wage data can be derived. Therefore, we finalized a wage index for rural Puerto Rico based on the hospital wage data for the area instead of the previously available pre-hospice floor wage index of 0.4047, which equaled an adjusted wage index value of 0.4654. The proposed FY 2027 pre-hospice floor unadjusted wage index for rural Puerto Rico is 0.2577 subsequently adjusted by the hospice floor to equal 0.2964. Because 0.2964 is more than a 5 percent decline in the FY 2026 wage index, the adjusted proposed FY 2027 wage index with the 5 percent cap applied would equal 0.95 multiplied by 0.4200 (that is, the FY 2026 wage index with 5 percent cap), which would result in a proposed FY 2027 wage index value of 0.3990.</P>
                    <P>
                        The proposed hospice wage index applicable for FY 2027 (October 1, 2026 through September 30, 2027) is available on the FY 2027 Hospice Wage Index proposed rule web page at 
                        <E T="03">https://www.cms.gov/medicare/payment/fee-for-service-providers/hospice/hospice-regulations-and-notices.</E>
                    </P>
                    <HD SOURCE="HD3">2. Proposed FY 2027 Hospice Payment Update Percentage</HD>
                    <P>
                        Section 4441(a) of the BBA of 1997, August 5, 1997) amended section 1814(i)(1)(C)(ii)(VI) of the Act to establish updates to hospice rates for FYs 1998 through 2002. Hospice rates were to be updated by a factor equal to the inpatient hospital market basket percentage increase set out under section 1886(b)(3)(B)(iii) of the Act, minus one percentage point. Payment rates for FYs since 2002 have been updated as required by section 1814(i)(1)(C)(ii)(VII) of the Act, which states that the update to the payment rates for subsequent FYs must be the inpatient hospital market basket percentage increase for that FY. In the FY 2022 IPPS/LTCH PPS final rule (86 FR 45194 through 45204), we finalized the rebased and revised IPPS market basket to reflect a 2018 base year. In the FY 2026 IPPS/LTCH PPS final rule (90 FR 36859 through 36866), we finalized the rebased and revised IPPS market basket to reflect a 2023 base year, to begin in FY 2026.
                        <PRTPAGE P="17343"/>
                    </P>
                    <P>
                        Section 3401(g) of the Affordable Care Act mandated that, starting with FY 2013 (and in subsequent FYs), the hospice payment update percentage be annually reduced by changes in economy-wide productivity as specified in section 1886(b)(3)(B)(xi)(II) of the Act. The Act defines the productivity adjustment to be equal to the 10-year moving average of changes in annual economy-wide private nonfarm business multifactor productivity as projected by the Secretary for the 10-year period ending with the applicable FY, year, cost reporting period, or other annual period (the “productivity adjustment”). The United States Department of Labor's Bureau of Labor Statistics (BLS) publishes the official measures of productivity for the United States economy. The productivity measure referenced in section 1886(b)(3)(B)(xi)(II) of the Act is published by BLS as private nonfarm business total factor productivity (TFP) (previously referred to as multifactor productivity).
                        <SU>3</SU>
                        <FTREF/>
                         We refer readers to 
                        <E T="03">https://www.bls.gov/</E>
                         productivity for the BLS historical published TFP data. A complete description of IHS Global Inc.'s (IGIs) TFP projection methodology is available on the CMS website at 
                        <E T="03">https://www.cms.gov/data-research/statistics-trends-and-reports/medicare-program-rates-statistics/market-basket-research-and-information.</E>
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">https://www.bls.gov/productivity/notices/2021/mfp-to-tfp-term-change.htm.</E>
                        </P>
                    </FTNT>
                    <P>Consistent with our historical practice, we estimate the market basket percentage increase, and the productivity adjustment based on IGI's forecast, using the most recent available data. The proposed hospice payment update percentage for FY 2027 is based on the most recent estimate of the inpatient hospital market basket (based on IGI's fourth quarter 2025 forecast). Due to the requirements at sections 1886(b)(3)(B)(xi)(II) and 1814(i)(1)(C)(v) of the Act, the proposed inpatient hospital market basket percentage increase for FY 2027 of 3.2 percent is required to be reduced by a productivity adjustment as mandated by section 3401(g) of the Affordable Care Act. The proposed productivity adjustment for FY 2027 is 0.8 percentage point (based on IGI's fourth quarter 2025 forecast). Therefore, the proposed hospice payment update percentage for FY 2027 is 2.4 percent. We are also proposing that if more recent data become available after the publication of the proposed rule and before the publication of the final rule (for example, a more recent estimate of the inpatient hospital market basket percentage increase or productivity adjustment), we would use such data, if appropriate, to determine the hospice payment update percentage in the FY 2027 final rule. We continue to believe it is appropriate to routinely update the hospice payment system so that it reflects the best available data regarding differences in patient resource use and costs among hospices as required by the statute.</P>
                    <P>In the FY 2022 Hospice Wage Index and Rate Update final rule (86 FR 42532), we rebased and revised the labor shares for RHC, CHC, GIP, and IRC using Medicare cost report data for freestanding hospices (CMS Form 1984-14, OMB Control Number 0938-0758) from 2018. The current labor portion of the payment rates are: RHC, 66.0 percent; CHC, 75.2 percent; GIP, 63.5 percent; and IRC, 61.0 percent. The non-labor portion is equal to 100 percent minus the labor portion for each level of care. The non-labor portion of the payment rates are as follows: RHC, 34.0 percent; CHC, 24.8 percent; GIP, 36.5 percent; and IRC, 39.0 percent.</P>
                    <HD SOURCE="HD3">3. Proposed FY 2027 Hospice Payment Rates</HD>
                    <P>There are four payment categories that are distinguished by the location and intensity of the hospice services provided. The base payments are adjusted for geographic differences in wages by multiplying the labor share, which varies by category, of each base rate by the applicable hospice wage index. A hospice is paid the RHC rate for each day the beneficiary is enrolled in hospice, unless the hospice provides CHC, IRC, or GIP. CHC is provided during a period of patient crisis to maintain the patient at home; IRC is short-term care to allow the usual caregiver to rest and be relieved from caregiving; and GIP care is intended to treat symptoms that cannot be managed in another setting.</P>
                    <P>As discussed in the FY 2016 Hospice Wage Index and Rate Update final rule (80 FR 47172), we implemented two different RHC payment rates, one RHC rate for the first 60 days and a second RHC rate for day 61 and subsequent days. In addition, in that final rule, we implemented a Service Intensity Add-On (SIA) payment for RHC when direct patient care is provided by a registered nurse (RN) or social worker during the last 7 days of the beneficiary's life. The SIA payment is equal to the CHC hourly rate multiplied by the hours of nursing or social work provided (up to 4 hours total) that occur on the day of service if certain criteria are met. To maintain budget neutrality, as required under section 1814(i)(6)(D)(ii) of the Act, the new RHC rates were adjusted by an SIA budget neutrality factor (SBNF). The SBNF is used to reduce the overall RHC rate to ensure that SIA payments are budget neutral. At the beginning of every FY, SIA utilization is compared to the prior year in order calculate a budget neutrality adjustment. For FY 2027, the proposed SIA budget neutrality factor is 0.9999 for RHC days 1-60 and 0.9999 for RHC days 61+.</P>
                    <P>In the FY 2017 Hospice Wage Index and Rate Update final rule (81 FR 52156), we initiated a policy of applying a wage index standardization factor to hospice payments to eliminate the aggregate effect of annual variations in hospital wage data. For FY 2027 hospice rate setting, we are continuing our longstanding policy of using the most recent data available. Specifically, we propose using FY 2025 claims data (as of January 15, 2026) for the FY 2027 payment rate updates. We note that the budget neutrality factors and payment rates would be updated with more complete FY 2025 claims data in the FY 2027 hospice final rule. The wage index standardization factor is calculated by simulating total payments using FY 2025 hospice utilization claims data with the FY 2026 wage index (pre-floor, pre-reclassified hospital wage index with the hospice floor and the 5 percent cap on wage index decreases) and FY 2026 payment rates and compare it to our simulation of total payments using FY 2025 utilization claims data, the FY 2027 hospice wage index (pre-floor, pre-reclassified hospital wage index with hospice floor, and the 5 percent cap on wage index decreases) and FY 2026 payment rates. By dividing payments for each level of care (RHC days 1 through 60, RHC days 61+, CHC, IRC, and GIP) using the FY 2026 wage index and FY 2026 payment rates for each level of care by the FY 2027 wage index and FY 2026 payment rates, we obtain a wage index standardization factor for each level of care. The proposed wage index standardization factors using FY 2025 claims data (as of January 15, 2026) for each level of care are shown in Tables 1 and 2.</P>
                    <P>The proposed FY 2027 RHC payment rates are shown in Table 1. The proposed FY 2027 payment rates for CHC, IRC, and GIP are shown in Table 2.</P>
                    <GPH SPAN="3" DEEP="141">
                        <PRTPAGE P="17344"/>
                        <GID>EP06AP26.000</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="138">
                        <GID>EP06AP26.001</GID>
                    </GPH>
                    <P>Sections 1814(i)(5)(A) through (C) of the Act require that hospices submit quality data on measures to be specified by the Secretary. In the FY 2012 Hospice Wage Index and Rate Update final rule (76 FR 47320 through 47324), we implemented a Hospice Quality Reporting Program (HQRP) as required by those sections. Hospices were required to begin collecting quality data in October 2012 and submit those quality data in 2013. Section 1814(i)(5)(A)(i) of the Act requires that for FY 2014 through FY 2023, the Secretary shall reduce the market basket percentage increase by 2 percentage points for any hospice that does not comply with the quality data submission requirements with respect to that FY. Section 1814(i)(5)(A)(i) of the Act was amended by section 407(b) of Division CC, Title IV of the Consolidated Appropriations Act (CAA), 2021 (Pub. L. 116-260) to change the payment reduction for failing to meet hospice quality reporting requirements from 2 to 4 percentage points. Depending on the amount of the annual update for a particular year, a reduction of 4 percentage points beginning in FY 2024 makes a negative payment update more likely than the previous 2 percent reduction. This could result in the annual market basket update being less than zero percent for a FY and may result in payment rates that are less than payment rates for the preceding FY. We applied this policy beginning with the FY 2024 Annual Payment Update (APU), which we based on CY 2022 quality data. Therefore, the proposed FY 2027 rates for hospices that do not submit the required quality data would be updated by -1.6 percent, which is the proposed FY 2027 hospice payment update percentage of 2.4 percent minus 4 percentage points. The proposed payment rates for hospices that do not submit the required quality data are shown in Tables 3 and 4.</P>
                    <GPH SPAN="3" DEEP="210">
                        <PRTPAGE P="17345"/>
                        <GID>EP06AP26.002</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="238">
                        <GID>EP06AP26.003</GID>
                    </GPH>
                    <HD SOURCE="HD3">4. Proposed Hospice Cap Amount for FY 2027</HD>
                    <P>
                        As discussed in the FY 2016 Hospice Wage Index and Rate Update final rule (80 FR 47183), we implemented changes mandated by the IMPACT Act of 2014 (Pub. L. 113-185, Oct. 6, 2014). Specifically, we stated that for accounting years that end after September 30, 2016, and before October 1, 2025, the hospice cap is updated by the hospice payment update percentage rather than using the Consumer Price Index for All Urban Consumers (CPI-U). Division CC, section 404 of the CAA, 2021 extended the accounting years impacted by the adjustment made to the hospice cap calculation until 2030. In the FY 2022 Hospice Wage Index and Rate Update final rule (86 FR 42539), we finalized conforming regulation text changes at § 418.309 to reflect the provisions of the CAA, 2021. Division P, section 312 of the CAA, 2022 (Pub. L. 117-103, March 15, 2022) amended section 1814(i)(2)(B) of the Act and extended the provision that mandates the hospice cap be updated by the hospice payment update percentage (the inpatient hospital market basket percentage increase reduced by the productivity adjustment) rather than the CPI-U for accounting years that end after September 30, 2016 and before October 1, 2031. Division FF, section 4162 of the CAA, 2023 (Pub. L. 117-328, December 29, 2022) amended section 1814(i)(2)(B) of the Act and extended the provision that currently mandates the hospice cap be updated by the hospice payment update percentage (the inpatient hospital market basket percentage increase reduced by the productivity adjustment) rather than the CPI-U for accounting years that end after September 30, 2016 and before October 1, 2032. Division G, section 308 of the Consolidated Appropriations Act, 2024 (CAA, 2024) (Pub. L. 118-42, March 9, 2024) extends this provision to October 1, 2033.Therefore, for accounting years that end after September 30, 2016, and before October 1, 2033, the hospice cap amount is updated by the hospice payment update percentage rather than the CPI-U. In the FY 2025 Hospice Wage Index and Rate 
                        <PRTPAGE P="17346"/>
                        Update final rule (89 FR 64202), as a result of the changes mandated by the CAA, 2024, we finalized conforming regulation text changes at § 418.309 to reflect the revisions at section 1814(i)(2)(B) of the Act.
                    </P>
                    <P>Division J, section 6218 of the Consolidated Appropriations Act, 2026 (CAA, 2026) (Pub. L. 119-75, February 3, 2026) amended section 1814(i)(2)(B) of the Act and extended the accounting years impacted by the adjustment made to the hospice cap calculation until 2035. Before the enactment of this provision, the hospice cap update was set to revert to the original methodology of updating the annual cap amount by the CPI-U beginning on October 1, 2033. Therefore, for accounting years that end after September 30, 2016, and before October 1, 2035, the hospice cap amount is updated by the hospice payment update percentage rather than the CPI-U. As a result of the changes mandated by the CAA, 2026, we are proposing conforming regulation text changes at § 418.309 to reflect the revisions at section 1814(i)(2)(B) of the Act.</P>
                    <P>The proposed hospice cap amount for the FY 2027 cap year would be $36,210.11 which is equal to the FY 2026 cap amount ($35,361.44) updated by the proposed FY 2027 hospice payment update of 2.4 percent. We are also proposing that if more recent data become available after the publication of the proposed rule and before the publication of the final rule (for example, a more recent estimate of the hospice payment update percentage), we would use such data, if appropriate, to determine the hospice cap amount in the FY 2027 hospice final rule.</P>
                    <HD SOURCE="HD2">B. Non-Hospice Spending During a Hospice Election</HD>
                    <HD SOURCE="HD3">1. Medicare Non-Hospice Spending</HD>
                    <HD SOURCE="HD3">a. Background</HD>
                    <P>The Medicare hospice per diem payment amounts were developed to cover all services needed for the palliation and management of the terminal illness and related conditions, as described in section 1861(dd)(1) of the Act. Hospice services provided under a written plan of care (POC) should reflect patient and family goals and interventions based on the problems identified in the initial, comprehensive, and updated comprehensive assessments as outlined in the hospice CoPs at § 418.56. As referenced in our regulations at § 418.64, a hospice must routinely provide all core services directly by hospice employees and they must be provided in a manner consistent with acceptable standards of practice. Under the current payment system, hospices are paid for each day that a beneficiary is enrolled in hospice care, regardless of whether services are rendered on any given day.</P>
                    <P>Additionally, when a beneficiary elects the Medicare hospice benefit, he or she waives the right to Medicare payment for services related to the treatment of the terminal illness and related conditions, except for services provided by the designated hospice and the attending physician. The comprehensive nature of the services covered under the Medicare hospice benefit is structured so that hospice beneficiaries would not have to routinely seek items, services, and medications beyond those provided by hospice. We believe that it would be unusual and exceptional to see services provided outside of hospice for those individuals who are approaching the end of life, and we have reiterated since 1983 that “virtually all” care needed by the terminally ill individual would be provided by the hospice (48 FR 56010, 84 FR 38509, 85 FR 47091, 86 FR 19713, 88 FR 20032, 89 FR 64202). Hospices are required to provide the individual (or representative) with information indicating that services unrelated to the terminal illness and related conditions are exceptional and unusual and the hospice should be providing virtually all care needed by the individual who has elected hospice, as codified in regulations at § 418.24(b)(3).</P>
                    <HD SOURCE="HD3">b. Medicare Non-Hospice Spending Since Implementation of the Hospice Election Statement Addendum</HD>
                    <P>Since the implementation of the hospice election statement addendum requirement in FY 2020 (84 FR 38484), which must be provided upon request, Medicare non-hospice spending for beneficiaries who have elected the hospice benefit has shown substantial and consistent growth. Specifically, Medicare paid over $2.8 billion in non-hospice spending during a hospice election in FY 2024 for items and services under Parts A, B, and D (see Figure 1 and B).</P>
                    <HD SOURCE="HD1">Figure 1: Medicare Payments for Non-Hospice Medicare Part A and Part B Items and Services During Hospice Elections, FYs 2020-2024</HD>
                    <GPH SPAN="3" DEEP="336">
                        <PRTPAGE P="17347"/>
                        <GID>EP06AP26.004</GID>
                    </GPH>
                    <HD SOURCE="HD1">Figure 2: Medicare Payments for Non-Hospice Medicare Part D Drugs During Hospice Elections, FYs 2020-2024</HD>
                    <GPH SPAN="3" DEEP="406">
                        <PRTPAGE P="17348"/>
                        <GID>EP06AP26.005</GID>
                    </GPH>
                    <P>Medicare payments for non-hospice Part A and Part B items and services received by hospice beneficiaries during a hospice election increased from nearly $790 million in FY 2020 to over $2 billion in FY 2024 (see Figure B1). This represents an increase in non-hospice Medicare spending for Parts A and B of nearly $1.3 billion, or 160 percent. The most substantial increase in a single year occurred from FY 2023 to FY 2024, which demonstrated an increase in non-hospice Medicare spending for Part A and Part B items and services of $770 million, or 60 percent.</P>
                    <P>
                        While there is minimal beneficiary cost sharing under the Medicare hospice benefit,
                        <SU>4</SU>
                        <FTREF/>
                         non-hospice services received outside of the Medicare hospice benefit are subject to beneficiary cost sharing. In FY 2024, the total beneficiary cost sharing amount for beneficiaries electing the hospice benefit was $510 million for Parts A and B.
                        <SU>5</SU>
                        <FTREF/>
                         In FY 2024, beneficiaries receiving hospice services from for-profit hospices had, on average, nearly 167 percent higher non-hospice spending per day compared to beneficiaries under non-profit hospice care. This represents a significant increase from FY 2022, when beneficiaries receiving hospice services from for-profit hospices had, on average, 60 percent higher non-hospice spending per day compared to beneficiaries under non-profit hospice care.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             The amount of coinsurance for each prescription approximates five percent of the cost of the drug or biological to the hospice determined in accordance with the drug copayment schedule established by the hospice, except that the amount of coinsurance for each prescription may not exceed $5. The amount of coinsurance for each respite care day is equal to five percent of the payment made by CMS for a respite care.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Part A and B cost sharing is calculated by summing together the deductible and coinsurance amounts for each claim.
                        </P>
                    </FTNT>
                    <P>
                        We also examined non-hospice spending during a hospice election by claim type for Part A and Part B items and services, as shown in Table 5. In percentage terms, we found the most dramatic increase in billing related to carrier/physician supply. From FY 2020 to FY 2024, non-hospice spending related to carrier/physician supply increased 317.5 percent with a notable single year spike from FY 2022 to FY 2023 of 63.5 percent, and the largest increase in one year occurred from FY 2023 to FY 2024 with an increase of 90.8 percent. The diagnosis code for carrier claims with the largest increase in spending in FY 2024 was for pressure ulcers, largely associated with skin substitutes, which accounted for 47 percent, almost half of the carrier claim spending. Carrier claims for ulcers from FY 2020 to FY 2024 increased by almost 4,000 percent, rising from $18 million in FY 2020 to $714 million in FY 2024. CMS is aware of the increased provision of skin substitutes overall and changes were made to the reimbursement for 
                        <PRTPAGE P="17349"/>
                        skin substitutes beginning in 2026. Effective January 1, 2026, CMS implemented major changes to skin substitute payments, transitioning most products to a single, national unified rate of approximately $127.14 per cm
                        <SU>2</SU>
                         (90 FR 49266, 90 FR 53448) in CY 2026, with the intent to propose payment rates that differentiate among three FDA regulatory categories in future years. This policy, applicable to both non-facility and hospital outpatient settings, classifies products as “incident-to” supplies to eliminate the Average Sales Price (ASP) + 6 percent model, aiming to significantly reduce Medicare spending. Additionally, it is not unusual for terminally ill patients to have skin breakdown as a result of their deconditioned state and where wound care would be appropriate for comfort. As such, we question why hospices would not be providing needed wound care for pressure ulcers (which could potentially require a skin substitute in certain circumstances) given that pressure ulcers generally develop from unrelieved pressure as a result of limited mobility and in terminally ill individuals who are chairbound or bedbound.
                    </P>
                    <P>Additionally, we found notable consistent increases in outpatient and inpatient services in recent years, as shown in Table 5. From FY 2020 to FY 2024, non-hospice spending related to outpatient services increased 40.4 percent and inpatient services increased by 26.9 percent in the same time frame. Additionally, we found that 30.1 percent and 25.9 percent of the non-hospice spending that occurred in FY 2024 was related to the primary hospice diagnosis of Alzheimer's disease/dementia/Parkinson's and heart conditions (Congestive Heart Failure and other heart disease), respectively. We also found that daily rates of non-hospice spending for services in FY 2024 are greater for every claim type, and 166.9 percent higher in total spending per day, for patients receiving hospice services in for-profit vs. non-profit hospices. We also noted that 67 percent of non-hospice spending occurred after hospice election day 60.</P>
                    <GPH SPAN="3" DEEP="260">
                        <GID>EP06AP26.006</GID>
                    </GPH>
                    <P>
                        Hospices are responsible for covering drugs and biologicals related to the palliation and management of the terminal illness and related conditions while the patient is under hospice care. After a hospice election, many maintenance drugs or drugs used to treat or cure a condition are typically discontinued as the focus of care shifts to palliation and comfort measures. However, those same drugs may be appropriately continued, as they may offer symptom relief for the palliation and management of the terminal prognosis.
                        <SU>6</SU>
                        <FTREF/>
                         Similar to the increase in non-hospice spending during a hospice election for Medicare Parts A and B items and services, non-hospice spending for Part D drugs increased from $552.9 million in FY 2020 to $813.1 million in FY 2024, which represents an increase of over a 47 percent (Figure B2).
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             Update on Part D Payment Responsibility for Drugs for Beneficiaries Enrolled in Medicare Hospice. November 2016. 
                            <E T="03">https://www.cms.gov/Medicare/Medicare-Fee-for-Service-Payment/Hospice/Downloads/2016-11-15-Part-D-Hospice-Guidance.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        Table 6 details the various components of Part D spending for patients receiving hospice care for FYs 2020 to FY 2024. The portion of the FY 2020 to FY 2024 Part D spending that was paid by Medicare is the sum of the Low-Income Cost-Sharing Subsidy and the Covered Drug Plan Paid Amount, approximately $3.3 billion. The beneficiary cost sharing amount was approximately $335.1 million.
                        <SU>7</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Part D cost sharing is calculated by summing together the “the patient pay amount” and the “other true out of pocket” amount that are recorded on the Part D PDE.
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="441">
                        <PRTPAGE P="17350"/>
                        <GID>EP06AP26.007</GID>
                    </GPH>
                    <P>We also note hospice beneficiaries with principal diagnoses of neurological and degenerative diseases, circulatory and cerebrovascular diseases, respiratory diseases, and neoplasms have received clinically indicated services for these conditions outside the hospice benefit. This issue may arise from hospices misclassifying conditions, referring patients to non-hospice providers, failing to coordinate care, or deliberately avoiding costs. We have examined principal hospice diagnoses on claims and identified Part B items and services paid outside the hospice benefit and have found concerning trends in non-hospice spending. Our intent in including data regarding non-hospice spending related to hospice principal diagnosis codes in this proposed rule is to highlight items and services we believe should be covered under the hospice benefit. For example, it is not clear why medications like bronchodilators or oxygen would be considered unrelated to a respiratory condition indicated as the primary hospice diagnosis.</P>
                    <P>As we discussed previously, the hospice model is interdisciplinary and focuses on symptom management rather than curative treatment. Covering related services under the hospice benefit reinforces this philosophy by ensuring that care for the terminal condition, including medications, equipment, supplies, and therapies, is managed and integrated by the hospice IDG. We question whether increased spending outside of the hospice benefit is indicative of diminishing comprehensive and patient-centered care. Covering all items and services related to the principal hospice diagnosis ensures that patients receive coordinated medical, nursing, psychosocial, and supportive services that address the full scope of a patient's end-of-life needs. This approach reduces fragmentation, prevents gaps in care, and supports comfort, dignity, and quality of life. Further, it reduces the burden of navigating additional coverage and cost sharing that the patient would not have under the hospice benefit.</P>
                    <P>
                        As the hospice benefit requires hospice coverage of all items and services related to the terminal illness and any related conditions, the increase in non-hospice spending, particularly for items and services that appear objectively related to the principal diagnosis, may suggest non-compliance with statutory and regulatory requirements and inappropriate cost-
                        <PRTPAGE P="17351"/>
                        shifting to other Medicare benefits. Covering items and services related to the principal hospice diagnosis is essential to maintaining the integrity of the hospice benefit, ensuring coordinated and compassionate end-of-life care, protecting beneficiaries, and supporting responsible stewardship of Medicare resources. In the following section, we describe in more detail spending data on non-hospice services from FY 2024.
                    </P>
                    <GPH SPAN="3" DEEP="216">
                        <GID>EP06AP26.008</GID>
                    </GPH>
                    <P>Additionally, we analyzed the same principal diagnosis coding groups for Part D drugs paid outside of the hospice benefit.</P>
                    <GPH SPAN="3" DEEP="250">
                        <GID>EP06AP26.009</GID>
                    </GPH>
                    <HD SOURCE="HD3">Neurological and Degenerative Diseases</HD>
                    <P>
                        We grouped claims in this diagnostic coding group using ICD-10-CM codes for G30, G31, and G20. This group includes Alzheimer's disease, Parkinson's disease, and other degenerative diseases of the nervous system. In FY 2024 claims, there are about 48,840,937 hospice days and 1,951,568 hospice claims in this diagnosis coding group. The non-hospice spending for this category for DME and carrier claim types was about $576 million. DME services that were billed during hospice stays related to these conditions during the same time included medical/surgical supplies, such as wound care supplies, catheters and incontinence supplies, tubing, masks, and needles, costing about $400 million, and wheelchairs, oxygen supplies, and hospital beds together cost about $0.5 million. Part D drugs that were billed during hospice stays related 
                        <PRTPAGE P="17352"/>
                        to these conditions included (but are not limited to) about $44.5 million for common palliative drugs, such as analgesics, anxiolytics, antiemetics, and laxatives; $1.7 million for therapeutic nutrients and electrolytes; and $0.8 million for diuretics.
                    </P>
                    <HD SOURCE="HD3">Circulatory and Cerebrovascular Diseases</HD>
                    <P>We grouped claims in this diagnostic coding group using ICD-10-CM codes for I11, I25, I50, I63, I67, I69, and I13. This group includes circulatory and cerebrovascular diseases, such as heart failure, cerebrovascular diseases (stroke), ischemic heart disease, and hypertensive heart/kidney disease. In FY 2024 claims, there are about 47,380,977 hospice days and 1,938,372 hospice claims in this diagnosis coding group. The non-hospice spending for these conditions for DME and carrier claim types was about $590 million. DME services that were billed during hospice stays related to these conditions during the same time included (but are not limited to) medical/surgical supplies costing about $402 million; wheelchairs, oxygen supplies, and hospital beds together cost about $1.1 million. Part D drugs that were billed during hospice stays related to these conditions included about $177 million for anticoagulants, blood cell stimulations, beta blockers, vasodilators, and anti-hypertensives; $18.6 million for common palliative drugs, such as analgesics, anxiolytics, antiemetics, and laxatives; $3 million for therapeutic nutrients and electrolytes; and $2.2 million for diuretics.</P>
                    <HD SOURCE="HD3">Respiratory Diseases</HD>
                    <P>We grouped claims in this diagnostic coding group using ICD-10-CM codes for J44 and J96. This group includes chronic obstructive pulmonary disease and respiratory. In FY 2024 claims, there are about 11,101,869 hospice days and 511,917 hospice claims in this diagnosis coding group. The non-hospice spending for this category for DME and carrier claim types was about $95 million. DME services that were billed during hospice stays related to these conditions during the same time included medical/surgical supplies costing about $50 million; wheelchairs, oxygen supplies, and hospital beds together costing about $0.5 million. Part D drugs that were billed during hospice stays related to this condition included (but are not limited to) about $24 million for bronchodilators; $7 million for common palliative drugs, such as analgesics, anxiolytics, antiemetics, and laxatives; $0.6 million for therapeutic nutrients and electrolytes; and $0.5 million for diuretics.</P>
                    <HD SOURCE="HD3">All Cancers</HD>
                    <P>We grouped claims in this diagnostic coding group using ICD-10-CM codes for C00-D49. This group included all the diagnosis codes in the Neoplasms (C00-D49) Chapter in the ICD-10-CM. In FY 2024 claims, there are about 18,721,188 hospice days and 1,008,342 hospice claims in this diagnosis coding group. The non-hospice spending for this category for DME and carrier claim types was about $106 million. DME services that were billed during hospice stays related to these conditions during the same time included medical/surgical supplies costing about $46 million; wheelchairs, oxygen supplies, and hospital beds together cost about $0.3 million. Part D drugs that were billed during hospice stays related to these conditions included (but are not limited to) about $5.6 million for common palliative drugs, such as analgesics, anxiolytics, antiemetics, and laxatives; $0.5 million for therapeutic nutrients and electrolytes; and $0.4 million for diuretics.</P>
                    <P>
                        For more detailed non-hospice spending data, the full file is available in the downloads section found at the FY 2027 hospice final rule link on the Hospice Center web page at 
                        <E T="03">https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers/hospice-center.</E>
                    </P>
                    <HD SOURCE="HD3">2. Service and Spending Variation Index (SSVI)</HD>
                    <P>CMS currently monitors and publicly shares data related to hospice utilization. Using the most recent, complete claims data, CMS analyzes Medicare spending, utilization by level of care, lengths of stay, live discharge rates, and skilled visits during the last days of life. Interested parties report that such data is useful in highlighting certain issues and trends regarding Medicare policies. Additionally, we monitor a variety of other metrics from claims data including: percent of beneficiaries discharged with length of stay 180 days or more, percent of total discharges that were live discharges, total number of discharges (live or dead), average minutes of direct patient care per RHC day, average visits per RHC day, percent of RHC days on the weekend with at least one skilled visit, non-hospice spending per day, the percent of live discharges where a beneficiary returns to the same hospice within seven days, and total amount of non-hospice spending. By analyzing hospice utilization and other metrics, CMS can evaluate the behaviors of hospices to combat potential risks to the integrity of the Medicare program. </P>
                    <P>
                        Analyzing these particular Medicare hospice metrics together is important because patterns across them can signal potential program integrity risks, inappropriate utilization, or quality of care concerns, especially when they deviate substantially between different hospices or from expected norms. For example, long lengths of stay combined with high live discharge rates may signal inappropriate enrollment of ineligible beneficiaries. Low number of visits, shorter visits, or fewer weekend visits may indicate minimal service provision. We recognize that patient census could vary year to year for each hospice (for example, in a given year, it may be possible that a hospice had a patient census that did not require any general inpatient level of care) and does not necessarily signal that a hospice is acting in an inappropriate manner. As such, we developed a scoring system, the SSVI, that is calculated using nine claims-based measures, each representing different aspects of hospice utilization as well as non-hospice spending. To calculate the SSVI score, we first determined a threshold for each of the nine metrics. For the non-hospice spending component of the SSVI score, we created eight separate thresholds for total non-hospice spending, as the degree to which a hospice spends outside of the hospice benefit can indicate varying levels of concern. For example, a hospice with higher non-hospice spending levels receives a higher number of points than a hospice with about 12.5 percent less non-hospice spending. Metrics related to utilization reflect visit and discharge patterns. The SSVI can be used to identify hospices that are outliers across many different utilization metrics and those that have a high level of non-hospice spending. We established thresholds using percentiles. For most of the individual measures, we established the threshold at the top or bottom 25 percent of the distribution. It is important to note that falling into this quartile on a single measure does not necessarily indicate poor performance or improper practices. There are often legitimate operational reasons for a hospice to be an outlier in an isolated area. Instead, this 25 percent threshold acts as a preliminary filter. The objective of the SSVI is not to evaluate hospices based on a single metric, but to identify hospices that are outliers across multiple independent metrics. A hospice triggering the 25 percent threshold on at least one metric is not uncommon. A hospice triggering that 
                        <PRTPAGE P="17353"/>
                        threshold across many distinct metrics could indicate unusual utilization that may require further review.
                    </P>
                    <P>For these utilization metrics, when a hospice's outcome for that metric surpasses the metric's threshold, then the hospice receives one point in its score for that metric. Second, we add each of the nine scores, that is, one score per metric, together to calculate the SSVI score. The total SSVI score is derived by adding together a hospice's total non-hospice spending score and their utilization score.</P>
                    <P>The lowest SSVI score a hospice can receive is zero, that is, a score of zero for each of the nine metrics, and the maximum SSVI score is 16, that is, with the highest points assigned for each of the nine metrics. A higher SSVI score represents a potential higher level of concern, as this may signal potential program integrity risks or inappropriate utilization especially when a hospice's SSVI score is substantially higher than its peers. In Table 9 below, we describe each of the nine metrics and the threshold values for those metrics. Given that we calculate a hospice's SSVI score using an evaluation of nine metrics, a high SSVI score indicates to CMS that a hospice might have more than one area of concern and may require additional targeted education or oversight, such as medical review, education, and investigations that could result in payment suspension, and revocation, if there is identified fraud, waste, or abuse. In other words, each score used to calculate the SSVI score can be used to identify a specific area of concern for a hospice, and the SSVI score itself provides an aggregate measure to evaluate a hospice as a whole. The SSVI can assist interested parties in comparing hospices on a holistic scale. Likewise, the SSVI is potentially another vehicle to target, and address fraud, waste, and abuse. For example, higher spending outside the Medicare hospice benefit may be indicative of abusive billing because a hospice is paid a comprehensive per diem to cover essentially all care at the end of life. Excessive non-hospice spending, for either unrelated care or services and supplies which should be the hospice's responsibility, may undermine the financial integrity of the hospice benefit.</P>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17354"/>
                        <GID>EP06AP26.010</GID>
                    </GPH>
                    <P>
                        We plan to determine the SSVI for individual hospices each fiscal year using that applicable year's data. In this proposed rule, we are publishing the SSVI scores calculated from data for FYs 2024 and 2025 because these are our 
                        <PRTPAGE P="17355"/>
                        most recent and complete years of claims data. We may update the FY 2024 and FY 2025 SSVIs with any revisions we deem appropriate from comments received on this proposed rule, when we publish the FY 2027 Hospice Wage Index and Rate Update final rule. In subsequent rulemaking cycles, we would publish the updated SSVI, using the most recent claims data, with the final rule. The FY 2024 hospice SSVI includes 6,409,155 hospice claims, representing 6,735 hospices and a total of 148,012,785 hospice days. The FY 2025 hospice SSVI includes 6,750,840 hospice claims, representing 6,642 hospices and a total of 156,514,386 hospice days. Table 10 shows the distribution of the number of hospices by their total score for hospices in FYs 2024 and 2025 claims.
                    </P>
                    <GPH SPAN="3" DEEP="471">
                        <GID>EP06AP26.011</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                    <P>
                        We will post the metrics and the SSVI scores for FYs 2024 and 2025, additional data from claims-based measures, and related documentation on the methodology on our Hospice Center web page at 
                        <E T="03">https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers/hospice-center.</E>
                         Our goal is to identify individual hospice vulnerabilities to help focus program integrity efforts, such as conducting medical reviews, providing additional education, and conducting investigations into individual hospices that could result in administrative actions like payment suspension and/or revocation of hospices demonstrating fraudulent behavior. We also believe the public will benefit from the enhanced transparency this data provides, allowing beneficiaries and their families the ability to make more informed choices regarding care at the end of life. We seek feedback on the metrics used to calculate the SSVI score as well as thoughts and suggestions regarding the threshold values and point assignments.
                        <PRTPAGE P="17356"/>
                    </P>
                    <HD SOURCE="HD2">C. Proposed Election Statement Addendum Changes</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Hospice care is a comprehensive, holistic approach to treatment that recognizes the impending death of an individual may necessitate a transition from curative to palliative care if the individual so chooses. Medicare hospice care services are virtually all-inclusive, and are focused on meeting the physical, emotional, psychosocial, and spiritual needs of the terminally ill individual and his or her family. In order to make an informed choice about whether to receive hospice care, the patient, family, and caregiver must have an understanding of what services are going to be provided by the hospice and that, because there is no longer a reasonable expectation for a cure, care should now focus on comfort and quality of life. The services covered under the Medicare hospice benefit are comprehensive such that, upon election, the individual waives all rights to Medicare payment for services related to the treatment of the individual's condition with respect to which a diagnosis of terminal illness has been made, except when provided by the designated hospice or attending physician. Because of the significance of this decision, the terminally ill individual must elect hospice care in order to receive services under the Medicare hospice benefit. Since we first implemented the Medicare hospice benefit in 1983, it has been our general view that the waiver required by law requires hospices to provide virtually all the care that is needed by terminally ill patients (48 FR 56010). In the FY 2020 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Requirements final rule (84 FR 38484), we finalized a policy, for elections beginning on and after October 1, 2020, that requires hospices to provide a hospice election statement addendum to beneficiaries, their representatives, non-hospice providers, or Medicare contractors, upon request. The purpose of the addendum is to notify the hospice beneficiary (or representative) of those conditions, items, services, and drugs the hospice will not be covering because the hospice has determined they are unrelated to the beneficiary's terminal illness and related conditions. The addendum is subject to review and must be updated, as needed, when the plan of care is updated in accordance with §  418.56. The hospice must provide these updates, in writing, to the beneficiary (or representative).</P>
                    <P>Currently, if the beneficiary (or representative) requests an addendum at the time of hospice election (that is, within the first 5 days of the hospice election date), the hospice would have 5 days from the date of the request to furnish this information in writing. If the addendum is requested during the course of hospice care (that is, after the first 5 days of the date of the hospice election), the hospice has 3 days from the date of the request to provide the addendum in writing. However, if the beneficiary dies, revokes, or is discharged within the required timeframes, the hospice would not be required to furnish the addendum in this circumstance. These timeframes, and others, for providing the addendum are outlined in § 418.24(d). The required content of the hospice election statement addendum is outlined generally below and described in § 418.24(c):</P>
                    <P>• The addendum title (“Patient Notification of Hospice Non-Covered Items, Services, and Drugs”);</P>
                    <P>• Hospice name;</P>
                    <P>• Individual's name and medical record identifier;</P>
                    <P>• Identification of the terminal illness and related conditions;</P>
                    <P>• A list of the individual's conditions present on hospice admission (or upon POC update) and the associated items, services, and drugs not covered by the hospice because they have been determined by the hospice to be unrelated to the terminal illness and related conditions;</P>
                    <P>• A written clinical explanation written in language that the beneficiary (or representative) can understand;</P>
                    <P>• References to relevant any clinical practice, policy, or coverage guidelines;</P>
                    <P>• Information on the purpose of the addendum and the right to immediate advocacy through the Medicare Beneficiary and Family Centered Care-Quality Improvement Organization (BFCC-QIO) if the individual (or representative) disagrees with the hospice's determination;</P>
                    <P>• Individual (or representative) name, signature, and date signed, along with a statement that signing the addendum (or its updates) is only acknowledgement of receipt of the addendum (or its updates) and not the individual's (or representative's) agreement with the hospice determinations; and</P>
                    <P>• The date the hospice furnished the addendum.</P>
                    <HD SOURCE="HD3">2. Proposed Mandatory Hospice Election Statement Addendum for All Elections</HD>
                    <P>We are proposing to require that hospices provide the hospice election statement addendum to all Medicare beneficiaries at the time of hospice election for hospice elections beginning on or after October 1, 2026. Section 1812(d)(1) of the Act requires beneficiaries to affirmatively elect hospice care, and the hospice election involves a significant waiver of Medicare rights, as beneficiaries waive all rights to Medicare payment for services related to the treatment of their terminal illness and related conditions, except for services provided by the designated hospice and attending physician, pursuant to section 1812(d)(2)(A) of the Act. Given the magnitude of this decision and its impact on beneficiary rights and access to care, it is essential that beneficiaries receive complete information about what services will and will not be covered by the hospice at the time of election to ensure truly informed consent.</P>
                    <P>Additionally, section 1871 of the Act provides the Secretary with broad authority to prescribe regulations necessary to carry out the administration of the Medicare program, including the authority to establish provider conditions of participation, payment requirements, and beneficiary rights and protections. Specifically, section 1871(f)(1) specifies that the Secretary should make efforts to reduce inconsistency or conflicts for individuals entitled to Medicare benefits. Under this authority, and consistent with our obligation to ensure beneficiary protection and program integrity, we require that hospices provide comprehensive disclosure of coverage determinations to all beneficiaries electing the hospice benefit.</P>
                    <P>
                        In the FY 2020 Hospice Wage Index and Payment Rate Update proposed rule (84 FR 17570), CMS reiterated that hospice services should be providing virtually all the care needed by the terminally ill individual. CMS also reiterated that coverage decisions and treatment determinations should take into account multiple factors, including not only the opinion of the treating physician, but also other factors such as the condition of the patient upon admission, the nature of the principal diagnosis, and the existence of comorbid conditions, as these all play an important role in coverage determinations. Determinations about unrelated conditions, items, services, and drugs for each patient should take into account the needs, preferences, and goals of the terminally ill individual and his or her family; review of all of the beneficiary's conditions, related and unrelated to the terminal illness and related conditions; and current clinically relevant information 
                        <PRTPAGE P="17357"/>
                        supporting all diagnoses as required by regulation at § 418.25. This process requires clinical judgment in which hospices need to consider clinical practice guidelines and relevant research when making determinations of whether items, services, and drugs are related or unrelated to the terminal illness and related conditions.
                    </P>
                    <P>The significant increases in non-hospice spending patterns, as discussed in section III.B.1. of this proposed rule, suggest that the current framework, where the hospice election statement addendum is provided only upon request, has not achieved the intended accountability objective of ensuring that hospices provide virtually all care needed by terminally ill individuals as required under the comprehensive and holistic Medicare hospice benefit. Most notably, as discussed in section III.B.1., Medicare non-hospice spending for Parts A and B increased from nearly $790 million in FY 2020 to over $2 billion in FY 2024, representing a 160 percent increase, demonstrating that the voluntary nature of the current addendum requirement has not adequately addressed coverage transparency concerns or stemmed inappropriate billing of services outside of the hospice benefit. Additionally, many beneficiaries may not understand the importance of requesting the addendum, may not understand their right to receive this information, or may not receive it in time to make fully informed decisions about their care, also not achieving the intended transparency objective. Further, the substantial growth in non-hospice spending, particularly for services that may be related to the terminal illness and related conditions, indicates potential gaps in coverage transparency and coordination between hospice and non-hospice providers.</P>
                    <P>Per the hospice CoPs at § 418.56(e)(5), hospices are required to develop and maintain a system of communication and integration among all providers furnishing care to the terminally ill patient. This includes the ongoing sharing of information with other non-hospice healthcare providers and suppliers furnishing services unrelated to the terminal illness and related conditions is necessary to ensure coordination of services and to meet the patient, family, and caregiver needs. Despite this CoP requirement, we continue to receive reports from non-hospice providers stating that they are not provided a beneficiary's addendum when requested from the hospice, are unable to reach, or do not receive communication from the hospice to discuss the hospice beneficiary's coordination of services that the hospice has determined unrelated to his or her terminal illness and related condition(s). Similarly, we have also received reports from non-hospice providers who state that hospices are requesting that services be billed to Medicare Part A and B, other inquiries where non-hospice providers are requesting payment from hospices for services that should be the hospices' coverage responsibility but where the hospices have not paid for such services or do not respond to these requests, and hospices who state they were unaware that patients had received care from non-hospice providers. Additionally, if a beneficiary receives services related to the terminal illness and related conditions and the hospice did not arrange for such care, the beneficiary, potentially unknowingly, would be liable for the costs related to those services. Likewise, Medicare would be making duplicative payments for care related to the terminal illness and related conditions if non-hospice providers bill Medicare for services that should have been the coverage responsibility of the hospice.</P>
                    <P>
                        Additionally, the Office of Inspector General (OIG) has completed audits on non-hospice spending for outpatient services provided to hospice beneficiaries,
                        <SU>8</SU>
                        <FTREF/>
                         Medicare payments to non-hospice providers for items and services provided to hospice beneficiaries,
                        <SU>9</SU>
                        <FTREF/>
                         and improper Medicare payments for durable medical equipment, prosthetics, orthotics, and supplies provided to hospice beneficiaries.
                        <SU>10</SU>
                        <FTREF/>
                         These reports highlight vulnerabilities in the Medicare hospice benefit and describe fragmented care that beneficiaries may experience under a hospice election.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Medicare Improperly Paid Acute-Care Hospitals an Estimated $190 Million Over 5 Years for Outpatient Services Provided to Hospice Enrollees (A-09-23-03024). November 12, 2024. 
                            <E T="03">https://oig.hhs.gov/documents/audit/10055/A-09-23-03024.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Medicare Payments of $6.6 Billion to Nonhospice Providers Over 10 Years for Items and Services Provided to Hospice Beneficiaries Suggest the Need for Increased Oversight (A-09-20-03015). February 14, 2022. 
                            <E T="03">https://oig.hhs.gov/documents/audit/9604/A-09-20-03015-Complete%20Report.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             Medicare Improperly Paid Suppliers an Estimated $117 Million Over 4 Years for Durable Medical Equipment, Prosthetics, Orthotics, and Supplies Provided to Hospice Beneficiaries (A-09-20-03026). November 16, 2021. 
                            <E T="03">https://oig.hhs.gov/documents/audit/9609/A-09-20-03026-Complete%20Report.pdf.</E>
                        </P>
                    </FTNT>
                    <P>In the FY 2022 Hospice Wage Index and Payment Rate Update proposed rule (86 FR 42528), we requested feedback from interested parties as to whether the hospice election statement addendum has changed the way hospices make care decisions and how the addendum is used to prompt discussions with beneficiaries and non-hospice providers to promote the care needs of hospice beneficiaries. The responses revealed that the FY 2020 addendum provisions (84 FR 38484) enhanced communication during the admission process and prompted hospice providers to ensure patients are receiving all services necessary for symptom management regardless of the primary diagnosis. However, the feedback also included reports that very few patients and their representatives had requested the addendum and that the burden of implementation of the addendum outweighed the benefit.</P>
                    <P>In the FY 2024 Hospice Wage Index and Payment Rate Update proposed rule (88 FR 20022), we solicited feedback on how to work with hospice providers to ensure Medicare beneficiaries and their families are aware of coverage under the hospice benefit and how to enhance transparency. Comments discussed in the FY 2024 Hospice Wage Index and Payment Rate Update final rule (88 FR 51164) emphasized the critical need for CMS education directed toward patients and families about transitioning from curative to palliative interventions at the time of hospice admission. Specifically, several commenters suggested that the hospice election statement addendum (titled “Patient Notification of Hospice Non-Covered Items, Services, and Drugs”) should be provided to all patients at the time of hospice election or as part of the care plan, rather than only upon request. Commenters noted that hospice providers, non-hospice providers, Medicare beneficiaries, and their families need more information to understand coverage distinctions and that hospice providers must share this information with patients at the time of, and throughout, hospice election.</P>
                    <P>
                        Based on the FY 2022 feedback from interested parties indicating a low volume of requests, the continued growth in non-hospice spending, and the FY 2024 feedback from interested parties requesting mandatory provision of the addendum at the time of election, we are proposing to require that hospices provide the hospice election statement addendum to all Medicare beneficiaries at the time of hospice election for hospice elections beginning on or after October 1, 2026. We would require hospices to furnish the addendum within the first 5 days of a hospice election (that is, within the first 5 days of the effective date of the hospice election), and any updates to the addendum within 3 days of changes 
                        <PRTPAGE P="17358"/>
                        to the plan of care that impact the addendum determinations, in writing, to the individual (or representative), and to make the addendum available for non-hospice providers and Medicare contractors. This proposal would modify the current requirement at § 418.24(b)(6), (c), and (d), which establishes the addendum as a condition of payment only when requested by beneficiaries, their representatives, non-hospice providers, or Medicare contractors. As such, we propose amending § 418.24 to include the previously stated provisions related to making the hospice addendum mandatory at the time of hospice election. We remind that hospices may provide the election statement addendum in any format that best suits their needs, provided that the content requirements at § 418.24(b) and (c) are met (85 FR 47070); however, if desired, a model hospice election statement addendum is available on the Hospice Center web page at 
                        <E T="03">https://www.cms.gov/Center/Provider-Type/Hospice-Center.</E>
                    </P>
                    <P>As discussed in the FY 2020 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Requirements final rule (84 FR 38484), and again in section V.A. of this proposed rule, hospices are already required to make determinations about related versus unrelated conditions, items, and services as part of their comprehensive assessment and care planning processes. The mandatory addendum requirement would formalize and standardize the communication of these existing determinations to beneficiaries and their representatives. A one-time form development burden estimate was completed in FY 2020 hospice final rule (84 FR 38484). This burden estimate also accounted for the approximate amount of time it would take a hospice to complete the addendum and used the assumption that hospices would provide the addendum to all beneficiaries; it reflected an estimated $11.2 million in total costs to hospice providers. Despite the FY 2020 (84 FR 38484) burden estimates including the one-time addendum form development costs, the burden estimate reflected an estimated $5.2 million net reduction in total provider (that is, hospice provider and non-hospice provider) burden. In addition, the FY 2020 (84 FR 38484) burden estimates for all non-hospice providers (institutional, non-institutional, and Part D pharmacy providers) furnishing services to hospice beneficiaries were estimated to have an $8.2 million total reduction in burden with the availability of the addendum. In the FY 2020 hospice final rule (84 FR 38535), we stated that burden would be reduced for non-hospice providers, including institutional, non-institutional and pharmacy providers because less time would be spent trying to obtain needed information for treatment decisions and accurate claims submissions.</P>
                    <P>While the burden estimates completed in FY 2020 (84 FR 38484) already assumed that hospices would provide the addendum to all beneficiaries, we have updated the burden estimates, in section V.A.1. of this proposed rule, with more recent data that reflects the increase in hospices and hospice elections on the estimated hospice burden associated with the proposed mandatory election statement addendum for all elections; this includes a burden reduction estimate for non-hospice providers. The FY 2027 burden estimates continue to demonstrate a significant total overall burden reduction for non-hospice providers of $40.6 million, as well as a net hospice provider burden reduction of $20.8 million.</P>
                    <P>We solicit comments on this proposal.</P>
                    <HD SOURCE="HD2">D. Proposed Clarifying Regulation Text Changes</HD>
                    <HD SOURCE="HD3">1. Discharge From Hospice Care</HD>
                    <P>In the FY 2025 Hospice Wage Index and Payment Rate Update, Hospice Conditions of Participation Updates, and Hospice Quality Reporting Program Requirements final rule (89 FR 64202), we finalized conforming text changes to align the medical director CoP and the hospice payment requirements. Specifically, we amended § 418.102(b) by adding the physician member of the hospice interdisciplinary group (IDG), as defined in § 418.56(a)(1)(i), as an individual who may provide the initial certification of terminal illness. We also amended the medical director CoP in § 418.102(c) to include the medical director, or physician designee, as defined at § 418.3, if the medical director is not available, or physician member of the IDG among the specified physicians who may review clinical information as part of the recertification of the terminal illness. Further, to align payment regulations regarding the certification of the terminal illness and admission to hospice care under §§ 418.22 and 418.25 with the CoPs at § 418.102, we added “physician designee (as defined in § 418.3)” to clarify that when the medical director is not available, a physician designated by the hospice, who is assuming the same responsibilities and obligations as the medical director, may certify terminal illness and determine admission to hospice care. We clarified that this does not connote a change in policy; rather, we stated that we believe aligning the language at §§ 418.22(c) and 418.25 with the CoPs at § 418.102 allows for greater clarity and consistency between key components of hospice regulations and policies (89 FR 64231).</P>
                    <P>In response to comments received on the proposed amendments to §§ 418.22 and 418.25, in the FY 2025 proposed rule (89 FR 64202) to add physician designee to the hospice certification and admission payment policies, we again agreed with commenters who stated that our regulations at § 418.25 identifying which physicians can determine admission to hospice care should be consistent with those at § 418.22 identifying who can provide the certification of terminal illness. Accordingly, in the FY 2026 Hospice Wage Index and Payment Rate Update, Hospice Conditions of Participation Updates, and Hospice Quality Reporting Program Requirements final rule (90 FR 37416), to align with the updated payment and CoP regulations at §§ 418.22(c)(1)(i) and 418.102(b), respectively, we finalized the addition of “the physician member of the hospice interdisciplinary group” at § 418.25(a) and (b) to indicate that, in addition to the medical director or physician designee, the physician member of the hospice IDG may also determine admission to hospice care. We stated that we believe aligning the language at § 418.25(a) and (b) with the language at §§ 418.102(b) and 418.22(c)(1)(i) would allow for greater consistency between key components of hospice regulations and policies.</P>
                    <P>We note that § 418.26(b) requires that prior to discharging a patient for any reason listed in § 418.26, the hospice must obtain a written physician's discharge order from the hospice medical director. To align with the updated payment regulations at §§ 418.22, 418.102(b), and 418.25(a) and (b) and to create greater consistency between key components of hospice regulations and policies, we are proposing conforming additions to § 418.26(b) to state the hospice may also obtain the written physician's discharge order from the physician designee, as defined at § 418.3, or physician member of IDG. We request comments on the proposed additions to § 418.26(b).</P>
                    <HD SOURCE="HD3">2. Face-to-Face Encounter</HD>
                    <P>
                        Section 6209(f)(1)(A) of the CAA, 2026 amended section 1814(a)(7)(D)(i)(II) of the Act to extend the use of telehealth by a hospice 
                        <PRTPAGE P="17359"/>
                        physician or hospice nurse practitioner to conduct a face-to-face encounter for the sole purpose of recertifying the patient's eligibility for hospice, through December 31, 2027. Additionally, section 6209(f)(1)(B) of the CAA, 2026 amended section 1814(a)(7)(D)(i)(II) of the Act to include a prohibition on the use of telehealth to conduct the face-to-face encounter in the case of such an encounter with an individual occurring on or after January 31, 2026, if such individual is located in an area that is subject to a moratorium on the enrollment of hospice programs under this title pursuant to section 1866(j)(7) of the Act, if such individual is receiving hospice care from a provider that is subject to enhanced oversight under this title pursuant to section 1866(j)(3) of the Act, or if such encounter is performed by a hospice physician or nurse practitioner who is not enrolled under section 1866(j) of the Act and is not an opt-out physician or practitioner. Section 6209(f)(2) of the CAA, 2026 amended section 1814(a)(7)(D)(i)(II) of the Act to require (for face-to-face encounters conducted via telehealth occurring on or after January 1, 2027) that hospice claims include one or more modifiers or codes (as specified by the Secretary) to indicate that such encounter was conducted via telehealth.
                    </P>
                    <P>In accordance with section 6209(f) of the CAA, 2026, we propose amending § 418.22(a)(4)(ii) to align with the provisions described previously. The regulatory language would require the hospice to collect data reflecting face-to-face encounters furnished using telecommunications technology, which includes, at a minimum, the use of audio and video equipment permitting two-way, real-time interactive communication between the patient and the distant site hospice physician or hospice nurse practitioner, and the hospice would do so by reporting a G-code identifying that a face-to-face encounter was furnished using such technology, that is, telehealth. We are soliciting comments on these proposed amendments and on the use of the new G-code identifying face-to-face encounters furnished via telehealth. The proposed coding requirement will enable CMS to enforce the prohibition on the use of telehealth to conduct the face-to-face encounter when the circumstances described in section 6209(f)(1)(B) of the CAA, 2026 are present because we will be able to identify those face-to-face encounters conducted via telehealth. We would not require that in-person face-to-face encounters for the purposes of recertification to be collected on claims. In accordance with section 6209(h) of the CAA, 2026, we would issue further subregulatory guidance on implementation of this provision, including the exclusion from this permissible use of telehealth, via a Change Request (CR).</P>
                    <HD SOURCE="HD2">E. Requests for Information on Medicare Services and Payment Structure</HD>
                    <HD SOURCE="HD3">1. Request for Information on Ways To Enhance the Provision of Palliative Care Outside of Hospice Care: Current Coverage, Billing Practices, and Opportunities for Improvement</HD>
                    <P>Palliative care is often thought of in concert with hospice care; however, it is not mutually exclusive to the end of life. Medicare defines palliative care as patient and family-centered care that optimizes quality of life by anticipating, preventing, and treating suffering. Palliative care throughout the continuum of illness involves addressing physical, intellectual, emotional, social, and spiritual needs and to facilitate patient autonomy, access to information, and choice (§ 418.3). The Medicare hospice benefit provides comprehensive interdisciplinary palliative care once a patient is certified as having a life expectancy of 6 months or fewer; however, many palliative care patients are not yet ready or eligible for hospice. Therefore, as palliative care is a method of care delivery that is provided throughout the continuum of illness, it can be furnished under various Medicare benefits prior to a beneficiary's decision to elect hospice care. In particular, community-based palliative care plays an essential role in improving the quality of life for individuals living with serious illness. The home is an ideal environment for individuals to receive palliative care services, as remaining in the home during a serious illness may help alleviate psychological and mental distress and allow for more intimate caregiving to be provided by family members. Although Medicare does not currently offer a dedicated palliative care benefit, because palliative services are offered across existing Medicare programs, we are interested in soliciting public feedback regarding ways in which we can optimize current coverage and billing practices under various outpatient or home-based benefits to result in more cohesive, integrated, person-centered care as beneficiaries approach hospice care. Understanding how Medicare providers currently support palliative care, how providers bill for these services, and where gaps persist is critical to strengthening community-based palliative care within today's regulatory and payment structure.</P>
                    <P>Although Medicare covers many services that are core to palliative care, coverage can be indirect. Most community palliative care services fall under Medicare Part B, which reimburses for reasonable and medically necessary outpatient care. Medicare Part B also supports access to mental and behavioral health services, including counseling provided by clinical social workers, and rehabilitation therapies such as physical, occupational, and speech therapy aimed at reducing symptom burden and maintaining function. Telehealth, expanded in recent years, further enhances access to palliative expertise for homebound or mobility-limited patients. Medicare Part B also covers certain medical supplies and equipment needed for palliative care, such as oxygen and wheelchairs.</P>
                    <P>While Medicare Part A primarily covers inpatient services, it does provide limited outpatient-related support. Care delivered in hospital outpatient departments may be covered, as well as home health services for patients who are homebound and require skilled care. These benefits, though not palliative-specific, can provide essential nursing, social work, aide, and therapy support that aligns with palliative goals.</P>
                    <P>Medicare Part D further contributes to outpatient palliative care by covering prescription medications for symptom management, such as analgesics, antiemetics, and anxiolytics.</P>
                    <HD SOURCE="HD3">Understanding Billing Practices and Delivering Palliative Care</HD>
                    <P>
                        Because Medicare does not recognize palliative care as a distinct billable service, providers must rely on a variety of codes and benefit categories. Physicians and advanced practice providers typically bill evaluation and management (E/M) visits for outpatient or home-based palliative encounters. Clinicians may provide symptom management, chronic disease support, advance care planning (ACP), and behavioral health care through standard E/M visits or specialized billing codes. For example, ACP services are reimbursable through CPT codes 99497 and 99498, allowing providers to conduct structured discussions about patient values, goals, and treatment preferences. Similarly, chronic care management (CCM), complex CCM, principal care management (PCM), and transitional care management (TCM) codes support ongoing coordination of care, which is central to high-quality 
                        <PRTPAGE P="17360"/>
                        palliative care for complex conditions. Code Z51.5 
                        <E T="03">Encounter for Palliative Care</E>
                         can be used; however, it does not specify what services this code encompasses. These codes also may not reflect the time-intensive nature of holistic, interdisciplinary palliative care. We are interested in understanding how community providers bill for palliative services, which CPT or HCPCS codes they rely on, and what barriers they face in using ACP, care management, or telehealth codes. Specifically:
                    </P>
                    <P>• Do the E/M codes, care management codes, and ACP codes represent the majority of the billing codes providers use to capture community palliative care services?</P>
                    <P>• What services are typically provided when Z51.5 is billed?</P>
                    <P>• Are there challenges in meeting documentation requirements or integrating non-billable team members, such as social workers, chaplains, or nurses who are crucial to palliative care delivery?</P>
                    <P>• Is there uncertainty about compliance requirements or concern that billing for palliative care will result in claims denials?</P>
                    <P>• What non-medical services, such as caregiver training or spiritual care, would most benefit patients if reimbursed? And what enhancements to existing benefits (not requiring legislation) could strengthen palliative care? These might include expanding social worker billing privileges or creating standardized codes or definitions for serious-illness care.</P>
                    <HD SOURCE="HD3">Understanding Program and Beneficiary Needs</HD>
                    <P>Gathering information from providers and beneficiaries is essential to identify how outpatient or community palliative care is currently provided under Medicare and where gaps remain. In addition to providing feedback on billing practices, interested parties can offer insight into broader systemic challenges, staffing limitations, claim denials, and palliative services they provide but cannot bill for under Medicare's current structure. Specifically:</P>
                    <P>• What aspects of palliative care are financially unsustainable for providers?</P>
                    <P>• What documentation requirements do providers typically use, or suggest using, to identify the provision of palliative care?</P>
                    <P>• Do providers commonly refer patients for home health services when a patient needs palliative care concurrently with curative or life-sustaining care?</P>
                    <P>• What services do providers typically offer patients who are not eligible or ready to elect hospice care but require palliative services?</P>
                    <HD SOURCE="HD3">The Path Forward</HD>
                    <P>Medicare's current structure provides several pathways for delivering community palliative care; however, these programs may seem siloed, making it difficult for patients to understand how palliative services are provided outside of the hospice benefit. Interested party feedback is essential for guiding CMS toward policies that expand access to high-quality community palliative care without requiring legislative reform or the creation of an entirely new benefit. By gathering detailed input from those who deliver and manage palliative care services, we can better understand how to strengthen community palliative care under existing benefits. In addition to the questions previously listed, we are soliciting input on any additional targeted enhancements within current benefits, such as expanding billable services, simplifying documentation, standardizing definitions, or increasing beneficiary education that could meaningfully expand access to palliative care services. As the population ages and the prevalence of serious illness grows, refining how Medicare supports community palliative care, prior to hospice care, is both a practical necessity and an opportunity to enhance the well-being of millions of beneficiaries.</P>
                    <HD SOURCE="HD3">2. Request for Information Regarding Construction of a Hospice Specific Wage Index</HD>
                    <P>The hospice wage index is used to adjust payment rates for hospices under the Medicare program to reflect local differences in area wage levels, based on the location where services are furnished, as determined by the Secretary, in accordance with sections 1814(i)(1)(A) and 1814(i)(2)(D) of The Act. As described in the FY 1998 Hospice Wage Index final rule (62 FR 42860), the pre-floor and pre-reclassified hospital wage index is used as the raw wage index for the hospice benefit. These raw wage index values are subject to application of the hospice floor to compute the hospice wage index used to determine payments to hospices. Additionally, our regulations at § 418.306(c) require that each labor market be established using the most current hospital wage data available, including any changes made by the Office of Management and Budget (OMB) to Metropolitan Statistical Area (MSA) definitions.</P>
                    <P>However, CMS has received numerous comments regarding the use of the Inpatient Prospective Payment System (IPPS) wage index to adjust for the geographic variation of wages for hospice staff through the annual hospice rulemaking. Specifically, commenters have stated that the IPPS wage index uses data from four FYs prior to the current payment year and that the time lag may underestimate the changes in relative wages for hospice staff. Commenters have also stated that hospitals may have different labor costs and occupational mix than hospices and have requested that, like inpatient hospitals, hospices be able to reclassify their wage index in some instances. Additionally, we have received feedback opposing our proposals to adopt the new revised OMB CBSA delineations and the wage index values assigned to their geographic areas, wage index values assigned to rural areas, and adjusting wage index differences between high wage index and low wage index hospices in adjacent local areas through exceptions.</P>
                    <P>
                        We have also received recommendations from MedPAC to include all-employer, occupation-level wage data to establish different weights for setting-specific occupational labor mix to capture labor costs faced by all employers of the related occupations. In 2007 and 2022, MedPAC proposed using the BLS for wage data and to construct new wage indexes to more accurately reflect local area differences in labor costs between and within MSAs and statewide rural areas.
                        <E T="51">11 12</E>
                        <FTREF/>
                         Following the MedPAC analysis, a CMS-commissioned study issued in 2009 concluded that despite some limitations, BLS wage information is more accurate and reliable than the current source of wage information.
                        <SU>13</SU>
                        <FTREF/>
                         In a separate commissioned study from the Institute of Medicine (IOM), the committee examined ways to improve the accuracy of data sources and methods used for making the adjustments to payment to reflect geographic variation in labor prices.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             MedPAC, Report to Congress, 2007, p.124-125.
                        </P>
                        <P>
                            <SU>12</SU>
                             MedPAC, Report to Congress, 2023, p.386.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             MaCurdy et al., Revision of Medicare Wage Index.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             Committee on Geographic Adjustment Factors in Medicare Payment; Board on Health Care Services; Institute of Medicine; Edmunds M, Sloan FA, editors. Geographic Adjustment in Medicare Payment: Phase I: Improving Accuracy, Second Edition. Washington (DC): National Academies Press (US); 2011 Jun 1. Available at 
                            <E T="03">https://www.ncbi.nlm.nih.gov/books/NBK190070/</E>
                             doi: 10.17226/13138.
                        </P>
                    </FTNT>
                    <P>
                        In response to these numerous, ongoing comments from interested parties regarding the hospice wage 
                        <PRTPAGE P="17361"/>
                        index, we have examined possible alternatives to using the IPPS wage index for geographically adjusting hospice payments. We note that other non-hospital settings have also investigated using alternatives to the IPPS wage index, as hospital cost reports may not be representative of the occupations relative to the post-acute care settings. Most recently, in the CY 2025 End Stage Renal Disease (ESRD) PPS final rule (89 FR 89116), we finalized changes to the ESRD PPS wage index using BLS Occupational Employment and Wage Statistics (OEWS) data. Furthermore, in the 2023 Report to the Congress, MedPAC recommended using county-level wage data from the BLS with an occupational mix to construct a wage index that is more specific to the payment setting.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             MedPAC, Report to Congress, 2023, p.386.
                        </P>
                    </FTNT>
                    <P>
                        CMS hosted a Technical Expert Panel (TEP) on September 10, 2025, inviting 14 participants representing various interested parties including industry associations, academia, and hospices, to seek feedback on a proposed alternative to the current hospice wage index. We also provided a technical report for the TEP panelists that gave additional details regarding the potential methodology that could be used to construct a new hospice specific wage index and preliminary results for how specific hospices would be impacted. The TEP summary report, which summarizes the discussion and recommendations of the TEP, as well as the TEP technical report, which provides a detailed examination of the discussed alternative approaches, may be found at 
                        <E T="03">https://www.cms.gov/medicare/payment/prospective-payment-systems/hospice/hospice-educational-resources.</E>
                         In this proposed rule, we are looking for feedback on how the BLS OEWS data, and other public data can be used to construct a hospice specific wage index.
                        <SU>16</SU>
                        <FTREF/>
                         CMS requests input to understand the advantages and limitations of the suggested approach in using BLS data and cost reports to support the construction of a hospice specific wage index. In addition, as discussed elsewhere in the 
                        <E T="04">Federal Register</E>
                        , we note that we are also considering the potential use of alternative data sources in other payment systems including the Inpatient Rehabilitation Facilities (IRF) PPS and Skilled Nursing Facilities (SNF) PPS. We seek feedback on the unique considerations applicable to hospices that should inform how CMS considers the potential use of alternative data sources. We are seeking comment on the following suggested components of how a new hospice specific wage index would be constructed:
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">https://www.bls.gov/respondents/oes/instructions.htm#online.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">(1) Source data for determining area wages:</E>
                         When considering a source for wage data, we believe it is important that the data used is public to promote transparency, such that relevant interested parties would have access to the data and can conduct their own analyses. The IPPS hospital wage index is updated annually, based on a survey of wages and wage-related costs of short-term, acute care hospitals, as required by section 1886(d)(3)(E) of the Act. The final FY 2026 hospice wage index is based on the FY 2026 hospital pre-floor, pre-reclassified wage index for hospital cost reporting periods beginning on or after October 1, 2021 and before October 1, 2022 (using FY 2022 cost report data).
                    </P>
                    <P>
                        The BLS OEWS data provides MSA-level wage data for health professionals, including clinical and administrative office staff, that is updated annually using a pooled sample of six semi-annual surveys.
                        <SU>17</SU>
                        <FTREF/>
                         BLS OEWS data includes information on the wages that employers paid to their employees. It does not include self-employed contract labor wages or benefits paid to employees.
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">https://www.bls.gov/oes/current/oes_tec.htm.</E>
                        </P>
                    </FTNT>
                    <P>The hospice specific wage index would also include the use of freestanding hospice cost reports, claims, and Census Bureau population data. We would only be using freestanding hospice cost reports to ensure cost accuracy, as facility-based reports may share costs with the larger facility. Claims data is used to retrieve the total minutes of care delivered by the seven different disciplines of care (physical therapy, occupational therapy, speech language pathology, skilled nursing, medical social service, and home health aide) that are currently billed as visits on the claims form. Census Bureau population data is used to calculate weighted averages when aggregating wage data.</P>
                    <P>
                        <E T="03">(2) Occupational mix weights:</E>
                         In the IOM study, the committee recommended using a fixed national set of weights based on the hours of each occupation employed nationwide. When considering the construction of a hospice specific wage index, we need to better understand how hospices currently employ staff and determine what would be appropriate for using as fixed national weights. We want to gather feedback on relevant occupational categories to include in this calculation, which may include billable occupations, such as aides, registered nurses, licensed practical nurses, nurse practitioners, nurse assistants, medical social workers, physicians, occupational therapists, physical therapists, and speech pathologists. Since the full-time equivalent hours for the occupations are not reported in hospice cost reports, we would need to estimate using the most complete claims data available.
                    </P>
                    <P>The occupational mix determines how much weight each occupation's wage receives in the overall calculation of the wage level for each geographic area and the national level. Our suggested approach uses expenses reported in hospice cost reports and minutes reported in hospice claims data for 10 occupational categories (hospice aide, registered nurses, nursing administration, physician services, licensed practical nurse, licensed vocational nurse, medical social services, nurse practitioner, physical therapy, occupational therapy, and speech language pathology) shown in Table 11. Three occupations are available on cost reports but not claims (Nursing Administration, Physician Services, Nurse Practitioner). Those three occupations accounted for 22.05 percent of costs on the cost report and their share of the occupational mix was set to this percentage. The remaining 77.95 percent of the occupational mix was allocated among the other seven occupations based on their respective shares of minutes from claims data. We seek input on this suggested approach, as well as any other potential methodologies.</P>
                    <GPH SPAN="3" DEEP="222">
                        <PRTPAGE P="17362"/>
                        <GID>EP06AP26.012</GID>
                    </GPH>
                    <P>
                        <E T="03">(3) Hospice Specific Wage Index Construction:</E>
                         Similar to as described in the CY 2025 ESRD PPS final rule (89 FR 89104), we could construct a wage index for each CBSA by calculating an hourly wage for each CBSA (reflecting a weighted average of the occupational mix) and dividing by the aggregate hourly wage (reflecting a weighted average of the occupational mix). The specific computational steps used to calculate the new ESRD PPS wage index were provided in the supplementary document Addendum C of the CY 2025 ESRD PPS proposed rule.
                        <SU>18</SU>
                        <FTREF/>
                         In the following sections we present a potential methodology for constructing a potential hospice specific wage index:
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/addendum-c-cms-1805-p-esrd-pps-proposed-wage-index-construction-methodology.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Step 1: Estimate the Hospice National Average Occupational Mix</HD>
                    <P>We would use the combination of the share of costs from cost reports and share of minutes from claims to develop a hospice national occupational mix (as shown in Table 11).</P>
                    <HD SOURCE="HD3">Step 2: Calculate Occupation-Specific, CBSA-Level Wage Estimates</HD>
                    <P>To determine how hourly wages in an area compare with national wage levels for specific occupations, we would calculate a CBSA-level wage estimate for each occupation included in the hospice labor mix. The hourly wages provided in areas available in the BLS data do not exactly align with the CBSAs and state-wide rural areas for which wage index values are calculated, therefore we would first map the BLS data to counties. We then impute missing wage estimates at the county-level. Wages for an area could be missing due to small sample size or data quality issues. Finally, we would aggregate county-level hourly wage estimates to the CBSA level using a county population-weighted average of the county-level wage estimates.</P>
                    <HD SOURCE="HD3">Step 3: Calculate Cross-Occupation, CBSA-Level Wage Estimates</HD>
                    <P>For each CBSA, we calculate an average wage by multiplying the occupation-specific, CBSA-level wages by the hospice national occupational mix percentage (that is, registered nurse hourly wage times the 28.46 percent in Table 11) and then summing the wages for all occupations in Table 11. This is the numerator for the CBSA's hospice specific wage index value before adjustments.</P>
                    <HD SOURCE="HD3">Step 4: Calculate the Cross-Occupation, National Wage Estimate</HD>
                    <P>We would calculate the cross-occupation, national wage estimate, which is the denominator of the hospice specific wage index value before adjustments. We calculate a national weighted average of each occupation-specific wage estimate by weighting the occupation-specific wage estimate in each CBSA by the population in a CBSA. We would then weight the national averages by the share in the national occupational mix to obtain a cross-occupation, national wage estimate.</P>
                    <HD SOURCE="HD3">Step 5: Calculating Initial Hospice Wage Index Values</HD>
                    <P>The initial hospice wage index value for each CBSA would be calculated by dividing the cross-occupation, CBSA-level wage estimate from Step 3 by the cross-occupation, national wage estimate from Step 4.</P>
                    <HD SOURCE="HD3">Step 6: Adjustments to the Initial Wage Index Values</HD>
                    <P>We would recalibrate to ensure center of distribution equals the center of the legacy wage index. We would then apply the hospice floor and 5 percent cap on decreases to calculate the final hospice wage index.</P>
                    <P>We seek feedback on any steps that may need to be modified to be applicable to the data available for hospices and related occupations.</P>
                    <P>
                        <E T="03">(4) Labor market areas:</E>
                         The final FY 2026 hospice wage index does not consider any geographic reclassification of hospitals, including those in accordance with section 1886(d)(8)(B) or 1886(d)(10) of the Act. The final FY 2026 hospice wage index includes a 5 percent cap on wage index decreases. The appropriate wage index value would be applied to the labor portion of the hospice payment rate based on the geographic area in which the beneficiary resides when receiving RHC or CHC. The appropriate wage index value is applied to the labor portion of the payment rate based on the geographic location of the facility for beneficiaries receiving GIP or IRC. MedPAC recommended applying the wage index to a blend of MSA/statewide rural and counties as geographic delineation to set wage index values and smooth wage index differences greater than 10 percent between adjacent areas.
                        <SU>19</SU>
                        <FTREF/>
                         Currently, county information is not 
                        <PRTPAGE P="17363"/>
                        available to examine geographic variation of hospice labor costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2022/07/Wage-index-March-2023-SEC.pdf.</E>
                        </P>
                    </FTNT>
                    <P>For the purposes of constructing a hospice specific wage index, we are seeking feedback on the level of geographic delineation of labor market area to be applied to a new wage index and considerations for when neighboring areas have large differences in wage index values. In past rules, we have stated that OMB's geographic area delineations represent a useful proxy for differentiating between labor markets and that the geographic area delineations are appropriate for use in determining Medicare hospice payments. While we continue to hold this belief, we seek feedback from interested parties on what other delineation would be appropriate and what data sources could be used to support the changes.</P>
                    <P>
                        <E T="03">(5) Transition policy:</E>
                         We seek feedback on what an appropriate transition policy may be when shifting from a wage index using hospital IPPS wage data to a hospice specific wage index using BLS wage data.
                    </P>
                    <P>We appreciate hospices and national organizations sharing their support and commitment to offering meaningful comments for consideration. In addition to the methodological questions, we solicit public comment on the following questions:</P>
                    <P>• What data sources and changes should be considered to develop a wage index specific for hospices?</P>
                    <P>• What are the advantages of the suggested approach to constructing wage indexes, relative to the current system?</P>
                    <P>• What are the main limitations of the suggested approach?</P>
                    <P>• Can any limitations be addressed through changes to the data sources mentioned, such as cost reports and claims?</P>
                    <P>• What occupations should be included in the occupational mix to estimate geographic differences in expected prices to employ healthcare staff in hospices?</P>
                    <P>• What additional labor categories, if any, should be added to cost reports to support the revision of the hospice wage index? Are any other changes to the cost reports required for this purpose?</P>
                    <P>• How should we appropriately compare wages between geographic areas that match the way hospice services are delivered? Should we maintain the use of CBSA, or consider other geographic delineation, such as county, census area, etc.?</P>
                    <P>• How should we reduce large differences in wage index values for adjacent geographic areas?</P>
                    <P>• How should we consider policy to support the transition between the current hospice wage index approach to a new one?</P>
                    <HD SOURCE="HD3">3. Request for Information Regarding Medical Aid in Dying (MAID)</HD>
                    <P>
                        The Assisted Suicide Funding Restriction Act of 1997 (Pub. L. 105-12, April 30, 1997) prohibits the use of Federal funds (through Medicare, Medicaid, and other Federal programs) to provide or pay for any health care item or service, or health benefit coverage, for the purpose of causing, or assisting to cause, the death of any individual including mercy killing, euthanasia, or assisted suicide, sometimes referred to as “medical aid in dying” (MAID).
                        <SU>20</SU>
                        <FTREF/>
                         This law amended section 1862(a) of the Act (exclusions from coverage and Medicare as secondary payor) by adding a new paragraph (16) to the list of programs for which no payment may be made under Part A or Part B. CMS codified the exclusion of assisted suicide from coverage in regulation at § 411.15(q). This regulation clarifies that the prohibition does not pertain to the withholding or withdrawing of medical treatment or care, nutrition or hydration or to the provision of a service for the purpose of alleviating pain or discomfort, even if the use may increase the risk of death, so long as the service is not furnished for the specific purpose of causing death. MAID is not legal under Federal law; however, it is considered an end-of-life option for terminally ill adults to self-administer life-ending medication prescribed by a physician in certain states where it is allowed under State law. It is currently legal in 11 states and Washington, DC, and under these existing State laws, strict criteria require a prognosis of 6 months or less to live. More states are passing laws allowing MAID, creating new challenges for hospices and other providers that participate in Federal health programs on how to navigate relevant State and Federal laws.
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             CMS notes that entities must also comply with Section 1553 of the Affordable Care Act. Section 1553 prohibits the Federal Government, and any State or local government or health care provider that receives Federal financial assistance under the ACA, or any health plan created under the ACA from discriminating against an individual or health care entity on the basis that the individual or entity does not provide any health care item or service for assisted suicide, euthanasia, or mercy killing. Section 1553 clarifies it does not apply to withholding or withdrawing medical treatment or medical care, nutrition or hydration, abortion, or use of item or service to alleviate pain or discomfort withholding or withdrawing of medical treatment or care, nutrition or hydration or to the provision of a service for the purpose of alleviating pain or discomfort, even if the use may increase the risk of death, so long as the service is not furnished for the specific purpose of causing or assisting in causing, death, for any reason.
                        </P>
                        <P>CMS also notes that covered entities violate 42 U.S.C. 14406 if they interpret 42 U.S.C. 1395cc(f) or 1396a(w) to require covered entities or their employees “to inform or counsel any individual regarding any right to obtain an item or service furnished for the purpose of causing, or the purpose of assisting in causing, the death of the individual, such as by assisted suicide, euthanasia, or mercy killing; or to apply to or to affect any requirement with respect to a portion of an advance directive that directs the purposeful causing of, or the purposeful assisting in causing, the death of any individual, such as by assisted suicide, euthanasia, or mercy killing.” 42 U.S.C. 14406.</P>
                        <P>
                            The Office for Civil Rights investigates complaints related conscience statutes such as Section 1553, 42 U.S.C. 14406, or religious nondiscrimination provisions. See 
                            <E T="03">https://www.hhs.gov/conscience/your-protections-against-discrimination-based-on-conscience-and-religion/index.html.</E>
                        </P>
                    </FTNT>
                    <P>Because of State requirements (where MAID is allowed under State law) that a patient be terminally ill, we are interested in hearing from hospice providers and other interested parties about any issues that may arise when a Medicare hospice patient requests MAID. In particular:</P>
                    <P>• What information do hospice providers give to these patients and how often is there overlap when a patient pursues MAID? In other words, do hospices generally continue to provide clinical care while a patient seeks qualification for MAID and do patients generally remain on service until death?</P>
                    <P>• Conversely, do hospices encourage patients to revoke their election if they choose to utilize MAID?</P>
                    <P>• Is there confusion amongst hospices regarding visits or other comfort measures that can be provided during this process, especially on the day of death?</P>
                    <P>• Do hospices have written policies regarding caring for patients using MAID? We are especially interested in understanding what hospices do with any unused lethal medications prescribed for MAID.</P>
                    <P>
                        We wish to reiterate that no Medicare funds, including hospice payments, may be used to facilitate MAID, including physician consultation services, prescribing or dispensing of medications used for the purpose of causing death, or assistance with the ingestion of such medications. As such, we are also requesting information on any additional CMS oversight mechanisms that should be in place to safeguard the use of Federal funds for the provision of MAID items and services. We welcome any additional information regarding hospices' experience with patients choosing to utilize MAID, with the expectation that hospice providers and staff are adhering to Federal law.
                        <PRTPAGE P="17364"/>
                    </P>
                    <HD SOURCE="HD2">E. Updates for the Hospice Quality Reporting Program (HQRP)</HD>
                    <HD SOURCE="HD3">1. Background and Statutory Authority</HD>
                    <P>Section 1814(i)(5) of the Act requires the Secretary to establish and maintain a quality reporting program for hospices. The Hospice Quality Reporting Program (HQRP), consisting of Hospice Outcomes and Patient Assessment Evaluation (HOPE) administrative data, and Consumer Assessment of Healthcare Providers and Systems (CAHPS®), Hospice Survey, specifies reporting requirements that hospices complete and submit a standardized set of items for each patient to capture patient-level data, regardless of payer or patient age (§ 418.312(b)). Beginning with FY 2014, section 1814(i)(5) of the Act requires the Secretary to reduce the market basket update by 2 percentage points for those hospices failing to meet quality reporting requirements. Section 407(b) of Division CC, Title IV of the Consolidated Appropriations Act (CAA), 2021 amended section 1814(i)(5)(A)(i) of the Act to change the payment reduction for failing to meet hospice quality reporting requirements from 2 to 4 percentage points beginning in FY 2024 for any hospice that does not comply with the submission requirements provided for that FY. In the FY 2024 Hospice final rule (88 FR 51164), we codified the application of the 4-percentage point payment reduction for failing to meet hospice quality reporting requirements and set completeness thresholds at § 418.312(j).</P>
                    <P>Depending on the amount of the annual update for a particular year, a reduction of 4 percentage points beginning in FY 2024 could result in the annual market basket update being less than zero percent for a FY and may result in payment rates that are less than payment rates for the preceding FY. Any reduction based on failure to comply with the reporting requirements, as required by section 1814(i)(5)(B) of the Act, would apply only for the specified year.</P>
                    <P>In the FY 2014 Hospice Wage Index and Payment Rate Update final rule (78 FR 48234, 48257 through 48262), and in compliance with section 1814(i)(5)(C) of the Act, we finalized a new standardized patient-level data collection vehicle called the Hospice Item Set (HIS). We also finalized the specific collection of data items that support eight consensus-based entity (CBE)-endorsed measures for hospice.</P>
                    <P>
                        In the FY 2015 Hospice Wage Index and Payment Rate Update final rule (79 FR 50452), we finalized national implementation of the CAHPS® Hospice Survey, a component of the CMS HQRP which is used to collect data on the experiences of hospice patients and the primary caregivers listed in their hospice records. Readers who want more information about the development of the survey, originally called the Hospice Experience of Care Survey, may refer to the FY 2014 and FY 2015 Hospice Wage Index and Payment Update final rules (78 FR 48234 and 79 FR 50452, respectively) or to 
                        <E T="03">https://www.hospicecahpssurvey. org/.</E>
                         National implementation commenced January 1, 2015. We adopted eight CAHPS® survey-based measures for the CY 2018 data collection period and for subsequent years. These eight measures are publicly reported on the Care Compare website.
                    </P>
                    <P>In the FY 2016 Hospice Wage Index and Rate Update final rule (80 FR 47142, 47186 through 47188), we finalized the policy for retention of HQRP measures adopted for previous payment determinations and seven factors for removal. In that same final rule, we discussed how we would provide public notice through rulemaking of measures under consideration for removal, suspension, or replacement. We also stated that if we had reason to believe continued collection of a measure raised potential safety concerns, we would take immediate action to remove the measure from the HQRP and not wait for the annual rulemaking cycle. The measures would be promptly removed, and we would immediately notify hospices and the public of such a decision through the usual HQRP communication channels, including but not limited to listening sessions, email notifications and web postings. In such instances, the removal of a measure would be formally announced in the next annual rulemaking cycle.</P>
                    <P>On August 31, 2020, we added correcting language to the FY 2016 Hospice Wage Index and Payment Rate Update and Hospice Quality Reporting Requirements; Correcting Amendment (85 FR 53679) hereafter referred to as the FY 2021 HQRP Correcting Amendment. In the correcting amendment, we made updates to § 418.312 to correct technical errors identified in the FY 2016 Hospice Wage Index and Payment Rate Update final rule. Specifically, the FY 2021 HQRP Correcting Amendment (85 FR 53679) added paragraph (i) to § 418.312 to reflect our exemptions and extensions requirements for reporting, which were referenced in the preamble but inadvertently omitted from the regulations text. Thus, these exemptions or extensions can occur when a hospice encounters certain extraordinary circumstances.</P>
                    <P>In the FY 2017 Hospice Wage Index and Payment Rate Update final rule, we finalized the “Hospice Visits When Death is Imminent” measure pair (HVWDII, Measure 1 and Measure 2), effective April 1, 2017. We refer the public to the FY 2017 Hospice Wage Index and Payment Rate Update final rule (81 FR 52144, 52163 through 52169) for a detailed discussion.</P>
                    <P>
                        As stated in the FY 2019 Hospice Wage Index and Rate Update final rule (83 FR 38622, 38635 through 38648), we launched the “Meaningful Measures Initiative” (which identifies high priority areas for quality measurement and improvement) to improve outcomes for patients, their families, and providers while also reducing burden on clinicians and providers. The Meaningful Measures Initiative is not intended to replace any existing CMS quality reporting programs but would help such programs identify and select individual measures. The Meaningful Measures Initiative priority areas are intended to increase measure alignment across our quality programs and other public and private initiatives. Additionally, it would point to high priority areas where there may be gaps in available quality measures while helping to guide our efforts to develop and implement quality measures to fill those gaps. More information about the Meaningful Measures Initiative can be found at 
                        <E T="03">https://www.cms.gov/medicare/quality/meaningful-measures-initiative.</E>
                    </P>
                    <P>In the FY 2022 Hospice Wage Index and Payment Rate Update final rule (86 FR 42552), we finalized two new measures using claims data: (1) Hospice Visits in the Last Days of Life (HVLDL); and (2) Hospice Care Index (HCI). We also removed the HVWDII measure, as it was replaced by HVLDL. We also finalized a policy that claims-based measures would use 8 quarters of data, which would allow CMS to publicly report on more hospices. Additionally, the rule indicated that public data reflecting hospices' reporting of the two new claims-based quality measures (QMs), the HVLDL and the HCI measures, would be available on the Care Compare/Provider Data Catalogue (PDC) web pages as of the August 2022 refresh.</P>
                    <P>
                        In addition, we removed the seven HIS Process Measures from the program as individual measures, and ceased their public reporting because, in our view, the HIS Comprehensive Assessment Measure is sufficient for measuring care at admission without the seven individual process measures. In the FY 
                        <PRTPAGE P="17365"/>
                        2022 Hospice Wage Index and Rate Update final rule (86 FR 42553), we finalized § 418.312(b)(2), which requires hospices to provide administrative data, including claims-based measures, as part of the HQRP requirements for § 418.306(b). In that same final rule, we provided CAHPS Hospice Survey updates. In the FY 2023 and FY 2024 Hospice Wage Index final rules, we did not propose any new quality measures. However, we provided updates on already-adopted measures. In the FY 2025 Hospice Wage Index final rule, the HQRP finalized two measures, including new data collection through the Hospice Outcomes and Patient Evaluation (HOPE) tool and plans for further development. The FY 2026 Hospice Wage Index final rule provided updates on the HOPE instrument and public reporting.
                    </P>
                    <P>Table 12 shows the current quality measures in effect for the FY 2027 HQRP, which were updated and finalized in the FY 2025 Hospice Wage Index and Payment Rate Update final rule.</P>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="480">
                        <GID>EP06AP26.013</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                    <HD SOURCE="HD3">2. Updates Regarding the HOPE Measures</HD>
                    <P>The HOPE assessment was developed as the new patient assessment tool to replace the HIS as part of the HQRP. HOPE was finalized in the FY 2025 Hospice Wage Index final rule (89 FR 64202) and implemented on October 1, 2025. Additional information regarding HOPE and its associated costs and burden can be found in the FY 2025 Paperwork Reduction Act of 1995 (PRA) submission (CMS-10390; OMB Control Number: 0938-1153).</P>
                    <P>
                        As finalized in the FY 2025 Hospice Wage Index final rule (89 FR 64202), public reporting of the HOPE quality 
                        <PRTPAGE P="17366"/>
                        measures would be implemented no earlier than FY 2028. CMS still expects to begin public reporting in November 2027, but this may change based on the quality and reportability of the data as determined by the CMS analysis of CY 2026 data, which would begin in CY 2027.
                    </P>
                    <P>To meet the assessment timeliness threshold under the Annual Payment Update (APU), hospices must achieve a timely submission rate of 90 percent or higher for FY2027. This means that 90 percent of all HIS and/or HOPE assessments must be submitted to, and accepted by, CMS within 30 days of the patient's admission or discharge date. For HIS assessments, the reporting period is based on the submission of HIS admission or discharge assessments between January 1, 2025, and September 30, 2025. HOPE assessments began submission on October 1, 2025; therefore, the reporting period is based on the submission of the HOPE admission, discharge, and/or HOPE Update Visit (HUV) assessments between October 1, 2025, and December 31, 2025.</P>
                    <P>Due to the newness of the HOPE assessment along with the migration to the iQIES platform, CMS has granted a waiver to all HOPE assessments dated October 1, 2025, through December 31, 2025, and as a result, all HOPE assessments with a target date in 2025 will be considered timely.</P>
                    <HD SOURCE="HD3">3. Proposal To Add an Icon for Hospices on Medicare.gov Compare Tool To Indicate Failure To Meet Reporting Requirements</HD>
                    <P>
                        Since the creation of the Medicare.gov Compare Tool (
                        <E T="03">https://www.medicare.gov/care-compare/</E>
                        ) in 2020, CMS has made improvements to the information available to consumers to drive quality improvement among care settings. Due to the unique challenge of caring for patients in their last days of life, the HQRP has very few publicly reported measures compared to other care settings. Therefore, this lack of information in comparison can make it more challenging for consumers to differentiate between hospices when searching for end-of-life care. To help provide additional information and context to consumers, while also serving to highlight non-compliant hospices, we are proposing to add an icon identifying hospice facilities, on the Medicare.gov Compare Tool, that have failed to meet reporting requirements for the HQRP.
                    </P>
                    <P>The proposed icon will identify hospices failing to submit any data or submitting less than the required 90 percent of HOPE submissions within 30 days of the patient's admission or discharge date within a year period. Despite the APU penalty increase from 2 percent to 4 percent in Fiscal Year (FY) 2024, we have not observed a significant improvement in the number of hospices meeting the QRP reporting requirements. In FY 2023, prior to the APU percentage increase to 4 percent, 20.07 percent of hospices were found to be non-compliant with the HIS reporting requirements. In FY 2024, the first year of the 4 percent APU penalty, 22.06 percent of hospices were found to be non-compliant. In FY 2025, the percentage of non-compliant hospices increased to 23.53 percent and in FY 2026 the percentage of non-compliant hospices was 20.37 percent. The consistent lack of data for approximately one-fifth of hospices limits the ability of CMS to accurately measure the quality of care provided by hospices and limits the amount of data available to a consumer. We are proposing to add an icon to provide an incentive for hospices to comply with the quality data submission requirements, while also communicating to consumers that CMS may not have enough data to adequately determine the quality of the hospice.</P>
                    <P>
                        We propose to add the icon to the 
                        <E T="03">Medicare.gov</E>
                         Compare Tool no earlier than FY 2028 (October 1, 2027) to align with the addition of HOPE data to the 
                        <E T="03">Medicare.gov</E>
                         site, and the data will be based on CY 2026 APU submission data received from January 1, 2026, through December 31, 2026. The proposed icon will be added or removed on an annual basis to give hospices an ample amount of time to review and correct data, and to comply with the 90 percent threshold. The proposed icon would be visible both on the provider search page, as well as the individual hospice page on the Compare Tool, similar to how the icons appear for nursing homes and hospitals on the 
                        <E T="03">Medicare.gov</E>
                         site. Additional information will be added to the Compare Tool to ensure consumers are aware of what the icon means and how it should be taken into consideration. The aim of the icon would be to notify consumers that the hospice did not report sufficient data to CMS. Additional information about HQRP reporting requirements and APU penalty can be found on the HQRP Requirements and Best Practices website at 
                        <E T="03">https://www.cms.gov/medicare/quality/hospice/hqrp-requirements-and-best-practices.</E>
                         We invite public comment on our proposal to include an icon for hospices on the 
                        <E T="03">Medicare.gov</E>
                         Compare Tool to identify hospices that do not comply with the quality data submission requirements for the APU.
                    </P>
                    <HD SOURCE="HD3">4. Future Measures Update</HD>
                    <P>In the FY 2022 Hospice Wage Index and Payment Rate Update final rule (86 FR 42552), we finalized two new measures using claims data: (1) HVLDL; and (2) HCI. Our measure selection activities for the HQRP take into consideration input we receive from the CBE, as part of a pre-rulemaking process that we have established and are required to follow under section 1890A of the Act. The CBE convenes interested parties from multiple groups to provide CMS with recommendations on the Measures Under Consideration (MUC) list. This input informs how CMS selects certain categories of quality and efficiency measures as required by section 1890A(a)(3) of the Act. By February 1st of each year, the CBE must provide that input to CMS.</P>
                    <P>
                        A Technical Expert Panel (TEP) convened in November 2024 provided input on potential new or potential HCI indicators and based on that feedback. This report can be found at 
                        <E T="03">https://www.cms.gov/files/document/fall-2024-hqrp-tep-summary-report508c.pdf.</E>
                         Based on this feedback, along with input from other interested parties and additional analysis of the measure and its indicators, CMS is currently considering making changes to the HCI measure and plans to submit the updated measure to the 2026 MUC list. The aim of re-specifying the HCI measure is to make it more useful and important to providers and consumers.
                    </P>
                    <HD SOURCE="HD3">5. Form, Manner, and Timing of Quality Measure Data Submission</HD>
                    <HD SOURCE="HD3">a. Statutory Penalty for Failure To Report</HD>
                    <P>
                        Section 1814(i)(5)(C) of the Act requires that each hospice submit data to the Secretary on quality measures specified by the Secretary. The data must be submitted in a form and manner, and at a time specified by the Secretary. Section 1814(i)(5)(A)(i) of the Act was amended by the CAA, 2021 and the payment reduction for failing to meet hospice quality reporting requirements was increased from 2 percent to 4 percent beginning with FY 2024. During FYs 2014 through 2023, the Secretary reduced the market basket update by 2 percentage points for non-compliance. Beginning in FY 2024 and for each subsequent year, the Secretary will reduce the market basket update by 4 percentage points for any hospice that does not comply with the quality measure data submission requirements for that FY. In the FY 2023 Hospice 
                        <PRTPAGE P="17367"/>
                        Wage Index final rule (87 FR 45669), we revised our regulations at § 418.306(b)(2) in accordance with this statutory change.
                    </P>
                    <HD SOURCE="HD3">b. Compliance</HD>
                    <P>HQRP Compliance requires understanding the different timeframes for both HIS (or HOPE) and CAHPS: The relevant Reporting Year, the payment FY, and the Reference Year.</P>
                    <P>• The “Reporting Year” (HIS or HOPE) or “Data Collection Year” (CAHPS) is based on the calendar year (CY). It is the same CY for both HIS (or HOPE) and CAHPS. If the CAHPS Data Collection year is CY 2025, then the HIS (or HOPE) reporting year is also CY 2025.</P>
                    <P>• In the “Payment FY”, the APU is subsequently applied to FY payments based on compliance in the corresponding Reporting Year/Data Collection Year.</P>
                    <P>
                        • For the CAHPS Hospice Survey, the Reference Year is the CY before the Data Collection Year. The Reference Year applies to hospices submitting a size exemption from the CAHPS survey (there is no similar exemption for HIS or HOPE).
                        <SU>21</SU>
                        <FTREF/>
                         For example, for the CY 2025 data collection year, the Reference Year is CY 2024. This means providers seeking a size exemption for CAHPS in CY 2025 will base it on their hospice size in CY 2024.
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             CAHPS Hospice Survey, Participation Exemption for Size. 
                            <E T="03">https://www.hospicecahpssurvey.org/en/participation-exemption-for-size/.</E>
                        </P>
                    </FTNT>
                    <P>Submission requirements are codified at § 418.312. Table 13 summarizes the three timeframes. It illustrates how the CY interacts with the FY payments, covering the CY 2025 through CY 2028 data collection periods and the corresponding APU application from FY 2027 through FY 2030. Please note that for the final quarter of CY 2025, CMS has granted a waiver to all HOPE assessments dated October 1, 2025 through December 31, 2025, and as a result, all HOPE assessments with a target date in 2025 will be considered timely.</P>
                    <GPH SPAN="3" DEEP="151">
                        <GID>EP06AP26.014</GID>
                    </GPH>
                    <P>As illustrated in Table 13, CY 2025 data submissions compliance impacts the FY 2027 APU. CY 2026 data submissions compliance impacts the FY 2028 APU. CY 2027 data submissions compliance impacts FY 2029 APU. This CY data submission impacting FY APU pattern follows for subsequent years.</P>
                    <HD SOURCE="HD3">c. Submission of Data Requirements</HD>
                    <P>As finalized in the FY 2016 Hospice Wage Index final rule (80 FR 47142, 47192), hospices' compliance with HIS requirements beginning with the FY 2020 APU determination (that is, based on HIS Admission and Discharge records submitted in CY 2018) are based on a timeliness threshold of 90 percent. This means CMS requires that hospices submit 90 percent of all required HIS records within 30 days of the event (that is, patient's admission or discharge). The 90-percent threshold is hereafter referred to as the timeliness compliance threshold. Ninety percent of all required HIS records must be submitted and accepted within the 30-day submission deadline to avoid the statutorily mandated payment penalty.</P>
                    <P>We applied the same submission requirements for HOPE admission, discharge, and up to two hospice update visit (HUV) records. Hospices will continue to be required to submit 90 percent of all required HOPE records to support the quality measures within 30 days of the event or completion date (patient's admission, discharge, and based on the patient's length of stay up to two HUV timepoints).</P>
                    <P>Hospice compliance with claims data requirements is based on administrative data collection. Since Medicare claims data are already collected from claims, hospices are considered 100 percent compliant with the submission of these data for the HQRP. There is no additional submission requirement for administrative data.</P>
                    <P>
                        To comply with CMS' quality reporting requirements for CAHPS, hospices are required to collect data monthly using the CAHPS Hospice Survey. Hospices comply by utilizing a CMS-approved third-party vendor. Approved Hospice CAHPS vendors must successfully submit data on the hospice's behalf to the CAHPS Hospice Survey Data Center. A list of the approved vendors can be found on the CAHPS Hospice Survey website at 
                        <E T="03">https://www.hospicecahpssurvey.org/.</E>
                    </P>
                    <P>Table 14, HQRP Compliance Checklist, illustrates the APU and timeliness threshold requirements.</P>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="419">
                        <PRTPAGE P="17368"/>
                        <GID>EP06AP26.015</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                    <P>
                        Most hospices that fail to meet HQRP requirements do so because they miss the 90 percent threshold. We offer many trainings and educational opportunities through our websites, which are available 24/7, 365 days per year, to enable hospice staff to learn at the pace and time of their choice. We want hospices to be successful with meeting the HQRP requirements. We encourage hospices to visit the frequently updated HQRP website at 
                        <E T="03">https://www.cms.gov/medicare/quality/hospice.</E>
                         Available trainings can be found on the HQRP Training and Education Library web page at 
                        <E T="03">https://www.cms.gov/medicare/quality/hospice/hqrp-training-and-education-library</E>
                         and additional resources are located on the Requirements and Best Practices web page at 
                        <E T="03">https://www.cms.gov/medicare/quality/hospice/hqrp-requirements-and-best-practices.</E>
                         We also encourage readers to stay informed about HQRP by visiting the HQRP Provider and Stakeholder Engagement web page at 
                        <E T="03">https://www.cms.gov/medicare/quality/hospice/provider-and-stakeholder-engagement</E>
                         to sign-up for the Hospice Quality Listserv.
                    </P>
                    <HD SOURCE="HD1">V. Collection of Information Requirements</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501-3520, we are required to provide notice in the 
                        <E T="04">Federal Register</E>
                         and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. To fairly evaluate whether an information collection should be approved by OMB, 44 U.S.C. 3506(c)(2)(A) requires that we solicit comment on the following issues:
                    </P>
                    <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency.</P>
                    <P>• The accuracy of our estimate of the information collection burden.</P>
                    <P>• The quality, utility, and clarity of the information to be collected.</P>
                    <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques.</P>
                    <P>We are soliciting public comment on each of these issues for the following sections of this document that contain information collection requirements (ICRs):</P>
                    <HD SOURCE="HD2">A. Wage Data Used for the Proposed Mandatory Election Statement Addendum</HD>
                    <P>
                        To derive average (mean) costs, we are using data from the most current U.S. Bureau of Labor Statistics' (BLS's) National Occupational Employment and Wage Estimates for all salary estimates (
                        <E T="03">https://www.bls.gov/oes/tables.htm</E>
                        ). In this regard, Table 15 below outlines BLS's mean hourly wage, our estimated 
                        <PRTPAGE P="17369"/>
                        cost of fringe benefits and other overhead costs (calculated at 100 percent of salary), and our adjusted hourly wage. Table 15 contains our wage rate data for the proposed mandatory Election Statement Addendum: “Patient Notification of Hospice Non-Covered Items, Services, and Drugs” discussed in section III.B. of this proposed rule.
                    </P>
                    <GPH SPAN="3" DEEP="121">
                        <GID>EP06AP26.016</GID>
                    </GPH>
                    <HD SOURCE="HD2">B. Proposed Information Collection Requirements (ICRs)</HD>
                    <HD SOURCE="HD3">1. Proposed Burden Related to Mandatory Election Statement Addendum: “Patient Notification of Hospice Non-Covered Items, Services, and Drugs” (OMB Control Number: 0938-1067/Expiration date: 2/28/2029)</HD>
                    <GPH SPAN="3" DEEP="134">
                        <GID>EP06AP26.017</GID>
                    </GPH>
                    <P>Section 1814(a)(7) of the Act requires that for the first 90-day period of a hospice election, the individual's attending physician (as defined in section 1861(dd)(3)(B) of the Act) (which for purposes of this subparagraph does not include a nurse practitioner or a physician assistant), and the medical director (or physician member of the interdisciplinary group (IDG) described in section 1861(dd)(2)(B) of the Act) of the hospice program providing (or arranging for) the care, each certify in writing, at the beginning of the period, that the individual is terminally ill (as defined in section 1861(dd)(3)(A) of the Act). The regulations codified at §§  418.22 and 418.25 provide the requirements regarding the certification of terminal illness and admission to hospice care. The hospice medical director must specify that the individual's prognosis is for a life expectancy of 6 months or less if the terminal illness runs its normal course. Additionally, clinical information and other documentation that support the medical prognosis must accompany the certification and must be filed in the medical record with the written certification. The physician must include a brief narrative explanation of the clinical findings that supports a life expectancy of 6 months or less as part of the certification. The aforementioned regulations also require that the hospice medical director must consider both related and unrelated conditions and current clinically relevant information when making the decision to certify the individual as terminally ill. Likewise, the hospice CoPs at §  418.102(b) provide the requirements regarding the certification responsibility of the hospice medical director or hospice physician designee, which includes a review of the clinical information, including both related and unrelated conditions, for each hospice patient.</P>
                    <P>To receive hospice services under the Medicare hospice benefit, eligible beneficiaries must elect to receive hospice care by completing an election statement. By signing this election statement, the individual acknowledges that he/she waives all rights to Medicare payments for treatment related to the terminal illness and related conditions. The required content of the hospice election statement is outlined in part below and described in §  418.24(b):</P>
                    <P>
                        • Identification of the particular hospice and of the attending physician that will provide care to the individual. The individual or representative must acknowledge that the identified attending physician was his or her choice.
                        <PRTPAGE P="17370"/>
                    </P>
                    <P>• The individual's or representative's acknowledgement that he or she has been given a full understanding of the palliative rather than curative nature of hospice care, as it relates to the individual's terminal illness.</P>
                    <P>• Acknowledgement that certain Medicare services, as set forth in §  418.24(d), are waived by the election.</P>
                    <P>• The effective date of the election, which may be the first day of hospice care or a later date but may be no earlier than the date of the election statement.</P>
                    <P>• The signature of the individual or representative.</P>
                    <P>Once a beneficiary is certified as terminally ill and elects the Medicare hospice benefit, the hospice conducts an initial assessment visit in advance of furnishing care. During this visit, the hospice must provide the patient or representative with verbal and written notice of the patient's rights and responsibilities as required by the CoPs at §  418.52. Likewise, the regulations at §  476.78 state that providers must inform Medicare beneficiaries at the time of admission, in writing, that the care for which Medicare payment is sought will be subject to Quality Improvement Organization (QIO) review.</P>
                    <P>The beneficiary needs identified in the initial and comprehensive assessments drive the development and revisions of an individualized written plan of care for each patient as required by the hospice CoPs at §  418.56. The hospice plan of care is established, reviewed, and updated by the hospice IDG and must include all services necessary for the palliation and management of the terminal illness and related conditions. While needs unrelated to the terminal illness and related conditions are not the responsibility of the hospice, the hospice may choose to furnish services for those needs regardless of responsibility. However, if a hospice does not choose to furnish services for those needs unrelated to the terminal illness and related conditions, the hospice is to communicate and coordinate with those health care providers who are caring for the unrelated needs, as described in §  418.56(e). In accordance with the CoPs, the hospice must document the services and treatments that address how they will meet the patient and family-specific needs related to the terminal illness and related conditions in the plan of care, and those needs unrelated to the terminal illness and related conditions that are present when the patient elects hospice should also be documented. This documentation ensures that the hospice is aware of those unrelated needs and who is addressing them. This documentation provides the support for the hospices' financial responsibility for the hospice services they will be providing. There is limited beneficiary financial liability for hospice services upon election of the Medicare hospice benefit. However, for any services received that are unrelated to the terminal illness and related conditions, the beneficiary would incur any associated copayments and coinsurance.</P>
                    <P>Hospices already are required to review, determine, and document information on unrelated conditions per the hospice regulations and CoPs. The FY 2020 hospice final rule (84 FR 38484) finalized the requirement at § 418.24(b) and (c) for an election statement addendum titled “Patient Notification of Hospice Non-Covered Items, Services, and Drugs” that must be issued to the patient (or representative), upon request, within 5 days of the hospice election date, or within 3 days of the request during the course of hospice care (that is, after the first 5 days of the hospice election date), to ensure that Medicare beneficiaries are fully informed whether or not all items, services, and drugs identified on the hospice plan of care will be furnished by the hospice. The addendum statement is not required if the beneficiary dies within the required timeframe for furnishing the addendum. This addendum accompanies the hospice election statement. This requirement for payment is codified in the regulations at § 418.24(b) and (c).</P>
                    <P>To ensure Medicare beneficiaries are provided disclosure of those conditions, items, services, and drugs the hospice has determined to be unrelated to the terminal illness and related conditions at the time of admission, we propose to make the issuance of the hospice election statement addendum, in writing, mandatory for all elections at the time of election, rather than upon request of the beneficiary (or representative). Currently, the regulations at §  418.24(b) and (c), require the election statement addendum titled “Patient Notification of Hospice Non-Covered Items, Services, and Drugs” to be issued to the individual (or representative) upon request. We are proposing that the issuance of the hospice election statement addendum would be mandatory for all elections made on or after October 1, 2026, and would accompany the hospice election statement at the time of hospice election.</P>
                    <P>A one-time burden estimate for each hospice to develop and design their own addendum template to best meet their needs was completed in the FY 2020 hospice final rule (84 FR 38484). In the same rule, we also estimated the hospice's burden to complete the addendum; however, we will update these burden estimates to account for changes in the number of hospice elections and number of hospices. As mentioned in the FY 2020 final rule (84 FR 38484), we believe there is no associated burden for hospices to communicate/coordinate with non-hospice providers regarding the content of the addendum statement because the hospice CoPs, as described above, have always required hospices to have a system of communication with non-hospice providers in place. However, we believe that making the election statement addendum mandatory would reduce burden for non-hospice providers through a consistent and streamlined process by which non-hospice providers can make informed treatment decisions and accurately submit claims with the appropriate condition code or modifier. This requirement for payment is included in regulations at §  418.24(b) and (c).</P>
                    <P>The relevant information collection requirements are currently approved under OMB Control Number: 0938-1067/Expiration date: 2/28/2029.</P>
                    <HD SOURCE="HD2">C. Estimated Hospice Burden Related to Mandatory Election Statement Addendum</HD>
                    <HD SOURCE="HD3">1. Estimated Time for Hospice To Complete Addendum</HD>
                    <P>
                        In accordance with the hospice CoPs at §  418.56(a), the hospice must designate a registered nurse that is a member of the IDG to provide coordination of care and to ensure continuous assessment of each patient's and family's needs and implementation of the interdisciplinary plan of care. The hospice CoPs at §  418.54 require that a registered nurse conduct the initial assessment, therefore, the registered nurse would be responsible for completing the addendum for each hospice election as part of the routine admission paperwork. We estimate that there would be 1,873,148 hospice elections in a year based on FY 2024 claims data. However, if a beneficiary dies within the first five days of the hospice election, an addendum would not be required to be provided. Approximately, 19 percent (0.19) of hospice beneficiaries die within the first five days of hospice care. Therefore, the estimated total number of hospice elections in FY 2027 that would require the hospice election statement addendum would be (1,873,148 × 0.81) 
                        <PRTPAGE P="17371"/>
                        = 1,517,250. There are 6,732 Medicare-certified hospices, so on average there would be (1,517,250/6,732) = 225 hospice elections per hospice. The estimated burden for the hospice registered nurse to extrapolate this information from the existing documentation in the patient's hospice medical record and complete this addendum would be 10 minutes (10/60 = 0.1667). At $78.68 per hour for a registered nurse over 10 minutes (0.1667 × $78.68 = $13.12), we estimate the total cost of RN time to complete the addendum per hospice in FY 2027 to be ($13.12 × 225) = $2,952.00, and the total cost of RN time to complete the addendum for all hospices in FY 2027 would be ($2,952.00 × 6,732) = $19,872,864.00. The estimated total per hospice and total annual hospice cost associated with the proposed mandatory addendum in FY 2027 are shown in Table 17. These total costs only include the cost for the RN to complete the addendum statement, as a one-time burden estimate for the addendum form development was accounted for in FY 2020 (84 FR 38484). Additionally, providing this information to the beneficiary is currently part of the routine admissions process and, as such, incurs no additional burden to that process.
                    </P>
                    <GPH SPAN="3" DEEP="154">
                        <GID>EP06AP26.018</GID>
                    </GPH>
                    <HD SOURCE="HD3">2. Burden Estimate Without Election Statement Addendum for Non-Hospice Providers</HD>
                    <P>In order for non-hospice providers to make treatment decisions regarding services, items, and drugs for hospice beneficiaries and to submit the appropriate modifier or condition code on Medicare claims, they need supporting information from the hospice regarding related and unrelated conditions. As such, we first estimate the current burden associated with this communication and coordination in the absence of the election statement addendum. We believe this would require the non-hospice providers to contact the hospice and have a detailed phone call to obtain and document the information on unrelated conditions, items, services, and medications. For non-hospice providers submitting institutional claims (including inpatient acute care hospitals, SNFs, HHAs, and institutional outpatient providers), typically nurse case managers provide coordination of care for those beneficiaries in these settings who are receiving inpatient services or who are preparing to transition to a post-acute care setting or home. The estimated burden for the registered nurse to contact the hospice to obtain the needed information would be 15 minutes (15/60 = 0.25). The average number of hospice beneficiaries receiving services per institutional, non-hospice provider is 15.6 per year, which would mean each institutional, non-hospice provider would have an average of 15.6 communication encounters with hospice. The total number of institutional, non-hospice providers servicing hospice beneficiaries in FY 2024 was 24,086. At $78.68 per hour for a registered nurse (0.25 × $78.68) = $19.67, we estimate the total cost per institutional, non-hospice provider furnishing services to hospice beneficiaries in FY 2027 to be ($19.67 × 15.6) = $306.85 and the annual total cost for all institutional, non-hospice providers in FY 2027 would be ($306.85 × 24,086) = $7,390,789.10.</P>
                    <P>For non-institutional, non-hospice providers (including physicians), we also expect that a nurse would contact the hospice to obtain the needed clinical information on unrelated conditions, items, services and drugs. The estimated burden for the registered nurse to contact the hospice to obtain the needed information would be 15 minutes (15/60 = 0.25). The average number of hospice beneficiaries receiving services per non-institutional, non-hospice provider is 15.5 per year, which would mean each provider would have an average of 15.5 communication encounters with a hospice. The total number of non-institutional, non-hospice providers servicing hospice beneficiaries in FY 2024 was 135,407. At $78.68 per hour for a registered nurse (0.25 × $78.68) = $19.67, we estimate the total cost per non-institutional, non-hospice provider furnishing services to hospice beneficiaries in FY 2027 to be ($19.67 × 15.5) = $304.89 and the annual total cost for all non-institutional, non-hospice providers in FY 2027 would be ($304.89 × 135,407) = $41,284,240.23.</P>
                    <P>
                        For pharmacies dispensing Part D drugs to hospice beneficiaries, the estimated burden for the pharmacy technician at the point of service to contact the hospice to obtain the needed clinical information regarding the drugs deemed by the hospice as unrelated to the terminal illness and related conditions would be 15 minutes (15/60 = 0.25). The average number of hospice beneficiaries receiving services per pharmacy dispensing Part D maintenance drugs is 18.6 per year, which would mean each pharmacy would have an average of 18.6 communication encounters with hospice. The total number of pharmacies dispensing Part D maintenance drugs to hospice beneficiaries in FY 2024 was 57,642. At $45.80 per hour for a pharmacy technician (0.25 × $45.80) = $11.45, we estimate the total cost per pharmacy dispensing Part D maintenance drugs to be ($11.45 × 18.6) = $212.97 and the annual total cost for all pharmacies dispensing Part D maintenance drugs to be ($212.97 × 57,642) = $12,276,016.74. The estimated total annual burden for 
                        <PRTPAGE P="17372"/>
                        all non-hospice providers furnishing services, items and medications to hospice beneficiaries in FY 2027 without the availability of the hospice election statement addendum identifying unrelated conditions, items, services and drugs would be $60,951,046.07 ($7,390,789.10 + $41,284,240.23 + $12,276,016.74).
                    </P>
                    <HD SOURCE="HD3">3. Burden Reduction Estimate With the Proposed Mandatory Election Statement Addendum for Non-Hospice Providers</HD>
                    <P>With the availability of the “Patient Notification of Hospice Covered/Non-Covered Items, Services, and Drugs” election statement addendum, we believe the estimated burden would be reduced for non-hospice providers through a streamlining of the communication and coordination process. Following the same approach used in FY 2020 (84 FR 38484), we analyzed all Medicare Parts A and B non-hospice claims for beneficiaries under a hospice election in FY 2024. We also examined the Part D claims for drugs provided to hospice beneficiaries under a hospice election. Specifically, we analyzed the following:</P>
                    <P>• The total number of non-hospice, institutional claims with condition code 07 (to indicate the services were unrelated to the terminal illness and related conditions).</P>
                    <P>• The total number of non-hospice, non-institutional claims with “GW” modifier (to indicate the services were unrelated to the terminal illness and related conditions).</P>
                    <P>• The total number of Part D claims for beneficiaries under a hospice election.</P>
                    <P>• The average number of hospice beneficiaries per non-hospice provider with institutional claims with condition code 07.</P>
                    <P>• The average number of hospice beneficiaries per non-hospice provider with non-institutional claims with “GW” modifier.</P>
                    <P>• The average number of hospice beneficiaries per non-hospice provider with Part D claims.</P>
                    <P>To calculate the average number of hospice beneficiaries per non-hospice provider, we count the number of unique beneficiaries associated with each non-hospice provider as beneficiaries may receive services by more than one non-hospice provider. This means that some beneficiaries are double-counted. Because we double-counted beneficiaries, we expect that average to be larger than the ratio of unique beneficiaries to unique non-hospice providers. Table 18 summarizes Part A, B and D claims that overlap with hospice episodes in FY 2024.</P>
                    <GPH SPAN="3" DEEP="225">
                        <GID>EP06AP26.019</GID>
                    </GPH>
                    <P>For institutional, non-hospice providers (those who would submit claims for unrelated services with condition code 07), the estimated burden for the registered nurse to contact the hospice to obtain the needed information would be reduced from 15 minutes in the absence of the addendum to 5 minutes (5/60 = 0.0833). The average number of hospice beneficiaries receiving services per institutional non-hospice provider is 15.6 per year. The total number of institutional non-hospice providers servicing hospice beneficiaries in FY 2024 was 24,068. At $78.68 per hour for a registered nurse (0.0833 × $78.68) = $6.55, we estimate the total cost per institutional non-hospice provider in FY 2024 to be ($6.55 × 15.6) = $102.18 and the annual total cost for all institutional non-hospice providers in FY 2024 would be ($102.18 × 24,068) = $2,459,268.24, an annual decrease in burden by ($7,390,789.10−$2,459,268.24) = $4,931,520.86.</P>
                    <P>For non-institutional, non-hospice providers (those who would submit claims for unrelated services with modifier GW), the estimated burden for the registered nurse to contact the hospice to obtain the needed information would be reduced to 5 minutes (5/60 = 0.0833). The average number of hospice beneficiaries receiving services per non-institutional, non-hospice provider is 15.5 per year. The total number of non-institutional, non-hospice providers servicing hospice beneficiaries in FY 2024 was 135,407. At $78.68 per hour for a registered nurse (0.0833 × $78.68) = $6.55, we estimate the total cost per non-institutional, non-hospice provider in FY 2024 to be ($6.55 × 15.5) = $101.53 and the annual total cost for all non-institutional, non-hospice providers in FY 2024 would be ($101.53 × 135,407) = $13,747,872.71, an annual decrease in burden by ($41,284,240.23−$13,747,872.71) = $27,536,367.52.</P>
                    <P>
                        For pharmacies dispensing Part D drugs to hospice beneficiaries, the estimated burden for the pharmacy 
                        <PRTPAGE P="17373"/>
                        technician at the point of service to contact the hospice to obtain the needed clinical information regarding the drugs deemed by the hospice as unrelated to the terminal illness and related conditions would be reduced to 5 minutes (5/60 = 0.0833). The average number of hospice beneficiaries receiving services from pharmacies dispensing Part D maintenance drugs is 18.6 per year. The total number of pharmacies dispensing Part D maintenance drugs to hospice beneficiaries in FY 2024 was 57,642. At $45.80 per hour for a pharmacy technicians (0.0833 × $45.80) = $3.82, we estimate the total cost per pharmacy dispensing Part D maintenance drugs to be ($3.82 × 18.6) = $71.05 and the annual total cost for all pharmacies dispensing Part D maintenance drugs to be ($71.05 × 57,642) = $4,095,464.10, an annual decrease in burden by ($12,276,016.74−$4,095,464.10) = $8,180,552.64.
                    </P>
                    <P>The estimated total annual burden for all non-hospice providers furnishing services, items, and drugs to hospice beneficiaries in FY 2024 with the availability of the hospice election statement addendum identifying unrelated conditions, items, services, and medication would be $20,302,605.05 ($2,459,268.24 + $13,747,872.71 + $4,095,464.10) for an overall burden reduction of ($60,951,046.07−$20,302,605.05) = $40,648,441.02. The total reduction in burden for all institutional, non-institutional, and Part D pharmacy non-hospice providers is summarized in Table 19.</P>
                    <GPH SPAN="3" DEEP="215">
                        <GID>EP06AP26.020</GID>
                    </GPH>
                    <P>The use of the “Patient Notification of Hospice Non-Covered Items, Services, and Drugs” election statement addendum would result in an estimated, annual net reduction in burden of $20,775,577.02 ($40,648,441.02 − $19,872,864.00) in FY 2027. Table 20 summarizes the FY 2027 estimated total burden reduction.</P>
                    <GPH SPAN="3" DEEP="133">
                        <GID>EP06AP26.021</GID>
                    </GPH>
                    <HD SOURCE="HD2">D. Submission of PRA-Related Comments</HD>
                    <P>We have submitted a copy of this proposed rule to OMB for its review of the rule's information collection and recordkeeping requirements. The requirements are not effective until they have been approved by OMB.</P>
                    <P>
                        To obtain copies of the supporting statement and any related forms for the proposed collections previously discussed, visit our website at: 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.html,</E>
                         or call the Reports Clearance Office at (410) 786-1326.
                    </P>
                    <P>
                        We invite public comments on these information collection requirements. If you wish to comment, submit your comments electronically as specified in the 
                        <E T="02">DATES</E>
                         and 
                        <E T="02">ADDRESSES</E>
                         sections of this proposed rule and identify the rule (CMS-1851-P) and, where applicable, indicate the ICR's CFR citation, CMS ID number, and OMB control number.
                        <PRTPAGE P="17374"/>
                    </P>
                    <P>
                        Comments must be received by the date and time specified in the 
                        <E T="02">DATES</E>
                         section of this proposed rule.
                    </P>
                    <HD SOURCE="HD1">VI. Response to Comments</HD>
                    <P>
                        Because of the large number of public comments, we normally receive on 
                        <E T="04">Federal Register</E>
                         documents, we are not able to acknowledge or respond to them individually. We will consider all comments we receive by the date and time specified in the 
                        <E T="02">DATES</E>
                         section of this preamble, and, when we proceed with a subsequent document, we will respond to the comments in the preamble to that document.
                    </P>
                    <HD SOURCE="HD1">VII. Regulatory Impact Analysis</HD>
                    <HD SOURCE="HD2">A. Statement of Need</HD>
                    <HD SOURCE="HD3">1. Hospice Payment</HD>
                    <P>
                        This proposed rule meets the requirements of our regulations at § 418.306(c) and (d), which require annual issuance, in the 
                        <E T="04">Federal Register</E>
                        , of the Hospice Wage Index based on the most current available CMS hospital wage data, including any changes to the definitions of Core Based Statistical Areas (CBSAs) or previously used Metropolitan Statistical Areas (MSAs), as well as any changes to the methodology for determining the per diem payment rates. This proposed rule would update the payment rates for each of the categories of hospice care, described in § 418.302(b), for FY 2027 as required under section 1814(i)(1)(C)(ii)(VII) of the Act. The payment rate updates are subject to changes in economy-wide productivity as specified in section 1886(b)(3)(B)(xi)(II) of the Act.
                    </P>
                    <HD SOURCE="HD3">2. Hospice Election Statement Addendum</HD>
                    <P>This rule includes a proposal to make the hospice election statement addendum mandatory for all hospice elections. This proposal would require hospices to furnish the hospice election statement addendum within the first 5 days of a hospice election (that is, within the first 5 days of the effective date of the hospice election), and any updates to the addendum within 3 days of changes to the plan of care that impact the addendum determinations, in writing, to the to the individual (or representative), and to make the addendum available for non-hospice providers and Medicare contractors. If finalized, this change would become effective for hospice elections on and after October 1, 2026. The election statement addendum would add no additional burden for communicating with non-hospice providers, as this decision-making process has been a long-standing CoP requirement, as described in the preamble of this proposed rule. As reviewed in section V.B.1.of this proposed rule, hospices already are required to review, determine, and document information on unrelated conditions per the hospice regulations and CoPs. Additionally, our previous burden estimate, completed in FY 2020 hospice final rule (84 FR 38484), assumed that an addendum would be requested by every hospice beneficiary (or representative) receiving non-hospice services. While the number of hospice elections, and therefore the number of election statement addendums, have increased since our last burden estimate was completed, we continue to believe the actual burden would be less as hospices are already required to be comprehensive in their approach to covered services. As such, there would be hospices that would spend less time, than estimated, to complete the addendum as the hospice would be providing all items, services, and drugs. However, we believe that making the election statement addendum mandatory would reduce burden for non-hospice providers, including institutional, non-institutional and pharmacy providers because less time would be spent trying to obtain needed information for treatment decisions and accurate claims submissions.</P>
                    <HD SOURCE="HD3">3. Quality Reporting Program</HD>
                    <P>
                        This proposed rule would add an icon to the 
                        <E T="03">Medicare.gov</E>
                         Compare Tool to identify hospices that fail to meet the reporting submission requirements for the Annual Payment Update (APU). These requirements require hospices to submit 90 percent of HOPE assessments within 30 days of a patient's admission or discharge date. This new icon would allow consumers to identify hospices that may lack sufficient data to accurately gauge quality and provide another incentive for hospices to meet the 90 percent threshold.
                    </P>
                    <HD SOURCE="HD2">B. Overall Impact</HD>
                    <P>We have examined the impacts of this proposed rule as required by Executive Order 12866, “Regulatory Planning and Review”; Executive Order 13132, “Federalism”; Executive Order 13563, “Improving Regulation and Regulatory Review”; Executive Order 14192, “Unleashing Prosperity Through Deregulation”; the Regulatory Flexibility Act (RFA) (Pub. L. 96-354); section 1102(b) of the Social Security Act; and section 202 of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                    <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select those regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; and distributive impacts). Section 3(f) of Executive Order 12866 defines a “significant regulatory action” as any regulatory action that is likely to result in a rule that may: (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, or the President's priorities.</P>
                    <P>Based on our estimates, OMB's Office of Information and Regulatory Affairs has determined this rulemaking is significant per section 3(f)(1) of E.O. 12866. Accordingly, we have prepared a regulatory impact analysis that presents the costs and benefits of the rulemaking to the best of our ability.</P>
                    <HD SOURCE="HD3">1. Hospice Payment</HD>
                    <P>
                        We estimate that the aggregate impact of the payment provisions in this proposed rule would result in an estimated increase of $785 million in payments to hospices, resulting from the proposed hospice payment update percentage of 2.4 percent for FY 2027. The impact analysis of this proposed rule represents the projected effects of the changes in hospice payments from FY 2026 to FY 2027. Using the most recent complete data available at the time of rulemaking, in this case FY 2025 hospice claims data as of January 15, 2026, we simulate total payments using the proposed FY 2027 wage index (pre-floor, pre-reclassified hospital wage index with the hospice floor, and the 5 percent cap on wage index decreases) and FY 2026 payment rates and compare it to our simulation of total payments using FY 2025 utilization claims data, the final FY 2026 Hospice Wage Index (pre-floor, pre-reclassified hospital wage index with hospice floor, and the 5 percent cap on wage index decreases) and FY 2026 payment rates. By dividing payments for each level of care (RHC days 1 through 60, RHC days 61+, CHC, IRC, and GIP) using the FY 
                        <PRTPAGE P="17375"/>
                        2026 wage index and payment rates for each level of care by the proposed FY 2027 wage index and FY 2026 payment rates, we obtain a wage index standardization factor for each level of care. We apply the wage index standardization factors so that the aggregate simulated payments do not increase or decrease due to changes in the wage index.
                    </P>
                    <P>Certain events may limit the scope or accuracy of our impact analysis, because such an analysis is susceptible to forecasting errors due to other changes in the forecasted impact time- period. The nature of the Medicare program is such that the changes may interact, and the complexity of the interaction of these changes could make it difficult to predict accurately the full scope of the impact upon hospices.</P>
                    <HD SOURCE="HD3">2. Hospice Election Statement Addendum</HD>
                    <P>As a result of this election statement addendum, we estimate that this rule, if finalized, would generate $20.7 million in annualized cost savings to providers, beginning in FY 2027. The estimated burden reduction for this proposal is detailed in section V.C. of this proposed rule and the total annual estimated reduction is included in Table 20.</P>
                    <HD SOURCE="HD3">3. Hospice Quality Reporting Program</HD>
                    <P>
                        This proposed rule would add an icon to the 
                        <E T="03">Medicare.gov</E>
                         Compare Tool for hospices. There are no associated impacts for hospices with this proposal.
                    </P>
                    <HD SOURCE="HD2">C. Detailed Economic Analysis</HD>
                    <HD SOURCE="HD3">1. Proposed Hospice Payment Update for FY 2027</HD>
                    <P>The FY 2027 hospice payment impacts appear in Table 21. We tabulate the resulting payments according to the classifications (for example, provider type, geographic region, facility size) and compare the difference between current and future payments to determine the overall impact. The first column shows the breakdown of all hospices by provider type and control (non-profit, for-profit, government, other), facility location, and facility size. The second column shows the number of hospices in each of the categories in the first column. The third column shows the effect of using the FY 2027 updated wage index data with a 5 percent cap on wage index decreases. The aggregate impact of the change in column three is zero percent, due to the hospice wage index standardization factors. However, there are distributional effects of using the FY 2027 hospice wage index. The fourth column shows the effect of the hospice payment update percentage as mandated by section 1814(i)(1)(C) of the Act and is consistent for all providers. The hospice payment update percentage of 2.4 percent is based on the proposed 3.2 percent inpatient hospital market basket percentage increase reduced by a proposed 0.8 percentage point productivity adjustment. The fifth column shows the total effect of the updated wage data and the hospice payment update percentage on FY 2027 hospice payments. As illustrated in Table 21, the combined effects vary by specific types of providers and by location. We note that simulated payments are based on utilization in FY 2025 as seen on Medicare hospice claims (accessed from the Chronic Conditions Warehouse (CCW) on January 15, 2026) and only include payments related to the level of care and do not include payments related to the service intensity add-on.</P>
                    <P>As illustrated in Table 21, the combined effects vary by specific types of providers and by location.</P>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17376"/>
                        <GID>EP06AP26.022</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17377"/>
                        <GID>EP06AP26.023</GID>
                    </GPH>
                    <PRTPAGE P="17378"/>
                    <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                    <HD SOURCE="HD2">D. Regulatory Review Cost Estimation</HD>
                    <P>If regulations impose administrative costs on private entities, such as the time needed to read and interpret this proposed rule, we should estimate the cost associated with the regulatory review. Due to the uncertainty involved with accurately quantifying the number of entities that will review the rule, we assume that the total number of unique commenters on last year's proposed rule will be the number of reviewers of this proposed rule. However, we acknowledge that this assumption may understate or overstate the costs of reviewing this proposed rule. It is possible that not all commenters reviewed last year's proposed rule in detail, and it is also possible that some reviewers chose not to comment on the proposed rule. Despite these limitations, we believe that the number of commenters on last year's proposed rule is a fair estimate of the number of reviewers of this proposed rule. We welcome any comments on the approach to estimating the number of entities that will review this proposed rule. We also recognize that different types of entities are in many cases affected by mutually exclusive sections of this proposed rule, and therefore for the purposes of our estimate we assume that each reviewer reads approximately 50 percent of the rule. We seek comments on this assumption.</P>
                    <P>
                        Using the May 2024 National median hourly wage rate (doubled for benefits and overhead) for medical and health service managers (Code 11-9111); we estimate that the cost of reviewing this rule is $113.42 per hour, including overhead and fringe benefits (
                        <E T="03">https://www.bls.gov/oes/home.htm</E>
                        ). Assuming an average reading speed we estimate that it would take approximately 1.76 hours for staff to review half of this proposed rule. For each hospice that reviews the rule, the estimated cost is $199.62 (1.76 hours × $113.42). Therefore, we estimate that the total cost of reviewing this regulation is approximately $12,576 ($199.62 × 63 reviewers; which is based on last year's comments received).
                    </P>
                    <HD SOURCE="HD2">E. Alternatives Considered</HD>
                    <HD SOURCE="HD3">1. Hospice Payment</HD>
                    <P>Since the hospice payment update percentage is determined based on statutory requirements, we did not consider alternatives to updating the hospice payment rates by the proposed hospice payment update percentage. The proposed 2.4 percent hospice payment update percentage for FY 2027 is based on a proposed 3.2 percent inpatient hospital market basket percentage increase for FY 2027, reduced by a proposed 0.8 percentage point productivity adjustment. Payment rates since FY 2002 have been updated according to section 1814(i)(1)(C)(ii)(VII) of the Act, which states that the update to the payment rates for subsequent years must be the market basket percentage increase for that fiscal year. Section 3401(g) of the Affordable Care Act also mandates that, starting with FY 2013 (and in subsequent years), the hospice payment update percentage will be annually reduced by changes in economy-wide productivity as specified in section 1886(b)(3)(B)(xi)(II) of the Act. For FY 2027, since the hospice payment update percentage is determined based on statutory requirements at section 1814(i)(1)(C) of the Act, we did not consider alternatives for the hospice payment update percentage.</P>
                    <HD SOURCE="HD3">2. Hospice Election Statement Addendum</HD>
                    <P>An alternative to this proposal would be to not make the election statement mandatory but rather keep the existing policy where the addendum is only required when requested by the beneficiary, their representative, non-hospice providers or the Medicare contractors. However, as described in Section III.C. of this proposed rule, the intent of the election statement addendum is to increase coverage transparency for those seeking to elect the benefit. We believe that only requiring the provision of this addendum when requested does not fulfill this intent and that all beneficiaries deciding to elect hospice care in lieu of curative care should have all the information they need to make informed consent to elect. We also stated our concerns that the continued and increasing non-hospice spending during a hospice election may signal that beneficiaries are not being made aware of hospice coverage responsibility and this may result in increased beneficiary cost sharing and fragmented care which is counter to the comprehensive and holistic nature of hospice care.</P>
                    <HD SOURCE="HD3">3. Quality Reporting Program</HD>
                    <P>CMS considered proposing an icon that would indicate if a hospice does not meet the submission requirements for HOPE, CAHPS, and claims. However, since claims are required for payment, there is high compliance, and, as many hospices are exempt from CAHPS due to size limitations, CAHPS submissions would be excluded for a large number of hospices so both CAHPS and claims were omitted. CMS also considered proposing an icon that would indicate if a hospice has met the submission requirements, however CMS is trying to induce the non-submitting hospices to change behavior and believe a negative icon will be more effective than a positive icon. Additionally, creating an positive icon would also cause, at times, hospices with poor quality indicators to receive this icon and possibly give mixed messages to the consumer as to whether the hospice provides good quality of care.</P>
                    <P>
                        CMS considered proposing a star rating, similar to those seen in other care settings on the 
                        <E T="03">Medicare.gov</E>
                         Compare Tool. However, this change would require the need for more public feedback and additional analyses to create a star rating that would accurately reflect the care a hospice is providing. There was also a desire to not add something to the Compare Tool that may interfere with the changes that may be made by the Hospice Special Focus Program (SFP).
                    </P>
                    <HD SOURCE="HD2">F. Accounting Statement and Table</HD>
                    <P>
                        Consistent with OMB Circular A-4 (available at 
                        <E T="03">https://www.whitehouse.gov/wp-content/uploads/2025/08/CircularA-4.pdf</E>
                        ), we have prepared an accounting statement in Table 22 showing the classification of the expenditures associated with the provisions of this proposed rule. Table 22 provides our best estimate of the possible changes in Medicare payments under the hospice benefit as a result of the policies in this proposed rule. This estimate is based on the data for 6,642 hospices in our impact analysis file, which was constructed using FY 2025 claims (accessed from the CCW on January 15, 2026). All expenditures are classified as transfers to hospices.
                    </P>
                    <GPH SPAN="3" DEEP="251">
                        <PRTPAGE P="17379"/>
                        <GID>EP06AP26.024</GID>
                    </GPH>
                    <HD SOURCE="HD2">G. Regulatory Flexibility Act (RFA)</HD>
                    <P>
                        The RFA requires agencies to analyze options for regulatory relief of small entities if a rule has a significant impact on a substantial number of small entities. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small jurisdictions. We consider all hospices as small entities as that term is used in the RFA. The North American Industry Classification System (NAICS) was adopted in 1997 and is the current standard used by the Federal statistical agencies related to the U.S. business economy. There is no NAICS code specific to hospice services. Therefore, we utilized the NAICS U.S. industry title “Home Health Care Services” and corresponding NAICS code 621610 in determining impacts for small entities. The NAICS code 621610 has a size standard of $19 million.
                        <SU>22</SU>
                        <FTREF/>
                         Table 23 shows the number of firms, revenue, and estimated impact per home health care service category. Table 24 shows the number of nonemployer establishments, total, and average revenue per nonemployer establishment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">https://www.sba.gov/sites/sbagov/files/2023-03/Table%20of%20Size%20Standards_Effective%20March%2017%2C%202023%20%281%29%20%281%29_0.pdf.</E>
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="264">
                        <PRTPAGE P="17380"/>
                        <GID>EP06AP26.025</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="235">
                        <GID>EP06AP26.026</GID>
                    </GPH>
                    <P>
                        The Department of Health and Human Services' practice in interpreting the RFA is to consider effects economically “significant” only if greater than 5 percent of providers reach a threshold of 3 to 5 percent or more of total revenue or total costs. The majority of hospice visits are Medicare paid visits, and therefore the majority of hospice agency revenue consists of Medicare payments. Based on our analysis, we conclude that the policies proposed in this rule would result in an estimated total impact of 3 to 5 percent or more on Medicare revenue for greater than 5 percent of hospices. Therefore, the Secretary has determined that this hospice proposed rule would have significant economic impact resulting in a net increase in positive revenue on a substantial number of small entities. We estimate that the net impact of the policies in this rule is 2.4 percent or approximately $785 million in increased revenue to hospices in FY 2027. The 2.4 percent increase in expenditures when comparing FY 2026 payments to estimated FY 2027 payments is reflected in the last column of the first row in Table 21 and is driven solely by the impact of the proposed hospice payment update percentage reflected in the fourth column of the impact table. In addition, hospices with less than 3,500 RHC days will experience a higher estimated increase (2.6 percent), compared to hospices with greater than 20,000 RHC days (2.4 percent) due to the proposed updated wage index. We estimate that in FY 2027, hospices in urban areas would experience, on average, a 2.3 percent increase in 
                        <PRTPAGE P="17381"/>
                        estimated payments compared to FY 2026; while hospices in rural areas would experience, on average, a 3.0 percent increase in estimated payments compared to FY 2026. Hospices providing services in the Outlying region would experience the largest estimated increases in payments of 3.6 percent. Hospices serving patients in the West South Central region will experience, on average, the lowest estimated increase of 2.0 percent in FY 2027 payments. Further detail by hospice type and location is presented in Table 21. The statement of need for the various proposed policies in this rule are discussed in section VII.A. of the RIA. Additionally, the alternatives considered for the various proposed policies in this rule are discussed in section VII.E. of the RIA. We considered potential alternatives for the policies proposed in this rule, including the hospice payment update percentage and the hospice election statement addendum. Because the hospice payment update percentage is established annually in accordance with the statutory requirements of section 1814(i)(1)(C) of the Act, we did not evaluate alternative approaches for this provision. Similarly, we did not consider alternatives for the regulatory text revisions, as these changes either conform to policies already codified in regulation or are mandated by the Consolidated Appropriations Act, 2026. For the hospice election statement addendum, the proposed policy is expected to generate savings for all hospices, including small entities. We also considered an alternative under which the hospice statement addendum would be optional rather than mandatory. However, this approach would likely increase costs for hospices (we consider all hospices small entities) and would not fulfill the intended objective, as described in Section III.C. of this proposed rule, of enhancing transparency for beneficiaries seeking to elect the hospice benefit. We are soliciting comments on our proposed cost analysis.
                    </P>
                    <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 603 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of an MSA and has fewer than 100 beds. As this rule will only affect hospices, the Secretary has determined that this rule will not have a significant impact on the operations of a substantial number of small rural hospitals (see Table 23).</P>
                    <HD SOURCE="HD2">H. Unfunded Mandates Reform Act (UMRA)</HD>
                    <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. In 2025, that threshold is approximately $193 million. This rule will not have an unfunded effect on state, local, or tribal governments, in the aggregate, or on the private sector that exceeds this threshold in any 1 year.</P>
                    <HD SOURCE="HD2">I. Federalism</HD>
                    <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. We have reviewed this rule under these criteria of Executive Order 13132 and have determined that it will not impose substantial direct costs on State or local governments.</P>
                    <HD SOURCE="HD2">J. E.O. 14192, “Unleashing Prosperity Through Deregulation”</HD>
                    <P>Executive Order 14192, entitled “Unleashing Prosperity Through Deregulation” was issued on January 31, 2025, and requires that “any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations.” Therefore, this proposed rule, if finalized as proposed, is expected to be an E.O. 14192 deregulatory action. We estimate that this proposed rule would generate −$16.98 million in annualized cost savings at a 7 percent discount rate, discounted to relative to 2024, over a perpetual time horizon.</P>
                    <HD SOURCE="HD2">K. Conclusion</HD>
                    <P>We estimate that aggregate payments to hospices in FY 2027 will increase by $785 million as a result of the 2.4 percent proposed hospice payment update, compared to payments in FY 2026. We estimate that in FY 2027, hospices in urban areas would experience, on average, a 2.3 percent increase in estimated payments compared to FY 2026; while hospices in rural areas would experience, on average, a 3.0 percent increase in estimated payments compared to FY 2026. Hospices providing services in the Outlying region would experience the largest estimated increases in payments of 3.6 percent. Hospices serving patients in the West South Central region will experience, on average, the lowest estimated increase of 2.0 percent in FY 2027 payments.</P>
                    <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget.</P>
                    <P>Mehmet Oz Administrator of the Centers for Medicare &amp; Medicaid Services, approved this document on March 30, 2026.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 42 CFR Part 418</HD>
                        <P>Health facilities, Hospice care, Medicare, Reporting and recordkeeping requirements. </P>
                    </LSTSUB>
                    <P>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services proposes to amend 42 CFR part 418 as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 418—HOSPICE CARE</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 418 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 42 U.S.C. 1302 and 1395hh.</P>
                    </AUTH>
                    <AMDPAR>2. Section 418.22 is amended by revising paragraph (a)(4)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 418.22 </SECTNO>
                        <SUBJECT>Certification of terminal illness.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(4) * * *</P>
                        <P>
                            (ii) During a Public Health Emergency, as defined in § 400.200 of this chapter, or through December 31, 2027, whichever is later, if the face-to-face encounter conducted by a hospice physician or hospice nurse practitioner is for the sole purpose of hospice recertification, such encounter may occur via telecommunications technology and is considered an administrative expense. Telecommunications technology means the use of interactive multimedia communications equipment that includes, at a minimum, the use of audio and video equipment permitting two-way, real-time interactive communication between the patient and the distant site hospice physician or hospice nurse practitioner. For face-to-face encounters occurring on or after January 1, 2027, hospices must report any such encounters occurring via telecommunications technology on the claim, in accordance with guidance issued by CMS. Beginning January 31, 2026, telehealth may not be used for the face-to-face recertification encounter if any of the following conditions apply:
                            <PRTPAGE P="17382"/>
                        </P>
                        <P>(A) The hospice patient is located in an area subject to a hospice enrollment moratorium under section 1866(j)(7) of the Act;</P>
                        <P>(B) The patient is receiving care from a hospice provider that is subject to enhanced oversight pursuant to section 1866(j)(3) of the Act; or</P>
                        <P>(C) The face-to-face encounter is conducted by a hospice physician or nurse practitioner who is not enrolled in Medicare under section 1866(j) and is not an opt-out physician or practitioner (as defined in section 1802(b)(6)(D) of the Act.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>3. Section 418.24 is amended by revising paragraphs (b)(6), (c) introductory text, (c)(9) and (10), and (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 418.24</SECTNO>
                        <SUBJECT> Election of hospice care.</SUBJECT>
                        <P>(b) * * *</P>
                        <P>(6) For Hospice elections beginning on or after October 1, 2026, the hospice must provide the individual (or representative) an election statement addendum, as set forth in paragraphs (c) and (d) of this section, which includes any conditions, items, services, and drugs the hospice has determined to be unrelated to the individual's terminal illness and related conditions and would not be covered by the hospice.</P>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Content of hospice election statement addendum.</E>
                             For hospice elections beginning on or after October 1, 2026, the hospice must provide the individual (or representative) an election statement addendum. The election statement addendum (and its updates) must include the following:
                        </P>
                        <STARS/>
                        <P>(9) Name and signature of the individual (or representative) and date signed, along with a statement that signing this addendum (and its updates) is only acknowledgement of receipt of the addendum and not the individual's (or representative's) agreement with the hospice's determinations. If the individual (or representative) refuses to sign the addendum, the hospice must document on the addendum the reason the addendum was not signed and the addendum would become part of the patient's medical record. The addendum must also be available for non-hospice providers and Medicare contractors, although non-hospice providers and Medicare contractors are not required to sign the addendum.</P>
                        <P>(10) Date the hospice furnished the addendum to the individual (or representative).</P>
                        <P>
                            (d) 
                            <E T="03">Timeframes for the hospice election statement addendum.</E>
                             (1) For hospice elections beginning on or after October 1, 2026, the hospice must provide the individual (or representative) an election statement addendum, in writing, as set forth in paragraph (c) of this section, at the time of the hospice election (that is, within the first 5 days of the effective date of the hospice election). The hospice must also file this information with the election statement, as set forth in paragraphs (a) and (b) of this section, to be available for the individual (or representative), non-hospice providers, and Medicare contractors.
                        </P>
                        <P>(2) If there are any changes to the plan of care during the course of hospice care that impact the addendum determinations, the hospice must update the addendum, within 3 days, with the contents described in paragraph (c) of this section, and provide these updates, in writing, to the individual (or representative), as well as update the addendum on file in order to communicate these changes to the individual (or representative), non-hospice providers, and Medicare contractors.</P>
                        <P>(3) If the individual dies, revokes, or is discharged within the required timeframe for providing the addendum (and its updates) (as outlined in paragraphs (d)(1) and (2) of this section), and before the hospice has provided the addendum (and its updates), the addendum would not be required to be provided, in writing, to the individual (or representative). The hospice must note the reason the addendum (and its updates) was not completed and/or provided, in writing, to the individual (or representative) and this note would become part of the patient's medical record. If completed, the hospice must still file the addendum (and its updates) with the election statement, as set forth in paragraphs (a) and (b) of this section, to be available for the individual (or representative), non-hospice providers, and Medicare contractors.</P>
                        <P>(4) If the individual dies, revokes, or is discharged prior to signing the addendum (or its updates) (as outlined in paragraphs (d)(1) and (2) with the required contents described in paragraph (c) of this section), the addendum would not be required to be signed in order for the hospice to receive payment. The hospice must note (on the addendum itself) the reason the addendum (and any updates) was not signed and the addendum would become part of the patient's medical record.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>4. Section 418.26 is amended by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 418.26 </SECTNO>
                        <SUBJECT>Discharge from hospice care.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Discharge order.</E>
                             Prior to discharging a patient for any reason listed in paragraph (a) of this section, the hospice must obtain a written physician's discharge order from the hospice medical director (or physician designee, as defined at § 418.3) or physician member of the interdisciplinary group. If a patient has an attending physician involved in his or her care, this physician should be consulted before discharge and his or her review and decision included in the discharge note.
                        </P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 418.309 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>5. Section 418.309 is amended in paragraphs (a)(1) and (2) by removing “2033” and adding in its place “2035”.</AMDPAR>
                    <SIG>
                        <NAME>Robert F. Kennedy, Jr.,</NAME>
                        <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-06604 Filed 4-2-26; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>65</NO>
    <DATE>Monday, April 6, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="17383"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY> Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <HRULE/>
            <CFR>42 CFR Parts 422 and 423</CFR>
            <TITLE>Medicare Program; Contract Year 2027 and Certain Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="17384"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                    <CFR>42 CFR Parts 422 and 423</CFR>
                    <DEPDOC>[CMS-4208-F3 and CMS-4212-F]</DEPDOC>
                    <RIN>RIN 0938-AV40 and 0938-AV63</RIN>
                    <SUBJECT>Medicare Program; Contract Year 2027 and Certain Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), Department of Health and Human Services (HHS).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This final rule revises the Medicare Advantage (Part C), Medicare Prescription Drug Benefit (Part D), and Medicare cost plan regulations to implement changes related to Star Ratings, marketing and communications, drug coverage, enrollment processes, special needs plans, and other programmatic areas.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P/>
                        <P>
                            <E T="03">Effective date:</E>
                             These regulations are effective June 1, 2026.
                        </P>
                        <P>
                            <E T="03">Applicability date:</E>
                             These regulations are applicable to coverage beginning January 1, 2027.
                        </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <FP SOURCE="FP-1">Kristy Nishimoto, (206) 615-2367—General Questions and Beneficiary Enrollment Issues.</FP>
                        <FP SOURCE="FP-1">Naseem Tarmohamed, (410) 786-0814—Part C and Cost Plan Issues.</FP>
                        <FP SOURCE="FP-1">Lucia Patrone, (410) 786-8621—Part D Issues.</FP>
                        <FP SOURCE="FP-1">Alissa Gross, (410) 786-1120—Parts C and D Payment Issues.</FP>
                        <FP SOURCE="FP-1">Sara Klotz, (410) 786-1984—D-SNP Issues.</FP>
                        <FP SOURCE="FP-1">Beckie Peyton, (410) 786-1572—Manufacturer Discount Program Issues.</FP>
                        <FP SOURCE="FP-1">
                            <E T="03">PartCandDStarRatings@cms.hhs.gov</E>
                            —Parts C and D Star Ratings Issues.
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">CMMI_MAStrategy@cms.hhs.gov</E>
                            —RFI on Future Directions in Medicare Advantage
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">CPI_PartC&amp;D_RegIssues@cms.hhs.gov</E>
                            —Part D Program Integrity Issues
                        </FP>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">I. Executive Summary</HD>
                    <HD SOURCE="HD2">A. Purpose</HD>
                    <P>The primary purpose of this rule is to amend the regulations for the Medicare Advantage (Part C) program, Medicare Prescription Drug Benefit (Part D) program, and Medicare cost plan program. This rule includes a number of changes that would improve these programs for contract year 2027 as well as codify existing subregulatory guidance.</P>
                    <P>We note that, as with previous rules, the new marketing and communications policies in this rule are applicable for all contract year 2027 marketing and communications, beginning October 1, 2026.</P>
                    <HD SOURCE="HD2">B. Summary of the Key Provisions</HD>
                    <HD SOURCE="HD3">1. Medicare Part D Redesign</HD>
                    <P>We are implementing the changes made to the Part D benefit design and the payment obligations of enrollees, Part D plan sponsors, manufacturers, and CMS by section 11201 of the Inflation Reduction Act of 2022 (IRA) (Pub. L. 117-169).</P>
                    <P>We are codifying the statutory changes to the phases of the Part D benefit made by the IRA related to the deductible, the initial coverage limit, the coverage gap, the annual out-of-pocket threshold, and alternative prescription drug coverage options. In alignment with these changes to the Part D benefit, we are also codifying technical and conforming changes to our specialty tier regulations. We are codifying additional structural and operational statutory changes to the Part D benefit design, including making changes to the types of payments that count as True Out-Of-Pocket costs (TrOOP), establishing a policy for how an enrollee's costs for drugs not subject to the Part D defined standard deductible count towards becoming eligible for manufacturer discounts under the Medicare Part D Manufacturer Discount Program (Manufacturer Discount Program), making updates to the methodology for reinsurance payments from us to Part D sponsors, and implementing the Selected Drug Subsidy, among others.</P>
                    <HD SOURCE="HD3">2. Coverage Gap Discount Program</HD>
                    <P>We are codifying the sunsetting of the Coverage Gap Discount Program and termination of all Coverage Gap Discount Program agreements as of January 1, 2025, in alignment with subsection (h) of section 1860D-14A of the Social Security Act (the Act), as added by section 11201 of the IRA. Specifically, we are revising § 423.2300 by adding paragraph (b) to establish applicability dates for the Coverage Gap Discount Program, revising § 423.2345 by adding paragraph (f) to terminate all Coverage Gap Discount Program agreements, and making conforming changes for clarity.</P>
                    <HD SOURCE="HD3">3. Manufacturer Discount Program</HD>
                    <P>We are codifying the Manufacturer Discount Program, established in section 1860D-14C of the Act, as added by section 11201 of the IRA. Under the Manufacturer Discount Program, which replaces the Coverage Gap Discount Program and began on January 1, 2025, manufacturers that enter into a Manufacturer Discount Program agreement are required to provide discounts on applicable drugs in both the initial and catastrophic coverage phases of the Part D benefit. Specifically, we are adding new subpart AA to part 423 to codify the Manufacturer Discount Program requirements and are making several conforming changes throughout part 423 to reflect the new program.</P>
                    <HD SOURCE="HD3">4. Updates to Star Ratings</HD>
                    <P>We have continued to identify enhancements to the Star Ratings program over time to increase the health and wellbeing of enrollees. In this final rule, we are finalizing changes to simplify and refocus the areas included in the Star Ratings, including changes to the measure set with the exception of the Diabetes Care—Eye Exam measure which will remain in the Star Ratings. We are also finalizing that we will not move forward with the implementation of the Health Equity Index (also called Excellent Health Outcomes for All) reward at §§ 422.166(f)(3) and 423.186(f)(3) and will continue to include the historical reward factor in the Star Ratings methodology at §§ 422.166(f)(1) and 423.186(f)(1). We appreciate commenters' suggestions on ways to further simplify and modify the Star Ratings program to further drive improved quality of care and reduce regulatory burden.</P>
                    <P>
                        The measure removals will apply (that is, data will be collected and performance measured) for the 2027 measurement period and the 2029 Star Ratings, except for the Call Center—Foreign Language Interpreter and TTY Availability (Part C and D) measures and the Statin Therapy for Patients with Cardiovascular Disease (Part C) measure, which will apply beginning with the 2028 Star Ratings. Not proceeding with the HEI reward and maintaining the historical reward factor, finalizing additional information about the data available to Medicare Advantage (MA) organizations and Part D sponsors during the plan preview periods before each Star Ratings release at §§ 422.166(h)(2) and 423.186(h)(2), and clarifying the process for measure 
                        <PRTPAGE P="17385"/>
                        removals at §§ 422.164(e)(2), 422.164(e)(3), 423.184(e)(2) and 423.184(e)(2), will be applicable upon the effective date of this final rule and apply beginning with the 2027 Star Ratings. We are also finalizing the technical clarification proposed in the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on December 10, 2024 (89 FR 99340) (hereinafter referred to as the “Contract Year 2026 proposed rule”) to provide details about how the enrollment-weighted measure score is calculated when a consumed or surviving contract is missing data for a measure; this provision will be applicable upon the effective date of this final rule and apply beginning with the 2027 Star Ratings.
                    </P>
                    <HD SOURCE="HD3">5. Provisions Related to Supplemental Benefits Being Finalized From the Contract Year 2026 Proposed Rule</HD>
                    <P>In the Contract Year 2026 proposed rule (89 FR 99340), we proposed several policies that were not finalized at that time, some of which are being finalized in this CY 2027 final rule. Specifically, we proposed to strengthen the administration of Special Supplemental Benefits for the Chronically Ill (SSBCI) by increasing transparency and clarifying eligibility requirements, including a requirement to make plan-developed SSBCI eligibility criteria publicly available; we are finalizing this provision as proposed. We also proposed to codify and clarify requirements for the administration of supplemental benefits through debit cards to promote transparency, consistency, and program integrity, and are finalizing this proposal with modifications, including not finalizing the proposed prohibition on marketing the dollar value of supplemental benefits. We are finalizing these proposals to support beneficiary access, informed choice, and appropriate administration of MA benefits.</P>
                    <HD SOURCE="HD2">C. Summary of Costs and Benefits</HD>
                    <BILCOD>BILLING CODE --P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17386"/>
                        <GID>ER06AP26.027</GID>
                    </GPH>
                    <PRTPAGE P="17387"/>
                    <BILCOD>BILLING CODE ????-??-C</BILCOD>
                    <HD SOURCE="HD2">D. Publication of the Proposed Rule, Responding to Public Comments, Finalization of Proposed Provisions, and Requests for Information</HD>
                    <P>
                        The proposed rule titled “Medicare Program; Contract Year 2027 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program,” appeared in the 
                        <E T="04">Federal Register</E>
                         on November 28, 2025 (90 FR 54894) (hereinafter referred to as the “Contract Year 2027 proposed rule”).
                    </P>
                    <P>In response to the Contract Year 2027 proposed rule, we received approximately 42,632 timely pieces of correspondence containing a variety of comments on the proposed rule and the requests for information (RFIs) contained within the rule. Summaries of the public comments within the scope of the proposed rule and our responses to those public comments are set forth in the various sections of this final rule under the appropriate heading. We note that some of the public comments were outside of the scope of the proposed rule and are not addressed in this final rule. We also note that we do not respond specifically to the comments pertaining to the RFIs, but we thank commenters for their feedback.</P>
                    <P>In this final rule, CMS is not finalizing the proposal to establish a special enrollment period for provider terminations and are not addressing comments received on this proposal. We acknowledge the broad interest related to this topic and will continue to consider the extent to which it may be appropriate to engage in future rulemaking in this area.</P>
                    <HD SOURCE="HD2">E. Conclusion</HD>
                    <P>Finally, we are clarifying and emphasizing our intent that if any provision of this rule is held to be invalid or unenforceable by its terms, or as applied to any person or circumstance, or stayed pending further agency action, it shall be severable from this rule and not affect the remainder thereof or the application of the provision to other persons not similarly situated or to other, dissimilar circumstances. Through this rule, we are codifying provisions that are intended to and will operate independently of each other, even if each serves the same general purpose or policy goal. Where a provision is necessarily dependent on another, the context generally makes that clear (such as by a cross-reference to apply the same standards or requirements).</P>
                    <HD SOURCE="HD1">II. Implementation of Certain Provisions of the Inflation Reduction Act of 2022 and the Substance Use-Disorder Prevention that Promotes Opioid Recovery and Treatment for Patients and Communities Act of 2018</HD>
                    <HD SOURCE="HD2">A. Medicare Part D Redesign</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Section 11201 of the Inflation Reduction Act of 2022 (IRA) made significant changes to the Part D benefit design that affect the structure of the Part D benefit and the payment obligations of enrollees, Part D plan sponsors, manufacturers, and CMS. Several of the changes made by section 11201 of the IRA took effect before the Contract Year 2027 proposed rule and other changes went into effect in 2026, as described later.</P>
                    <P>
                        Section 11201(f) of the IRA directed the Secretary to implement section 11201 of the IRA for 2024, 2025, and 2026 by program instruction or other forms of program guidance. On February 1, 2023, we released guidance outlining changes to the Part D benefit that were specific to Calendar Year (CY) 2024 in the CY 2024 Advance Notice and Rate Announcement.
                        <SU>1</SU>
                        <FTREF/>
                         In that guidance, we eliminated cost sharing for covered Part D drugs in the catastrophic phase of coverage, consistent with section 1860D-2(b)(4)(A)(i) of the Social Security Act (the Act), as amended by section 11201 of the IRA.
                        <SU>2</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/2024-advance-notice-pdf.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/2024-advance-notice-pdf.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        On April 1, 2024, we released the Final CY 2025 Part D Redesign Program Instructions.
                        <SU>3</SU>
                        <FTREF/>
                         In these program instructions, we implemented changes to the structure of the Part D benefit for CY 2025 made by section 11201 of the IRA. Section 11201 of the IRA added section 1860D-2(b)(4)(B)(i)(VII) of the Act to reduce the annual out-of-pocket (OOP) threshold to $2,000 for CY 2025 (to be annually increased by the annual percentage increase, as described in section 1860D-2(b)(6) of the Act). The IRA also amended section 1860D-2(b) of the Act to eliminate the coverage gap phase and added subsection (h) to section 1860D-14A of the Act to sunset the Coverage Gap Discount Program. The IRA added section 1860D-14C of the Act to establish the Manufacturer Discount Program.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/final-cy-2025-part-d-redesign-program-instructions.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        On April 7, 2025, we issued the Final CY 2026 Part D Redesign Program Instructions which described changes to the Part D benefit for CY 2026.
                        <SU>4</SU>
                        <FTREF/>
                         In these program instructions, we implemented further changes made by the IRA to the Part D benefit that go into effect in CY 2026, including certain changes to the Part D benefit that relate to the Medicare Drug Price Negotiation Program that also was established by the IRA. Beginning January 1, 2026, the maximum fair prices (MFPs) negotiated under the Medicare Drug Price Negotiation Program for the first cohort of selected drugs went into effect.
                        <SU>5</SU>
                        <FTREF/>
                         This program, as established in Part E of title XI of the Act, permits the Secretary to negotiate MFPs for certain high expenditure, single source drugs and biological products with participating manufacturers. The IRA made further changes to payment obligations in Part D related to selected drugs (as defined in section 1192(c) of the Act) during a price applicability period (as defined in section 1191(b)(2) of the Act).
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/final-cy-2026-part-d-redesign-program-instruction.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             For more information on the Medicare Drug Price Negotiation Program, please see: 
                            <E T="03">https://www.cms.gov/priorities/medicare-prescription-drug-affordability/overview/medicare-drug-price-negotiation-program.</E>
                        </P>
                    </FTNT>
                    <P>As described in the Final CY 2026 Part D Redesign Program Instructions, the defined standard Part D benefit for CY 2026 consists of the following phases and liabilities, with the CY 2026 changes reflected in bolded and italicized font:</P>
                    <P>
                        • 
                        <E T="03">Annual deductible.</E>
                         The enrollee pays 100 percent of their gross covered prescription drug costs (GCPDC) until the deductible is met.
                    </P>
                    <P>
                        • 
                        <E T="03">Initial coverage.</E>
                         The enrollee pays 25 percent coinsurance for covered Part D drugs. The Part D plan sponsor typically pays 65 percent of the costs of applicable drugs and selected drugs 
                        <SU>6</SU>
                        <FTREF/>
                         and 75 percent of the costs of all other covered Part D drugs. The manufacturer, through the Manufacturer Discount Program, typically covers 10 percent of the costs of applicable drugs. 
                        <E T="7462">In the initial coverage phase, we pay a 10 percent subsidy for selected drugs during a price applicability period.</E>
                         This phase ends when the enrollee has 
                        <PRTPAGE P="17388"/>
                        reached the annual OOP threshold of $2,100 for CY 2026.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             An applicable drug under the Manufacturer Discount Program is a Part D drug approved under a new drug application (NDA) under section 505(c) of the Federal Food, Drug, and Cosmetic Act (FFDCA) or, in the case of a biological product, licensed under section 351 of the Public Health Service Act (PHSA), but does not include a selected drug (as defined in section 1192(c) of the Act) dispensed during a price applicability period (as defined in section 1191(b)(2) of the Act) with respect to that drug. Selected drug has the meaning given such term in section 1192(c) of the Act and any applicable regulations and guidance.
                        </P>
                    </FTNT>
                    <P>
                        • 
                        <E T="03">Catastrophic.</E>
                         The enrollee pays no cost sharing for Part D drugs. Part D plan sponsors typically pay 60 percent of the costs of all covered Part D drugs. The manufacturer pays a discount, typically equal to 20 percent, for applicable drugs. Medicare pays a reinsurance subsidy equal to 20 percent of the costs of applicable drugs, and equivalent to 40 percent of the costs of all other covered Part D drugs that are not applicable drugs. In the catastrophic phase, Medicare provides 40 percent reinsurance for selected drugs during a price applicability period.
                    </P>
                    <P>As part of the overall restructuring of the Part D benefit, the IRA also made changes to the treatment of Advisory Committee on Immunization Practices (ACIP)-recommended adult vaccines and covered insulin products under Part D. Section 11401 of the IRA added section 1860D-2(b)(8) of the Act to require that, effective for plan years beginning on or after January 1, 2023, the Medicare Part D deductible shall not apply to, and there is no coinsurance or cost sharing for, an adult vaccine recommended by ACIP that is a covered Part D drug. Further, section 11406 of the IRA added section 1860D-2(b)(9) of the Act to require that, effective for plan years beginning on or after January 1, 2023, the Medicare Part D deductible shall not apply to covered insulin products, and the Part D cost-sharing amount for a one-month supply of each covered insulin product must not exceed the applicable cost-sharing amount for all enrollees. For CYs 2023, 2024, and 2025, this amount was $35.</P>
                    <P>
                        Sections 11401(e) and 11406(d) of the IRA directed the Secretary to implement the vaccine and insulin cost sharing changes for CYs 2023, 2024, and 2025 by program instruction or other forms of program guidance. In accordance with the law, we issued several memoranda via the Health Plan Management System (HPMS) that implemented sections 11401 and 11406 of the Act for CYs 2023, 2024, and 2025.
                        <SU>7</SU>
                        <FTREF/>
                         These provisions of the IRA were then codified in the “Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly)” final rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on April 15, 2025 (90 FR 15792) (CY 2026 final rule).
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             See the following HPMS memoranda: Contract Year 2023 Program Guidance Related to Inflation Reduction Act Changes to Part D Coverage of Vaccines and Insulin (and Revision); Final Contract Year (CY) 2024 Part D Bidding Instructions; and Final CY 2025 Part D Redesign Program Instructions.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/04/15/2025-06008/medicare-and-medicaid-programs-contract-year-2026-policy-and-technical-changes-to-the-medicare.</E>
                        </P>
                    </FTNT>
                    <P>In the CY 2026 final rule, consistent with section 1860D-2(b)(9)(B) of the Act, we finalized the requirement that, for CY 2026 and each subsequent year, the applicable cost-sharing amount for a covered insulin product is the lesser of: (1) $35, (2) an amount equal to 25 percent of the MFP established for the covered insulin product in accordance with Part E of title XI of the Act; or (3) an amount equal to 25 percent of the negotiated price, as defined in § 423.100, of the covered insulin product under the Part D Prescription Drug Plan (PDP) or Medicare Advantage Prescription Drug (MA-PD) plan.</P>
                    <HD SOURCE="HD3">2. Redesigned Part D Benefit (§§ 423.100 and 423.104)</HD>
                    <P>We proposed to codify at §§ 423.100 and 423.104 changes to the Part D benefit made by the IRA related to the deductible, the initial coverage limit, the coverage gap, the annual out-of-pocket (OOP) threshold, and alternative prescription drug coverage options.</P>
                    <HD SOURCE="HD3">a. Deductible (§ 423.104(d)(1))</HD>
                    <P>
                        The IRA Part D benefit redesign does not change how the annual deductible for standard prescription drug coverage is calculated. However, as discussed previously, sections 11401 and 11406 of the IRA provide that, effective for plan years beginning on or after January 1, 2023, the Medicare Part D deductible shall not apply to ACIP-recommended adult vaccines or covered insulin products under Part D. We codified these changes in the CY 2026 final rule.
                        <SU>9</SU>
                        <FTREF/>
                         Specifically, the vaccine changes codified at § 423.120(g)(1) and the insulin changes codified at § 423.120(h)(1) state, respectively, that the Part D deductible does not apply with respect to ACIP-recommended adult vaccines and covered insulin products.
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/04/15/2025-06008/medicare-and-medicaid-programs-contract-year-2026-policy-and-technical-changes-to-the-medicare.</E>
                        </P>
                    </FTNT>
                    <P>In alignment with these changes, we proposed to revise the regulatory text at § 423.104(d)(1) by adding language to state there, too, that the deductible does not apply to ACIP-recommended adult vaccines or covered insulin products, as defined in § 423.100.</P>
                    <HD SOURCE="HD3">b. Initial Coverage Limit (§§ 423.104(d)(2) and 423.104(d)(3))</HD>
                    <P>Section 11201 of the IRA amended section 1860D-2(b)(3)(A) of the Act to specify that the initial coverage limit only applies for years preceding CY 2025. Prior to this statutory change, once an enrollee met their deductible, they would enter the initial coverage phase, which would extend until the enrollee's gross covered prescription drug costs, as defined in § 423.100, reached the initial coverage limit. At that point the enrollee would enter the coverage gap phase. The enrollee would remain in the coverage gap phase until the enrollee's incurred costs, as defined in § 423.100, met the OOP threshold, at which point the enrollee would enter the catastrophic phase.</P>
                    <P>By eliminating the initial coverage limit beginning in CY 2025, the IRA eliminated the coverage gap phase, resulting in a three-phase benefit for Part D prescription drug coverage which includes the deductible phase, the initial coverage phase, and the catastrophic phase. As such, as of CY 2025, there is no longer an initial coverage limit and the initial coverage phase extends to the annual OOP threshold, at which point the catastrophic phase begins. Once an enrollee enters the catastrophic phase, they pay no cost sharing for Part D drugs.</P>
                    <P>As a result of these changes, we proposed to revise § 423.104(d)(2) and (d)(3) to reflect the elimination of the initial coverage limit beginning in CY 2025. Specifically, we proposed to revise the section heading at § 423.104(d)(2) by removing “the initial coverage limit” and replacing it with “prescription drug plans” to accurately reflect the new benefit structure in which there is no initial coverage limit beginning in CY 2025 and to ensure consistency with the statutory changes made by the IRA. This heading language change is intended to accurately encompass the regulations included in the paragraphs that are subordinate to § 423.104(d)(2), which include regulations related to tiered copayments and the specialty tier.</P>
                    <P>
                        We also proposed to revise § 423.104(d)(2)(i), which currently specifies that coinsurance for actual costs for covered Part D drugs above the annual deductible applies up to the initial coverage limit. To align our regulations with current statute and the redesigned Part D benefit structure where beneficiaries move directly from the initial coverage phase to the catastrophic phase once they reach the OOP threshold, we proposed to revise this language to specify that for each year preceding 2025, this coinsurance applies up to the initial coverage limit and, for 2025 and each subsequent year, this coinsurance applies up to the 
                        <PRTPAGE P="17389"/>
                        annual OOP threshold specified in § 423.104(d)(5)(iii).
                    </P>
                    <P>We also proposed to revise § 423.104(d)(3), which specifies how the initial coverage limit is determined. We first proposed to remove the references in § 423.104(d)(3) to paragraphs (d)(4) and (d)(5) of this section because those paragraphs refer to regulations related to cost sharing in the coverage gap and the out-of-pocket threshold, which do not affect how the initial coverage limit is determined. We proposed to revise § 423.104(d)(3)(ii) to specify that the methodology for increasing the initial coverage limit was in effect from 2007 to 2024. We also proposed to add new § 423.104(d)(3)(iii) to state that, for 2025 and each subsequent year, there is no initial coverage limit.</P>
                    <P>Finally, we proposed two conforming changes at § 423.128(e), which refers to the explanation of benefits that a Part D sponsor must furnish directly to enrollees. First, we proposed to revise § 423.128(e)(3)(ii) which states that Part D sponsors are required to include information on the cumulative, year-to-date total amount of benefits provided in relation to the initial coverage limit for the current year in the explanation of benefits provided to enrollees. In alignment with section 1860D-4(a)(4)(B)(i) of the Act, as amended by section 11201 of the IRA, we proposed to revise § 423.128(e)(3)(ii) by adding language to specify that the requirement to include information about the initial coverage limit was only in effect for years preceding 2025. Second, we proposed to revise § 423.128(e)(7) which states that the explanation of benefits must be provided no later than the end of the month following any month when prescription drug benefits are provided under this part, including the covered Part D spending between the initial coverage limit described in § 423.104(d)(3) and the out-of-pocket threshold described in § 423.104(d)(5)(iii). In alignment with the elimination of the initial coverage limit and coverage gap phase beginning in CY 2025, we proposed to add language to specify that the covered Part D spending between the initial coverage limit and the out-of-pocket threshold requirement is only applicable for years preceding 2025.</P>
                    <P>Rather than striking the regulations that apply through CY 2024, we proposed to maintain these regulations, with the described revisions, for historical purposes and for any reconciliation activities related to benefit years prior to 2025.</P>
                    <HD SOURCE="HD3">c. Coverage Gap (§§ 423.100 and 423.104(d)(4))</HD>
                    <P>Section 11201 of the IRA eliminated the coverage gap phase of the Part D benefit by amending section 1860D-2(b) of the Act to eliminate the initial coverage limit beginning in CY 2025.</P>
                    <P>To align with these changes to the Part D benefit, we proposed to revise § 423.104(d)(4) by adding language to reflect that the coverage gap phase was eliminated. The proposed revision would state that the methodology for determining cost sharing in the coverage gap that is described in this section applies only for years preceding 2025. This proposed change aligns with our proposed revision to the definition of “coverage gap” in § 423.100 to specify that the coverage gap means the period in prescription drug coverage that occurs between the initial coverage limit and the OOP threshold during the years 2006 through 2024.</P>
                    <P>We proposed to revise § 423.104(d)(4)(iii), which describes the generic gap coinsurance percentage, by adding an end date to paragraph (C) of this section to state that the 25 percent generic gap coinsurance percentage only applied for years 2020 through 2024. This aligns with the IRA's elimination of the coverage gap phase in CY 2025. We also proposed to revise § 423.104(d)(4)(iv), which describes the applicable gap coinsurance percentage, by revising paragraph (E) to specify that the applicable gap coinsurance percentage for 2019 was 75 (not 80 percent) and to add an end date indicating that the 75 percent applies for years 2019 through 2024, and removing paragraph (F), which incorrectly stated that the applicable gap coinsurance percentage for 2020 and subsequent years was 75 percent. These changes align with changes made by the Bipartisan Budget Act (BBA) of 2018 and the IRA. Section 53116 of the BBA amended section 1860D-2(b)(2)(D)(ii) of the Act to specify that the applicable gap percentage for 2019 is 75 percent, not 80 percent, thus accelerating by 1 year a reduction in enrollee cost sharing in the coverage gap phase. We note that this revision to paragraph (E) is, in part, a technical correction to align our regulations with the statutory change made by the BBA, which was implemented in 2019. This revision does not change how the applicable gap percentage was calculated in the past, as these amounts were properly determined consistent with the statutory requirement. We additionally proposed to add a new paragraph at § 423.104(d)(4)(v) to specify that, for 2025 and each subsequent year, there is no coverage gap.</P>
                    <P>Finally, we proposed conforming changes to §§ 422.2267(e)(5)(ii)(B)(1) and 423.2267(e)(5)(ii)(A)(2) which state that information on prescription drug expenses, including information on the deductible, the initial coverage phase, coverage gap, and catastrophic coverage, is required to be included in the Summary of Benefits provided to prospective enrollees. Due to the elimination of the coverage gap in CY 2025, we proposed to revise §§ 422.2267(e)(5)(ii)(B)(1) and 423.2267(e)(5)(ii)(A)(2) by adding language to specify that the requirement to include information about the coverage gap was only in effect for years preceding 2025.</P>
                    <P>Even though the coverage gap phase was eliminated in CY 2025, we proposed to maintain these regulations, with the described revisions, for historical purposes and for any reconciliation activities related to benefit years prior to 2025.</P>
                    <HD SOURCE="HD3">d. Annual Out-of-Pocket Threshold (§ 423.104(d)(5))</HD>
                    <P>
                        Section 11201 of the IRA amended section 1860D-2(b)(4)(B)(i) of the Act to limit the annual OOP threshold for CY 2025 and each subsequent year. As amended, section 1860D-2(b)(4)(B)(i)(VII) of the Act specifies that the annual OOP threshold is $2,000 for CY 2025. For subsequent years, section 1860D-2(b)(4)(B)(i)(VIII) of the Act specifies that the annual OOP threshold will be increased by the annual percentage increase described in section 1860D-2(b)(6). Accordingly, as specified in the CY 2026 Rate Announcement, the annual OOP threshold for CY 2026 was determined to be $2,100.
                        <SU>10</SU>
                        <FTREF/>
                         This amount was calculated, consistent with section 1860D-2(b)(4)(B) of the Act, by multiplying the CY 2025 OOP threshold amount of $2,000 by the 2026 annual percentage increase and rounding to the nearest multiple of $50. Once an enrollee's incurred costs, as defined at § 423.100, exceed the annual OOP threshold, an enrollee will enter the catastrophic phase where there is no cost sharing for Part D drugs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/2026-announcement.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        As a result of these changes, we proposed to revise § 423.104(d)(5) to state the specific years for which certain aspects of this section apply and describe the new methodology for determining the annual OOP threshold, consistent with section 1860D-2(b)(4)(B)(i) of the Act.
                        <PRTPAGE P="17390"/>
                    </P>
                    <P>We proposed to revise § 423.104(d)(5)(i) to specify that, once an enrollee's incurred costs, as defined at § 423.100, exceed the annual OOP threshold described in paragraph (d)(5)(iii) of this section, they would have $0 cost sharing for 2024 and each subsequent year and, for each year preceding 2024, the cost-sharing structure currently outlined at paragraphs (d)(5)(i)(A) and (d)(5)(i)(B) of this section would apply. We also proposed to revise § 423.104(d)(5)(i)(A)(2) to specify that the methodology described in this section for determining an enrollee's copayment amount applies through 2023. These changes reflect the elimination of enrollee cost sharing for Part D drugs in the catastrophic phase beginning in CY 2024, consistent with section 1860D-2(b)(4)(A)(i) of the Act, as amended by section 11201 of the IRA.</P>
                    <P>We proposed to revise § 423.104(d)(5)(iii)(F) to add an end date to state that this paragraph describes how the annual OOP threshold was determined for years 2021 through 2024. We also proposed to add new § 423.104(d)(5)(iii)(G) to establish that for 2025, the annual OOP threshold was set at $2,000, consistent with section 1860D-2(b)(4)(B)(i)(VII) of the Act. Additionally, we proposed to add new § 423.104(d)(5)(iii)(H) to specify the methodology for determining the annual OOP threshold for 2026 and each subsequent year. Consistent with section 1860D-2(b)(4)(B)(i)(VIII) of the Act, we proposed that the annual OOP threshold for 2026 and each subsequent year would be the amount specified in this paragraph for the previous year, increased by the annual percentage increase specified in paragraph (d)(5)(iv) of this section, and rounded to the nearest $50.</P>
                    <HD SOURCE="HD3">e. Alternative Prescription Drug Coverage (§ 423.104(e)(5)) and Enhanced Alternative Coverage (§ 423.104(f)(1))</HD>
                    <P>Part D sponsors must provide their enrollees with qualified prescription drug coverage which, as defined at § 423.100, means coverage that consists of either: (1) standard prescription drug coverage or (2) alternative prescription drug coverage. Standard prescription drug coverage, as defined at § 423.100, means coverage of Part D drugs that meets the requirements of § 423.104(d) and includes two distinct types of coverage: (1) defined standard coverage and (2) actuarially equivalent (AE) standard coverage.</P>
                    <P>Prior to the implementation of the IRA, defined standard coverage consisted of coverage of covered Part D drugs subject to an annual deductible, 25 percent coinsurance for costs above the annual deductible but at or below an initial coverage limit, coinsurance that was equal to the costs of non-applicable and applicable drugs during the coverage gap multiplied by the gap coinsurance percentages, and catastrophic coverage with nominal cost sharing for the remainder of the coverage year once an enrollee's incurred costs, as defined in § 423.100, exceeded the annual OOP threshold. After the implementation of the IRA, defined standard coverage, as discussed in more detail in the introduction of this section of this final rule, now consists of an annual deductible, an initial coverage phase where the enrollee pays 25 percent coinsurance for covered Part D drugs until they reach the annual OOP threshold ($2,100 for CY 2026), and a catastrophic phase where the enrollee pays no cost sharing for Part D drugs. AE standard coverage, as defined at § 423.100, provides for cost sharing as described in § 423.104(d)(2)(i)(B) or cost sharing as described in § 423.104(d)(5)(ii), or both. In other words, under an AE plan, Part D sponsors modify certain benefit parameters, such as cost-sharing structures, while maintaining the same actuarial value. The changes the IRA made to the defined standard benefit are discussed in detail in the preceding sections of this final rule.</P>
                    <P>The IRA also, through section 11201 which amended section 1860D-2(c) of the Act, made changes to the requirements for alternative prescription drug coverage. Alternative prescription drug coverage, as defined in § 423.100, means coverage of Part D drugs, other than standard prescription drug coverage, that meets the requirements of § 423.104(e). Alternative prescription drug coverage includes two types of coverage: (1) basic alternative coverage and (2) enhanced alternative coverage. Both basic alternative and enhanced alternative coverage must provide access to negotiated prices, coverage of Part D drugs, and meet the requirements described in § 423.104(e).</P>
                    <P>Basic alternative coverage is alternative coverage that is actuarially equivalent to defined standard coverage, as determined through the processes and methods established under § 423.265(d)(2). Prior to the implementation of the IRA, Part D sponsors offering basic alternative coverage could, within the parameters for alternative prescription drug coverage as described in § 423.104(e), combine certain features to maintain an actuarial value of coverage equal to defined standard prescription drug coverage, such as: (1) reducing the deductible, (2) making changes in cost sharing in an actuarially equivalent manner to the 25 percent cost sharing above the deductible and below the initial coverage limit under defined standard coverage and in an actuarially equivalent manner to the gap coverage coinsurance during the coverage gap, or (3) modifying the initial coverage limit. With the changes made to the Part D benefit by the IRA, including the elimination of the initial coverage limit and the coverage gap, certain features that could be offered by basic alternative plans are no longer available. Thus, we proposed to revise our regulations at § 423.104(e) to align with these changes, as discussed in more detail later.</P>
                    <P>Enhanced alternative coverage is alternative coverage that includes both required basic prescription drug coverage and supplemental benefits, as described at § 423.104(f)(1)(ii). Prior to the implementation of the Part D benefit redesign provisions in the IRA, supplemental benefits included: the coverage of drugs that are specifically excluded from the definition of a Part D drug in § 423.100 under paragraph (2)(ii) and/or any one or more of the following changes that increase the actuarial value of benefits above the actuarial value of defined standard prescription drug coverage:</P>
                    <P>• Reduction (or elimination) of the defined standard deductible.</P>
                    <P>• Reduction of cost sharing in the initial coverage phase.</P>
                    <P>• Increase of the initial coverage limit threshold.</P>
                    <P>• Additional cost-sharing reduction in the coverage gap phase.</P>
                    <P>• Reduction (or elimination) of cost sharing in the catastrophic phase.</P>
                    <P>
                        As noted in the Final CY 2025 Part D Redesign Program Instructions, section 1860D-2(a)(2)(A)(i) of the Act does not include a reduction in the annual OOP threshold in its list of permissible supplemental benefits, and we have never interpreted such provision to allow for a reduction in the annual OOP threshold. Because the IRA established a defined annual OOP threshold of $2,000 for CY 2025, and an amount equal to the previous year's OOP threshold increased by the annual percentage increase for 2026 and subsequent years, and did not modify the list of permissible supplemental benefits in section 1860D-2(a)(2)(A)(i) of the Act to include a reduction in the annual OOP threshold, Part D sponsors may not lower the annual OOP threshold below the specified amount. Additionally, the IRA eliminated cost sharing in the catastrophic phase beginning in CY 2024 and eliminated the coverage gap phase and replaced the 
                        <PRTPAGE P="17391"/>
                        Coverage Gap Discount Program with the Manufacturer Discount Program beginning in CY 2025. Thus, only the following supplemental benefits remain as possible enhancement features: coverage of drugs that are specifically excluded from the definition of a Part D drug, and/or
                    </P>
                    <P>• Reduction (or elimination) of the defined standard deductible</P>
                    <P>• Reduction of cost sharing in the initial coverage phase.</P>
                    <P>Given these changes to alternative prescription drug coverage, we proposed to revise § 423.104(e)(5) to align our requirements for alternative prescription drug coverage with the changes made by the IRA. We proposed to revise § 423.104(f)(1) to align our requirements for enhanced alternative drug coverage with the changes made by the IRA.</P>
                    <P>We first proposed to revise § 423.104(e)(5) to establish a distinction between the requirements for alternative prescription drug coverage that are applicable for years preceding 2025 and requirements for 2025 and each subsequent year. Specifically, we proposed to add language that, for years preceding 2025, alternative prescription drug coverage is required to provide coverage that is designed to provide payment for costs incurred for covered Part D drugs that is equal to the initial coverage limit. We also proposed to add language stating that, for 2025 and each subsequent year, this coverage must be equal to the annual OOP threshold, consistent with section 1860D-2(c)(1)(C) of the Act. Similarly, we proposed to revise § 423.104(e)(5)(i) to specify that when calculating the required payment amount for costs incurred for covered Part D drugs, the amount the initial coverage limit exceeds the deductible should be used for years preceding 2025, and the amount the annual OOP threshold exceeds the deductible should be used for 2025 and each subsequent year. We proposed maintaining § 423.104(e)(5)(ii) without change; therefore, the amount calculated in § 423.104(e)(5)(i) would be multiplied by 100 percent minus the coinsurance percentage specified in paragraph (d)(2)(i) of this section to determine the required payment amount.</P>
                    <P>Finally, we proposed to revise § 423.104(f)(1) to specify that an increase in the initial coverage limit could be considered a supplemental benefit only for years preceding 2025. This change reflects the elimination of the initial coverage limit beginning in CY 2025. All other requirements for enhanced alternative coverage that are described in § 423.104(f) remain applicable under the redesigned Part D benefit. Therefore, we did not propose any additional changes to this section.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many comments were supportive of our proposals to codify the changes to the phases of the Part D benefit made by the IRA. We did not receive any comments opposed to our codification of these requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of our proposals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few comments expressed support for our proposed revision to the regulatory text at § 423.104(d)(1) to specify that the deductible does not apply to ACIP-recommended adult vaccines or covered insulin products. A commenter encouraged CMS to provide simple and clear guidance on immunization coverage to plans, their beneficiaries, as well as the range of providers who serve them.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of this proposal. We agree that clear guidance is important to support implementation of these requirements. We will continue to provide guidance to Part D plan sponsors, providers, and beneficiaries regarding coverage of ACIP-recommended adult vaccines as appropriate. We refer the commenter to 
                        <E T="03">Medicare.gov</E>
                        , the Medicare Learning Network Fact Sheet on Medicare Part D Vaccines, and Chapters 5 and 6 of the Medicare Prescription Drug Benefit Manual for some of our existing guidance on this topic.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             MLN Fact Sheet on Part D Vaccines: 
                            <E T="03">https://www.cms.gov/files/document/mln908764-medicare-part-d-vaccines.pdf;</E>
                             Chapter 5: 
                            <E T="03">https://www.cms.gov/files/document/chapter-5-benefits-and-beneficiary-protection-v92011.pdf;</E>
                             Chapter 6: 
                            <E T="03">https://www.cms.gov/medicare/prescription-drug-coverage/prescriptiondrugcovcontra/downloads/part-d-benefits-manual-chapter-6.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters who were supportive of our proposals to codify the changes to the phases of the Part D benefit also expressed concerns about potential unintended consequences of the redesigned Part D benefit. Commenters stated that the reallocation of financial risk under the redesigned Part D benefit creates incentives for plans to control costs through increased utilization management, increased usage of step therapy protocols, narrower formularies, restricted pharmacy networks, and reduced coverage for certain brand or specialty drugs.
                    </P>
                    <P>Several commenters emphasized that, without sufficient safeguards, these behaviors could undermine the intended affordability and access benefits of the redesigned Part D benefit. A few commenters highlighted the potential negative impacts these behaviors may have on high-cost and medically complex populations, including beneficiaries with end-stage renal disease (ESRD), hospitalized patients transitioning from inpatient to outpatient care, and low-income beneficiaries. A commenter noted that these behaviors may also increase administrative burden for hospital clinicians, thus delaying treatment initiation and complicating discharge planning and care coordination.</P>
                    <P>Due to these concerns, several commenters urged CMS to strengthen its oversight of Part D plans, particularly with respect to formulary design, utilization management practices, and appeals processes. A commenter also urged CMS to require minimum formulary protections for certain drugs and prohibit Part D plans from removing drugs mid-year in response to increased plan liability.</P>
                    <P>A few commenters requested that CMS monitor the impacts on access to drugs and evaluate whether costs are being shifted to beneficiaries. A couple of commenters emphasized the importance of monitoring both standalone prescription drug plans and Medicare Advantage prescription drug plans. A few commenters also requested that CMS increase transparency around formulary and evidentiary review findings so stakeholders can better understand how access is evolving under the redesigned Part D benefit.</P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of our proposals to codify the changes made by the IRA to the phases of the Part D benefit. We appreciate the commenters sharing their concerns regarding potential unintended consequences of the redesigned Part D benefit, including the possibility that changes in plan liability could influence formulary design, utilization management practices, and beneficiary access to prescription drugs. We agree that robust oversight and monitoring are essential to the successful implementation of the redesigned Part D benefit, particularly for medically complex beneficiaries and those transitioning across care settings. We will continue to monitor the implementation of the redesigned Part D benefit as part of our ongoing program oversight.
                    </P>
                    <P>
                        We emphasize that Part D plan sponsors remain subject to existing statutory and regulatory requirements regarding formulary design, utilization management, pharmacy access, coverage determinations, and appeals. We will continue to oversee plan compliance with these requirements and monitor plan behavior through our comprehensive clinical formulary review process, which includes 
                        <PRTPAGE P="17392"/>
                        evaluation of tier placement and utilization management restrictions and criteria.
                    </P>
                    <P>We note that there are several longstanding statutory and regulatory safeguards in place to protect beneficiary access to critical medications. Section 1860D-11(e)(2)(D)(i) of the Act and § 423.272(b)(2)(i) require that CMS not approve a bid from a Part D sponsor if the design of its plan and its benefits, including its formulary structure and utilization management program, are “likely to substantially discourage enrollment by certain Part D eligible individuals.” In addition, § 423.120(b) establishes requirements for Part D formularies, including the requirement at § 423.120(b)(2)(i) that formularies include at least two Part D drugs within each therapeutic category and class. Section 1860D-4(b)(3)(G) of the Act and § 423.120(b)(2)(v) further require Part D sponsors to include all covered Part D drugs in the classes and categories of clinical concern identified by the Secretary, with limited exceptions as described in § 423.120(b)(2)(vi) and Chapter 6, Section 30.2.5 of the Medicare Prescription Drug Benefit Manual. Finally, § 423.120(e) limits the circumstances under which a Part D sponsor may make negative formulary changes during a contract year.</P>
                    <P>We appreciate the commenters' recommendations regarding transparency and will consider appropriate opportunities to share additional information regarding the formulary review and oversight process in the future.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that we develop clear and simple beneficiary communications about the changes to the Part D benefit. The commenters stated that beneficiaries and their caregivers must understand how costs accrue over the plan year, what payments count towards the annual OOP threshold, how catastrophic coverage works, and what costs to expect across benefit phases. Another commenter recommended that CMS encourage plans to use mobile applications and digital tools for beneficiary education on the new benefit structure.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestions. We agree that beneficiary education and clear communication are critical to the successful implementation of the redesigned Part D benefit. We will continue to support the development of educational materials to help beneficiaries understand the redesigned Part D benefit. We encourage the commenters to refer beneficiaries to the Medicare &amp; You Handbook, which provides general information on Medicare benefits, costs, rights, and protections; the Evidence of Coverage document provided by their Part D plan, which provides details on what their plan covers, how much they will pay, how to file a complaint, and more; and Medicare Plan Finder on Medicare.gov which allows users to compare Medicare health and drug plans in their area and compare costs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS establish a formal mechanism for patients and patient advocacy organizations to communicate directly with CMS, including any barriers to getting prescribed medications when enrollees need them. Another commenter urged CMS to commit to ongoing provider and hospital engagement as part of a long-term monitoring and evaluation strategy for the Part D redesign. The commenter noted that hospitals and frontline clinicians are uniquely positioned to identify access barriers and unintended consequences as they emerge and that their input should be systematically incorporated into CMS oversight frameworks.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' recommendations. There are multiple avenues through which beneficiaries, providers, and other stakeholders may raise concerns regarding access to prescription drugs, including through the grievance, coverage determination, or appeals processes, consistent with the requirements outlined in 42 CFR part 423, subpart M. Beneficiaries may also submit inquiries, complaints, grievances, appeals, and requests for information to the Medicare Beneficiary Ombudsman and 1-800-MEDICARE. Additionally, we developed the Complaint Tracking Module (CTM) in the Health Plan Management System (HPMS) to track complaints received by CMS from beneficiaries, providers, and their representatives regarding specific plans. Complaints are recorded in the CTM and assigned to the appropriate plan and, as required under the contract provisions established at § 422.504(a)(15) and § 423.505(b)(22), plans are required to address and resolve the complaints received by CMS against them in the CTM. Plans must also adhere to the timelines to resolve complaints in compliance with § 422.125 and § 423.129. We will consider additional opportunities to engage with stakeholders as part of our ongoing oversight of the Part D program as appropriate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter who supported CMS's proposal to codify the Part D benefit changes also expressed concerns about the unintended consequences of the IRA's changes. The commenter stated that plans have experienced higher-than-anticipated costs due to changes in plan liability, higher utilization among beneficiaries reaching the out-of-pocket cap, and continued growth in the prescription drug pipeline. The commenter noted that if current utilization trends continue, there may be additional pressure on bids in CY 2027.
                    </P>
                    <P>The commenter expressed prior concerns related to premium increases resulting from the Part D benefit redesign. They noted that they appreciated CMS's voluntary Part D Premium Stabilization Demonstration but indicated that additional policy changes are needed to assist Part D plan sponsors in preserving the affordability historically associated with Part D plans. Specifically, the commenter recommended modifications to the RxHCC model, including incorporating Direct and Indirect Remuneration (DIR) into the model and using drug utilization to better account for variation in drug costs among beneficiaries.</P>
                    <P>The commenter also urged CMS to provide additional flexibility to Part D plans to manage costs by streamlining regulations and reducing administrative burdens.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges the commenter's concerns about balancing changes in plan liability under the Part D redesign with a need to preserve affordability for Part D enrollees. We will continue to monitor impacts of the redesigned Part D benefit and seek to identify opportunities to improve program efficiency and reduce unnecessary administrative burden. We appreciate the commenter's recommendations on streamlining regulations and reducing administrative burden and will consider this feedback in future rulemaking as appropriate. However, we note that changes to the RxHCC model are outside the scope of this rulemaking.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing these proposals as proposed.</P>
                    <HD SOURCE="HD3">3. Specialty Tier (§ 423.104)</HD>
                    <P>
                        Section 1860D-2(b)(2) of the Act established the parameters of the Part D program's defined standard benefit and allows for alternative benefit designs that are actuarially equivalent to the defined standard benefit, including the use of tiered formularies. Although not required, Part D sponsors are permitted to include a specialty tier in their plan design. A specialty tier, as defined in § 423.104(d)(2)(iv), is a formulary cost-
                        <PRTPAGE P="17393"/>
                        sharing tier dedicated to high-cost Part D drugs with ingredient costs for a 30-day equivalent supply (as described in paragraph (d)(2)(iv)(A)(2) of this section) that are greater than the specialty-tier cost threshold specified in paragraph (d)(2)(iv)(A) of this section. Consistent with § 423.104(d)(2)(iv)(D), Part D sponsors may maintain up to two specialty tiers.
                    </P>
                    <P>Use of one or two specialty tiers provides the opportunity for Part D sponsors to manage high-cost drugs apart from tiers that have less expensive drugs. Our policies for the specialty tier aim to strike the appropriate balance between plan flexibility and Part D enrollee access to drugs, consistent with our statutory authority.</P>
                    <P>As described further later, the implementation of the IRA has made it necessary for us to make changes to our current specialty-tier regulations related to adjusting the specialty-tier cost threshold and determining the maximum allowable cost sharing to align with the redesigned Part D benefit. In the Contract Year 2027 proposed rule, we proposed to codify technical and conforming changes to our specialty-tier regulations at § 423.104.</P>
                    <HD SOURCE="HD3">a. Technical Correction to the Specialty-Tier Cost Threshold Determination (§ 423.104(d)(2)(iv)(A)(4))</HD>
                    <P>We proposed a technical correction in § 423.104(d)(2)(iv)(A)(4), which describes how the specialty-tier cost threshold is determined for the plan year. The current regulation text incorrectly refers to paragraph (d)(2)(iii) for the cost threshold determination, but it should refer to the top one percent methodology for determining the specialty-tier cost threshold at paragraph (d)(2)(iv)(A)(3). We therefore proposed to correct this inadvertent technical error.</P>
                    <HD SOURCE="HD3">b. Limit on Specialty-Tier Cost Threshold Adjustment (§ 423.104(d)(2)(iv)(B))</HD>
                    <P>We annually calculate a minimum dollar-per-month threshold amount to determine which drugs are eligible, based on relative high cost, for inclusion on the specialty tier. This cost threshold is adjusted to maintain approximately 1 percent of Part D drugs as specialty-tier eligible. In the final rule titled “Medicare and Medicaid Programs; Contract Year 2022 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicaid Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly” (CY 2022 final rule), we codified at § 423.104(d)(2)(iv)(B) our methodology to increase the specialty-tier cost threshold as follows:</P>
                    <P>
                        (
                        <E T="03">1</E>
                        ) CMS increases the specialty-tier cost threshold for a plan year only if the amount determined in paragraph (d)(2)(iv)(A)(
                        <E T="03">3</E>
                        ) of this section for a plan year is at least 10 percent above the specialty tier cost threshold for the prior plan year.
                    </P>
                    <P>
                        (
                        <E T="03">2</E>
                        ) If an increase is made in accordance with this paragraph (d)(2)(iv)(B), CMS rounds the amount determined in paragraph (d)(2)(iv)(A)(
                        <E T="03">3</E>
                        ) of this section to the nearest $10, and the resulting dollar amount is the specialty-tier cost threshold for the plan year.
                    </P>
                    <P>Our current regulation only contemplates increasing the specialty-tier cost threshold and does not consider decreasing the threshold when market conditions might warrant such a change. Given the many changes made to the Part D benefit by the IRA, we believe that it may be necessary in future years to decrease the specialty-tier cost threshold due to reductions in Part D drug costs. In general, shifting market dynamics, such as increased utilization of lower cost generic drugs, could potentially lead to reductions in Part D drug costs. The Medicare Drug Price Negotiation Program, as established in Part E of title XI of the Act, which permits the Secretary to negotiate MFPs for certain high expenditure, single source drugs and biological products with participating manufacturers, could also lead to a future need for a downward adjustment. The MFPs for the first 10 selected drugs went into effect on January 1, 2026, with new MFPs taking effect and new drugs being selected for negotiation each subsequent year. Therefore, it is possible that as a result of general market dynamics and more high expenditure drugs being selected for negotiation and their negotiated MFPs taking effect, the methodology for determining the specialty-tier cost threshold, as described in § 423.104(d)(2)(iv)(A), may yield an amount that is at least 10 percent below the previous plan year's specialty-tier cost threshold.</P>
                    <P>Thus, we proposed to revise § 423.104(d)(2)(iv)(B)(1) and (2) by adding language to allow CMS to reduce the cost threshold under certain circumstances. Specifically, in paragraph (B)(1) of this section, we proposed to replace “increase” with “modifies” and add “or below” following “10 percent above.” In paragraph (B)(2), we proposed to replace “increase” with “modification.”</P>
                    <HD SOURCE="HD3">c. Specialty Tier Maximum Allowable Cost Sharing (§ 423.104(d)(2)(iv)(D))</HD>
                    <P>Each year, we set the maximum allowable cost sharing for the specialty tier based on the plan's deductible, in accordance with § 423.104(d)(2)(iv)(D). The intent of this policy is to ensure a plan's value is reflective of the defined standard benefit. The regulation limits a plan with the full defined standard deductible to a 25 percent coinsurance on its specialty tier but allows a plan that fully eliminates the deductible up to a 33 percent coinsurance on its specialty tier. Based on the pre-IRA benefit design, we determined that the 33 percent maximum coinsurance was mathematically equivalent to the effective coinsurance for a beneficiary who would have paid the defined standard deductible for any given year plus the 25 percent coinsurance in the initial coverage phase until their drug costs reached the initial coverage limit. In other words, prior to CY 2025, beneficiary OOP costs divided by total drug costs equaled a 33 percent effective coinsurance for the beneficiary regardless of the plan deductible, represented by the following equation:</P>
                    <GPH SPAN="3" DEEP="28">
                        <GID>ER06AP26.028</GID>
                    </GPH>
                    <P>To operationalize the concept of maximum allowable cost sharing for the specialty tier based on the plan's deductible, CMS, in the CY 2022 final rule, codified the following calculation at § 423.104(d)(2)(iv)(D)(3) to determine the deductible range that corresponded to each specialty-tier coinsurance percentage point from 25 percent through 33 percent. Thus, under the pre-IRA Part D benefit design, we used this equation for the calculation:</P>
                    <GPH SPAN="3" DEEP="26">
                        <PRTPAGE P="17394"/>
                        <GID>ER06AP26.029</GID>
                    </GPH>
                    <P>Consistent with the first equation, the numerator here represents beneficiary OOP costs while the denominator represents total drug costs, resulting in an effective coinsurance of 33 percent, to align with the defined standard benefit. This equation was then solved for the deductible, and each specialty-tier coinsurance percentage point was inserted, to calculate the maximum allowable deductible value corresponding to that coinsurance percentage.</P>
                    <P>
                        However, in CY 2025, under statutory changes made by the IRA, the ICL was eliminated and, as a result, the methodology codified at § 423.104(d)(2)(iv)(D)(3) was no longer valid. Therefore, in the Final CY 2025 Part D Redesign Program Instructions,
                        <SU>12</SU>
                        <FTREF/>
                         we established a new methodology to determine the specialty-tier coinsurance/deductible ranges to represent the effective coinsurance for a beneficiary under the redesigned Part D benefit. In the Final CY 2026 Part D Redesign Program Instructions,
                        <SU>13</SU>
                        <FTREF/>
                         we continued to use the methodology outlined in the Final CY 2025 Part D Redesign Program Instructions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/final-cy-2025-part-d-redesign-program-instructions.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/final-cy-2026-part-d-redesign-program-instruction.pdf.</E>
                        </P>
                    </FTNT>
                    <P>In accordance with the Final CY 2025 Part D Redesign Program Instructions, we proposed to codify this methodology for determining the specialty-tier coinsurance/deductible ranges to represent the effective coinsurance for a beneficiary under the Part D benefit. To ensure that a plan's value reflects the defined standard benefit, we proposed to codify a methodology similar to the methodology used to calculate the cost-sharing requirements in § 423.104(d)(2)(iv)(D). For Part D plans with the full deductible provided under the defined standard benefit, the coinsurance is 25 percent, consistent with the defined standard benefit. Using the CY 2025 defined standard benefit parameters of a $590 deductible, a $2,000 annual OOP threshold, and a 25 percent coinsurance after the deductible is met and before the annual OOP threshold is reached, the total drug costs can be calculated at $6,230. This results in an effective coinsurance of 32.1 percent. To ensure that coinsurance for the specialty tier remains in alignment with cost sharing under the defined standard benefit, we are retaining the 33 percent maximum coinsurance currently effective at § 423.104(d)(2)(iv)(D)(2).</P>
                    <P>We proposed to use, as in previous years, an effective coinsurance equation to calculate the deductible that corresponds to each specialty-tier coinsurance percentage point from 25 percent through 33 percent. Consistent with our decision to retain the 33 percent maximum coinsurance, we proposed to use 33 percent to calculate the deductible that corresponds to each specialty-tier coinsurance percentage point. This equation would continue to represent beneficiary OOP costs in the numerator divided by total drug costs in the denominator. The following equation illustrates how we would calculate the effective coinsurance for the Part D benefit for purposes of calculating specialty-tier cost-sharing percentages:</P>
                    <GPH SPAN="3" DEEP="41">
                        <GID>ER06AP26.030</GID>
                    </GPH>
                    <P>As with the previous methodology, the equation is solved for the deductible, and each maximum allowable specialty tier coinsurance value is inserted, to determine the maximum allowable deductible value corresponding to that coinsurance. For example, the results for CY 2026 are shown in Table 2.</P>
                    <GPH SPAN="3" DEEP="203">
                        <GID>ER06AP26.031</GID>
                    </GPH>
                    <PRTPAGE P="17395"/>
                    <P>Consistent with the approach taken for both CY 2025 and CY 2026 as detailed in the Final CY 2025 Part D Redesign Program Instructions, we proposed to codify this methodology for determining specialty-tier coinsurance/deductible ranges. Thus, we proposed to revise § 423.104(d)(2)(iv)(D)(3)(i) to describe how the maximum coinsurance percentage was determined for years preceding 2025. We also proposed to add new § 423.104 (d)(2)(iv)(D)(3)(ii) to describe the methodology for calculating the maximum coinsurance percentage for 2025 and each subsequent year.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments that were supportive of our proposal to allow for a decrease in the specialty-tier cost threshold when market conditions might warrant such a change.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters opposed our proposal to allow for a decrease in the specialty-tier cost threshold when market conditions might warrant such a change. These commenters stated that lowering the specialty-tier cost threshold would expand the number of drugs eligible for placement on the specialty tier and expose beneficiaries to higher cost sharing. Commenters expressed concern that this would move drugs from non-specialty tiers with fixed copayments or lower coinsurance into the specialty tier, resulting in increased and less predictable out-of-pocket (OOP) costs. A few commenters also noted that because tiering or cost-sharing exception requests may be denied for specialty-tier drugs, beneficiaries have no recourse to appeal their cost-sharing liability, even when the drug is needed for clinical reasons and expanding their specialty tier would exacerbate these issues.
                    </P>
                    <P>Some commenters asserted that this proposal would undermine the goals of the IRA's Part D redesign provisions and prevent beneficiaries from benefitting from the IRA's affordability protections. Some commenters further noted that Part D plans have increasingly shifted from fixed copayments to coinsurance in response to IRA-related changes, and they argued that allowing the specialty-tier cost threshold to decrease would exacerbate these trends rather than limit them.</P>
                    <P>Several commenters also raised concerns about beneficiary access to prescription drugs. A few commenters stated that higher specialty-tier cost sharing contributes to delayed initiation of therapy, treatment disruptions, and prescription abandonment, particularly for beneficiaries with serious or complex medical conditions who rely on specialty drugs as well as those living in long-term care settings. Additionally, some commenters expressed concern that decreasing the specialty-tier cost threshold would lead to increased usage of utilization management, including prior authorization and step therapy, further limiting access to medically appropriate therapies.</P>
                    <P>A few commenters raised concerns that lowering the specialty-tier cost threshold could also increase opportunities for vertically integrated Pharmacy Benefit Managers (PBMs) to inappropriately steer beneficiaries toward PBM-affiliated pharmacies or favor higher-cost drugs on their formularies. These commenters recommended anti-steering provisions, increased formulary oversight, and other guardrails.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' feedback on our proposal to allow for a decrease in the specialty-tier cost threshold. We do not agree that movement of drugs to the specialty tier will necessarily result in increased beneficiary cost sharing. Under § 423.104(d)(2)(iv)(D)(1) through (3), the maximum allowable cost sharing for drugs on the specialty tier is set between 25 percent and 33 percent. In contrast, drugs placed on non-preferred tiers may be subject to coinsurance rates that exceed these limits, up to 50 percent. Further, we do not agree that specialty-tier placement uniformly increases beneficiary out-of-pocket costs.
                    </P>
                    <P>As noted by many commentors, more plans are moving non-specialty drug tiers from a copayment to a coinsurance cost-sharing structure, so we do not agree that placement on the specialty tier will always result in a change from a fixed copayment amount to a coinsurance. Placement on the specialty tier may, in some cases, result in lower cost sharing than placement on other formulary tiers.</P>
                    <P>We also note that the specialty-tier cost threshold is established through a data-driven methodology that examines a year's worth of prescription drug event (PDE) data to determine the dollar amount associated with the top one percent of Part D drug claims. This methodology is intended to ensure that the specialty tier remains focused on the highest-cost drugs in the program. Historically, the dollar amount associated with the top one percent of claims has increased over time, and we do not anticipate that the specialty-tier cost threshold will decrease in the near term. However, we believe it is appropriate to maintain regulatory flexibility to account for future market changes, including those that may result from the increasing number of drugs subject to negotiation in the Medicare Drug Price Negotiation Program.</P>
                    <P>We acknowledge the commenters' concerns regarding affordability and access, including the interaction between specialty-tier placement, cost sharing, and utilization management requirements. As discussed earlier, Part D sponsors remain subject to existing requirements related to formulary design, utilization management, pharmacy access, and beneficiary protections. Given that the cost-sharing limits on the specialty tier are intended to align with the defined standard benefit, we do not consider placement on the specialty tier to be a cause for concern regarding access and affordability. In addition, the redesigned Part D benefit includes affordability protections, such as the reduced annual out-of-pocket threshold, which will mitigate beneficiary exposure to high prescription drug costs across the benefit.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters who opposed our proposal to allow for a decrease in the specialty-tier cost threshold urged CMS to establish clear guardrails before any downward adjustment is made in the future. These commenters stated that such guardrails should include a beneficiary impact analysis, advance notice, meaningful stakeholder input, and strengthened affordability protections so beneficiaries do not experience higher out-of-pocket costs. Another commenter recommended that CMS conduct research on the effects of our proposed regulatory change on patient out-of-pocket costs and health outcomes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestions. We remain committed to robust oversight and monitoring of Part D formularies and utilization management practices. If future evidence indicates that additional safeguards or refinements to our specialty-tier policies are warranted, we may consider such adjustments in future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter who supported our proposal to allow for a decrease in the specialty-tier cost threshold recommended that CMS establish clear guardrails to ensure that this bidirectional flexibility does not inadvertently enable routine mid-year tiering changes or create cost-sharing disruptions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their recommendation. We clarify that specialty-tier cost threshold adjustments are effective at the start of a contract year and should not result in mid-year formulary changes. All 
                        <PRTPAGE P="17396"/>
                        existing formulary change policies and protections remain in place. As stated previously, if future evidence indicates that additional safeguards or refinements to our specialty-tier policies are warranted, we may consider such adjustments in future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that we explain why we are retaining the 33 percent specialty-tier maximum allowable coinsurance when our calculations show a maximum allowable coinsurance percentage of 32 percent. The commenter noted that CMS reports that this calculation, using the CY 2025 values of $590 for the defined standard benefit deductible and $2,000 for the out-of-pocket limit, results in an effective coinsurance rate of 32.1 percent. The commenter also noted that the same calculation, using the CY 2026 values of $615 for the defined standard benefit deductible and $2,100 for the out-of-pocket limit, results in an effective coinsurance rate of 32.0 percent. By retaining the 33 percent maximum coinsurance percentage, the commenter stated that enrollees in Part D plans with deductibles below that of the defined standard benefit cost-sharing would be charged cost sharing that is above the effective coinsurance rate, thus, reducing access to covered Part D drugs and potentially leading to negative health outcomes. The commenter recommended that CMS set the maximum allowable coinsurance percentage for the specialty tier at 32 percent.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To maintain continuity in transitioning our specialty-tier calculation from the prior methodology to the updated methodology reflecting the redesigned Part D benefit, CMS opted to maintain consistency in the cost-sharing thresholds compared to the thresholds prior to redesign. CMS agrees with the commenter's calculations of effective coinsurance amount. When performing the annual calculation using updated benefit parameters, we note that the effective coinsurance amount calculated using the full deductible amount and 25 percent coinsurance results in a value that varies slightly from year to year. For CY 2025, the calculation resulted in an effective coinsurance of 32.10 percent compared to 32.04 percent for CY 2026. We note that similar magnitudes of variance existed in the calculation of this annual effective coinsurance even before the IRA's changes to the Part D benefit design went into effect. An alternative approach to the calculation could use this calculated value as the upper limit to the specialty tier coinsurance; however CMS opted to use a single value annually to maintain stability year-over-year. As such, the methodology laid out in this final rule relies on the effective coinsurance value of 33 percent as the basis for all calculations. We also note that this is a mathematical equivalence calculation, for a hypothetical beneficiary taking only specialty-tier drugs, and not intended to reflect actuarial equivalence.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter thanked CMS for the detailed illustrative example of how the maximum coinsurance percentage would be calculated, noting that it provides important clarity for plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their support.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing our specialty-tier proposals as proposed.</P>
                    <HD SOURCE="HD3">4. Changes in True Out-Of-Pocket (TrOOP) Costs (§§ 423.100 and 423.464)</HD>
                    <P>A beneficiary's progression through the Part D benefit phases is determined by the total amount of costs incurred by the beneficiary for covered Part D drugs in the plan year. This amount is also referred to as the beneficiary's accumulated TrOOP spending. Incurred costs are defined at section 1860D-2(b)(4)(C) of the Act and the statutory definition has been revised several times since the beginning of the Part D program.</P>
                    <P>As discussed in the Contract Year 2027 proposed rule, section 11201 of the IRA amended the definition of incurred costs to include, for CY 2025 and subsequent years, costs incurred that are reimbursed through insurance, a group health plan, or certain other third party payment arrangements, but not including the coverage provided by a prescription drug plan or an MA-PD plan that is basic prescription drug coverage or any payments by a manufacturer under the Manufacturer Discount Program.</P>
                    <P>Section 11201(f) of the IRA directed the Secretary to implement section 11201 of the IRA for 2024, 2025, and 2026 by program instruction or other forms of program guidance. In the Final CY 2025 Part D Redesign Program Instructions, we released guidance to implement the IRA's additions to section 1860D-2(b)(4)(C) of the Act. Specifically, we stated that supplemental Part D coverage provided by enhanced alternative Part D plans and other health insurance (OHI) will be counted as incurred costs and included in the calculation of TrOOP for CY 2025. This includes supplemental coverage provided by Employer Group Waiver Plans (EGWPs), plan reductions in cost sharing for enrolled beneficiaries, such as reductions by Medicare-Medicaid Plans and D-Special Needs Plans (SNPs), and Center for Medicare and Medicaid Innovation (CMMI) model benefits that reimburse costs for covered Part D drugs (unless stated otherwise in an applicable CMMI model's respective Request for Applications or model guidance).</P>
                    <P>We further stated in the Final CY 2025 Part D Redesign Program Instructions that under section 1860D-2(b)(4)(C)(iii)(II) of the Act, only amounts reimbursed by supplemental coverage will be newly included in the calculation of TrOOP. For enhanced alternative plans, plan liability is mapped to the defined standard benefit to distinguish between basic and supplemental benefits provided under the Part D sponsor. Because of this, if beneficiary cost sharing is greater than what it would have been under the defined standard benefit, a negative value is recorded on a Prescription Drug Event (PDE) record for the field representing the value of the supplemental coverage. Such negative values will be disregarded (that is, be treated as zero) when calculating TrOOP, because they do not represent reimbursement to the beneficiary.</P>
                    <P>Additionally, we noted that section 1860D-2(b)(4)(C)(iii)(II) of the Act states that reimbursements through “certain other third party payment arrangements” are to be included in the calculation of TrOOP. We did not identify any third-party payment arrangements in addition to those described in the preceding paragraphs that could be included in the calculation of TrOOP.</P>
                    <P>Further, we stated that, as required by section 1860D-2(b)(4)(C)(iii)(II) of the Act, any manufacturer payments made under the Manufacturer Discount Program, which was newly created under the IRA, do not count as incurred costs and are not included in the calculation of TrOOP in 2025.</P>
                    <P>In the Final CY 2026 Part D Redesign Program Instructions, we stated that certain policies described in the Final CY 2025 Part D Redesign Program Instructions, including the policy with respect to incurred costs, also applied in CY 2026.</P>
                    <P>
                        In the Contract Year 2027 proposed rule, we proposed to codify at § 423.100 the policies we established in the Final CY 2025 Part D Redesign Program Instructions for CY 2025 and applied via the Final CY 2026 Part D Redesign Program Instructions for CY 2026 with respect to the definition of incurred costs for 2025 and subsequent years, without modification. These policies are 
                        <PRTPAGE P="17397"/>
                        currently in effect for CY 2026. Specifically, we proposed to add a new subparagraph (3) to the definition of incurred costs at § 423.100 defining incurred costs for 2025 and subsequent years to include costs that are reimbursed through insurance, a group health plan, or certain other third party payment arrangements, but not including the coverage provided by a PDP or an MA-PD plan that is basic prescription drug coverage or any payments by a manufacturer under the Manufacturer Discount Program under section 1860D-14C of the Act. We also proposed to amend § 423.464(f)(2)(i)(C) to remove the exclusion of expenditures for covered Part D drugs made by insurance or otherwise, a group health plan, or other third party payment arrangements, including expenditures by plans offering other prescription drug coverage and replace it with an exclusion limited to expenditures for covered Part D drugs made by government-funded health programs or the coverage provided by a PDP or an MA-PD plan that is basic prescription drug coverage or any payments by a manufacturer under the Manufacturer Discount Program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters opposed CMS' proposal to codify the inclusion of supplemental coverage provided by enhanced alternative Part D plans in the calculation of TrOOP. Several commenters asserted that Congress's intent in amending the definition of “incurred costs” under section 1860D-2(b)(4)(C)(iii)(II) of the Act was to address the specific and unique situation of EGWP beneficiaries who faced higher out-of-pocket costs and longer stays in the coverage gap due to their supplemental coverage. These commenters asserted that if Congress intended to include supplemental coverage provided by Part D enhanced alternative plans in the definition of “incurred costs,” they would have done so explicitly. Several commenters stated that the use of the term “insurance” to describe costs that are included as incurred costs and the use of the phrase “coverage provided by a prescription drug plan or an MA-PD plan” to describe basic coverage that is not included as incurred costs illustrates Congress's intent that supplemental coverage provided by Part D plans should not be included in TrOOP because Congress typically uses the latter language rather than the term “insurance” to refer to costs incurred by Part D plans, including supplemental coverage. Commenters suggested that the best reading of the statutory text is that only “wrap-around” benefits should be added to the definition of incurred costs, and that the statute's reference to costs “reimbursed” through insurance implies a focus on costs covered through other insurance rather than costs covered directly by the Part D benefit. A commenter asserted that if Congress intended to include basic Part D coverage in the scope of “reimbursed by insurance,” the same logic should apply to enhanced alternative coverage, on the grounds that enhanced alternative coverage is merely a variant design of the same underlying Part D benefit structure.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their input. CMS disagrees that enhanced alternative supplemental benefits are not included in the calculation of TrOOP under section 1860D-2(b)(4)(C)(iii) of the Act. The statute does not draw a distinction between non-Part D commercial insurance and coverage under Part D when it uses the term “reimbursed through insurance' in this provision. By excluding “coverage provided by a prescription drug plan or an MA-PD plan that is basic prescription drug coverage” from the definition of costs “reimbursed through insurance,” the plain text of section 1860D-2(b)(4)(C)(iii)(II) indicates that drug coverage provided by Part D plans other than basic prescription drug coverage is included in the definition of costs “reimbursed through insurance.” If the provision only included EGWP supplemental coverage in the definition of costs “reimbursed through insurance,” the statutory text would have done so by explicitly including EGWP supplemental coverage in the definition of “costs reimbursed through insurance” and expanding the exclusion clause to apply to both basic prescription drug coverage and enhanced alternative supplemental coverage. However, the statute does not do so and instead enacted a broader provision for which the plain text requires any costs “reimbursed through insurance” be treated as incurred unless such costs constitute basic prescription drug coverage provided by a prescription drug plan or an MA-PD plan. We disagree with the assertion that if the statute were intended to exclude basic Part D coverage from the scope of “reimbursed through insurance,” the same logic must apply to enhanced alternative coverage, because the statute draws an explicit, meaningful distinction between basic and enhanced alternative coverage. The Part D statute and regulations repeatedly distinguish between basic and enhanced benefits, given that enhanced alternative coverage is optional and sponsor-specific.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern that the inclusion of supplemental benefits in TrOOP artificially accelerates beneficiaries through benefit phases into catastrophic coverage, increasing plan, federal, and manufacturer liability. These commenters asserted that including supplemental benefits in TrOOP creates distortions in plan design and undermines market stability. Specifically, a few commenters suggested that the inclusion of enhanced alternative supplemental benefits in TrOOP decreases plans' ability to manage beneficiary costs, increases government spending, increases bid pressure, and may cause plans to scale back supplemental benefits or exit the PDP market entirely, ultimately undermining program sustainability.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their input. CMS acknowledges that the inclusion of enhanced alternative supplemental benefits in TrOOP may affect the incentives available to beneficiaries enrolled in enhanced alternative plans, including the incentives for beneficiaries to choose higher-cost drugs over lower-cost ones in certain circumstances. When beneficiaries move through the benefit phases more quickly, overall plan liability increases, which may contribute to increased premium costs for enhanced alternative plans and affect sponsors' decisions about enhanced alternative plan offerings. While we cannot definitively attribute these changes to this policy, as other elements of the Part D redesign may also be contributing factors, we have seen a notable decline in standalone Part D-only enhanced alternative plan offerings along with a broader shift from copayments to coinsurance benefit design since the redesign was implemented. CMS recognizes stakeholder concerns that the proposed provision has the potential to increase Part D program costs and government spending and reduce plan offerings. We note that only a statutory change would allow CMS to exclude enhanced alternative supplemental benefits from counting towards TrOOP.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters requested that CMS clarify whether manufacturer copayment assistance or patient assistance programs are considered to be “certain other third-party payment arrangements” included as incurred costs for the calculation as TrOOP.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS clarifies that manufacturer copayment assistance and 
                        <PRTPAGE P="17398"/>
                        patient assistance programs do not count as incurred costs for purposes of TrOOP accumulation, as these programs operate outside of the Part D benefit.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that CMS clarify whether the proposed provision changes the treatment of supplemental benefits provided by Puerto Rico Platino plans for the purposes of calculating TrOOP, and requested that CMS codify current guidance related to the treatment of supplemental benefits provided by Platino plans in regulation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' request for clarity regarding the treatment of Puerto Rico Platino wrap-around coverage for purposes of calculating TrOOP. The proposed changes do not alter the longstanding treatment of Platino wrap-around coverage funded by the Commonwealth of Puerto Rico. Platino plans continue to submit Part D bids with only basic benefits. Under section 1860D-42(a) of the Act and § 423.859(c), which permits CMS to waive or modify applicable Part D requirements if CMS determines that waiver or modification is necessary to secure access to qualified prescription drug coverage for Part D eligible individuals residing in the territories, Platino wrap-around coverage count towards the beneficiary's TrOOP. Note that no other Medicaid assistance counts towards TrOOP, only those payments for residents of territories that substitute for low-income cost-sharing subsidies in accordance with the statute. CMS believes that existing statutory provisions and guidance provide sufficient clarity and additional rulemaking to codify current guidance related to supplemental benefits provided by Platino plans is not warranted given the longstanding nature of the section 1860D-42(a) waiver in place for Platino wrap-around coverage.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters disagreed with the proposal to codify the exclusion of negative values in the field on the PDE representing supplemental coverage from the calculation of TrOOP. A commenter stated that disregarding negative PDE values overstates the value of supplemental benefits. Another commenter suggested that it could lead to beneficiary confusion.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their input. CMS acknowledges that while excluding such negative values from TrOOP can overstate the net value of total supplemental benefits provided to beneficiaries over the course of the year, including negative values in TrOOP would inappropriately disregard any beneficiary cost sharing in excess of the defined standard cost sharing amount when calculating TrOOP. This would particularly disadvantage certain beneficiaries who have patterns of utilization that disproportionately include this situation. For example, if a beneficiary in an enhanced alternative plan has higher cost sharing than the defined standard benefit for a maintenance medication, including the negative values in TrOOP could significantly disadvantage that beneficiary as these negative values would continually offset part of the payments the beneficiary actually paid OOP. This would create some circumstances where certain beneficiaries have a net negative value for their supplemental benefits when they reach the OOP threshold, which could also lead to beneficiary confusion and could potentially violate the statutory requirement for an enrollee to have $0 cost sharing once their incurred costs exceed the OOP threshold.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported CMS' proposal to codify the inclusion of supplemental coverage provided by enhanced alternative Part D plans in the calculation of TrOOP. These commenters stated that aligning the regulatory definition of incurred costs with the statutory amendments provides needed clarity and consistency for beneficiaries, plans, and other stakeholders.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are finalizing the proposed amendments to §§ 423.100 and 423.464 without modification.</P>
                    <HD SOURCE="HD3">5. Policy For Drugs Not Subject to Defined Standard Deductible (§ 423.104)</HD>
                    <P>Under sections 1860D-2(b) and (c) of the Act, as amended by section 11201 of the IRA, the coverage gap phase was eliminated in CY 2025. Beginning in CY 2025, a beneficiary leaves the initial coverage phase and enters the catastrophic phase once they incur enough TrOOP-eligible costs to meet the annual OOP threshold. Accordingly, under section 1860D-14A(h) of the Act, as added by section 11201 of the IRA, the Coverage Gap Discount Program sunset effective January 1, 2025. Section 11201 of the IRA added section 1860D-14C of the Act, which created the Manufacturer Discount Program beginning January 1, 2025. Under section 1860D-14C(b)(1)(A) of the Act, manufacturers that enter into a Manufacturer Discount Program agreement will provide discounts on applicable drugs, typically amounting to 10 percent of the negotiated price for enrollees in the initial coverage phase and 20 percent of the negotiated price for enrollees in the catastrophic phase, in CY 2025 and subsequent years.</P>
                    <P>In the Contract Year 2027 proposed rule, we explained that manufacturer discounts are available under the Manufacturer Discount Program once a beneficiary becomes an “applicable beneficiary.” Section 1860D-14C(g)(1) of the Act defines an applicable beneficiary as an individual who, on the date of dispensing a covered Part D drug, is enrolled in a PDP or MA-PD plan, is not enrolled in a qualified retiree prescription drug plan, and has incurred TrOOP-eligible costs that exceed the defined standard deductible specified in section 1860D-2(b)(1) of the Act. TrOOP-eligible costs for drugs not subject to the defined standard deductible, specifically covered insulin products, as well as TrOOP-eligible costs for drugs not subject to a non-defined standard plan deductible or drugs subject to a reduced deductible under non-defined standard plans, all count towards a beneficiary's satisfaction of the defined standard deductible.</P>
                    <P>
                        We described the policy established in the Final CY 2025 Part D Redesign Program Instructions for drugs not subject to the defined standard deductible, which addresses situations where a beneficiary has not satisfied their plan deductible but has incurred sufficient TrOOP-eligible costs to satisfy the defined standard deductible, or situations where a beneficiary incurs sufficient costs to satisfy the plan deductible but has not incurred TrOOP-eligible costs cumulatively across all drugs at or above the defined standard deductible amount. We explained that, as established in the Final CY 2025 Part D Redesign Program Instructions, manufacturer discounts are not available until cumulative TrOOP-eligible costs meet the defined standard deductible. Plans that offer a non-defined standard plan deductible are responsible for the portion of costs that would otherwise be covered by the discount when a beneficiary incurs sufficient costs to satisfy the plan deductible but has not incurred TrOOP-eligible costs cumulatively across all drugs at or above the defined standard deductible amount. Additionally, we noted that in the Final CY 2026 Part D Redesign Program Instructions, we stated that this policy also applied in CY 2026 and established that for CY 2026 the policy for drugs not subject to the defined standard deductible also applies to the selected drug subsidy 
                        <PRTPAGE P="17399"/>
                        with respect to selected drugs during a price applicability period. In the Contract Year 2027 proposed rule, we proposed to codify the policy for drugs not subject to the defined standard deductible that are in effect for 2025 and 2026 without modification. Specifically, we proposed to codify the policy for drugs not subject to defined standard deductible at a new § 423.104(j).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported the proposal to codify the policies outlined in the Final CY 2025 and CY 2026 Part D Redesign Program Instructions regarding the application of the Manufacturer Discount Program to drugs that are not subject to the defined standard deductible. The commenter stated that codifying these policies ensures clarity, consistency, and effective implementation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS use the beneficiary's plan deductible as the threshold for becoming an applicable beneficiary under the Manufacturer Discount Program to alleviate potential beneficiary confusion, stating that the current approach favors some beneficiaries over others and ignores plan terms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1860D-14C(g)(1)(C) of the Act defines an “applicable beneficiary” as an individual who, on the date of dispensing a covered Part D drug, is enrolled in a Part D or MA-PD plan, is not enrolled in a qualified retiree prescription drug plan, and has incurred TrOOP-eligible costs that exceed the defined standard deductible specified in section 1860D-2(b)(1) of the Act. As such, once a beneficiary has incurred sufficient TrOOP-eligible costs to satisfy the defined standard deductible, they will be an applicable beneficiary under the Discount Program. Because the threshold for when a beneficiary becomes an applicable beneficiary is defined in statute, CMS cannot choose an alternative threshold.
                    </P>
                    <P>After considering the comments received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are finalizing the proposed amendments to § 423.104 without modification.</P>
                    <HD SOURCE="HD3">6. Annual Indexing of Part D Benefit Parameters Using the Annual Percentage Increase in Drug Expenditures (API) and Consumer Price Index (CPI) (§§ 423.104, 423.782)</HD>
                    <P>The Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (Pub. L. 108-173) (MMA) added sections 1860D-2(b) and 1860D-14(a) of the Act directing the Secretary to index certain Part D benefit parameters each year, which include, but are not limited to, the deductible limit and low-income cost-sharing amounts. The required annual adjustments ensure that the actuarial value of the drug benefit remains consistent with changes in Part D drug expenditures and general inflation. The MMA established two indices for adjusting Part D benefit parameters: (1) the annual percentage increase in average per capita aggregate expenditures for covered Part D drugs in the U.S. for Part D eligible individuals under section 1860D-2(b)(6) of the Act (referred to as the API); and (2) the annual percentage increase in the Consumer Price Index based on all items per a U.S. city average under section 1860D-14(a)(4)(A) of the Act (referred to as the CPI).</P>
                    <P>In accordance with the statute and corresponding regulation, the following Part D benefit parameters are updated annually using the API: the standard Part D benefit deductible, the initial coverage limit, the OOP threshold, maximum copayments below the OOP threshold for low-income full subsidy eligible enrollees with income less than 150 percent, but greater than 100 percent of Federal Poverty Level (FPL) not including institutionalized individuals, the RDS cost threshold, and the RDS cost limit. The CPI is used to update maximum copayments below the OOP threshold for low-income full subsidy eligible enrollees with income less than 100 percent of FPL.</P>
                    <P>In the Contract Year 2027 proposed rule, we explained that the current regulations do not describe the specific methods used to calculate the annual percentage increases. Instead, the specific methods for calculating the annual percentage increases in drug expenditures and CPI that are applied to the Part D benefit parameters have been proposed for each CY in the Advance Notice of Methodological Changes for Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies (Advance Notice) and finalized in the Announcement of Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies (Rate Announcement). In the Contract Year 2027 proposed rule, we proposed to codify these methodologies in regulation. Although we proposed to codify the calculation methodology for the API and CPI, we will continue to publish the annual percentage increases in drug expenditures and CPI and updated Part D benefit parameters for each CY through the Advance Notice and Rate Announcement.</P>
                    <HD SOURCE="HD3">Calculation of the Annual Percentage Increase in Drug Expenditures</HD>
                    <P>In the Contract Year 2027 proposed rule, we described the calculation of the API for Part D as the product of the annual percentage trend (APT), which is the year-over-year change in total per capita Part D covered drug expenditures based on PDE data, and a multiplicative update (MU) factor that incorporates updated data for prior years into the calculation.</P>
                    <P>We proposed to revise § 423.104(d)(5)(iv) by adding three paragraphs describing (1) the overall calculation of the annual percentage increase, or the API, in per capita Part D drug expenditures, (2) the calculation of the annual percentage trend, or the APT, and (3) the calculation of the multiplicative update factor, or the MU. We will continue to publish updates to the Part D benefit parameters calculated through these methodologies through the Advance Notice and Rate Announcement process described in section 1853(b) of the Act.</P>
                    <HD SOURCE="HD3">Calculation of the Annual Percentage Increase in CPI</HD>
                    <P>In the Contract Year 2027 proposed rule, we described the calculation of the annual percentage increase in the CPI as the product of an annual percentage trend, which is a year-over-year comparison of the CPI-U for all items, ending in September, and a multiplicative update factor that incorporates revisions when estimated CPI values are replaced with actual BLS data. We explained that this CPI-based update applies to copayments for the lowest-income dually eligible beneficiaries (with incomes not exceeding 100 percent of the FPL) to preserve purchasing power relative to general inflation.</P>
                    <P>
                        To implement the CPI calculation described previously in our regulations, we proposed to revise § 423.782(a)(2)(iii)(A) to include a reference to a new paragraph (d), which we proposed to add at the end of § 423.782. New § 423.782(d) would comprise the general language of the statute, as well as add three subparagraphs describing: (1) the overall calculation of the annual percentage increase in CPI and specify the period ending in “September of such previous year,” (2) the calculation of the annual percentage trend, and (3) the calculation of the multiplicative update factor. We will continue to publish updates to the Part D benefit parameters calculated through these methodologies through the Advance Notice and Rate 
                        <PRTPAGE P="17400"/>
                        Announcement process described in section 1853(b) of the Act.
                    </P>
                    <HD SOURCE="HD3">Technical Changes</HD>
                    <P>We also proposed two technical changes to § 423.782(b).</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for CMS' proposal to codify the methodologies for calculating the API and CPI used to update Part D benefit parameters. The commenter stated that the proposal ensures uniform application of Part D parameter updates across plan sponsors and benefit years.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their support.
                    </P>
                    <P>After considering the comments we received, we are finalizing the proposed provisions at §§ 423.104 and 423.782 without modification.</P>
                    <HD SOURCE="HD3">7. Changes to GCPDC and Allowable Reinsurance Cost Definitions To Include Costs Paid by the MDP (§ 423.308)</HD>
                    <P>Section 1860D-15(b)(3) of the Act defines gross covered prescription drug costs (GCPDC) and allowable reinsurance costs for the purpose of describing the methodology for calculating the reinsurance payment amount. In the Contract Year 2027 proposed rule, we explained that GCPDC is defined as the costs incurred under a Part D plan, excluding administrative costs but including deductible and dispensing-related costs, regardless of payer, while allowable reinsurance costs are limited to amounts actually paid net of discounts and rebates. We further explained that consistent with the statutory and regulatory definition of GCPDC, manufacturer discounts under the Coverage Gap Discount Program were included in GCPDC, but the IRA amended the statute to require inclusion of manufacturer discounts under the new Manufacturer Discount Program in both GCPDC and allowable reinsurance costs beginning in 2025. CMS implemented these statutory changes through the Final CY 2025 Part D Redesign Program Instructions and Final CY 2026 Part D Redesign Program Instructions.</P>
                    <P>In the Contract Year 2027 proposed rule, we proposed that the regulatory definition of “gross covered prescription drug costs” at § 423.308 be revised to include “all amounts paid by manufacturers under the Manufacturer Discount Program (as defined at § 423.100).” We also proposed to add the phrase “for years prior to 2025” before the phrase “amounts between the initial coverage limit and the out-of-pocket threshold” and the phrase “because the enrollee is between the initial coverage limit and the out-of-pocket threshold” to reflect that the coverage gap phase does not exist for 2025 and subsequent years. Additionally, we proposed to revise the regulatory definition of “allowable reinsurance costs” at § 423.308 to include “the portion of the negotiated price (as defined in section 1860D-14C(g)(6) of the Act) of an applicable drug (as defined at § 423.100) paid by manufacturers under the Manufacturer Discount Program (as defined at § 423.100).”</P>
                    <P>We received no comments on this proposal and are finalizing the proposed revision at § 423.308 without modification.</P>
                    <HD SOURCE="HD3">8. Reinsurance Methodology (§ 423.329)</HD>
                    <P>Section 1860D-15(b) of the Act, originally enacted into law by the MMA, sets forth rules for the calculation and payment of federal reinsurance subsidies for Part D plans. For years preceding CY 2025, the reinsurance amount for a Part D eligible individual was an amount equal to 80 percent of the allowable reinsurance costs attributable to that portion of gross covered prescription drug costs incurred after that individual reached the catastrophic phase of the benefit.</P>
                    <P>Beginning in 2025, the IRA reduced the reinsurance payment amount for a Part D beneficiary from 80 percent to 20 percent for applicable drugs or 40 percent for drugs that are not applicable drugs. As we explained in the Contract Year 2027 proposed rule, we make reinsurance payments to Part D plan sponsors based on the GCPDC that were actually paid during the coverage year, meaning that the costs must be actually incurred by the Part D sponsor and must be net of any direct and indirect remuneration (DIR). In the Final CY 2025 Part D Redesign Program Instructions, we established a methodology to calculate reinsurance subsidies separately for applicable drugs and non-applicable drugs and allocate the share of DIR for applicable and non-applicable drugs based on their respective gross drug costs that fall in the catastrophic phase. In the Final CY 2026 Part D Redesign Program Instructions we updated the methodology to account for selected drugs, which are grouped with non-applicable drugs for purposes of calculating the reinsurance subsidy. We explained that the Final CY 2026 Part D Redesign Program Instructions established the process for calculating reinsurance separately for applicable and non-applicable or selected drugs, allocating DIR based on each category's share of gross drug costs in the catastrophic phase, and reconciling the adjusted reinsurance amounts against prospective payments using NDC-level drug classifications.</P>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify at § 423.329 the policies we established in the Final CY 2025 Part D Redesign Program Instructions for CY 2025 and the Final CY 2026 Part D Redesign Program Instructions for CY 2026 with respect to the reinsurance methodology without modification. Specifically, we proposed to redesignate paragraph (c)(1) as paragraph (c)(1)(i) and revise the introductory language to state “general rule for years preceding 2025” and add a new paragraph (c)(1)(ii) to codify the rules described previously for 2026 and future years.</P>
                    <P>We received no comments on this proposal and are finalizing the proposed revisions to § 423.329 without modification.</P>
                    <HD SOURCE="HD3">9. Selected Drug Subsidy (§§ 423.265, 423.315, 423.329, 423.343)</HD>
                    <P>Section 11201 of the IRA added section 1860D-14D to the Act, creating a new selected drug subsidy program which began in CY 2026. In the Contract Year 2027 proposed rule, we described the selected drug subsidy program, under which the Secretary provides Part D plan sponsors with a subsidy equal to 10 percent of the negotiated price for selected drugs during a price applicability period dispensed to applicable beneficiaries below the annual out-of-pocket threshold after the deductible is met. We further explained that because of the intertwined structure and wording of the Manufacturer Discount Program and selected drug subsidy program provisions in the Act, we proposed to treat claims that are subject to the selected drug subsidy as coterminous with claims that would qualify for applicable discounts under the Manufacturer Discount Program, but for the drug's status as a selected drug during a price applicability period. Finally, we described our proposal to make monthly prospective payments for the selected drug subsidy program, based on Part D plan sponsors' estimates of selected drug subsidy amounts submitted with their annual bids, and reconciled using the actual selected drug subsidy amounts that Part D plan sponsors report on PDE data.</P>
                    <P>
                        In the Contract Year 2027 proposed rule, we proposed to codify at new § 423.265(d)(2)(vi) a requirement that assumptions regarding selected drug subsidy amounts payable be included in Part D bids submitted to us. We also proposed to codify at new § 423.315(h) that we would provide prospective selected drug subsidy payments on a 
                        <PRTPAGE P="17401"/>
                        monthly basis. We also proposed to codify at new § 423.329(e) the determination of selected drug subsidy payments. Finally, we proposed to codify at § 423.343(e) that we would make final payment for selected drug subsidy payments after a coverage year after obtaining all information necessary to determine the amount of payment.
                    </P>
                    <P>We received no comments on this proposal and are finalizing the proposed additions at §§ 423.265, 423.315, 423.329, and 423.343 without modification.</P>
                    <HD SOURCE="HD3">10. Technical Correction—Retroactive Adjustments and Reconciliations (§§ 423.336 and 423.343)</HD>
                    <P>In the Contract Year 2027 proposed rule, we noted the need for a technical correction at § 423.343(d)(2). The final sentence of this paragraph is incorrectly placed in § 423.343 and should instead be placed in § 423.336. Thus, we proposed to revise § 423.343 to remove this sentence and revise § 423.336(c) to add this sentence in its proper context.</P>
                    <P>We received no comments on this proposal and are finalizing the proposed revisions at §§ 423.336 and 423.343 without modification.</P>
                    <HD SOURCE="HD3">11. Base Beneficiary Premium (§ 423.286)</HD>
                    <P>Section 1860D-13(a)(2) of the Act, as established by the MMA, describes the statutory formula for calculating plan-specific basic Part D premiums under the Part D program. The national base beneficiary premium (BBP) is the starting point for calculating a plan-specific basic Part D premium. Prior to the enactment of the IRA, the BBP was calculated as the product of the beneficiary premium percentage and the national average monthly bid amount. The beneficiary premium percentage (“applicable percentage”) is a fraction, with a numerator of 25.5 percent and a denominator equal to 100 percent minus a percentage equal to (i) the total reinsurance payments that we estimate will be paid for the coverage year, divided by (ii) that amount plus the total payments that we estimate will be paid to Part D plans based on the standardized bid amount during the year, taking into account amounts paid by both CMS and plan enrollees.</P>
                    <P>In the Contract Year 2027 proposed rule, we explained that the IRA amended section 1860D-13(a)(2) of the Act such that the statutory formula described in the preceding paragraph would apply subject to a newly added section 1860D-13(a)(8)(A) of the Act, which states that, for a prescription drug plan for a month in 2024 through 2029, the BBP shall be equal to the lesser of the BBP for the preceding year increased by 6 percent or the amount computed under the formula described at section 1860D-13(a)(2) of the Act.</P>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify the statutory amendments to section 1860D-13(a) of the Act. Specifically, we proposed to redesignate § 423.286(b) as § 423.286(b)(1) and codify the BBP formula for 2024 through 2029 at new § 423.286(b)(2).</P>
                    <P>We received no comments on this proposal and are finalizing the proposed changes to § 423.286 without modification.</P>
                    <HD SOURCE="HD3">12. Low-Income Cost-sharing Subsidy (§ 423.782)</HD>
                    <P>The Part D low-income subsidy (LIS) helps individuals with Medicare who meet certain statutory income and resource criteria pay for prescription drugs and lowers the costs of prescription drug coverage. Prior to the enactment of the IRA, individuals who qualified for the full LIS received assistance to pay their full premiums and deductibles (in certain Part D plans) and have reduced cost sharing. Individuals who qualified for the partial LIS paid reduced premiums (on a sliding scale based on their income) and also had reduced deductibles and cost sharing. Section 11404 of the IRA amended section 1860D-14 of the Act to expand eligibility for the full LIS to individuals who are determined to have incomes below 150 percent of the FPL and who meet either the resource standard in paragraph (3)(D) or paragraph (3)(E) of section 1860D-14(a) of the Act, with respect to plan years beginning on or after January 1, 2024. Thus, beginning in CY 2024, individuals who previously would have qualified for the partial subsidy now receive the full LIS.</P>
                    <P>In the Contract Year 2027 proposed rule, we proposed to amend the eligibility criteria for LIS cost sharing reductions at § 423.782 to align with the IRA's amendments to section 1860D-14(a)(1) of the Act and the changes to §§ 423.773 and 423.780. Specifically, we proposed to update the FPL limit specified in § 423.782(a)(2)(i)(B) to 150 percent for plan years beginning on or after January 1, 2024.</P>
                    <P>In addition, we proposed to amend paragraph (a)(2) of § 423.782 to state that for years preceding 2025, LIS cost sharing reductions applied to covered Part D drugs obtained after the initial coverage limit and below the OOP limit.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for CMS's proposal to align LIS eligibility criteria with the IRA by updating the FPL limit to 150 percent for plan years beginning January 1, 2024.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their support.
                    </P>
                    <P>After considering the comments we received, we are finalizing the proposed revisions to § 423.782 without modification.</P>
                    <HD SOURCE="HD3">13. Retiree Drug Subsidy Parameters (§§ 423.882 and 423.884)</HD>
                    <P>Section 1860D-22 of the Act provides for subsidy payments to sponsors of qualified retiree prescription drug plans, provided that the employment-based retiree health coverage is at least actuarially equivalent to the standard prescription drug coverage under Medicare Part D. In the Contract Year 2027 proposed rule, we explained that, although the IRA amended the parameters of the standard prescription drug coverage and makes other changes to the Part D benefit, it did not change the requirements for qualified retiree prescription drug plans.</P>
                    <P>Although the majority of the IRA policies in effect for CY 2027 and subsequent years do not require updates to Subpart R, we explained in the Contract Year 2027 proposed rule that there are certain conforming edits required. Specifically, we proposed to revise the definitions of “gross covered retiree plan-related prescription drug costs” and “allowable retiree costs” at § 423.882 to reflect the proposed revisions to the definitions of “gross covered prescription drug costs” and “allowable reinsurance costs” at § 423.308. We also proposed to replace all references in § 423.884(d) to “not taking into account the value of any discount or coverage provided during the coverage gap” with the statement “for years prior to 2025, not taking into account the value of any discount or coverage provided during the coverage gap and for 2025 and subsequent years, not taking into account the value of any discount provided under the Manufacturer Discount Program.”</P>
                    <P>We received no comments on this proposal and are finalizing the proposed revisions to §§ 423.882 and 423.884 without modification.</P>
                    <HD SOURCE="HD3">14. Medical Loss Ratio (§ 423.2420)</HD>
                    <P>
                        In the Contract Year 2027 proposed rule, we explained that the medical loss ratio (MLR) requirements established under section 1857(e) of the Act require Part D contracts to report the percentage of revenue received under the contract spent on incurred claims for all enrollees for Part D prescription drugs and on quality initiatives that meet the requirements at § 423.2430. The percentage of revenue that is used for 
                        <PRTPAGE P="17402"/>
                        other items such as administration, marketing, and profit is excluded from the numerator of the MLR. We described longstanding policy that pass-through payments for which plans retain no liability, such as low-income cost-sharing subsidies and Coverage Gap Discount Program payments, are excluded from both the numerator and denominator of the MLR. We further explained that new federal payments created by the IRA, including Manufacturer Discount Program payments, the Inflation Reduction Act Subsidy Amount (IRASA), and the selected drug subsidy, are treated similarly as pass-through amounts and therefore excluded from the MLR calculation. This was established in the Final CY 2025 Part D Redesign Program Instructions and applied in CY 2026 through the Final CY 2026 Part D Redesign Program Instructions.
                    </P>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify for CY 2027 and subsequent years the policies established in the Final CY 2025 Part D Redesign Program Instructions and Final CY 2026 Part D Redesign Program Instructions with respect to the treatment of the Manufacturer Discount Program payments, IRASA, and selected drug subsidy program payments for MLR purposes. These policies are currently in effect. Specifically, we proposed to codify the exclusion of the Manufacturer Discount Program payments, IRASA, and selected drug subsidy program payments at § 423.2420(b)(4)(iii), (iv), and (v) respectively.</P>
                    <P>We received no comments on this proposal and are finalizing the proposed revisions at § 423.2420 without modification.</P>
                    <HD SOURCE="HD3">15. Severability</HD>
                    <P>We proposed that the Medicare Part D redesign provisions finalized herein would be separate and severable from one another. Further, we proposed that if any of these provisions is held to be invalid or unenforceable by its terms, or as applied to any person or circumstance, or stayed pending further agency action, it is our intention that such provision shall be severable from this rule and not affect the remainder thereof, or the application of such provision to other persons not similarly situated or to other, dissimilar circumstances.</P>
                    <P>We received no comments on this proposal and are finalizing without modification.</P>
                    <HD SOURCE="HD2">B. Medicare Coverage Gap Discount Program</HD>
                    <P>Section 1860D-14A of the Act established the Medicare Coverage Gap Discount Program, which began on January 1, 2011. Coverage Gap Discount Program requirements were codified in the “Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Programs for Contract Year 2013 and Other Changes” final rule (77 FR 22072) under subpart W of 42 CFR part 423.</P>
                    <P>The Inflation Reduction Act of 2022 (Pub. L. 117-169) (IRA) added section (h) to section 1860D-14A of the Act, which sunset the Coverage Gap Discount Program and terminated all Coverage Gap Discount Program agreements, effective January 1, 2025. Section 1860D-14A(h)(2) of the Act further specifies that the provisions of section 1860D-14A of the Act, including all responsibilities and duties under such agreements continue to apply with respect to applicable drugs dispensed prior to January 1, 2025. Accordingly, we proposed to amend § 423.2300 by adding a new paragraph to specify that the requirements of subpart W apply before January 1, 2025 and, with respect to applicable drugs dispensed prior to that date, continue to apply on and after January 1, 2025. To make this change, we proposed to redesignate the existing text of § 423.2300 as paragraph (a) and redesignate existing paragraphs (a) through (h) as § 423.2300(a)(1) through (8), respectively. We proposed to add the new text at § 423.2300(b). We also proposed to revise § 423.2315(c)(2) to reflect the sunset of the Coverage Gap Discount Program by specifying the effective date of a Coverage Gap Discount Program agreement to 2012 and subsequent years prior to 2025. Finally, in accordance with section 1860D-14A(h)(1) of the Act, we proposed to amend § 423.2345 by adding a new paragraph (f) to specify that, subject to § 423.2300(b), as redesignated, all Coverage Gap Discount Program agreements under this subpart are terminated as of January 1, 2025.</P>
                    <P>To address programmatic differences between the Coverage Gap Discount Program and the Manufacturer Discount Program, which are discussed in more detail in section II.C. of this final rule, we proposed to revise § 423.2305 to clarify that the definitions at § 423.2305 apply only for purposes of the Coverage Gap Discount Program. Further, we proposed to revise the definition of “applicable discount” at § 423.2305 to specify that it refers to 50 percent of the negotiated price with respect to a plan year before 2019 and 70 percent of the negotiated price with respect to plan year 2019 through plan year 2024. Lastly, we proposed technical changes throughout subpart W to replace the shorthand term “Discount Program” with “Coverage Gap Discount Program.”</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters were in support of the proposed changes. Commenters acknowledged the proposals as important and consistent with statutory requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support and are finalizing the changes to the subpart that were proposed.
                    </P>
                    <HD SOURCE="HD2">C. Medicare Part D Manufacturer Discount Program</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>
                        The Medicare Part D Manufacturer Discount Program (Manufacturer Discount Program) was enacted into law in section 11201 of the Inflation Reduction Act of 2022, Public Law 117-169 (IRA) and codified in sections 1860D-14C and 1860D-43 of the Act. Section 11201(f) of the IRA directed the Secretary to implement the Manufacturer Discount Program by program instruction or other forms of program guidance for 2025 and 2026. In accordance with the law, on November 17, 2023, CMS released the Medicare Part D Manufacturer Discount Program Final Guidance. On December 20, 2024, we released the Revised Medicare Part D Manufacturer Discount Program Final Guidance (Manufacturer Discount Program Final Guidance).
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             Available at: 
                            <E T="03">https://www.cms.gov/files/document/revised-manufacturer-discount-programfinal-guidance122024.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        In the proposed rule, we proposed to codify the Manufacturer Discount Program Final Guidance, with limited refinements and changes, to be effective beginning CY 2027. Under the Manufacturer Discount Program, for applicable drugs and selected drugs to be coverable under Part D, manufacturers of such drugs are required to enter into a Manufacturer Discount Program agreement with CMS and agree to provide discounts on their applicable drugs when dispensed to Part D enrollees who are in the initial and catastrophic coverage phases of the Part D benefit. Discounts under the Manufacturer Discount Program are advanced at the point of sale by the Part D plan sponsor, and manufacturers are invoiced quarterly based on the amounts submitted by plan sponsors on Prescription Drug Event (PDE) records. CMS provides prospective payments to plan sponsors and adjusts the payments through an annual reconciliation.
                        <PRTPAGE P="17403"/>
                    </P>
                    <P>Discounts under the Manufacturer Discount Program generally reduce the amount the Part D sponsor pays for the drug, and discounts are paid for all Part D enrollees who have exceeded the annual Part D deductible specified in section 1860D-2(b)(1) of the Act. Discounts are 10 percent of the negotiated price of the applicable drug in the initial coverage phase and 20 percent in the catastrophic coverage phase, and are phased in over the first several years of the program for manufacturers that meet statutory criteria for specified manufacturers and specified small manufacturers.</P>
                    <P>Many of the other policies currently in effect pursuant to the Manufacturer Discount Program Final Guidance, which we proposed to codify mirror longstanding policies under the Coverage Gap Discount Program, including use of a third party administrator (TPA) to facilitate program operations such as invoicing and payment, use of the Health Plan Management System (HPMS) to execute agreements and house data, and the manufacturer dispute resolution process. All of these policies are discussed in more detail later in this section.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments supportive of our proposal to codify existing Manufacturer Discount Program policies. Commenters appreciated that CMS implemented the Manufacturer Discount Program in a manner similar to the former Coverage Gap Discount Program.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support. We are finalizing the regulatory policies for the Manufacturer Discount Program largely as proposed, with limited modifications, which are described in greater detail below.
                    </P>
                    <HD SOURCE="HD3">2. Basis and Scope (§ 423.2700)</HD>
                    <P>We proposed to codify the requirements for the Manufacturer Discount Program under sections 1860D-14C and 1860D-43 of the Act as new subpart AA of part 423. Proposed § 423.2700(a) and (b) set forth the basis and scope, respectively.</P>
                    <P>We proposed a conforming change at § 423.1 to incorporate section 1860D-14C of the Act into the scope of part 423.</P>
                    <P>We received no comments on this section and we are finalizing § 423.2700 as proposed.</P>
                    <HD SOURCE="HD3">3. Definitions (§§ 423.100, 423.1002, and 423.2704)</HD>
                    <P>We proposed to codify the definition of frequently used terms consistent with section 1860D-14C of the Act or established in the Manufacturer Discount Program Final Guidance, as well as new definitions consistent with the policies we are finalizing in this rule.</P>
                    <P>Several of these terms are also used for purposes of the Coverage Gap Discount Program. Because some of the terms are applicable to both subpart W and proposed subpart AA, we proposed to revise certain definitions in existing §§ 423.100, 423.1002, and 423.2305, move certain definitions from § 423.2305 to § 423.100 with revisions as necessary to comply with relevant statutory requirements, and add new definitions for purposes of the Manufacturer Discount Program at proposed § 423.2704.</P>
                    <P>At § 423.100, we proposed to revise a number of existing definitions as discussed below.</P>
                    <P>• “Applicable beneficiary”;</P>
                    <P>We proposed to revise the definition of “applicable beneficiary” to reflect the statutory definition of such term under the Coverage Gap Discount Program and the Manufacturer Discount Program.</P>
                    <P>• “Applicable drug”;</P>
                    <P>We proposed to modify the existing definition of “applicable drug” to specify that compounded drug products (as described in § 423.120(d)) containing an applicable drug are excluded from the definition. As stated in the proposed rule, this change would codify both longstanding CMS policy under the Coverage Gap Discount Program as well as policy established in section 40.1 of the Manufacturer Discount Program Final Guidance. Whereas plans may cover compounds that include at least one Part D ingredient, and that ingredient would be an applicable drug if dispensed on its own, because compounds as a whole are not approved under a New Drug Application (NDA) or Biologic Licensing Application (BLA), CMS has established that compounds do not meet the definition of an applicable drug.</P>
                    <P>For the purposes of the Manufacturer Discount Program, we proposed to clarify that “applicable drug” also includes a Part D drug that is provided to a particular applicable beneficiary as a transition fill under § 423.120(b)(3) or as an emergency supply as may be required for an applicable beneficiary who is a long-term care resident. As stated in the proposed rule, this clarification would codify our longstanding approach under the Coverage Gap Discount Program where, in practice, such fills have been treated as meeting the definition of “applicable drug.”</P>
                    <P>Finally, in accordance with the statutory definition of “applicable drug” at section 1860D-14C(g)(2) of the Act and the Manufacturer Discount Program Final Guidance, we proposed to specify that, for the purposes of the Manufacturer Discount Program, an applicable drug is not a selected drug during a price applicability period with respect to such drug.</P>
                    <P>We proposed to add definitions for the following terms at § 423.100:</P>
                    <P>• “Applicable discount”;</P>
                    <P>We proposed to add a definition of “applicable discount” that identifies the separate programmatic definitions of such term for the Coverage Gap Discount Program and the Manufacturer Discount Program. Specifically, we proposed to define “applicable discount” as, for purposes of the Coverage Gap Discount Program, having the meaning set forth at § 423.2305, and for purposes of the Manufacturer Discount Program, the meaning set forth at § 423.2712.</P>
                    <P>• “Applicable number of calendar days”;</P>
                    <P>We proposed to remove the definition of “applicable number of calendar days” from § 423.2305 and add it at § 423.100. This definition would apply to both the Coverage Gap Discount Program and the Manufacturer Discount Program.</P>
                    <P>• “Date of dispensing”;</P>
                    <P>We proposed to remove the existing definition of “date of dispensing” from § 423.2305 and add it, with revisions, at § 423.100. Specifically, we proposed to add at the end of the definition, “For long-term care and home infusion pharmacies, the date of dispensing can be interpreted as the date the pharmacy submits the discounted claim for reimbursement.”</P>
                    <P>• “Labeler code”;</P>
                    <P>We proposed to remove the existing definition of “labeler code” from § 423.2305 and add it, with revisions, at § 423.100. Specifically, we proposed to remove the phrase “Food and Drug Administration.”</P>
                    <P>• “Manufacturer”;</P>
                    <P>We proposed to remove the existing definition of “manufacturer” from § 423.2305 and add it at § 423.100 with a revision removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program and the Manufacturer Discount Program”.</P>
                    <P>• “Manufacturer Discount Program”;</P>
                    <P>We proposed to define “Manufacturer Discount Program” as the Medicare Part D Manufacturer Discount Program established under section 1860D-14C of the Act.</P>
                    <P>• “Manufacturer Discount Program agreement”;</P>
                    <P>
                        We proposed to define “Manufacturer Discount Program agreement” as the 
                        <PRTPAGE P="17404"/>
                        agreement described at section 1860D-14C(b) of the Act.
                    </P>
                    <P>• “Medicare Coverage Gap Discount Program”;</P>
                    <P>We proposed to remove the definition of “Medicare Coverage Gap Discount Program” from § 423.2305 and add it at § 423.100, with revisions to remove the phrase “Program (or Discount Program)” and add in its place the phrase “Program (or Coverage Gap Discount Program)”.</P>
                    <P>• “Medicare Coverage Gap Discount Program agreement”;</P>
                    <P>We proposed to remove the definition of “Medicare Coverage Gap Discount Program agreement” from § 423.2305 and add it at § 423.100 with revisions to remove the phrase “Program agreement (or Discount Program agreement)” and add in its place the phrase “Program agreement (or Coverage Gap Discount Program agreement)”.</P>
                    <P>• “National Drug Code (NDC)”; and</P>
                    <P>We proposed to remove the definition of “National Drug Code” from § 423.2305 and add it at § 423.100 with revisions to remove the phrase “the product” and add in its place the phrase “the product's manufacturer, product”.</P>
                    <P>• “Non-applicable drug”;</P>
                    <P>We proposed to define “non-applicable drug” to mean any Part D drug that is not an applicable drug and not a selected drug during a price applicability period with respect to such drug.</P>
                    <P>• “Price applicability period”;</P>
                    <P>We proposed to define “price applicability period” as having the meaning given such term in section 1191(b)(2) of the Act and any applicable regulations and guidance.</P>
                    <P>• “Selected drug”; and</P>
                    <P>We proposed to define “selected drug” as having the meaning given such term in section 1192(c) of the Act and any applicable regulations and guidance.</P>
                    <P>• “Third Party Administrator (TPA)”.</P>
                    <P>We proposed to add at § 423.100 the definition of “Third Party Administrator” that we proposed to remove from § 423.2305, with revisions. Specifically, we proposed to remove the phrase “section 1860D-14A of the Act” and add in its place the phrase “sections 1860D-14A and 1860D-14C of the Act”.</P>
                    <P>At § 423.1002, we proposed to revise the existing definition of “affected party” to account for the definition of “manufacturer” under the Coverage Gap Discount Program and the definition of “agreement holder” under the Manufacturer Discount Program. Specifically, we proposed that affected party means any Part D sponsor or, for purposes of the Coverage Gap Discount Program, any manufacturer (as defined in § 423.100), or, for purposes of the Manufacturer Discount Program, any manufacturer that is an agreement holder (as defined in § 423.2704), impacted by an initial determination or, if applicable, by a subsequent determination or decision issued under this part, and “party” means the affected party or CMS, as appropriate.</P>
                    <P>We proposed to remove the following definitions from § 423.2305 because, as noted previously, we proposed to add definitions for such terms at § 423.100, for purposes of incorporating the Manufacturer Discount Program:</P>
                    <P>• “Applicable number of calendar days”;</P>
                    <P>• “Date of dispensing”;</P>
                    <P>• “Labeler code”;</P>
                    <P>• “Manufacturer”;</P>
                    <P>• “Medicare Coverage Gap Discount Program”;</P>
                    <P>• “Medicare Coverage Gap Discount Program Agreement”;</P>
                    <P>• “National Drug Code (NDC)”; and</P>
                    <P>• “Third Party Administrator (TPA)”.</P>
                    <P>At § 423.2704, we proposed to define the following terms for purposes of proposed subpart AA and the Manufacturer Discount Program:</P>
                    <P>• “Agreement holder”;</P>
                    <P>We proposed to define “agreement holder” as a manufacturer that has executed and has in effect its own Manufacturer Discount Program agreement in accordance with § 423.2708(b)(1).</P>
                    <P>• “Applicable discount”;</P>
                    <P>We proposed to define “applicable discount” as having the meaning set forth at § 423.2712.</P>
                    <P>• “Applicable LIS percent”;</P>
                    <P>We proposed to define “applicable LIS percent” as having the meaning set forth at § 423.2712(d)(1).</P>
                    <P>• “Applicable small manufacturer percent”;</P>
                    <P>We proposed to define “applicable small manufacturer percent” as having the meaning set forth at § 423.2712(d)(2).</P>
                    <P>• “Covered Part D drug”;</P>
                    <P>We proposed to define “covered Part D drug” as having the meaning set forth at § 423.100.</P>
                    <P>• “Dispute submission deadline”;</P>
                    <P>We proposed to define “dispute submission deadline” as the date that is 60 calendar days from the date of the invoice containing the information that is the subject of the agreement holder's dispute.</P>
                    <P>• “Negotiated price”;</P>
                    <P>We proposed to define “negotiated price” as having the meaning set forth at § 423.100, and with respect to an applicable drug under the Manufacturer Discount Program, the negotiated price includes any dispensing fee and, if applicable, any vaccine administration fee and sales tax.</P>
                    <P>• “Network pharmacy”;</P>
                    <P>We proposed to define “network pharmacy” as having the meaning set forth at § 423.100.</P>
                    <P>• “Part D drug”;</P>
                    <P>We proposed to define “Part D drug” as having the meaning set forth at § 423.100.</P>
                    <P>• “Primary manufacturer”;</P>
                    <P>We proposed to define “primary manufacturer” as having the meaning given such term pursuant to applicable regulations and guidance for the Medicare Drug Price Negotiation Program.</P>
                    <P>• “Specified drug”;</P>
                    <P>We proposed to define “specified drug” as meaning, with respect to a specified manufacturer, for 2021, an applicable drug that is produced, prepared, propagated, compounded, converted, or processed by the specified manufacturer.</P>
                    <P>• “Specified small manufacturer drug”; and</P>
                    <P>We proposed to define “specified small manufacturer drug” as meaning, with respect to a specified small manufacturer, for 2021, an applicable drug that is produced, prepared, propagated, compounded, converted, or processed by the specified small manufacturer.</P>
                    <P>• “Total expenditures”.</P>
                    <P>We proposed to define “total expenditures” as meaning, with respect to Part D, the total gross covered prescription drug costs, as defined in § 423.308; and as meaning, with respect to Part B, the total Medicare allowed amount (that is, total allowed charges), inclusive of beneficiary cost sharing, for Part B drugs and biologicals, except that expenditures for a drug or biological that are bundled or packaged into the payment for another service are excluded.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments regarding our proposed definitions, specifically in support of our proposed definitions of “applicable drug” and “date of dispensing.” Both commenters noted that the proposed definitions will provide clarity for stakeholders, including plans, pharmacies, enrollees, and manufacturers. A commenter applauded CMS's recognition that transition fills and emergency supplies are “applicable drugs” and may be necessary for long term care residents to ensure uninterrupted access to medications that can be lifesaving. Another commenter appreciated CMS ensuring that definitions are consistent across the agency's guidance documents, policies, and programs.
                        <PRTPAGE P="17405"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support and are finalizing the proposals discussed in this section without modification our proposed definitions at §§ 423.100, 423.1002, 423.2305, and 423.2704.
                    </P>
                    <HD SOURCE="HD3">4. Conditions for Coverage of Drugs Under Part D (§ 423.2708)</HD>
                    <P>Section 1860D-43(a) of the Act, as amended by the IRA, specifies that, beginning January 1, 2025, in order for Part D coverage to be available for the covered Part D drugs of a manufacturer, the manufacturer must participate in the Manufacturer Discount Program and have entered into and have in effect a Manufacturer Discount Program agreement with CMS, as described in section 1860D-14C(b) of the Act. Operationally, coverage of a drug under a Manufacturer Discount Program agreement is determined by coverage of its labeler code (as defined at § 423.100) under such agreement.</P>
                    <P>Any Part D drug that is a selected drug during a price applicability period with respect to such drug, is excluded from the definition of applicable drug under section 1860D-14C(g)(2)(B) of the Act and, therefore, not subject to applicable discounts under the Manufacturer Discount Program when dispensed during a price applicability period. However, a selected drug would otherwise meet the definition of an applicable drug, but for it being in a price applicability period following its selection into the Medicare Drug Price Negotiation Program. Therefore, applying section 1860D-43(a) of the Act's coverage exclusion in the absence of a Manufacturer Discount Program agreement to both applicable drugs and selected drugs provides incentive for manufacturers of brand name drugs and biological products to participate in the Manufacturer Discount Program, while not undermining beneficiary access to generics. Moreover, this interpretation is consistent with the IRA's addition of section 1860D-43(c)(2) of the Act, which prohibits the Secretary from authorizing coverage for a covered Part D drug of a manufacturer without a Manufacturer Discount Program agreement for any period described in section 5000D(c)(1) of the Internal Revenue Code under the exception for drugs determined to be essential to the health of Part D enrollees. This provision further demonstrates that the statute does not allow for a selected drug to be eligible for Part D coverage in the absence of a Manufacturer Discount Program agreement. As stated in section 40 of the Manufacturer Discount Program Final Guidance and consistent with the policy on applicable drugs, beginning January 1, 2025, Part D coverage for selected drugs during a price applicability period is available only for selected drugs for which the labeler code is covered by a Manufacturer Discount Program agreement with CMS, as described in section 1860D-14C(b) of the Act.</P>
                    <P>At § 423.2708(a), we proposed to codify existing Manufacturer Discount Program policy that, in order for coverage to be available under Part D for a Part D drug of a manufacturer that is an applicable drug or a selected drug during a price applicability period:</P>
                    <P>• The FDA-assigned labeler code of such drug must be covered under a Manufacturer Discount Program agreement that is in effect;</P>
                    <P>• The manufacturer must participate in the Manufacturer Discount Program; and</P>
                    <P>• The manufacturer must have entered into and have in effect a Manufacturer Discount Program agreement.</P>
                    <P>We expect each manufacturer that chooses to participate in the Manufacturer Discount Program to enter into its own Manufacturer Discount Program agreement with CMS. However, we acknowledge a longstanding practice where CMS has permitted manufacturers to cover by their Manufacturer Discount Program agreement (and previously by their Coverage Gap Discount Program agreement) labeler code(s) assigned by the FDA to another manufacturer. CMS did not propose to prohibit this practice, provided all other requirements of the Manufacturer Discount Program are met. As discussed in the preamble to the proposed rule, a manufacturer is considered to participate in the Manufacturer Discount Program and to have entered into and have in effect a Manufacturer Discount Program agreement under proposed § 423.2708(a)—and thus, under section 1860D-43(a) of the Act—if such manufacturer executes and has in effect its own Manufacturer Discount Program agreement or participates by means of an arrangement whereby its labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement that is in effect. We proposed to codify this requirement at § 423.2708(b).</P>
                    <P>While a manufacturer may participate in the Manufacturer Discount Program in accordance with proposed § 423.2708(b)(2), as described in more detail in section II.C.12. of this preamble, only the entity that executes an agreement pursuant to proposed § 423.2708(b)(1) is an agreement holder (as defined at § 423.2704). Consistent with our longstanding practice, only the agreement holder is a party to the Manufacturer Discount Program agreement with CMS, and the agreement holder is the entity subject to the rights and obligations of the Manufacturer Discount Program agreement, including the obligation to pay all invoiced amounts under such agreement.</P>
                    <P>In accordance with section 1860D-43(c)(1)(A) of the Act, we proposed to codify at § 423.2708(c) that an applicable drug of a manufacturer that does not participate in the Manufacturer Discount Program or has not entered into and does not have in effect a Manufacturer Discount Program agreement under section 1860D-14C(b) of the Act is not excluded from Part D coverage if CMS has made a determination that the availability of the applicable drug is essential to the health of Part D enrollees. In addition, we proposed to codify that, as specified in section 1860D-43(c)(2) of the Act, this exception to the exclusion from Part D coverage does not apply to any applicable drug or selected drug of a manufacturer for any period described in section 5000D(c)(1) of the Internal Revenue Code of 1986 with respect to such manufacturer.</P>
                    <P>Consistent with our prior interpretation of section 1860D-43(a) of the Act under the Coverage Gap Discount Program, for purposes of the Manufacturer Discount Program, the exclusion from Part D coverage applies only to applicable drugs and selected drugs not covered by a Manufacturer Discount Program agreement that is fully executed and in effect. Coverage under Medicare Part D is available to non-applicable drugs of a manufacturer regardless of whether the manufacturer participates in the Manufacturer Discount Program or has a Manufacturer Discount Program agreement in effect.</P>
                    <P>At § 423.2708(d), we proposed that non-applicable drugs, as we proposed to define the term in § 423.100, will continue to be coverable under Part D whether or not the manufacturer participates in the Manufacturer Discount Program or has a Manufacturer Discount Program agreement in effect.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a comment on the proposals in this section. The commenter expressed concern about limitations on enrollee access to drugs of a manufacturer that does not participate in the Manufacturer Discount Program, and recommended that CMS specify criteria for making a determination that an applicable drug is essential to the health of Part D enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates and shares the commenter's concern about 
                        <PRTPAGE P="17406"/>
                        enrollee access to applicable drugs of manufacturers that choose not to participate in the Manufacturer Discount Program. However, we decline to codify specifications for the exception provision at § 423.2708(c) at this time. Based on experience under the Coverage Gap Discount Program and the Manufacturer Discount Program to date, CMS does not anticipate using this exception, which has not been used to date under either program. We are concerned that proactive exemptions for certain drugs, or categories and classes of drugs, from the required conditions for Part D coverage would result in higher costs to Part D sponsors, beneficiaries, and the government because manufacturers of those drugs would have no incentive to participate in the Manufacturer Discount Program. Manufacturers should not expect to get their applicable drugs covered under Part D as a result of this exception.
                    </P>
                    <P>CMS is finalizing the regulation text at § 423.2708 without modification.</P>
                    <HD SOURCE="HD3">5. Applicable Discounts (§ 423.2712)</HD>
                    <P>Under the Manufacturer Discount Program, once an enrollee incurs costs exceeding the annual deductible specified in section 1860D-2(b)(1) of the Act, that is, the deductible under the defined standard benefit, manufacturer discounts are available in both the initial and catastrophic coverage phases of the benefit. The applicable discount lowers Part D sponsor liability on the negotiated price of the drug.</P>
                    <HD SOURCE="HD3">a. Defined</HD>
                    <P>Consistent with the definition in § 423.100 that we are finalizing in this final rule, “applicable discount” means, subject to the phase-ins and the straddle claims policy described in this section, with respect to an applicable drug of a manufacturer dispensed during a year to an applicable beneficiary who has—</P>
                    <P>• Not incurred costs, as determined in accordance with section 1860D-2(b)(4)(C) of the Act, for covered Part D drugs in the year that are equal to or exceed the annual out-of-pocket threshold specified in section 1860D-2(b)(4)(B)(i) of the Act for the year, 10 percent of the negotiated price of such drug; and</P>
                    <P>• Incurred costs, as determined in accordance with section 1860D-2(b)(4)(C) of the Act, for covered Part D drugs in the year that are equal to or exceed the annual out-of-pocket threshold specified in section 1860D-2(b)(4)(B)(i) of the Act for the year, 20 percent of the negotiated price of such drug.</P>
                    <P>We proposed to codify this policy at § 423.2712(a). Consistent with the statutory requirements and the Manufacturer Discount Program Final Guidance, the applicable discount is not available until the enrollee has incurred costs exceeding the annual deductible specified in section 1860D-2(b)(1) of the Act, regardless of whether the enrollee has to pay a deductible (for example, through eligibility for an income-related subsidy or enrollment in an enhanced benefit plan with a reduced or no deductible, or for a drug that is not subject to the deductible, such as a covered insulin product or an Advisory Committee on Immunization Practices (ACIP)-recommended adult vaccine).</P>
                    <P>Because the applicable discount and enrollee cost sharing are both calculated based on the negotiated price of the drug, as described in section II.A. of this final rule, the applicable discount will not affect the application of the standard 25 percent coinsurance under section 1860D-2(b)(2)(A) of the Act or the application of the copayment amount under section 1860D-2(b)(4)(A) of the Act unless, after the discount is applied to the negotiated price of the drug, the enrollee cost sharing specified under the plan would exceed such negotiated price minus the applicable discount. In such a situation, the enrollee cost sharing will be the negotiated price minus the applicable discount. We proposed to codify this policy at § 423.2712(g).</P>
                    <P>In accordance with section 1860D-14C(c)(1)(C) of the Act, we proposed to codify at § 423.2712(b) our policy that the value of the discount is calculated before the application of supplemental benefits, and at § 423.2712(c) that the applicable discount must be calculated before any coverage or financial assistance under another health or prescription drug benefit plan or program that provides prescription drug coverage or financial assistance.</P>
                    <HD SOURCE="HD3">b. Application of Discount Phase-in for Specified Manufacturers and Specified Small Manufacturers</HD>
                    <P>The IRA provides for lower applicable discounts for certain manufacturers' applicable drugs marketed as of August 16, 2022, during a multi-year phase-in period which concludes by 2031. Under section 1860D-14C(g)(4) of the Act, there are two such phase-ins: one for certain applicable drugs of specified manufacturers dispensed to applicable beneficiaries who are eligible for LIS under section 1860D-14(a) of the Act and one for certain applicable drugs of specified small manufacturers dispensed to all applicable beneficiaries.</P>
                    <P>The applicable discount paid by specified manufacturers for specified drugs dispensed to applicable beneficiaries who are eligible for LIS, referred to in the statute as the “specified LIS percent,” is defined in section 1860D-14C(g)(4)(B) of the Act. The discount paid by specified small manufacturers for specified drugs dispensed to all applicable beneficiaries, referred to in the statute as the “specified small manufacturer percent,” is defined in section 1860D-14C(g)(4)(C) of the Act. These provisions, which also set forth the criteria by which specified manufacturers and specified small manufacturers are defined, require such manufacturers to pay, when applicable, the phased-in discount.</P>
                    <HD SOURCE="HD3">(1) Applicable LIS Percent</HD>
                    <P>Under section 1860D-14C(g)(4)(B) of the Act, for an applicable drug of a specified manufacturer (as described at proposed § 423.2716(a)) that is marketed as of August 16, 2022, and dispensed for an applicable beneficiary who is a subsidy eligible individual (as defined in section 1860D-14(a)(3) of the Act), the applicable discount is as follows:</P>
                    <P>• For such individual who has not incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                    <P>++ For 2025, 1 percent;</P>
                    <P>++ For 2026, 2 percent;</P>
                    <P>++ For 2027, 5 percent;</P>
                    <P>++ For 2028, 8 percent; and</P>
                    <P>++ For 2029 and each subsequent year, 10 percent.</P>
                    <P>• For such individual who has incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                    <P>++ For 2025, 1 percent;</P>
                    <P>++ For 2026, 2 percent;</P>
                    <P>++ For 2027, 5 percent;</P>
                    <P>++ For 2028, 8 percent;</P>
                    <P>++ For 2029, 10 percent;</P>
                    <P>++ For 2030, 15 percent; and</P>
                    <P>++ For 2031 and each subsequent year, 20 percent.</P>
                    <P>We proposed to codify the policy for the applicable LIS percent at § 423.2712(d)(1).</P>
                    <HD SOURCE="HD3">(2) Applicable Small Manufacturer Percent</HD>
                    <P>Under section 1860D-14C(g)(4)(C) of the Act, for an applicable drug of a specified small manufacturer (as described at proposed § 423.2716(b)), that is marketed as of August 16, 2022, and dispensed for an applicable beneficiary, the applicable discount is as follows:</P>
                    <P>
                        • For such individual who has not incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—
                        <PRTPAGE P="17407"/>
                    </P>
                    <P>++ For 2025, 1 percent;</P>
                    <P>++ For 2026, 2 percent;</P>
                    <P>++ For 2027, 5 percent;</P>
                    <P>++ For 2028, 8 percent; and</P>
                    <P>++ For 2029 and each subsequent year, 10 percent; and</P>
                    <P>• For such individual who has incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                    <P>++ For 2025, 1 percent;</P>
                    <P>++ For 2026, 2 percent;</P>
                    <P>++ For 2027, 5 percent;</P>
                    <P>++ For 2028, 8 percent;</P>
                    <P>++ For 2029, 10 percent;</P>
                    <P>++ For 2030, 15 percent; and</P>
                    <P>++ For 2031 and each subsequent year, 20 percent. </P>
                    <FP>We proposed to codify the policy for the applicable small manufacturer percent at § 423.2712(d)(2).</FP>
                    <HD SOURCE="HD3">(3) Marketed as of the Date of Enactment</HD>
                    <P>Sections 1860D-14C(g)(4)(B)(i) and 1860D-14C(g)(4)(C)(i) of the Act limit the application of the discount phase-ins for specified manufacturers and specified small manufacturers, respectively, to drugs of such manufacturers that are “marketed as of the date of enactment” (that is, August 16, 2022). CMS interprets the reference to a drug that is marketed as of August 16, 2022 to refer to a drug that was marketed by the manufacturer on one specific, backward-looking date, that is, the date of enactment of the IRA. Accordingly, for purposes of identifying applicable drugs of specified manufacturers and specified small manufacturers subject to phase-ins, CMS will determine whether an applicable drug had Part D expenditures on or before August 16, 2022, and did not have a marketing end date on the FDA NDC SPL Data Elements File before August 17, 2022.</P>
                    <P>We proposed to codify this requirement at § 423.2712(d)(3).</P>
                    <HD SOURCE="HD3">c. Straddle Claims</HD>
                    <P>In the case of a claim for an applicable drug for an applicable beneficiary that “straddles” multiple phases of the benefit, section 1860D-14C(g)(4)(E) of the Act requires that for claims that do not fall entirely—</P>
                    <P>• Above the annual deductible specified in section 1860D-2(b)(1) of the Act, the manufacturer provides the applicable discount on only the portion of the negotiated price that falls above the deductible; and</P>
                    <P>• Below or entirely above the annual out-of-pocket threshold specified in section 1860D-2(b)(4)(B)(i) of the Act, the manufacturer provides the applicable discount on each portion of the negotiated price in accordance with this section based on the benefit phase into which each portion of the negotiated price falls.</P>
                    <P>We proposed to codify the policy for straddle claims at § 423.2712(e).</P>
                    <HD SOURCE="HD3">d. Claims Not Subject to Discount</HD>
                    <P>Since CMS is unable to ascertain from the PDE how much liability, if any, the Part D sponsor has on Medicare Secondary Payer (MSP) claims, we proposed to codify our policy under the Manufacturer Discount Program that discounts are not applied to MSP claims. In addition, since discounts are not applied to Medicaid subrogation claims under the Manufacturer Discount Program because drug costs reported on such claims are accounted for during the payment reconciliation process as contributing entirely to Covered D Plan Paid Amounts (CPP), we proposed to codify our policy that discounts are not paid on Medicaid subrogation claims involving an applicable drug. We proposed to codify those policies at § 423.2712(f)(1) and (2), respectively.</P>
                    <P>We proposed at § 423.2712(f)(3) to specify that non-standard format coordination of benefits claims involving an applicable drug are not subject to discounts under the Manufacturer Discount Program.</P>
                    <P>Lastly, at § 423.2712(f)(4) we proposed to codify our longstanding policy that manual claims involving an applicable drug with a service provider identification qualifier of “Other” are not subject to discounts under the Manufacturer Discount Program.</P>
                    <P>As discussed in section II.C.3. of this preamble, compounded drug products are excluded from the definition of applicable drug that we proposed to revise at § 423.100; as such, claims for Part D compounds are not subject to discounts under the Manufacturer Discount Program.</P>
                    <P>CMS received no comments on proposed § 423.2712 and we are finalizing this provision without modification.</P>
                    <HD SOURCE="HD3">6. Phase-In of Applicable Discounts (§§ 423.2716 Through 423.2728)</HD>
                    <P>The IRA establishes lower percentages for discounts on applicable drugs that are subject to phase-ins for specified manufacturers and specified small manufacturers. Since the discount reduces the plan liability for applicable drugs, Part D sponsors are responsible for covering the remaining amount of the negotiated price, less enrollee cost sharing, for applicable drugs subject to a phased-in discount percentage as discussed in this section.</P>
                    <P>Section 1860D-14C(b)(1)(A) of the Act specifies that a Manufacturer Discount Program agreement shall require the agreement holder to provide discounted prices for applicable drugs covered by its agreement when dispensed to applicable beneficiaries. The IRA does not provide a mechanism by which CMS could permit specified manufacturers or specified small manufacturers to “opt out” of the phase-in discounts. At § 423.2716, we proposed to codify, without modification, the criteria for phase-in eligibility for specified manufacturers and specified small manufacturers established in the Manufacturer Discount Program Final Guidance.</P>
                    <HD SOURCE="HD3">a. Specified Manufacturer</HD>
                    <P>Pursuant to section 1860D-14C(g)(4)(B)(ii) of the Act, a specified manufacturer is a manufacturer of an applicable drug that, in 2021 had—</P>
                    <P>
                        • A Coverage Gap Discount Program agreement in effect; 
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             A manufacturer that participated in the Coverage Gap Discount Program in 2021 by means of an arrangement whereby its labeler code(s) were listed on another manufacturer's Coverage Gap Discount Program agreement would be considered to have had an agreement in effect during 2021. See November 17, 2023 HPMS memorandum entitled, “Medicare Part D Manufacturer Discount Program: Methodology for Identifying Specified Manufacturers and Specified Small Manufacturers” for more information.
                        </P>
                    </FTNT>
                    <P>• Total expenditures for all of its specified drugs (as proposed at § 423.2704) covered by a Coverage Gap Discount Program agreement for 2021 and covered under Part D in 2021 represented less than 1.0 percent of total expenditures for all Part D drugs in 2021; and</P>
                    <P>• Total expenditures for all of its specified drugs that are single source drugs and biological products for which payment may be made under Part B in 2021 represented less than 1.0 percent of the total expenditures under Part B for all drugs or biological products in 2021.</P>
                    <P>We proposed to codify this eligibility criteria for specified manufacturers at § 423.2716(a).</P>
                    <P>
                        Pursuant to the aggregation rule set forth in section 1860D-14C(g)(4)(B)(ii)(II)(bb) of the Act, all entities, including corporations, partnerships, proprietorships, and other entities treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986 are treated as one manufacturer for purposes of this section. Our proposed definition of specified manufacturer is subject to the limitation with respect to manufacturer acquisitions proposed at § 423.2724 and discussed in section II.C.6.d. of this final rule.
                        <PRTPAGE P="17408"/>
                    </P>
                    <P>We proposed to codify the aggregation rule at § 423.2716(c).</P>
                    <HD SOURCE="HD3">b. Specified Small Manufacturer</HD>
                    <P>Pursuant to section 1860D-14C(g)(4)(C)(ii) of the Act, a specified small manufacturer is a manufacturer of an applicable drug that, in 2021—</P>
                    <P>• Is a specified manufacturer as described at proposed § 423.2716(a); and</P>
                    <P>• The total expenditures under Part D for any one of its specified small manufacturer drugs (as defined in § 423.2704) covered under a Coverage Gap Discount Program agreement for 2021 and covered under Part D in 2021 are equal to or greater than 80 percent of the total expenditures for all its specified small manufacturer drugs covered under Part D in 2021.</P>
                    <P>We proposed to codify this eligibility criteria for specified small manufacturers at § 423.2716(b).</P>
                    <P>Pursuant to the aggregation rule set forth in section 1860D-14C(g)(4)(C)(ii)(II)(bb) of the Act, all entities, including corporations, partnerships, proprietorships, and other entities treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986 are treated as one manufacturer for purposes of this section. Our proposed definition of specified small manufacturer is subject to the limitation with respect to manufacturer acquisitions proposed at § 423.2724 and discussed in section II.C.6.d. of this final rule.</P>
                    <P>We proposed to codify the aggregation rule at § 423.2716(c).</P>
                    <HD SOURCE="HD3">c. Determination of Phase-In Eligibility</HD>
                    <P>As discussed in section 50.1 of the Manufacturer Discount Program Final Guidance and the preamble to the proposed rule, CMS identifies which manufacturers qualify for phase-ins by analyzing Medicare Part B claims data, Part D PDE data, and ownership information submitted by manufacturers. The methodology used by CMS to identify manufacturers eligible for phase-ins was provided in the November 17, 2023 HPMS memorandum titled “Medicare Part D Manufacturer Discount Program: Methodology for Identifying Specified Manufacturers and Specified Small Manufacturers” (Manufacturer Discount Program Methodology).</P>
                    <P>The phase-in determination is a one-time assessment that CMS performs with respect to each manufacturer when it executes a Manufacturer Discount Agreement or when a manufacturer's labeler code(s) is first added to another manufacturer's Manufacturer Discount Program agreement. As such, the phase-in statuses have already been determined for likely the vast majority of manufacturers that will participate in the Manufacturer Discount Program during the phase-in periods (that is, through 2030). Codifying the methodology described in the Manufacturer Discount Program Methodology for identifying specified manufacturers and specified small manufacturers ensures consistency across the program by applying the same methodology to future cases of new phase-in determinations to be made under the regulations proposed in this rule (for example, when a new manufacturer enters into a Manufacturer Discount Program agreement with respect to 2027 or thereafter) as the methodology that was applied to the manufacturers currently participating in the Manufacturer Discount Program. We proposed to codify the methodology at § 423.2720.</P>
                    <P>Specifically, we proposed to codify at § 423.2720 that for each manufacturer with one or more FDA-assigned labeler codes covered by a Manufacturer Discount Program agreement, CMS will determine whether the manufacturer is a specified manufacturer or a specified small manufacturer when the manufacturer executes a Manufacturer Discount Program agreement, or, in the case of a manufacturer whose FDA-assigned labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement, when such labeler code(s) is first added to such agreement. In addition, we proposed to codify that in applying the aggregation rule at § 423.2716(c), CMS will attribute expenditures for a drug to a manufacturer based on the NDC(s) for the drug, as reported on PDE records. Specifically, CMS will match the labeler code extracted from the first 5 digits of each NDC to the manufacturer to whom the labeler code is assigned by the FDA.</P>
                    <P>As discussed in detail later in this section, we proposed at paragraph (a) of § 423.2720 the methodology for identifying “specified manufacturers”, at paragraph (b) of § 423.2720 the methodology for identifying “specified small manufacturers”, and at paragraph (c) the approach CMS will use to issue the phase-in determination notices once a phase-in determination is made.</P>
                    <P>For identification of a specified manufacturer, we proposed to codify at § 423.2720(a)(1) that a manufacturer is considered to have had a Coverage Gap Discount Program agreement in 2021, as specified at § 423.2716(a)(1), if the manufacturer (i) had a Coverage Gap Discount Program agreement in effect during 2021, or (ii) participated in the Coverage Gap Discount Program in 2021 by means of an arrangement whereby its labeler code(s) was covered by another manufacturer's Coverage Gap Discount Program agreement in effect during 2021.</P>
                    <P>CMS will calculate the three values needed for determining which manufacturers that had a Coverage Gap Discount Program agreement in 2021 are specified manufacturers and specified small manufacturers. The three values are:</P>
                    <P>• The manufacturer's percent share of Part D total expenditures,</P>
                    <P>• The manufacturer's percent share of Part B total expenditures, and</P>
                    <P>• Each drug's percent share of the specified manufacturer's Part D total expenditures.</P>
                    <P>The first value that needs to be determined is each manufacturer's share of Part D total expenditures, which will be used to determine if the manufacturer's total expenditures for all of its applicable drugs covered under a Coverage Gap Discount Program agreement(s) for 2021, and covered under Part D in 2021, represented less than 1.0 percent of total expenditures for all Part D drugs in 2021. CMS will identify manufacturers that meet this threshold for the specified manufacturer phase-in by first summing the 2021 Part D total expenditures for Part D drugs, then summing the 2021 Part D total expenditures for applicable drugs for each manufacturer, and finally, identifying each manufacturer for which 2021 Part D total expenditures for applicable drugs are less than 1.0 percent of all 2021 Part D total expenditures.</P>
                    <P>
                        The first step is to calculate the Part D total expenditures for 2021. We will calculate the Part D total expenditures for 2021 reported on all final action,
                        <SU>16</SU>
                        <FTREF/>
                         non-delete Prescription Drug Event (PDE) records submitted as of June 30, 2022, which represents the annual PDE data submission deadline for Part D payment reconciliation, for all Part D drugs dispensed in benefit year 2021. This value represents the Part D total expenditures and will be used as the denominator when calculating the percent share of Part D total expenditures attributable to each 
                        <PRTPAGE P="17409"/>
                        manufacturer's applicable drugs in step 3 below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             We use the term “final action” to describe the most recently accepted original, adjustment, or delete PDE record representing a single dispensing event. See the 2011 Regional Prescription Drug Event Data Technical Assistance Participant Guide, page 3-29, available at 
                            <E T="03">https://www.csscoperations.com/internet/csscw3.nsf/DIDC/FJUKANFCP1~Prescription%20Drug%20Program%20(Part%20D)~Training.</E>
                        </P>
                    </FTNT>
                    <P>The second step is to calculate each manufacturer's Part D total expenditures for applicable drugs for 2021. For purposes of this calculation, CMS will identify the National Drug Codes (NDCs) attributable to the manufacturer that have a Marketing Category Code of `NDA', `BLA', or `NDA AUTHORIZED GENERIC' on the NDC SPL Data Elements (NSDE) File maintained by the Food and Drug Administration (FDA). CMS will attribute an NDC as reported on the PDE record to the manufacturer using the labeler code extracted from the first 5 digits of each NDC. CMS will calculate the Part D total expenditures for each relevant NDC attributable to the manufacturer as reported on all final action, non-delete PDE records submitted as of June 30, 2022 for applicable drugs dispensed in benefit year 2021. CMS will then sum the Part D total expenditures for all relevant NDCs attributable to the manufacturer—that is, the Part D total expenditures for all applicable drugs of all manufacturers treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986, as identified by the ownership information submitted and attested to by the manufacturer (as described in the aggregation rule proposed at § 423.2716(c)).</P>
                    <P>The third step is to calculate each manufacturer's percent share of Part D total expenditures for 2021. CMS will divide the Part D total expenditures for applicable drugs of the manufacturer, determined in step 2 above, by the Part D total expenditures for all Part D drugs, determined in step 1 above, and then multiply by 100 to get the manufacturer's percent share. If a manufacturer's Part D total expenditures for its applicable drugs are less than 1.0 percent of the 2021 Part D total expenditures, CMS will consider the manufacturer to have satisfied the Part D total expenditure criterion for specified manufacturer phase-in eligibility.</P>
                    <P>We proposed to codify this part of the methodology at § 423.2720(a)(2).</P>
                    <P>Next, CMS will determine each manufacturer's share of Part B total expenditures, which will be used to determine if the manufacturer's total expenditures for all of its specified drugs that are single source drugs or biological products represented less than 1.0 percent of the total expenditures for all drugs or biologicals under Part B in 2021, excluding expenditures for a drug or biological that are bundled or packaged into payment for another service. This calculation involves three steps: identifying 2021 Part B total expenditures for drugs and biological products, identifying the 2021 Part B total expenditures for single-source drugs and biological products for each manufacturer that had a Coverage Gap Discount Program agreement(s) in 2021, and identifying eligible manufacturers for which Part B total expenditures for single source drugs or biological products represent less than 1.0 percent of total expenditures for drug and biological products under Part B for 2021.</P>
                    <P>The first step is to calculate Part B total expenditures for all drugs and biological products for 2021. CMS will identify all Healthcare Common Procedure Coding System (HCPCS) codes for drugs and biological products. Then, CMS will calculate Part B Carrier, durable medical equipment (DME), and Outpatient Medicare Part B total expenditures for drug and biological products for Fee-for-Service claim line items with a drug- or biological product-related HCPCS code, submitted as of December 31, 2022, which represents the Medicare Fee-For-Service submission deadline for CY 2021.</P>
                    <P>The second step is to calculate each manufacturer's Part B total expenditures for applicable drugs that are single-source drugs and biological products for 2021. CMS will first map the HCPCS codes identified in step 1 above to NDCs using the NDC-HCPCS Crosswalk file provided as part of the CMS ASP Pricing File and the Pricing, Data Analysis and Coding (PDAC) HCPCS to NDC crosswalk file. Since the ASP NDC-HCPCS Crosswalk file is not a comprehensive list of all drugs/NDCs available in the United States, a Medi-Span Generic Product Identifier (GPI-14) expansion is used to help identify all NDCs associated with the HCPCS codes. We define a single source drug or biological following the definition in section 1847A(c)(6)(D) of the Act and we are identifying NDCs for single source drugs using Medi-Span and the FDA NSDE marketing category data, or biological products using the FDA Purple Book. A HCPCS code is considered to be indicative of a single source drug or biological product if each NDC associated with the HCPCS code is for a single source drug or biological product. The corresponding NDCs are used to determine the labeler codes for each applicable HCPCS code. CMS will match the labeler code extracted from the first 5 digits of each NDC to the manufacturer. Since a HCPCS code can be mapped to multiple NDCs and labeler codes, it can also be associated with multiple manufacturers. While Part B single source drugs or biological products can be mapped to a particular HCPCS code, mapping applicable Part B expenditures to a particular manufacturer when a particular HCPCS code may reflect drugs of multiple manufacturers can be challenging. For this reason, CMS will only count the payments associated with a HCPCS code toward a manufacturer's 2021 Part B total expenditures if the HCPCS code is only mapped to drugs of that same manufacturer, consistent with the aggregation rule proposed at § 423.2716(c).</P>
                    <P>The third step is to calculate each manufacturer's percent share of Part B total expenditures for 2021. CMS will divide the Part B total expenditures for the applicable drugs that are single source drugs and biological products of the manufacturer, determined in step 2 above, by the Part B total expenditures for all drugs and biological products, determined in step 1 above, and then multiply by 100 to get the manufacturer's percent share. If a manufacturer's Part B total expenditures are less than 1.0 percent of the 2021 Part B total expenditures, CMS will consider the manufacturer to have satisfied the Part B total expenditure criterion for the specified manufacturer phase-in eligibility.</P>
                    <P>We proposed to codify this part of the methodology at § 423.2720(a)(3).</P>
                    <P>The last value that must be determined for each specified manufacturer is the total expenditures under Part D for any one of the manufacturer's specified drugs covered under a Coverage Gap Discount Program agreement(s) for 2021, and covered under Part D in 2021. This will be used to determine if the manufacturer's total expenditures for one specified drug are equal to or greater than 80 percent of the total expenditures for all of its specified drugs covered under Part D in 2021 such that the manufacturer is eligible for the specified small manufacturer phase-in.</P>
                    <P>
                        The first step is to aggregate all NDCs for applicable drugs reported on PDEs for each specified manufacturer that have the same active moiety for drug products, or same active ingredient for biological products, and with the same holder of the NDA or BLA. To determine one drug's share of a manufacturer's Part D total expenditures, which we will use to identify specified small manufacturers, we first note that for drug products, one specified small manufacturer drug will include all dosage forms and strengths of a drug with the same active moiety 
                        <PRTPAGE P="17410"/>
                        and the same holder of the NDA,
                        <SU>17</SU>
                        <FTREF/>
                         inclusive of products that are marketed pursuant to different NDAs. For biological products, one specified small manufacturer drug will include all dosage forms and strengths of the biological product with the same active ingredient and the same holder of the BLA,
                        <SU>18</SU>
                        <FTREF/>
                         inclusive of products that are marketed pursuant to different BLAs. CMS will identify the holder of the NDA/BLA for a drug or biological product as reported in Drugs@FDA or FDA Purple Book. If a drug is a fixed combination drug 
                        <SU>19</SU>
                        <FTREF/>
                         with two or more active moieties/active ingredients, the distinct combination of active moieties/active ingredients will be considered as one active moiety/active ingredient for the purpose of identifying a specified small manufacturer drug. Therefore, all formulations of this distinct combination with the same NDA/BLA holder will be aggregated across all dosage forms and strengths of the fixed combination drug. A product containing only one (but not both) of the active moieties/active ingredients with the same NDA/BLA holder will not be aggregated with the formulations of the fixed combination drug and will be considered a separate specified small manufacturer drug. CMS will attribute Part D expenditures for a drug, including authorized generic drugs and repackaged and relabeled drugs, to a specified manufacturer based on the NDC(s) for the drug, as reported on PDE records. Specifically, CMS will match the labeler code extracted from the first 5 digits of each NDC to the manufacturer. (See the aggregation rule proposed at § 423.2716(c)).
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             As described in section 505(c) of the FD&amp;C Act.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             As described in section 351(a) of the PHS Act.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             As described in 21 CFR 300.50.
                        </P>
                    </FTNT>
                    <P>The second step is to calculate the Part D total expenditures for each aggregated drug for 2021. CMS will calculate the Part D total expenditures for each aggregated drug attributable to the manufacturer as identified in step 1 by summing the Part D total expenditures for all NDCs under each aggregated drug as reported on all final action, non-delete PDE records submitted as of June 30, 2022, for drugs dispensed in benefit year 2021.</P>
                    <P>The third step is to calculate each drug's percent share of the specified manufacturer's Part D total expenditures for applicable drugs for 2021. CMS will divide the Part D total expenditures for each aggregated drug, determined in step 2, by the Part D total expenditures for all applicable drugs of the specified manufacturer, and then multiply by 100 to get the percent share. Specified manufacturers that have 2021 Part D total expenditures for a single specified drug that are equal to or greater than 80 percent of the specified manufacturer's Part D total expenditures for all specified drugs are considered to have met the eligibility criteria for specified small manufacturers and are eligible for the specified small manufacturer phase-in.</P>
                    <P>We proposed to codify this part of the methodology at § 423.2720(b).</P>
                    <P>Finally, at paragraph (c)(1) of § 423.2720, we proposed to specify that CMS will issue a phase-in determination notice to each manufacturer that has executed and has in effect a Manufacturer Discount Program agreement when such determination is made, delivered by electronic mail, to the primary point of contact as identified by the manufacturer. At paragraph (c)(2) of § 423.2720, we proposed to specify that in the case of a manufacturer that participates in the Manufacturer Discount Program by means of an arrangement whereby its labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement, CMS will issue a phase-in eligibility determination notice to the agreement holder.</P>
                    <P>For purposes of identifying manufacturers eligible for phase-ins, the aggregation rule at section 1860D-14C(g)(4)(B)(ii)(II)(bb) of the Act for specified manufacturers and section 1860D-14C(g)(4)(C)(ii)(II)(bb) of the Act for specified small manufacturers requires that CMS treats as a single manufacturer all entities that are treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986. As noted previously, we proposed to codify the aggregation rule at § 423.2716(c). The statute, at section 1860D-14C(g)(4)(B)(ii)(II)(bb) of the Act for specified manufacturers and section 1860D-14C(g)(4)(C)(ii)(II)(bb) of the Act for specified small manufacturers, also requires that manufacturers provide and attest to necessary information as specified by CMS. Because CMS does not have information about which entities are treated as a single employer under the Internal Revenue Code of 1986, manufacturers that wish to participate in the Manufacturer Discount Program must submit and attest to information about the company and its products in order for CMS to make a determination about phase-in eligibility.</P>
                    <HD SOURCE="HD3">d. Effect of Manufacturer Acquisition on Phase-In Eligibility</HD>
                    <P>Section 1860D-14C(g)(4)(B)(ii)(III) of the Act requires that when a specified manufacturer is acquired after 2021 by another manufacturer that is not a specified manufacturer, the acquired manufacturer is no longer a specified manufacturer effective at the beginning of the plan year immediately following the acquisition. For acquisitions before 2025, the change is effective January 1, 2025. Section 1860D-14C(g)(4)(C)(ii)(III) of the Act establishes a similar requirement for specified small manufacturers: when acquired after 2021 by a manufacturer that is not a specified small manufacturer, such manufacturer is no longer a specified small manufacturer effective at the beginning of the plan year immediately following the acquisition (or January 1, 2025, for acquisitions before 2025).</P>
                    <P>
                        While the statute is explicit that an acquired specified manufacturer or specified small manufacturer loses that specific phase-in status upon acquisition by another manufacturer that is not a specified manufacturer or a specified small manufacturer, respectively, it does not expressly address whether such acquired manufacturers assume the phase-in eligibility of the acquiring manufacturer or lose all phase-in eligibility (for example, a specified manufacturer is acquired by a specified small manufacturer or a specified small manufacturer is acquired by a specified manufacturer). Similarly, the statute does not expressly address what happens if a specified manufacturer or a specified small manufacturer acquires a manufacturer that CMS determined was not eligible for either phase-in. Consistent with our approach to acquisitions under the Manufacturer Discount Program thus far, we proposed at § 423.2724 to review phase-in status bidirectionally such that acquired manufacturers may gain or lose phase-in eligibility as the result of an acquisition. In other words, regardless of the phase-in status of the acquiring manufacturer or the acquired manufacturer at the time of the acquisition, when a manufacturer acquires another manufacturer (that is, the acquired manufacturer becomes part of such acquiring manufacturer under the aggregation rule at § 423.2716(c)), the acquired manufacturer will assume the phase-in status of the acquiring manufacturer, as of the effective date following the acquisition discussed later in this section. CMS believes this bidirectional policy best aligns with the statutory structure and purpose of the 
                        <PRTPAGE P="17411"/>
                        phase-ins. First, we believe this policy is most consistent with the directive in sections 1860D-14C(g)(4)(B)(ii)(II)(bb) and 1860D-14C(g)(4)(C)(ii)(II)(bb) of the Act to treat all entities, including corporations, partnerships, proprietorships, and other entities, treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986 as one manufacturer for the purposes of the phase-ins. Without applying the effect of acquisitions bidirectionally, manufacturers that are members of the same controlled group could have different phase-in eligibility statuses as a result of an acquisition. Additionally, while a specified small manufacturer that is acquired by a specified manufacturer will lose its specified small manufacturer status consistent with section 1860D-14C(g)(4)(C)(ii)(III) of the Act, such manufacturer becomes a specified manufacturer under this policy, rather than losing eligibility for phase-in altogether.
                    </P>
                    <P>We proposed that all changes to a manufacturer's phase-in status as a result of an acquisition will become effective on January 1 of the year following the acquisition or, in the case of an acquisition before 2025, effective January 1, 2025. This aligns the effective date of changes to a manufacturer's phase-in status across all acquisitions with the requirements in sections 1860D-14C(g)(4)(B)(ii)(III) and 1860D-14C(g)(4)(C)(ii)(III) of the Act discussed previously and is consistent with our approach to date for acquisitions that have already occurred. Operationally, adopting a January 1 effective date minimizes burden on Part D sponsors who would otherwise need to regularly make additional claims processing changes to accommodate phase-in status changes throughout the year given the frequency of corporate ownership changes in the pharmaceutical industry. It also minimizes any need for Part D sponsors to make retrospective PDE adjustments if, for example, CMS does not become aware of the acquisition until after it occurs.</P>
                    <P>In sum, in alignment with the statutory requirements and the procedures already in place under the Manufacturer Discount Program, we proposed at § 423.2724 to codify a regulatory policy for manufacturer acquisitions where, regardless of the manufacturer's phase-in eligibility status prior to the acquisition, once acquired, the acquired manufacturer is recognized as having the phase-in eligibility status of the acquiring manufacturer. Consistent with the statutory requirements related to the loss of phase-in eligibility, and to minimize any potential impact on Part D sponsors or manufacturers as a result of changes to manufacturer phase-in status in the middle of a plan year, we also proposed at § 423.2724 that any change in phase-in eligibility status as a result of an acquisition, regardless of whether the acquired manufacturer gains or loses phase-in eligibility, would be effective on January 1 of the year following the acquisition.</P>
                    <HD SOURCE="HD3">e. Recalculation</HD>
                    <P>We proposed to codify the recalculation policy discussed in section 50.2.2 of the Manufacturer Discount Program Final Guidance, with certain modifications, at § 423.2728.</P>
                    <P>As discussed in the guidance, while the requirements to qualify as a specified manufacturer or specified small manufacturer are set forth in statute, we recognize that, while unlikely, a manufacturer may wish to raise concerns with the outcome of the application of those statutory requirements. As such, CMS established a mechanism for manufacturers that wish to request a recalculation of their phase-in eligibility determination. Such requests can only be filed by the manufacturer that received the determination. We proposed to codify this requirement at § 423.2728(a).</P>
                    <P>Under the recalculation policy, a manufacturer that seeks a recalculation of their phase-in eligibility determination must file the request with CMS no later than 30 calendar days from the date the eligibility determination is electronically sent to the manufacturer. The request must clearly describe the issue(s) forming the basis of the request for recalculation, and include any relevant supporting information. We proposed to codify these requirements at § 423.2728(b).</P>
                    <P>After consideration of the issues raised in a recalculation request, CMS will decide whether to perform the recalculation, and will issue a written decision to the manufacturer that will include CMS's decision about whether to perform the requested recalculation and, if such recalculation is performed, the resulting eligibility determination. The decision is final and binding, subject to the requirements of the Manufacturer Discount Program under section 1860D-14C of the Act and the Manufacturer Discount Program agreement. We proposed to codify this policy at § 423.2728(c).</P>
                    <P>Finally, at § 423.2728(d), we proposed to limit the recalculation process to requests that meet the requirements proposed in § 423.2728(a) and (b). The recalculation request process cannot be used to request or be granted an exception to the requirements set forth in statute that determine eligibility for the specified manufacturer or specified small manufacturer phase-in.</P>
                    <P>CMS received two comments regarding the phase-in methodology and summaries of the comments with our responses are below.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter was opposed to aspects of our proposed methodology to determine specified small manufacturer eligibility. Specifically, the commenter objected to our proposal to calculate total expenditures under Part D for each applicable drug of a manufacturer based exclusively on PDE records and urged CMS to instead use PDE data as prima facie evidence, rather than the sole determinant of Part D total expenditures, and to consider, as part of CMS's recalculation process, other sources of evidence for Part D total expenditures, including data submitted to CMS by the manufacturer. The commenter argued that CMS must include all costs directly related to the dispensing of a covered drug when determining Part D total expenditures, even if those costs are not included in the PDE data set. The commenter also argued that, because of supposed flaws in the PDE data set and because PDE data is not relied on exclusively in certain other contexts, it cannot be relied on exclusively to determine the Part D total expenditures for applicable drugs of a manufacturer.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges that certain aspects of our Manufacturer Discount Program phase-in methodology as set forth in applicable guidance are the subject of recent litigation, including 
                        <E T="03">Servier Pharmaceuticals LLC</E>
                         v. 
                        <E T="03">Becerra,</E>
                         No. 1:24-cv-02664 (D.D.C.) and related appeal 
                        <E T="03">Servier Pharmaceuticals LLC</E>
                         v. 
                        <E T="03">Kennedy,</E>
                         No. 25-5054 (D.C. Cir.) (hereafter referred to as 
                        <E T="03">Servier</E>
                        ) and 
                        <E T="03">PharmaEssentia USA Corp.</E>
                         v. 
                        <E T="03">HHS,</E>
                         No. 1:24-cv-03346 (D.D.C.) (hereafter referred to as 
                        <E T="03">PharmaEssentia</E>
                        ). The district court in 
                        <E T="03">Servier</E>
                         upheld CMS's determination that Servier fails to qualify as a specified small manufacturer. Servier appealed the district court's decision, which appeal is pending in the U.S. Court of Appeals for the D.C. Circuit. The district court in 
                        <E T="03">PharmaEssentia</E>
                         vacated CMS's determination that PharmaEssentia failed to qualify as a specified small manufacturer and remanded the matter back to CMS after expressly recognizing that CMS might reach the same conclusion after further proceedings.
                    </P>
                    <P>
                        CMS appreciates the comment, but we will continue to use PDE data as the basis for calculating total expenditures under Part D because PDEs are the 
                        <PRTPAGE P="17412"/>
                        records used to capture Part D expenditures. CMS created the Medicare Drug Data Processing System (DDPS) to collect and maintain records for all Part D claims, and the agency requires Part D sponsors to submit a PDE for every claim. The PDE contains information about payment liability of the plan and the enrollee. As discussed in more detail in section II.C.13 of this final rule, PDEs are subject to a robust editing process to verify their accuracy. PDE records are used to pay Part D sponsors for administering the prescription drug benefit and to calculate manufacturer discounts under the Coverage Gap Discount Program and the Manufacturer Discount Program. We note that while PDEs, like any data set, may contain errors, Part D sponsors have significant financial incentive to submit timely and accurate PDE records, in addition to being legally required to do so. As a result, we continue to believe that it is appropriate and consistent with the statute to calculate Part D total expenditures based on PDE data when determining a manufacturer's phase-in eligibility under the Manufacturer Discount Program.
                    </P>
                    <P>
                        Nevertheless, consistent with the district court's opinion in 
                        <E T="03">PharmaEssentia,</E>
                         we are clarifying that a manufacturer may provide additional information, as part of a timely recalculation request under the process described at § 423.2728, that the manufacturer asserts is evidence of Part D total expenditures that were not reported on PDEs. CMS will evaluate the information to determine if it is sufficient to merit consideration and what, if any, further investigation of the information provided is necessary to determine if there were actually paid Part D claims. If CMS determines based upon the additional information, and any additional investigation, that there were paid Part D claims that were not reported on PDEs that constitute Part D total expenditures under section 1860D-14C(g)(4)(D) of the Act, CMS will include those expenditures in the recalculation, consistent with the requirements of this section.
                    </P>
                    <P>For clarity and precision, we are making a minor change in the regulation text at § 423.2728(b) to specify that supporting documentation for recalculation requests must be included with the recalculation request.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter also opposed aspects of CMS's proposed methodology for determining specified small manufacturer phase-in eligibility. Specifically, the commenter disagreed with our proposal to attribute 2021 total expenditures under Part D to a manufacturer based on the labeler code for purposes of identifying each specified drug of a manufacturer and calculating the Part D total expenditures for such drugs under § 423.2720(b). Instead, the commenter recommended that CMS attribute total expenditures for a drug to the holder of the New Drug Application (NDA) for that drug. The commenter stated that in other CMS programs that utilize similar statutory definitions of manufacturer as the definition found in section 1860D-14C(g)(5) of the Act, the NDA holder is identified as a manufacturer. The commenter further recommended that even if CMS were not to attribute expenditures based on the entity that holds the NDA for the applicable drug, the agency should consider evidence in addition to the labeler code when attributing total expenditures. The commenter stated that, while the labeler code may accurately reflect the manufacturer in many cases and can be used as a first step, the agency should consider additional evidence where appropriate to identify the manufacturer.
                    </P>
                    <P>The commenter also opined that, if CMS alters the methodology used to determine phase-in eligibility, the changes should be applied retroactively to phase-in determinations made for manufacturers that have already entered into agreements to participate in the Manufacturer Discount Program or at least to those phase-in determinations that manufacturers have previously challenged as erroneous. Relatedly, the commenter further recommends that CMS establish a mechanism to adjust manufacturer liability on previously invoiced discount amounts of a manufacturer affected by an erroneous determination that the manufacturer is not a specified small manufacturer, and suggests that the dispute resolution framework at § 423.2764 should be used for this purpose.</P>
                    <P>
                        <E T="03">Response:</E>
                         While we recognize that the statutory definition of manufacturer at section 1860D-14C(g)(5) of the Act may be similar to the statutory definition of manufacturer used in other programs, we decline to adopt the commenter's suggestion that such similarities in manufacturer definitions indicate that for purposes of the Manufacturer Discount Program, CMS should attribute Part D expenditures for a specified drug to the entity that holds the NDA of such drug. We continue to believe that the labeler code provides the most appropriate basis by which to attribute Part D expenditures to a manufacturer for purposes of making phase-in eligibility determinations under the Manufacturer Discount Program and that this methodology is consistent with section 1860D-14C of the Act, including CMS's longstanding practices of entering into the agreement for participation in the Coverage Gap Discount Program and Manufacturer Discount Program with the entity that meets the statutory definition of manufacturer based on such entity being the holder of the FDA-assigned labeler code(s) for the applicable drugs to which the agreement will apply.
                        <SU>20</SU>
                        <FTREF/>
                         As explained in the Manufacturer Discount Program Methodology, CMS identifies each Part D expenditure for a drug using the unique NDC reported on the PDE record for the expenditure and attributes that expenditure to the one manufacturer uniquely assigned the labeler code for that drug as reflected in the first five digits of the NDC.
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             As discussed earlier, such agreements may also include the labeler codes assigned by the FDA to another manufacturer, but only when such manufacturers have entered into an arrangement whereby the agreement holder lists such labeler codes on its agreement and all other applicable requirements are met.
                        </P>
                    </FTNT>
                    <P>CMS agrees with the commenter's recommendation that there should be a mechanism to adjust previously invoiced discounts of a manufacturer impacted by an erroneous determination about the manufacturer's phase-in eligibility. Prior to any correction of PDE records or discounts, a determination would have to be made that the phase-in eligibility status was incorrect. The process established in the Manufacturer Discount Program Final Guidance and codified at § 423.2728 for requesting such corrections is the recalculation process. CMS has also made a small number of corrections to manufacturer phase-in status in the first year of the program through own-motion review.</P>
                    <P>
                        Retrospective adjustment of previously invoiced discounts or previously submitted PDE records can occur for reasons not limited to a retrospective change to or correction of a manufacturer's phase-in status. While retrospective application of a correction would depend on the specific situation, and may involve adjustments of overpayments or underpayments by a manufacturer, CMS has already established a process for adjusting previously invoiced manufacturer discounts, which is the PDE outlier process described in the January 17, 2025 HPMS memorandum, 
                        <E T="03">Prescription Drug Event (PDE) Analysis website for CMS Data Quality Review Outliers, Withheld and Invoiced Outliers, and Reviews of Invoiced Data Disputed by Manufacturers.</E>
                    </P>
                    <P>
                        After consideration of the comments received on these sections of our 
                        <PRTPAGE P="17413"/>
                        proposal, and for the reasons described, we are finalizing the regulation text at §§ 423.2716 through 423.2728 as proposed, with minor modifications at § 423.2728(b) to further clarify our expectation that such supporting documentation must be included with the timely recalculation request.
                    </P>
                    <HD SOURCE="HD3">7. Use of a Third Party Administrator (§ 423.2732)</HD>
                    <P>We proposed to codify the agency's engagement of a TPA at § 423.2732. Specifically, we proposed at § 423.2732(a) that CMS will engage a TPA to assist in the administration of the Manufacturer Discount Program, which may include and is not limited to facilitating Manufacturer Discount Program invoicing, the receipt and distribution of funds of a manufacturer, and the dispute resolution process described in § 423.2764.</P>
                    <P>We proposed at § 423.2732(b)(1) that agreement holders must enter into and have in effect an agreement with the TPA and that such TPA agreement will only terminate upon the termination of the agreement holder's Manufacturer Discount Program agreement. We further proposed at § 423.2732(b)(2) that agreement holders must establish and maintain electronic connectivity with the TPA for the purpose of timely transmission of data and funds.</P>
                    <P>We received no comments on proposed § 423.2732 and are finalizing this provision as proposed.</P>
                    <HD SOURCE="HD3">8. Requirement for Point-of-Sale Discounts (§§ 423.505 and 423.2736)</HD>
                    <HD SOURCE="HD3">a. Point-of-Sale Discounts</HD>
                    <P>Under section 60.1 of the Manufacturer Discount Program Final Guidance, Part D sponsors must provide applicable discounts on applicable drugs at the point of sale on behalf of the manufacturer. We proposed to codify this policy at § 423.2736(a). In order to provide point-of-sale discounts, plan sponsors must determine whether an enrollee is an applicable beneficiary (as defined at § 423.100), including where the enrollee falls in the phases of the Part D benefit based on their gross drug spend and incurred costs at the time an applicable drug is dispensed; whether a drug is an applicable drug (as defined at § 423.100); and the amount of the discount (in accordance with proposed § 423.2712, which we are finalizing in this final rule).</P>
                    <P>Part D regulations at part 423 subpart K set forth the requirements for Part D contracts between Part D sponsors and CMS. We proposed a conforming change to revise the text of § 423.505(b)(24) to specify that Part D sponsors must provide applicable discounts on applicable drugs when dispensed to applicable beneficiaries in accordance with the requirements in subpart W of part 423 for the Coverage Gap Discount Program and the requirements in subpart AA of part 423 for the Manufacturer Discount Program.</P>
                    <HD SOURCE="HD3">b. Direct Member Reimbursement</HD>
                    <P>As established under section 60.1.1 of the Manufacturer Discount Program Final Guidance, Part D sponsors must provide applicable discounts on claims for applicable drugs submitted by applicable beneficiaries as direct member reimbursements (DMRs), including out-of-network and in-network paper claims, if such claims are payable under the Part D plan. While the sponsor must account for the discount in adjudicating the DMR request and the associated PDE submitted to CMS, the point-of-sale requirement does not apply. We proposed codifying this policy at § 423.2736(b). As we explained in the proposed rule, for purposes of discounting DMR claims for prescriptions filled at out-of-network pharmacies, the negotiated price means the plan allowance as set forth in § 423.124.</P>
                    <HD SOURCE="HD3">c. Pharmacy Prompt Payment</HD>
                    <P>Pursuant to section 1860D-14C(c)(1)(B) of the Act, and consistent with section 60.3 of the Manufacturer Discount Program Final Guidance and CMS pharmacy prompt payment requirements at § 423.520, we proposed at § 423.2736(c) that Part D sponsors must reimburse a network pharmacy (as defined in § 423.100) the amount of the applicable discount no later than the applicable number of calendar days (as defined in § 423.100) after the date of dispensing (as defined in § 423.100) of an applicable drug. As described in the definition of date of dispensing, for long-term care and home infusion pharmacies, the date of dispensing can be interpreted as the date the pharmacy submits the claim for reimbursement.</P>
                    <HD SOURCE="HD3">d. Prescription Drug Event Requirements</HD>
                    <P>We proposed to codify at § 423.2736(d) a requirement that Part D sponsors must report the applicable discounts made available to their enrollees under the Manufacturer Discount Program on the PDE records associated with such discounts. We explained that this information is later used for the cost-based reconciliation of prospective Manufacturer Discount Program payments made to each sponsor (as proposed at § 423.2744(c)) and to invoice agreement holders for reimbursement of the amount advanced on their behalf by the Part D sponsor at the point of sale (as proposed at § 423.2756(a)).</P>
                    <HD SOURCE="HD3">e. Retroactive Adjustments</HD>
                    <P>Under section 60.1.5 of the Manufacturer Discount Program Final Guidance, Part D sponsors must make retroactive adjustments to applicable discounts as necessary to reflect applicable changes, including changes to the claim, beneficiary eligibility, or benefit phase determined after the date of dispensing. We proposed to codify this policy at § 423.2736(e).</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a comment in support of our proposal at § 423.505 to require Part D sponsors to provide applicable discounts on applicable drugs at the point of sale on behalf of the manufacturer, in alignment with the process that has been used under the Coverage Gap Discount Program since 2011.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several supportive comments on our proposal at § 423.2736(c) to require Part D sponsors to reimburse a network pharmacy the amount of the applicable discount no later than the applicable number of calendar days after the date of dispensing of an applicable drug. These commenters stated that clear prompt payment requirements promote consistent administration of the Manufacturer Discount Program, reduce payment delays that can create operational burdens at the pharmacy counter, support continuity of care for Part D enrollees, and strengthen the integrity of the redesigned Part D benefit.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of our prompt payment proposals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS ensure Manufacturer Discount Program discounts are applied correctly at the point of sale so that increased out-of-pocket costs do not result in access disruptions. Another commenter recommended that enrollees be provided with real-time data regarding the impact of discounts under the Manufacturer Discount Program on the enrollee's progress toward the Part D out-of-pocket maximum.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback but decline to make the requested changes. Because manufacturer discounts generally do not impact the amount of enrollee cost sharing, are applied at the point of sale, and reduce plan liability for the cost of Part D drugs, we do not expect the 
                        <PRTPAGE P="17414"/>
                        Manufacturer Discount Program to have any negative impact on enrollee access or out-of-pocket costs. As noted in section II.C.15 of this final rule, beneficiary protections established under subpart M of part 423 continue to apply and are separate from the Manufacturer Discount Program. Enrollees maintain the right to request a coverage determination from their plan or file a grievance.
                    </P>
                    <P>Consistent with section 1860D-14C(g)(4) of the Act, applicable discounts under the Manufacturer Discount Program are not counted toward an enrollee's incurred costs. Thus, while we agree that it is important to provide enrollees with accurate and timely information about their benefits and liabilities with respect to their Part D coverage, we are not making any changes to existing policies related to enrollee notification requirements. Part D enrollees will continue to receive information about Part D coverage of their medications through existing vehicles, including the Part D explanation of benefits as required under § 423.128(e).</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS establish timing requirements for plans to submit PDE records.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS established deadlines for the timely submission of PDE records at the start of the Part D program, which were recently codified at 42 CFR 423.325. We are finalizing changes to those requirements that are unrelated to the Manufacturer Discount Program in this final rule, which are described in section IV.K.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted the unique integrated financing structure of PACE and urged CMS to monitor implementation of the Manufacturer Discount Program carefully to ensure PACE organizations have the technical support and guidance needed to administer manufacturer discounts.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's feedback and agree that it is important for CMS to monitor implementation of the Manufacturer Discount Program and provide guidance and technical support to PACE organizations. Recognizing that implementation of the Manufacturer Discount Program necessitated significant operational changes for PACE organizations, including reporting an expanded set of data elements on PDE submissions and understanding and developing capabilities related to the dispute resolution process for the Manufacturer Discount Program, CMS issued guidance specific to PACE organizations in HPMS memoranda, titled “PACE Participation in the Manufacturer Discount Program beginning January 1, 2025,” issued on January 26, 2024, and “2025 Prescription Drug Event (PDE) File Layout Updates for all Part D Plan Sponsors, and Additional 2025 Changes to PDE Reporting for PACE Organizations” issued on March 8, 2024. In addition, CMS held multiple technical assistance and training sessions to help PACE organizations prepare for changes related to implementation of the Manufacturer Discount Program.
                        <SU>21</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             CMS provided training sessions for PACE Organizations at two User Group Calls held on February 14, 2024 and May 22, 2024, and also provided training via a presentation and question and answer session at the National PACE Association Spring Policy Forum, on March 11, 2024.
                        </P>
                    </FTNT>
                    <P>
                        We will continue to issue guidance and support, as needed, regarding the Manufacturer Discount Program, and we encourage interested parties to monitor for additional guidance or information issued through HPMS or posted on our Manufacturer Discount Program web page at 
                        <E T="03">https://www.cms.gov/medicare/coverage/prescription-drug-coverage/part-d-information-pharmaceutical-manufacturers.</E>
                         Part D sponsors with questions regarding the Manufacturer Discount Program can reach out to their CMS account manager or submit questions to 
                        <E T="03">PartDManufacturerDiscountProgram@cms.hhs.gov.</E>
                    </P>
                    <P>After consideration of the public comments we received on this section, we are finalizing without modification our proposals at §§ 423.505 and 423.2736.</P>
                    <HD SOURCE="HD3">9. Negative Invoice Payment Process for Part D Sponsors (§ 423.2740)</HD>
                    <P>In certain instances in the quarterly Manufacturer Discount Program invoicing process (described in section II.C.13.a of this preamble) a Part D sponsor may receive a negative invoice amount. This can occur when a PDE, which had been previously invoiced, is either deleted or adjusted by the plan such that the reported discount amount is less than originally invoiced. A negative invoice amount can be thought of as the amount an agreement holder has overpaid a Part D sponsor in a prior quarter that is now due back to the agreement holder because of the PDE adjustment or deletion. We proposed at § 423.2740 that Part D sponsors must pay such negative invoices in the manner specified by CMS within 38 calendar days of receipt of the invoice, the same timeframe specified in the July 12, 2013 memorandum. A sponsor's failure to pay such a negative invoice within the 38-day deadline may result in CMS taking compliance action in accordance with § 423.505(n).</P>
                    <P>We received no comments on this section of our proposal. We are finalizing § 423.2740 as proposed.</P>
                    <HD SOURCE="HD3">10. Prospective Payments to Part D Sponsors (§ 423.2744)</HD>
                    <HD SOURCE="HD3">a. General Rule</HD>
                    <P>As discussed in more detail in the preamble to the proposed rule, at § 423.2744(a), CMS proposed to codify existing policies to provide monthly prospective Manufacturer Discount Program payments to Part D sponsors so that sponsors can advance applicable discounts at the point of sale under § 423.2736(a) and reimburse network pharmacies within the timeframe required under § 423.2736(c).</P>
                    <HD SOURCE="HD3">b. Exception</HD>
                    <P>As described in section 60.4 of the Manufacturer Discount Program Final Guidance, employer group waiver plans (EGWPs) do not submit Part D bids; therefore, CMS does not have the information necessary to estimate the cost of applicable discounts for these plans and will not provide prospective Manufacturer Discount Program payments to EGWPs. We proposed to codify this exception to the Manufacturer Discount Program prospective payments at § 423.2744(b). However, because manufacturers are required to provide discounts for applicable drugs when dispensed to applicable beneficiaries who are enrolled in an EGWP, EGWPs are required to advance such discounts at the point of sale. The discounts will be invoiced to the manufacturer for reimbursement to the EGWP through the invoicing process at proposed § 423.2756(a).</P>
                    <HD SOURCE="HD3">c. Reconciliation</HD>
                    <P>Because prospective discount payments are estimates, Part D sponsors may incur actual Manufacturer Discount Program costs that are greater or less than the prospective payments. To ensure that Part D sponsors are made whole for the manufacturer discount amounts they advanced on behalf of the manufacturer, we proposed at § 423.2744(c) to codify cost-based reconciliation in accordance with subpart G of Part 423 and as implemented under section 60.5 of the Manufacturer Discount Program Final Guidance.</P>
                    <HD SOURCE="HD3">d. Manufacturer Bankruptcy</HD>
                    <P>
                        In the event that an agreement holder declares bankruptcy, as described in title 11 of the United States Code, and as a result of the bankruptcy, does not 
                        <PRTPAGE P="17415"/>
                        pay all invoiced amounts due under the requirements of proposed § 423.2756(a), we proposed at § 423.2744(d) to adjust the Manufacturer Discount Program reconciliation amount for each affected Part D sponsor to account for the total unpaid quarterly invoiced amount owed to each Part D sponsor for the contract year being reconciled, as per proposed § 423.2744(c). We proposed to reserve the government's right to file a proof-of-claim and take any other action under bankruptcy law, as appropriate, to attempt to recover such unpaid amounts and any civil money penalties imposed by CMS under these regulations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a comment on our proposals regarding prospective payments to Part D sponsors. The commenter requested additional guidance on the prospective payment process and the related documentation plans should maintain for tracking, submission for payment, and potential reconciliation. In addition, the commenter encouraged CMS to consider the potential impact of these requirements and stated that it is critical for plan sponsors to receive clear guidance to minimize administrative burden and ensure EGWPs remain a viable option for plan sponsors.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their feedback. As described in our proposed rule, prospective Manufacturer Discount Program payments to Part D sponsors will be based on the projections included in each plan's bid and on current enrollment. Under this process, CMS estimates the per member per month cost of the manufacturer discounts for each plan based on a percentage of the cost assumptions submitted with plan bids under § 423.265 and negotiated and approved under § 423.272, adjusted as necessary to account for applicable drug costs for applicable beneficiaries. CMS then multiplies the plan's manufacturer discount estimate by the number of beneficiaries enrolled in the plan and distributes the prospective Manufacturer Discount Program payments to plans on the first of each month. The Manufacturer Discount Program payments are reflected as a separate line item on each plan's Monthly Membership Detail Reports and included in the Part D payments displayed on the Monthly Membership Summary Reports. As we explained in the proposed rule, when manufacturers pay their quarterly Manufacturer Discount Program invoices, sponsors will appear to have a temporary duplicate payment from two sources, the manufacturer and CMS, for the same expense. After receiving payment from the manufacturer, the Part D sponsor no longer needs the cash flow advance from the prospective Manufacturer Discount Program payment. Therefore, CMS will offset the monthly prospective Manufacturer Discount Program payment, with the offset amount being equal to the total manufacturer discount amount received by the Part D sponsor from the manufacturer in the previous quarter. Document retention requirements for Part D sponsors are specified at § 423.505(d) and described in section IV.D. of this final rule. At this time, we do not believe additional CMS guidance is necessary. We encourage interested parties to monitor for additional guidance or information issued through HPMS or posted on our Manufacturer Discount Program web page at 
                        <E T="03">https://www.cms.gov/medicare/coverage/prescription-drug-coverage/part-d-information-pharmaceutical-manufacturers.</E>
                         Part D sponsors with questions regarding the Manufacturer Discount Program can reach out to their CMS account manager or submit questions to 
                        <E T="03">PartDManufacturerDiscountProgram@cms.hhs.gov.</E>
                    </P>
                    <P>CMS acknowledges the commenter's concern regarding the impact of requirements on Part D sponsors generally and EGWPs more specifically. With respect to prospective Manufacturer Discount Program payments and the exception for EGWPs, because EGWPs are not subject to typical Part D bidding requirements due to a longstanding waiver by CMS, they do not submit Part D bids. As such, CMS lacks the information necessary to estimate the cost of applicable discounts for these plans.</P>
                    <P>After consideration of the comments received, we are finalizing proposed § 423.2744 without modification.</P>
                    <HD SOURCE="HD3">11. Requirement To Use the Health Plan Management System (§ 423.2748)</HD>
                    <P>At § 423.2748, we proposed to codify requirements related to use of the Health Plan Management System (HPMS) that were included in the Manufacturer Discount Program Final Guidance. Specifically, we proposed that agreement holders are required to maintain HPMS access and use the HPMS to—</P>
                    <P>• Provide and maintain required information, as specified by CMS;</P>
                    <P>• Attest to the completeness and accuracy of the data necessary for CMS to determine whether the manufacturer qualifies as a specified manufacturer or specified small manufacturer, as described at § 423.2716;</P>
                    <P>• Execute a Manufacturer Discount Program agreement and a TPA agreement; and</P>
                    <P>• As otherwise specified by CMS to administer the program.</P>
                    <P>We did not receive any comments regarding this section of our proposal. We are finalizing § 423.2748 without modification.</P>
                    <HD SOURCE="HD3">12. Manufacturer Discount Program Agreement (§ 423.2752)</HD>
                    <P>Section 1860D-14C(a) of the Act requires CMS to enter into Manufacturer Discount Program agreements with manufacturers in order for manufacturers to participate in the Manufacturer Discount Program. CMS released the Manufacturer Discount Program agreement template on November 17, 2023. The burden associated with executing the agreement and related requirements is currently approved under OMB control number 0938-1451 (CMS-10846) through December 31, 2028. We proposed to codify the requirements for the Manufacturer Discount Program agreement at § 423.2752.</P>
                    <HD SOURCE="HD3">a. Requirements of Agreement</HD>
                    <P>As discussed in more detail in section II.C.4. of this preamble, CMS is finalizing at § 423.2708(b) the requirement that a manufacturer is considered to participate in the Manufacturer Discount Program and to have entered into and have in effect a Manufacturer Discount Program agreement, as required under section 1860D-43(a) of the Act, if such manufacturer executes and has in effect its own Manufacturer Discount Program agreement or participates by means of an arrangement whereby its labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement that is in effect. As discussed in the preamble to the proposed rule, only a manufacturer that is an agreement holder (as defined in § 423.2708) is a party to such agreement with CMS, and the entity subject to the rights and obligations of such agreement. In accordance with this framework, the requirements we proposed at § 423.2752 related to the Manufacturer Discount Program agreement apply only to manufacturers that are agreement holders. Pursuant to section 1860D-14C(b) of the Act, we proposed at § 423.2752(a) that the Manufacturer Discount Program agreement require, at a minimum, each agreement holder to:</P>
                    <P>
                        • Reimburse, within the required 38-day timeframe, all applicable discounts provided by Part D sponsors on behalf of the manufacturer for applicable drugs dispensed on or after January 1, 2025 that have an NDC with a labeler code that is covered by the manufacturer's 
                        <PRTPAGE P="17416"/>
                        Manufacturer Discount Program agreement and invoiced to the manufacturer. As proposed at § 423.2756(b)(2), when an invoice deadline falls on a Saturday, Sunday, or legal holiday, the payment timeframe is extended to the first day thereafter which is not a Saturday, Sunday, or legal holiday.
                    </P>
                    <P>• Provide CMS with all labeler codes covered by its Manufacturer Discount Program agreement.</P>
                    <P>• Ensure that the labeler codes provided to CMS include, at a minimum, all labeler codes assigned by the FDA to the manufacturer that contain NDCs for any of the manufacturer's applicable drugs or selected drugs, and promptly update CMS with any labeler codes newly assigned to the manufacturer by the FDA that contain NDCs for any of the manufacturer's applicable drugs or selected drugs in accordance with the timing requirements discussed later in this section and proposed at § 423.2756(c)(3) for newly assigned labeler codes.</P>
                    <P>• Comply with the requirements established by CMS for purposes of administering the Manufacturer Discount Program and monitoring compliance with such program, including providing the manufacturer's Employer Identification Number (EIN) and other identifying information to CMS upon request.</P>
                    <P>• Comply with the requirements related to the provision and maintenance of data, including collecting, maintaining, and reporting appropriate data related to the labeler codes covered by its agreement and any other data CMS determines necessary to carry out the Manufacturer Discount Program and demonstrate compliance with its requirements.</P>
                    <P>• Enter into and have in effect, under the terms and conditions specified by CMS, an agreement with the TPA and comply with such agreement and all TPA instructions, processes, and requirements.</P>
                    <P>• Provide and attest to information, as specified by CMS, necessary for CMS to determine eligibility for, and implement, the specified manufacturer and specified small manufacturer phase-in discounts.</P>
                    <P>• Agree that, no less than 30 days after the date CMS determines that a primary manufacturer of a selected drug has, in accordance with proposed § 423.2752(c)(1)(ii), provided notice to CMS of its decision not to enter into or continue its participation in the Medicare Drug Price Negotiation Program and to discontinue its applicable agreements under the Medicaid Drug Rebate Program and the Manufacturer Discount Program, none of the drugs of such primary manufacturer will be covered by the manufacturer's Manufacturer Discount Program agreement.</P>
                    <P>• Comply with all other requirements of the Manufacturer Discount Program.</P>
                    <HD SOURCE="HD3">b. Term and Renewal</HD>
                    <P>Consistent with section 1860D-14C(b)(4)(A) of the Act, Manufacturer Discount Program agreements are valid for an initial term of not less than 12 months, and automatically renew for a period of 1 year on each subsequent January 1, except as described later in this section, unless terminated as described in section II.C.12.c. of this final rule. Consistent with the policies CMS established in the Manufacturer Discount Program Final Guidance, we proposed to codify the requirements related to Manufacturer Discount Program agreement term and renewal at § 423.2752(b).</P>
                    <HD SOURCE="HD3">c. Termination of Agreement</HD>
                    <HD SOURCE="HD3">(1) Termination by CMS</HD>
                    <P>Under section 1860D-14C(b)(4)(B)(i) of the Act, CMS may terminate a Manufacturer Discount Program agreement for a knowing and willful violation of the requirements of the agreement or other good cause shown in relation to a manufacturer's participation in the Manufacturer Discount Program. The statute also specifies that a termination by CMS will not be effective earlier than 30 calendar days after the date of notice to the manufacturer of such termination. We proposed to codify the policies for termination by CMS at § 423.2752(c)(1).</P>
                    <P>
                        Consistent with applicable guidance for the Medicare Drug Price Negotiation Program,
                        <SU>22</SU>
                        <FTREF/>
                         a manufacturer that is a primary manufacturer, as defined at § 423.2704, may submit a request for termination of a Manufacturer Discount Program agreement in connection with a notice of its decision that it is unwilling to participate in, or continue its participation in, the Medicare Drug Price Negotiation Program.
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             See, for example, sections 40.1 and 40.6, as applicable, of the June 30, 2023 Medicare Drug Price Negotiation Program Revised Guidance, Implementation of Sections 1191-1198 of the Social Security Act for Initial Price Applicability Year 2026, available at 
                            <E T="03">https://www.cms.gov/files/document/revised-medicare-drug-price-negotiation-program-guidance-june-2023.pdf;</E>
                             the October 2, 2024 Medicare Drug Price Negotiation Program: Final Guidance, Implementation of Sections 1191—1198 of the Social Security Act for Initial Price Applicability Year 2027 and Manufacturer Effectuation of the Maximum Fair Price in 2026 and 2027, available at 
                            <E T="03">https://www.cms.gov/files/document/medicare-drug-price-negotiation-final-guidance-ipay-2027-and-manufacturer-effectuation-mfp-2026-2027.pdf; and the September 30, 2025 Medicare Drug Price Negotiation Program: Final Guidance, Implementation of Sections 1191-1198 of the Social Security Act for Initial Price Applicability Year 2028 and Manufacturer Effectuation of the Maximum Fair Price in 2026, 2027, and 2028, available at https://www.cms.gov/files/document/ipay-2028-final-guidance.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        Specifically, a manufacturer that is the primary manufacturer of a selected drug may provide a notice to CMS stating the primary manufacturer's unwillingness to participate in, or its request to terminate an agreement under, the Medicare Drug Price Negotiation Program (herein referred to as a “Request to Terminate”). In accordance with applicable regulations and guidance for the Medicare Drug Price Negotiation Program, such Request to Terminate must incorporate both: (1) a request for termination of the primary manufacturer's applicable agreements under the Medicaid Drug Rebate Program and the Manufacturer Discount Program, consistent with the requirements as set forth in 26 U.S.C. 5000D(c)(1)(A)(i); and (2) an attestation that provides in part that through the end of the price applicability period (as defined in section 1191(b)(2) of the Act) for the selected drug that the primary manufacturer (i) shall not seek to enter into any subsequent agreement with the Manufacturer Discount Program under section 1860D-14C of the Act; and (ii) shall not seek coverage for any of its drugs under the Manufacturer Discount Program under section 1860D-14C of the Act, consistent with the requirements set forth in 26 U.S.C. 5000D(c)(1)(B). If CMS determines the primary manufacturer's Request to Terminate complies with applicable requirements, the primary manufacturer's request will constitute good cause under section 1860D-14C(b)(4)(B)(i) of the Act to terminate the primary manufacturer's applicable agreements under the Manufacturer Discount Program in accordance with the proposed § 423.2752(c)(1)(ii) and the proposed § 423.2752(c)(1)(v)(A)(1), as applicable.
                        <SU>23</SU>
                        <FTREF/>
                         CMS also will terminate coverage for all of the drugs of the 
                        <PRTPAGE P="17417"/>
                        primary manufacturer under the Manufacturer Discount Program in accordance with proposed § 423.2752(c)(1)(v)(A)(2), as discussed in more detail later in this section.
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             26 U.S.C. 5000D(c)(2), as enacted by section 11003 of the IRA, defines “applicable agreement.” In the context of the Manufacturer Discount Program, the primary manufacturer's applicable agreements include any Manufacturer Discount Program agreement for which the primary manufacturer is the agreement holder, as well as any arrangement in which FDA-assigned labeler code(s) of the primary manufacturer is/are covered under the Manufacturer Discount Program agreement of another manufacturer. If the primary manufacturer's Request to Terminate complies with applicable requirements, CMS will effectuate removal of only the previously described FDA-assigned labeler code(s) from the Manufacturer Discount Program agreement of another manufacturer.
                        </P>
                    </FTNT>
                    <P>Consistent with the requirement in section 1860D-14C(b)(4)(B)(i) of the Act and the termination policies established in section 80.1.3.1 of the Manufacturer Discount Program Final Guidance, CMS will provide, upon written request, a manufacturer a hearing concerning a termination by CMS. This hearing will take place prior to the effective date of the termination with sufficient time for the termination to be repealed prior to the effective date if CMS determines repeal would be appropriate. If a manufacturer or CMS receives an unfavorable decision from the hearing officer, the manufacturer or CMS may request review by the CMS Administrator within 30 calendar days of receipt of the notification of such determination. The decision of the CMS Administrator is final and binding. A timely request for a hearing before a hearing officer or review by the CMS Administrator will stay termination until the parties have exhausted their appeal rights under the Manufacturer Discount Program, which means either the timeframes to pursue a hearing before a hearing officer or review by the CMS Administrator have passed or a final decision by the Administrator has been issued and there is no remaining opportunity to request further administrative review. We proposed to codify these policies regarding hearings at § 423.2752(c)(1)(iv)(A) and (B).</P>
                    <P>In the case of a primary manufacturer of a selected drug under the Medicare Drug Price Negotiation Program that is unwilling to enter into a Medicare Drug Price Negotiation Program agreement or continue its participation in the Medicare Drug Price Negotiation Program and submits a Request to Terminate that complies with all applicable requirements, CMS shall, upon written request from such primary manufacturer, provide a hearing concerning the termination of the primary manufacturer's applicable agreements under the Manufacturer Discount Program, in accordance with section 1860D-14C(b)(4)(B)(i) of the Act. Such a hearing will be held prior to the effective date of termination with sufficient time for such effective date to be repealed. Such a hearing will be held solely on the papers. CMS's determination that there is good cause for termination depends solely on the primary manufacturer's request for termination to effectuate its decision not to participate in or to terminate its participation in the Medicare Drug Price Negotiation Program. Therefore, the only question to be decided in the hearing is whether the primary manufacturer has asked to rescind its Request to Terminate prior to the effective date of the termination. CMS will automatically grant such request from the primary manufacturer to rescind its Request to Terminate. We proposed to codify these policies at § 423.2752(c)(1)(iv)(C).</P>
                    <P>If CMS determines that a primary manufacturer's Request to Terminate complies with all applicable requirements, we will effectuate the removal of the FDA-assigned labeler code(s) of the primary manufacturer from all Manufacturer Discount Program agreements for which the primary manufacturer is not the agreement holder no earlier than 30 days from the date we send the notice of termination to the manufacturer in accordance with proposed § 423.2752(c)(1)(iii).</P>
                    <P>
                        We proposed to codify this requirement at § 423.2752(c)(1)(v)(A)(
                        <E T="03">1</E>
                        ).
                    </P>
                    <P>
                        Similarly, CMS will effectuate the termination of coverage under any Manufacturer Discount Program agreement specific to NDCs of all applicable drugs and selected drugs for which the primary manufacturer is the holder of the new drug application or biologics license application. Such termination of coverage under this provision will apply to all applicable drug and selected drug NDCs of the primary manufacturer for which the labeler code is assigned to a manufacturer other than the primary manufacturer and for which the primary manufacturer is the new drug application or biologics license application holder for such drug. We proposed to codify this requirement at § 423.2752(c)(1)(v)(A)(
                        <E T="03">2</E>
                        ).
                    </P>
                    <P>At § 423.2752(c)(1)(v)(B), we proposed to clarify that, consistent with the requirement at § 423.2752(c)(3) discussed below, the removal of labeler code(s) in accordance with § 423.2752(c)(1)(v)(A)(1) and the termination of coverage specific to NDCs in accordance with § 423.2752(c)(1)(v)(A)(2) do not affect the agreement holder's responsibility to reimburse Part D sponsors for applicable discounts for applicable drugs with such labeler code(s) or such NDCs that were incurred under the agreement before the effective date of removal or termination.</P>
                    <HD SOURCE="HD3">(2) Termination by the Manufacturer</HD>
                    <P>In accordance with section 1860D-14C(b)(4)(B)(ii) of the Act, an agreement holder may terminate its Manufacturer Discount Program agreement for any reason. Under the policies established in section 80.1.3.2 of the Manufacturer Discount Program Final Guidance, if the manufacturer provides notice of termination under section 1860D-14C(b)(4)(B)(ii) of the Act before January 31 of a calendar year, such termination will be effective as of January 1 of the succeeding calendar year. If the manufacturer provides such notice of termination on or after January 31 of a calendar year, the termination will be effective as of January 1 of the second succeeding calendar year.</P>
                    <P>We proposed to codify these existing policies at § 423.2752(c)(2).</P>
                    <HD SOURCE="HD3">(3) Post-Termination Obligations</HD>
                    <P>Consistent with section 1860D-14C(b)(4)(B)(iii) of the Act, the termination of a Manufacturer Discount Program agreement under either sections 1860D-14C(b)(4)(B)(i) or 1860D-14C(b)(4)(B)(ii) of the Act will not affect the manufacturer's responsibility to reimburse Part D sponsors for applicable discounts for applicable drugs having NDCs with labeler code(s) covered by the manufacturer's agreement that were incurred under the agreement before the effective date of termination.</P>
                    <P>We proposed to codify this requirement at § 423.2752(c)(3).</P>
                    <HD SOURCE="HD3">(4) Reinstatement</HD>
                    <P>As described in section 80.1.4 of the Manufacturer Discount Program Final Guidance, reinstatement in the Manufacturer Discount Program subsequent to termination by CMS will be available to a manufacturer only upon payment of all outstanding applicable discounts and penalties incurred under any previous Manufacturer Discount Program agreement or Coverage Gap Discount Program agreement. The timing of any such reinstatement will be consistent with the requirements for entering into an agreement under proposed § 423.2752(b).</P>
                    <P>We proposed to codify this policy at § 423.2752(c)(4).</P>
                    <HD SOURCE="HD3">(5) Automatic Assignment Upon Change of Ownership</HD>
                    <P>
                        At § 423.2752(d) we proposed to codify the requirements of section 80.5.1 of the Manufacturer Discount Program Final Guidance and section (VIII)(b) of the Manufacturer Discount Program agreement, that in the event of a change in ownership of a manufacturer that is an agreement holder, the Manufacturer Discount Program agreement is automatically assigned to the new owner, and all terms and conditions of the agreement remain in effect as to the new owner 
                        <PRTPAGE P="17418"/>
                        unless terminated in accordance with requirements at § 423.2752(c). Further, we proposed that the new agreement holder would agree to be bound by and to perform all the duties and responsibilities under the Manufacturer Discount Program, and assume all obligations and liabilities of, and all claims incurred against, the prior agreement holder under the Manufacturer Discount Program agreement whether arising before or after the effective date of the change of ownership.
                    </P>
                    <P>
                        CMS did not receive any comments on our proposals in this section. We are finalizing the provisions of § 423.2752 with a minor clarifying change at paragraph (c)(1)(v)(A)(
                        <E T="03">2</E>
                        ) to clarify that the termination of coverage described in paragraph (c)(1)(v)(A)(
                        <E T="03">2</E>
                        ) is specific to the termination of coverage “under paragraph (
                        <E T="03">2</E>
                        )”.
                    </P>
                    <HD SOURCE="HD3">13. Manufacturer Requirements (§ 423.2756)</HD>
                    <P>We proposed that manufacturers that are agreement holders, as defined at § 423.2704, must comply with all requirements at § 423.2756.</P>
                    <HD SOURCE="HD3">a. Manufacturer Invoicing</HD>
                    <P>At § 423.2756(a), CMS proposed that we will calculate, based on information reported by Part D sponsors, the amounts owed for applicable discounts for applicable drugs having NDCs with a labeler code covered by an agreement holder's Manufacturer Discount Program agreement and will invoice the agreement holder quarterly. We also proposed that CMS will invoice manufacturer discount amounts from accepted PDE data for 37 months following the end of the benefit year.</P>
                    <P>As we explained in the preamble to the proposed rule, CMS includes the following detail on Manufacturer Discount Program invoices:</P>
                    <P>• Date of service;</P>
                    <P>• Service provider identifier qualifier;</P>
                    <P>• Service provider identifier;</P>
                    <P>• Prescription/service reference number;</P>
                    <P>• Product/service identifier;</P>
                    <P>• Quantity dispensed;</P>
                    <P>• Days supply;</P>
                    <P>• Fill number;</P>
                    <P>• Reported discount;</P>
                    <P>• Low-income cost sharing amount;</P>
                    <P>• Total gross covered drug cost accumulator;</P>
                    <P>• True out-of-pocket accumulator;</P>
                    <P>• Gross drug cost below out-of-pocket threshold; and</P>
                    <P>• Gross drug cost above out-of-pocket threshold.</P>
                    <HD SOURCE="HD3">b. Requirement for Timely Payment</HD>
                    <P>At § 423.2756(b) CMS proposed to codify the requirements for timely payment of manufacturer discounts. Specifically, at § 423.2756(b)(1) we proposed that agreement holders must pay each Part D sponsor invoiced amounts no later than 38 calendar days from receipt of the relevant invoice, with limited exceptions in proposed paragraphs (b)(2) and (b)(3). At § 423.2756(b)(2), we proposed that if an invoice deadline falls on a Saturday, Sunday, or legal holiday, the payment timeframe is extended to the first day thereafter which is not a Saturday, Sunday, or legal holiday.</P>
                    <P>At § 423.2756(b)(3), we proposed that agreement holders are not permitted to withhold payment for any disputed invoiced amount, including while a dispute is pending, except when the basis for the dispute is that the agreement holder has been invoiced amounts for applicable drugs that have NDCs that do not correspond to labeler codes covered by the agreement holder's Manufacturer Discount Program agreement. We further proposed that if payment is withheld in such an instance, the agreement holder must notify the TPA within 38 calendar days of the manufacturer's receipt of the applicable invoice that payment is being withheld for this reason.</P>
                    <P>As discussed in the preamble to the proposed rule, this payment withholding rule is consistent with processes established in section 80.2.3 of the Manufacturer Discount Program Final Guidance, and we believe it strikes a reasonable balance between the needs of manufacturers and Part D sponsors. CMS performs extensive quality assurance with respect to PDE data submitted by sponsors and we believe that prohibiting the withholding of disputed invoices minimizes the risk to Part D sponsors for these discount-related incurred liabilities without significantly increasing the financial risk to a manufacturer. The PDE data used to calculate quarterly invoices are derived from claims for each prescription submitted to Part D sponsors for payment. Part D sponsors validate each claim as part of their process to reimburse pharmacies for the cost of the drug. In addition, CMS applies multiple edits to validate the PDE data submitted by Part D sponsors. Those edits include identification and adjustment of outlier and other erroneous entries for variables, such as discount amount, beneficiary eligibility for the discount, and NDCs.</P>
                    <HD SOURCE="HD3">c. Reporting Requirements</HD>
                    <P>At paragraph (c)(1) of § 423.2756, we proposed that, in general, agreement holders must collect, have available, and maintain appropriate data related to the labeler codes covered by their Manufacturer Discount Program agreement. This includes FDA drug approvals, FDA NDC Directory listings, NDC last-lot expiration dates, utilization and pricing information relied on by the manufacturer to dispute quarterly invoices, and any other data CMS determines necessary to carry out the Manufacturer Discount Program and demonstrate compliance with its requirements. We also proposed that manufacturers maintain such data as described previously for a period of not less than 10 years from the date of payment of the corresponding invoice.</P>
                    <P>At § 423.2756(c)(2), we proposed requirements related to providing information to CMS about manufacturer ownership. Specifically, at paragraph (c)(2)(i), we proposed to require agreement holders to provide and attest to ownership and other data, in the form and manner specified by CMS, as necessary for CMS to determine eligibility for discount phase-ins for specified manufacturers and specified small manufacturers in accordance with statutory requirements, as we proposed to codify at § 423.2716. Likewise, at paragraph (c)(2)(iii), we proposed that if the agreement holder covers the FDA-assigned labeler code(s) of another manufacturer by its Manufacturer Discount Program agreement, the agreement holder would also be required to provide ownership information about such other manufacturer.</P>
                    <P>
                        As we explained in the proposed rule, it is also imperative that CMS be notified promptly of any ownership changes of a manufacturer participating in the Manufacturer Discount Program so that we can evaluate such changes as they relate to the application of discount phase-ins, including the acquisition policy under proposed § 423.2724. At § 423.2756(c)(2)(ii), we proposed to codify our longstanding policy that agreement holders notify us of a change in their ownership no later than 30 calendar days after the agreement holder executes a legal obligation for such an arrangement and no later than 45 calendar days prior to the change in ownership taking effect. At § 423.2756(c)(2)(iii) we proposed a corresponding requirement that, if an agreement holder covers the labeler code(s) of another manufacturer by its Manufacturer Discount Program agreement, the agreement holder must 
                        <PRTPAGE P="17419"/>
                        notify us of a change in ownership of such other manufacturer.
                    </P>
                    <P>If CMS is not notified of an ownership change, the original agreement holder will be invoiced and payment will have to be reconciled between the manufacturers involved in the transaction. CMS will not consider untimely notice of a change of ownership to be grounds for an agreement holder to dispute the invoiced amount.</P>
                    <P>At § 423.2756(c)(3), we proposed requirements related to labeler codes. Consistent with the Manufacturer Discount Program Final Guidance, section 80.5.2, we proposed at § 423.2756(c)(3)(i) that each agreement holder must cover by its agreement all labeler codes assigned by the FDA to the agreement holder that contain NDCs for the agreement holder's applicable drugs and selected drugs. We also proposed at § 423.2756(c)(3)(ii) that, consistent with § 423.2708(b)(2), an agreement holder may cover by its Manufacturer Discount Program agreement applicable drugs or selected drugs with labeler code(s) assigned by the FDA to another manufacturer, provided the other manufacturer has not executed and does not have in effect its own Manufacturer Discount Program agreement in accordance with § 423.2708(b)(1).</P>
                    <P>We proposed that agreement holders must provide to CMS and maintain all required labeler code information as instructed by CMS. Specifically, we proposed at § 423.2756(c)(3)(iii) to require agreement holders to provide to CMS the following labeler code information:</P>
                    <P>• All labeler codes assigned by the FDA to the agreement holder that contain NDCs for the agreement holder's applicable drugs and selected drugs; and</P>
                    <P>• All labeler codes assigned by the FDA to another manufacturer that the agreement holder covers by its agreement and for which the agreement holder agrees to pay discounts.</P>
                    <P>We also proposed at § 423.2756(c)(3)(iv) that agreement holders must provide labeler codes newly assigned by the FDA to the agreement holder to CMS no later than 3 business days after receiving written notification of the newly assigned labeler code(s) from the FDA and in advance of providing any NDCs associated with such labeler codes to electronic database vendors.</P>
                    <P>As proposed at § 423.2756(c)(3)(v), agreement holders are responsible for maintaining the list of labeler codes covered by their agreement to ensure that it remains current on an ongoing basis. An agreement holder's failure to update labeler codes covered by its agreement does not change the agreement holder's responsibility to pay the amounts invoiced for applicable drugs. Specific instructions on how agreement holders are to submit information to CMS are available in the HPMS Drug Manufacturer Management User Manual.</P>
                    <P>As part of maintaining the list of labeler codes covered by their Manufacturer Discount Program agreement, agreement holders should submit a request in HPMS to terminate labeler codes where all of the NDCs are past the last lot expiration date. In order to submit the request, the agreement holder must attest in HPMS that the marketing end date on the FDA NDC SPL Data Elements file, defined by the FDA as the date of expiration of the last lot released to the marketplace, has passed for all applicable drugs and selected drugs associated with the labeler code. Termination of labeler codes where all of the NDCs are past the last lot expiration date differs from the process proposed at § 423.2752(c)(1)(v), which applies to the CMS termination of labeler codes and NDCs of a primary manufacturer and is described in section II.C.12.c. of this preamble.</P>
                    <P>At § 423.2756(c)(4), we proposed requirements related to maintenance of FDA records and related records. CMS relies on data available through the FDA to identify applicable drugs in the Manufacturer Discount Program. Accordingly, we proposed at § 423.2756(c)(4)(i)(A) that agreement holders must ensure that all labeler codes assigned by the FDA to the agreement holder that contain NDCs for any of its applicable drugs or selected drugs are properly listed on the FDA NDC Directory. We proposed at § 423.2756(c)(4)(i)(B) that agreement holders must electronically list all NDCs of their applicable drugs or selected drugs with the FDA in advance of commercial distribution of the product(s) so that CMS and plans can accurately identify applicable drugs once they are provided to pharmacies for distribution. Further, CMS proposes at § 423.2756(c)(4)(i)(C) that agreement holders must maintain up-to-date electronic FDA registrations and listings of all NDCs, including the timely removal of discontinued NDCs from the FDA NDC Directory. Accurate NDC listings enable CMS and Part D sponsors to accurately identify applicable drugs. For this reason, updates to the FDA NDC Directory must precede NDC additions made to commercial electronic databases used for pharmacy claims processing.</P>
                    <P>In addition, we proposed at § 423.2756(c)(4)(i)(D) that agreement holders must maintain up-to-date listings with the electronic database vendors to whom they provide their NDCs for pharmacy claims processing. This includes ensuring that these electronic database vendors are prospectively notified when NDCs no longer represent products that are still available on the market. A manufacturer's failure to provide appropriate advance notice to electronic database vendors may result in the agreement holder being responsible for discounts after the last-lot expiration date unless the manufacturer can document that it provided such appropriate advance notice to the database vendors, or the manufacturer has provided advance notice to the FDA of the marketing end date.</P>
                    <P>At § 423.2756(c)(4)(ii), we proposed that if an agreement holder's Manufacturer Discount Program agreement covers labeler code(s) that are assigned by the FDA to another manufacturer that participates in the Manufacturer Discount Program in accordance with § 423.2708(b)(2), the agreement holder must ensure that the requirements of this section are met with respect to such labeler codes.</P>
                    <P>At § 423.2756(d), we proposed to codify existing CMS policy that permits agreement holders to transfer labeler code(s) between Manufacturer Discount Program agreements so long as the transfer is consistent with requirements of the proposed subpart AA and the Manufacturer Discount Program agreement and is approved by CMS. As explained in the proposed rule, transfers of labeler codes from one Manufacturer Discount Program agreement to another are not considered complete until CMS has approved both requests. The agreement holder seeking to transfer the labeler code from its agreement remains liable for payment of all discounts related to such labeler code until the transfer is complete. An agreement holder is not permitted to transfer its own FDA-assigned labeler code(s) to the Discount Program agreement of another manufacturer.</P>
                    <P>
                        Once the transfer is complete, the receiving agreement holder assumes responsibility for all Manufacturer Discount Program requirements with respect to the transferred labeler code(s). Manufacturer Discount Program invoices to the receiving agreement holder include the discount amounts by labeler code for the entire quarter. If an agreement holder assumes liability for a labeler code effective the second or third month of a quarter, that agreement holder will be invoiced and is 
                        <PRTPAGE P="17420"/>
                        responsible for all discount amounts of that labeler code for the entire quarter, including any claims from dates of service in prior quarters that are included on that quarter's invoice.
                    </P>
                    <P>In the event that business needs do not coincide with the timing of the transfer, agreement holders are expected to reconcile any payments among themselves without CMS involvement.</P>
                    <P>The transfer of a labeler code between Manufacturer Discount Program agreements includes all NDCs associated with the transferred labeler code; CMS will not transfer individual NDCs.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments regarding the data elements CMS provides on Manufacturer Discount Program invoices. The commenters thanked CMS for expanding the data provided to manufacturers compared to what was provided under the Coverage Gap Discount Program. A few commenters supported codifying the Manufacturer Discount Program invoice data elements.
                    </P>
                    <P>
                        The commenters also recommended that CMS expand the set of data elements currently provided on manufacturer invoices, arguing that additional data fields are necessary for manufacturers to accurately verify Manufacturer Discount Program discounts. In combination, these commenters asked that CMS add the following additional data elements to Manufacturer Discount Program invoices: Part D contract and Part D plan benefit package identifiers; a de-identified Part D beneficiary identifier; the prescriber's National Provider Identifier; the date the Part D plan paid the pharmacy; claim status (
                        <E T="03">i.e.,</E>
                         whether the claim was paid or reversed); a Medicare Prescription Payment Plan participation identifier; information about the indication for which the drug was prescribed; and various cost accumulator fields to identify an enrollee's actual out-of-pocket costs and where the enrollee falls in the phases of the Part D benefit.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support and acknowledgement of CMS's decision at the start of the Manufacturer Discount Program to include additional data elements on manufacturer invoices. As commenters recognized, the current data elements included on invoices provide manufacturers with more data than they received on invoices under the Coverage Gap Discount Program. However, we disagree with the commenters that additional data elements are necessary or would be beneficial. We are not persuaded by the comments to add any of the additional data elements requested. We believe the current data elements included on invoices appropriately balance important beneficiary privacy protection and sufficient information for agreement holders to meet their statutory obligation to provide discounted prices for applicable drugs under section 1860D-14C(b)(1)(A) of the Act. We further clarify that we did not propose to enumerate in the regulation text which specific data elements are included on Manufacturer Discount Program invoices.
                    </P>
                    <P>As discussed in the Manufacturer Discount Program Final Guidance and the preamble to the proposed rule, in providing the invoice data, CMS seeks to limit the disclosure of claim-level information to the minimum necessary for an agreement holder to verify payment. Pursuant to section II(l) and section (b)(1) of Exhibit C of the Manufacturer Discount Program agreement, information sent from CMS or the TPA to the agreement holder with each quarterly invoice may be used only for evaluating the accuracy of the invoiced discounts and resolving disputes concerning the manufacturer's payment obligations under the Manufacturer Discount Program.</P>
                    <P>
                        Manufacturers should consider that prior to invoicing under the Manufacturer Discount Program, CMS performs extensive editing on PDE records and conducts outlier analyses to check for duplicate claims, applicable national drug codes (NDCs), and incorrect discount calculations, among other checks. Detailed information on the PDE submission process, including on CMS's robust PDE editing process, can be found on the Customer Service and Support Center (CSSC) website.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             
                            <E T="03">https://www.csscoperations.com/internet/csscw3.nsf.</E>
                        </P>
                    </FTNT>
                    <P>After consideration of the comments received, we are finalizing § 423.2756 as proposed.</P>
                    <HD SOURCE="HD3">14. Audits (§ 423.2760)</HD>
                    <P>We proposed to codify at § 423.2760 the Manufacturer Discount Program audit processes established in section 90 of the Manufacturer Discount Program Final Guidance.</P>
                    <P>Regarding manufacturer audits of TPA data, we proposed at § 423.2760(a)(1) that an agreement holder may conduct audits, directly or through third parties and no more often than annually, of TPA data and information used to determine discounts for applicable drugs covered under the agreement holder's Manufacturer Discount Program agreement. We proposed at § 423.2760(a)(2) that the agreement holder must provide 60 calendar days' notice to the TPA of the reasonable basis for the audit and a description of the information required for the audit.</P>
                    <P>As discussed in the preamble to the proposed rule, when developing audit processes for the Manufacturer Discount Program Final Guidance, CMS considered feedback from interested parties. In response to this feedback and in alignment with section 90.1.2 of the Manufacturer Discount Program Final Guidance, CMS provides the following data to agreement holders that are auditing TPA data, in addition to the data elements included on invoices:</P>
                    <P>• Contract number;</P>
                    <P>• Plan benefit package identifier;</P>
                    <P>• Ingredient cost paid;</P>
                    <P>• Dispensing fee paid;</P>
                    <P>• Total amount attributed to sales tax;</P>
                    <P>• Non-covered plan paid amount; and</P>
                    <P>• Vaccine administration fee or additional dispensing fee.</P>
                    <P>We proposed limits on audits of TPA data and information at § 423.2760(a)(3). Specifically, we proposed at § 423.2760(a)(3)(i) that the data provided to the manufacturer conducting the audit be limited to a statistically significant random sample of data held by the TPA that were used to determine applicable discounts for applicable drugs having NDCs with labeler codes covered by the agreement holder's Manufacturer Discount Program agreement. At § 423.2760(a)(3)(ii), we proposed that manufacturers are not permitted to audit CMS records or the records of Part D sponsors beyond the data provided to the TPA, which includes claim-level information.</P>
                    <P>At § 423.2760(a)(3)(iii), we proposed that audits must occur on site at a location specified by the TPA, and with the exception of work papers, audit data cannot be removed from the audit site. Additionally, we proposed at § 423.2760(a)(3)(iv) that the auditor may release only an opinion of the audit results and is prohibited from releasing any other information obtained from the audit, including work papers, to its client, employer, or any other party. CMS believes these limitations on the distribution of data support beneficiary privacy, while addressing manufacturer need for access to data that are relevant to the calculation of the discounts.</P>
                    <P>
                        Regarding CMS audits of manufacturer data, we proposed at § 423.2760(b)(1) that an agreement holder is subject to periodic audit by CMS no more often than annually, directly or through third parties. We proposed at § 423.2760(b)(2) that CMS must provide agreement holders with 60 
                        <PRTPAGE P="17421"/>
                        calendar days' notice of the reasonable basis for the audit and a description of the information required for the audit. We further proposed at § 423.2760(b)(3) that CMS has the right to audit appropriate data, including data related to labeler codes covered by the agreement holder's Manufacturer Discount Program agreement and related NDC last-lot expiration dates, utilization, and pricing information relied on by the agreement holder to dispute quarterly invoices, and any other data CMS determines necessary to evaluate compliance with the requirements of the Manufacturer Discount Program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS remove the requirement that audits be conducted on site only, because the requirement imposes a significant burden on the manufacturer, including travel time and expenses. The commenter suggested that CMS allow manufacturers to access audit data through a secure online portal overseen by the TPA.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their feedback. Regarding allowing manufacturer audits of TPA data to be conducted remotely, CMS intends to continue exploring with the TPA ways in which remote audits might be conducted in the future. While we do not expect remote auditing of the TPA to be in place by CY 2027, in order to allow for the possibility of remote audits in the future, we are striking the words “on site” and “the audit site” from the proposed regulation text at § 423.2760(a)(3)(iii) that specified that audits must occur on site at a location specified by the TPA and that data cannot be removed from the audit site. As modified, the regulatory text requires that audits must occur at “a location specified by the TPA” and that data cannot be removed from “such specified location”. CMS and the TPA may specify through future guidance whether an audit will be conducted on site or remotely at a virtual location. Until CMS establishes and operationalizes a secure method for allowing manufacturers to conduct remote audits of TPA data, audits will continue to occur on site at a physical location specified by the TPA.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The same commenter urged CMS to clarify the limitation on an auditor sharing information beyond its opinion of the audit results with its client and specifically permit the manufacturer to review all data underlying an audit conducted on its behalf. The commenter also requested that CMS permit manufacturers to audit CMS records and the records of Part D sponsors beyond the data provided to the TPA, including any data CMS would use to audit the selected drug subsidy under proposed § 423.329(e) .
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with these comments. As previously noted, CMS believes that the limitations on distribution of audit data strike the appropriate balance between supporting beneficiary privacy and ensuring manufacturer access to data relevant to the calculation of discounts.
                    </P>
                    <P>Regarding manufacturer audits of information beyond the data provided to the TPA, we note that section 1860D-14A(d)(3)(D) of the Act permitted manufacturers to conduct periodic audits “of the data and information used by the third party to determine discounts” under the Coverage Gap Discount Program. There is no statutory requirement under the Manufacturer Discount Program to permit manufacturers to audit any data or information used to determine discounts. We chose to carry over this policy because we continue to utilize a TPA to facilitate administration of the program. While manufacturers can dispute invoiced discounts through the process described at § 423.2764, which may involve CMS review of data beyond what is provided by the TPA, including consultation with Part D sponsors, we believe that data available to manufacturers under our proposed rule is sufficient for manufacturers to validate invoiced discounts. We decline to permit manufacturers to audit information beyond the data provided to the TPA.</P>
                    <P>After consideration of the comments received, we are finalizing § 423.2760 with modification, as described in our response to comments. Specifically, we are striking the words “on site,” “such,” and “the audit site” from the proposed regulation text at § 423.2760(a)(3)(iii), and we are modifying the regulatory text to specify that “audit” data cannot be removed from “such specified location”. We are also adding the word “calendar” to convey 60 calendar days at § 423.2760(a)(2), which was inadvertently left out of the regulation text in the proposed rule.</P>
                    <HD SOURCE="HD3">15. Dispute Resolution (§ 423.2764)</HD>
                    <P>At § 423.2764, CMS proposed a 3-level dispute resolution framework through which agreement holders can dispute applicable discounts that they were invoiced via the invoicing process at § 423.2756(a). Specifically, we proposed at § 423.2764(a) that an agreement holder may dispute applicable discounts invoiced to such agreement holder under § 423.2756(a) by filing an initial dispute. We proposed at § 423.2764(a)(1) that the initial dispute must be filed in the manner specified by CMS no later than the dispute submission deadline, which is defined at § 423.2704 as the date that is 60 calendar days from the date of the invoice containing the information that is the subject of the dispute. The disputing manufacturer must explain why it believes the invoiced discount amount is in error and must provide supporting evidence that is material, specific, and related to the dispute. We proposed at § 423.2764(a)(2) that CMS will issue a written determination on such initial dispute no later than 60 calendar days from the dispute submission deadline.</P>
                    <P>At § 423.2764(b), we proposed that an agreement holder that receives an unfavorable determination from CMS on its initial dispute, or that has not received a determination within 60 calendar days of the dispute submission deadline, may request review by the independent review entity (IRE) contracted by CMS. We proposed at § 423.2764(b)(1) that an agreement holder must file a request for review by the IRE in the manner specified by CMS no later than the earlier of 30 calendar days from the date of the unfavorable determination on the initial dispute, or 90 calendar days from the dispute submission deadline if no determination was made within 60 calendar days of the dispute submission deadline.</P>
                    <P>We proposed at § 423.2764(b)(2) that the IRE may seek additional information from any agreement holder that requests an independent review, for the purpose of considering the appeal. An agreement holder's failure to comply with an information request from the IRE within the timeframe specified could result in the IRE issuing a denial. In addition to the information provided by the agreement holder, the IRE will base its decision on information received by CMS, the TPA, the Part D sponsor, and other sources.</P>
                    <P>We proposed at § 423.2764(b)(3) that the IRE will issue a written decision to the agreement holder and to CMS no later than 90 calendar days from receipt of the request. At § 423.2764(b)(4), we proposed that the notice must include a clear statement indicating whether the decision is favorable or unfavorable to the agreement holder; an explanation of the rationale for the IRE's decision; and instructions on how to request a review by the CMS Administrator. At § 423.2764(b)(5), we proposed that a decision by the IRE is binding on all parties unless the agreement holder or CMS files a valid request for review by the CMS Administrator.</P>
                    <P>
                        At § 423.2764(c)(1), we proposed that an agreement holder or CMS may 
                        <PRTPAGE P="17422"/>
                        request review by the CMS Administrator following receipt of an unfavorable determination from the IRE. We proposed at § 423.2764(c)(2) that such request must be filed in the manner specified by CMS, no later than 30 calendar days from the date of the IRE decision. We proposed at § 423.2764(c)(3) that after completing the review and making a decision, the CMS Administrator will issue a written decision to both parties. Such decision by the CMS Administrator is final and binding under proposed § 423.2764(c)(4). At § 423.2764(d), we proposed that CMS will adjust future invoices, or implement an alternative reimbursement process if determined necessary, if a dispute is resolved in favor of the agreement holder. We further proposed at § 423.2756(b)(3) that agreement holders cannot withhold payment for any disputed invoiced amount, including while a dispute is pending, except as specified at § 423.2756(b)(3).
                    </P>
                    <P>We proposed at § 423.2764(e) that agreement holders cannot use this dispute resolution process to dispute a decision by CMS to terminate an agreement holder's participation in the Manufacturer Discount Program under § 423.2752(c)(1) or a decision by CMS about a manufacturer's eligibility for discount phase-ins described at § 423.2720. The dispute resolution process must be used specifically for the purpose of resolving disputes regarding applicable discounts invoiced to agreement holders under § 423.2756(a).</P>
                    <P>Regarding beneficiary disputes, the IRA does not require a dispute resolution mechanism for Part D enrollees with respect to the Manufacturer Discount Program and, as a practical matter, an individual would likely not be aware if a discount is provided on their claim, because in most cases, the Manufacturer Discount Program will not affect enrollee cost sharing, and consistent with section 1860D-14C(g)(4) of the Act, applicable discounts are not counted toward an enrollee's incurred costs. Nevertheless, any Part D enrollee who has a dispute about their plan's decision not to provide or pay for a Part D drug, including a dispute about whether a drug is excluded from Part D or about the amount of cost sharing, has the right to request a coverage determination from the plan and the right to appeal any coverage determination not fully favorable to the enrollee under the procedures specified in subpart M of part 423.</P>
                    <P>We received no comments on this section and are finalizing § 423.2764 as proposed.</P>
                    <HD SOURCE="HD3">16. Civil Money Penalties (§§ 423.1000, 423.1002 and 423.2768)</HD>
                    <P>Section 1860D-14C(e) of the Act requires that a manufacturer that fails to provide, in accordance with the terms of its Manufacturer Discount Program agreement and the requirements of the Manufacturer Discount Program, applicable discounts for applicable drugs covered by the manufacturer's Manufacturer Discount Program agreement and dispensed to applicable beneficiaries is subject to a civil money penalty (CMP) for each such failure. CMS proposed codifying this general rule at § 423.2768(a), in alignment with processes established in section 120 of the Manufacturer Discount Program Final Guidance.</P>
                    <P>CMS proposed at § 423.2756(b)(1) to require agreement holders to pay invoiced amounts to relevant Part D sponsors within 38 calendar days of receipt of a TPA invoice. CMS considers an agreement holder to have failed to provide applicable discounts if payment is not made within 38 calendar days, with limited exceptions as proposed at § 423.2756(b)(2) and (b)(3). As we stated in the proposed rule, it is imperative that agreement holders make timely payments under the Manufacturer Discount Program, and an agreement holder's failure to establish sufficient controls to ensure compliance with this requirement will not relieve the agreement holder of penalties imposed under section 1860D-14C(e)(1) of the Act.</P>
                    <P>We proposed at § 423.2768(b) that CMS will issue a notice of non-compliance to an agreement holder that fails to make a timely payment as required under § 423.2756(b), and that the agreement holder has 5 business days to respond to CMS.</P>
                    <P>Consistent with section 1860D-14C(e)(1) of the Act, we proposed at § 423.2768(c) that a CMP will be equal to the sum of the amount the agreement holder would have paid with respect to the applicable discount, plus 25 percent of such amount. We stated in the proposed rule that in situations where an agreement holder pays an invoice in part, but not in full, within the required timeframe, any CMP imposed by CMS would be based only on the outstanding invoiced amount that was not paid within the required timeframe. Additionally, while the amount of a CMP may be reduced by any invoiced amount the agreement holder pays after the 38-day timeframe, such late payments will not relieve the agreement holder of its obligation to pay the additional 25 percent penalty, which will be assessed on all invoiced amounts not paid within the required timeframe, as proposed at § 423.2756(b).</P>
                    <P>We proposed at § 423.2768(d) that if after issuing a notice of non-compliance, CMS makes a determination to impose a CMP on an agreement holder, CMS will send to such agreement holder a written notice of the determination to impose a CMP. Under our proposal, CMS would include the following 6 elements in the notice: a description of the basis for the determination, the basis for the penalty, the amount of the penalty, the date the penalty is due, the agreement holder's right to a hearing according to the administrative appeal process and procedures established in 42 CFR part 423, subpart T, and information about where to file the request for a hearing.</P>
                    <P>To ensure a consistent approach to CMPs, we proposed at § 423.2768(e) to apply existing appeal procedures for CMPs in 42 CFR part 423, subpart T to agreement holders appealing a CMP imposed under the Manufacturer Discount Program. Specifically, we proposed to amend paragraph § 423.1000(a)(3) by replacing it with new paragraphs (a)(3)(i) and (a)(3)(ii) to codify that CMS must impose a CMP on a manufacturer that fails to provide applicable discounts for applicable drugs of the manufacturer pursuant to both the terms of such manufacturer's Coverage Gap Discount Program agreement and such manufacturer's Manufacturer Discount Program agreement.</P>
                    <P>We also proposed conforming changes to the definition of “affected party” at § 423.1002 to revise the definition to refer to “for purposes of the Coverage Gap Discount Program, any manufacturer (as defined in § 423.100)” and “for purposes of the Manufacturer Discount Program, any manufacturer that is an agreement holder (as defined in § 423.2704)”.</P>
                    <P>Section 1128A(c)(2) of the Act specifically requires that CMS not collect a CMP until the affected party has received written notice and been given an opportunity for a hearing. Accordingly, we proposed to codify at § 423.2768(f)(1) that CMS may not collect a CMP until the affected party (as defined at § 423.1002) has received notice and the opportunity for a hearing under section 1128A(c)(2) of the Act.</P>
                    <P>
                        We proposed to codify timing requirements for collecting CMPs that are assessed under the Manufacturer Discount Program in alignment with section 120.3 of the Manufacturer Discount Program Final Guidance and with existing CMP appeal procedures codified in 42 CFR part 423, subpart T. Specifically, we proposed at 
                        <PRTPAGE P="17423"/>
                        § 423.2768(f)(2) that an agreement holder that has received from CMS a notice of determination to impose a CMP must pay such CMP in full within 60 calendar days of the date of the CMS notice of determination, except as provided in § 423.2768(f)(3). At § 423.2768(f)(3), we proposed that if the agreement holder requests a hearing to appeal in accordance with 42 CFR part 423, subpart T, the CMP is due, as applicable, once the administrative process specified in subpart T has concluded. We further proposed at § 423.2768(f)(4) that CMS will initiate the collection of a CMP owed by an agreement holder either following the expiration of 60 days from the date of the CMS notice of determination to impose a CMP, or, if later, the conclusion of the administrative process specified in 42 CFR part 423, subpart T, as applicable.
                    </P>
                    <P>Section 1860D-14C(e)(2) of the Act makes the provisions of section 1128A of the Act (except for subsections (a) and (b) of section 1128A of the Act) applicable to CMPs imposed under the Manufacturer Discount Program. We proposed to codify this requirement at § 423.2768(g).</P>
                    <P>At § 423.2768(h), we proposed that, in the event an agreement holder declares bankruptcy, as described in title 11 of the United States Code, and, as a result of such bankruptcy, fails to pay the total sum of the CMPs imposed, the government reserves the right to file a proof-of-claim and take any other action under bankruptcy law, as appropriate, to attempt to recover such unpaid amounts and any CMPs imposed by CMS under these proposed regulations.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a comment on our proposed regulations related to CMPs. The commenter argued that the language in our proposed CMP regulation fails to recognize the agency's flexibility and enforcement discretion. Pointing to language in proposed § 423.2768, which states that CMS “must impose a civil money penalty,” the commenter asserted that CMS's proposed regulation does not take into account factors in section 1128A(d) of the Act when determining the scope or amount of CMP. The commenter also stated that CMS procedures should allow for discussion and explanation between CMS and the manufacturer and should include an opportunity for the manufacturers to confer with the agency prior to imposition of CMPs and without requiring a manufacturer to request a formal hearing. The commenter stated generally that this would be consistent with government agencies issuing pre-enforcement notification letters or pursuing other informal means to give regulated parties an opportunity to respond before the agency initiates formal proceedings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's feedback on the proposed CMP regulations. We believe our proposed CMP regulations at §§ 423.1000, 423.1002, and 423.2768 are consistent with statutory requirements under the Manufacturer Discount Program, and that the clarity provided in our CMP regulation text is important for enforcement purposes. Section 1860D-14C(e) of the Act states that if a manufacturer fails to provide discounted prices for applicable drugs of the manufacturer dispensed to applicable beneficiaries in accordance with the Manufacturer Discount Program agreement in effect, such manufacturer “shall” be subject to a CMP for each such failure. Further, section 1860D-14C(e) of the Act explicitly provides the formula that must be used to determine the amount of such CMP.
                    </P>
                    <P>We agree with the commenter that CMS may exercise enforcement discretion in our imposition of CMPs. Our proposed regulation text does not preclude the agency from exercising discretion and allows an opportunity for dialogue prior to the agency making a determination to impose a CMP under the Manufacturer Discount Program, using the same process used under the Coverage Gap Discount Program. Proposed § 423.2768(b) provides that when an agreement holder fails to make a timely payment as required under § 423.2756(b), CMS will issue to the agreement holder a notice of non-compliance with information about the violation, and the agreement holder will have five business days from the date of the notice to respond to CMS. As we stated in response to similar comments in the Manufacturer Discount Program Final Guidance and in the preamble to the proposed rule, this gives the agreement holder an opportunity to provide additional context, evidence refuting the violation, or other factors CMS may consider when determining whether to impose a CMP. Part D sponsors advance applicable discounts at the point of sale on behalf of manufacturers, and it is essential that manufacturers, in turn, provide timely reimbursement. Accordingly, such discretion is generally limited to a situation where the manufacturer demonstrates that the non-compliance is due to a technical or other reason beyond the manufacturer's control.</P>
                    <P>After consideration of the public comments we received, we are finalizing without modification our proposals at §§ 423.1000, 423.1002, and 423.2768.</P>
                    <HD SOURCE="HD3">17. Severability</HD>
                    <P>We proposed that the Manufacturer Discount Program provisions finalized herein would be separate and severable from one another. Further, we proposed that if any of these provisions is held to be invalid or unenforceable by its terms, or as applied to any person or circumstance, or stayed pending further agency action, it is our intention that such provision shall be severable from this rule and not affect the remainder thereof, or the application of such provision to other persons not similarly situated or to other, dissimilar circumstances.</P>
                    <P>We received no comments on this section of our proposal and are finalizing without modification.</P>
                    <HD SOURCE="HD2">D. Definition of Creditable Coverage</HD>
                    <P>Section 1860D-13(b) of the Act contains provisions related to late enrollment penalties (LEPs), which are increases in monthly beneficiary premiums for individuals without creditable coverage for a continuous period of Part D eligibility of 63 days or longer prior to Part D enrollment. Per section 1860D-13(b)(5) of the Act, coverage meets the creditable coverage requirement “only if the coverage is determined (in a manner specified by the Secretary) to provide coverage of the cost of prescription drugs the actuarial value of which (as defined by the Secretary) to the individual equals or exceeds the actuarial value of standard prescription drug coverage.”</P>
                    <P>
                        The allowable methodologies used to determine creditable coverage have been updated a few times since the start of the Part D program, including most recently for CY 2025 and CY 2026 in the Final CY 2025 Part D Redesign Program Instructions and Final CY 2026 Part D Redesign Program Instructions.
                        <SU>25</SU>
                        <FTREF/>
                         Under changes to Part D made by the IRA, the definition of creditable prescription drug coverage at § 423.56(a) was modified in these Program Instructions. Prior to the Final CY 2025 Part D 
                        <PRTPAGE P="17424"/>
                        Redesign Program Instructions, § 423.56(a) specified that prescription drug coverage would be considered creditable “only if the actuarial value of the coverage equals or exceeds the actuarial value of defined standard prescription drug coverage under Part D in effect at the start of such plan year, not taking into account the value of any discount or coverage provided during the coverage gap, and demonstrated through the use of generally accepted actuarial principles and in accordance with CMS guidelines.” We now describe historical changes to the creditable coverage definition and allowable methodologies in greater detail.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             Draft CY 2025 Part D Redesign Program Instructions available at 
                            <E T="03">https://www.cms.gov/files/document/draft-cy-2025-part-d-redesign-program-instruction.pdf.</E>
                        </P>
                        <P>
                            Final CY 2025 Part D Redesign Program Instructions available at 
                            <E T="03">https://www.cms.gov/files/document/final-cy-2025-part-d-redesign-program-instructions.pdf.</E>
                        </P>
                        <P>
                            Draft CY 2026 Part D Redesign Program Instructions available at 
                            <E T="03">https://www.cms.gov/files/document/draft-cy-2026-part-d-redesign-program-instructions.pdf.</E>
                        </P>
                        <P>
                            Final CY 2026 Part D Redesign Program Instructions available at 
                            <E T="03">https://www.cms.gov/files/document/final-cy-2026-part-d-redesign-program-instruction.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        Since the start of the Part D program in 2006, CMS, consistent with section 1860D-13 of the Act, has permitted an entity offering a group health plan that is not applying for the retiree drug subsidy (RDS) under section 1860D-22(a) of the Act 
                        <SU>26</SU>
                        <FTREF/>
                         to use either actuarial equivalence testing or the creditable coverage “simplified determination methodology” to determine whether its prescription drug coverage is creditable. Some group health plans would undertake considerable workloads in conducting in-house actuarial testing, while others would use the simplified approach presented in the “Updated Creditable Coverage Guidance,” which we released on September 18, 2009. Under the simplified approach, coverage would be considered creditable if it:
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             The attestation of actuarial equivalence requirements for qualified retiree prescription drug plans (also known as plans receiving the Retiree Drug Subsidy) are set forth in section 1860D-22 of the Act and codified in § 423.884.
                        </P>
                    </FTNT>
                    <P>• Provides coverage for brand and generic prescriptions;</P>
                    <P>• Provides reasonable access to retail providers;</P>
                    <P>• The plan is designed to pay on average at least 60 percent of participants' prescription drug expenses; and</P>
                    <P>• Satisfies at least one of the following:</P>
                    <P>++ The prescription drug coverage has no annual benefit maximum or a maximum annual benefit payable by the plan of at least $25,000.</P>
                    <P>++ The prescription drug coverage has an actuarial expectation that the amount payable by the plan will be at least $2,000 annually per Medicare eligible individual.</P>
                    <P>++ For entities that have integrated health coverage, the integrated health plan has no more than a $250 deductible per year, has no annual benefit maximum, or a maximum annual benefit payable by the plan of at least $25,000, and has no less than a $1,000,000 lifetime combined benefit maximum.</P>
                    <P>The IRA eliminated the coverage gap phase and sunset the Coverage Gap Discount Program (CGDP) effective December 31, 2024. The Medicare Part D Manufacturer Discount Program (Manufacturer Discount Program) replaced the CGDP beginning January 1, 2025. The IRA revised section 1860D-22(a)(2)(A) of the Act to specify that any discount provided pursuant to the Manufacturer Discount Program established by the IRA under section 1860D-14C of the Act is not taken into account when determining the actuarial value of qualified retiree coverage. Additionally, section 1860D-14C(g)(1)(B) of the Act excludes enrollees in a qualified retiree prescription drug plan from the definition of applicable beneficiary for the purposes of the Manufacturer Discount Program. The changes made by the IRA required us to revise the existing regulatory definition of creditable prescription drug coverage in § 423.56(a). Under the requirement in section 11201(f) of the IRA that we use program instruction or other forms of program guidance to implement section 11201 of the IRA for 2025 and 2026, we issued a revised regulatory definition of creditable prescription drug coverage in § 423.56(a) in the Final CY 2025 Part D Redesign Program Instructions and Final CY 2026 Part D Redesign Program Instructions. In 2025 and 2026, the definition of creditable prescription drug coverage reads as follows (bolded and italicized text indicates the language we added in light of the IRA):</P>
                    <P>Creditable prescription drug coverage means:</P>
                    <P>
                        Any of the following types of coverage listed in paragraph (b) of this section only if the actuarial value of the coverage equals or exceeds the actuarial value of defined standard prescription drug coverage under Part D in effect at the start of such plan year, not taking into account the value of any discount 
                        <E T="7462">provided under section 1860D-14C of the Social Security Act,</E>
                         and demonstrated through the use of generally accepted actuarial principles and in accordance with CMS guidelines.
                    </P>
                    <P>In the Draft CY 2025 Part D Redesign Program Instructions, we proposed that because of the IRA changes to the Part D benefit, the simplified determination methodology would no longer be a valid methodology to determine whether such an entity's prescription drug coverage is creditable as of 2025. For instance, the increased plan liability in the catastrophic phase of the defined standard benefit requires sponsors to pay more than the 60 percent specified in the current simplified determination methodology and, therefore, continuing to use 60 percent would not satisfy requirements for actuarial equivalence for creditable coverage. We received several comments on the Draft CY 2025 Part D Redesign Program Instructions that raised concerns about the potential risk that a large number of Part D eligible individuals would no longer have creditable coverage through their group health plan if the existing simplified determination methodology were no longer available for 2025. Commenters were also concerned that group health plan sponsors would not have sufficient time to consider the impact of the Part D benefit changes made by the IRA to make decisions about their benefit offerings in time for 2025 coverage.</P>
                    <P>In response to those comments, in the Final CY 2025 Part D Redesign Program Instructions we recognized the IRA's sweeping changes to the Part D benefit in CY 2025, which, if coupled with the retirement of the creditable simplified determination methodology, could pose various challenges for group health plan sponsors and could have an adverse effect on certain Part D eligible individuals who could lose creditable coverage and be at risk for the Part D LEP. After consideration of the comments received and available options to mitigate potential disruptive effects of the Part D redesign on the group health plan market and the Part D eligible individuals served by such group health plans, we decided for CY 2025 to continue to permit use of the creditable coverage simplified determination methodology, without modification to the existing parameters, for group health plan sponsors not applying for the RDS. By permitting continued use of the creditable coverage simplified determination methodology for 2025, we stated we would have additional time to better assess the various impacts of the Part D redesign and evaluate modifications to this methodology to ensure Part D eligible individuals with creditable coverage continue to have prescription drug coverage that is at least as good as defined standard Part D coverage. We committed to re-evaluating the continued use of the existing simplified determination methodology, or establish a revised one, for 2026.</P>
                    <P>
                        For 2026, the Final CY 2026 Part D Redesign Program Instructions adopted a revised simplified determination methodology for non-RDS group health plans to determine whether their prescription drug coverage is creditable. Under the revised simplified determination methodology, coverage is 
                        <PRTPAGE P="17425"/>
                        deemed to provide prescription drug coverage with an actuarial value that equals or exceeds the actuarial value of defined standard Part D coverage if it meets all of the following standards:
                    </P>
                    <P>• Provides reasonable coverage for brand name and generic prescription drugs and biological products.</P>
                    <P>• Provides reasonable access to retail pharmacies.</P>
                    <P>• Is designed to pay on average at least 72 percent of participants' prescription drug expenses.</P>
                    <P>The revised simplified determination methodology retained some parameters of the prior methodology, such as a requirement for reasonable coverage of brand and generic prescription drugs and reasonable retail pharmacy access. We added coverage of biological products due to changes in the prescription drug landscape since the prior methodology was developed. We removed the requirements related to annual and lifetime benefit maximums because changes to the health insurance landscape under the Affordable Care Act have essentially eliminated such limitations among group health plans. We also removed requirements related to an annual deductible, because outside of the Medicare program it is unusual for health and drug coverage to be separate benefits, and integrated health and drug plans could have a significantly higher deductible than standard Part D coverage but still offer comparable drug coverage. Although plans with higher annual deductibles (including high deductible health plans) might have appeared less likely to meet the requirement to pay at least 72 percent of prescription drug expenses, such risk may be mitigated through other aspects of the benefit such as not applying a deductible to preventive (that is, maintenance) medications, a reasonable and supportable allocation of the deductible attributable to prescription drug expenses, or offering lower cost sharing than standard Part D coverage once the deductible is met.</P>
                    <P>Under the revised simplified methodology for 2026, the group health plan coverage must be designed to pay at least 72 percent of participants' prescription drug expenses, versus 60 percent under the prior methodology. We made this revision because of program changes in Part D—in particular, the benefit changes mandated by the IRA, which significantly enhanced the Part D defined standard benefit. These changes—which included a $35 cost sharing cap on a month's supply of each covered insulin product, access to recommended adult vaccines without cost sharing, the implementation of an annual out-of-pocket threshold ($2,100 for CY 2026), and the elimination of the coverage gap phase of the benefit—increased the proportion of drug costs paid by the Part D plan sponsor. In light of the more robust Part D benefit under the IRA, we determined that the 60 percent value was no longer an accurate representation of the value of the Part D benefit and that group health plan coverage for 2026 should be designed to pay on average at least 72 percent of participants' prescription drug expenses in order to provide coverage to the individual that equals or exceeds the actuarial value of standard Part D coverage, as required by section 1860D-13(b)(5) of the Act. We estimated the actuarial value of the defined standard benefit for 2026 using 2023 Part D claims experience under the projected 2026 benefit structure. The 2026 benefit parameters were deflated to a 2023 dollar basis. We estimated that the actuarial value increased to 72 percent, primarily as a result of the changes made by the IRA to the Part D defined standard benefit.</P>
                    <P>The Draft CY 2026 Part D Redesign Program Instructions stated that non-RDS group health plans could make the determination of creditable coverage either by (1) determining whether the actuarial value of the coverage equals or exceeds the actuarial value of defined standard Part D coverage, demonstrated through generally accepted actuarial principles, or (2) using the revised simplified determination methodology described previously. In response to comments received requesting a phased in approach to this change, in the Final CY 2026 Part D Redesign Program Instructions, we decided to allow for a transition year whereby non-RDS group health plans that opted to make the determination of creditable coverage through the simplified determination methodology were permitted for 2026 to use either the 2009 simplified determination methodology (that is, among other requirements, at least 60 percent of prescription drug expenses) or the revised simplified determination methodology (that is, among other requirements, at least 72 percent of prescription drug expenses) to determine whether their prescription drug coverage is creditable. We determined that this transitional policy for CY 2026 was appropriate to minimize potential risks to the employer group market and to Part D eligible individuals who may no longer have access to creditable coverage through an employer plan. In the Final CY 2026 Part D Redesign Program Instructions, we also stated our intention to propose to no longer permit use of the 2009 simplified determination methodology for CY 2027.</P>
                    <P>As the IRA's directive to implement the Part D redesign by program instruction or other forms of program guidance expires in 2027, we proposed codifying in § 423.56(a) the revised definition of creditable coverage in the Final CY 2026 Part D Redesign Program Instructions to account for the Manufacturer Discount Program. We also proposed to amend § 423.56(a) to sunset use of the 2009 simplified determination methodology and codify the revised simplified determination methodology, starting with 2027. In § 423.56(a), we proposed to require that non-RDS group health plans may either use actuarial equivalence testing under § 423.56(a)(1) or the revised simplified determination methodology under § 423.56(a)(2) and in place for CY 2026, with one modification from 72 to 73 percent of prescription drug costs the non-RDS group health plan must cover compared with coverage under a Part D defined standard plan.</P>
                    <P>To determine the percent of prescription drug costs that must be covered to be creditable, our modeling is based on the prescription drug event (PDE) data for a recent year. We modify the claims line by line to adjust for benefit differences while maintaining actual utilization patterns. For the purposes of determining what the simplified determination value should be for a given future year, we readjudicate all claims as they would have been paid under the defined standard benefit design for the year we are projecting. This process also requires estimating the benefit parameters for the year of interest and deflating the values to align with the historical PDE experience year we are using in our projection. After the PDE records are adjusted to the benefit design of the future year, we aggregate the results to determine the average percentage of gross drug cost that would be covered by a defined standard plan. We use this value rounded to the nearest whole percentage point as the minimum percent of participants' prescription drug expenses that the non-RDS health plan benefit needs to be designed to pay in order to qualify as creditable coverage.</P>
                    <P>
                        As discussed and consistent with the methodology described previously in this section, we estimated the actuarial value of the defined standard benefit for 2026 using 2023 Part D claims experience under the projected 2026 benefit levels deflated to a 2023 dollar basis to arrive at the requirement that a 
                        <PRTPAGE P="17426"/>
                        non-RDS health plan's benefit must be designed to pay on average 72 percent of participants' prescription drug expenses to meet the conditions of the revised simplified determination methodology. For 2027, this model estimates an actuarial value of 73 percent for the defined standard benefit. In subsequent years, this value is projected to increase, ultimately reaching 75 percent in 2030 and stabilizing thereafter. Accordingly, we proposed a minimum of 73 percent instead of 72 percent for 2027. We further proposed that we would update this figure for future years in a time and manner as we determine, consistent with the actuarial equivalence requirements in section 1860D-13(b)(5) of the Act and the methodology described earlier in this section. We intend to update the percentage via subregulatory guidance, such as a memo issued by the Health Plan Management System (HPMS). We would release this guidance in advance of the yearly Part D bid submission deadline for non-RDS group health plans to take into account as they prepare for the following year.
                    </P>
                    <P>As described previously, the proposed changes to § 423.56 would retire the simplified approach presented in the “Updated Creditable Coverage Guidance” that we released on September 18, 2009, and generally proposed to codify the options available to plans in the Final CY 2026 Part D Redesign Program Instructions: choosing between conducting actuarial equivalence testing themselves or the revised simplified determination methodology. Non-RDS plans using either approach in the proposed § 423.56(a) can attest to the creditable coverage of their plan offerings, thereby ensuring individuals in creditable non-RDS plans will not owe an LEP upon enrollment in a Part D plan. The proposed § 423.56 requirements have mostly been previously implemented and our proposal in this rulemaking is similar to the ways plans assessed creditable coverage in 2026. We do not believe that the proposed changes to the regulatory text would have a significant impact on plan sponsors or individuals. There is no change to paperwork burden to plans or individuals.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated their support for the proposed creditable coverage methodology, citing that it appropriately balances a few considerations: the need to have standards that accurately capture the value of Part D coverage; the need to let patients make informed decisions about whether they have adequate prescription drug coverage; the need to minimize paperwork burdens on non-Medicare plans; and the need to protect taxpayers from the increase in the cost of Medicare Part D that would occur if eligible individuals were able to wait to enroll until they had high prescription drug expenses without any penalty.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asked whether we account for the selected drug subsidies under section 1860D-14D of the Act and federal reinsurance under 1860D-15(b)(1)(B) of the Act with respect to selected drugs in the determination of creditable coverage. They requested that CMS treat selected drug subsidies under sections 1860D-14D of the Act and federal reinsurance under 1860D-15(b)(1)(B) with respect to selected drugs analogously to manufacturer discounts under section 1860D-14C and exclude them from the creditable coverage methodology. The commenter stated that excluding these amounts from the creditable coverage methodology would be consistent with the approach established for the Manufacturer Discount Program and help employer-sponsored group health plans continue to provide creditable prescription drug coverage, including retiree drug coverage through the Retiree Drug Subsidy (RDS) program, as more drugs become selected over time.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their input. As stated in the Final CY 2025 Part D Redesign Program Instructions, CMS determines actuarial equivalence based on plan liability and does not include subsidies such as low income cost sharing (LICS). Consistent with the existing policy, federal reinsurance in the catastrophic phase is included in the plan paid amount. The value of any selected drug subsidy under section 1860D-14D of the Act is not included in the determination of actuarial value.
                    </P>
                    <P>
                        To clarify the existing policy that the selected drug subsidy is excluded from the determination of actuarial equivalence, we have revised § 423.56(a) to state that the actuarial value of creditable prescription drug coverage “equals or exceeds the actuarial value of defined standard prescription drug coverage under Part D in effect at the start of such plan year, not taking into account the value of any discount provided under section 1860D-14C of the Act 
                        <E T="04">or of any selected drug subsidy under section 1860D-14D</E>
                         of the Act” (bold indicates new text).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters were supportive of codifying the revised simplified determination methodology but requested a delay in moving to the 73 percent of prescription drug costs that a plan must cover for it to be considered creditable. A couple commenters requested a 1-year delay and another commenter suggested starting to phase in 66 percent of prescription drug expenses in 2027 and move to 73 percent in 2028. The commenter questioned if CMS does not adopt a phase-in approach, to allow a 1-year grace period of allowing plans to continue to use the existing simplified determination methodology.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the support of codifying the revised simplified determination methodology and do not believe that further delay or grace periods for adopting this methodology are justified at this time. In the Final CY 2026 Part D Redesign Program Instructions, we provided a grace period that permitted non-RDS group health plans to use either the existing simplified determination methodology or the revised simplified determination methodology to determine whether their prescription drug coverage is creditable. In those instructions, we emphasized that the grace period was for CY 2026 only and that for CY 2027 and subsequent years, CMS intended to propose to no longer permit use of the existing simplified determination methodology. As explained in the Final CY 2025 Part D Redesign Program Instructions and Final CY 2026 Part D Redesign Program Instructions, there were significant changes to the Part D program that took effect in those years under the IRA's Part D redesign that warranted a transitional delay to a revised simplified determination methodology. We believe that plans now have adequate experience under the new benefit design to incorporate the changes we proposed and are finalizing in this rulemaking. Additionally, as discussed above, plans have been on notice that we intended to retire the existing simplified determination methodology in favor of transitioning to one that more accurately reflects the actuarial value of a defined standard Part D plan in accordance with section 1860D-13(b)(5) of the Act. For 2027, we are finalizing the percent value at 73 percent. For 2028 and going forward, we will release the percentage of prescription drug costs to use in the creditable coverage methodology with enough time for group health plans to take into account when designing their plan benefits.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter highlighted the timing of releasing guidance in future years that would, as needed, update the percentage value of prescription drug expenses and requested that it be released in a timely manner—ideally at the same time the 
                        <PRTPAGE P="17427"/>
                        Part D Defined Standard benefit parameters are released.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter and agree. We would release this guidance in advance of the yearly bid submission deadline for Part D plan sponsors so that they may consider the guidance as they prepare their bids and group health plans to design their plan benefits. This timing would align with the release of the Part D Defined Standard benefit parameters as the commenter suggests.
                    </P>
                    <P>We appreciate all of the comments on this proposal and are largely finalizing this provision as proposed, with one modification to specify in § 423.56(a) that the value of any selected drug subsidy under section 1860D-14D of the Act is not included in the determination of actuarial value.</P>
                    <HD SOURCE="HD2">E. Outlier Prescriber Criteria</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Section 6065 of the Substance Use Disorder Prevention that Promotes Opioid Recovery and Treatment for Patients and Communities (SUPPORT) Act (Pub. L. 115-271) added subparagraph (D) to section 1860D-4(c)(4) of the Act, which requires the Secretary to identify Part D outlier prescribers of opioids, using the valid prescriber National Provider Identifier (NPI) included on claims for covered part D drugs, and notify those prescribers that they have been identified as outliers. The notifications provided to prescribers identified as outliers include information on how the prescriber compares to other prescribers within the same specialty and geographic area, as well as resources on proper prescribing methods.</P>
                    <P>
                        The Secretary is required to establish thresholds for identifying whether a prescriber is an outlier based on prescribers in the same specialty and geographic area, with certain exclusions. We currently define outlier prescribers as those in the top 25th percentile when compared to their peers (that is, prescribers in the same National Plan &amp; Provider Enumeration System (NPPES) taxonomy and State) for both (1) co-prescribing opioids and benzodiazepines, and (2) the average daily morphine milligram equivalent (MME) prescribed to those patients. Exclusions to this methodology include (1) beneficiaries who have cancer or sickle cell disease diagnosis, are enrolled in hospice, or reside in a long-term care facility; and (2) providers subject to a current CMS or HHS Office of Inspector General (“HHS-OIG”) investigation. Over time, should the opioid crisis continue to evolve and CDC practice guidelines change, we will make further adjustments to the methodology, as appropriate, to ensure beneficiary safety, as well as alignment with clinical standards and regulatory requirements that govern the Medicare Part D program. Our current outlier prescriber methodology is available on the CMS website (
                        <E T="03">https://www.cms.gov/files/document/methodology-comparison.pdf</E>
                        ), and any future updates to the methodology will be made at this website location.
                    </P>
                    <P>Section 6065 of the SUPPORT Act also established additional requirements for outlier prescribers that are identified by us as “persistent” at section 1860D-4(c)(4)(D)(v) of the Act, although it does not provide criteria or thresholds to determine persistently identified outlier prescribers of opioids. First, we may require a persistent outlier to enroll in the Medicare program but only after other appropriate remedies have been provided, such as receiving technical assistance on best practices related to prescribing opioid and non-opioid pain management therapies through entities funded through section 6052 of the SUPPORT Act. Second, we are required to communicate information on such prescribers to Part D plan sponsors no less frequently than annually. Considering the significant implications of being identified as an outlier prescriber of opioids, including a persistent outlier, we believe it prudent to clearly outline the key criteria for such a designation in regulation.</P>
                    <HD SOURCE="HD3">2. Proposed Provisions</HD>
                    <P>First, to reflect the requirements surrounding the Secretary's identification of an outlier prescriber of opioids under section 1860D-4(c)(4)(D)(ii) of the Act, we proposed to define an outlier prescriber of opioids as a statistical outlier when compared to their peers based on NPPES taxonomy and state. Second, given the potential impact(s) of being identified as a persistent outlier prescriber of opioids (for example, the potential for becoming a lead for a Part D plan sponsor investigation), we proposed and sought public comment on what criteria should apply for designation as a persistent outlier prescriber of opioids. We proposed to establish a threshold to identify persistent outlier prescribers of opioids as those outlier prescribers who receive three consecutive outlier prescriber notifications from us based on the same methodology. If there is an update to the methodology, only prescribers that have been identified three times by the same methodology would be considered “persistent.” We sought comments on this threshold.</P>
                    <P>Specifically, we proposed to add a paragraph (f) under § 423.504:</P>
                    <P>• (f) Outlier Prescribers of Opioids.</P>
                    <P>++ CMS will identify and send notifications to outlier prescribers of opioids, which includes information about how the prescriber compares to other specified prescribers and resources on proper prescribing methods.</P>
                    <P>++ At least annually, CMS will communicate information about persistent outlier prescribers of opioids to all Part D plan sponsors.</P>
                    <P>We also proposed to add the following definitions under § 423.4:</P>
                    <P>
                        <E T="03">Outlier prescriber of opioids</E>
                         means a prescriber who is a statistical outlier compared to their peers in a specialty and geographic area.
                    </P>
                    <P>
                        <E T="03">Specialty</E>
                         means the National Plan and Provider Enumeration System (NPPES) taxonomy of a prescriber.
                    </P>
                    <P>
                        <E T="03">Geographic area</E>
                         means the State in which a prescriber is practicing.
                    </P>
                    <P>
                        <E T="03">Persistent outlier prescriber of opioids</E>
                         means an outlier prescriber identified by CMS in three consecutive outlier prescriber notifications.
                    </P>
                    <P>We received public comments on these provisions in the proposed rule. The following is a summary of the comments we received and our responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested that the statistical identification of outlier prescribers may disproportionately affect those prescribers that treat patients with chronic pain or complex diagnoses and ultimately affect proper pain management and palliative care of beneficiaries. A commenter suggested that the use of a statistical methodology could identify prescribers whose prescribing is clinically appropriate and suggests identifying outliers by considering beneficiary specific clinical factors, comorbidities, and treatment history.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenters' insights and considerations for the prescribers of our beneficiaries with chronic pain and complex care. CMS agrees with commenters that statistical analyses may identify outlier prescribers that care for patients with unique circumstances that result in prescribing patterns that vary from the norm, yet are still clinically appropriate. As such, CMS acknowledges this point in the annual outlier prescriber notifications and encourages prescribers to utilize the information to review their current prescribing habits and take advantage of educational resources and programs to remain current on treatment guidelines. While CMS notes that utilizing 
                        <PRTPAGE P="17428"/>
                        beneficiary specific clinical factors, comorbidities, and treatment history would allow for a robust review of individual prescriber habits, it is unrealistic for CMS to do that on a broad scale for all prescribers as part of an educational analysis and would require the review of medical records. CMS would encourage prescribers notified as outliers to internally review their medical records to ensure that they are prescribing appropriately based on their patients' individual health and care plans.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the current excluded patient groups within CMS's methodology. Some commenters suggested that beneficiaries in palliative care should be excluded. Another commenter recommended that in addition to beneficiaries with cancer pain, those beneficiaries with cancer treatment related pain should also be excluded.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS, beginning with the 2027 letters is aligning the exclusion criteria for beneficiaries with other CMS initiatives and the definition of an exempted beneficiary at § 423.100, including beneficiaries in hospice or receiving palliative or end of life care; residing in a long-term care facility; being treated for cancer-related pain; or with sickle cell disease. Of note, in a CMS final rule (89 FR 30448) the definition at § 423.100 shifted the terminology from `active cancer-related pain' to `cancer-related pain' effective January 1, 2025. CMS currently utilizes a year look-back period to identify beneficiaries with past cancer treatment.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended maintaining a standardized statistical methodology to improve transparency and prevent variation, in addition to a standardized notification letter and prescriber education materials. These commenters recommended CMS refine the methodology to keep up with changing opioid practice and consider accounting for intermittent benzodiazepine use.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS currently maintains both a methodology and aggregate data summary for public consumption found at 
                        <E T="03">https://www.cms.gov/about-cms/story-page/prescribing-opioids.</E>
                         The methodology and aggregate data are updated annually to align with the latest outlier prescriber notifications. CMS does refine the methodology regularly and considers changes to guidelines and will continue to do so going forward, including appropriate thresholds for being identified as an outlier. Annually, in each notification to prescribers identified as an outlier, CMS provides standardized language, including educational resources for the prescriber to reference for up-to-date opioid prescribing best practices. In identifying outlier prescribers, CMS currently only considers beneficiaries receiving a benzodiazepine that overlaps with an opioid for a consecutive 30 days but thanks the commenters for their suggestion and will continue to refine the methodology, as necessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters noted that guidelines no longer set thresholds as these limited access to care for beneficiaries in the high-risk groups. A commenter recommended CMS limit the prescribing threshold to the top 5 or 10 percent as a 25 percent threshold is overly-broad.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges the Centers for Disease Control and Prevention (CDC) 2022 opioid guideline update and shift from morphine milliequivalent (MME) thresholds. CMS does not utilize a single MME threshold for this analysis but rather uses a comparative analysis of prescriber habits according to specialty and state to determine outlier prescribers of opioids. CMS also notes that the annual outlier prescriber letters are based on a statistical methodology, and CMS clearly recognizes that an outlier may be prescribing within clinical norms for certain patient populations and still be identified as an outlier. CMS does refine the methodology regularly and considers changes to guidelines and will continue to do so going forward, including appropriate thresholds for being identified as an outlier.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter also recommended that CMS establish an appeals process for being identified as an outlier.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS takes no administrative action based on the outlier prescriber identification. These letters are solely an identification that the identified prescribers are statistically different than other prescribers in their same specialty and state in an effort to provide education on prescribing practices. As such, no appeals process is necessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several other commentors were in support of the proposals and definitions for identifying outliers and persistent outliers but a commenter expressed that CMS's support is critical as plan sponsors may not have all information necessary to identify potential outliers on a provider and beneficiary level. It was recommended that CMS continue to release the methodologies and updates on the website.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their support and will continue to release the methodologies and updates on the website, 
                        <E T="03">https://www.cms.gov/about-cms/story-page/prescribing-opioids.</E>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters questioned the utilization of NPPES for prescriber specialty as it is dependent on a prescriber updating their taxonomy and using an appropriate taxonomy code. A commenter suggested CMS consider the order of taxonomy codes in NPPES. A few commenters recommended the need for consideration of subspecialties as some complex patients are treated by physicians of a subspecialty under a more general primary specialty. A commenter recommended that CMS consider different thresholds for different specialties.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their suggestions on further refining the taxonomy of a prescriber by subspecialty. CMS will consider this going forward. CMS encourages prescribers to update NPPES accordingly when taxonomy changes occur to ensure they are up to date and accurate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed CMS's proposed methodology and recommended that CMS work collaboratively with physician groups and other stakeholders to develop alternative approaches that ensure continued access to care, eliminate arbitrary prescribing thresholds, and avoid targeting physicians treating complex patients. A commenter suggested that the proposal to report persistent outliers would lead Part D plan sponsors to refuse patient prescriptions from the prescribers and lead to patient harm. Additionally, a commenter suggested that CMS clarify what the Part D plan sponsors' expectations were for the information received on persistent outliers. Another commenter suggested that CMS provide plan sponsors with flexibility in overseeing the appropriate use of opioid therapies and to collaborate with plan sponsors. One commenter suggested that CMS and plan sponsors review for outlier prescribers prescribing based on specialty-specific norms and allow for clinical review before adverse actions are imposed.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 6065 of the SUPPORT Act requires CMS to identify outlier prescribers of opioids based on specialty and geographic area and provide notification annually to such providers. CMS collaborated with external stakeholders to establish the thresholds CMS utilizes to determine a prescriber is an outlier and continuously works with plan sponsors and other stakeholders to ensure oversight of the Part D program and provide the best outcomes for Medicare 
                        <PRTPAGE P="17429"/>
                        beneficiaries. Consistent with section 1860D-4(c)(4)(D)(v) of the Act, CMS will issue a persistent outlier prescriber report to plan sponsors in an effort for increased transparency and provide investigative leads. CMS understands the concerns from commenters regarding the potential for unsubstantiated penalties on the prescribers identified as persistent outliers; however, this report will identify outliers across the Medicare Part D program and assist plan sponsors that may have limited views of trends and schemes within their own data. CMS will direct plan sponsors to not act solely on the information in the report without performing their own internal fraud, waste, and abuse efforts that substantiate their actions, thereby allowing plan sponsors to maintain autonomy to review any persistent outliers for specialty norms and conduct clinical review in accordance with their organizations policies and procedures. CMS will continue to clarify in each outlier prescriber notification letter that each prescriber's unique circumstances may result in prescribing patterns that vary from the norm yet are still clinically appropriate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters recommended CMS identify persistent outliers more frequently than annually to ensure proper oversight. Another commenter suggested that CMS provide a list of all outliers to Part D plan sponsors, not just those that are classified as persistent. One commenter recommended reviewing outlier prescribing behavior every 6 months to not only identify prescribers by statistical comparison but also percent increase in their prescribing. Additionally, a commenter recommended CMS look at prescribing trends.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the feedback and clarifies that alternative options have been considered. Providing persistent outlier letters more frequently than annually is allowable in accordance with section 1860D-4(c)(4)(D)(v) of the Act; however, CMS believes prescribers should have the opportunity to make prescribing adjustments, if necessary, prior to being identified as an outlier on subsequent notification. Annual outlier notifications allow prescribers identified as an outlier to have approximately 6 months of time to make prescribing changes after receiving the outlier letter. CMS also disagrees with releasing all outlier prescribers to plan sponsors annually as the statutory requirement, section 1860D-4(c)(4)(D)(v) of the Act, applies to only those outliers identified as persistent. CMS believes that one annual identification does not establish a pattern of behavior. In response to a commenter recommending that CMS look at prescriber trends, CMS does evaluate trends internally and externally posts a data summary chart for outliers identified by state each year on the CMS website.
                        <SU>27</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             See: 
                            <E T="03">https://www.cms.gov/files/document/opioid-benzodiazepine-prescribing-patterns.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that plan sponsors have additional requirements to offer education, peer consultation, pain management, and addiction specialists, as well ensure beneficiaries have access to medication-assisted therapy and a variety of counseling options. Another commenter recommends CMS consider additional steps to deter persistent outlier prescriber behavior beyond technical assistance and Medicare provider enrollment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the suggestion to have plan sponsors provide additional education and services to both outlier providers and their beneficiaries. CMS will consider recommending to plan sponsors that they offer services that align with their current organization's contracts with both prescribers and beneficiaries in their networks. CMS will also continue to review and assess other steps that can be taken to address outlier prescribers.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the provisions as proposed. Section 6065 of the SUPPORT Act (Pub. L. 115-271) and section 1860D-4(c)(4)(D)(v) of the Act requires CMS to notify outlier prescribers based on specialty and state and provide information about persistent outliers to plan sponsors annually. While CMS received comments and feedback on specific methodology considerations, CMS is not adopting these comments in this final rule. Considerations and recommendations for exclusion criteria, thresholds, postings of methodology and other documents, and frequency of reporting will all be considered by CMS annually through program instruction or otherwise as we continue to refine the methodology and enhance our oversight of the Medicare Part D program.</P>
                    <HD SOURCE="HD2">F. Reopening and Payment Appeals</HD>
                    <P>The Inflation Reduction Act of 2022 (Pub. L. 117-169) made several amendments to Part D of Title XVIII of the Act, including adding section 1860D-14C of the Act, which describes the Manufacturer Discount Program; section 1860D-14D of the Act, which describes the Selected Drug Subsidy Program; and section 1860D-15(h) of the Act, which describes the temporary retrospective subsidy for the reduction in cost-sharing and deductible for adult vaccines recommended by the advisory committee on immunization practices (ACIP) and insulin. The temporary retrospective subsidy for ACIP-recommended adult vaccines and insulin was limited to contract year 2023 and is hereinafter referred to as the Inflation Reduction Act Subsidy Amount (IRASA).</P>
                    <P>
                        In subregulatory guidance, we described the reconciliation and payment determination processes for the Manufacturer Discount Program, selected drug subsidy, and IRASA.
                        <SU>28</SU>
                        <FTREF/>
                         For the Manufacturer Discount Program and the selected drug subsidy, we make monthly prospective payments for estimated costs submitted with bids, then make final payments based on the plan's actual costs after a coverage year after obtaining all of the information necessary to determine the amount of payment through cost-based reconciliations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             See the HPMS memorandum, Revised Medicare Part D Manufacturer Discount Program Final Guidance, December 20, 2024 (available at 
                            <E T="03">https://www.cms.gov/files/document/revised-manufacturer-discount-programfinal-guidance122024.pdf</E>
                            ); Final CY 2026 Part D Redesign Program Instructions (available at 
                            <E T="03">https://www.cms.gov/files/document/final-cy-2026-part-d-redesign-program-instruction.pdf</E>
                            ); and HPMS memorandum, PDE Reporting Instructions for Implementing the Cost Sharing Maximums Established by the Inflation Reduction Act for Covered Insulin Products and ACIP-Recommended Vaccines for Contract Year 2023, September 26, 2022 (available 
                            <E T="03">https://www.cms.gov/files/document/2023-pde-reporting-instructions.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <P>IRASA is the difference between the beneficiary cost-sharing for a covered insulin product or an ACIP-recommended adult vaccine under the plan's 2023 benefit design and the applicable statutory maximum cost-sharing ($35 for each covered insulin product and $0 for ACIP-recommended adult vaccines). The difference was reimbursed by Medicare during the 2023 Part D payment reconciliation. We proposed to amend § 423.308 to add the definition of Inflation Reduction Act Subsidy Amount (IRASA).</P>
                    <P>
                        We proposed that the Manufacturer Discount Program reconciliation, selected drug subsidy reconciliation, and IRASA reconciliation payment determinations would be payment determinations that may be reopened by CMS under § 423.346 and would also be appealable by the Part D sponsors under § 423.350. Therefore, we proposed to update the existing regulation concerning the reopening of final payment determinations and the existing payment appeals regulation by 
                        <PRTPAGE P="17430"/>
                        adding the Manufacturer Discount Program reconciliation, selected drug subsidy reconciliation, and IRASA reconciliation payment determinations. We also proposed to amend the time for filing a payment appeal under the existing payment appeals provision.
                    </P>
                    <HD SOURCE="HD3">1. Definition of Inflation Reduction Act Subsidy Amount (IRASA)</HD>
                    <P>Section 1860D-2(b)(9) of the Act imposes a $35 monthly limit on cost sharing for a month's supply of each covered insulin product throughout all phases of the Part D benefit for CYs 2023, 2024, and 2025. For CY 2026 and each subsequent year, this limit is the lesser of: (1) $35, (2) an amount equal to 25 percent of the maximum fair price established for the covered insulin product in accordance with Part E of title XI of the Act, or (3) an amount equal to 25 percent of the negotiated price, as defined in § 423.100, of the covered insulin product under the Part D Prescription Drug Plan (PDP) or Medicare Advantage Prescription Drug (MA-PD) plan. Section 1860D-2(b)(8) of the Act requires the elimination of beneficiary cost sharing for ACIP-recommended adult vaccines that are administered in accordance with the ACIP recommendation (hereafter referred to as “ACIP-recommended adult vaccines”) under a Part D plan throughout the entire Part D benefit beginning January 1, 2023. Section 1860D-15(h) of the Act requires that a temporary retrospective subsidy be paid to Part D plans for the reduction in cost sharing and the elimination of the deductible for ACIP-recommended adult vaccines and covered insulin products during the 2023 plan year—the Inflation Reduction Act Subsidy Amount (IRASA).</P>
                    <P>We proposed to amend § 423.308 to add the definition of Inflation Reduction Act Subsidy Amount (IRASA). Under our proposed rule, Inflation Reduction Act Subsidy Amount (IRASA) would mean a temporary retrospective subsidy paid to Part D plan sponsors for contract year 2023 for the statutory reduction in cost-sharing and deductible for covered insulin products or for advisory committee on immunization practices (ACIP)-recommended adult vaccines administered in accordance with the ACIP recommendation and is equal to the difference between the following: (1) The beneficiary cost-sharing for a covered insulin product or an ACIP-recommended adult vaccine under the plan's approved bid submitted under § 423.265 for contract year 2023, and (2) the applicable statutory maximum cost-sharing for the covered insulin product or for the ACIP-recommended adult vaccine for contract year 2023.</P>
                    <P>We did not receive comments on this section of the proposed rule and are finalizing the definition of Inflation Reduction Act Subsidy Amount (IRASA) at § 423.308 as proposed.</P>
                    <HD SOURCE="HD3">2. Reopenings</HD>
                    <P>
                        Under the authority under section 1860D-15(f)(1)(B) of the Act, the Secretary has the right to inspect and audit any books and records of a Part D sponsor or MA organization that pertain to the information regarding costs provided to the Secretary. We stated in our final rule, “Medicare Program; Medicare Prescription Drug Benefit,” which appeared in the January 28, 2005, 
                        <E T="04">Federal Register</E>
                         (70 FR, 4316), that this right to inspect and audit would not be meaningful, if upon finding mistakes under such audits, the Secretary was not able to reopen final payment determinations. Therefore, we established the reopening provision at § 423.346, which allows CMS, at its discretion, to reopen and revise initial or reconsidered specified payment determinations. Section 423.346(a) lists the payment determinations that we may reopen and revise. These payment determinations include the final amount of direct subsidy described in § 423.329(a)(1), final reinsurance payments described in § 423.329(c), the final amount of the low-income subsidy described in § 423.329(d), and final risk corridor payments as described in § 423.336. In our final rule, “Medicare Program; Contract Year 2016 Policy and Technical Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Programs,” which appeared in the February 12, 2015 
                        <E T="04">Federal Register</E>
                         (80 FR 7936), we added the Coverage Gap Discount Program reconciliation payment to the list of payment determinations that we may reopen and revise.
                    </P>
                    <P>
                        We proposed to amend § 423.346(a) to add the Manufacturer Discount Program reconciliation payment determination, the selected drug subsidy reconciliation payment determination, and the IRASA reconciliation payment determination to the list of payment determinations that we may reopen and revise. Under our proposal, these payment determinations would be subject to reopening consistent with the current reopening guidelines described at § 423.346, which are explained in detail in our final rule, “Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024—Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE),” which appeared in the April 23, 2024 
                        <E T="04">Federal Register</E>
                         (89 FR 30460) (hereinafter referred to as the Contract Year 2025 Final Rule).
                    </P>
                    <P>
                        Under our proposal, the selected drug subsidy reconciliation payment determination and the IRASA reconciliation payment determination would be included in scheduled global reopenings and could be included in targeted reopenings, which are defined at § 423.308 (definition of 
                        <E T="03">Reopening</E>
                        ). However, similar to the Coverage Gap Discount Program reconciliation payment determination, we anticipate that we would rarely reopen the Manufacturer Discount Program reconciliation payment determination. This is because Manufacturer Discount Program invoicing continues after the Manufacturer Discount Program reconciliation, and sponsors receive payments from the pharmaceutical manufacturers for a total of 17 quarters.
                        <SU>29</SU>
                        <FTREF/>
                         Under our proposal and similar to current guidance in the CY 2025 Final Rule, we would also be able to reopen and revise the Manufacturer Discount Program reconciliation, selected drug subsidy reconciliation, and the IRASA reconciliation payment determinations, as necessary, to correct certain issues such as a CMS-identified problem with an internal CMS file that we used in a payment reconciliation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             See the Medicare Part D Coverage Gap Discount Program (CGDP) and Manufacturer Discount Program (MDP) Calendar, available at 
                            <E T="03">https://tpadministrator.com/internet/tpaw3_files.nsf/F/TPACGDP_MDP_Calendar_2024-2028_12062024.pdf/$FILE/CGDP_MDP_Calendar_2024-2028_12062024.pdf.</E>
                        </P>
                    </FTNT>
                    <P>We did not receive comments on this section of the proposed rule and are finalizing the amendments to § 423.346(a) as proposed.</P>
                    <HD SOURCE="HD3">3. Payment Appeals</HD>
                    <P>
                        Section 1860D-15(d)(1) of the Act gives the Secretary broad authority to develop payment methodologies for payments described in section 1860D-15 of the Act, and we use this broad authority to establish a payment appeals process. Accordingly, in our final rule, “Medicare Program; Medicare Prescription Drug Benefit,” which appeared in the January 28, 2005 
                        <E T="04">Federal Register</E>
                         (70 FR 4316), we added § 423.350 to establish a payment appeals process for the reconciled health status risk adjustment of the direct subsidy as provided in § 423.343(b); the reconciled reinsurance payments under § 423.343(c); the 
                        <PRTPAGE P="17431"/>
                        reconciled final payments made for low-income cost sharing subsidies provided in § 423.343(d); and the final risk-sharing payments made under § 423.336. In our final rule, “Medicare Program; Contract Year 2016 Policy and Technical Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Programs,” which appeared in the February 12, 2015 
                        <E T="04">Federal Register</E>
                         (80 FR 7938), we added the reconciled Coverage Gap Discount Program payment to the list of payment determinations that could be appealed under § 423.350.
                    </P>
                    <P>
                        We proposed to amend § 423.350(a)(1) to add the following payment determinations that would be subject to appeal under § 423.350—the reconciled IRASA payment for contract year 2023, reconciled Manufacturer Discount Program payment, and reconciled selected drug subsidy payment. We note that the IRASA reconciliation payment for contract year 2023 has already been made to Part D sponsors. In subregulatory guidance, we explained that the Part D sponsors could appeal the IRASA reconciliation payment determination.
                        <SU>30</SU>
                        <FTREF/>
                         We proposed to include the IRASA reconciliation payment determination in the appeals provision for consistency with the proposed updates to § 423.346, under which we would be able to reopen the IRASA reconciliation payment determination. Indeed, we anticipate that we would reopen the IRASA reconciliation during the global reopening of the contract year 2023 Part D payment reconciliation. Under our proposal, the reopened IRASA reconciliation payment determination would be appealable under § 423.350.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             HPMS memorandum, Completion of the 2023 Final Part D Payment Reconciliation and the 2023 Inflation Reduction Act Subsidy Amount (IRASA) Reconciliation, September 27, 2024 (available at 
                            <E T="03">https://www.cms.gov/about-cms/information-systems/hpms/hpms-memos-archive-weekly/hpms-memos-wk-4-september-23-27</E>
                            ).
                        </P>
                    </FTNT>
                    <P>The Part D payment appeals process only applies to perceived errors in the application of our payment methodology. The payment information submitted by the Part D sponsor cannot be appealed through this process. Part D sponsors are expected to submit payment information correctly and within the established timeframes. We codified at § 423.350(a)(2) that payment information submitted to us under § 423.322 and reconciled under the various payment provisions is final and may not be appealed nor may the appeals process be used to submit new information after the submission of information necessary to determine retroactive adjustments and reconciliations. We proposed to amend the regulation at § 423.350(a)(2) to add language specifying that information that is submitted and reconciled or used in the payment calculations for the Manufacturer Discount Program reconciliation, the selected drug subsidy reconciliation, and the IRASA reconciliation are final and would not be appealable nor would the appeals process be used to submit new information after the submission of information necessary to determine these retroactive adjustments and reconciliations.</P>
                    <P>We also proposed to amend § 423.350(a)(2) to add a reference to § 423.336, which describes the risk corridor payment, to correct an inadvertent omission. The information that is submitted and used in the payment calculations under § 423.336 is final and would not be appealable nor would the appeals process be used to submit new information after the submission of information necessary to determine that payment determination.</P>
                    <P>We did not receive comments on this section of the proposed rule and are finalizing the amendments to Payment appeals at § 423.350(a)(1) and (a)(2) as proposed.</P>
                    <HD SOURCE="HD3">4. Payment Appeals—Time for Filing</HD>
                    <P>Under existing § 423.350(b)(1), the payment appeal (specifically, the request for reconsideration of the payment determination) must be filed within 15 days from the date of the final payment. We proposed two amendments to § 423.350(b)(1) to reflect actual practice. First, we proposed to amend 15 days to 15 calendar days. Second, we proposed that the appeal deadline would be based on the release of the reconciliation reports to the Part D sponsors, as opposed to the date of the final payment. The reconciliation reports that CMS releases to the Part D sponsors are detailed reports that specify the inputs and results of the payment reconciliation at the plan-level. These detailed reports allow plans to understand how their Part D payment reconciliation was calculated by us. Part D sponsors currently appeal their payment determinations based on information in the reconciliation reports. Therefore, we proposed to update that the time for filing an appeal would be within 15 calendar days from the date we issue the payment reconciliation report for the payment determination that is being appealed by the Part D sponsor.</P>
                    <P>We did not receive comments on this section of the proposed rule and are finalizing the amendments to payment appeals at § 423.350(b)(1) as proposed.</P>
                    <P>The provisions described in this section of the final rule are consistent with our current guidance and requirements. The changes are updates that do not place additional requirements on Part D sponsors, nor do they place any additional burden on the Part D sponsors or their pharmacy benefit managers (PBMs).</P>
                    <P>Part D sponsors' compliance with this reopening process is evidenced by each Part D sponsor's signed attestation certifying the cost data (under § 423.505(k)(3) and (5)) that we use in each of the reopenings. In addition, the burden associated with the submission of cost data is already approved under the OMB control numbers 0938-0982 (CMS-10174) and 0938-0964 (CMS-10141).</P>
                    <P>We believe that the payment appeals process at § 423.350 is an administrative action or investigation with respect to a specific party, which is exempt from the COI process. Therefore, as our changes do not result in additional burden, we have not included a discussion of this provision in the COI section of this rule.</P>
                    <P>We are not scoring this provision in the Regulatory Impact Analysis section because industry is already complying with this process.</P>
                    <P>We did not receive comments on this proposal and are finalizing this provision without modification.</P>
                    <HD SOURCE="HD1">III. Enhancements to the Medicare Advantage and Medicare Prescription Drug Benefit Programs</HD>
                    <HD SOURCE="HD2">A. Revise List of Non-Allowable Special Supplemental Benefits for the Chronically Ill (SSBCI) (§ 422.102)</HD>
                    <P>
                        The “Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly Final Rule” appeared in the April 15, 2025, 
                        <E T="04">Federal Register</E>
                         (90 FR 15792), hereafter referred to as the April 2025 final rule. In this rule, CMS codified new regulation language at 42 CFR 422.102(f)(1)(iii)(G) that cannabis products are not allowable Special Supplemental Benefits for the Chronically Ill (SSBCI), as they are illegal substances under federal law.
                    </P>
                    <P>
                        Section 10113 of the Agriculture Improvement Act of 2018, also known as the 2018 Farm Bill (Pub. L. 115-334 
                        <SU>31</SU>
                        <FTREF/>
                        ), added a definition of “hemp” to the Agricultural Marketing Act of 1946. Under this definition, “[t]he term 
                        <PRTPAGE P="17432"/>
                        `hemp' means the plant Cannabis sativa L. and any part of that plant, including the seeds thereof and all derivatives, extracts, cannabinoids, isomers, acids, salts, and salts of isomers, whether growing or not, with a delta-9 tetrahydrocannabinol (THC) concentration of not more than 0.3 percent on a dry weight basis.” In addition, section 12619 of the 2018 Farm Bill amended the Controlled Substances Act (CSA) to exclude hemp from the CSA's definition of marijuana.
                        <SU>32</SU>
                        <FTREF/>
                         The Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026, amended the definition of hemp to exclude any cannabinoids that are not naturally found or produced in the cannabis plant, cannabinoids that are synthesized outside of the plant, and final form products for human use that contain more than 0.4 milligrams per container combined total of naturally occurring tetrahydrocannabinols and other naturally produced cannabinoids determined by the Secretary of Health and Human Services to have the same effect. This amended definition of hemp takes effect on November 12th, 2026. Consequently, hemp and hemp-derived cannabis products that meet the current 2018 definition are not federally controlled substances through November 11th, 2026, and those that meet the amended definition beginning on November 12th, 2026, will remain not federally controlled substances as of that date under current law as of the time of this rulemaking. If such products comply with all other applicable federal laws, including any future changes to the definition of hemp and applicable provisions of the Federal Food, Drug, and Cosmetic Act (FFDCA), then they are not illegal under federal law. To reflect this distinction, CMS proposed amending § 422.102(f)(1)(iii)(G) to state more precisely that cannabis products that are illegal under applicable State or Federal law, including the FFDCA, are not allowable as SSBCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             Agriculture Improvement Act of 2018, H.R.2, 115th Congress (2018). 
                            <E T="03">https://www.congress.gov/bill/115th-congress/house-bill/2.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             Defining Hemp: A Fact Sheet. 
                            <E T="03">https://www.congress.gov/crs-product/R44742#:~:text=The%202018%20farm%20bill%20further,regulations%2C%20and%20applicable%20state%20regulations.</E>
                        </P>
                    </FTNT>
                    <P>
                        In December 2018, FDA completed its evaluation of three generally recognized as safe (GRAS) notices for the following hemp seed-derived food ingredients: hulled hemp seed, hemp seed protein powder, and hemp seed oil.
                        <SU>33</SU>
                        <FTREF/>
                         FDA had no questions at that time about the notifier's conclusion that the ingredients were GRAS for their intended use in food. An ingredient that meets the GRAS standard can be used in food without being required to undergo premarket review and approval by FDA for that intended use.
                        <SU>34</SU>
                        <FTREF/>
                         CMS also noted in the Contract Year 2027 proposed rule 
                        <SU>35</SU>
                        <FTREF/>
                         (90 FR 54940) that while the prescription drug Epidiolex meets the definition of hemp under the 2018 Farm Bill, because it is covered under Medicare Part D, it would not be permitted to be offered as a Part C supplemental benefit.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             
                            <E T="03">https://www.fda.gov/food/hfp-constituent-updates/fda-responds-three-gras-notices-hemp-seed-derived-ingredients-use-human-food.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             
                            <E T="03">https://www.fda.gov/food/food-ingredients-packaging/generally-recognized-safe-gras.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             Medicare Program; Contract Year 2027 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program (90 FR 54894).
                        </P>
                    </FTNT>
                    <P>
                        Therefore, this regulation will allow MA organizations to offer hulled hemp seed, hemp seed protein powder, and hemp seed oil, consistent with FDA's review of the GRAS notices, as SSBCI to qualifying enrollees, to the extent otherwise appropriate as SSBCI and under federal and applicable state law. Additionally, at the time of this rulemaking, any cannabis product with a delta-9 THC content above the 0.3 percent threshold is still considered marijuana, remains a Schedule I controlled substance, and therefore is illegal under federal law and would be subject to CMS's prohibition. Barring subsequent legal changes, any product that does not comply with the amended definition of hemp after the November 12th, 2026 effective date will be a Schedule I controlled substance and therefore will be illegal under federal law 
                        <SU>36</SU>
                        <FTREF/>
                         and subject to CMS's prohibition.
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             Under the Controlled Substances Act, Schedule I controlled substances may only be used for research purposes by practitioners who are registered with DEA to conduct such research. 21 U.S.C. 822(b), 823(g)(2).
                        </P>
                    </FTNT>
                    <P>
                        Section 1852(a)(3)(D)(ii)(I) of the Act requires that an item or service offered as an SSBCI must have a reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollee. There may be situations in which foods containing one or more of these three specific ingredients meet the “reasonable expectation of improving or maintaining the health or overall function” standard for SSBCI. For example, there is evidence that hemp seed protein powder may offer nutritional benefits.
                        <SU>37</SU>
                        <FTREF/>
                         CMS reminds MA organizations about the importance of ensuring that the items and services provided to enrollees, including any foods containing these specific hemp-derived ingredients, meet the requirements for being offered as an SSBCI. CMS notes that should MA organizations choose to offer any of these three hemp-derived ingredients, they would be subject to all applicable SSBCI requirements under § 422.102(f), including the bibliography requirements for SSBCI items and services set forth at § 422.102(f)(3) to demonstrate through relevant acceptable evidence that the item has a reasonable expectation of improving or maintaining the health or overall function of a chronically ill enrollee.
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             
                            <E T="03">https://www.sciencedirect.com/science/article/pii/S221345302200235X.</E>
                        </P>
                    </FTNT>
                    <P>The amended language also clarifies that MA organizations remain prohibited from covering any cannabis product, including any hemp-derived cannabis product, that is illegal under state law within their service area regardless of the product's federal legal status.</P>
                    <P>CMS solicited comment on the proposed amendments and thanks commenters for their input. In the following section, CMS describes the comments received and CMS's corresponding responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed support for the proposal.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this support of the proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters found the proposal to be overly restrictive. Several commenters urged CMS to allow plans to cover all hemp-derived THC or CBD products that meet federal hemp standards under the 2018 Farm Bill (0.3 percent delta-9 THC dry-weight threshold), while others expressed concern that overly restrictive THC limits would eliminate full-spectrum products. Commenters also requested CMS distinguish between non-psychoactive industrial hemp grain products and hemp-derived cannabinoid products, noting that the proposed 0.4 mg per-container THC threshold was operationally unworkable for bulk agricultural commodities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' feedback and would like to take this opportunity to provide additional clarification regarding certain aspects of the proposal, including CMS's role in the regulation of cannabis-derived products. CMS's authority does not extend to the direct regulation of cannabis-derived products. Moreover, given the regulation of cannabis-derived products is relatively nascent at both the federal and state levels, CMS does not address the specific technical applications of such laws directly in the regulation text to provide maximum flexibility for MA plans to be able to adapt their SSBCI offerings as the legal landscape changes.
                        <PRTPAGE P="17433"/>
                    </P>
                    <P>As outlined in the Contract Year 2027 proposed rule and this final rule, current regulations prohibit all cannabis products from being offered as SSBCI. Here, CMS acknowledges that not all cannabis products are illegal under federal law and is amending the regulation to accurately reflect this distinction. At the time of this rulemaking, there are only three products that are permissible under applicable state and federal law and therefore may be covered as SSBCI. Those products are hulled hemp seed, hemp seed protein powder, and hemp seed oil. However, should additional products become allowable as the law continues to evolve, this regulation would allow MA plans in a subsequent plan year the option to increase their offerings without requiring additional rulemaking from CMS. Therefore, should other cannabis-derived products become allowable as SSBCI due to changes in state or federal law, MA plans must wait until their next bid submission for the following plan year to add these items to their list of covered SSBCI.</P>
                    <P>CMS notes that the reference to the FFDCA in the text of the regulation is not necessary because the regulation's reference to current applicable federal law includes the FFDCA. Therefore, CMS is finalizing the regulation with a modification to read as follows, “Cannabis products that are illegal under applicable State or Federal law.”</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters emphasized the therapeutic benefits of hemp-derived CBD and other cannabinoid products for various medical conditions including chronic pain, cancer, and dementia. Some commenters argued that further investment in cannabinoid products could improve health outcomes and reduce healthcare costs. Others indicated a need for further research.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these recommendations, however given that CMS does not regulate cannabis and hemp-derived cannabis products, many of these comments were outside the scope of this proposal. CMS would like to note that while the current list of products that are available to be offered as SSBCI is limited, should additional products become allowable in the future CMS will accept a variety of evidence from MA plans to meet the bibliography requirement set forth at 42 CFR 422.102(f)(3), including randomized control trials, case studies or internal analyses to demonstrate that the proposed benefits meet the “reasonable expectation” that the benefit improves or maintains the overall health or function of the enrollee. CMS encourages MA plans that wish to offer these products as SSBCI to monitor emerging studies regarding the efficacy of these products.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS conduct a cost-benefit analysis of hemp coverage, specifically examining potential Medicare savings from reduced hospitalizations and emergency room visits if hemp were covered by MA plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their input, however this comment is outside the scope of this proposal. The amendment to the regulation text is meant to ensure conformity with federal and state law. CMS did not propose to evaluate the clinical benefit or cost of hemp coverage in MA but will consider it as laws evolve.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter recommended that CMS clarify how its proposals regarding treatment of cannabis and hemp products as SSBCI would apply if the Administration finalizes policies to reschedule marijuana from Schedule I to Schedule III of the Controlled Substances Act.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment and the opportunity to clarify, especially in light of Executive Order (E.O.) 14370, “Increasing Medical Marijuana and Cannabidiol Research,” which was issued on December 18, 2025. The E.O. directs the Attorney General to expedite the rulemaking process to reschedule marijuana from Schedule I to Schedule III under the Controlled Substances Act, among other things. Should cannabis be rescheduled to Schedule III, this would change its status under the Controlled Substance Act. However, rescheduling alone would not automatically make cannabis products allowable SSBCI unless the relevant products also meet other applicable State and Federal laws, including the FFDCA.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter noted that in light of possible changes to acceptable SSBCI benefits, CMS should have a clear process and timeline to solicit feedback and receive public input on permissible SSBCI and ensure that plans have sufficient time to analyze this information for their advanced planning for annual submissions of bid and benefit packages.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment, and as CMS did here, any changes to SSBCI requirements will be made by requesting public comment on a proposed regulation through a Notice of Proposed Rulemaking (NPRM). However, CMS regulations do not include an exhaustive list of every qualifying item or service that meets the requirements for CMS approval as SSBCI. CMS will ensure that updates to bid instructions and other relevant sub-regulatory guidance are timely and provide sufficient advance notice to MA plans. As a reminder, CMS releases guidance every spring regarding standards for bid review and evaluation prior to the bid submission. In these memos and other guidance, CMS includes references to resource mailboxes for MA benefit questions and MA policy questions. These mailboxes are open year-round for plans and other stakeholders to submit questions, including questions regarding supplemental benefits. MA organizations that are looking to cover new or novel benefits are strongly encouraged to raise those to CMS well in advance of bid submission to allow ample time for the MA organization to provide, and for CMS to review, information explaining how the applicable statutory and regulatory standards are met for the proposed benefits without the time pressures of the bid review process. This is especially true regarding cannabis and cannabidiol products, as the legal landscape continues to quickly evolve.
                    </P>
                    <P>CMS notes that MA plans are prohibited from making mid-year benefit changes pursuant to 42 CFR 422.254(a)(5), which prohibits MA plans from changing benefits, cost-sharing and premiums for an MA plan after they begin marketing for the prospective plan year. Therefore, should other cannabis-derived products become allowable as SSBCI due to changes in state or federal law, MA plans must wait to add these items to their list of covered SSBCI in their next bid submission for the following plan year.</P>
                    <P>CMS appreciates commenters' input in this area and is finalizing the proposed amendment to regulation text with a modification. CMS is finalizing that 42 CFR 422.102(f)(1)(iii)(G) be amended as follows: “Cannabis products that are illegal under applicable State or Federal law.”</P>
                    <HD SOURCE="HD2">A. Coordination of Election Mechanisms for MA and Part D (§§ 422.62, 422.66, 423.32, 423.36, and 423.38)</HD>
                    <P>
                        Section 1851(c) of the Act provides the Secretary with the authority to establish a process by which MA enrollment elections (hereinafter referred to as “elections”) are made and changed, including the form and manner in which they are changed. Section 1851(e)(4)(D) of the Act provides the Secretary with the authority to establish Special Election Periods for exceptional conditions, during which individuals may make 
                        <PRTPAGE P="17434"/>
                        elections. Section 1860D-1(b)(1)(B) of the Act directs the Secretary to use rules related to enrollment, disenrollment, termination, and change of enrollment for Part D sponsors that are similar to those established for MA plans under specified subsections of section 1851 of the Act. Section 1860D-1(b)(1)(B)(ii) of the Act specifies that the Secretary shall use section 1851(c) of the Act, other than paragraph (3)(A) and paragraph (4) of such section, for Part D rules relating to exercise of choice.
                    </P>
                    <P>Consistent with these sections of the Act, in 1998, we published a final rule (63 FR 34968) to codify the Part C election process required under section 1851(c) of the Act at § 422.66. In 2005, we published a final rule (70 FR 4194) to codify the Part D election process required under section 1860D-1(b)(1)(B) of the Act at §§ 423.32 and 423.36. The Parts C and D subpart B regulations set forth our requirements with respect to the election process under §§ 422.60 (election process), 422.66 (coordination of enrollment and disenrollment through MA organizations), 423.32 (enrollment process), and 423.36 (disenrollment process).</P>
                    <P>MA election requests, with few exceptions, are submitted by the individual requesting enrollment in or disenrollment from a particular MA plan. In certain circumstances, namely passive enrollment (a process where CMS initiates enrollment into another plan in cases of immediate plan terminations, harm to beneficiaries, or for the promotion of integrated care with state Medicaid agency approval) and default enrollment (a process available only for integrated D-SNP enrollments), CMS directly enrolls individuals and transmits an enrollment transaction to the plan, which bypasses the usual process discussed later in this section.</P>
                    <P>Current Part C regulations at § 422.60(e) specify that MA organizations must have effective systems for receiving, controlling, and processing election requests. After satisfying those requirements and accepting an individual's election request, the MA organization transmits the information necessary for CMS to add the individual to its records as an enrollee of the MA organization. Current Part C regulations at §§ 422.66(a) and (b) specify that elections may be made by filing appropriate election forms with the MA organization or through other mechanisms as determined by CMS. The same process is mirrored in current Part D regulations at §§ 423.32(a) through (d) and 423.36(a) and (b), whereby the Part D sponsor receives an election request from an individual and then submits necessary information to CMS.</P>
                    <P>Outside of circumstances where CMS directly enrolls an individual into a plan (passive, default enrollment, etc.) most election requests are filed with the MA organization or Part D sponsor, though the election form or mechanism may differ. Election mechanisms are how an individual communicates their election request to the MA organization or Part D sponsor, whether on paper, over the phone, electronically, etc. Even if an individual uses a CMS-operated election mechanism (1-800-MEDICARE or the Online Enrollment Center), the election request is still filed with the plan for processing.</P>
                    <P>
                        Historically, CMS has regulated the required content of election mechanisms under the “form and manner” authority specified at section 1851(c)(1) of the Act and codified at §§ 422.60(c), 422.66(a), 423.32(a), and 423.36(a). Consistent with section 1851(e)(4) of the Act, CMS has required CMS approval for certain election periods. For example, consistent with the provisions in section 1851(e)(4)(C) providing that a SEP may be available where an “individual demonstrates (in accordance with guidelines established by the Secretary) that . . . the organization offering the plan substantially violated a material provision of the organization's contract under this part in relation to the individual . . . ,” CMS's current regulations governing the special enrollment period (SEP) for contract violation (§§ 422.62(b)(3) and 423.38(c)(8)) provide that the SEP is available where an individual demonstrates to CMS that specified criteria have been met. This SEP is only available once CMS determines that a contract violation has occurred. An individual alleging a contract violation must call 1-800-MEDICARE to explain their circumstances and demonstrate to CMS that there was a violation. Once eligibility is demonstrated, the individual can elect a new plan or disenroll from their current plan and the election request is subsequently transmitted to the plan to process. The requirement that the individual demonstrate eligibility to CMS has been in place since the SEP was first codified in a 1998 final rule (63 FR 34968, 34980) and the process to demonstrate eligibility to CMS is also described in section 30.6.28 of the Medicare Advantage and Part D Enrollment and Disenrollment Guidance, 
                        <E T="03">see also</E>
                         MA-PD Plan Communications User Guide, pg. 3-38.
                    </P>
                    <P>There are other SEPs that are currently only available with prior CMS approval, provided by CMS sending a notice or election request to the MA organization or Part D sponsor. These SEPs are: SEP for individuals who disenroll in connection with CMS sanction (§§ 422.62(b)(5) and 423.38(c)(12)); SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage (§§ 422.62(b)(20) and 423.38(c)(2)); and SEP for other exceptional circumstances (§§ 422.62(b)(27) and 423.38(c)(36)). As described in CMS's Medicare Advantage and Part D Enrollment and Disenrollment Guidance, Section 30.6, in order for CMS to review that appropriate circumstances apply to allow for an SEP based on a CMS sanction, an individual not receiving adequate information about loss of creditable prescription drug coverage, or other exceptional circumstances, plans must have prior approval from CMS to submit enrollment transactions based on these SEPs.</P>
                    <P>We proposed to codify our current policy that for elections that are made based on certain special election periods, the beneficiary at issue must either have CMS approval for the use of that SEP through the use of a CMS-operated election mechanism (for example, 1-800-MEDICARE or the Online Enrollment Center (OEC)) or other means, such as enrollee receipt of a notice. We proposed this change to codify longstanding guidance and practice requiring CMS approval for certain SEPs. This policy allows for control over election periods and mechanisms to ensure appropriate use and allows us to delineate a clear process for each election. To accomplish this, we proposed to establish at §§ 422.66(g), 423.32(k), and 423.36(g) the requirement that elections may require CMS approval based on the use of specified SEPs. CMS approval would be provided for plan elections either through the use of a CMS-operated election mechanism or through the individual's receipt of a notice which explains eligibility for the SEP and election instructions. As CMS approval would be an eligibility criterion of the SEP, MA organizations and Part D plan sponsors may not transmit elections to CMS using the specified SEPs without prior CMS approval. We proposed to codify these limitations for the following SEPs:</P>
                    <P>• SEP for individuals who disenroll in connection with CMS sanction (§§ 422.62(b)(5) and 423.38(c)(12));</P>
                    <P>
                        • SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage (§§ 422.62(b)(20) and 423.38(c)(2));
                        <PRTPAGE P="17435"/>
                    </P>
                    <P>• SEP for contract violation (§§ 422.62(b)(3) and 423.38(c)(8));</P>
                    <P>• SEP for other exceptional circumstances (§§ 422.62(b)(27) and 423.38(c)(36)).</P>
                    <P>These limitations were proposed to be codified at §§ 422.62(b)(3), (b)(5), (b)(20), (b)(23), (b)(27), and 423.38(c)(2), (c)(8), (c)(12), and (c)(36). Language was added to each SEP we proposed to limit to require CMS approval. The language indicates that CMS approval is required and references how CMS approval will be indicated, either through providing a notice or the acceptance of an election through a CMS-operated mechanism. These limitations and applicable SEPs are also described at §§ 422.66(g)(2), 423.32(k)(2), and 423.36(g)(2).</P>
                    <P>We proposed to codify these limitations in order to better oversee the use of SEPs which may not be appropriate for plans to use without prior CMS eligibility determination and approval. It would, for example, be inappropriate for an organization to evaluate the claim that another organization violated their contract with an individual, or that the individual was impacted by conduct that was sanctioned by CMS. In those cases, other organizations are not neutral arbiters of eligibility as they have a financial interest in deeming the conduct of other organizations as a contract violation or they lack the complete information about the circumstances of the sanctioned conduct. The SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage is similarly justified as requiring CMS approval prior to the election request being filed with the plan for processing. The eligibility determination for this SEP also requires evaluation of the conduct of another organization or entity and whether they provided adequate notice of the loss of creditable coverage. We believe these SEP limitations would prevent organizations, who do not have appropriate context, from incorrectly determining eligibility. This is especially true for the SEP for other exceptional circumstances, which covers situations not otherwise captured in the SEPs in regulation. This SEP is determined on a case-by-case basis for circumstances that warrant an enrollment opportunity given the exceptional conditions experienced by the individual. In these types of cases, only CMS can appropriately consider the circumstances of an individual's eligibility.</P>
                    <P>In order to best facilitate CMS approval prior to the election request being filed with the plan, these SEPs should only be available through a CMS-operated mechanism, to allow the approval for the SEP to be sent to the plan along with the election request for processing. The requirement for certain SEPs to be approved by CMS first, before the election is filed with the plan, does not preclude the involvement of an agent or broker assisting the enrollee. The enrollee can meet with an agent/broker for assistance in selecting the best plan for the enrollee. The enrollee can then use the CMS mechanism, for example, call 1-800-MEDICARE on their own or with the assistance of the agent/broker. 1-800-MEDICARE and the OEC are capable of capturing the involvement of the agent/broker and transmitting that information to the newly selected plan when CMS sends the approved election request.</P>
                    <P>As the pre-existing limitations have been long-standing, previously implemented and are currently being followed by plan sponsors, in the Contract Year 2027 proposed rule, we concluded that the changes to the regulatory text would not adversely impact plan sponsors, individuals, or agents/brokers, nor would the changes have any impact on the Medicare Trust Funds or result in a paperwork burden. We also stated that all information impacts related to the procedural steps plans must take to receive and process election requests have already been accounted for under OMB control numbers 0938-0753 (CMS-R-267) for Part C and 0938-0964 (CMS-10141) for Part D.</P>
                    <P>CMS solicited comments on this proposal as well as comments on how these SEPs can be further improved for beneficiaries. The following is a summary of the comments we received and our responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed support for the proposal to codify limits to certain SEPs that would require prior CMS approval, via receipt of a notice or election through a CMS-operated mechanism.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed this proposal and recommended CMS allow agents and brokers to assist individuals to enroll directly with a new election mechanism instead of limiting elections to existing CMS-operated mechanisms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestion to create a new election mechanism that would allow agents and brokers to assist individuals more directly. However, we disagree that a new mechanism is necessary to maintain the ability for agents and brokers to assist individuals. As we stated in the proposal, agents and brokers are still able to assist individuals making elections using these SEPs and have their involvement captured by 1-800-MEDICARE and the OEC by providing their National Producer Number, which is transmitted to the plan along with the enrollment request. We believe that the existing process allows agents and brokers to actively guide individuals with their plan options and during their election request and results in no additional burden to the plan.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed this proposal and stated that these SEPs are not used regularly but broadening the SEPs could lead to more churn. The commenter also suggested that educational materials on these SEPs be updated and designed with the reader's health literacy level in mind.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their suggestion to improve educational materials and will bear in mind the readability of materials when updating guidance and education materials regarding codification of this proposal. We disagree with the commenter's statement that these SEPs are being broadened by the proposed changes and could lead to enrollment churn. This proposal codifies existing restrictions on these SEPs, which puts guardrails on them, and does not broaden their availability. Therefore, codifying these requirements is likely to result in no change or reduce enrollment churn.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed the inclusion of the SEP for other exceptional circumstances in this proposal. The commenter stated that requiring CMS approval would place an undue burden on beneficiaries wishing to make an election, particularly for individuals looking to enroll in a C-SNP.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for this perspective on how the SEP for other exceptional circumstances might be used by individuals wishing to enroll in a C-SNP. However, we disagree with the suggestion that the SEP for other exceptional circumstances not be limited to situations in which CMS approval is provided via notice or use of a CMS-operated election mechanism. As stated previously, we proposed to codify these limitations in order to better oversee the use of SEPs that may not be appropriate for plans to use without prior CMS eligibility determination and approval. This is especially true for the SEP for other exceptional circumstances, which covers situations not otherwise captured in the SEPs in regulation and is determined on a case-by-case basis. We believe that CMS is the only party that 
                        <PRTPAGE P="17436"/>
                        can reasonably make these SEP determinations. We remind the commenter that this limitation does not apply to an SEP that is relevant to enrollment in a C-SNP, the SEP for individuals who are eligible or are found ineligible to enroll in a C-SNP (§ 422.62(b)(13)), which is designed to allow for an enrollment in a C-SNP that serves individuals with specific severe or disabling chronic conditions.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed this proposal and stated that the change would have significant operational impacts on plans. Additionally, the comment stated that beneficiaries may not understand the enrollment process through CMS-operated mechanisms, which may delay enrollments and result in continuity of care issues. The commenter stated that plans would need to implement systems changes to validate these SEPs, update workflows, and train staff and agents to prevent enrollment errors.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's perspective on potential impacts of this proposal. However, we disagree that this change would result in additional burden. As stated previously, the limitation on these SEPs is already implemented and long-standing. Additionally, the procedural steps plans must take to receive and process election requests and its impacts have already been accounted for in existing burden calculations and plans should not need to make procedural changes in response to this proposal if they are currently following long-standing enrollment guidance.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter in support of this proposal also suggested that CMS similarly limit the SEP for individuals affected by a government-entity declared disaster or other emergency to only CMS-operated election mechanisms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their support and their suggestion. We will consider limiting the SEP for individuals affected by a government-entity declared disaster or other emergency to only CMS-operated election mechanisms in future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters in support of this proposal requested clarification on whether individuals will be expected to provide a copy of a notice of SEP eligibility or otherwise provide documentation to prove their eligibility for these SEPs. The commenters also recommended that the availability of State Health Insurance Assistance Programs (SHIPs) should be promoted whenever individuals need assistance with the SEPs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their requests for clarification and recommendations. Individuals will not be expected to provide a copy of a notice of SEP eligibility when enrolling through a CMS-operated mechanism, or other mechanism when allowed. Currently, only the SEP for individuals who disenroll in connection with CMS sanction requires receipt of a notice for SEP eligibility, in which case they will not be expected to provide the notice or other documentation to establish eligibility, they must only attest that they received the notice about SEP eligibility; the other SEPs are approved through the use of a CMS-operated mechanism, eligibility in these cases is established through attestations made to CMS during the election, such as verbal attestations of the conditions of eligibility made to a 1-800-MEDICARE customer service representative. We will consider the commenters' suggestions about referring individuals to SHIPs when developing guidance and educational materials for these SEPs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter in support of this proposal recommended that CMS improve existing guidance and educational materials on these SEPs and mention the availability of agent/broker assistance.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their support and recommendations. We will update our guidance and educational materials to reflect the codification of this proposal and explain the availability of agent/broker assistance where appropriate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asked for clarification on whether current regulations allow CMS to create SEPs in response to plans providing false information related to provider networks.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is outside of the scope of the final rule as this proposal did not discuss creating new SEPs.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing this proposal without modification.</P>
                    <HD SOURCE="HD2">B. Use and Release of Risk Adjustment Data</HD>
                    <P>Section 1853(a) of the Act requires CMS to risk adjust payments made to Medicare Advantage (MA) organizations. In order to carry out risk adjustment, section 1853(a)(3)(B) of the Act requires MA organizations to submit data regarding inpatient hospital services and data regarding other services and other information the Secretary deems necessary. Risk adjustment data are the data submitted to CMS by MA organizations to carry out risk adjustment, including the development and application of a risk adjustment payment model. Regulations at 42 CFR 422.310 establish requirements regarding the collection and submission of risk adjustment data, as well as the allowable uses of risk adjustment data and conditions under which the data can be released.</P>
                    <P>The MA program now comprises more than 50 percent of the Medicare population, and there has been a coinciding increase in the number and variety of requests that CMS receives for risk adjustment data. This increase is due to both the utility of the more detailed risk adjustment data that CMS started collecting in 2012 (that is, encounter data) and growing enrollment in MA. With the increased variety of requests for risk adjustment data and CMS's better understanding of the data requests received, CMS has come to recognize that the limits on the use and release of risk adjustment data imposed by § 422.310(f) may be unnecessary, burdensome, and overly restrictive for CMS, and for private and public stakeholders requesting the data. The existing restrictions may limit innovative uses of the data by CMS and non-CMS entities that may improve program integrity, increase efficiency, and reduce waste. The changes to the use and release regulations described in section IV.C of the proposed rule would lead to more efficient use of public and private sector resources by removing the existing restrictions on the use and release of risk adjustment data while maintaining the protections in place for beneficiary identifying information through CMS data sharing procedures and for plan-submitted dollar amounts reported for an associated encounter. CMS believes that easing the use and release requirements for risk adjustment data would support the goals of Executive Order 14243 “Stopping Waste, Fraud, and Abuse by Eliminating Information Silos” (March 20, 2025) by reducing barriers to sharing government data across agencies, improve CMS's ability to effectively and efficiently administer and oversee MA and other Federal health care programs, as well as encourage research into improving health care delivery.</P>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>
                        Section 1853(a) of the Act requires the Secretary to make monthly payments to MA organizations for each beneficiary enrolled in an MA plan. Section 1853(a)(1)(C) of the Act requires the Secretary to adjust the monthly payments based on risk factors of a plan's enrolled beneficiaries, such as demographic factors and other factors 
                        <PRTPAGE P="17437"/>
                        that the Secretary determines are appropriate, including health status. To support risk adjustment, section 1853(a)(3)(B) of the Act requires MA organizations to submit data regarding the services provided to enrollees and other information the Secretary deems necessary.
                    </P>
                    <P>
                        The requirements for the submission of risk adjustment data by MA organizations are set forth at § 422.310. In accordance with these regulations, MA organizations must submit the data necessary to characterize the context and purposes of each item and service provided to their enrollees by a provider, supplier, physician, or other practitioner in accordance with CMS instruction. Paragraphs (a) through (d) of § 422.310 define risk adjustment data, the basic rules of risk adjustment data collection, the sources and extent of risk adjustment data, and other risk adjustment data requirements. There are two forms of risk adjustment data: (1) data equivalent to Medicare fee-for-service (FFS) data, hereafter referred to as Original Medicare (OM) data, when appropriate, and to all relevant national standards, referred to as encounter data, and (2) data submitted by MA organizations prior to 2022 in an abbreviated format, referred to as Risk Adjustment Processing System (RAPS) data.
                        <SU>38</SU>
                         
                        <SU>39</SU>
                        <FTREF/>
                         Both encounter data and RAPS data submissions include beneficiary diagnoses.
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             Refer to the CSSC Operations website for information about the submission of encounter data and RAPS data.
                        </P>
                        <P>
                            <SU>39</SU>
                             RAPS remains available to MA organizations for the submission of data corrections for years prior to 2022.
                        </P>
                    </FTNT>
                    <P>Though section 1853(a)(3)(B) of the Act does not limit the Secretary's use or disclosure of risk adjustment data, Federal laws, such as the Privacy Act of 1974 (as amended), impose restrictions on the disclosure of data collected by Federal agencies, and section 1106(a) of the Act [42 U.S.C. 1306(a)] generally prohibits the disclosure of any information obtained by HHS except as the Secretary may prescribe by regulations and except as otherwise provided by Federal law. Over time, CMS has regulated the scope of permissible uses and releases of the MA risk adjustment data, including RAPS and encounter data, in order to achieve a balance between protection of beneficiary identifying information and the interests of MA organizations with the need to effectively administer Federal programs and to encourage research into better ways to provide health care. In the final rule establishing the MA program, published in January 2005 (70 FR 4661), CMS adopted regulations at § 422.310(f) such that CMS may use risk adjustment data to determine the risk adjustment factor used to adjust payments, and for unspecified other purposes, with an exception made to limit CMS's use of medical record data collected under § 422.310(e) to validation studies.</P>
                    <P>
                        In April 2008, CMS proposed to amend § 422.310 to provide that CMS will collect data from MA organizations regarding each item and service provided to an MA plan enrollee,
                        <SU>40</SU>
                        <FTREF/>
                         which would allow CMS to include utilization data and other factors in developing CMS-Hierarchical Condition Categories (CMS-HCC) risk adjustment models that reflect patterns of diagnoses and expenditures in the MA program. In response to the April 2008 proposal and CMS's efforts to collect encounter data, some stakeholders raised concerns that the use of risk adjustment data for “other purposes,” as finalized in the January 2005 final rule, was too broad. Some stakeholders also believed that the data collected for risk adjustment, including encounter data, could not be used for purposes other than risk adjustment. CMS disagreed with this assertion. As stated in the August 2008 final rule, “Section 1853(a)(3)(B) of the Act obligates MA organizations to submit inpatient and outpatient encounter data for purposes of use in implementing a risk adjustment methodology. Unlike the case of information collected under section 1860D-15 of the Act, however, which the statute restricts to being used solely for purposes of implementing that section (see section 1860D-15(d)(2)(B) and (f)(2) of the Act), section 1853(a)(3)(B) of the Act does not impose any such restrictions on other legitimate uses of the encounter data collected” (73 FR 48653). While CMS is not subject to specific statutory restrictions on our own use of risk adjustment data, the agency responded to industry concerns by establishing regulatory limits on the agency's use of risk adjustment data. Specifically, in the August 2008 final rule, CMS revised § 422.310(f) to establish the following five specific uses of risk adjustment data: (i) calculating the risk adjustment factors used to adjust payments, (ii) updating risk adjustment models, (iii) calculating Medicare Disproportionate Share Hospital (DSH) percentages, (iv) conducting quality review and improvement activities, and (v) for Medicare coverage purposes (73 FR 48651, 48653-48654).
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             Refer to 
                            <E T="04">Federal Register</E>
                            , 73 FR 23528, section H: 
                            <E T="03">https://www.federalregister.gov/documents/2008/04/30/08-1135/medicare-program-proposed-changes-to-the-hospital-inpatient-prospective-payment-systems-and-fiscal</E>
                            .
                        </P>
                    </FTNT>
                    <P>CMS made further revisions to § 422.310(f) in the August 2014 final rule to strengthen program management and increase transparency in the MA program by adding four more uses of risk adjustment data at § 422.310(f)(1)(vi) through § 422.310(f)(1)(ix) and by adding two subparagraphs § 422.310(f)(2) and § 422.310(f)(3) to address the terms under which risk adjustment data could be released to non-CMS entities (79 FR 50324-50334). Specifically, the four uses added to § 422.310(f)(1) in the August 2014 final rule are: (vi) to conduct evaluations and other analysis to support the Medicare program (including demonstrations) and to support public health initiatives and other health care-related research; (vii) for activities to support the administration of the Medicare program; (viii) for activities conducted to support program integrity; and (ix) for purposes authorized by other applicable laws.</P>
                    <P>The subparagraph CMS added in the August 2014 final rule at § 422.310(f)(2) provided that the agency may release the minimum data it determines is necessary for one of the purposes listed in § 422.310(f)(1) to other HHS agencies, other Federal executive branch agencies, States, and external entities where that disclosure would be in accordance with: (i) applicable Federal laws; (ii) CMS data sharing procedures; (iii) subject to the protection of beneficiary identifier elements and beneficiary confidentiality, (iv) subject to the aggregation of dollar amounts reported for the associated encounter to protect commercially sensitive data; and (v) risk adjustment data other than that described in paragraphs (f)(2)(iii) and (f)(2)(iv) of § 422.310 will be released without the redaction or aggregation described in paragraphs (f)(2)(iii) and (f)(2)(iv), respectively. CMS clarified that an external entity could be an individual, a group, or an organization, and that CMS would not release payment data (that is, dollar amounts) submitted by MA organizations at the level of the encounter as that data might reveal proprietary negotiated payment rates between MA plans and providers (79 FR 50328).</P>
                    <P>
                        The subparagraph CMS added at (f)(3) in the August 2014 final rule stipulates additional conditions related to the timing of release of risk adjustment data in response to comments from some stakeholders that there should be a delay in releasing the data. CMS added subparagraph (f)(3) in response to comments to clarify that CMS did not plan to regularly release risk adjustment 
                        <PRTPAGE P="17438"/>
                        data for a data collection year prior to the completion of the reconciliation period. Risk adjustment reconciliation refers to the period provided to MA organizations to identify and correct errors in data they have submitted for a data collection year to ensure that the risk adjustment data is complete and accurate based on the MA organization's best knowledge, information, and belief. Risk adjustment data are not considered reconciled for a given payment year until after the final risk adjustment data submission deadline, established at § 422.310(g)(2)(ii), which can be no earlier than January 31 of the year following the payment year (for example, January 31, 2025, for payment year 2024). Specifically, § 422.310(f)(3)(i) specifies that risk adjustment data submitted for a given payment year are not available for release by CMS unless the risk adjustment reconciliation has been completed for that payment year except under limited circumstances, such as when CMS determines that releasing risk adjustment data before reconciliation is necessary for emergency preparedness (§ 422.310(f)(3)(ii)) or due to extraordinary circumstances (§ 422.310(f)(3)(iii)) (79 FR 50331).
                    </P>
                    <P>Since the August 2014 final rule was published, CMS has identified additional circumstances that warranted releasing risk adjustment data prior to reconciliation outside of emergency preparedness and extraordinary circumstances. In the final rule issued in November 2023, CMS provided an additional circumstance (§ 422.310(f)(3)(iv)) to allow for releasing aggregate risk adjustment data prior to risk adjustment reconciliation (88 FR 79397-79400). This provision was added to provide MA utilization data measures on the Care Compare website, along with OM utilization data, to support the administration of the Medicare program and to more completely fulfill the public reporting required by section 104 of the Medicare Access and CHIP Reauthorization Act (MACRA) and section 10331 of the Patient Protection and Affordable Care Act of 2010 (Pub. L. 111-148) (Affordable Care Act) and provide beneficiaries with useful and appropriate information when selecting a Medicare provider.</P>
                    <P>The following year, in April 2024, CMS issued a final rule in which CMS revised two of the allowable uses (§ 422.310(f)(1)(vi) and (vii)) to support the administration of the Medicaid program as well as the Medicare program. CMS further allowed for the release of risk adjustment data to State Medicaid agencies before reconciliation for the specific purpose of coordinating care for dually eligible individuals if CMS determined it was necessary and appropriate to support the administration of the Medicare and Medicaid programs (§ 422.310(f)(3)(v)) (89 FR 30536-30541). This expansion of CMS's use of risk adjustment data to support the administration of the Medicaid program is consistent with the goals of better integrating benefits and improving care coordination for dually eligible individuals as established at section 2602 of the Affordable Care Act.</P>
                    <HD SOURCE="HD3">2. Overview of Proposed Regulatory Changes</HD>
                    <P>CMS proposed to increase access to risk adjustment data while reducing regulatory burden and the resources expended by public and private organizations when requesting risk adjustment data by removing the uses enumerated in §  422.310(f)(1). This change would enable CMS to align more closely with standards applicable to OM claims and other MA and Part D data and allow the data to be used for more purposes than are permitted under the existing regulations. CMS receives requests to use risk adjustment data for a broad range of purposes including research, health care operations, and oversight of public benefit programs, and from a broad range of entities including academic institutions, government entities, and oversight bodies. CMS believes the limitations imposed by §  422.310(f)(1) may be excessive and does not think that MA risk adjustment data should have a different or more restrictive standard for use and release than the standard applied to Medicare OM claims. Similarly, the list of external parties to whom the data can be released at §  422.310(f)(2) (“other HHS agencies, other Federal executive branch agencies, States, and external entities”) may unnecessarily limit access to risk adjustment data to some external entities for legitimate uses that are in the public's interest. CMS believes the proposed removal of §  422.310(f)(2), which would eliminate the restriction on which types of entities can access the data, would be in keeping with our approach to make the risk adjustment data more broadly available. CMS also believes that the provisions on the timing of release of risk adjustment data at §  422.310(f)(3) may be overly restrictive, and there should be more flexibility to release data before reconciliation.</P>
                    <P>
                        We emphasize, however, that CMS release of the data would remain contingent on Federal law and CMS data sharing procedures, per the proposal at §  422.310(f). CMS data sharing procedures include an evaluation of requests to ensure that data requests comply with applicable Federal laws, regulations, and CMS data policies. Additionally, as part of the request process, unless the requester is a beneficiary requesting his or her own data, a data sharing agreement is required to be established between CMS and the requesters prior to disclosing the data. Data sharing agreements include, but are not limited to, information exchange agreements (IEA),
                        <SU>41</SU>
                        <FTREF/>
                         memoranda of understanding (MOU), and data use agreements (DUAs),
                        <SU>42</SU>
                        <FTREF/>
                         all of which are agreements that document the terms and conditions under which CMS data may be used to ensure that data requesters adhere to CMS privacy and security requirements and data release policies. Included in the terms and conditions are safeguards to protect beneficiary identifying information and confidentiality. Also, consistent with what we stated in the August 2014 final rule, CMS data sharing agreements have enforcement mechanisms, and data requesters are required to acknowledge these mechanisms. For example, penalties under section 1106(a) of the Act [42 U.S.C. 1306(a)], including possible fines or imprisonment, and criminal penalties under the Privacy Act [5 U.S.C. 552a(i)(3)] may apply, as well as criminal penalties imposed under 18 U.S.C. 641 (79 FR 50333). Requesters of CMS data are responsible for abiding by the law, policies, and restrictions of the data sharing agreements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             Centers for Medicare &amp; Medicaid Services. (n.d). CMS Information Exchange Agreement (IEA). U.S. Department of Health and Human Services. 
                            <E T="03">https://security.cms.gov/learn/cms-information-exchange-agreement-iea.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             Centers for Medicare &amp; Medicaid Services. (n.d.). CMS data: Data disclosures and data use agreements (DUAs). U.S. Department of Health and Human Services. 
                            <E T="03">https://www.cms.gov/data-research/cms-data/data-disclosures-and-data-use-agreements-duas.</E>
                             An example of a research DUA can be found on the ResDAC website at 
                            <E T="03">https://resdac.org/request-form/rif-data-use-agreement.</E>
                        </P>
                    </FTNT>
                    <P>
                        Over time, §  422.310(f) has become increasingly complex and cumbersome to implement as CMS receives more requests and identifies additional reasonable uses that CMS did not anticipate. As described previously, CMS has revised the regulation over the years by adding specific uses or exceptions for release of risk adjustment data as they are identified, which is burdensome, slows progress, and limits opportunities to effectively and efficiently administer, oversee, and improve Federal programs, and to conduct health care research that can 
                        <PRTPAGE P="17439"/>
                        improve health care delivery. As outlined in section IV.C of the proposed rule, we address these concerns by easing restrictions on the use and release of risk adjustment data while maintaining the current protections for plan-submitted payment amounts for an associated encounter that are currently in place. Protections for beneficiary identifying information currently specified in regulation would be maintained through CMS data sharing procedures and other applicable Federal laws as described previously.
                    </P>
                    <P>CMS expects that transparency in the MA program will be improved by removing: (1) the specific uses at §  422.310(f)(1), aside from protections of the plan-submitted payment amounts that currently exist; (2) the restrictive conditions regarding which external government entities the data can be released to at §  422.310(f)(2); and (3) the timing of when the data can be released at §  422.310(f)(3). We believe these revisions will also allow for more streamlined access to information on the Medicare program as MA grows, thereby strengthening program management, continuing to advance program integrity, supporting public health initiatives, and reducing burden through the implementation of practices and processes for the use and release of MA risk adjustment data that align more closely with standards applicable to other Medicare data, such as OM claims. The revisions to §  422.310(f) are consistent with Executive Order 14192 “Unleashing Prosperity through Deregulation” (January 31, 2025) by reducing the burden for CMS and external entities associated with the increasingly complex regulation surrounding the use and release of risk adjustment data and would support the goals of Executive Order 14243 “Stopping Waste, Fraud, and Abuse by Eliminating Information Silos” (March 20, 2025) by reducing barriers to sharing government data across agencies.</P>
                    <HD SOURCE="HD3">3. Broadening of the Use and Release of Risk Adjustment Data</HD>
                    <P>CMS proposed to ease restrictions on the use of risk adjustment data at § 422.310(f)(1) and repeal the limitations surrounding the release of risk adjustment data at § 422.310(f)(2) and (f)(3), other than the protections currently in place for plan-submitted payment amounts, to allow for the use and release of risk adjustment data that is more aligned with the use and release of OM claims and other MA data. The limited uses of risk adjustment data were established when CMS resumed activities to collect encounter data to alleviate concerns from some stakeholders that risk adjustment data would be used in ways that they thought were inappropriate. As stated previously, CMS does not believe the statute restricts our use of risk adjustment data, and over time CMS has identified unanticipated uses and releases of the data that are in the public's interest beyond the nine listed at § 422.310(f)(1). Historically, this has necessitated CMS resources to conduct rulemaking to add to or amend the list, resulting in regulatory burden and increasingly complex requirements. For example, as previously discussed, CMS could not use risk adjustment data to conduct evaluations and other analyses to support the Medicaid program, nor could CMS use the data to support the administration of the Medicaid program, like care coordination, before amending § 422.310(f)(1)(vi) and (vii) in the final rule CMS issued in April 2024 (89 FR 30536 through 30541).</P>
                    <P>Given the growth of MA, risk adjustment data is increasingly important to understanding the Medicare program and health care delivery more broadly. CMS anticipates that the number and variety of requests for risk adjustment data will continue to increase, as will the resources required to enforce the more restrictive requirements and to develop revised regulations when unanticipated yet warranted uses are identified. We believe that removing the specified uses and easing restrictions for data release at § 422.310(f) would provide CMS flexibility to release MA risk adjustment data in a way that more closely aligns with the release of OM claims and other MA data, which is crucial to burden reduction and the ability of CMS and external entities to be innovative in the pursuit of improved health care delivery and program integrity, greater transparency, and reduced fraud, waste, and abuse.</P>
                    <P>
                        Specifically, CMS proposed to revise § 422.310(f) as follows: “Regarding the data described in paragraphs (a) through (d) of this section, CMS may use and release the minimum data it determines is necessary in accordance with CMS data sharing procedures and applicable Federal laws, subject to the aggregation of dollar amounts reported for the associated encounter to protect commercially sensitive data, unless authorized by other applicable laws.” The updates provide for the stipulation that this regulation does not limit CMS disclosure of data as authorized under separate statutory authority.
                        <SU>43</SU>
                        <FTREF/>
                         We proposed to repeal the nine specified uses currently listed in § 422.310(f)(1) that would be encompassed under the revised paragraph (f) text. We also proposed to repeal the release restrictions specified at § 422.310(f)(2) and § 422.310(f)(3), other than the existing restrictions on the release of the minimum data necessary and on the release of dollar amounts at the encounter level, which were moved to § 422.310(f). We noted in the proposed rule, however, that protections to the beneficiary identifying information would be encompassed under the data sharing procedures in the revised paragraph (f) text.
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             For example, 31 U.S.C. 716, 2 U.S.C. 166(d)(1) and 601(d), section 1805 of the Act (42 U.S.C. 1395b-6), section 1128J of the Act (42 U.S.C. 1320a-7k), and section 6(a) of the Inspector General Act of 1978 (5 U.S.C. 406).
                        </P>
                    </FTNT>
                    <P>Though CMS proposed to repeal the regulatory language at § 422.310(f)(2) that stipulates protections for beneficiary confidentiality, the protections of beneficiary identifying information currently specified at § 422.310(f)(2) would remain in place in accordance with applicable Federal laws, such as the Privacy Act, section 1106(a) of the Act, and CMS information disclosure regulations at 42 CFR part 401, subpart B, that continue to govern this data sharing. CMS would be able to release an individual's risk adjustment data when authorized by that individual and, for other kinds of requests for release of risk adjustment data, CMS would release such information in accordance with CMS data sharing procedures, consistent with current practice. We intend to continue to protect beneficiary data through, for example, encryption, or removal of the confidential fields when risk adjustment data is released. CMS has an established process to evaluate requests for data and enters into data sharing agreements with data requesters for disclosures of risk adjustment data to ensure that data requesters adhere to CMS privacy and security requirements and data release policies. We believe this process contains the necessary checks and safeguards to ensure that the risks of disclosure of beneficiary identifying information are minimal.</P>
                    <P>
                        In the Contract Year 2027 proposed rule, CMS discussed maintaining the protections that currently exist regarding the release of plan-submitted dollar amounts associated with the items or services submitted to CMS pursuant to § 422.310(b) that characterize the context and purposes of each item and service provided to a Medicare enrollee by a provider, supplier, physician, or other practitioner. In the August 2014 final rule (79 FR 49854), we stated our belief 
                        <PRTPAGE P="17440"/>
                        that release of payment data at the level of the encounter record might reveal proprietary negotiated payment rates between MA plans and providers and, therefore, we restricted the release of payment data by only allowing for its release if aggregated. In the Contract Year 2027 proposed rule, CMS stated it was maintaining the guardrails for payment data (dollar amounts) at the level of the encounter as they were originally finalized in the August 2014 final rule. Per the change to §  422.310(f), CMS may only release aggregated dollar amounts reported for an associated encounter, retaining the regulatory text that currently exists at §  422.310(f)(2)(iv)-risk adjustment data is “subject to the aggregation of dollar amounts reported for the associated encounter to protect commercially sensitive data.” As stated in the Contract Year 2027 proposed rule, this change would not limit CMS disclosure of risk adjustment data as authorized under separate statutory authority.
                    </P>
                    <P>
                        Currently, § 422.310(f)(3) imposes the restriction that risk adjustment data will not become available for release before reconciliation for the applicable payment year has been completed, unless CMS determines that it is necessary for one of four specific exceptions.
                        <SU>44</SU>
                        <FTREF/>
                         Consistent with our proposed changes to remove the list of permissible uses and conditions for release of risk adjustment data, CMS also proposed to remove the detailed list of exceptions for release of risk adjustment data prior to reconciliation in paragraph (f)(3). The change would continue to allow for the release of risk adjustment data prior to reconciliation for the four previously identified exceptions and provide flexibility when CMS receives novel requests for data that have not been reconciled.
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             §  422.310(f)(3)(ii) through (f)(3)(v).
                        </P>
                    </FTNT>
                    <P>As discussed previously in section IV.C of the proposed rule, because MA plans have a window of time in which they should submit data corrections for a given payment year (typically January 31 of the year following the payment year), risk adjustment data are not considered reconciled for payment purposes before that date has passed. For this reason, there is currently a prohibition against releasing the data prior to the final submission deadline except in specific, limited circumstances. However, over time CMS identified more purposes for which using the data prior to reconciliation may be appropriate and that the original reasons and concerns that led to delaying the release of risk adjustment data in the August 2014 final rule may not always apply or may no longer apply. Some of the purposes identified are reflected in the recent changes to § 422.310(f)(3) where additional exceptions for early release were added, one of which is care coordination, but others may include program integrity initiatives that necessitate timelier data or to support beneficiaries in managing their health by allowing them to access and share their current data. For example, currently, through the CMS Blue Button 2.0 Application Programming Interface (API), an individual may choose to share their own Medicare A, B, and D claims data with Medicare-approved applications or websites that a third party (not Medicare) creates, thereby allowing an individual to use health technology and their own data to improve their health outcomes and decision making. In removing restrictions related to releasing pre-reconciled risk adjustment data, this tool could also be made available to MA enrollees.</P>
                    <P>While this update allows for release of risk adjustment data prior to reconciliation broadly, CMS understands that it is not always necessary and appropriate for risk adjustment data to be released prior to reconciliation. For example, relying on diagnosis information for research or program operations may not be appropriate before the final risk adjustment data submission deadline since plans have at least 13 months after the end of the service year to submit additional diagnoses for payment. CMS will review requests for the release of risk adjustment data prior to reconciliation to assess whether pre-reconciled data is necessary and appropriate for the requester's purpose. CMS's updates to remove restrictions on the use and release of pre-reconciled risk adjustment data would provide greater flexibility in the release of risk adjustment data, supporting the goals of Executive Order 14243 “Stopping Waste, Fraud, and Abuse by Eliminating Information Silos” (March 20, 2025). Additionally, by no longer restricting release to prescribed purposes, CMS is supporting the goals of Executive Order 14192 “Unleashing Prosperity through Deregulation” (January 31, 2025) by reducing the burden for CMS and external entities associated with the increasingly complex regulation that necessitates rulemaking when an unanticipated use of the data is identified.</P>
                    <P>CMS sought public comments on all aspects of the proposed revisions to the use and release of risk adjustment data at § 422.310(f) and allowing for greater flexibility in the release of data prior to the final risk adjustment data submission deadline. Summaries of and responses to the public comments on CMS's proposal to revise § 422.310(f) are presented below.</P>
                    <P>
                        <E T="03">Comment:</E>
                         The majority of commenters supported CMS's proposal to revise 42 CFR 422.310(f) to ease restrictions on the use and release of MA risk adjustment data. These commenters emphasized that increased transparency is necessary given the continued growth of the MA program and that the proposed revisions would better align MA risk adjustment data availability with OM data, noting that current regulations constrained research, oversight, and program evaluation. Commenters asserted that broader access to MA risk adjustment data would result in greater transparency and support improved program integrity, research, innovation, and accountability, including analyses of coding practices, care delivery, and utilization trends.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported the flexibility provided with the proposed regulatory revision to relax restrictions regarding the timing of release of MA risk adjustment data. Some commenters noted that delays and gaps in MA data have limited timely evaluation of MA program impacts on patient outcomes and costs, and emphasized that, given the growth of MA enrollment, MA data should more closely match OM data in timeliness, completeness, and quality. Several commenters urged CMS to ensure the data released is accurate and complete, requesting that CMS improve the completeness of encounter data to prevent inaccurate or misleading conclusions. A couple of commenters opposed the release of pre-reconciled data or urged CMS to maintain restrictions on pre-reconciled data, warning that incomplete or unvalidated data could be misinterpreted and result in inaccurate analysis.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the thoughtful comments and acknowledges the concerns raised regarding timeliness and completeness of MA risk adjustment data. While the proposed revision allows for release of MA risk adjustment data prior to reconciliation more broadly, CMS understands that it is not always necessary or appropriate for risk adjustment data to be used or released prior to the final risk adjustment data submission deadline, which is when data are considered reconciled for payment purposes for a given payment year. However, over time and as encounter data has matured, the 
                        <PRTPAGE P="17441"/>
                        original reasons and concerns that led to delaying the release of risk adjustment data in the August 2014 final rule may not always apply or may no longer apply. As reflected in the recent changes to § 422.310(f)(3), CMS has identified purposes for which use of the data prior to reconciliation may be appropriate, such as emergency preparedness and care coordination, and CMS believes other purposes may include those for program integrity, emerging health situations, to support beneficiaries in managing their health by allowing them to access and share their current data, for example, through the CMS Blue Button 2.0 Application Programming Interface (API), or for research initiatives that necessitate timelier data. Having flexibility to release risk adjustment data prior to reconciliation when necessary and appropriate reduces regulatory burden and removes barriers that slow progress and limit opportunities to effectively and efficiently administer, oversee, and improve Federal programs.
                    </P>
                    <P>CMS will continue to review requests for pre-reconciled MA risk adjustment data to ensure that pre-reconciled data are necessary and appropriate for the requester's purpose. The completeness and validity of the data will be considered during the review process. An example of a necessary and appropriate use of pre-reconciled data would be for the care coordination of beneficiaries participating in State Medicaid programs. However, since plans have at least 13 months after the end of the service year to submit diagnoses for payment, relying on diagnosis information for research or program operations may not always be appropriate before the final risk adjustment data submission deadline.</P>
                    <P>CMS continues to employ a range of activities aimed at improving the completeness and validity of encounter data including submission outreach, technical assistance, data analysis, and monitoring. These activities continue to improve the completeness and validity of encounter data. CMS continues to see evidence in the data that the efforts by the agency and MA organizations to improve accuracy and completeness of encounter data have been effective. Specifically, CMS's analysis conducted in 2023 found that the utilization data are complete in a similar time frame as OM claims. Further, a recent CMS analysis of encounter data records with 2021 dates of services submitted for payment year 2022 found that 97.7 percent of all encounter data records submitted by the risk adjustment reconciliation deadline (July 31, 2023) had been submitted by August 2022—8 months after the end of the service year.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stressed the importance of maintaining appropriate beneficiary privacy protections and enforcing robust safeguards through data sharing agreements and privacy and security requirements with expanded data sharing to ensure confidentiality and compliance with applicable Federal laws. A couple of commenters called for additional privacy protections, de-identification standards, and controlled-access environments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in the proposed rule, CMS will maintain existing guardrails that protect beneficiary information in accordance with applicable Federal laws such as the Privacy Act of 1974, section 1106(a) of the Act, and CMS information disclosure regulations at 42 CFR part 401, subpart B. CMS will be able to release an individual's risk adjustment data when authorized by that individual. For other kinds of requests for release of MA risk adjustment data, CMS will release such information in accordance with CMS data sharing procedures that reflect applicable Federal laws and agency privacy and security policies, consistent with current practice. We intend to continue to protect beneficiary data through, for example, encryption, or removal of the confidential fields when risk adjustment data is released. CMS has an established process to evaluate requests for CMS data and enters into data sharing agreements with data requesters for disclosures of MA risk adjustment data to ensure that data requesters agree to comply with CMS privacy and security requirements and data release policies. CMS maintains that this process contains the necessary checks and safeguards to appropriately protect beneficiary identifying information.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested transparency and clarity on what MA data fields are available for release and when data would be released, including requests for publication of a comprehensive data-element inventory, release cadence, and context notes to avoid misinterpretation or inaccurate analysis given the complexity of MA risk adjustment data. A few commenters requested clarity on which external entities or third parties may receive access to the data, under what terms or agreements and for what purposes. A commenter requested CMS retain explicit regulatory language noting that MA risk adjustment data may be released to States to avoid implying that CMS might bypass longstanding state partnerships as it broadens authority for external releases.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         MA risk adjustment data can be requested by external stakeholders, such as an individual, a group, an organization, a State, or Federal Agency, for a variety of purposes including, for example, for program administration and oversight, care coordination, research initiatives, public health preparedness, program integrity, and quality improvement. CMS does not intend to bypass longstanding state partnerships as it broadens authority for external releases.
                    </P>
                    <P>As discussed in the proposed rule, CMS has long-standing data sharing procedures and pathways for entities to request and obtain approval for access to CMS data, including risk adjustment data. This includes an evaluation by CMS to ensure that data requests comply with applicable Federal laws, regulations, and CMS data sharing policies. As part of the request process, unless the requester is a beneficiary requesting his or her own data, a data sharing agreement is established between CMS and the requesters prior to disclosing the data that documents the terms and conditions under which CMS data may be released and used to ensure that data requesters agree to comply with CMS privacy and security requirements and data release policies, including safeguards to protect beneficiary identifying information and confidentiality. In addition, data sharing agreements provide for potential enforcement mechanisms and penalties. Requesters of CMS data are responsible for abiding by applicable federal and state law, as well as the policies and restrictions of the data sharing agreements.</P>
                    <P>
                        General information on data products and data files available to external stakeholders can be found at the following link: 
                        <E T="03">https://www.cms.gov/data-research/cms-data/learn-more-about-cms-data.</E>
                         Detailed information on research requests, including the Research Data Use Agreement (DUA) and datafiles (including variables) available for request can be found at: 
                        <E T="03">https://resdac.org/.</E>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters appreciated that CMS maintained the regulatory language restricting the release of plan-submitted dollar amounts, with a few of those commenters stating that this restriction preserves safeguards on commercially sensitive information and minimizes the risk of potentially anticompetitive harm. A few commenters urged CMS to expand transparency by releasing the plan-submitted dollar amounts at the encounter level, arguing that the 
                        <PRTPAGE P="17442"/>
                        continued restriction on dollar amounts limits the ability to evaluate MA spending, provider payment methodologies, and enrollee cost-sharing, and is inconsistent with broader federal price transparency initiatives. These commenters asserted that increased disclosure could improve understanding of MA program performance, value of care, and benefit beneficiaries without causing competitive harm.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their comments and acknowledges concerns regarding the restriction of plan-submitted payment data. At this time, CMS will maintain the restrictions that currently exist such that we will not release plan-submitted dollar amounts associated with the items or services for which data is submitted to CMS pursuant to § 422.310(b) to characterize the context and purposes of each item and service provided to a Medicare enrollee by a provider, supplier, physician, or other practitioner. In the August 2014 final rule, we stated our belief that release of payment data at the level of the encounter record might reveal proprietary negotiated payment rates between MA plans and providers and, therefore, we restricted the release of payment data at the level of the encounter record without taking steps to protect the information through aggregation. While changes in federal laws and regulations, such as the Transparency in Coverage Final Rule (CMS-9915-F), and Executive Order 14221 “Making America Healthy Again by Empowering Patients With Clear, Accurate, and Actionable Healthcare Pricing Information” (February 25, 2025) are making plan pricing information for specific services more widely available in the group and individual health insurance markets, CMS believes the dollar amounts plans report at the encounter data record level are not ready for release at this time. CMS has not provided extensive guidance for the wide range of payment scenarios that exist in the MA program. As a result, plan practices for reporting service level payment amounts vary widely. CMS's research suggests that the data are a valid representation of MA spending on services in aggregate, but more research and guidance is needed before more detailed data can be made available. Consequently, CMS is maintaining the guardrails for payment data at the level of the encounter as they were originally finalized in the August 2014 final rule, with the inclusion of language to clarify that, as stated previously, these updates do not limit or supersede separate statutory authority that requires CMS disclosure of the data. We look forward to working with stakeholders to continue improving the reliability of plan-submitted payment data and may consider reassessing the restriction on its release in the future.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter raised concerns about commercial use of MA risk adjustment data, particularly with AI/machine learning companies, and urged CMS to limit or prohibit  “profit-driven” reuse of such risk adjustment data.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the August 2014 final rule CMS stated our intention to have consistent policies for the release of data across the OM (Parts A and B) program, the Part D prescription drug program, and the Part C Medicare Advantage program. We noted that in the event policy regarding the release of Parts A, B, and D data for commercial purposes were to change, we would also revise our Part C risk adjustment data sharing policies to be consistent with that change. Since 2014, CMS has established an innovator research program that allows a researcher associated with a for-profit organization to request data for research, or anyone to conduct research with the intent to create a product or tool to be sold. For example, an innovator could use CMS data to develop care management or predictive modeling tools. There are a number of additional protections in place to access data through the innovator research program. First, innovators provide information on the research that will be conducted. This is reviewed and approved by the CMS Privacy Board.
                        <SU>45</SU>
                        <FTREF/>
                         Second, innovators are required to provide information on the product, tool, or analyses that will be created using the CMS data. This information undergoes an extensive review to ensure that the data is not used to exploit beneficiaries or to create fraud or abuse in the CMS programs. CMS data cannot be used for marketing purposes. Finally, innovators are only permitted to access CMS data that are approved for their research protocol within the CMS Chronic Condition Warehouse Virtual Research Data Center (CCW VRDC). The CCW VRDC is a virtual research environment for securely accessing and analyzing CMS data. All individual-level data are stored in the CCW VRDC and cannot be downloaded. Innovators only have the ability to download aggregated and de-identified reports and results to their own personal workstation. CMS maintains that these protections provide sufficient safeguards on the commercial use of MA risk adjustment data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             The CMS Privacy Board is an internal CMS panel that reviews research requests for compliance with CMS data policies, but does not act as a HIPAA Privacy Board.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         We received some comments that were out of the scope of this regulation including broader transparency for MA data beyond risk adjustment data such as plan-level metrics, the cost of MA encounter data, more timely reporting requirements, additional reporting requirements, updates to the Part C and Part D risk adjustment models, and improvements to condition specific data. Additionally, some commenters requested CMS ensure plans receive risk adjustment data as early as possible for beneficiaries that move into their plan and others voiced concern regarding plan-initiated medical record requests.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback; however, we note that these comments are out of scope for the changes proposed to § 422.310(f). This provision concerns the use and release of the risk adjustment data MA organizations are required to submit to CMS. This provision does not address arrangements between plans and providers, risk adjustment methodology, or plan submission requirements.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the provisions at § 422.310(f) as proposed.</P>
                    <HD SOURCE="HD2">C. Strengthened Documentation Standards for Part D Plan Sponsors</HD>
                    <HD SOURCE="HD3">1. Background of Part D Coverage Determinations and Point-of-Sale (POS) Claim Adjudications</HD>
                    <P>
                        CMS regulations at § 423.566 specify that each Part D plan sponsor must have a procedure for making timely coverage determinations regarding the prescription drug benefits an enrollee is entitled to receive under the plan and the amount, including cost sharing, if any, that the enrollee is required to pay for a drug. In addition to a standard procedure for making such determinations, it must also have an expedited procedure for situations in which applying the standard procedure may seriously jeopardize the enrollee's life, health, or ability to regain maximum function, in accordance with § 423.570. When a Part D plan sponsor requires a drug to be reviewed for coverage under Part D, there is coordination between the Part D plan sponsor and another entity, such as the prescriber, pharmacy, enrollee, or enrollee representative, to ensure that the drug meets the criteria for coverage prior to accepting the claim for payment under the Part D benefit.
                        <PRTPAGE P="17443"/>
                    </P>
                    <P>Coverage determinations can be requested by the Part D enrollee, the enrollee's representative, or the prescriber on behalf of the enrollee. Current regulations at § 423.566(b) outline the actions that are considered Part D coverage determinations, such as a decision not to provide or pay for a Part D drug, including a decision not to pay because the drug is not on the plan's formulary, the drug is determined not to be medically necessary, the drug is furnished by an out-of-network pharmacy, or the Part D plan sponsor determines that the drug is otherwise excludable under section 1862(a) of the Act if applied to Medicare Part D.</P>
                    <P>
                        A POS claim adjudication occurs when a claim is submitted by a pharmacy for payment after the presentation of a valid prescription, regardless of whether the Part D plan sponsor treats the POS transaction as a coverage determination. In general, Part D plan sponsors do not treat POS claim adjudications as coverage determinations.
                        <SU>46</SU>
                        <FTREF/>
                         However, Part D plan sponsors may implement utilization management edits in various situations to determine a drug's coverage at the POS. In such cases, the Part D sponsor may or may not choose to treat the POS claim adjudication as a coverage determination, leading to variance among plan sponsors. One reason a Part D plan sponsor might require a coverage determination or POS claim adjudication edit is to verify a drug's coverage under the Part D benefit. For example, Part D plan sponsors can use prior authorization for drugs with the highest likelihood of non-Part D covered uses, such as when coverage is available under Part A or Part B (versus D) for the drug as prescribed and dispensed or administered, or when the drug is not used for a medically accepted indication (MAI).
                        <SU>47</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             Parts C &amp; D Enrollee Grievances, Organization/Coverage Determinations, and Appeals Guidance, Section 40.2 (found at 
                            <E T="03">https://www.cms.gov/Medicare/Appeals-and-Grievances/MMCAG/Downloads/Parts-C-and-D-Enrollee-Grievances-Organization-Coverage-Determinations-and-Appeals-Guidance.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             Medicare Prescription Drug Benefit Manual, Chapter 6—Part D Drugs and Formulary Requirements, Section 30.2.2.3 (found at 
                            <E T="03">https://www.cms.gov/Medicare/Prescription-Drug-Coverage/PrescriptionDrugCovContra/Downloads/Part-D-Benefits-Manual-Chapter-6.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <P>Depending on the drug, Part D plan sponsors vary the scope of review when determining coverage or conducting a POS claim adjudication that determines coverage, and therefore, CMS must be able to review the plan sponsors' original documentation to ensure that a Part D plan sponsor asked relevant questions and received appropriate responses for the drug being reviewed. For example, in the instance of reviewing a drug for an MAI, the Part D plan sponsor needs to verify the diagnosis that led to the drug being prescribed to ensure that it is being prescribed and dispensed for an MAI and is eligible for coverage under Part D.</P>
                    <HD SOURCE="HD3">2. Audits of Part D Program Integrity Prescription Drug Event Records</HD>
                    <P>Under section 1860D-12(b)(3)(C) of the Act and 42 CFR 423.505(d)-(e), Part D plan sponsors are required to maintain certain categories of documentation for specified periods of time. Specifically, § 423.505(d) requires that the contract between a Part D plan sponsor and CMS include an agreement by the Part D plan sponsor to maintain books, records, documents, and other evidence of accounting procedures and practices for 10 years that are sufficient to meet certain requirements, including enabling CMS to evaluate the quality, appropriateness, and timeliness of services performed under the contract and to audit the services performed or determinations of amounts payable under the contract. In addition, § 423.505(e) requires that Part D plan sponsors agree to allow HHS, the Comptroller General or their designee to evaluate through audit, inspection, or other means (1) the quality, appropriateness, and timeliness of those services furnished to Medicare enrollees; (2) compliance with CMS requirements for maintaining the privacy and security of protected health information and other personally identifiable information of Medicare enrollees; (3) facilities of the Part D sponsor; and (4) enrollment/disenrollment records for the current contract period and 10 prior periods. Furthermore, §§ 423.568(a)(3), 423.570(c)(2), and 423.584(c)(1) outline requirements for Part D plan sponsors to establish and maintain a method of documenting and to retain documentation for oral requests for coverage determinations under standard timeframes, expedited timeframes, and redeterminations respectively.</P>
                    <P>Although the statute and current regulatory requirements address documentation maintenance and availability, these requirements do not detail the documentation needed to be maintained to support the appropriateness of a Part D coverage determination or POS claim adjudication that is used to determine coverage under the Part D benefit. The availability of complete and accurate documentation in its original format (for example, fax, call notes, electronic PA), is a key component of ensuring that taxpayer dollars are spent appropriately in the Part D program. Through CMS's Part D program integrity prescription drug event (PDE) record review audits, we have observed a large degree of variation among the documentation that Part D plan sponsors maintain when conducting coverage determinations, including prior authorizations, and POS claim adjudication edits, used to determine a drug's coverage under Part D, and subsequently provide to CMS upon audit. While some Part D plan sponsors have robust documentation standards that outline the information the Part D plan sponsor obtained that led to coverage under the Part D benefit, others provide or maintain little to no documentation. In some instances, plan sponsors maintain a summary of the original coverage request or refer to a past coverage determination to extend an authorization. In these instances, CMS is unable, upon audit, to review the original documentation to ensure that the information obtained was accurate. For CMS to provide proper oversight of the Part D program and the approvals made for drugs covered under the Part D benefit, it is imperative that Part D plan sponsors provide and maintain original documentation that describes how and why the Part D plan sponsor approved a drug for coverage. Without sufficient documentation, CMS cannot fully review, during an audit or educational analyses, or other program integrity efforts, Part D plan sponsor coverage determinations and POS claim adjudications for accuracy. The standardization and availability of sufficient documentation to support a drug's coverage under the Part D benefit will allow CMS to conduct more effective audits and help ensure CMS can verify that a drug was accurately paid under Part D.</P>
                    <HD SOURCE="HD3">3. Provisions</HD>
                    <P>
                        We proposed standardized, detailed documentation requirements for coverage determinations and POS claim adjudications, used for purposes of determining coverage under the Part D benefit. We proposed documentation requirements that include but are not limited to certain written, verbal, and electronic communications, such as the date and time the request was received; the name and title of the individual who submitted or verified the request; and the information used to make the coverage determination. These requirements would not apply to POS claim adjudications for purposes that are unrelated to the determination of coverage under the Part D benefit or the correct Medicare benefit for coverage, 
                        <PRTPAGE P="17444"/>
                        such as those POS claim adjudications for safety, dose limitations, and quantity limits. Any additional documentation recorded or maintained will be subject to existing protected health information (PHI) and personally identifiable information (PII) rules and regulations.
                    </P>
                    <P>Specifically, we proposed the following revisions to the documentation requirements:</P>
                    <P>• First, to revise § 423.505(d)(1) to add new paragraph (vi) to enable CMS to review original format documentation or information from all written, electronic, and verbal communications between the pharmacist, prescriber, enrollee, or other relevant stakeholders, in addition to what is included on the pharmacy claim, that is relied upon by the Part D plan sponsor to make a coverage determination or otherwise permit a point-of-sale claim adjudication that determines a drug's coverage under the Part D benefit. In instances when a coverage determination is extended, the original coverage determination must be maintained as documentation. The documentation covered by these standards must be made available to CMS during Part D program integrity prescription drug event (PDE) record review audits. Failure to produce this documentation will result in an improper Part D audit determination and will be subject to PDE record deletion in accordance with § 423.325(a)(2).</P>
                    <P>• Second, to revise § 423.505 to add the following new paragraphs:</P>
                    <P>++ Paragraph (d)(2)(xiii) to include all documentation or information from all written, electronic, and verbal communications between the pharmacist, prescriber, enrollee, or other relevant stakeholders, in addition to what is included on the pharmacy claim, that is relied upon when a Part D plan sponsor makes a coverage determination or otherwise permit a point-of-sale claim adjudication that determines coverage of a drug under the Part D benefit, consistent with paragraph (d)(1)(vi). This includes:</P>
                    <P>++ Paragraph (d)(2)(xiii)(A) to include the date and time the request for a coverage determination or point-of-sale claim adjudication was received and the identity of the individual who submitted the request.</P>
                    <P>++ Paragraph (d)(2)(xiii)(B) to include the name and title (as applicable) of the individual the Part D plan sponsor contacted to verify the request (for example, pharmacist, prescriber, enrollee, or enrollee representative).</P>
                    <P>++ Paragraph (d)(2)(xiii)(C) to include information obtained, including the questions asked and the responses received, and the final decision rendered.</P>
                    <P>++ Paragraph (d)(2)(xiii)(D) to include the diagnosis code for a coverage determination or point-of-sale claim adjudication used to support a medically accepted indication.</P>
                    <P>++ Paragraph (d)(2)(xiii)(E) to include any additional information that the Part D plan sponsor utilized to determine the final outcome of the coverage determination or point-of-sale claim adjudication request.</P>
                    <P>• Third, to revise § 423.505(e)(2) to add a phrase to reference the requirement to make available the records containing information used to make the coverage determination or POS claim adjudication.</P>
                    <P>We received public comments on these provisions in the proposed rule. The following is a summary of the comments we received and our responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters were in support of the proposed provision to require standard documentation for coverage determinations and POS edits that determine coverage. Of note, commenters acknowledged this was critical to effective auditing, promoting compliance, improving consistency, enhancing beneficiary understanding of coverage, reducing administrative burden, and enhancing program integrity. One commenter also expressed support for the provision as it levels the playing field for smaller health plans and increases transparency for health plans that are vertically integrated. In addition, a few commenters noted that they are in support of documentation standards as long as they avoid duplicative and prescriptive requirements, and one commenter suggested providing documentation templates.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' support on its efforts to strengthen program integrity. It is CMS's intention to standardize documentation standards for all Part D plan sponsors to ensure proper oversight of the program while not increasing burden for plan sponsors. CMS understands the commenter request for documentation templates; however, given the vast array of systems and flexibilities for plan sponsors and the varying information needed for different requests, CMS cannot create one singular template that would be applicable universally.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters requested clarification on the meaning and intent of “original format documentation,” particularly as it pertained to audio recordings. Commenters expressed concern for the administrative and financial burden of maintaining audio recordings, especially on small health plans. Another commenter requested examples of original format documentation and if call notes or transcripts would suffice. It was further recommended that retention of transcripts be permitted in lieu of recordings. A few commenters suggested it would create a great burden especially for plan sponsors to obtain communications between pharmacists, prescribers, enrollees, or other stakeholders that plan sponsors do not currently collect or have direct access to, such as pharmacies that cannot transmit their internal call notes to plans. One commenter recommended that CMS clarify if scanned or digitized copies of documents are considered original records for purposes of compliance.
                    </P>
                    <P>In addition, a commenter expressed concern that this requirement may read as retention beyond the 10-year standard, effectively increasing costs, annual coverage determinations and burden. It was noted by another commenter that CMS already can request the original coverage determination documentation during audit and that no new documentation requirement is needed.</P>
                    <P>Another commenter supported the requirement for plan sponsors to maintain original format documentation.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands the commenters' concerns and requests for clarification surrounding “original format documentation.” In regard to audio recordings, we do not expect the retention of the actual audio recording; a transcript or call note(s) of the call will be sufficient documentation. The maintenance of transcripts or call notes should not increase burden on plan sponsors because this information should already be maintained. However, the information in a transcript or call note(s) of an audio recording must include sufficient information to allow CMS to fully evaluate the appropriateness of coverage under the Part D program in accordance with § 423.505(d)(ii). Additionally, a scanned or digitized copy of a request will be considered original format documentation.
                    </P>
                    <P>
                        Regarding the comments about obtaining communications between pharmacists, prescribers, enrollees, or other stakeholders and the worry that plan sponsors do not have access to those calls or communications, CMS agrees with the commenters' concerns and did not intend to suggest that those communications be collected. Rather, the proposed provisions related to 
                        <PRTPAGE P="17445"/>
                        expectations of Part D plan sponsors, including that plan sponsors maintain communications that 
                        <E T="03">they</E>
                         have with these different entities, not communications that those entities have with one another. CMS is therefore modifying the language of the proposed rule to clarify that the communications that must be maintained are between the plan sponsor and those entities.
                    </P>
                    <P>Plan sponsors must have documentation to support Part D coverage determinations and POS edits that determine coverage, including when an authorization is reauthorized for an extended period or original approved for a timeframe greater than 10 years. If the authorization is still ongoing, documentation must be available to support it.</P>
                    <P>CMS agrees that original coverage determination documentation is already expected upon audit; however, we disagree with the commenter that no new documentation standards are necessary. As stated in the proposed rule, the documentation CMS receives during an audit varies greatly among plan sponsors. An example would be a call note stating “approved Part D” instead of documentation reflecting the questions asked and answers provided during the call. For this reason, CMS believes it is imperative to establish standards for strengthening oversight and ensuring all plan sponsors are being held to the same standards.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters requested clarification on what is meant by both the “entity who submitted the request” and the “name and title (as applicable) of the individual the Part D plan sponsor contacted to verify the request,” including what is meant by “verify the request.” One commenter questioned how the name and title of the requester applied to a POS claim. A few commenters requested that CMS clarify the expectation for handling requests when information is unavailable to the plan sponsor, including the expectation for documenting the name and title of an individual when additional information is not required to verify a request. It was also noted that plan sponsors, especially PDPs, do not have contracts with the providers and cannot enforce the information being provided. A commenter also questioned the ability of plan sponsors to obtain this information, especially from large provider groups. Additionally, a commenter noted that these requirements will extend adjudication processing time to ensure documentation retrospectively while not providing any real-time clinical decision-making benefit, while another noted that the requirements proposed goes far beyond what is reasonable or necessary for effective program oversight.
                    </P>
                    <P>A few commenters expressed concern over providing the information CMS proposed to require, as the NCPDP standard for coverage determinations does not allow for the collection of this information. A commenter noted that plan sponsors often have no mechanism to capture this information, especially the identity of the individual submitting the pharmacy claim and verbal discussions between the prescriber, pharmacist and patient. Another commenter noted that plans are prohibited from requiring submission(s) on a specific form and must accept any format.</P>
                    <P>Another commenter supported the requirement to document the identity and title of the individual submitting a coverage determination or POS request, as well as the individual contacted to verify it as it establishes accountability, improves the accuracy and efficiency of follow-up when documentation is incomplete or inconsistent, enables identification of aberrant or high-risk submission patterns, and supports CMS's ability to validate that drugs were paid for medically accepted indications (MAIs).</P>
                    <P>
                        <E T="03">Response:</E>
                         The “entity who submitted a request” refers to the person who submitted the coverage determination request. CMS's Part C &amp; D Enrollee Grievances, Organization/Coverage Determinations, and Appeals Guidance 
                        <SU>48</SU>
                        <FTREF/>
                         states that an individual or entity authorized to request a coverage determination include: (1) enrollee, (2) enrollee's appointed representative, (3) prescribing physician or other prescriber, or (4) any individual representative authorized under state or other applicable law. This information is important to CMS for determining that an appropriate entity requested the coverage determination and allows CMS to monitor for potential fraud, waste, and abuse in instances where an entity is requesting determinations on their own behalf to increase utilization and payment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             Parts C &amp; D Enrollee Grievances, Organization/Coverage Determinations, and Appeals Guidance, (found at 
                            <E T="03">https://www.cms.gov/Medicare/Appeals-and-Grievances/MMCAG/Downloads/Parts-C-and-D-Enrollee-Grievances-Organization-Coverage-Determinations-and-Appeals-Guidance.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <P>In regard to the “name and title (as applicable) of the individual the Part D plan sponsor contacted to verify the request,” CMS is referring to those situations in which plan sponsors conduct further follow up with an individual or entity to clarify a coverage determination. For example, in the case of conflicting or missing information needed to approve coverage, CMS would want to ensure that the individual contacted would be able to provide the information necessary to determine coverage. For instance, a beneficiary may not have the necessary information to determine if a drug or service was covered by Medicare. CMS believes this information is still relevant, when available, for a POS edit that determines coverage. In accordance with the Prescription Drug Benefit Manual (PDBM), a plan sponsor that approves or denies a drug through application of a POS edit has made a coverage determination and is subject to all applicable coverage determination standards, timelines, and requirements. As such, plan sponsors maintain some level of information or automation that allowed the POS edit to make an appropriate coverage determination. In these instances, CMS would expect to see what in their system determined that the drug was covered under the Part D program and make that information available to CMS upon audit.</P>
                    <P>However, CMS does understand that this information may not be available in all instances and/or may be unobtainable by the plan sponsors within authorization timeframes due to a variety of reasons, such as unresponsive entities or format of the coverage determination, including the NCPDP standard. CMS did not intend to require plan sponsors to reject a claim based on the lack of this information, but to include it when reasonable and obtainable. CMS does not expect plan sponsors to perform additional outreach if the information available to the plan sponsor clearly illustrates how a decision for Part D coverage was made.</P>
                    <P>Based on the comments received, CMS is modifying the proposed regulatory text to make it clear for plan sponsors that the identity of the individual requiring the coverage determination be provided when available. CMS already had proposed “as applicable” language for the name and title of the individual the plan contacted to verify the request, but is modifying the proposed language to better clarify that the identity of the individual the plan contacted to verify the request refers to who was contacted in instances when additional information is needed to complete a request.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters questioned the need for a diagnosis code to establish a MAI, as this information is captured in different manners, such as ICD-10 codes, provider attestations and medical record review. Other 
                        <PRTPAGE P="17446"/>
                        commenters questioned if widespread Part D coverage of drugs is a significant driver of improper payments, especially in cancer treatments and questioned if gathering the MAI at the POS is warranted given risks of imperfect, insufficient, or delayed coding especially in oncology and ultra rare disease. A commenter suggested that CMS clarify how a plan sponsor should adjudicate and document coverage determinations, including when both coverable and non-coverable diagnoses are listed and clarification cannot be obtained within adjudication timeframes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenters' discussion on the requirement to provide a diagnosis code for coverage determinations reviewing for a MAI. CMS agrees that a diagnosis code itself may be limiting in some instances as suggested by commenters in oncology or rare disease, and CMS is modifying the language in the proposed rule to remove the terminology “code.” This will provide the plan sponsors with flexibility in instances where the diagnosis is provided by ICD-10 code, prescriber attestations, or medical records.
                    </P>
                    <P>CMS does expect plan sponsors to ensure that drugs are only covered under the Medicare Part D program when they are prescribed and dispensed or administered for an MAI in accordance with the section 1860D-(2)(e)(4) of the Act. CMS does recognize that not all drugs can be monitored for MAI at the POS, specifically as it relates to routine drugs. However, plan sponsors do make formulary decisions for their organization as it relates to coverage determinations, such as prior authorization, for drugs that have a high likelihood of being utilized for a non-MAI. In these instances, CMS expects that plan sponsors document a diagnosis used by the plan sponsor in making a coverage determination under the Part D benefit. In instances where there is conflicting information, CMS expects plan sponsors to make a reasonable determination within the adjudication timeframes but notes that plan sponsors should retrospectively be getting clarification to ensure proper coverage for the drug.</P>
                    <P>Under the rule as proposed, plan sponsors would be required to supply a diagnosis on any coverage determination or POS edit that determines coverage for only those coverage determinations reviewing a drug for a MAI. Based on the commenters' feedback, CMS is modifying the proposed language to clarify and be more explicit that the requirement for a diagnosis is only for those reviews of a MAI.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that plan sponsors may feel compelled to require a diagnosis on all prescriptions for a likelihood of non-Part D covered uses, even though CMS does not explicitly propose this. The commenter further noted that prescribers are not required to include diagnosis codes on all scripts and NCPDP standards do not require pharmacies to submit them.
                    </P>
                    <P>Additionally, a commenter noted that CMS should establish that coverage determinations made via ePA transactions conforming to adopted standards (for example, NCPDP SCRIPT or successor standards) are compliant with documentation requirements when the structured transaction data is retained, as this includes clinical criteria responses, attestations, and decision outcomes.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees with the commenter that requiring a diagnosis on all prescriptions was not proposed by CMS and is, therefore, outside the scope of this provision.
                    </P>
                    <P>Further, CMS disagrees with the commenter that CMS should establish that coverage determinations made via an adopted standard are compliant with the documentation standards. CMS recognizes that different authorizations require different information, and CMS cannot state that any one standard will fulfill all requirements of all request types.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported CMS's proposal for standardization but suggested that CMS coordinate audit methodologies and create standard requirements and protocols across Centers for consistency, to minimize duplication and improve understanding and compliance. The commenter noted that the proposal only affects CMS Part D Self-Audits, which would cause misalignment between auditing programs and increase burden. It was also noted by a commenter that currently, plan sponsors are not told why a PDE failed and not offered the opportunity to rebut, which is inconsistent with other program audits in CMS. A few commenters questioned the interplay between CMS's expectations for plan sponsors to approve coverage determinations timely and utilize information available while also expecting detailed documentation retrospectively.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their feedback. CMS currently coordinates internally on upcoming audits and methodologies. CMS will continue to work internally to enhance program auditing by reducing any audit duplication, minimizing burden for plan sponsors, and creating consistency when able. CMS also clarifies that these requirements would apply to any program integrity PDE record review audit, which currently would include CMS's Part D Self-Audits and National Audits. CMS believes that these proposed standards will streamline auditing and ultimately make it easier for plan sponsors to provide case files upon audit, as well as create consistency across plan sponsors. CMS appreciates the commenters' concern for the current audit methodology in which plan sponsors are not provided why a specific PDE record failed and subsequently no mechanism to appeal. The audit methodology, including determination rationale, is not a part of this rule and is outside the scope of this specific provision; however, CMS will take this comment into consideration for audit enhancements.
                    </P>
                    <P>In addition, CMS notes that it proposed to create a mechanism for appeal elsewhere in the proposed rule, which is being finalized at 42 CFR part 423 subpart Z (90 FR 54962). CMS also recognizes that plan sponsors have expectations to approve or deny determinations within adjudication timeframes set by CMS using the best available information. However, if a plan sponsor utilizes the best information available and knows that information was missing or conflicting, plan sponsors should be retrospectively performing outreach to ensure appropriate coverage of its drugs, items or services.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the proposed documentation standards but noted that CMS's formulary oversight lacks transparency. Of note, stakeholders have limited insight into how CMS evaluates submissions and utilization management criteria. Specific criteria to increase transparency were recommended including quarterly or annual summaries of Part D formulary review, structured process for stakeholder input, standardized reporting and transparency for a variety of indicators such as coverage determinations by drug category, approval and denial rates, average turnaround times and the clinical criteria applied, and auditing to identify patterns of inappropriate denials and denial appeals.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their concerns over CMS's formulary oversight; however, that subject is outside the scope of the proposed provisions.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that there is no differentiation between coverage determinations and POS 
                        <PRTPAGE P="17447"/>
                        determinations. One commenter expressed that POS decisions are not coverage determinations and should be exempted from the more extensive documentation CMS is proposing, as at the pharmacy level it could disrupt efficient real-time coverage authorization processes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees with the commenters that not all POS decisions are coverage determinations, such as those triggered based on an approved formulary criteria such as quantity limits. However, in accordance with the PDBM, a plan sponsor that approves or denies a drug through application of a POS edit has made a coverage determination and is subject to all applicable coverage determination standards, timelines, and requirements. As such, plan sponsors maintain some level of information or automation that allowed the POS edit to make an appropriate coverage determination. In these instances, CMS would expect to see what in their system determined that the drug was covered under the Part D program and make that information available to CMS upon audit. For these reasons, CMS proposed that only coverage determination and those POS edits utilized to determine coverage are subject to these requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed concerns over the implications for pharmacies and pharmacists. It was noted that pharmacists work in fast-paced environments and verbal exchanges are not recorded, and therefore, mandating capture would disrupt workflow, reduce patient care time, and add administrative burden. A commenter suggests that CMS ensure Part D plan sponsors are solely responsible for recording these interactions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS clarifies that pharmacists and pharmacies are not subject to the requirements proposed at § 423.505 and would not be held accountable for capturing exchanges with the plan sponsors. The requirements proposed are applicable to the plan sponsors contracted by CMS and subject to the requirements at § 423.505.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed concern over PDE records, upon audit, being subject to deletion for not having all information documented and the implications it could have on timely decision making, conflicting with CMS's beneficiary-first approach to coverage determinations. It was noted that plan sponsors may hesitate to approve coverage for high-cost drugs, impose stricter internal evidence requirements than medically necessary, or require additional documentation slowing access. Another commenter expressed that the requirement to maintain “any additional information that the Part D plan sponsor utilized to determine the final outcome of the coverage determination or point-of-sale claim adjudication request” is broad and unclear especially when tied to PDE record deletion upon audit. Commenters recommended that CMS provide alternative oversight approaches that leverage existing documentation requirements and improved audit methodologies. Alternatively, another commenter recommended that CMS soften the terminology from “will” to “may” in regard to marking a PDE record as improper.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS, through previous comment responses, clarifies that not all information in the documentation standards is required for every coverage determination and POS edit that determines coverage. For CMS to provide oversight and ensure that plan sponsors are meeting their requirements to only provide coverage for Part D when it meets the definition of a Part D drug, CMS must be able to review the information utilized by the plan sponsor. When not documented sufficiently, CMS is unable to determine that it was appropriately covered under Medicare Part D, which may lead to an audit finding that the PDE was improper. CMS has modified the proposed regulatory text to clarify that not all requirements are expected for every determination, as not every determination is evaluating the same criteria. The language modifications clarify that some requirements are only necessary when applicable or available, while others like the questions asked and responses received that led to coverage under Part D are required for documentation to be considered sufficient for CMS to evaluate appropriateness. Therefore, documentation provided to CMS upon audit that does not contain each proposed requirement will not automatically mean that a PDE records is deemed improper.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS adopt an audit approach to focus on enhanced documentation review on coverage determinations with elevated program integrity risk, drugs with Part B/D coverage, or drugs with unknown fraud or abuse patterns. It was noted that this approach targets resources without imposing uniform burden across all coverage determinations. Another commenter suggested adopting a risk-based audit approach, where plans with strong compliance histories or those in the upper performance quartile are audited less frequently.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS clarifies that the program integrity PDE record review audits currently focus on enhanced documentation review for coverage determinations and POS edits that determine coverage, specifically for drugs, items, or services that have a high likelihood that, (1) coverage is available under Parts A or B, (2) the drug is excluded from coverage or otherwise restricted under Part D, or (3) the drug is used for non-medically accepted indications
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed that these requirements may slow prior authorization and coverage determination processes that are in opposition to CMS's efforts to streamline administrative requirements. It was suggested that these requirements could hinder the industry's progress toward automation and electronic prior authorization and could unintentionally undermine both beneficiary access and the modernization goals shared by CMS and plan sponsors. It was recommended that CMS consider not finalizing the proposed documentation language and instead work with plans to develop documentation standards that support program integrity without creating operational inefficiencies or impeding automation efforts.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for the suggestions. CMS's intent is not to change the current process for prior authorization and coverage determinations, but rather to have the plan sponsors document the information they are already collecting to determine coverage under Medicare Part D when approving coverage determinations or POS edits that determine coverage. CMS is modifying the proposed language to clarify not all information is required in all situations to address concerns about increasing administrative burden to gather the information proposed.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters opposed CMS's provision to standardize documentation requirements. Overall concerns expressed pertain to unintended consequences for beneficiary access, increased administrative burdens, and financial risk.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for sharing their concerns regarding the proposed provisions. Many of the specific concerns voiced by these commenters that led to the consequences of beneficiary access, increased administrative burdens, and financial risk were addressed in other comments. CMS believes that modifications to the regulatory language 
                        <PRTPAGE P="17448"/>
                        proposed will mitigate many of the commenters' concerns. For example, adding that some of the requirements are “as applicable” allows plan sponsors discretion in the documentation required based on the specific evaluation criteria for each coverage determination and when the information is not obtainable due to outreach going unanswered. CMS does not expect plan sponsors to do additional outreach for coverage determinations but does expect plan sponsors to provide sufficient and clear documentation that shows how a coverage determination or POS edit that determines coverage led to Medicare Part D approval. CMS believes the burden is minimal and the benefits of program oversight and beneficiary safety vastly outweigh the perceived burden by plan sponsors.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the proposal as modified.</P>
                    <HD SOURCE="HD2">D. Updating Third-Party Marketing Organizations (TPMO) Disclaimer Requirements (§§ 422.2267 and 423.2267)</HD>
                    <P>
                        As a part of the Medicare Program; Contract Year 2023 Policy and Technical Changes to the Medicare Advantage and Medicare Prescription Drug Benefit Programs; Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency; Additional Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency Final Rule which appeared in the 
                        <E T="04">Federal Register</E>
                         on May 9, 2022 (hereafter referred to as the May 2022 final rule) (87 FR 27704), as a part of a broader effort to address concerns with TPMOs, CMS finalized regulations at §§ 422.2267(e)(41) and 423.2267(e)(41) to improve regulatory oversight of Third-Party Marketing Organizations (TPMOs). One provision required Medicare Advantage (MA) organizations and Part D sponsors to ensure that the TPMOs, with whom MA organizations and Part D sponsors directly or indirectly do business, verbally convey a standardized disclaimer during sales calls with beneficiaries. CMS implemented these regulations after listening to TPMO-based sales calls and hearing first-hand beneficiary confusion about the information the TPMO was conveying and to help ensure that TPMOs were not marketing information in a misleading way that might lead beneficiaries to join a plan contrary to their intention, or a plan that did not best meet their health care needs. The disclaimer, as finalized, consisted of the following statement: “We do not offer every plan available in your area. Any information we provide is limited to those plans we do offer in your area. Please contact 
                        <E T="03">Medicare.gov</E>
                         or 1-800-MEDICARE to get information on all of your options.” After these regulations were implemented, CMS continued to monitor TPMOs' interactions with beneficiaries during these sales calls. In CMS's review of hundreds of sales, marketing, and enrollment audio calls, CMS found that only one plan option from one MA organization was discussed in over 80 percent of the calls reviewed. These reviews also showed that TPMOs rarely, if ever, informed the beneficiary that there were multiple plans available in their service area. Although the TPMO may have researched other plans, the TPMO rarely communicated information about those plan options to the beneficiary; thus, the beneficiary may not have known about other available options. These monitoring efforts heightened CMS's concern that beneficiaries were not receiving comprehensive information about all their plan choices, thus limiting their ability to make an informed decision about the plan best able to meet their health care needs.
                    </P>
                    <P>To address those concerns, CMS issued the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program; and Programs of All-Inclusive Care for the Elderly Final Rule, hereinafter referred to as the April 2023 final rule (88 FR 22120). In this final rule, CMS amended §§ 422.2267(e)(41) and 423.2267(e)(41) revising the existing disclaimer, which was applicable to TPMOs that represented more than one, but not all, MA organizations or Part D sponsors in a given service area, to notify the beneficiary about the number of organizations and the number of plans the organizations offered. Additionally, CMS revised §§ 422.2267(e)(41) and 423.2267(e)(41) to include a new required disclaimer for TPMOs that contracted with every MA organization or Part D sponsor in a service area. Finally, CMS added State Health Insurance Assistance Programs (SHIPs) as a source of information for beneficiaries to both versions of the disclaimer and required TPMOs convey the applicable disclaimer within the first minute of a sales call, among other requirements for the TPMO to communicate the disclaimer through other electronic means or materials (as described under §§ 422.2267(e)(41) and 423.2267(e)(41)).</P>
                    <P>In the April 2023 final rule, CMS addressed comments received in response to the proposed rule (88 FR 22120). Some industry stakeholders raised concerns about the new disclaimer requirements. For example, some asserted that requiring TPMOs to list all the plans with which they contract would confuse or distract beneficiaries; or for those TPMOs that represent many plans, the disclaimer would be too long to read within the first minute. Similarly, some stakeholders pointed out that budget constraints and limited training would hinder a SHIP's ability to effectively assist beneficiaries with plan choices. While CMS understood those concerns, given CMS's observations about common TPMO interactions with beneficiaries during the sales and enrollment calls previously described, the Agency determined that these regulatory changes were warranted.</P>
                    <P>
                        CMS regularly reviews MA and Part D program requirements and how they affect Medicare beneficiaries and industry stakeholders. Based on CMS's review and industry feedback, CMS determined that additional changes to the TPMO disclaimer may be appropriate. CMS proposed to modify the TPMO disclaimer requirement in §§ 422.2267(e)(41) and 423.2267(e)(41) to: (1) replace the existing requirement to read the disclaimer within the first minute of the call, so that TPMOs are instead required to read the disclaimer “prior to the discussion of any benefits” during the call, and to: (2) remove SHIPs as a source of information from the disclaimer. CMS has determined that requiring TPMOs to convey the disclaimer during the first minute of a sales call is not always the appropriate time to notify the beneficiary of the number of plan choices available. CMS believes that many calls typically begin with the TPMO obtaining basic demographic information from the beneficiary, which allows the TPMO to immediately determine if the call should proceed to the benefit discussion phase. In other instances, the TPMO may determine that the beneficiary does not have a valid election period, which would end the call, making the disclaimer unnecessary. Notifying the beneficiary of the number of plans that a TPMO represents in the first minute does not always promote clear communication with the beneficiary or mitigate beneficiary confusion. By permitting TPMOs to read the disclaimer at an appropriate point during the call, provided it is read prior to the discussion of any benefits, the disclaimer will fit in better with the flow of the conversation. CMS does not consider the mere mention of a benefit, 
                        <PRTPAGE P="17449"/>
                        for example pointing out that nearly all MA organizations offer routine dental care, constitutes a discussion of benefits. Rather, CMS believes that discussing the specificity of a benefit with the intent to draw a beneficiary's attention to an MA or Part D plan(s), or to influence a beneficiary's decision-making process when making an MA or Part D plan selection, or to influence a beneficiary's decision to stay enrolled in a plan, could represent a discussion of benefits, as defined by the marketing definition under §§ 422.2260 and 423.2260. This could include, for example, talking with a beneficiary about the benefits listed in a plan's Evidence of Coverage document, or how beneficiary out of pocket cost sharing might work given a plan's benefit structure and the beneficiary's previous health care experience or needs. If there is no discussion of benefits, CMS would not expect TPMOs to provide the disclaimer to beneficiaries. When proposing these changes, CMS solicited comment on how the Agency should identify when a “discussion of benefits” occurs.
                    </P>
                    <P>In the Contract Year 2027 proposed rule, CMS only proposed changes to the TPMO disclaimer provision at §§ 422.2267(e)(41)(ii) and 423.2267(e)(41)(ii). Thus, the proposal did not alter the existing requirements provided within §§ 422.2267(e)(41)(i), (iii), (iv), and (v); and 423.2267(e)(41)(i), (iii), (iv), and (v). That is, any TPMO, as defined under §§ 422.2260 and 423.2260, that sells plans on behalf of more than one MA organization or Part D sponsor, must electronically convey the TPMO disclaimer when communicating with a beneficiary through email, online chat, or other electronic means of communication, prominently display the disclaimer on TPMO websites, and include the disclaimer in any marketing materials, including print materials and television advertisements, developed, used or distributed by the TPMO.</P>
                    <P>CMS also proposed to remove SHIPs as a source of information from the disclaimer. CMS recognized that, while SHIPs can be a source of unbiased information about plan choices, informing beneficiaries on every sales call about the SHIP may cause additional issues for beneficiaries. SHIP volunteers may not always have the expertise to help beneficiaries navigate increasingly complex MA and Part D programs. CMS stated that beneficiaries enrolled in the MA and Part D programs may be more effectively served by information and entities for which CMS has direct oversight. CMS also recognized that each SHIP works differently and provides different training to its counselors, which can vary further at the local level. This can result in Medicare beneficiaries receiving different information based on the SHIP and SHIP counselor that is ultimately reached. CMS stated that, for the TPMO disclaimer, 1-800-MEDICARE is a better option to assist beneficiaries with health care choices.</P>
                    <P>1-800-MEDICARE has representatives available 24/7 to assist beneficiaries, provides standardized training to its customer service representatives, is centrally monitored and controlled by CMS, which facilitates efficient and consistent information sharing, and is a one-stop shop for all beneficiaries, regardless of the state in which they live.</P>
                    <P>
                        In summary, and for reasons previously discussed, CMS proposed to revise introductory text in §§ 422.2267(e)(41) and 423.2267(e)(41) to remove references to the SHIPs, while maintaining guidance for beneficiaries to contact 
                        <E T="03">Medicare.gov</E>
                         or 1-800-MEDICARE for plan advice. Additionally, CMS proposed to revise §§ 422.2267(e)(41)(ii) and 423.2267(e)(41)(ii) to require TPMOs to provide the TPMO disclaimer during sales calls before engaging in discussions about benefits rather than requiring TPMOs to verbally convey the disclaimer during the first minute of a sales call.
                    </P>
                    <P>CMS solicited comments on this proposal and appreciates stakeholders' input on the proposed changes. The Agency received the following comments and provided responses as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         CMS received several comments supporting the proposal to adjust the timing of when TPMOs are required to verbally convey the disclaimer during a call. A few commenters noted that the first minute of the sales call is not the most effective place to present the TPMO disclaimer. These commenters agreed that conveying the disclaimer before benefits are discussed ensures beneficiaries understand the role and affiliation of the marketing organization before receiving substantive information that could influence decision-making. Additionally, some commenters noted that relaxing the existing requirement for the disclaimer to be conveyed within the first minute of the call is a common-sense change that would retain important beneficiary safeguards and reduce confusion while preserving disclosure objectives.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for supporting this proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         CMS received several comments disagreeing with the proposal to adjust the timing of when TPMOs are required to verbally convey the disclaimer during a call. A commenter expressed concerns that delaying the disclaimer would permit TPMOs to harvest personal information from callers who would not share their information if they knew the limits of the plans the TPMO offers. Others were concerned that beneficiaries would not have immediate awareness of the scope of the conversation they are having before being lured into any kind of discussion about plan choices, and that beneficiaries largely do not understand how MA plans' networks work, so it is essential to immediately provide the disclaimer. A commenter also noted that maintaining the current requirement would maintain transparency and consistency in MA plan marketing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the concerns raised by commenters. The Agency is committed to ensuring the protection of beneficiaries' personal data. However, CMS respectfully disagrees with the assertion that altering the requirements for when TPMOs verbally convey the disclaimer puts beneficiaries' personal information at risk. There are other data-focused beneficiary protections still in place to prevent the unauthorized sharing of beneficiary information, such as those found under §§ 422.2274(g)(4) and 423.2274(g)(4) that prohibit personal beneficiary data collected by TPMOs for marketing or enrolling a beneficiary into an MA or Part D plan to be shared with other TPMOs, unless prior express written consent is given by the beneficiary.
                    </P>
                    <P>CMS also disagrees that this change would diminish beneficiaries' understanding of the call's scope or impact transparency and consistency in MA plan marketing. As previously discussed in this preamble, CMS has determined that many calls typically begin with the TPMO obtaining basic demographic information from the beneficiary. As such, it is CMS' position that the change to the timing of the disclaimer will enhance the effectiveness of the disclaimer. The Agency also believes that conveying the disclaimer before a discussion of benefits occurs will promote clear communication with the beneficiary and mitigate beneficiary confusion. CMS does not anticipate that changing the timing of when the disclaimer is verbally conveyed will have a negative impact on the transparency and consistency of MA plan marketing.</P>
                    <P>
                        <E T="03">Comment:</E>
                         CMS received several comments about how the Agency 
                        <PRTPAGE P="17450"/>
                        should identify when a “discussion of benefits” occurs to mitigate any confusion over when the disclaimer should be read and to ensure consistency in interpretation. Commenters suggested that a “discussion of benefits” occurs when the specificity of benefits is being discussed with the intent to draw a beneficiary's attention to an MA or Part D plan or to influence a beneficiary's decision-making process, when discussing plan options, or whenever a TPMO representative begins to discuss unique benefits, premiums, or cost sharing of a particular MA or Part D plan. Another commenter urged CMS to align “discussion of benefits” with the current regulatory definition of marketing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these recommendations. As previously discussed in this preamble, CMS believes that discussing the specificity of a benefit with the intent to draw a beneficiary's attention to an MA or Part D plan(s), to influence a beneficiary's decision-making process when making an MA or Part D plan selection, or to influence a beneficiary's decision to stay enrolled in a plan, could represent a discussion of benefits, consistent with the marketing definition under §§ 422.2260 and 423.2260. This could include, for example, talking with a beneficiary about the benefits listed in a plan's Evidence of Coverage document, or how beneficiary out of pocket cost sharing might work given a plan's benefit structure and the beneficiary's previous health care experience or needs. Thus, the Agency agrees that a “discussion of benefits” can align with the definition of marketing in §§ 422.2260 and 423.2260. Additionally, the examples previously provided establish a framework that agents and brokers can use to judge when the disclaimer should be read. In addition, as this final rule is implemented, CMS will continue to gauge industry's need for more examples or other means of operational guidance for these requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         CMS received numerous comments from stakeholders who submitted similar, and in some cases identical, comments regarding the TPMO disclaimer. The commenters asserted that the TPMO disclaimer, as currently framed, forces independent agents to make statements that are untrue and confuses beneficiaries. The comments included that the disclaimer operates under the flawed assumption that insurance agents, particularly independent ones, do not or cannot represent all plans available in a given area. The commenters further stated that it is common for experienced independent agents, especially in less saturated markets or those committed to extensive certifications, to represent every single plan available to a beneficiary. These commenters further urged CMS to eliminate the entire TPMO disclaimer requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS disagrees with the commenters' assertion that the disclaimer requires them to make statements that are untrue or confusing to the beneficiary. The current disclaimer already addresses the commenters' concerns and provides disclaimer language for instances where the agent offers all plans in a service area. Additionally, the TPMO disclaimer is currently designed to ensure that agents provide beneficiaries information about the scope of plans that they represent, inform beneficiaries that there are a variety of plans in their service area to consider when picking a plan, and provide beneficiaries with additional resources for information. The modifications to the current requirements in this final rule are a practical step in refining the rules around the disclaimer to alleviate TPMO burden without a negative impact to the beneficiary. While the elimination of the TPMO disclaimer was not proposed, and hence this comment is out of scope, CMS appreciates these commenters' input and will take it under advisement.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         CMS received several comments strongly disagreeing with the proposal to remove SHIPs from the TPMO disclaimer. These commenters asserted that SHIPs are the only federally-funded source of independent, individual-level counseling available to Medicare beneficiaries and are a critical source of unbiased information for Medicare beneficiaries. Commenters also noted that 1-800-MEDICARE customer service representatives often refer to SHIPs because SHIPs have expertise in state programs, can meet with people in person, and provide a higher level of advocacy and assistance than 1-800-MEDICARE.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that SHIPs can be a source of unbiased information about plan choices. For the purpose of the of the TPMO disclaimer, CMS prefers that TPMOs direct beneficiaries to 1-800-MEDICARE. As previously mentioned in this preamble, this is based on the fact that 1-800-MEDICARE has representatives available 24/7 to assist beneficiaries, provides standardized training to its customer service representatives, is centrally monitored and controlled by CMS, which facilitates efficient and consistent information-sharing, and is a one-stop shop for all beneficiaries, regardless of the state in which they live. When appropriate, 1-800-MEDICARE representatives may refer beneficiaries to their local SHIP.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters acknowledged the complexity of the MA and Part D programs and suggested that, instead of removing the SHIPs from the TPMO disclaimer, SHIPs should be provided with additional resources. Other commenters noted that increased support for SHIPs, both from a staffing and training perspective, and receiving similar training to 1-800-MEDICARE staff, could help SHIP volunteers better navigate the MA and Part D programs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While out of scope to this provision, CMS appreciates these comments and will take them under advisement.
                    </P>
                    <P>After consideration of the public comments CMS received, CMS is finalizing as proposed revisions to the introductory text of §§ 422.2267(e)(41) and 423.2267(e)(41) and revisions to §§ 422.2267(e)(41)(ii) and 423.2267(e)(41)(ii).</P>
                    <HD SOURCE="HD2">E. Removing Rules on Time and Manner of Beneficiary Outreach (§§ 422.2264, 423.2264, 422.2274, and 423.2274)</HD>
                    <P>Section 1851(h) and (j) of the Act provides a structural framework for how Medicare Advantage (MA) organizations may market and communicate with beneficiaries and directs CMS to adopt standards related to prohibitions and limitations on marketing and communications activities. Section 1860D-1(b)(1)(B)(vi) of the Act directs that the Secretary use rules similar to and coordinated with the MA rules at section 1851(h) of the Act relating to approval of marketing material and application forms for Part D sponsors. Section 1860D-4(l) of the Act applies certain prohibitions under section 1851(h) of the Act to Part D sponsors in the same manner as such provisions apply to MA organizations (and agents, brokers, and other third parties representing MA organizations).</P>
                    <P>
                        CMS has adopted regulations related to marketing and communications by MA organizations and Part D sponsors in 42 CFR part 422, subpart V, and 42 CFR part 423, subpart V; these regulations include the specific standards and prohibitions in the statute as well as standards and prohibitions promulgated under the statutory authority granted to the Agency. Additionally, under 42 CFR 417.428, most marketing and communications requirements in subpart V of part 422 also apply to section 1876 cost plans. CMS has long provided further interpretation and sub-regulatory 
                        <PRTPAGE P="17451"/>
                        guidance for these regulations in the form of a manual titled, “Medicare Communications and Marketing Guidelines” (MCMG), previously known as “Medicare Marketing Guidelines.” Because this final rule is applicable to MA organizations, Part D sponsors, and cost plans, CMS refers to each of these regulated entities as a “plan.”
                    </P>
                    <P>In the Medicare and Medicaid Programs; Contract Year 2022 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicaid Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly Final Rule (hereinafter referred to as the January 2021 final rule), CMS codified guidance contained in the MCMG by integrating it with existing regulations. In the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly Final Rule (hereinafter referred to as the April 2023 final rule), CMS then finalized several changes to 42 CFR parts 422 and 423, subpart V, to strengthen beneficiary protections and improve MA and Part D marketing.</P>
                    <P>
                        In the Contract Year 2027 proposed rule, CMS proposed several changes to requirements regarding the time and manner of plans' outreach to beneficiaries. The primary proposals included three changes to §§ 422.2264(c) and 423.2264(c) to remove rules on the time and manner of beneficiary outreach. In addition, at §§ 422.2264(c)(3), 423.2264(c)(3), 422.2274(b)(3), 423.2274(b)(3), 422.2274(c)(9)(ii), and 423.2274(c)(9)(ii), CMS proposed a few other regulatory changes to add specificity and clarify policy. As CMS stated in the Contract Year 2027 proposed rule, in total, these proposals and clarifications were designed to improve the enrollment decision-making process by creating a more convenient, beneficiary-friendly outreach experience and to reduce the burden on beneficiaries, plans, and agents/brokers. Furthermore, CMS noted that these proposals align with the January 31, 2025, Executive Order 14192, “Unleashing Prosperity Through Deregulation” (hereinafter referred to as E.O. 14192).
                        <SU>49</SU>
                        <FTREF/>
                         E.O. 14192 describes the Administration's policy goals to promote prudent financial management and alleviate unnecessary regulatory burdens. Section 2 of E.O. 14192 states that it is the policy of the executive branch to be prudent and financially responsible in the expenditure of funds, from both public and private sources, and to alleviate unnecessary regulatory burdens placed on the American people. The changes CMS proposed are deregulatory and therefore support the Administration's policy goals.
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             
                            <E T="03">https://www.whitehouse.gov/presidential-actions/2025/01/unleashing-prosperity-through-deregulation/.</E>
                        </P>
                    </FTNT>
                    <P>CMS solicited comment on the proposed changes to §§ 422.2264(c)(3), 423.2264(c)(3), 422.2274(b)(3), 423.2274(b)(3), 422.2274(c)(9)(ii), and 423.2274(c)(9)(ii), including on the accuracy of CMS's assumptions regarding information collection requirements. CMS did not receive comment on the information collection requirements. CMS thanks commenters for their input on the proposed amendments and removal of rules regarding time and manner of beneficiary outreach. In the following sections, CMS describes each proposal, along with the comments received and CMS's corresponding responses.</P>
                    <HD SOURCE="HD3">1. Marketing Events Following Educational Events in Same Location</HD>
                    <P>In the January 2021 final rule, CMS codified guidance existing in the MCMG regarding events with beneficiaries. The finalized regulation text at §§ 422.2264(c)(2)(i) and 423.2264(c)(2)(i) required that if a marketing event directly followed an educational event, the beneficiary must be made aware of the change from an educational to a marketing event and be given the opportunity to leave prior to the marketing event beginning. In the April 2023 final rule, CMS modified §§ 422.2264(c)(2)(i) and 423.2264(c)(2)(i) to prohibit marketing events from taking place within 12 hours of an educational event in the same location (that is, the entire building or adjacent buildings). This prohibition was intended to protect beneficiaries from feeling pressured to stay for a marketing event after having attended an educational event. However, it also created additional barriers for plans or agents/brokers as well as beneficiaries who wished to discuss potential enrollment options with respect to specific plan products following an educational event.</P>
                    <P>As described in the April 2023 final rule, approximately half of the commenters opposed this provision. Some commenters stated that agents/brokers were not hurting seniors by holding a marketing event after an educational event, that this provision would result in beneficiaries being upset with agents/brokers for something that is out of their control, that it would not add any additional protection from marketing abuses, that it would degrade the consumer experience, and that the proposal was both heavy-handed and unworkable. Furthermore, some commenters were concerned that the number of educational events would decrease, resulting in beneficiaries being less informed regarding plan options overall and increasing the likelihood of a beneficiary enrolling in a plan that did not meet their health care needs. Other commenters said that the 12-hour delay was burdensome, specifically for dually eligible, low-income, disabled, and other underserved beneficiaries, who might experience transportation barriers or lack access to transportation. Such barriers factor in when beneficiaries are forced to travel to separate locations to attend an educational event and a separate marketing event 12 or more hours later, thus making access to information and resources in just one interaction a critical component. For greater detail on the different types of burden potential identified by commenters, see the April 2023 final rule.</P>
                    <P>
                        Following the April 2023 final rule, CMS has continued to receive stakeholder feedback reiterating concerns about the burden placed on both plans or agents/brokers and beneficiaries regarding the 12-hour delay requirement. While CMS considered similar hypothetical concerns prior to finalizing the April 2023 rule, the Agency is now reconsidering these requirements based on valuable input, such as the real-world experience cited in stakeholder feedback. After reevaluating these impacts, CMS is concerned that the requirements at §§ 422.2264(c)(2)(i) and 423.2264(c)(2)(i) do impose an unnecessary burden on beneficiaries and plans and agents/brokers. Furthermore, CMS believes, based on stakeholder input, that the 12-hour delay requirement between an educational event and a marketing event may also create an unnecessary barrier to accessing important MA and Part D information for beneficiaries, especially those who live far from the events or those who lack access to transportation. Moreover, based on a lack of evidence of a quantifiable protection to the beneficiary from the existing regulatory requirement, CMS believes that the beneficiary protections that CMS previously identified in the April 2023 final rule have not materialized. For example, in the April 2023 final rule, CMS explained that its concern about inappropriate pressure on beneficiaries (especially dually eligible individuals and other vulnerable groups) that may occur when marketing events occur 
                        <PRTPAGE P="17452"/>
                        directly after educational events outweighed some of the access and transportation concerns. However, CMS is now reconsidering these previous positions taken in 2023 because for vulnerable beneficiaries, especially those in SNPs, it is common to have caregivers or other friends or family members provide assistance in gathering information on plan options (and often ultimately make decisions on behalf of the beneficiary), thus, there is often a built-in layer of added protection from any potential undue pressure. CMS notes that there are also various beneficiary protections in place, including the possibility of providing special enrollment periods (SEPs) when appropriate, or, if warranted, processing a retrospective enrollment to place the beneficiary back into their prior coverage, if a beneficiary makes an adverse enrollment decision based on misrepresentation or otherwise non-compliant sales tactics. Thus, CMS proposed that plans and agents/brokers should be able to hold an educational event and a marketing event back-to-back and in the same location.
                    </P>
                    <P>For these reasons, in the Contract Year 2027 proposed rule, CMS proposed to eliminate the 12-hour delay requirement, so that a marketing event may take place directly following and in the same location as an educational event. This proposal aligned with section 1851(j)(1)(D)(ii) of the Act, which prohibits sales and marketing activities at educational events but does not require a specific timeframe between an educational event and a marketing event. CMS also noted that this proposal, permitting marketing events to follow educational events, provided there is an appropriate break, is consistent with the statutory requirement. CMS proposed to amend paragraph (c)(2)(i) in both §§ 422.2264 and 423.2264 to state that if a marketing event directly follows an educational event, plans and agents/brokers would be required to notify the beneficiary that the educational event is ending and a marketing event will begin shortly. CMS provided examples of appropriate beneficiary notification, such as a verbal announcement at the educational event or a clear and distinct notation on a written schedule of the day's event. In addition to the beneficiary notification, CMS proposed that plans and agents/brokers would also be required to give the beneficiary a sufficient opportunity to leave the educational event prior to the start of the marketing event. CMS noted that an example of “a sufficient opportunity to leave” appropriately given by the plan or agent/broker would be a brief restroom or snack break between the educational event and the marketing event. CMS stated in the Contract Year 2027 proposed rule that this deregulatory change is expected to significantly reduce burden and cost for plans and agents/brokers in terms of event planning, and it would also likely ease burden on beneficiaries when they attend an educational event and subsequently want to obtain more plan-specific information at a marketing event. CMS underscored that, by allowing both types of events to occur at the same location once beneficiaries are made aware of both events and given a sufficient opportunity to leave, beneficiaries would not need to return on a different day or to a different venue to attend a marketing event. As such, CMS expressed in the Contract Year 2027 proposed rule that this proposal would provide greater convenience for beneficiaries and enhance the beneficiary experience in shopping for a plan.</P>
                    <P>CMS received the following comments on this proposal, and CMS's response follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported eliminating the 12-hour delay between an educational event and a marketing event, viewing it as overburdensome and confusing. They noted that beneficiaries attending educational events often wanted immediate personalized guidance and that forcing them to wait disrupted natural inquiry flow, leading to disengagement or frustration. Commenters viewed the delay as serving no protective purpose when beneficiaries actively requested assistance. In addition, commenters emphasized that agents/brokers should be empowered to respond to beneficiary-initiated questions without fear of regulatory violation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the support for this proposal and agrees with commenters' sentiments regarding potential implications of the 12-hour delay on beneficiaries and agents/brokers.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters highlighted practical benefits of CMS permitting marketing events to follow educational events, noting that the change would reduce transportation burdens (especially for dually eligible individuals), allow multiple meetings in a single day, increase outreach efficiency, and better utilize limited staffing resources, which is particularly important for smaller plans serving geographically dispersed populations. Commenters also stated the change would reduce unnecessary delays and administrative burden while preserving beneficiary protections. The proposal was viewed as a practical, beneficiary-friendly improvement that promoted timely access to information, reduced confusion, and improved the beneficiary experience while maintaining appropriate safeguards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that there are many practical benefits to allowing marketing events to follow educational events, including those related to transportation and administrative burden relief, time saving, and efficiency. CMS also agrees that this proposal would help beneficiaries while also preserving safeguards.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the proposal would allow plans and agents/brokers to provide education followed by enrollment at the same event, enabling in-person discussion of unique situations. A commenter noted that the change would allow tailored outreach aligned with beneficiary preferences, enable quicker and more responsive communication, and result in better beneficiary experiences and improved health outcomes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' support for the promotion of in-person, tailored beneficiary communications that this provision invites. CMS also believes that the provision may improve beneficiaries' experiences and ultimately health outcomes in the long run.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Other commenters opposed eliminating the 12-hour delay, warning it would merge educational and marketing events into sales seminars that pressure beneficiaries into hasty decisions. Commenters claimed a brief restroom or snack break was inadequate separation between the two event types. These commenters described the waiting period as essential for beneficiaries to digest information, access SHIP resources, conduct research, discuss with families, and make informed choices. Commenters believed that without meaningful separation, the statutory prohibition against sales activities at educational events would become meaningless, particularly given the vulnerabilities of the Medicare-eligible population.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS disagrees with commenters that eliminating the 12-hour delay would result in beneficiary pressure. As discussed in the Contract Year 2027 proposed rule, CMS believes that beneficiaries' support from caregivers is a built-in layer of added protection from any potential undue pressure, coupled with other various beneficiary protections, such as potential SEPs, including retrospective enrollments, if warranted. CMS notes that the provision includes the 
                        <PRTPAGE P="17453"/>
                        important requirement that plans and agents/brokers notify the beneficiary that the educational event is ending and a marketing event will begin shortly. CMS disagrees with commenters and believes that a brief restroom or snack break is indeed an adequate separation between the two types of events. Furthermore, in response to the comment about the statutory prohibition against sales activities at educational events, CMS notes, as stated in the Contract Year 2027 proposed rule, that section 1851(j)(1)(D)(ii) of the Act does in fact prohibit sales and marketing activities at educational events but does not require a specific timeframe between an educational event and a marketing event.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In other comments opposing this provision, commenters cited extensive experiences with unwitting enrollments, including beneficiaries who did not consent, thought they were enrolling in dental/vision only, did not understand network limitations, or had dementia and were enrolled without family present. Commenters mentioned low-income individuals who were pushed into plans without adequate discussion. The commenters described plan marketing violations and suggested that, if finalized, the rule would foster problematic behaviors in an increasingly commission-based market.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands commenters' concerns but reiterates that beneficiaries are able to take advantage of certain important beneficiary protections such as potential SEPs, including retrospective enrollments, when appropriate, if a beneficiary makes an adverse enrollment decision based on misrepresentation or otherwise non-compliant sales tactics. However, CMS believes that such instances of plan marketing violations and negative beneficiary enrollment experiences that commenters describe are rare, as CMS does not often receive reports or complaints in this area. Additionally, CMS routinely monitors compliance with MA marketing rules and may take compliance action if CMS determines that a plan or agent/broker is out of compliance with these rules.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed the proposed changes could increase confusion and high-pressure interactions, especially for beneficiaries with complex medication needs, limited health literacy, cognitive impairment, or limited English proficiency. Commenters stated that relying on family presence or SEPs as safeguards is inadequate because caregivers may not help beneficiaries discern where education stops and marketing starts, and that no one is immune from Medicare system confusion. Commenters asserted that relying on SEPs after misleading enrollment was unacceptable because these remedies were exceedingly difficult to use, and many beneficiaries did not seek help until well after problems emerged (
                        <E T="03">e.g.,</E>
                         discovering out-of-network providers). Also, commenters stated that beneficiaries might not successfully obtain SEPs due to lack of knowledge about how to access them, leaving them without options once enrolled.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS respectfully disagrees. The various beneficiary protections mentioned have previously served as more than sufficient safeguards to potential beneficiary confusion and pressure during both educational and marketing events, as well as during other enrollment processes. This includes the possibility of CMS processing a retrospective enrollment if warranted. As noted previously, CMS routinely monitors compliance with MA marketing rules and may take compliance action if CMS determines that a plan or agent/broker is out of compliance with these rules, including in instances where plans or agents/brokers engage in high-pressure interactions with and possibly confuse vulnerable beneficiaries with complex medication needs, limited health literacy, cognitive impairment, or limited English proficiency.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the change could result in educational presentations being less complete and built solely to support subsequent sales activities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenter's concern but views this as a hypothetical scenario that is unlikely to occur. Specifically, CMS expects relevant safeguards—such as existing requirements for educational events—will protect beneficiaries from being exposed to partial educational presentations that are designed solely to support subsequent sales activities. For example, §§ 422.2264(c) and 423.2264(c) prohibit plans and agents/brokers from marketing specific plans or benefits and from conducting sales or marketing presentations at educational events. CMS also notes that plans and agents/brokers have the freedom to design educational presentations as they choose, provided that they remain in compliance with CMS's marketing and communication requirements at 42 CFR part 422, subpart V, and 42 CFR part 423, subpart V.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters believed the proposed changes would remove beneficiary protections without replacement, and that each time federal protections were removed, states had to navigate the new landscape or create their own rules. They asserted that state staff spent significant time addressing problematic plan growth rather than advancing integration, MA was described as “the wild west,” and these rules were necessary to prevent vulnerable populations from being pressured into unsuitable products.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for offering this information regarding the state perspective. However, CMS disagrees that the proposed changes would remove beneficiary protections without replacement; rather, CMS is simply amending the existing beneficiary protections. Furthermore, in response to the reference to states creating their own rules, CMS reminds all parties of the statutory and regulatory framework applicable to MA, and that standards established under federal law preempt state law, other than state licensing laws or state laws relating to plan solvency, with respect to MA plans. These federal standards include communications and marketing standards set forth in 42 CFR part 422, subpart V, and 42 CFR part 423, subpart V. Section 1856(b)(3) of the Act states the following: “Relation to state laws. The standards established under this part shall supersede any State law or regulation (other than State licensing laws or State laws relating to plan solvency) with respect to MA plans which are offered by MA organizations under this part.” In turn, CMS's regulation, under § 422.402, closely mirrors this statutory language regarding federal preemption. CMS does note that for D-SNPs, state Medicaid agencies may include communications and marketing requirements in state Medicaid agency contracts as long as the requirements do not conflict with federal requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters urged CMS to protect PACE enrollments from aggressive MA marketing that might not clearly communicate differences between MA plans and the PACE program, as PACE participants were particularly vulnerable.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While out of scope of the requirements in this final rule, CMS will take this into consideration when evaluating both MA and PACE marketing rules and beneficiary protection rules in the future.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asserted that plans, rather than beneficiaries, would benefit from the proposed change and took issue with CMS's reliance on undefined stakeholder input, the presence of others at events, and the availability of corrective measures to support the change.
                        <PRTPAGE P="17454"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As previously explained, CMS has received stakeholder input that the 12-hour delay requirement between an educational event and a marketing event makes it difficult for beneficiaries who live far from the events or who lack transportation to access important MA and Part D information. CMS agrees that this input raises legitimate concerns about access challenges. CMS reiterates its stance on the sufficiency of existing beneficiary protections in place and the likelihood of support from beneficiaries' family, friends, and caregivers during education, marketing, and enrollment experiences. CMS believes that eliminating the 12-hour delay between an educational event and a marketing event will foster a better, more convenient plan shopping experience for beneficiaries. For these and other reasons stated in the Contract Year 2027 proposed rule, CMS stands by its reasoning for this change.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported a tailored approach—supporting the change for dually eligible individuals but expressing concern that other MA beneficiaries could be pressured into real-time coverage decisions. Commenters also expressed concerns about potential “unintentional non-compliance.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for the idea, but unfortunately such a tailored approach is not feasible because educational and marketing events are attended by a wide range of beneficiaries, including both dually eligible and non-dually eligible individuals. CMS does not believe it would be practical for the 12-hour delay between events to be eliminated for some attendees and not others. CMS is unclear on what the commenter meant by “unintentional non-compliance.” CMS notes that plans are responsible for ensuring compliance with CMS regulations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended that if CMS proceeded with the proposal, it should replace timing guardrails with clear, enforceable standards preventing immediate transitions and ensuring clear beneficiary consent. They suggested, at minimum, there should be sufficient time (30-60 minutes) and space between events so individuals could affirmatively choose whether to attend the marketing event.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this input and believes that a brief restroom or snack break is a sufficient opportunity for all beneficiaries, including those with mobility concerns, to leave the facility if they wish prior to the beginning of a marketing event.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter recommended that if this proposal were finalized, CMS should provide a dedicated office to receive referrals from state departments and SHIP offices, take swift enforcement action, and share complaints with states to enable compliance with state licensing laws.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for these recommendations. If states or SHIP offices encounter any issues or have questions related to this regulation, they may contact CMS directly through already established channels, including the use of the Complaints Tracking Module and sharing of information as outlined in existing memorandums of understanding (MOUs) that CMS has with states.
                    </P>
                    <P>After considering all the comments received on allowing marketing events to directly follow educational events in the same location, CMS is finalizing the proposal to eliminate the 12-hour delay requirement, so that a marketing event may take place directly following and in the same location as an educational event, as long as plans and agents/brokers notify the beneficiary that the educational event is ending and a marketing event will begin shortly and also give the beneficiary a sufficient opportunity to leave the educational event prior to the start of the marketing event.</P>
                    <HD SOURCE="HD3">2. Timing of Personal Marketing Appointment After Scope of Appointment (SOA) Form Completion</HD>
                    <P>Sections 1851(j)(2)(A) and 1860D-4(l)(2) of the Act direct that the Secretary shall establish limitations with respect to the scope of any marketing appointment and that such limitation shall require advance agreement with a prospective enrollee on the scope of the marketing appointment and that documentation of such agreement must be done by the plan. In situations where the marketing appointment is in person, the statute further provides that such documentation shall be in writing. The advance agreement documentation is commonly referred to as the Scope of Appointment (SOA) form. The SOA requirement helps to ensure beneficiaries understand what types of plans will be discussed prior to meeting with a plan or an agent/broker.</P>
                    <P>Over the course of the past several years, CMS SOA policy has evolved as reflected in CMS's regulatory requirements. This is in part due to changes in the MA market over time, which has led to an evolving understanding of what measures may be appropriate to regulate for improper marketing activities and to ensure that beneficiaries are able to make informed decisions about their enrollment choices. CMS first codified the SOA statutory requirement at §§ 422.2268(g) and 423.2268(g) in the Medicare Program; Revisions to the Medicare Advantage and Prescription Drug Benefit Programs Interim Final Rule with Comment Period (hereinafter referred to as the September 2008 IFC) (73 FR 54226), prohibiting plans from marketing during a marketing appointment beyond the scope agreed upon by the beneficiary, and documented by the plan, prior to the appointment occurring. Aligning with the statute, CMS explained that the beneficiary must have the opportunity to agree to the range of choices that will be discussed, and that agreement would have to be documented. Then in the Medicare Program; Medicare Advantage and Prescription Drug Benefit Programs Final Rule (hereinafter referred to as the September 2011 final rule) (76 FR 54634), CMS modified §§ 422.2268(g) and 423.2268(g) by designating a specific timeframe standard for the SOA advance agreement—48 hours in advance of the marketing appointment, when practicable. This CMS interpretation was also memorialized in the MCMG at the time. In the January 2021 final rule, CMS made some structural changes to 42 CFR part 422, subpart V, and 42 CFR part 423, subpart V, removed §§ 422.2268 and 423.2268, and shifted the SOA rule to §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i). Also, in this January 2021 final rule (86 FR 5890), CMS removed the 48-hour SOA standard again, stating that prior to the personal marketing appointment beginning, the plan (or agent/broker, as applicable) must agree upon and record the SOA with the beneficiary(ies).</P>
                    <P>
                        In the April 2023 final rule, CMS reverted to the 48-hour SOA standard, prohibiting personal marketing appointments from taking place until after 48 hours have passed since the time the SOA was completed by the beneficiary. However, this change did not include the previously codified “when practicable” because CMS, at the time, believed this phrase nullified the purpose of the 48-hour timeframe given the various reasons why waiting 48 hours may not be practicable.
                        <FTREF/>
                        <SU>50</SU>
                          
                        <PRTPAGE P="17455"/>
                        Therefore, in the April 2023 final rule (88 FR 22336), CMS added the phrase “At least 48 hours” to §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i) to require such a timeframe prior to the personal marketing appointment for the SOA to be agreed upon and recorded with the beneficiary. CMS also finalized two exceptions to the 48-hour SOA rule—one for SOAs that are completed during the last four days of a valid election period for the beneficiary and the other for unscheduled in-person meetings (walk-ins) initiated by the beneficiary (see §§ 422.2264(c)(3)(i)(A)-(B) and 423.2264(c)(3)(i)(A)-(B)). These are the current policies for the 48-hour SOA rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             For more details, please refer to the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, Medicare Parts A, B, C, and D Overpayment Provisions of the Affordable Care Act and Programs of All-Inclusive Care for the Elderly; Health Information Technology Standards and Implementation Specifications Proposed Rule 
                            <PRTPAGE/>
                            (hereinafter referred to as the December 2022 proposed rule).
                        </P>
                    </FTNT>
                    <P>Similar to the reasoning for proposing to eliminating the 12-hour delay requirement at §§ 422.2264(c)(2)(i) and 423.2264(c)(2)(i), CMS believes that the strict 48-hour SOA requirement may create an unnecessary barrier to accessing important MA and Part D information for impacted beneficiaries, and also barriers for plans and agents/brokers distributing this information, without offering a quantifiable protection to the beneficiary. For example, after both the September 2011 final rule and the April 2023 final rule, CMS received numerous inquiries from plans and agents/brokers questioning the logistics of the 48-hour SOA rule and objecting to the rule's tendency to create obstacles to promoting beneficiaries' smooth, informed, and timely decision-making when faced with various enrollment options. The 48-hour delay may have a negative impact on a beneficiary's freedom to engage with a plan or an agent/broker on a schedule that works best for them. On the other hand, the 48-hour delay may require a beneficiary to dedicate more time than they wished to spend should they wish to engage with multiple plans or agents/brokers and need to wait 48 hours before engaging with them and deciding in which plan they wish to enroll.</P>
                    <P>Consequently, in the Contract Year 2027 proposed rule, CMS proposed to eliminate the 48-hour waiting period required between the SOA completion and a personal marketing appointment, as well as eliminate the two corresponding exceptions to the 48-hour SOA rule. CMS noted that under this proposal, plans and agents/brokers would no longer be required to wait 48 hours between obtaining an SOA and speaking with a beneficiary about plan products. CMS also stressed that beneficiaries would be able to learn about plan products in real time, rather than having to come back for a personal marketing appointment 48 hours later. CMS acknowledged in the Contract Year 2027 proposed rule that, if finalized, it would still require an advance agreement, as statutorily required, but without a specified timeframe, as beneficiaries would be able to fill out an SOA just prior to discussing plan products or may fill out an SOA for a future personal marketing appointment. For this proposed change, paragraph (c)(3)(i) in both §§ 422.2264 and 423.2264 would revert to its original language as finalized in the January 2021 final rule by removing the phrase “At least 48 hours” and the phrase “, except for:” and by removing the two exceptions listed at paragraphs (c)(3)(i)(A) and (B). CMS also proposed a minor technical correction in § 422.2264(c)(3)(i) to add the missing word “appointment” after “marketing.”</P>
                    <P>In the Contract Year 2027 proposed rule, CMS explained that eliminating the 48-hour SOA rule would benefit all parties, especially beneficiaries, by allowing for a discussion of plan products on the beneficiary's schedule. CMS also stated that, similar to the 12-hour delay requirement between an educational event and a marketing event, the 48-hour SOA rule potentially inhibits a beneficiary from receiving information. While the current requirement has an exception for in-person meetings (walk-ins) initiated by the beneficiary, CMS noted that it does not account for other interactions that may take place between the beneficiary and a plan or an agent/broker. In the Contract Year 2027 proposed rule, CMS provided the example of beneficiaries who live far away or those with transportation issues who sign an SOA with a plan or an agent/broker when attending a marketing event, who would be required to come back no less than 48 hours later to meet with that plan or agent/broker again.</P>
                    <P>CMS acknowledged that in the April 2023 final rule, CMS stated that the burden caused by the 48-hour SOA rule was outweighed by the potential benefit of providing beneficiaries, especially vulnerable beneficiaries, time to speak with caregivers and others who they may rely upon for help or advice or just provide the beneficiary additional time to consider their options. However, in the Contract Year 2027 proposed rule, CMS asserted that a different approach may be appropriate now for a similar reason as mentioned for the proposal to eliminate the 12-hour delay requirement. CMS stated that there is often a built-in layer of added protection from any potential undue pressure, as evidenced by the tendency for vulnerable beneficiaries to have other people help them with plan options and making decisions (for example, caregivers or authorized representatives), together with previously mentioned existing beneficiary protections if a beneficiary makes an adverse enrollment decision based on misrepresentation or otherwise non-compliant sales tactics. In the Contract Year 2027 proposed rule, CMS stated that the Agency is now reexamining the relative protection offered by these other factors and based on additional information that CMS has received about the relative benefit or burden of the 48-hour SOA rule. As described earlier, since the September 2011 final rule, and more recently, the April 2023 final rule, CMS has received numerous clarifying questions regarding the 48-hour timeframe, as well as stakeholder commentaries providing anecdotal and hypothetical concerns and reasons why the 48-hour SOA rule may be harmful to beneficiaries. Criticism regarding the potentially adverse effects on beneficiaries led CMS to further review the unintended consequences of the “cooling off” period. This led CMS to conclude that it may be appropriate for plans and agents/brokers to meet with the beneficiary or the beneficiary's representative sooner than 48 hours after the collection of the SOA form. In other cases, the plan or agent/broker may need to travel long distances, possibly hundreds of miles, to have a follow-up appointment based on the current 48-hour SOA rule, therefore, as stated in the Contract Year 2027 proposed rule, the proposal CMS put forth would also reduce the burden on plans and agents/brokers in addition to beneficiaries and their representatives.</P>
                    <P>Furthermore, CMS explained that by returning to the same regulatory language as in the January 2021 final rule (and similar language as in the September 2008 IFC)—which aligned with section 1851(j)(2)(A) of the Act—CMS is closely aligning with statute. CMS stated that the Agency believes this proposal to eliminate the 48-hour SOA rule is consistent with the statutory requirement at section 1851(j)(2)(A) of the Act that requires an advance agreement with a prospective enrollee, given the statute does not define the timeframe between the agreement and the marketing appointment with the plan or agent/broker.</P>
                    <P>
                        In conjunction with proposing to eliminate the 48-hour SOA rule, CMS also proposed a few additional associated regulation changes and 
                        <PRTPAGE P="17456"/>
                        clarified various SOA policies that would further bolster the precision of the remaining requirements should the Agency finalize the elimination of the 48-hour SOA rule. CMS has received questions from plans and agents/brokers regarding SOA policies, and so in the Contract Year 2027 proposed rule, CMS deemed these proposed regulation changes and policy clarifications as necessary and responsive to those questions. CMS requested that plans and agents/brokers review the following information carefully and provide feedback through the comment process. CMS also noted that, if this portion of the rule is finalized as proposed, the SOA policy clarifications contained herein will supersede any existing SOA guidance.
                    </P>
                    <P>First, CMS proposed to more clearly define what qualifies as a personal marketing appointment. The introductory language at §§ 422.2264(c)(3) and 423.2264(c)(3) currently states that personal marketing appointments are those appointments that are tailored to an individual or small group and that personal marketing appointments are not defined by the location. CMS proposed to clarify this regulatory definition by adding language to paragraph (c)(3) in both §§ 422.2264 and 423.2264 stating that personal marketing appointments are for purposes of discussing marketing topics, so that the proposed language reads as follows: “Personal marketing appointments are those appointments that are tailored to an individual or small group (for example, a married couple) for purposes of discussing marketing topics.”</P>
                    <P>In addition to this proposed change to the regulatory text, CMS also clarified in the Contract Year 2027 proposed rule that a small group, for purposes of an SOA, is a limited number of people, generally related or living in the same household. While the regulation provides an example of a married couple, CMS clarified that another example would be a parent and child who are both Medicare-eligible. CMS also explained that meetings with unrelated beneficiaries in a home or a public space, such as a book club at a house or a small group at a library, would require separate SOAs for each individual. In addition, CMS noted that §§ 422.2264(c)(3) and 423.2264(c)(3) state that personal marketing appointments are not defined by the location, meaning that such an appointment could take place in-person, telephonically, or virtually.</P>
                    <P>For more context on what a personal marketing appointment is, in the Contract Year 2027 proposed rule, CMS reminded plans and agents/brokers of the types of activities that may take place at such an appointment. Per §§ 422.2264(c)(3)(ii) and 423.2264(c)(3)(ii), plans and agents/brokers holding a personal marketing appointment may do any of the following: (1) provide marketing materials; (2) distribute and accept plan applications; (3) conduct marketing presentations; and (4) review the individual needs of the beneficiary including, but not limited to, health care needs and history, commonly used medications, and financial concerns.</P>
                    <P>Following the introductory definition of a personal marketing appointment, §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i) describe the current 48-hour SOA rule. CMS proposed to remove the word “scheduled” before “personal marketing appointment” at §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i), so that the proposed text would state that “prior to the personal marketing appointment,” the MA/Part D plan (or agent or broker, as applicable) must agree upon and record the Scope of Appointment with the beneficiary(ies). Likewise, CMS proposed to amend §§ 422.2274(b)(3) and 423.2274(b)(3) to more closely align with §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i) by replacing “prior to meeting with potential enrollees” with “prior to a personal marketing appointment.” CMS explained that these regulatory text changes were necessary to avoid ambiguity and prevent misinterpretation.</P>
                    <P>CMS stated in the Contract Year 2027 proposed rule that, if finalized as proposed, CMS's removal of the word “scheduled” would mean that an SOA would be required for all appointments that meet the definition of personal marketing appointments. As an example, CMS stated that an SOA would be required for plan/agent/broker-initiated outbound contact and for beneficiary-initiated inbound contact (including walk-ins, unscheduled calls and web-based chats, and web-based forms), as long as the contact is tailored to an individual or small group (as explained earlier in the proposal) for purposes of discussing marketing topics. To be clear, in the Contract Year 2027 proposed rule, CMS stressed that this means that an SOA would be required regardless of whether the personal marketing appointment was initiated by the plan, an agent/broker, or the beneficiary.</P>
                    <P>Other relevant requirements regarding the SOA are related to the method of delivery and where SOAs may and may not be accepted or collected. In order to align with the statutory requirements at section 1851(j)(2)(A) of the Act, CMS proposed to add that the SOA must be in writing for in-person personal marketing appointments by adding new regulatory text to §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i). CMS pointed out that this proposed change mirrors the statutory requirement which provides that if the marketing appointment is in person, then the SOA must be in writing. The proposed new regulatory text at §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i) would read, “The Scope of Appointment must be in writing for in-person personal marketing appointments.” Additionally, §§ 422.2274(c)(9)(ii) and 423.2274(c)(9)(ii) require agents/brokers to establish and maintain a system for confirming that agents/brokers appropriately complete SOA records for all marketing appointments (including telephonic and walk-in). Here, CMS proposed to add the word “personal” to §§ 422.2274(c)(9)(ii) and 423.2274(c)(9)(ii), so that it reads “personal marketing appointments” to ensure consistency with the other regulation sections previously mentioned. CMS also clarified that there are many ways that an agent/broker can complete an SOA record, for example, an audio or audio-visual recording or an electronic record would suffice as an SOA record for a personal marketing appointment that does not occur in person. In the Contract Year 2027 proposed rule, CMS listed instances in which SOAs may be accepted or collected, including: (1) plan activities in the health care setting (§§ 422.2266(e)(1) and 423.2266(e)(1)); (2) marketing events (§§ 422.2264(c)(2)(ii)(C) and 423.2264(c)(2)(ii)(C)); and (3) educational events—in the case where the proposed changes to §§ 422.2264(c)(1)(ii)(D) and 423.2264(c)(1)(ii)(D) would be finalized as proposed. CMS also listed instances in which SOAs may not be accepted or collected, including: (1) plan-initiated provider activities (§§ 422.2266(d)(1)(i) and 423.2266(d)(1)(i)); and (2) activities performed by social workers of an I-SNP (employees, agents, or contracted providers) (§ 422.2266(f)(3)).</P>
                    <P>
                        Regarding the content of the SOA, CMS clarified in the Contract Year 2027 proposed rule that, because §§ 422.2264(c)(3)(iii) and 423.2264(c)(3)(iii) require that plans and agents/brokers holding personal marketing appointments may not market any health care related product during an appointment beyond the scope agreed upon by the beneficiary and documented in an SOA, the SOA must therefore include, at a minimum, the 
                        <PRTPAGE P="17457"/>
                        type of product(s) to be discussed. CMS asserted that this aligns with section 1851(j)(2)(A) of the Act's reference to “the scope of the marketing appointment” and provided the following non-exhaustive list of examples of types of products to be discussed: MA plans, MA-PD plans, and standalone PDPs. As a best practice, in addition to the type of product(s) to be discussed, CMS encouraged plans to also include other pertinent information in the SOA, such as the date of the appointment and beneficiary contact information. In addition, CMS stated that on the SOA form, CMS permits plans to have check boxes or requests from the beneficiary regarding the type of product(s) to be discussed, for example, an internet site with an online form that requests a plan or an agent/broker to contact the beneficiary. As explained in the Contract Year 2027 proposed rule, provided this type of SOA form addresses the type of product(s) to be discussed, the plan or agent/broker may contact the beneficiary after the form has been filled out. CMS also clarified that Business Reply Cards (BRCs), voicemails, online forms, or other requests for information that include the type of product(s) to be discussed are, in effect, SOAs. CMS noted that the Agency currently does not provide a model document for SOAs.
                    </P>
                    <P>Lastly, in the Contract Year 2027 proposed rule, CMS reminded plans and agents/brokers of and clarified the requirements regarding the validity time period for an SOA. Pursuant to §§ 422.2264(c)(3)(iii)(A) and (B) and 423.2264(c)(3)(iii)(A) and (B), SOAs, BRCs, and other requests for additional information are valid for 12 months following the beneficiary's signature date or the date of the beneficiary's initial request for information. During this 12-month period, plans or agents/brokers may contact beneficiaries regarding the agreed upon scope of products documented in the SOA. CMS clarified that this does not grant permission to discuss products not previously agreed upon in the original SOA; any new product discussion outside the scope previously agreed upon would require a new SOA. This includes the same product for a different year (for example, if there is an SOA to discuss contract year 2026 plans, then a new SOA would be required to discuss contract year 2027 plans). Finally, CMS noted that the signed SOA can be used for multiple telephonic or in-person contacts or appointments. With that said, a plan or agent/broker must respect a beneficiary's request to no longer be contacted, even if that additional contact takes place within the 12-month window.</P>
                    <P>CMS received the following comments on this proposal, and CMS's response follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         The majority of commenters strongly supported eliminating the 48-hour waiting period between obtaining an SOA and conducting a personal marketing appointment. Commenters characterized the requirement as creating unnecessary delays, administrative burden, and paperwork without providing meaningful beneficiary protection. The waiting period was described as preventing timely assistance, particularly for beneficiaries with urgent needs or limited availability, and taking valuable time away from agents/brokers during the short open enrollment window. Commenters believed the 48-hour SOA rule created situations where beneficiaries were available, agents/brokers were available, and questions were time-sensitive, yet agents/brokers could not answer questions, provide quotes, or explain benefits for 48 hours. This was viewed as dismissive, confusing, bureaucratic, and distrust-inducing from the beneficiary perspective. Commenters noted that by the time 48 hours passed, many beneficiaries contacted someone else, enrolled immediately without the help of an agent/broker, or worked with individuals who did not follow the rules.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the strong support for this proposal and agrees with commenters' sentiments regarding potential implications of the 48-hour SOA rule on the interactions between beneficiaries and agents/brokers.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that the SOA often confused beneficiaries who were eager to understand their options and created unnecessary barriers to access. Commenters believed the cooling-off period assumption that beneficiaries were incapable of requesting information responsibly was both inaccurate and disrespectful. Eliminating the waiting period, commenters believed, would allow beneficiaries to engage with knowledgeable, trained advisors on a timeline that worked best for them and enable same-day appointments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands that the SOA could potentially be confusing to beneficiaries or present a barrier to access, and CMS appreciates the commenters' support for removing the 48-hour waiting period.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters characterized the 48-hour SOA requirement as a unique administrative burden imposed specifically on agents/brokers that did not apply to other enrollment channels. They stated that this disparity created an uneven playing field and introduced unnecessary friction into the enrollment process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges the commenters' implication that they are pleased with CMS's proposal to eliminate the 48-hour SOA requirement to give agents/brokers selling MA and Part D products a more even playing field as compared to agents/brokers selling other insurance products. CMS appreciates this observation and the support for this proposal expressed by commenters.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended eliminating the SOA requirement entirely and implementing a uniform post-enrollment rescission period applicable to all channels. They suggested that this would allow beneficiaries a designated timeframe after enrollment to review their decisions and change their minds if necessary, providing more robust and beneficiary-centric safeguards. If CMS retained the SOA requirement, commenters suggested allowing one universal SOA at first contact, permitting immediate discussion of benefits once completed, eliminating the 48-hour waiting period, and allowing SOAs to remain valid for ongoing discussions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS is not eliminating the SOA requirement entirely, as it is a statutory requirement under section 1851(j)(2)(A) of the Act, as well as out of the scope of CMS's proposal. The concept of a uniform post-enrollment recission period is also outside of the scope of what CMS proposed, but CMS may take this suggestion under consideration for future rulemaking. However, there are various existing beneficiary safeguards already in place, as previously mentioned, such as potential SEPs, including retrospective enrollments, if warranted. Finally, regarding the suggestion to allow one universal SOA at first contact, CMS is not in favor of this approach because requiring a new SOA for each appointment is an important beneficiary protection that ensures common agreement and clarity regarding the intended scope of each individual personal marketing appointment prior to the appointment taking place.
                    </P>
                    <P>
                        <E T="03">Comment: S</E>
                        everal commenters opposed eliminating the 48-hour waiting period and urged CMS to retain it. Commenters stated that the waiting period was designed to protect 
                        <PRTPAGE P="17458"/>
                        beneficiaries from high-pressure sales tactics and provide time for them to consult with family or caregivers before making enrollment decisions, and that removing this safeguard would increase the risk of rushed and uninformed enrollments, further undermining trust in the Medicare enrollment process. Some commenters believed the 48-hour cooling-off period already struck the appropriate balance by reducing the likelihood that beneficiaries would be subject to undue pressure and giving beneficiaries the opportunity to consider their options fully before making key decisions. Regarding other safeguards that CMS identified in the Contract Year 2027 proposed rule, such as potential availability of assistance from family and availability of SEPs in the event of certain marketing or enrollment improprieties, some commenters deemed these as inadequate on their own to ensure beneficiaries had the opportunity to engage in well-informed decision-making during enrollment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges commenters' concerns with eliminating the 48-hour waiting period before a beneficiary's personal marketing appointment. However, as stated in the Contract Year 2027 proposed rule, the 48-hour delay may have a negative impact on a beneficiary's freedom to engage with a plan or an agent/broker on a schedule that works best for them. In the time since the 48-hour delay went into effect, CMS has received multiple email inquiries from agents/brokers who have provided real-world examples of how this rule has had unintended negative consequences for the beneficiary. For example, if a beneficiary calls an agent to discuss MA plan options but does not immediately connect and instead leaves a message for the agent to call back, when the agent does call back, the agent must complete the SOA with the beneficiary, and then inform the beneficiary that they are unable to discuss MA plan options until 48 hours later. Another example is a beneficiary completes an SOA to discuss Part D options, meets with an agent, and during the conversation, the beneficiary asks about MA. In this scenario, the agent must complete a new SOA, but based on the current regulation, must then wait an additional 48 hours before the discussion about MA options can continue. In eliminating such a delay, CMS is enabling beneficiaries to learn about plan products in real time, rather than having to come back for a personal marketing appointment 48 hours later. Additionally, CMS reiterates its stance on the sufficiency of existing beneficiary protections in place and the likelihood of support from beneficiaries' family, friends, and caregivers during education, marketing, and enrollment experiences. CMS believes such safeguards offer appropriate beneficiary protection in the absence of the 48-hour SOA rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters believed that having no waiting period presented the possibility of agents/brokers pressuring beneficiaries to sign an SOA directly before an appointment. Commenters asserted that this would be wholly inappropriate in light of ongoing pressure tactics deployed in MA marketing. Commenters urged CMS to, at a minimum, prohibit the SOA from being signed simultaneously with the beginning of a personal marketing appointment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Any pressure tactics deployed during MA marketing events would be considered non-compliant and subject to potential compliance or enforcement action by CMS. Moreover, concerns about potential pressure tactics could be mitigated by existing beneficiary safeguards already in place, as previously mentioned, such as potential beneficiary support from caregivers and potential SEPs, including retrospective enrollments, if warranted. Such safeguards offer appropriate and sufficient beneficiary protection in the absence of the 48-hour SOA rule. Plans and agents/brokers will still be required to complete an advance agreement (an SOA form) as statutorily required, just without a specified timeframe, giving beneficiaries the flexibility to fill out an SOA just prior to discussing plan products or in advance of a future personal marketing appointment.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed that community health centers routinely assisted patients who later discovered high-cost sharing, restrictive networks, or prior authorization barriers, with no recourse until the next enrollment period. Thus, in this commenter's opinion, removing the 48-hour SOA safeguard would increase rushed and uninformed enrollments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for sharing these unfortunate beneficiary experiences at community health centers. CMS notes that beneficiaries are always encouraged to contact 1-800-MEDICARE if they believe that they have been misled or steered into a plan that does not meet their needs as a result of plans or agents/brokers engaging in misrepresentation or otherwise non-compliant sales tactics. As previously noted, CMS has the ability to grant SEPs, when warranted, including the potential for retrospective enrollments. Finally, CMS takes such beneficiary complaints seriously and will take compliance or enforcement actions as appropriate, including in such cases of rushed and uninformed enrollments per the commenter's concerns.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters encouraged CMS to prioritize protecting beneficiaries from abusive marketing practices over the interests of marketing and brokerage firms or MA plans. Commenters characterized the proposal as primarily benefiting agents/brokers rather than beneficiaries, despite CMS's stated rationale. Commenters stated that the proposed change seemed to remove guardrails previously put in place to protect beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees with commenters' sentiment that protecting beneficiaries from abusive marketing practices is of utmost importance. CMS assures commenters that the Agency is committed to ensuring existing important beneficiary protections remain in place. As previously mentioned, there are a range of such beneficiary protections, and CMS engages in active oversight of plans, holding plans accountable for complying with CMS rules and ensuring that their contracted agents/brokers also comply. In light of the beneficiary safeguards outlined here, CMS does not believe the 48-hour SOA guardrail is necessary. In instances of beneficiary harm, CMS will take compliance or enforcement actions as appropriate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters supported eliminating the 48-hour waiting period after signing an SOA but emphasized it was critical that CMS maintain strong structural safeguards. For example, commenters believed that SOAs must still be required before any personal marketing discussion, clear definitions around what constituted a personal marketing appointment were helpful, and consistency across guidance was essential. Commenters also noted that simplification was beneficial, but any relaxation of oversight would inevitably be exploited by bad actors. Commenters recommended that CMS should streamline the process but not weaken the protections that kept beneficiaries safe. While not opposed to administrative simplification and finding the right ways to safeguard and protect beneficiaries in a competitive landscape, commenters stated that they would have liked to see new or different proposals rather than simply removing existing protections.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         SOAs are still required before personal marketing appointments. CMS's removal of the 
                        <PRTPAGE P="17459"/>
                        word “scheduled” means that an SOA will be required for all appointments that meet the definition of personal marketing appointments. As an example, an SOA will be required for plan/agent/broker-initiated outbound contact and for beneficiary-initiated inbound contact (including walk-ins, unscheduled calls and web-based chats, and web-based forms), as long as the contact is tailored to an individual or small group for purposes of discussing marketing topics. To be clear, this means that an SOA is required regardless of whether the personal marketing appointment is initiated by the plan, an agent/broker, or the beneficiary. CMS thanks commenters for their praise of the clear definition, simplification, and streamlining the process. CMS also agrees on the importance of consistency across guidance, oversight, and beneficiary protections, as stated previously. Regarding the recommendation for new or different proposals, CMS will consider new ideas for future rulemaking in this area.
                    </P>
                    <P>After considering all the comments received on the timing of a personal marketing appointment after SOA completion, CMS is finalizing the proposal to eliminate the 48-hour waiting period required between the SOA completion and a personal marketing appointment, as well as eliminating the two corresponding exceptions to the 48-hour SOA rule.</P>
                    <HD SOURCE="HD3">3. Scope of Appointment (SOA) Forms at Educational Events</HD>
                    <P>In the January 2021 final rule, at §§ 422.2264(c)(1)(ii)(E) and 423.2264(c)(1)(ii)(E), CMS codified rules permitting plans and agents/brokers holding or participating in educational events with beneficiaries to obtain beneficiary contact information, including SOA forms, at educational events. In the April 2023 final rule, at §§ 422.2264(c)(1)(ii)(D) and 423.2264(c)(1)(ii)(D), CMS finalized rules that revised these regulations by prohibiting plans and agents/brokers from making available and receiving SOA forms from beneficiaries at educational events (other forms of beneficiary contact information, including BRCs, were still permitted). This is the current policy regarding SOA forms at educational events.</P>
                    <P>In the Contract Year 2027 proposed rule, CMS proposed to rescind these requirements as finalized in the April 2023 final rule and revert to the language established in the January 2021 final rule, to permit plans and agents/brokers to obtain SOA forms at educational events. Although section 1851(j)(1)(D)(ii) of the Act prohibits sales and marketing activities from occurring at educational events, the statute does not prohibit the collection of SOA forms at educational events. The collection of an SOA form is not a sales or marketing activity but is the making of an agreement regarding what type of product(s) will be discussed in advance of a personal marketing appointment between the beneficiary and the plan or agent/broker. As CMS noted in the Contract Year 2027 proposed rule, by permitting plans and agents/brokers to obtain SOA forms at educational events, the burden on beneficiaries, plans, and agents/brokers would be reduced, and parties would be allowed to conveniently schedule personal marketing appointments to discuss plan options in the future, instead of having to wait until after the educational event ends to schedule an appointment. CMS also pointed out that if plans and agents/brokers are allowed to collect SOAs at educational events, then it decreases the likelihood that beneficiaries might face undue burden and the potential challenge of reconnecting with a plan or agent/broker or traveling back to a venue to locate a plan or agent/broker at the conclusion of an educational event.</P>
                    <P>In the Contract Year 2027 proposed rule, CMS acknowledged that this proposal reflects a change in the Agency's position as described in the April 2023 final rule where CMS most recently adopted the ban on collecting SOA forms at educational events. For example, as part of its previous reasoning, CMS stated that it was concerned that beneficiaries may feel uncomfortable refusing to fill out an SOA form, or that they may feel obligated to provide this information in exchange for attending an educational event. Upon reconsideration, in the Contract Year 2027 proposed rule, CMS recognized that these concerns regarding beneficiary pressure appear to be outweighed by the importance of maximizing beneficiary access to information on available plan options, which could be accomplished by allowing the collection of SOA forms at educational events. In addition, as previously mentioned, CMS highlighted that there are also beneficiary protections in place should a beneficiary make an adverse enrollment decision based on misrepresentation or otherwise non-compliant sales tactics.</P>
                    <P>Thus, CMS proposed to modify §§ 422.2264(c)(1)(ii)(D) and 423.2264(c)(1)(ii)(D) to permit plans and agents/brokers holding or participating in educational events with beneficiaries to make available and receive SOA forms at those same educational events. Specifically, at paragraph (c)(1)(ii)(D) in both §§ 422.2264 and 423.2264, CMS proposed to replace the phrase “Cards, but not including Scope” with the phrase “Cards and Scope” so that it reads “including Business Reply Cards and Scope of Appointment forms.” CMS noted that the remaining distinctions and inherent beneficiary protections between educational events as required under §§ 422.2264(c)(1) and 423.2264(c)(1) and marketing or sales events as required under §§ 422.2264(c)(2) and 423.2264(c)(2) remain.</P>
                    <P>CMS received the following comments on this proposal, and CMS's response follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported CMS's proposal to allow the collection of SOA forms at educational events. They noted that current restrictions create unnecessary barriers preventing beneficiaries from receiving timely assistance, as beneficiaries often attend these events seeking help understanding how information applies to their situations and requesting next steps. Commenters believed the change would improve the beneficiary experience by reducing confusion, improving access to guidance, alleviating transportation burdens, streamlining processes, enabling quicker and more responsive communication, and providing greater flexibility for decision-making at convenient times.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the support for this proposal and agrees with commenters' sentiments regarding the benefits, including improving the beneficiary experience and communication, alleviating transportation burdens, and providing flexibility.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters also highlighted that the change would enhance workflow efficiency for plans and agents/brokers, modernize Medicare outreach rules, reduce administrative burden, lower costs, and improve resource allocation. Commenters characterized the change as practical, consumer-friendly, and balanced, stating it would support informed decision-making while preserving beneficiary protections.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that this change will result in administrative efficiencies, reduce burden, and result in practical improvements to the beneficiary decision-making process.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters opposed CMS's proposal, emphasizing that existing rules protect vulnerable populations from pressure tactics and inappropriate products. They expressed concerns that the change would increase 
                        <PRTPAGE P="17460"/>
                        confusion, high-pressure interactions, and misleading encounters during plan selection, especially for beneficiaries with complex medication needs, limited health literacy, cognitive impairment, limited English proficiency, or those relying on local counseling resources.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the Contract Year 2027 proposed rule, these concerns regarding beneficiary pressure appear to be outweighed by the importance of maximizing timely beneficiary access to information on available plan options, which could be accomplished by allowing the collection of SOA forms at educational events. In addition, as previously mentioned, there are also beneficiary protections in place should a beneficiary make an adverse enrollment decision based on misrepresentation or otherwise non-compliant sales tactics.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters questioned characterizing SOA collection as educational rather than as a marketing activity, noting that procuring a signature on an SOA form relates to a sales appointment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the Contract Year 2027 proposed rule, CMS reiterates that although section 1851(j)(1)(D)(ii) of the Act prohibits sales and marketing activities from occurring at educational events, the statute does not prohibit the collection of SOA forms at educational events. The collection of an SOA form is not a sales or marketing activity because it does not meet the definition of marketing at §§ 422.2260 and 423.2260, which requires the activity to meet specific standards for intent and content. Rather, the collection of an SOA form is simply the making of an agreement regarding what type of product(s) will be discussed in advance of a personal marketing appointment between the beneficiary and the plan or agent/broker.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters asserted that when federal protections are removed, states must either navigate the new landscape or create their own rules, and states lose contractor attention to beneficiary protection. Some commenters urged CMS to withdraw the proposal, establish a dedicated office to receive referrals from state insurance departments and SHIP offices, take swift enforcement action against violations, share complaints with state insurance departments, and retain existing standards for beneficiary outreach.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for these recommendations. If states or SHIP offices encounter any issues or have questions related to this regulation, they may contact CMS directly through already established channels, including the use of the Complaints Tracking Module and sharing of information as outlined in existing MOUs that CMS has with states.
                    </P>
                    <P>As to the comment that states must create their own rules, CMS reminds all parties of the statutory and regulatory framework applicable to MA, and that standards established under federal law preempt state law, other than state licensing laws or state laws relating to plan solvency, with respect to MA plans. These federal standards include communications and marketing standards set forth in 42 CFR part 422, subpart V, and 42 CFR part 423, subpart V. Section 1856(b)(3) of the Act states the following: “Relation to state laws. The standards established under this part shall supersede any State law or regulation (other than State licensing laws or State laws relating to plan solvency) with respect to MA plans which are offered by MA organizations under this part.” In turn, CMS's regulation, under § 422.402, closely mirrors this statutory language regarding federal preemption.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested clarity regarding compliant educational environments for SOA collection, “standardized scripts,” clear guidance, and guardrails to prevent beneficiary confusion and promote industry consistency.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Compliant educational environments for SOA collection include any educational events that meet the requirements outlined at § 422.2264(c)(1). CMS is unsure what commenters mean by “standardized scripts,” however, CMS notes that the Agency currently does not provide a model document for SOAs, nor any SOA scripts. CMS will consider the need for any sub-regulatory guidance regarding the finalized policy.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters also noted the importance of ongoing oversight and evaluation to ensure changes meaningfully advance beneficiary understanding and trust without unintended consequences and emphasized ensuring discussions are clear about plan benefit offerings. Commenters commended CMS for recognizing the evolving marketing and communications landscape and encouraged the Agency to work proactively to empower beneficiaries to make informed choices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated previously, CMS engages in active oversight and evaluation of plans and their contracted agents/brokers. CMS agrees with commenters that beneficiary understanding and trust are important. CMS also appreciates commenters' commending the Agency's recognition of the evolving MA landscape and proactive work to help beneficiaries. CMS remains committed to improving MA marketing and communications policies.
                    </P>
                    <P>After considering all the comments received on allowing the SOA at educational events, CMS is finalizing the proposal to permit plans and agents/brokers holding or participating in educational events with beneficiaries to make available and receive SOA forms at those same educational events.</P>
                    <HD SOURCE="HD3">4. Summary of Regulatory Changes</HD>
                    <P>In summary, in the Contract Year 2027 proposed rule, CMS proposed to modify §§ 422.2264(c) and 423.2264(c) to improve rules regarding beneficiary outreach and §§ 422.2274(b)(3), 423.2274(b)(3), 422.2274(c)(9)(ii), and 423.2274(c)(9)(ii) to add specificity and clarify policy in conjunction with the primary proposals at §§ 422.2264(c) and 423.2264(c). These primary proposals included: (1) allowing a marketing event to directly follow an educational event in the same location (provided there is appropriate beneficiary notification and opportunity to leave); (2) allowing a personal marketing appointment to occur at any point following completion of an SOA form; and (3) allowing the SOA form to be collected from beneficiaries at educational events.</P>
                    <P>
                        CMS received a range of comments pertaining to these proposals, the majority of which reflected support for the regulations. After considering the comments received and for the reasons outlined in the Contract Year 2027 proposed rule and in responses to comments, CMS is finalizing all provisions under 
                        <E T="03">Removing Rules on Time and Manner of Beneficiary Outreach</E>
                         as proposed. As finalized, these regulatory changes will remove current rules on the time and manner of beneficiary outreach, reduce burden on beneficiaries, plans, and agents/brokers, foster a convenient, beneficiary-friendly experience in the enrollment decision-making process, and ensure consistency and clarity in the regulatory text.
                    </P>
                    <HD SOURCE="HD2">F. Relaxing the Restrictions on Language in Advertising (§§ 422.2262(a)(1)(i), 422.2262(a)(1)(ii), 423.2262(a)(1)(i), and 423.2262(a)(1)(ii))</HD>
                    <P>
                        In the Medicare and Medicaid Program; Contract Year 2022 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicaid Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly final rule (86 FR 5864), hereinafter referred to as the January 2021 final rule, CMS codified 
                        <PRTPAGE P="17461"/>
                        42 CFR 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii), which prohibited MA organizations and Part D sponsors from making unsubstantiated statements, except when used in logos or taglines. Prior to the January 2021 final rule, this requirement was in the Medicare Communications and Marketing Guidelines (MCMG). In the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (88 FR 22120), hereinafter referred to as the April 2023 final rule, CMS updated §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) to prohibit MA organizations and Part D sponsors from using superlatives, unless sources of documentation or data supportive of the superlative is also referenced in the marketing or communications material where the superlative is being used. In the April 2023 final rule, CMS asserted that a beneficiary may have no knowledge of how the superlative is determined, which may mislead the beneficiary into believing a statement that is not accurate. At the time, CMS noted that providing current, reliable, and valid data as the basis for superlatives is critical for beneficiaries to review the data themselves (88 FR 22238).
                    </P>
                    <P>When CMS first codified §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) in the January 2021 final rule, CMS explained that the policies being codified were not new to MA organizations and Part D sponsors as they were already included in the MCMG, on which the industry heavily relied at that time (86 FR 5981). In the Contract Year 2027 proposed rule, CMS explained that, after years of implementation and oversight, including one revision to the requirement, the current restrictions regarding use of superlatives at §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) were unnecessary as, per §§ 422.2262 and 423.2262, MA organizations and Part D sponsors are already broadly prohibited from providing beneficiaries marketing and communications materials that are misleading, confusing, or materially inaccurate (90 FR 54956). Although CMS proposed to remove the prohibition on the use of superlatives, MA organizations and Part D sponsors would still be required to ensure that all statements, including superlatives, included in marketing and communications materials do not mislead, confuse, or provide materially inaccurate information to current or potential beneficiaries. CMS noted that the Agency would continue to review materials as described at §§ 422.2261 and 423.2261, and may request data, reports, or other documentation that supports the MA organization or Part D sponsor's statements in these materials either as a part of the formal review process or based on beneficiary complaints after the materials are actively being used (90 FR 54956). CMS also explained that it would continue to encourage MA organizations and Part D sponsors to make available to beneficiaries and the public data, reports, or other documentation that supports the superlative to promote informed enrollment decisions (90 FR 54956).</P>
                    <P>As described in the Contract Year 2027 proposed rule, sections 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) were intended to strengthen protections for beneficiaries to ensure they had access to all necessary information needed to make an informed enrollment decision (90 FR 54956). However, because §§ 422.2262 and 423.2262 already broadly prohibit misleading, confusing, and inaccurate marketing and communications materials, CMS believes that removing §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) will not affect the existing beneficiary protections, which will still be in effect, but will reduce the administrative burden for all parties. CMS also explained that, although removing §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) does not remove the prohibition on providing misleading, confusing, or materially inaccurate information to beneficiaries, it does remove the requirement for MA organizations and Part D sponsors to reference supporting documentation or data directly in the material (90 FR 54957). CMS noted, however, that if this proposed change to CMS's regulations was finalized, MA organizations and Part D sponsors could still choose to make data available to beneficiaries as they determine appropriate, which may reduce the administrative burden (90 FR 54957).</P>
                    <P>CMS stated it would continue to review applicable materials to ensure they do not provide misleading, confusing, or materially inaccurate information to beneficiaries. To aid CMS in determining if a material is misleading, confusing, or materially inaccurate; in some instances, it may expedite the review process if the MA organization or Part D sponsor provides supporting documentation when submitting marketing materials that include the use of superlatives. Moreover, when CMS is investigating a complaint regarding a misleading, confusing, or materially inaccurate material, CMS may request the plan provide documentation that supports a superlative used, per the Agency's oversight authority at §§ 422.504(f)(2) and 423.505(f)(2).</P>
                    <P>In the Contract Year 2027 proposed rule, CMS provided examples of quantifiable superlatives that would be acceptable if this provision was finalized, such as “highest rated providers in Chester County,” “largest provider network in Florida,” or “highest rated plan in Virginia” (90 FR 54957). Further, CMS noted that MA organizations and Part D sponsors would need to be able to factually support such superlatives through data, surveys, studies, or other type of information, and when requested, provide that information to CMS (90 FR 54957). In addition, when including superlatives based on older data, to ensure that they are not misleading or confusing, MA organizations and Part D sponsors should indicate the year or in some way show the statement is based on data older than the current or prior contract year. CMS explained that the use of a superlative such as “The most popular Medicare Prescription Drug plan in Montgomery County in 2023” would be acceptable (90 FR 54957). Conversely, CMS noted that the Agency would generally find the same statement to be misleading if the date was missing (90 FR 54957).</P>
                    <P>CMS recognized that not all superlatives can be quantified or reasonably measured. For example, the use of superlatives such as “our plan cares about you the most” and “we have the most dedicated providers in our network” (90 FR 54957). CMS explained that both examples would be permissible, and CMS would not expect MA organizations or Part sponsors to provide supporting documentation as a part of submission, nor would the Agency request such information as a part of a complaint investigation (90 FR 54957).</P>
                    <P>
                        Consistent with Executive Order 14267,
                        <SU>51</SU>
                        <FTREF/>
                         Reducing Anti-Competitive Regulatory Barriers, issued on April 9, 2025, CMS believes that removing the prohibition on the use of superlatives and underscoring the continued requirement of not misleading, confusing, or providing inaccurate information to beneficiaries will likely promote competition as this revision provides more opportunities for MA 
                        <PRTPAGE P="17462"/>
                        organizations and Part D sponsors to innovate while simultaneously protecting beneficiaries' access to accurate materials to help with their enrollment decisions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/04/15/2025-06463/reducing-anti-competitive-regulatory-barriers</E>
                            .
                        </P>
                    </FTNT>
                    <P>For the reasons discussed, CMS proposed to delete current paragraphs at §§ 422.2262(a)(1)(ii) and 423.2262(a)(1)(ii) in their entirety to remove the prohibition of using superlatives in marketing and communications materials without providing supporting documentation. With this revision, CMS explained that the Agency would renumber current paragraphs §§ 422.2262(a)(1)(iii)-(xix) and 423.2262(a)(1)(iii)-(xviii) (90 FR 54957).</P>
                    <P>
                        Consistent with Executive Order 14192,
                        <SU>52</SU>
                        <FTREF/>
                         Unleashing Prosperity Through Deregulation, issued on January 31, 2025, CMS also proposed deleting the current paragraphs at §§ 422.2262(a)(1)(i) and 423.2262(a)(1)(i), which reiterated the prohibition on MA organizations and Part D sponsors providing misleading and inaccurate information to beneficiaries (90 FR 54957). This is a technical change that would remove the duplication of §§ 422.2262 and 423.2262, which already require MA organizations and Part D sponsors to not provide misleading, confusing, or materially inaccurate information to current and potential beneficiaries. CMS solicited comments on this proposal and appreciates stakeholders' input on the proposed changes. The Agency received the following comments and provided responses as follows.
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/02/06/2025-02345/unleashing-prosperity-through-deregulation</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed support for this proposal. They stated that the marketing landscape is currently so restrictive that the actual benefits of plans are often unable to be effectively and clearly communicated to beneficiaries, which can be harmful.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters urged CMS to reconsider or revise this proposal as they believed it may result in increased complaints, and a few added that the Agency may not have the bandwidth to adequately oversee all those complaints. Many expressed that this proposal would allow for exaggerated, subjective, and misleading information that beneficiaries may not be able to verify themselves, which the industry has previously experienced. Some commenters underscored examples of past beneficiary complaints related to marketing, including several that highlighted the current substantial marketing of supplemental benefits, which already creates frequent beneficiary confusion. Some commenters requested additional guidance on superlatives that CMS would consider permissible.
                    </P>
                    <P>Another commenter suggested that CMS maintain the requirement to include supporting documentation for a material with a superlative but modify it to allow exceptions for media formats with limited time and space. Another suggested that CMS adopt limitations with this proposal, such as prohibiting the use of superlatives when marketing materials describe benefits or prices of a plan.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the feedback on this proposal and acknowledges the commenters' concerns and suggestions. However, CMS maintains that the existing marketing and communications requirements at §§ 422.2262 and 423.2262 uphold beneficiary protections against misleading, confusing, and inaccurate information. CMS will continue oversight of marketing materials, as statutorily required, and will adjust resources accordingly if there is an increase in the volume of complaints. As such, the Agency will consider the use of superlatives and may request supporting documentation when conducting marketing material reviews or investigating beneficiary complaints.
                    </P>
                    <P>CMS acknowledges that some supplemental benefits can be complex and challenging for beneficiaries to understand. CMS expects the majority of superlatives that mention benefits, including supplemental benefits, to be quantifiable, as they can be reasonably measured. To offer some examples of superlatives about supplemental benefits, CMS would consider “we have the best supplemental benefits in Texas” to be misleading and confusing as the “best” supplemental benefits are entirely subjective to the health needs of each beneficiary. However, when describing mandatory supplemental benefits as, “we have the most comprehensive dental benefits in Michigan” and “we offer the cheapest over the counter benefits in Beaverhead County,” CMS would not consider those misleading, confusing, or materially inaccurate, provided “most comprehensive” and “cheapest” can be factually supported through data, surveys, studies, or other types of information, and when requested, the plan can provide that information to CMS.</P>
                    <P>Moreover, during a review of a material that uses a superlative, whether it be a routine prospective review or a retrospective review in response to a complaint, CMS will focus on the use of the superlative in tandem with other regulatory requirements to determine if the overall material is misleading, confusing, or inaccurate. For example, if a material markets an optional supplemental benefit by saying, “we offer the most rides to medical appointments in Oregon,” CMS would consider the use of the superlative “most” acceptable provided it can be factually supported with data, but would consider the statement in its entirety misleading and confusing because it does not include information informing the beneficiary that they must opt into the optional benefit to access it, such as “. . . for those who elect our optional transportation benefit.” That is, CMS would still consider a marketing material misleading, confusing, or inaccurate unless the statement clearly references that the beneficiary must pay for, elect, or opt in to the optional benefit mentioned. Additionally, for superlatives focused on special supplemental benefits for the chronically ill (SSBCI), for example, CMS would consider “we offer the most meal deliveries in Massachusetts for those who qualify,” to not be misleading, confusing, or inaccurate provided the use of the superlative “most” can be factually supported and the statement clarifies that a beneficiary must qualify for the special supplemental benefit. As a reminder of an additional beneficiary protection, if a marketing material includes any information or statements about SSBCI, that material must include the SSBCI disclaimer as required at § 422.2267(e)(34).</P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters urged CMS to continue or increase oversight and monitoring efforts to ensure beneficiaries are protected from misleading, confusing, and inaccurate information. Proactive oversight recommendations included issuing significant civil money penalties or temporary suspension of marketing for repeated non-compliance, requiring correction and re-education campaigns to affected beneficiaries. Another commenter requested clarification on how this proposal will be enforced.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS reiterates that the Agency will continue to conduct oversight and monitoring of marketing and communications materials to ensure beneficiaries receive accurate information. In addition, beneficiaries or their caregiver can report misleading marketing to 1-800-MEDICARE. As 
                        <PRTPAGE P="17463"/>
                        noted previously, when investigating a marketing or communications material for accusations of the material being misleading, confusing, or materially inaccurate, such as from a complaint reported to 1-800-MEDICARE, if the material includes the use of superlatives, CMS may request supporting documentation from MA organizations and Part D sponsors per the Agency's oversight authority. Also, CMS reminds MA organizations and Part D sponsors to maintain adequate oversight of entities marketing on their behalf as they are ultimately responsible for ensuring their first tier, downstream, and related entities, as well as TPMOs, comply with CMS's requirements, per §§  422.504(i), 423.505(i), 422.2274(g)(1) and 423.2274(g)(1).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted that this proposal will not responsibly increase competition and will only lead to greater beneficiary confusion, with a commenter stating that beneficiaries will no longer be able to easily verify the recency of the supporting data.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks these commenters for sharing their concerns. CMS disagrees that this rule will create confusion for beneficiaries because MA organizations will continue to be prohibited from providing misleading, confusing, or inaccurate information in marketing and communications materials. As described previously, if a superlative is based on supporting documentation that uses data from before the current or prior contract year, the statement should directly refer to the relevant contract year to not be considered misleading, confusing, or materially inaccurate.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that this proposal will not reduce administrative burden, with some stating that it will shift the burden away from plans and onto beneficiaries, with another commenter stating that this signals CMS's intent to neglect its oversight of marketing. Another commenter remarked that this proposal may result in higher operational costs, yet a different commenter stated that this proposal will be especially beneficial for small plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS respectfully disagrees that this provision will shift administrative burden onto beneficiaries, nor does this proposal impede CMS's oversight of marketing. MA organizations and Part D sponsors will still remain responsible for complying with the robust beneficiary protections that remain at §§  422.2262 and 423.2262. This includes that MA organizations and Part D sponsors are still required to ensure their materials do not include misleading, confusing or inaccurate information and the Agency will continue oversight of all marketing and communication materials for compliance with these requirements. In addition, CMS reiterates here that MA organizations and Part D sponsors remain ultimately responsible for entities marketing on their behalf and should maintain adequate oversight of said entities. While a quantifiable superlative must be able to be substantiated by supporting documentation, CMS reiterates that this provision could reduce administrative burden, depending on plans' internal processes, as the supporting documentation must no longer be provided directly in the material. The Agency appreciates the feedback that this provision may be especially beneficial for small MA organizations and Part D sponsors that may have less administrative capacity.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter stated that this proposal might negatively impact Make America Healthy Again (MAHA) priorities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Without any examples of how or why, CMS does not see how this proposal negatively impacts MAHA priorities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asked CMS to specify what types of supporting documentation would be acceptable for substantiating superlative statements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS has similar expectations for supporting documentation as the Agency did previously. CMS expects supporting documentation data to reflect data, reports, studies, or other documentation that applies to the current year. If the supporting documentation includes data that is not from the current or prior contract year, as described previously, it would be permissible if the older contract year is referenced in the superlative. In the Contract Year 2027 proposed rule, CMS provided examples of permissible superlatives supported by data from prior contract years, which CMS will include in the Agency's review of marketing materials and requests for supporting documentation when necessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter wrote that CMS should allow descriptive language such as superlatives and terms like “free” when the statements are substantiated by facts. Another commenter noted that advertising rides to medical appointments as “free” could be misleading if there are only a limited number of rides.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in this rule, CMS agrees that superlative statements should be permitted in marketing and communications materials provided they can be factually supported, when applicable, as previously discussed. However, CMS also notes that the use of the term “free” is outside the scope of this proposal as “free” is not a superlative. Currently, § 422.2262(a)(1)(xiii) prohibits the use of “free” in certain scenarios, and §  422.2262(a)(2)(iii) explains when the term “free” may be used.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters urged CMS to reinstate the “meaningful difference” requirement, which would limit plans to only benefit packages that are “substantially different” from other plans offered by the same parent organization in a service area.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and will take them into consideration. However, the “meaningful difference” requirement that was previously in place is outside the scope of this proposal.
                    </P>
                    <P>After consideration of the public comments CMS received, CMS is finalizing these provisions as proposed.</P>
                    <HD SOURCE="HD2">G. Third-Party Marketing Organization (TPMO) Oversight: Revising the Record Retention Requirements for Marketing and Sales Call Recordings §§ 422.2274(g)(2) and 423.2274(g)(2)</HD>
                    <P>
                        In the Contract Year 2027 proposed rule, CMS proposed to codify the revision of marketing and sales recording requirements at 42 CFR 422.2274(g)(2) and 423.2274(g)(2). Consistent with the 10-year record retention requirements and access to records requirements described in §§ 422.504(d) and (e)(1)(iv) and §§ 423.505(d) and (E)(1)(iv), MA Organizations and Part D sponsors are presently expected to retain the sales and marketing call recordings described in §§ 422.2274(g)(2) and 423.2274(g)(2) for 10 years. CMS proposed to update §§ 422.2274(g)(2)(ii) and 423.2274(g)(2)(ii) to reduce the amount of time that MA Organizations and Part D sponsors are required to retain recordings of marketing and sales calls to 6 years, while maintaining the requirement that enrollment records be retained for 10 years, as required under §§ 422.504(e)(1)(iv) and 423.505(e). This proposal only modified the record retention requirements for the marketing and sales portions of calls at 42 CFR part 422, subpart V and Part 423, Subpart V. CMS has long required enrollment records to be maintained for 10 years and the proposal did not remove applicable enrollment documentation and retention requirements set forth in other regulations, specifically the requirement to file and retain enrollment forms as required in §§ 422.60(c)(2), 422.504(e)(1)(iv) and 423.505(e)(1)(iv). 
                        <PRTPAGE P="17464"/>
                        To meet enrollment documentation requirements for enrollments that occur over the phone, plans are still required to record the enrollment portion of the call, as the recording in this instance serves as the enrollment form and provides proof that the beneficiary attested to their intent to enroll in accordance with § 422.60(c)(2) and the Medicare Managed Care Manual, Chapter 2, Medicare Advantage Enrollment and Disenrollment, Section 40.1.3. The enrollment portion of the call begins when the beneficiary is advised that they are completing an enrollment request, after which they provide the information as required by the enrollment form and attest to their intention to enroll.
                    </P>
                    <P>As a part of the Medicare Program; Contract Year 2023 Policy and Technical Changes to the Medicare Advantage and Medicare Prescription Drug Benefit Programs; Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency; Additional Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency Final Rule (hereafter referred to as the May 2022 final rule) (87 FR 27704), CMS finalized regulations at §§ 422.2274(g)(2) and 423.2274(g)(2) regarding plan oversight of Third-Party Marketing Organizations (TPMOs). Under these regulations, MA organizations and Part D sponsors must have certain requirements in their contracts, written arrangements, and agreements with TPMOs, or between the TPMO and MA organization or Part D sponsor's first tier, downstream, and related entities (FDR). In §§ 422.2274(g)(2)(ii) and 423.2274(g)(2)(ii), CMS finalized the requirement that an MA organization or a Part D sponsor's contract, written arrangement and/or agreement with the aforementioned entities must ensure that all calls with beneficiaries are recorded in their entirety. In addition, in order to ensure compliance with the 10-year record retention and access to records requirements described in §§ 422.504(d) and (e)(1)(iv) and § 423.505(d) and (e)(1)(iv), MA organizations and Part D sponsors are expected to retain the sales and marketing call recordings described in §§ 422.2274(g)(2) and 423.2274(g)(2) for 10 years.</P>
                    <P>Following the finalization and implementation of the May 2022 final rule, CMS received questions regarding retention requirements for recorded calls, as MA organizations and Part D sponsors were unsure if calls regarding marketing, sales, and enrollment were subject to the 10-year record retention requirements at §§ 422.504(d) and 423.505(d). CMS also received questions about the scope of “all calls” for recording purposes, including if the recording requirement extended to calls that merely set an appointment with a potential enrollee, calls to enrollees to confirm welcome packets were received, and other non-marketing or non-sales calls to prospective enrollees. CMS notes that the May 2022 final rule did not provide exceptions or otherwise establish a more defined boundary for the type of call that was subject to recording and retention. To rectify any potential unintended consequences stemming from the standard that CMS codified in the May 2022 final rule, CMS issued the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program; Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly Policy Final Rule (hereafter referred to as the April 2023 final rule) (88 FR 22120), to address the requirement that all calls be recorded and retained. In the April 2023 final rule, CMS modified §§ 422.2274(g)(2)(ii) and 423.2274(g)(2)(ii) to require only the recording of marketing, sales, and enrollment calls, including the audio portion of calls via web-based technology. The implementation of this revised and less burdensome call recording requirement was to ensure the necessary calls were recorded and available for oversight and monitoring while still reducing some level of burden on plans.</P>
                    <P>CMS has continued to oversee and monitor agent and broker behavior by reviewing call recordings to determine compliance. In addition to CMS, other governmental entities, such as the Department of Justice (DOJ) have relied on call recordings for investigations. CMS has requested call recordings based on complaints from CMS's Complaint Tracking Module (CTM). The requested recordings were chosen based on the severity of the allegations in the complaint. The recordings were reviewed to determine if the claims against the agent or broker were supported by the call recording. The outcome of CMS's review of the marketing and sales portion of the call recordings has been mixed. In some instances, the recordings did not support the beneficiary's complaint as detailed in the CTM. In other instances, the complaints were substantiated by the recording. These reviews have shown examples where agents and brokers fail to provide sufficient information for a beneficiary to make an informed decision or the information provided by the agent or broker is inaccurate. For reviewed complaints that are substantiated, CMS notifies the MA organization or Part D sponsor of the Agency's findings and requests the organization review the results and take appropriate action against the agent, broker, or TPMO. MA organizations and Part D sponsors have responded to CMS's findings with actions such as retraining or discontinuing contracts with certain entities.</P>
                    <P>
                        MA organizations and Part D sponsors are responsible for ensuring all downstream entities meet CMS's requirements. When CMS proposed revisions to these regulations in the Contract Year 2027 proposed rule, there were over 68 million Medicare beneficiaries, of which 51.1 percent are enrolled in MA and other health plans.
                        <SU>53</SU>
                        <FTREF/>
                         Of the approximately 34 million beneficiaries enrolled in an MA plan or other health plan, 31 percent use agents to assist with plan choices,
                        <SU>54</SU>
                        <FTREF/>
                         resulting in 10,540,000 beneficiaries discussing plan options with agents annually. Each year, only three out of every ten beneficiaries compare plans during Medicare's Annual Election Period,
                        <SU>55</SU>
                        <FTREF/>
                         resulting in approximately 3.1 million beneficiaries using agents or brokers to review their plan choices. Based on these data, CMS conservatively estimated that MA organizations, Part D Sponsors, and their TPMOs must record hundreds of thousands of calls each year to comply with these regulatory requirements, resulting in millions of calls being subject to the 10-year retention requirement.
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             
                            <E T="03">https://data.cms.gov/summary-statistics-on-beneficiary-enrollment/medicare-and-medicaid-reports/medicare-monthly-enrollment.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2024/08/Medicare-agents-MedPAC-03.25sec.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             
                            <E T="03">https://www.kff.org/medicare/issue-brief/nearly-7-in-10-medicare-beneficiaries-did-not-compare-plans-during-medicares-open-enrollment-period/.</E>
                        </P>
                    </FTNT>
                    <P>
                        CMS recognizes the cost and burden of these requirements. CMS has received comments from industry groups noting the costs associated with recording and retaining the marketing and sales portion of calls. Audio call files are large, taking a substantial amount of data storage, especially when the record retention requirement is to store these calls for 10 years. In addition, to the cost of maintaining these calls, CMS is highly unlikely to review calls past the 6-year mark. To best address marketing complaints, the review of calls typically needs to be much closer to the timeframe of the actual complaint. Reviewing complaints that are 10 years 
                        <PRTPAGE P="17465"/>
                        old may result in the discovery of issues that are irrelevant and that will not result in identifying current issues that affect beneficiaries. Because of these reasons, CMS proposed to reduce the timeframe for the retention of the marketing and sales portion of calls from a 10-year requirement to a 6-year requirement. The revised retention requirement would also apply to currently retained call recordings, meaning that any marketing and sales portion of calls older than 6 years that are currently being retained would no longer need to be retained.
                    </P>
                    <P>CMS stated that a 6-year record retention requirement for the marketing and sales portion of calls is sufficient for the purpose of enabling CMS to review agent and broker behavior and balances the need for appropriate oversight while also providing consideration of the burden imposed by record retention. It is helpful for CMS to review the marketing and sales portion of audio recordings when the Agency receives complaints from beneficiaries related to being misled into choosing a plan and then enrolling in that plan. The marketing and sales portion of these recordings is most useful when it is recent and permits CMS to provide timely feedback to MA organizations and Part D sponsors, so they may, in turn, quickly address any compliance issues that are identified by CMS review.</P>
                    <P>When CMS proposed a revised 6-year record retention requirement for the marketing and sales portion of calls, in the Contract Year 2027 proposed rule, CMS also said that the Agency would consider several other alternatives for finalization as described below. CMS considered alternatives based on the cost and burden of recording and storing calls.</P>
                    <P>One alternative to the proposed 6-year retention requirement was to reduce the 10-year retention requirement for the marketing and sales portion of calls to a 3-year retention requirement. In the Contract Year 2027 proposed rule, CMS noted that a 3-year retention would further decrease existing burden and costs on MA organizations and Part D sponsors but would provide both CMS and other oversight organizations with a shorter lookback period. A shorter lookback period could make it more challenging to identify longer-term trends, including potential trends associated with TPMOs. However, CMS also noted in the Contract Year 2027 proposed rule that a 3-year retention requirement would result in a more significant decrease in burden as compared to the proposed 6-year retention requirement.</P>
                    <P>
                        In the Contract Year 2027 proposed rule, CMS also considered alternatives such as whether audio recordings of the marketing and sales portion of calls are necessary for record retention purposes or whether the ability to review agent and broker behavior could be achieved via other, less expensive means. Specifically, CMS considered whether permitting written retention of the marketing and sales portion of calls (
                        <E T="03">i.e.,</E>
                         a transcript) in lieu of retaining audio recordings of such calls, or a hybrid approach that requires audio recordings for 3 years followed by written retention for the remainder of the retention period would be sufficient to achieve the purpose articulated by CMS in the Contract Year 2027 proposed rule. An important factor to this alternative that CMS considered was the ability of current technology to automate the transcription with sufficient accuracy. CMS stated the Agency was considering that transcripts might still provide CMS with enough ability to review interactions between beneficiaries and agents and brokers to identify non-compliance similar to the review of audio recordings. However, CMS also stated that, on the other hand, transcripts would not capture the tone by which the agent or broker interacted with the beneficiary. The Agency also acknowledged that the data storage costs of retaining transcripts may be less than the data storage costs of audio recordings, further reducing burden if new costs from automated transcription did not outweigh those savings.
                    </P>
                    <P>Finally, based on the mixed findings from the review of call recordings, CMS considered as an alternative whether maintaining a recording, audio or otherwise, of the marketing and sales portion of calls is necessary at all. The results of the review of these portions of calls, as identified earlier in this proposal, have provided examples that agents and brokers do not always provide accurate and truthful information. Conversely, in other instances, the call recordings offer a way to refute beneficiary complaints, such as those filed through 1-800-MEDICARE. However, by eliminating these requirements, CMS and other oversight organizations would not have the ability to directly review agent and broker behavior to ensure beneficiaries select a plan that best meets their needs. CMS acknowledged there are differences between MA, Part D, Marketplace, Medicaid, and commercial insurance, however, CMS noted the elimination of recording the MA and Part D marketing and sales portion of calls would result in more parity with the requirements of these programs.</P>
                    <P>CMS solicited comments on all aspects of the proposal and requested comments on other alternatives for consideration in the final rule. CMS thanks commenters for their input. In the following section, CMS describes the comments received and CMS's corresponding responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the proposal to change the call recording requirement from 10 to 6 years, mentioning that auditing recorded calls is a necessary practice to protect beneficiaries. Commenters noted the proposal reflects operational realities while preserving program integrity; assists small and mid-size brokerages regarding storage and cybersecurity; represents a balanced regulatory approach that appropriately reduces administrative and financial burdens; will foster greater competition with the industry, ultimately improving the cost effectiveness and quality of products offered by MA organizations and Part D sponsors; and addresses the issue of compliance costs not proportionality improving oversight outcomes. Commenters stated that a 6-year retention requirement is still sufficient for oversight and monitoring and preserves accountability for enrollment related interactions. Commenters also mentioned that it is unlikely to need call recordings for review beyond certain timeframes ranging from 1 to 6 years. Other commenters supported the proposal with no specific reasons for the support.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' support. CMS agrees that the shorter timeframe will still provide CMS, MA and Part D plans, TPMOs, and agents and brokers with the necessary tools for oversight and monitoring. The Agency also appreciates the commenters addressing how the proposal will be beneficial for the industry in areas including storage costs, compliance costs, and operational realities while still protecting beneficiaries.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters opposed the proposal and urged CMS to maintain the 10-year record retention requirement. These commenters emphasized that the record retention requirement serves as an important beneficiary protection, supports a Medicare enrollee's marketing violation complaint with Medicare that can lead to a timely resolution (for example, retroactive or prospective enrollment via a SEP), and that the calls constitute an integral source of accountability for TPMOs and MA organizations. A commenter stated that call recordings were needed when plan changes and 
                        <PRTPAGE P="17466"/>
                        billing timelines are pushed into the following year or beyond as claims work through various systems. The commenter stated that CMS's requirements should remain aligned with similar requirements associated with Medicaid and Medicare dually eligible individuals. In addition, this commenter also stated that 10 years may be excessive.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge the commenters' concerns. However, we have determined that a shorter record retention period will not compromise beneficiary protections, result in an untimely resolution of a beneficiary, or jeopardize appropriate accountability for TPMOs and MA organizations. Commenters noted that most beneficiary issues and complaints arise within the first few years of a beneficiary's plan enrollment. Reviewing more dated call recordings would provide limited value for oversight, monitoring, or beneficiary assistance, particularly when beneficiaries have transitioned to different plans since the original recording. In some instances, the TPMO, agent, or broker no longer sells MA plans, further limiting the value of a dated call recording. After 6 years, it is also likely that additional training was provided, which resulted in more compliant agent or broker behavior. As for the commenter who stated that call recordings assist in a timely resolution for marketing complaints, CMS agrees that a call recording can assist in a timely resolution for marketing complaints. However, CMS believes that the outcome is often optimized when the issue is addressed within close proximity of a marketing complaint and that keeping call recordings for an additional 4 years would provide no added value in resolving marketing complaints in a timely manner. Regarding the commenter stating that CMS's rules should align with similar Medicaid and Medicare requirements associated with dually eligible individuals, CMS notes that the 6-year requirement would apply to dually eligible individuals who are enrolled into MA or Part D plans, unless a State Medicaid Agency Contract requires a longer retention period. In addition, alignment with State Medicaid programs would be extremely challenging given each state may have different requirements. To protect enrollees, it is longstanding CMS policy that MA and Part D enrollees who believe they may be adversely impacted by an enrollment decision based on an agent or broker misrepresenting plan options may contact 1-800-MEDICARE to request a special enrollment period (SEP) due to the circumstances. CMS reviews the supporting details and documentation for these requests and determines eligibility for an exceptional circumstances SEP on a case-by-case basis.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters requested that CMS eliminate the call recording requirement entirely without providing any alternatives. These commenters stated that the recordings add unnecessary complexity and cost without demonstratable benefit to clients. The commenters furthered this point in saying the recordings do not solve any issue, and seniors do not like recordings at all.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the feedback from the commenters. However, CMS does not support eliminating call recordings in their entirety at this time. Currently, call recordings play an integral role as a beneficiary protection, assist in identifying brokers, agents, and TPMOs that fail to adhere to CMS regulations, and assist in monitoring and oversight of the MA and Part D programs. CMS will continue to gather data on the value of call recordings to further inform future decisions about marketing and sales recording requirements before making any additional changes beyond what was proposed in the Contract Year 2027 proposed rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should focus monitoring efforts on unscrupulous marketing organizations that have United States call centers that contract with Third Party Marketing Organizations (TPMOs) that use foreign call center representatives. The commenter added that these call centers can spend up to 18 hours a day calling Medicare beneficiaries within the U.S. to get them to enroll or change Medicare Advantage plans. The commenter further stated that these foreign call centers are driven by sales quotas, not beneficiary suitability.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that monitoring call centers, including those contracting with out-of-country entities, is important. Although the commenter's suggestion is out of scope, CMS's review of call recordings assists in identifying unscrupulous marketing organizations, including those that contract with out-of-country entities. In cases where CMS determines marketing violations have occurred, MA and Part D plans are held accountable for the actions of their downstream entities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS assumes an audio call meaningfully prevents fraud, citing that beneficiaries sometimes claim the voice is not theirs, resulting in a plan-based enforcement action taken against an agent. The commenter stated that, if a call recording can be dismissed by a beneficiary simply stating, “that is not my voice,” recordings are not immune to dispute, do not conclusively prove identity, create massive data security and privacy risks, and expose agents and beneficiaries to long-term breach liability. This same commenter also said that documentation and transcripts are better because they capture intent, document what was discussed, are searchable and auditable, are less costly to store, and reduce exposure to sensitive voice data. This commenter suggested that CMS allow secure transcripts, summaries, or enrollment attestations instead of call recordings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter but maintain that call recordings are extremely valuable. Call recordings can capture the intent and the tone of the call, providing a clear, realistic view of the interaction between the beneficiary and the agent or broker that transcripts cannot capture. CMS acknowledges that voice recordings can be manipulated but maintains that they are not quite as easy to manipulate as transcripts. Entire sections of a call can be eliminated in a transcript, which could go unnoticed, while removing a portion of an audio recording would likely be more noticeable. CMS also believes a beneficiary's identity is more likely to be authenticated through a call recording over a transcript. Regarding data breaches and security concerns, CMS recognizes these are areas of concern, but requirements are in place for securing sensitive data. Currently, it is the Agency's position that transcript summaries are too limited and do not provide enough detail to capture inaccurate or misleading information between an agent and a beneficiary during a marketing or sales calls. Likewise, enrollment attestations provide even less information than a transcript summary. Summaries and attestations do not provide the information necessary to properly monitor TPMO marketing and sales calls. CMS agrees with the commenter that transcripts are searchable and less costly to store but does not agree that transcripts have more value than call recordings. Because call recordings are a valuable tool, CMS will not be allowing transcripts in lieu of all audio recordings for the entire retention period, however, CMS is modifying its original proposal to allow the use of transcripts in the last 3 years of the retention period.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         About half of the commenters requested that the requirement for call recordings be eliminated, however, they 
                        <PRTPAGE P="17467"/>
                        acknowledged that if CMS determined a full rescinding of the requirement was not feasible, a reduced retention period of 2 years would be more than sufficient for review purposes. The vast majority of these commenters relayed the same concerns, including legal and practical challenges, logistical and financial strain on independent agents with no measurable enhanced beneficiary protection, unwarranted data management burden, and strains on resources that could otherwise be dedicated to serving beneficiaries. Additional concerns included infrastructure, compliance oversight, data storage, privacy, operational complexities, liability risks, the sheer number of recordings to maintain, and an unnecessary barrier to natural communications between the beneficiary and agent. Commenters also stated that a 10-year retention period is excessive, places an undue administrative burden on independent agents and agencies, and far exceeds what is practically necessary for addressing most beneficiary complaints or conducting CMS investigations. According to commenters, a 2-year record retention period would adequately accommodate compliance needs, allowing for thorough review and investigation without creating an unnecessarily extensive and costly data storage requirement for independent agents who are already managing multiple administrative tasks. Commenters also stated that a 2-year retention period would be entirely sufficient to fully accommodate most beneficiary complaints, CMS investigations, and plan or agent reviews, while maintaining adequate oversight without imposing unnecessary burden on independent agents and freeing up resources for more direct beneficiary support.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS values these commenters' suggestions and recognizes that record retention requirements impose additional burden and costs, which may affect independent agents and brokers more than other entities. CMS agrees that call recording retention for 10 years is excessive and exceeds what is necessary to review and address beneficiary complaints. CMS appreciates the commenters understanding CMS's need for call recordings and proposing the alternative 2-year record retention requirement. As stated in the Contract Year 2027 proposed rule, the DOJ utilizes call recordings for investigative and legal purposes. DOJ's investigations and legal proceedings often span multiple years, necessitating access to call recordings that extend beyond a 2-year timeframe. Beyond the DOJ requirements, CMS's monitoring activities, including potential audits, may require access to records beyond a 2-year retention period. Insufficient retention or eliminating call recordings could prevent the identification of misleading agent or broker practices and hinder the ability of MA plans and Part D sponsors to take appropriate corrective action.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed support of the proposal to reduce the record retention period while recommending alternative timeframes ranging from 2 to 5 years. Commenters' rationales for a 2 to 5 year record retention period varied by specific reasons but the sentiments were similar in nature. These commenters suggested: noting that a much reduced timeframe would be longer than most consumers remain in a particular plan; there would be ample opportunity for post enrollment reviews; requests for recordings beyond 3 years are uncommon; reduced administrative burden and data storage costs would not impair oversight and audit integrity; existence of consumer protection; alignment with the Federal Trade Commission's Telemarketing Record Retention requirement; more efficient storage of call recordings; a more accurate reflection of real-world compliance timeliness while continuing to support complaint resolution, audits, and enforcement actions; significant reduction in data storage volume and associated costs resulting in meaningful financial and administrative efficiencies for MA and Part D plans without compromising program integrity or beneficiary protections; essential accountability and affordability promoting prudent financial guidance and product offering is maintained; reduction of potential cybersecurity risks; and that it is a correct balance of satisfying CMS's interests while reflecting the pragmatic realities of member churn and administrative burden. Commenters expressed similar concerns as previously noted, regarding the 10-year retention requirement, stating that a 10-year requirement is excessive, places an undue financial and logistical burden on independent agents, and has significant storage costs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS values the feedback from commenters recommending a further reduction from 6 years to a range of 2 to 5 years. CMS agrees that a further reduction in call recording retention requirements will further reduce costs, storage volume, and administrative burden. CMS also agrees that a shorter audio recording retention period is a more accurate reflection of CMS's and DOJ's compliance needs without compromising program integrity. However, CMS maintains that a reduction from a 10-year retention period to a 6-year retention period fulfills the Agency's and DOJ's oversight, investigative, and litigation requirements; while a 2 to 5 year retention period is too limited to adequately address those needs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters supported the alternative of permitting transcripts in lieu of call recordings, citing reasons including substantially less storage, transcripts being more easily ingested by AI systems to review, and a reduction of administrative burden.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for providing feedback on alternatives to current call recording requirements as well as those that were proposed in the Contract Year 2027 proposed rule. CMS agrees that transcripts are substantially less expensive and require less storage. CMS believes transcripts can be a valuable and cost-effective alternative for call retention. However, CMS believes that call recordings provide additional benefits beyond those provided by transcripts. Call recordings provide the tone of both the beneficiary and the agent, including if the beneficiary is pressured into enrolling in a plan. CMS believes the benefits of call recordings outweigh the benefits of transcripts during the time period that most complaints occur. As mentioned by the commenters, most complaints are addressed within the first few years after a beneficiary enrolls in a plan. A decreased retention period will still adequately support CMS's and DOJ's monitoring, oversight, and litigation needs. Following the timeframe in which most complaints are addressed, CMS believes transcripts can provide the pertinent information if additional review is necessary.
                    </P>
                    <P>
                        Therefore, based on alternative proposals included as part of CMS's request for comments in the Contract Year 2027 proposed rule and CMS's oversight and monitoring requirements, CMS is finalizing its proposal with a modification to allow for marketing and sales call records to be retained using both audio recordings and transcripts. For the first 3 years of the retention period, records must be maintained in audio format. In the last 3 years of retention (of the 6-year retention period), records may be maintained in either audio format or as complete and accurate transcript recordings. A transcription is considered complete and accurate if it documents the full recording, reflecting all statements made 
                        <PRTPAGE P="17468"/>
                        by the participants as it originally occurred. CMS believes this strikes the appropriate balance in maintaining program integrity while reducing burden and costs on MA organizations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed concerns with call centers. These commenters noted that call centers presented more significant concerns than independent agents and recommended that CMS require recordings from call centers but not from independent agents.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the suggestion but maintains that, at this time, all sales and marketing calls should be recorded, not just those from call centers. Any agent, regardless of whether the agent works for a call center or is independent, may provide inaccurate information or steer a beneficiary into a particular plan. Complaints received by CMS concern both independent agents and agents working for call centers. Call recordings currently allow CMS and other agencies to fully address these complaints.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters mentioned that CMS needs to reduce the retention requirements for enrollment calls, citing that many times the sale, marketing, and enrollment calls are combined, making separating them difficult and more burdensome.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their feedback. However, the Contract Year 2027 proposed rule did not address the call retention timeframe of enrollment calls and therefore this comment is out of scope.
                    </P>
                    <P>After careful consideration of public comments, CMS is finalizing in §§ 422.2274(g)(2)(ii) and 423.2274(g)(2)(ii) the 6-year marketing and sales call retention policy with a modification to allow for complete and accurate transcripts in the last 3 years of retention. As mentioned above, a transaction is considered complete and accurate if it documents the full recording, reflecting all statements made by the participants as it originally occurred. In summary, all marketing and sales calls, including the audio portion of calls conducted via web-based technology, must be recorded and retained in their entirety for a minimum period of 6 years. For the first 3 years of the retention period, records must be maintained in audio format. For years 4, 5, and 6, records may be maintained in either audio format or as complete and accurate transcript recordings.</P>
                    <HD SOURCE="HD2">H. Rescinding the Requirement for the Notice of Availability (§§ 422.2267(e)(31) and 423.2267(e)(33))</HD>
                    <P>
                        The Notice of Availability of language assistance services and auxiliary aids and services (NoA) material, formerly known as the Multi-language insert (MLI), required at 42 CFR 422.2267(e)(31) and 423.2267(e)(33), has been modified in conjunction with changes to the Health and Human Services Office for Civil Rights (OCR) language assistance notification requirements (currently at 45 CFR 92.11), implementing section 1557 of the Affordable Care Act (ACA), 42 U.S.C. 18116. CMS's NoA requirements are closely aligned with and broadly duplicate OCR's NoA requirements and were adopted by CMS to implement and ensure compliance with Title VI, section 504 of the Rehabilitation Act of 1973, and ACA Section 1557 (incorporating Title VI and section 504 by reference). On March 1, 2025, Executive Order (E.O.) 14224 was issued: “Designating English as the Official Language of The United States” (hereinafter referred to as E.O. 14224).
                        <SU>56</SU>
                        <FTREF/>
                         E.O. 14224 designates English as the official language of the United States and includes the revocation of E.O. 13166 of August 11, 2000 (Improving Access to Services for Persons with Limited English Proficiency), but recognizes that “[a]gency heads should make decisions as they deem necessary to fulfill their respective agencies' mission and efficiently provide Government services to the American people” and notes that “nothing in [the E.O.] requires or directs any change in the services provided by any agency” and “[a]gency heads are not required to amend, remove, or otherwise stop production of documents, products, or other services prepared or offered in languages other than English.” On January 31, 2025, E.O. 14192 was issued: “Unleashing Prosperity Through Deregulation” (hereinafter referred to as E.O. 14192).
                        <SU>57</SU>
                        <FTREF/>
                         E.O. 14192 describes the Administration's policy goals to promote prudent financial management and alleviate unnecessary regulatory burdens. Section 2 of E.O. 14192 states that “it is the policy of the executive branch to be prudent and financially responsible in the expenditure of funds, from both public and private sources, and to alleviate unnecessary regulatory burdens placed on the American people.” Lastly, a recent memorandum from the Office of the Attorney General, released on July 14, 2025,
                        <SU>58</SU>
                        <FTREF/>
                         provides guidance for compliance with E.O. 14224, but indicates that additional guidance will be forthcoming on compliance with Title VI. As CMS stated in the Contract Year 2027 proposed rule, to ensure consistency and reduce the risk of misalignment, CMS believes it is prudent to defer to OCR as to how this guidance will impact language assistance requirements under Title VI and Section 1557 throughout the programs under HHS's purview.
                        <SU>59</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">https://www.whitehouse.gov/presidential-actions/2025/03/designating-english-as-the-official-language-of-the-united-states/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             
                            <E T="03">https://www.whitehouse.gov/presidential-actions/2025/01/unleashing-prosperity-through-deregulation/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             
                            <E T="03">https://www.justice.gov/opa/pr/justice-department-releases-guidance-implementing-president-trumps-executive-order.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             As discussed later in this section, CMS imposes other language assistance (and auxiliary aid and service) requirements on such entities for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, and unrelated to nondiscrimination requirements imposed by Title VI or ACA Section 1557.
                        </P>
                    </FTNT>
                    <P>CMS inadvertently omitted references to cost plans from this proposal in the Contract Year 2027 proposed rule and notes that the intent was always for the proposal to rescind the NoA requirement to apply to cost plans pursuant to CMS's authority in section 1876(c)(3)(C) to regulate marketing by section 1876 cost plans and the authority in section 1876(i)(3)(D) to specify new section 1876 contract terms as the Secretary may find necessary and appropriate. It is also established at § 417.428 that most of the marketing and communication regulations in subpart V of part 422, including the NoA requirement, also apply to section 1876 cost plans. Accordingly, the rescission of the NoA requirement applies to cost plans as well as MA organizations and Part D sponsors.</P>
                    <P>CMS's requirements under §§ 422.2267(e)(31) and 423.2267(e)(33) currently duplicate OCR requirements at 45 CFR 92.11. To ensure clarity, minimize administrative burden, and limit confusion for MA organizations, Part D sponsors, and cost plans, CMS proposed to eliminate CMS's NoA requirement under §§ 422.2267(e)(31) and 423.2267(e)(33) and to defer to OCR's requirements related to notification of language assistance services and auxiliary aids and services under 45 CFR 92.11. CMS stated that this would mitigate the potential for future misalignment and the need for additional modifications to CMS's requirements as policy evolves.</P>
                    <P>
                        CMS historically has looked to OCR's language requirements when promulgating regulations for the MA and Part D programs with respect to civil rights and nondiscrimination. On May 18, 2016, OCR published the Nondiscrimination in Health Programs and Activities final rule (81 FR 31376), hereinafter referred to as the “2016 
                        <PRTPAGE P="17469"/>
                        section 1557 final rule,” implementing the requirement that all covered entities—any health program or activity, any part of which receives Federal financial assistance (including credits, subsidies, or contracts of insurance), and any program or activity that is administered by an executive agency or any entity established under title I of the ACA (or amendments)—include taglines with all “significant communications.” On June 19, 2020, the Department of Health and Human Services (Department) published a new section 1557 final rule, “Nondiscrimination in Health and Health Education Programs or Activities, Delegation of Authority,” hereinafter referred to as the 2020 section 1557 final rule (85 FR 37160), rescinding the 2016 section 1557 final rule's tagline requirements (84 FR 27860).
                    </P>
                    <P>To address the gap after the rescission of OCR's tagline requirements in the 2020 section 1557 final rule, CMS finalized an MLI requirement in the “Medicare Program; Contract Year 2023 Policy and Technical Changes to the Medicare Advantage and Medicare Prescription Drug Benefit Programs; Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency; Additional Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency” final rule (87 FR 27704), hereinafter referred to as the “May 2022 final rule.” CMS, at §§ 422.2267(e)(31) and 423.2267(e)(33), required the MLI to have a CMS-provided standardized tagline in the following languages: Spanish, Chinese, Tagalog, French, Vietnamese, German, Korean, Russian, Arabic, Italian, Portuguese, French Creole, Polish, Hindi, and Japanese. Additionally, the MLI required that MA organizations and Part D sponsors include additional languages in the plan's service area that met the five percent service area threshold, as required under §§ 422.2267(a)(2) and 423.2267(a)(2). Sections 422.2267(a)(2) and 423.2267(a)(2) require that, for all required materials and content under §§ 422.2267 and 423.2267, MA organizations and Part D sponsors must, “for markets with a significant non-English speaking population, be in the language of these individuals.” Specifically, MA organizations and Part D sponsors “must translate required materials into any non-English language that is the primary language of at least 5 percent of the individuals in a plan benefit package (PBP) service area.”</P>
                    <P>
                        On August 4, 2022, OCR proposed a new rule, Nondiscrimination in Health Programs and Activities (hereinafter referred to as the “2022 proposed rule”) for section 1557 of the ACA (87 FR 47824), to require covered entities to notify the public of the availability of language assistance services and auxiliary aids and services for their health programs and activities at no cost using a NoA and requiring that OCR's NoA be provided in English and at least in the 15 most common languages spoken by individuals with limited English proficiency in the relevant State or States, and in alternate formats for individuals with disabilities who request auxiliary aids and services to ensure effective communications.
                        <SU>60</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             The proposed rule was finalized, with minor modifications on May 6, 2024, (89 FR 37522), creating the requirements for the notice of the availability of language assistance services and auxiliary aids and services at 45 CFR 92.11.
                        </P>
                    </FTNT>
                    <P>To ensure consistency, following OCR's 2022 proposed rule, CMS finalized the current NoA in the “Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024-Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE)” final rule (89 FR 30448), hereinafter known as the “April 2024 final rule.” In this rule, CMS renamed the required document from the MLI to the notice of availability of language assistance services and auxiliary aids and services (Notice of Availability) at §§ 422.2267(e)(31) and 423.2267(e)(33) to align with OCR's language. Additionally, the notice was recategorized from a standardized communications material to a model communications material, requiring MA organizations and Part D sponsors to include in the notice that, at a minimum, they provide language assistance services and appropriate auxiliary aids and services free of charge (89 FR 30534). CMS's updated NoA also updated the language criteria to align with OCR's proposed language at the time. To align with OCR, CMS finalized the requirement for MA organizations and Part D sponsors to provide CMS's NoA “in English and at least the 15 languages most commonly spoken by individuals with limited English proficiency of the relevant State or States associated with the plan's service area and must be provided in alternate formats for individuals with disabilities who require auxiliary aids and services to ensure effective communication.” CMS maintained the requirement that CMS's NoA also include any non-English language that is the primary language of at least 5 percent of the individuals in a plan benefit package (PBP) service area, provided it was beyond the 15 languages most commonly spoken by individuals with limited English proficiency of the relevant State or States associated with the plan's service area. This update resulted in the potential for MA organizations and Part D sponsors to develop a NoA with more than 15 languages, exceeding OCR's requirements.</P>
                    <P>In the Contract Year 2027 proposed rule, CMS explained that while currently OCR's and CMS's requirements are mostly aligned, CMS noted minor differences in the language of the current regulations. The OCR NoA requirement applies to the “State or States in which a covered entity operates” which is broader than CMS's requirement. CMS explained that its NoA requirement applies to the “State or States associated with the plan's service area” which CMS defined as the plan benefit package level. Additionally, CMS requires its NoA to be included on all CMS required materials at §§ 422.2267(e) and 423.2267(e), whereas OCR's language regarding where its NoA should be placed (45 CFR 92.11(c)(5)) is less specific, though its guidance still aligns with many of CMS's required materials.</P>
                    <P>
                        As discussed in the April 2024 final rule, ACA Section 1557 (42 U.S.C. 18116(a)) provides that, except where otherwise provided in Title I of the ACA, an individual shall not, on the grounds prohibited under Title VI of the Civil Rights Act of 1964, 42 U.S.C. 2000d 
                        <E T="03">et seq.</E>
                         (race, color, or national origin), Title IX of the Education Amendments of 1972, 20 U.S.C. 1681 
                        <E T="03">et seq.</E>
                         (sex), the Age Discrimination Act of 1975, 42 U.S.C. 6101 
                        <E T="03">et seq.</E>
                         (age), or section 504 of the Rehabilitation Act of 1973, 29 U.S.C. 794 (disability), be excluded from participation in, be denied the benefits of, or be subjected to discrimination under, any health program or activity, any part of which is receiving Federal financial assistance (including credits, subsidies, or contracts of insurance); any program or activity administered by an Executive Agency; or any program or activity administered by any entity established under Title I of the Act or amendments.
                    </P>
                    <P>
                        In the April 2024 final rule, CMS cited discussions from the May 2022 final rule, that “solely relying on the requirements delineated in the 2020 section 1557 final rule for covered entities to convey the availability of interpreter services is insufficient for the MA, cost plan, and Part D programs 
                        <PRTPAGE P="17470"/>
                        and is not in the best interest of Medicare beneficiaries who are evaluating whether to receive their Medicare benefits through these plans and who are enrolled in these plans” (89 FR 30529). At the time, CMS took the position that “informing Medicare beneficiaries that interpreter services are available is essential to realizing the value of our regulatory requirements for interpreter services” (89 FR 30529). CMS further explained that through additional insights “regarding the void created by the lack of any notification requirement associated with the availability of interpreter services for Medicare beneficiaries the materials required under §§ 422.2267(e) and 423.2267(e) were vital to the beneficiary's decision-making process” (87 FR 27821). CMS also cited complaint tracking module (CTM) cases in the Health Plan Management System (HPMS) related to “language” and found a pattern of beneficiary confusion stemming from not fully understanding materials based on a language barrier.
                    </P>
                    <P>In the April 2024 final rule, CMS also explained that updating CMS's NoA requirements in Parts C and D would help align with the Medicaid requirement under § 438.10(d)(2), in which “States must require Medicaid managed care organizations (MCOs), prepaid inpatient health plans (PIHPs), prepaid ambulatory health plans (PAHPs), and primary care case management programs to include taglines in written materials that are critical to obtaining services for potential enrollees in the prevalent non-English languages in the State explaining the availability of oral interpretation to understand the information provided, information on how to request auxiliary aids and services, and the toll-free telephone number of the entity providing choice counseling services in the State” (89 FR 30529). Therefore, CMS finalized its NoA requirements that also aligned with Medicaid materials requirements, such as updating CMS's NoA to require the 15 most common languages in the State rather than the 15 most common languages nationally (89 FR 30529).</P>
                    <P>CMS stated in the Contract Year 2027 proposed rule that, while CMS's and OCR's current requirements are now mostly aligned, CMS was concerned that the duplicative nature of these requirements may potentially result in additional regulatory updates, and corresponding burdens as policy evolves. Because CMS and OCR regulatory schedules vary, the potential differences in requirements can be confusing and burdensome to MA organizations and Part D sponsors who are subject to CMS requirements and the broader OCR requirements as covered entities. Additionally, uncertainty regarding broad changes to language assistance and notification requirements, or how OCR may modify their requirements as policy evolves may result in additional confusion, administrative burden and potential for misalignment of CMS's NoA requirement under §§ 422.2267(e)(31) and 423.2267(e)(33). CMS stated that eliminating its NoA requirement under §§ 422.2267(e)(31) and 423.2267(e)(33) will ensure consistency and clarity for covered entities as these requirements will be addressed centrally by OCR under OCR's relevant authorities. CMS notes that dual eligible special needs plans (D-SNPs) would still be subject to any notice requirements that may be included in the state Medicaid agency contract or state statute for Medicaid as applicable. Overall, CMS's position in the Contract Year 2027 proposed rule was that eliminating the duplicative nature of OCR's and CMS's regulatory requirements supported the principles set forth in E.O. 14192 by promoting prudent financial management and alleviating unnecessary regulatory burdens.</P>
                    <P>In summary, removing §§ 422.2267(e)(31) and 423.2267(e)(33) reduces the potential for future confusion and administrative burden on CMS and MA organizations and Part D sponsors by eliminating duplicative requirements. CMS is not scoring this update in the COI section as CMS believes there will be no burden impacts for this update. In addition, this update is not expected to have any economic impact on the Medicare Trust Fund.</P>
                    <P>CMS reiterates that it is rescinding the CMS-specific NoA requirement promulgated pursuant to Title VI, to avoid duplication and potential misalignment as OCR Title VI policies evolve, but this policy, as finalized, will not reduce Medicare program protections related to language assistance and effective communication, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act. Even with the rescission of the CMS-specific NoA requirements at §§ 422.2267(e)(31) and 423.2267(e)(33), MA organizations, Part D sponsors, and cost plans remain subject to multiple Medicare program requirements that ensure meaningful access for individuals with limited English proficiency (LEP) and individuals with disabilities. For example, MA organizations, Part D sponsors, and cost plans must continue to provide interpreter services for non-English speaking and LEP individuals, including requirements related to interpreter availability and wait times for incoming calls, and that such services be available at no cost to the caller consistent with §§ 422.111(h)(1)(iii), 423.128(d)(1)(iii), and 417.427. In addition, CMS's existing translation and accessibility standards for CMS-required materials and content remain in effect. Under §§ 422.2267(a)(2) and 423.2267(a)(2), MA organizations, Part D sponsors, and cost plans must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4), including the Annual Notice of Change (ANOC), Evidence of Coverage (EOC), Explanation of Benefits (EOB), Summary of Benefits (SB), and provider directories, among others.</P>
                    <P>CMS solicited comment on the proposed amendments and thanks commenters for their input. In the following section, CMS describes the comments received and CMS's corresponding responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported CMS's plan to rescind CMS's NoA requirement and suggested that this proposal would reduce administrative burden and costs for MA organizations and Part D sponsors while protecting against future misalignment between CMS and OCR's language access requirements. Commenters expressed support for eliminating duplicative requirements and centralizing oversight of language access requirements under OCR, with one commenter noting the importance of this, given forthcoming changes to language access requirements. They also noted that this rescission, while reducing administrative burden, would maintain beneficiary protections around language access. Multiple commenters cited the significant volume of notice requirements, which can be lengthy or confusing to enrollees, as further support for CMS to streamline notice requirements and reduce redundancy. One commenter noted the reduced burden from rescinding this notice could benefit small plans like special needs plans (SNPs).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their support of this proposal. Because the provisions proposed to be rescinded relate only to the notice of 
                        <PRTPAGE P="17471"/>
                        availability of language access services and auxiliary aids and services, CMS notes that CMS proposed to defer to OCR with respect to such requirements at 45 CFR 92.11, promulgated under Title VI, Section 504, and/or ACA Section 1557, and that it remains responsible for language assistance and auxiliary aids and services requirements promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter, though supportive of the rescission and greater efficiency, noted concern regarding the transition of these requirements to OCR's oversight and requested MA organizations and Part D sponsors receive timely and detailed guidance on future OCR oversight and clarifications on how OCR's requirement will differ from CMS's NoA requirements. The commenter also requested implementation timelines and coordination between CMS and OCR to prevent conflicting directives and clarification of any ongoing notice obligations for D-SNPs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands the commenter's concern about changing MA and Part D oversight and will share these concerns with OCR. CMS notes that OCR already has oversight of its NoA requirements, and that oversight will continue despite this final rule. OCR is the HHS component responsible for interpreting, implementing, overseeing and enforcing Title VI/ACA Section 1557 notice requirements related to language assistance.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The majority of commenters opposed this proposal and requested CMS maintain its NoA requirement, citing the importance of CMS's NoA in informing beneficiaries of their ability to access language assistance services, and auxiliary aids and services, at no cost to the beneficiary. Some commenters stated that beneficiaries with limited English proficiency (LEP) and those with disabilities rely on CMS's NoA as a safeguard for vulnerable populations. A few commenters expressed concern that rescinding CMS's NoA requirement would limit language access and, therefore, effective communication which could lead to worse health outcomes or result in expensive downstream consequences. These commenters were concerned that without the CMS NoA, beneficiaries will face greater barriers to care, with one commenter citing the already substantial barriers to care that beneficiaries with limited English proficiency may face. Another commenter was concerned that without CMS's NoA, enrollees will not be aware of these services for enrollees with LEP or disabilities. Lastly, a commenter noted that CMS's NoA helps reduce burden on community-based organizations with limited resources.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their thoughts and acknowledges these concerns. However, the Agency wants to emphasize that MA organizations and Part D sponsors will still be required to provide OCR's NoA as required by 45 CFR 92.11 and Medicaid regulations at § 438.10(d)(2), as applicable. As stated earlier, CMS is proposing to rescind CMS's NoA to ensure clarity, minimize administrative burden, and limit confusion for MA organizations and Part D sponsors. Under OCR's requirements, beneficiaries will continue to receive the appropriate notices. Deferring to OCR's oversight, management, and enforcement of Title VI, Section 504, and/or ACA Section 1557 with respect to such notice requirements as required by 45 CFR 92.11, related to language assistance services and auxiliary aids and services, would also mitigate the potential for future misalignment and the need for additional modifications to CMS's Title VI, Section 504, and/or ACA Section 1557 requirements as policy evolves. Moreover, CMS has other language-based requirements, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, that remain in effect that provide a level of protection to non-English speaking beneficiaries. Under §§ 422.2267(a)(2) and 423.2267(a)(2), for example, MA organizations and Part D sponsors must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters had specific concerns about deferring oversight to OCR's NoA requirements, with commenters claiming OCR has a limited capacity, due to low staffing, to properly oversee these requirements or that there could be enforcement gaps. Commenters articulated concern that the lack of clear oversight or protection could harm beneficiaries or lead to ineffective oversight and that reducing CMS oversight may mean MA organizations and Part D sponsors are less inclined to provide these notifications. Another commenter noted that, while appreciative of CMS's goal to mitigate future misalignment, they were concerned that this change would create more confusion, without additional benefit for beneficiaries. Furthermore, this commenter recommended CMS communicate changes to OCR guidance through HPMS and continue streamlining requirements. Another commenter requested that CMS not defer oversight and management to OCR until clear, enforceable mechanisms are in place to ensure enforcement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' thoughts. However, CMS reiterates that OCR is the HHS component responsible for interpreting, implementing, overseeing, and enforcing Title VI, Section 504, and/or ACA Section 1557 requirements related to notification for language assistance services and auxiliary aids and services at 45 CFR 92.11. Rescinding CMS's NoA requirement will assist MA organizations and Part D sponsors and beneficiaries in removing duplicative requirements that could result in potential confusion for beneficiaries and unnecessary administrative burden, including the need to ensure compliance with both CMS and OCR NoA requirements. Moreover, CMS has other language-based requirements, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, that remain in effect that provide a level of protection to non-English speaking beneficiaries. Under §§ 422.2267(a)(2) and 423.2267(a)(2), for example, MA organizations and Part D sponsors must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed concern about limitations to civil rights and that this proposal will harm Americans with disabilities and individuals with LEP. A commenter disagreed with CMS's rationale that CMS and OCR's requirements are duplicative or confusing and instead believes that these requirements work together to promote effective communication. This commenter added that removing CMS's requirement eliminates CMS's monitoring capacity 
                        <PRTPAGE P="17472"/>
                        in its complaint tracking system. An additional commenter disagreed with CMS that CMS's NoA is duplicative with OCR's requirements, arguing that it provides clear directions to MA organizations and Part D sponsors within the Medicare context. Another commenter was concerned administrative burden would shift from MA organizations and Part D sponsors to beneficiaries and providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands commenters' concerns but reiterates that OCR is the HHS component responsible for implementation of Title VI, Section 504, and/or ACA Section 1557 requirements and that CMS is proposing to rescind CMS's NoA due to its duplicative nature and to streamline oversight of notice requirements as required by 45 CFR 92.11 under OCR. Rescinding CMS's NoA does not limit CMS's ability to monitor relevant complaints, and MA organizations and Part D sponsors will still be responsible under their CMS contracts to follow all applicable federal rules and regulations. As previously stated, CMS has other language-based requirements, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, that remain in effect that provide a level of protection to non-English speaking beneficiaries. Under §§ 422.2267(a)(2) and 423.2267(a)(2), for example, MA organizations and Part D sponsors must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern with deferring to OCR requirements, arguing that those are broader and less specific to Medicare populations. A few commenters noted that MA and Part D requirements are more explicit and supportive of Medicare beneficiaries than OCR's requirements. A commenter noted that the current CMS NoA requirements are clear and prescriptive, requiring CMS's NoA to be included on all CMS required documents, which promotes clarity and consistency for operations and compliance. The commenter explained that while some of the OCR's NoA categories are straightforward, others are subjective and require detailed, document-level interpretation which MA organizations and Part D sponsors would be required to evaluate for all CMS required documents. Another commenter expressed concern that certain CMS-required materials, such as the Mid-Year Change Notifications, Star Ratings Document, and Federal Contracting Statement, would not include the NoA under OCR's requirements. Another commenter requested CMS collaborate with OCR to limit the number of required communications OCR's NoA must be included in, arguing costly printing and a poor enrollee experience and recommended that CMS require the inclusion of the NoA in the Annual Notice of Change (ANOC), Evidence of Coverage (EOC), Explanation of Benefits (EOB), and Summary of Benefits documents.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands commenters' concerns regarding the minor differences in OCR and CMS's current NoA requirements. However, CMS notes that language access notification requirements have historically been updated based on OCR's language access requirements. Most recently, in the April 2024 final rule, CMS updated its notice requirements from the MLI to the NoA to align with proposed changes to OCR's language access notifications. Furthermore, OCR is the HHS component responsible for implementing and enforcing the HHS civil rights regulations at Section 1557 and 45 CFR 92.11 and their requirements currently include many pertinent and important materials. CMS disagrees with commenters that OCR's requirements are less specific to Medicare beneficiaries or less detailed than CMS's requirements. Some examples, as listed in OCR requirements at 45 CFR 92.11(c)(5), include that the NoA is required to be included on application and intake forms, and communications related to an individual's rights, eligibility, benefits, or services that require or request a response from a participant, beneficiary, enrollee, or applicant. OCR also requires the NoA to be provided annually to participants, beneficiaries, enrollees (including late and special enrollees), and applicants of a covered entity's health program or activity, per 45 CFR 92.11(c)(1), and upon request, per 45 CFR 92.11(c)(2). To streamline regulatory processes and limit duplicative guidance and enforcement, deferring to OCR with respect to Title VI, Section 504, and/or ACA Section 1557 requirements related to notification for language assistance services and auxiliary aids and services, as required by 45 CFR 92.11, will ensure MA organizations and Part D sponsors have clear guidance on civil rights requirements. CMS notes that, although the OCR requirements do not specifically define the applicable CMS materials, OCR's NoA requirements provide clear instructions on which materials should include OCR's NoA,
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters shared concerns that OCR's NoA requirement does not include the CMS requirement at §§ 422.2267(e)(31)(ii)(B) and 423.2267(e)(33)(ii)(B) that CMS's NoA be provided in additional languages if there are additional languages in a particular service area that meet the five percent service area threshold beyond the languages described in §§ 422.2267(e)(31)(i) or 423.2267(e)(33)(i), and that CMS's NoA must also be translated into those languages. One commenter was concerned about the impact on local populations with LEP that may no longer receive notices in their primary language, leading to barriers to coverage.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands commenters' concern regarding the five percent service area threshold. CMS notes that while the OCR requirement does not include this additional five percent service area threshold requirement, OCR's current requirement at 45 CFR 92.11(b) requires “at least the 15 languages most commonly spoken by individuals with limited English proficiency of the relevant State or States in which a covered entity operates.” MA organizations and Part D sponsors are permitted to include additional languages in OCR's NoA beyond this requirement. Furthermore, under CMS requirements at §§ 422.2267(a)(2) and 423.2267(a)(2), for all required materials and content under §§ 422.2267 and 423.2267, MA organizations and Part D sponsors must, “[f]or markets with a significant non-English speaking population, be in the language of these individuals.” Specifically, MA organizations and Part D sponsors “must translate required materials into any non-English language that is the primary language of at least 5 percent of the individuals in a plan benefit package (PBP) service area,” and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4). These requirements are also applicable to cost plans pursuant to § 417.428.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters who opposed this proposal had concerns 
                        <PRTPAGE P="17473"/>
                        about how this rescission would impact MA organizations and Part D sponsors. A commenter expressed concern the proposal would result in MA organizations and Part D sponsors needing to hire more translators, increased call center volume and a re-allocation of resources to address these changes, which would disproportionally impact smaller MA organizations and Part D sponsors. Another commenter, while appreciative of the effort to streamline communication requirements, was concerned the proposal would inadvertently create increased complexity and introduce additional compliance risks for MA organizations and Part D sponsors. Another commenter recommended CMS revert to CMS' MLI requirement, arguing that the language requirement to include the top 15 non-English languages nationally was less burdensome to MA organizations and Part D sponsors, less costly and better for beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS maintains the position that the duplicative nature of these requirements may result in potential confusion and burden for MA organizations and Part D sponsors and beneficiaries as well as resulting in additional regulatory updates, and corresponding burdens as policy evolves. While CMS understands concerns regarding adapting to the requirements, CMS notes that OCR currently oversees its Title VI, Section 504, and/or ACA Section 1557 NoA requirements. Under this proposal, CMS is solely removing a duplicative requirement and deferring to OCR, the agency responsible for implementing these civil rights requirements at 45 CFR 92.11. Additionally, CMS believes that MA organizations and Part D sponsors will benefit from more centralized and streamlined civil rights guidance, especially those organizations whose operations include more insurance products than Medicare Advantage and Medicare prescription drug plans.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters highlighted the impact on SNPs and their enrollees, citing the potential for regulatory inconsistency. One commenter noted that, for D-SNPs, coordination with state Medicaid requirements is still applicable and that rescinding the NoA could create problems with enrollment in D-SNPs, who would still be subject to notice requirements in the State Medicaid Agency Contract (SMAC) or State statute. Another commenter noted while CMS's NoA requirement will exist for D-SNPs, for non-D-SNPs, beneficiaries could be harmed in their ability to fully understand and comprehend complex information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges that D-SNPs would still be required to follow the Medicaid requirement under § 438.10(d)(2), as described above. By removing the NoA requirements under §§ 422.2267(e)(31) and 423.2267(e)(33), D-SNPs will only need to consider applicable Medicaid and OCR language access notification requirements, which CMS believes will reduce the administrative burden on D-SNPs of complying with MA and Part D, Medicaid and OCR notification requirements concerning language access services and auxiliary aids and services.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters praised the current CMS NoA requirement burden reduction, by allowing MA organizations and Part D sponsors at §§ 422.2267(e)(31)(ii)(F) and 423.2267(e)(33)(ii)(F), to only provide one notice when mailing multiple required materials together. One commenter noted OCR does not have this requirement, which may result in a higher volume of mail and redundancy for MA organizations, Part D sponsors, and enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' insight on the benefits of mailing one notice with multiple required materials. In alignment with CMS's rationale to reduce duplication, CMS's goal with this proposal is to further streamline requirements for MA organizations and Part D sponsors and to prevent beneficiaries being inundated with duplicative notices. OCR's regulations implementing section 1557 of the Affordable Care Act separately require recipients of Federal financial assistance, such as MA organizations and Part D sponsors, to provide an NoA in certain circumstances as set forth in 45 CFR 92.11, including in specified electronic and written communications listed under § 92.11(c)(5). CMS notes that while OCR's requirements do not explicitly permit MA organizations and Part D sponsors to provide one notice when mailing multiple required materials as in §§ 422.2267(e)(31)(ii)(F) and 423.2267(e)(33)(ii)(F), doing so is not explicitly prohibited by OCR's requirements at 45 CFR 92.11.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter argued that CMS did not provide a sufficient rationale for why previously cited concerns about language barriers for beneficiaries are outweighed by potentially confusing regulations for MA organizations and Part D sponsors. Another commenter disagreed with CMS that OCR's requirement was duplicative, citing CMS's rationale in the April 2024 final rule that OCR's requirements were insufficient to protect beneficiaries and stated that CMS has not provided a rationale to reverse these statements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in the Contract Year 2027 proposed rule, eliminating CMS's NoA requirement under §§ 422.2267(e)(31) and 423.2267(e)(33) will ensure consistency and clarity for covered entities as any Title VI language access services and Section 504 auxiliary aids and services notification requirements required by 45 CFR 92.11 will be addressed by OCR, which is responsible for enforcing civil rights laws with respect to HHS programs. OCR is the HHS component that implements and enforces civil rights requirements, and CMS will defer to OCR's oversight, management, and enforcement of any Title VI, Section 504, and/or ACA Section 1557 requirements related to notification for language assistance services and auxiliary aids and services at 45 CFR 92.11. Regarding CMS's previous rationale, in the April 2024 final rule, CMS referenced the discussion from the May 2022 final rule that “relying on the requirements delineated in the 2020 section 1557 final rule for covered entities to convey the availability of interpreter services is insufficient.” 
                        <SU>61</SU>
                        <FTREF/>
                         In OCR's 2020 section 1557 final rule, they rescinded their language access notification requirements, known as “taglines.” Since that time, in May 2024, OCR finalized new rules implementing their NoA requirements,
                        <SU>62</SU>
                        <FTREF/>
                         after proposing these changes in their 2022 section 1557 proposed rule.
                        <SU>63</SU>
                        <FTREF/>
                         CMS had already updated its NoA requirements in the April 2024 final rule to align its requirements with OCR's based on OCR's 2022 section 1557 proposed rule. While these requirements are now aligned, CMS is concerned about the redundancy of these requirements and is taking the prudent step to defer to OCR for oversight of Title VI and/or ACA Section 1557 language access requirements at 45 CFR 92.11. CMS reiterates that it has other language-based requirements, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, that remain in effect that provide a level of protection to non-English speaking beneficiaries. Under §§ 422.2267(a)(2) and 423.2267(a)(2), for example, MA organizations and Part D sponsors must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan 
                        <PRTPAGE P="17474"/>
                        benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4).
                    </P>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             89 FR 30529
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             89 FR 37522
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             87 FR 47824
                        </P>
                    </FTNT>
                      
                    <P>
                        <E T="03">Comment:</E>
                         One commenter described the legal foundation for the requirement for covered entities to notify individuals of the availability of language assistance services, citing Title VI of the Civil Rights Act of 1964, Section 1557 of the Affordable Care Act, and the implementing regulations at 45 CFR 92.11. The commenter stated that these statutory requirements cannot be overridden by executive orders, and that they cannot nullify civil rights protections established by statute. The commenter noted that the July 2025 Attorney General memorandum cited by CMS does not eliminate Section 1557 requirements and argued that these legal requirements exist because meaningful access to healthcare services requires that individuals first know that language assistance is available to them.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS clarifies that rescinding the CMS required NoA should not be construed as the Agency taking a position on the laws and regulations cited by the commenter. Rather, CMS's decision to rescind CMS's NoA requirements under §§ 422.2267(e)(31) and 423.2267(e)(33) is due to concerns previously expressed in this preamble, including the duplicative nature of CMS and OCR's requirements and the corresponding burden placed on MA organizations and Part D sponsors to ensure compliance with NoA requirements from CMS and OCR. OCR is also the HHS component responsible for implementing and enforcing Title VI, Section 504, and/or ACA Section 1557 notice requirements as required by 45 CFR 92.11. CMS has other language-based requirements, promulgated for programmatic reasons related to the operation of the Medicare program pursuant to its authority under the Social Security Act, that remain in effect that provide a level of protection to non-English speaking beneficiaries. Under §§ 422.2267(a)(2) and 423.2267(a)(2), for example, MA organizations and Part D sponsors must translate required materials into any non-English language that is the primary language of at least 5 percent of individuals in a plan benefit package service area, and under §§ 422.2267(a)(3) and 423.2267(a)(3), upon request or when otherwise learning of an enrollee's primary language, provide non-English materials in any non-English language identified in §§ 422.2267(a)(2), 423.2267(a)(2), 422.2267(a)(4), and 423.2267(a)(4).
                    </P>
                    <P>After considering the comments received and for the reasons outlined in the Contract Year 2027 proposed rule and in responses to public comments, CMS is finalizing the rescission of CMS's NoA requirements at §§ 422.2267(e)(31) and 423.2267(e)(33) as proposed.</P>
                    <HD SOURCE="HD2">I. Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Section 423.505(e) authorizes CMS to evaluate, through audit, inspection, or other means, the appropriateness of services furnished to Medicare enrollees under a Part D contract. Consistent with this authority, CMS conducts Part D prescription drug event (PDE) record review audits under the Center for Program Integrity (CPI) that identify improper PDE records paid under the Medicare Part D benefit, herein referred to as Part D program integrity PDE record review audits, including instances in which the drug, item, or service does not meet the definition of a covered Part D drug under section 1860D-2(e) of the Act. As part of these audits, CMS identifies PDE records that it believes are potentially improper, and plan sponsors submit supporting documentation to rebut this finding and demonstrate that the drug, item, or service was appropriate for coverage under the Medicare Part D program. If CMS determines based on a review of this documentation that Medicare Part D rules and regulations were not met and therefore the PDE is improper, CMS notifies the Part D plan sponsor to submit PDE deletion or adjustment records for the associated record(s) in accordance with § 423.325(a)(2) and subregulatory guidance. The deleted PDE records result in savings to the Medicare Trust Fund when the PDE record for a given plan year is included in that plan year's global reopening, described at § 423.308 and § 423.346(a)(2).</P>
                    <P>Currently, Part D plan sponsors have one opportunity to submit documentation demonstrating that a PDE record was appropriate for coverage under the Part D program, which occurs during the audit itself. Because there is currently no process for Part D plan sponsors to further appeal determinations that a PDE record was improper, we proposed to establish a three level appeals process for Part D program integrity PDE record review audits (90 FR 54962). Specifically, we proposed to amend 42 CFR part 423 subpart Z, which currently outlines the Recovery Audit Contractor (RAC) Part D appeals process, to include any Part D program integrity PDE record review audits. We also proposed several conforming revisions to achieve alignment and streamlining of the Part D program integrity PDE record review audit appeals processes. Under this revised appeals process, Part D plan sponsors would receive an audit close out letter including: (1) an explanation of the drug, item, or service under audit; (2) a high-level overview of improper and proper PDE record counts; (3) an attached PDE level record file denoting improper and proper PDE records; (4) requirements for the submission of deletion records or adjustment records for the PDEs determined to be improper; and (5) instructions on how the Part D plan sponsor may appeal the findings. There would be no minimum threshold for an appeal at any level.</P>
                    <HD SOURCE="HD3">2. Appeals Process</HD>
                    <P>In this final rule, we are codifying at 42 CFR part 423 subpart Z changes to the existing RAC appeals process to include any CMS Part D program integrity PDE record review audits. To reflect the proposed expansion of the appeals process, we proposed to revise the regulatory text title of subpart Z from “Recovery Audit Contractor Part D Appeals Process” to “Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits”. This change will establish an appeals process for Part D plan sponsors to appeal findings for Part D program integrity audits conducted by CMS that review PDE records for appropriateness.</P>
                    <P>Currently, 42 CFR part 423 subpart Z sections 423.2600 to 423.2615 describe what may or may not be subject to appeal and the processes for each of the three levels of appeal, which include: (1) request for reconsideration, (2) hearing official review, and (3) review by the Administrator. In alignment with the proposed changes to the scope of subpart Z, we proposed to remove from these regulations any mention of the RACs specifically, as the proposed appeals process would include any Part D program integrity audits that review PDE records for appropriateness (90 FR 54962).</P>
                    <P>
                        Furthermore, the proposed modifications would serve to establish review timeframes for the different review entities at each level of appeal. The RAC Part D payment audits recovered improper payments from Part D plan sponsors through the monthly capitation payment; and therefore, could recover funds at any time without constraints. As such, the current 
                        <PRTPAGE P="17475"/>
                        regulatory text for the RAC audit appeals did not have a need to require that the independent reviewer make their decision within a certain timeframe. However, current Part D program integrity PDE record review audits require the plan sponsors to submit deletion records to CMS for all PDE records deemed improper during audit, in accordance with § 423.325(a)(2) and prior to the global reopening for any given plan year, to ensure the integrity of the Medicare Trust Fund. As explained in the proposed rule, for these reasons, we believe it is necessary to provide timeframes for decisions to be made at each appeal level (90 FR 54962). We believe that three levels of appeal, with review timeframes, would allow sufficient opportunity for Part D plan sponsors to appeal a determination and ensure that timely and accurate determinations are made consistent with the rules and regulations of the Part D program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the addition of an appeals process for the Part D program integrity PDE record review audits. A commenter requested CMS consider establishing a standard timeframe by which PDE record review audits must be completed, so that plans receive findings or recommendations and delete improper PDE records accordingly.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We proposed specific timeframes for completion of each step of the appeals process (90 FR 54962). CMS thanks the commenter for this feedback. While audit completion timelines are outside the scope of this provision, we will consider this feedback separately.
                    </P>
                    <HD SOURCE="HD3">a. Payment Appeals (§ 423.2600)</HD>
                    <P>The current payment appeals language at § 423.2600 describes for the Part D plan sponsor what is or is not considered appealable during a RAC payment audit. In alignment with our proposal to broaden the scope of subpart Z to include CMS [Part D program integrity PDE record review audits], we also proposed to amend the language describing what is or is not considered appealable to reflect the scenarios that apply to Part D program integrity PDE record review audits (90 FR 54962). As such, we proposed to modify the existing regulatory language at § 423.2600 to state Medicare Part D plan sponsors may appeal program integrity prescription drug even record review audit determinations. We proposed to add a new paragraph (a) to § 423.2600, which would identify the issues that may be appealed through the audit appeals process. Specifically, under (a) Issues eligible for appeal, we proposed to add paragraph (a)(1) to state CMS's application of Part D policy(ies). Part D policy(ies) refer to any Part D sponsor requirement from CMS outlined in the Code of Federal Regulations (CFR), CMS manuals, or other communications from CMS. Proposed paragraph (a)(2) would specify that Part D sponsors may appeal factual or data errors. Examples of appealable issues at (a)(1) or (a)(2) would include: (1) a determination that a drug, item or service was excluded from coverage under the Medicare Part D program; or (2) a determination that a Medicare Part D payment was a duplicate payment. Errors of this nature would be appealable given there would be documentation for the reviewers to review to ensure that the payment was proper under the Medicare Part D benefit. The independent reviewer would review the documentation to determine and ensure that the payment was proper and in accordance with Medicare Part D policies. Furthermore, the independent reviewer may also determine, based on documentation deleted, whether the error resulted from actions made by CMS.</P>
                    <P>We proposed to further amend § 423.2600 by adding a new paragraph (b), which would identify issues ineligible for appeal (90 FR 54962). Proposed paragraph (b)(1) would specify that Part D plan sponsors may not appeal the failure to submit documentation in the timeframes specified by CMS during the audit. Failure to submit documentation would not be appealable, given the plan sponsor has the opportunity to provide the documentation to CMS for review within a specified audit timeframe. Historically, during Part D program integrity PDE record review audits, the audit timeframes are extended due to the documentation lacking specific information needed to evaluate the PDE records' appropriateness. This greatly affects the overall length of the audit and causes undue burden on both the plan sponsor and CMS. Therefore, CMS proposed to require that plan sponsors provide documentation in accordance with the proposed provisions the proposed rule that proposed updates at § 423.505, and accordingly, failure to provide this information would result in an improper determination that is not appealable. Providing documentation in accordance with the provisions proposed at § 423.505 will greatly reduce the burden and overall audit timeline for both CMS and Part D plan sponsors, as CMS will not have to request additional information from the plan sponsors. Proposed paragraph (b)(2) would state that Medicare Part D plan sponsors may not appeal the program integrity PDE record review audit methodology. That is, while CMS's application of Part D policy(ies) and factual or data errors may be appealed, the Part D plan sponsor may not appeal the underlying audit methodology, such as the manner in which data was extracted.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for CMS's proposal to introduce a structured appeals process for PDE record review audits, stating the proposal represents a step toward ensuring fairness, transparency, and due process for Part D sponsors. Furthermore, the three-tiered appeal structure and defined timelines will improve predictability and compliance planning. This commenter also believes that the process as proposed has some limitations, including the scope, burden/timelines, adequate evidence standards, technology enablement, and compliance risks.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support for this provision but disagree with the commenter regarding the limitations of the appeals process. For the three levels of appeals, CMS will not allow additional documentation to be considered during an appeal. It is essential for plans to provide all documentation needed to support coverage under the Medicare Part D benefit at the time of submission. As CMS has previously explained, the issues that are appealable under this process include CMS's application of Part D policy(ies) and factual or data errors because there would be documentation to review to ensure that the payment was proper under the Medicare Part D benefit. CMS has been granting, and will continue to grant, plan sponsors extensions to submit initial documentation when requested. Requests are often made due to plan sponsors' involvement in other concurrent CMS audits or large universe sample size. In addition, the audit methodology is not subject to appeal under our proposed policy.  
                    </P>
                    <P>Regarding the commenter's concerns about the lack of technology enablement or digital submission capabilities and a standardized tracking platform, CMS reminds commenters that a standard system is in place, and CMS utilizes a secure online portal for all steps of aforementioned Part D PDE Record Review Audits.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported efforts to improve audit consistency but was concerned that some of the proposed requirements could create onerous obligations and risk PDE record deletion. Other commenters believed 
                        <PRTPAGE P="17476"/>
                        that the proposals in section IV.D. of the proposed rule to “Strengthen Documentation Standards for Part D Plan Sponsors” would involve collecting information not typically available to plans. An example was the identity of the person who submitted the request at the provider's office, which is not information currently collected or easy to retroactively collect if that information is not submitted to the plan, particularly if it comes from a larger provider office or group. Another commenter expressed concern that if this information is not available and documented, then upon audit the PDE record would be marked improper, and the PDE record determination would also be unable to be appealed by the plan sponsor.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate this concern and assure the commenters that, under this approach, we will review the case file in its entirety and will not require PDE deletions simply because a specific piece of information that does not impact the determination is missing. CMS has clarified that the documentation requirements included in this rule will account for scenarios in which certain information, such as the identity of the requestor, may not be available or not retrievable. CMS also clarifies that if the plan sponsor believes that the information in the case file documentation is sufficient to ensure payment under the Medicare Part D benefit is appropriate, this scenario would be appealable on the basis of “factual or data errors.” In addition, CMS reminds the commenter that supporting documentation is not appealable in the instance where a plan sponsor fails to submit a full case file within the audit timeframe specified. This is to ensure that plan sponsors provide CMS complete and accurate case files to avoid unnecessary delays in the audit.
                    </P>
                    <HD SOURCE="HD3">b. Reconsiderations (§ 423.2605)</HD>
                    <P>In existing paragraph (a), we proposed to replace the term “demand letter” with the term “close out letter” for consistency with current terminology in CMS's Part D program integrity PDE record review audits. In existing paragraph (e), we proposed to add a timeframe for when the independent reviewer's decision needs to be decided and communicated to the Part D plan sponsor and CMS. Specifically, we proposed to amend the language from “[t]he independent reviewer informs CMS and the Part D plan sponsor of its decision in writing” to “the independent reviewer decides the reconsideration within 60 calendar days after the timeframe for filing a rebuttal has expired, and sends a written decision to the Part D plan sponsor and CMS, explaining the basis for the decision.” Adding a timeframe for the independent reviewer's decision gives CMS the opportunity to ensure that any upheld improper PDE records can be submitted as a deletion record by the plan sponsor within the global reopening timeframe.</P>
                    <HD SOURCE="HD3">c. Hearing Official Review (§ 423.2610)</HD>
                    <P>In the existing regulatory text at § 423.2610, CMS outlines the process for a hearing official review. We proposed to revise paragraph (d)(2)(i), to replace “Part D RAC” with “CMS” for consistency with the changes, discussed previously, regarding the audits to which these appeals processes apply. We proposed to revise paragraph (d)(3) to remove the phrase “nor CMS may submit” and replace it with “nor CMS is permitted to submit” to establish stronger verbiage that the submission of new evidence is not permitted by either the plan sponsor or by CMS and will not be considered by the hearing official. In addition, we proposed to revise paragraph (e), to replace “60 days” with “60 calendar days after the timeframe for filing a rebuttal has expired,” to be explicit that 60 days refers to calendar days rather than business days. Furthermore, we proposed to revise paragraph (f), to replace the existing language that states “§ 423.2610” with “§ 423.2615”, to fix a citation error in the existing regulatory text. The existing text in paragraph (f) refers to the hearing official's decision being binding unless overturned in the third level of appeal by the CMS Administrator. The Administrator level of appeal is found at § 423.2615 not at § 423.2610, and therefore, the citation needs to be corrected.</P>
                    <HD SOURCE="HD3">d. Review by the Administrator (§ 423.2615)</HD>
                    <P>In the existing regulatory text at § 423.2615, CMS outlines the process for the review by the Administrator. We proposed to revise paragraph (b)(2) to remove the phrase “nor CMS may submit” and replace it with “nor CMS is permitted to submit” to establish stronger verbiage that the submission of new evidence is not permitted by either the plan sponsor or by CMS and will not be considered by the Administrator. In existing paragraph (d), we proposed to replace “45 days” with “30 calendar days.” Furthermore, in existing paragraph (e), we proposed to add a 45-calendar day timeframe for the Administrator to furnish a final decision. Specifically, the regulatory text will be amended to read, “If the CMS Administrator agrees to review the hearing official's decision, he or she determines, after reviewing the hearing record and any arguments submitted by the Part D plan sponsor or CMS in accordance with this section, whether the determination should be upheld, reversed, or modified. The CMS Administrator furnishes a written decision, which is final and binding, to the Part D plan sponsor and CMS within 45 calendar days after the timeframe for filing a rebuttal has expired.” Both reducing the timeframe for the Administrator to decide if they will review the case and adding a timeframe for furnishing a final decision would help ensure that any upheld improper PDE records can be submitted as a deletion record by the plan sponsor within the global reopening timeframe. The timeframes proposed are critical to ensure the appeals process is completed by the PDE submission deadline for the global reopening. Completion within the global reopening timeframe enables CMS to properly oversee the Medicare Part D program by ensuring CMS has accurate, complete, and truthful claims data, in accordance with § 423.505(k)(3), and to protect the integrity of the Medicare Trust Fund.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter appreciated that the appeals process for PDE record review audits does not create extra burden or require changes to the current process for plan sponsors. The commenter welcomed guidance on the steps and timelines required for each level of appeal. Several other commenters supported the establishment of an appeals process, stating it would enhance transparency and promote greater fairness in the audit process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their support of the proposal. Additional information regarding each level of appeal will be provided through program instruction or otherwise.
                    </P>
                    <P>After consideration of the comments received and for the reasons outlined in the proposed rule and our responses to those comments, we are finalizing our proposal to update the existing appeals process at 42 CFR part 423 subpart Z to include any CMS Part D program integrity PDE record review audits, without modification.</P>
                    <HD SOURCE="HD2">J. Prescription Drug Event Submission Timeliness Requirements (§ 423.325)</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>
                        CMS codified its requirements for the timely submission of prescription drug event (PDE) records at 42 CFR 423.325 in the final rule titled “Medicare and Medicaid Programs; Contract Year 2026 
                        <PRTPAGE P="17477"/>
                        Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly,” which appeared in the April 15, 2025, 
                        <E T="04">Federal Register</E>
                         (hereinafter referred to as the April 2025 final rule). In that rule, we described the General PDE Submission Timeliness Requirements at § 423.325(a) and the Selected Drugs PDE Submission Timeliness Requirement at § 423.325(b).
                    </P>
                    <P>Under the General PDE Submission Timeliness Requirements, a Part D sponsor must submit an initial PDE record within 30 calendar days from the date the Part D sponsor receives the claim, submit adjustment or deletion PDE records within 90 calendar days of the discovery or notification of an issue requiring a change to the previously submitted PDE records, and resolve rejected PDE records within 90 calendar days of the rejection. The General PDE Submission Timeliness Requirements apply unless the Selected Drugs PDE Submission Timeliness Requirement is applicable, which requires a Part D sponsor to submit an initial PDE record for a selected drug (as described at section 1192(c) of the Act) within 7 calendar days from the date the Part D sponsor receives the claim.</P>
                    <P>In this rule, we proposed to modify the General PDE Submission Timeliness Requirements by modifying existing § 423.325(a)(3) related to the submission of PDE records to resolve a rejected PDE record. Under the current rule, Part D sponsors must submit a revised PDE record to resolve a PDE record that CMS rejected through the PDE editing process within 90 calendar days of the receipt of rejected record status from CMS. We recognize that submission of a revised PDE record is not always appropriate. As the regulation is currently written, a Part D sponsor may not be able to comply with the current rule under various scenarios. Therefore, we proposed to set forth new requirements related to the resolution of rejected PDE records.</P>
                    <HD SOURCE="HD3">a. Rejected PDE Records</HD>
                    <P>
                        Part D sponsors submit PDE records to CMS through the Drug Data Processing System (DDPS). The DDPS performs checks on the data to help ensure its accuracy, including checks for missing and invalid information, beneficiary eligibility, and calculation checks on costs and payment fields.
                        <SU>64</SU>
                        <FTREF/>
                         These checks can result in the PDE data being accepted or rejected by the DDPS. Consistent with our long-standing guidance 
                        <SU>65</SU>
                        <FTREF/>
                         and pursuant to § 423.325(a)(3), Part D sponsors must resolve those rejections within 90 calendar days, that is, resubmit corrected PDE records to CMS within 90 calendar days of receiving the rejection.
                    </P>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             See generally, DDPS Edit Spreadsheet, at 
                            <E T="03">https://www.csscoperations.com/internet/csscw3.nsf/DIDC/FGSMOX8LWK~Prescription%20Drug%20Program%20(Part%20D)~References.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             HPMS memorandum, 
                            <E T="03">Revision to Previous Guidance Titled “Timely Submission of Prescription Drug Event (PDE) Records and Resolution of Rejected PDEs”,</E>
                             October 6, 2011, available at 
                            <E T="03">https://www.cms.gov/httpseditcmsgovresearch-statistics-data-andsystemscomputer-data-and-systemshpmshpmsmemos-archive/hpms-memo-qtr1-4.</E>
                        </P>
                    </FTNT>
                    <P>CMS recognizes there are a range of situations where it might be inappropriate to submit a revised PDE record after receiving a rejection. For example, if a rejected record is no longer associated with a valid claim, it would not be appropriate for the Part D sponsor to submit a corrected PDE record. A valid claim would not exist, for example, if a pharmacy reversed the claim and returned the drug to stock because the beneficiary never obtained the prescription.</P>
                    <P>Likewise, if the PDE record that was rejected should never have been submitted to CMS in the first instance because the record was contrary to CMS's requirements, it would not be appropriate to resubmit a PDE record that continues to be contrary to CMS's requirements. For example, if a PDE record was rejected because the prescriber listed on the applicable claim is on the HHS-OIG's List of Excluded Individuals/Entities (LEIE) without an applicable waiver, CMS does not expect that the Part D sponsor would resubmit the PDE record listing an excluded prescriber without an applicable waiver.</P>
                    <P>As reflected in the scenarios described in this Background, it may not be appropriate to resolve every PDE rejection with submission of a revised PDE record. The submission of a PDE record implies that there was and continues to be a valid claim. Resubmission of a previously rejected PDE record associated with an invalid claim could be harmful to the Part D program. Such data could inadvertently cause problems with the analysis of the rejected data, with no visibility into why such rejected data was never corrected.</P>
                    <P>In addition, due to operational constraints, it is not possible for the Part D sponsor to “delete” the rejected PDE record to avoid non-compliance with the requirement when these scenarios arise. CMS's DDPS does not allow Part D sponsors to submit PDE deletion records associated with rejected PDE records.</P>
                    <HD SOURCE="HD3">2. Requirements</HD>
                    <P>As explained earlier, CMS does not have insight into all of the reasons why a Part D sponsor might not submit a revised PDE record to resolve rejected PDE records. Ensuring greater transparency regarding the status of rejected PDE records would enhance CMS's oversight of Part D sponsors' compliance with PDE submission timeliness requirements. We proposed to modify the existing regulation at § 423.325(a)(3) to account for the scenarios described in the Background, increase transparency, and construct the requirement to account for circumstances where resubmission of PDE records is not appropriate.</P>
                    <P>We proposed that Part D sponsors must submit a PDE record within 90 calendar days from receipt of the rejection and within every 90 calendar days thereafter until a revised PDE record is accepted unless the claim associated with the rejected PDE record is reversed or deleted, or the PDE record is otherwise found to have been submitted in error. We believe that submissions at least once every 90 calendar days will allow CMS to know that the rejected PDE record continues to reflect an active claim that the sponsor believes is valid and for which the sponsor is working to resolve the bases for the PDE rejection. The sponsor is not required to submit revised PDE records at least once every 90 calendar days, if the claim associated with the rejected PDE record is reversed or deleted, or the PDE record is otherwise found to have been submitted in error. This additional information will provide CMS with greater insight into the PDE revision process and ensure that a rejected PDE record must be corrected by the plan sponsor unless it is not appropriate to do so.</P>
                    <P>CMS believes that it is beneficial for program integrity for the agency to have increased visibility into the processing and progression of revisions of rejected PDE records. This includes ensuring that rejected PDE records that are not resubmitted within 90 days, in accordance with § 423.325(a)(3), are limited to claims that are no longer active and where resubmission is inappropriate (because, for example, the pharmacy has since reversed the claim).</P>
                    <P>
                        We note that since 2011, the vast majority of the PDE records that are rejected are resolved by sponsors within the 90-day timeframe, and in more recent years, nearly all the PDE rejections are resolved within the 90-day timeframe. Therefore, CMS expects 
                        <PRTPAGE P="17478"/>
                        no additional costs or savings from the proposed change and is not scoring these requirements in the Regulatory Impact Analysis section. There are no new reporting requirements.
                        <SU>66</SU>
                        <FTREF/>
                         We do not anticipate additional paperwork burden. Therefore, no increase is included in the Collection of Information section.
                    </P>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             
                            <E T="03">See</E>
                             OMB 0938-0982, CMS-10174, expiration April 30, 2027 (available at 
                            <E T="03">https://www.reginfo.gov/public/do/PRAViewDocument?ref_nbr=202403-0938-002</E>
                            ).
                        </P>
                    </FTNT>
                    <P>In the proposed rule, we welcomed feedback on these proposed changes.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed their support for CMS's proposal to revise the general PDE submission timeliness requirements specified in § 423.325(a)(3).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters believed that CMS's proposal was burdensome. One commenter was concerned about potential downstream impacts on contracted pharmacy audit partners and pharmacies, as the proposed requirements would necessitate changes to current research processes related to rejected PDE records.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in our proposed rule and this final rule, since 2011, the vast majority of the PDE records that are rejected are resolved by sponsors within the current 90-calendar-day timeframe. In recent years, nearly all PDE rejections are resolved within this period. The current regulation already requires sponsors to submit a revised PDE record to resolve a rejected PDE within 90 calendar days of the rejection. To the extent rejected PDE records result in claims adjustments to address and resolve these PDE rejections, sponsors are already collaborating with their pharmacy partners, and therefore, we do not believe that our provision will necessitate changes to the current research processes related to PDE records. Therefore, we disagree with the commenters that our proposed rule is burdensome.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters stated that the proposal would not provide CMS with additional insight into the underlying status of the rejected PDE records and believed that it would be beneficial for CMS to have a definitive claim status. Commenters recommended alternatives to gain visibility into the status of a claim associated with a rejected PDE record. Some commenters encouraged CMS to consider adopting mechanisms to promote information sharing about the status of a claim associated with a rejected PDE record within the existing PDE record review process, under which CMS flags PDE records and requests additional information from sponsors. Other commenters recommended that CMS create new functionality in the PDE to allow the submitter to inform CMS that the previously rejected PDE is for a claim that has been reversed or has been deemed invalid by the sponsor. One commenter recommended the creation of a new deletion code value (or another field or new value for a field) for the sponsor to specifically inform CMS the claim has been reversed or has been deemed invalid. A commenter noted that such a mechanism could have benefits beyond the intent of the proposal.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the recommendations for alternative approaches and acknowledge that these suggestions may provide CMS with more definitive information regarding the status of the claim associated with a rejected PDE record. However, our proposal achieves our goals. As we stated in both the proposed rule and in this final rule, we recognize that submission of a revised PDE record in accordance with the current rule is not always appropriate, and a sponsor may not be able to comply under various scenarios. The new requirements we proposed account for these scenarios, increase transparency, and address circumstances where resubmission of PDE records is not appropriate.
                    </P>
                    <P>We considered the recommendations from commenters regarding alternatives to promote visibility into the status of a claim associated with a rejected PDE record that they believe would provide a clearer understanding of the status of the claim associated with the rejected PDE record. After careful thought, we concluded that the proposed alternatives—such as additional analysis, outreach to sponsors, and responses from sponsors, or modifications to the PDE file layout or the creation of new functionality in the PDE—would impose a greater burden on CMS and Part D sponsors compared to our proposal.</P>
                    <P>While we acknowledge that an alternative approach might yield more comprehensive information with benefits extending beyond the intent of this proposal, such considerations are beyond the scope of our proposed rule.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that certain PDE rejections cannot be resolved by sponsors because they do not have the ability to resolve the reject. These commenters pointed to plan-to-plan (P2P) PDE rejection edits, for example PDE Edit 706.
                        <SU>67</SU>
                        <FTREF/>
                         Commenters also stated that certain beneficiary enrollment and eligibility PDE rejection edits cannot be resolved by the sponsor and that the sponsor may be waiting for a response from CMS on a pending eligibility case prior to resolution of a PDE rejection.
                    </P>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             PDE Edit 706—PDE rejects when the Submitting Contract differs from Contract of Record and does not fall within a valid P2P period (Beneficiary is not enrolled in the Submitting Contract for the given DOS. PDE falls outside of the P2P period facilitated by CMS (greater of enrollment effective date with new Contract of Record + 30 days, or CMS process date + 30 days)). See DDPS Edit Spreadsheet, at 
                            <E T="03">https://www.csscoperations.com/internet/csscw3.nsf/DIDC/FGSMOX8LWK~Prescription%20Drug%20Program%20(Part%20D)~References.</E>
                        </P>
                    </FTNT>
                    <P>The commenters suggested that when a PDE rejects due to edits that the sponsor cannot resolve, CMS should assume no further action is needed by the sponsor. The sponsor should not be required to continue resubmissions of these PDE records and should be exempt from any compliance action. Additionally, commenters recommended that when PDE rejections occur due to enrollment or eligibility issues, CMS should assume no further action is needed by the sponsor, as there is no way to resolve the error. The sponsor should not be required to continue resubmissions of these PDE records unless enrollment or eligibility changes such that the sponsor would expect the resubmitted PDE record to be accepted by CMS.</P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that in some cases, our proposed rule will result in a sponsor repeatedly submitting PDE records that will not be accepted by CMS. Based on comments, we explored potential exclusions and exceptions of certain PDE rejection edits from our rule. In doing so, we considered our goal of transparency into claims status and the volume of PDE records impacted. Given that nearly all PDE rejections are resolved within 90 calendar days, our proposed rule will result in only a small percentage of PDE records being repeatedly submitted without resolution until DDPS closes 
                        <FTREF/>
                        <SU>68</SU>
                          
                        <PRTPAGE P="17479"/>
                        for the contract year of the PDE at issue. In addition, it is possible that a claim associated with a PDE record that continues to be rejected by CMS is later reversed by the pharmacy. Under that scenario, and consistent with the proposed rule, a sponsor would cease submission of the PDE records, indicating to CMS that the claim was reversed or deleted, or the PDE record that was rejected was otherwise found to have been submitted in error by the sponsor. As proposed, our rule gives us transparency into the status of claims associated with rejected PDE records and allows us to know whether sponsors are compliant with our PDE submission requirements. Therefore, we decline to exempt or exclude certain PDE rejection edits from our requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             CMS systems remain open to PDE data (adjustments, deletions, and new submissions) until the end of the 6-year overpayment look-back period. Defined in 42 CFR 423.360(f), the overpayment look-back period encompasses the 6 most recently completed payment years. This period is tied to the “applicable reconciliation,” which marks the annual deadline for submitting data for a Part D payment reconciliation, according to 42 CFR 423.360(a). Upon reaching the deadline for a Part D payment reconciliation (
                            <E T="03">i.e.,</E>
                             around June 30), the year being reconciled is included in the look-back period, and the earliest year leaves the look-back period. Consequently, from July 1 onward, sponsors are no longer able to submit PDE data for the year that has exited the look-back period. See, for example, the HPMS memorandum titled “Closing 
                            <PRTPAGE/>
                            the Drug Data Processing System (DDPS) for benefit year 2018”, dated April 11, 2025 (available at 
                            <E T="03">https://www.cms.gov/about-cms/information-systems/hpms/hpms-memos-archive-weekly/hpms-memos-wk-2-april-7-11</E>
                            ).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comme</E>
                        nt: A few commenters noted that CMS's proposal does not address situations where additional CMS guidance or clarifications are needed or when there is a known issue with PDE processing. In these cases, sponsors cannot resolve the errors until CMS takes action to resolve the issue. Commenters recommended that in such scenarios, CMS should allow sponsors to temporarily stop resubmitting the related PDE records until CMS issues additional guidance or corrections are made to DDPS. Furthermore, commenters suggested that CMS should provide a grace period, giving sponsors enough time to implement any necessary changes related to CMS guidance, clarifications, or DDPS changes. One commenter recommended a minimum grace period of 180 days. During this grace period, commenters suggested that the related PDE records should be exempt from any timeliness requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         PDE processing and editing can be complicated, and at times, CMS must correct system issues or release new or clarifying guidance for a valid PDE record to be accepted. Under these circumstances, it is still important for us to know if the rejected PDE record is associated with a paid claim or if the claim is reversed or deleted or the PDE that was rejected by CMS is otherwise found to have been submitted in error. In addition, compliance with our proposed rule allows us to understand the scope of the issue.
                    </P>
                    <P>We acknowledge that there would be various considerations given the nature and scope of an issue preventing acceptance of a valid PDE record. The resolution may or may not reasonably require a “grace period” for PDE submissions as suggested by the commenters. Each situation requiring us to take action to resolve a PDE editing issue will be individually assessed based on its unique circumstances. When necessary, we will provide guidance to clarify the requirements for the sponsors.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested guidance related to the proposed rule. A commenter sought guidance from CMS on when resubmission to correct a rejected PDE record is required. Another commenter requested that CMS clarify its expectations related to rejected PDE records that are actively under research or rework. A commenter also requested technical support and system testing for PACE organizations to ensure that the requirements could be met without disrupting participant care or operations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in this final rule, there are no exceptions or exemptions to our proposed rule. It is applicable to all rejected PDE records, including those that are actively under research or rework.
                    </P>
                    <P>We do not believe that CMS system testing is necessary for PACE organizations to comply with the requirements. Under the current regulations at § 423.325(a)(3), sponsors must submit a revised PDE record to resolve a CMS rejected record within 90 calendar days of the rejection. The proposed amendment to that rule will not result in disruptions to participant care or the operations of the PACE organization.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that the proposed rule did not address rejected PDE records sent to the Medicare Transaction Facilitator (MTF), which CMS uses to facilitate manufacturer effectuation of negotiated maximum fair prices (MFPs) under Part E of Title XI of the Act (sections 1191 through 1198 of the Act) through the exchange of data and, if applicable, the pass through of MFP refund payments between manufacturers and dispensing entities. One commenter highlighted that it would be beneficial for the MTF to receive information indicating a claim associated with a PDE record that was previously rejected is reversed, so that if an MFP refund has been paid to a pharmacy, it can be recouped by the manufacturer. Commenters encouraged CMS to provide information about such rejected PDE records to the MTF.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the feedback on our proposal and how it relates to the operations of the MTF for the purposes of the Medicare Drug Price Negotiation Program. While we value these insights, the operations of the MTF under the Medicare Drug Price Negotiation Program are beyond the scope of this regulation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter referenced CMS's memorandum dated July 3, 2013, PDE Guidance for Post Point-of-Sale Claim Adjustments.
                        <SU>69</SU>
                        <FTREF/>
                         The commenter stated that the proposal does not appear to clearly align with this guidance.
                    </P>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             HPMS memorandum, PDE Guidance for Post Point-of-Sale Claim Adjustments, July 3, 2013.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Response:</E>
                         Our July 3, 2013, PDE guidance for Post Point-of-Sale Claim Adjustments provided sponsors with information on determining the appropriate course of action for post point-of-sale (POS) adjustments to rectify errors under specific scenarios. The guidance explains how to adjust or delete PDE records that were previously accepted. Our proposal amends § 423.325(a)(3) related to rejected PDE records. The proposal does not amend the PDE submission timeliness requirements for adjustments or deletions of accepted PDE records addressed in § 423.325(a)(2). Although we believe that our proposed regulation text is clear, we have slightly modified the proposed regulation text to make clear that the amendment to § 423.325(a)(3) is limited to rejected PDE records for paid claim transactions. The revised § 423.325(a)(3) requires a sponsor to submit a PDE record for a paid claim transaction associated with a PDE record that was previously rejected by CMS at least once every 90 calendar days from receipt of a rejection until the PDE record is accepted unless the claim associated with the rejected PDE record is reversed or deleted, or the PDE record that was rejected is otherwise found to have been submitted in error.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the proposal to modify § 423.325(a)(3) with slight modifications to make clear that the requirements are related only to rejected PDE records.</P>
                    <HD SOURCE="HD2">K. Eligibility for Supplemental Benefits for the Chronically Ill (SSBCI) and Technical Changes to the Definition of Chronically Ill Enrollee (§ 422.102)</HD>
                    <P>
                        The Balanced Budget Act (BBA) of 2018 (Pub. L. 115-123) provided new authorities concerning supplemental benefits that may be offered to chronically ill enrollees in Medicare Advantage (MA) plans. CMS addressed these new supplemental benefits, now known as Special Supplemental Benefits for the Chronically Ill (SSBCI), extensively in the Medicare Program; Contract Year 2021 Policy and 
                        <PRTPAGE P="17480"/>
                        Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program (hereinafter referred to as the June 2020 final rule) (85 FR 33800 through 33805).
                    </P>
                    <P>
                        Supplemental benefits, including SSBCI, are generally funded using MA plan rebate dollars. MA rebate dollars may be used for mandatory, but not optional, supplemental benefits offered by the plan (§ 422.266(b)(1)).
                        <SU>70</SU>
                        <FTREF/>
                         When submitting an annual bid to participate in the MA program, an MA organization includes in its bid a Plan Benefit Package (PBP) and Bid Pricing Tool (BPT) for each of its plans, where the MA organization provides information to CMS on the premiums, cost sharing, and supplemental benefits (including SSBCI) it proposes to offer. Since the statutory amendment authorizing SSBCI and subsequent guidance in a Health Plan Management System (HPMS) memorandum dated April 24, 2019,
                        <SU>71</SU>
                        <FTREF/>
                         the number of MA plans that offer SSBCI—and the number and scope of SSBCI offered—has significantly increased.
                    </P>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             Rebates can also be used to buy down Part B and D premiums under § 422.266(b)(2) and (b)(3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             
                            <E T="03">https://www.cms.gov/medicare/health-plans/healthplansgeninfo/downloads/supplemental_benefits_chronically_ill_hpms_042419.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>Section 422.102(f)(4)(i) and (ii) requires that the MA plans have written policies for making SSBCI enrollment determinations, document that each enrollee eligible for SSBCI is a chronically ill enrollee, and provide this documentation to CMS upon request. As CMS described in Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024-Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE) (hereinafter referred to as the April 2024 final rule) (89 FR 30551), to offer an item or service as an SSBCI to an enrollee, an MA plan must make at least two separate determinations, with respect to that enrollee, in order to satisfy the statutory and regulatory requirements for these benefits.</P>
                    <P>First, the MA plan must determine that an enrollee is eligible for SSBCI by meeting the statutory definition of “chronically ill enrollee.” Section 1852(a)(3)(D)(iii) of the Act defines “chronically ill enrollee” as an individual enrolled in the MA plan who meets all of the following: (I) has one or more comorbid and medically complex chronic conditions that is life-threatening or significantly limits the overall health or function of the enrollee; (II) has a high risk of hospitalization or other adverse health outcomes; and (III) requires intensive care coordination. Per § 422.102(f)(1)(i)(B), CMS may publish a non-exhaustive list of conditions that are medically complex chronic conditions that are life-threatening or significantly limit the overall health or function of an individual. This list of chronic conditions is the same as the list for which MA organizations may offer chronic condition special needs plans (C-SNPs), which can be found in the definition of “severe or disabling chronic condition” within § 422.2. CMS does not further define “high risk of hospitalization” or “intensive care coordination.” As noted in the June 2020 Final Rule, plans have flexibility in determining what these phrases mean in a way that will best serve their enrollees. However, CMS noted some examples of methods through which plans may assess hospitalization risk or need for care coordination, such as conducting a health risk assessment, performing a retrospective claims review for an enrollee, or by other means the plan deems necessary. Second, the MA plan must determine that the SSBCI has a reasonable expectation of improving or maintaining the health or overall function of the enrollee. Section 422.102(f)(4)(iii)(A) requires that MA plans have and apply written policies based on objective criteria for determining a chronically ill enrollee's eligibility to receive a particular SSBCI. Section 422.102(f)(4)(v) further requires that MA plans maintain without modification, as it relates to an SSBCI, evidentiary standards for a specific enrollee to be determined eligible for a particular SSBCI, or the specific objective criteria used by a plan as part of SSBCI eligibility determinations for the full coverage year.</P>
                    <P>In the June 2020 final rule, CMS stated the expectation that plans communicate information to enrollees about the scope of SSBCI that the MA plan covers and who is eligible for those benefits in a clear manner (85 FR 33803). CMS made further changes in the April 2024 final rule, where CMS modified the disclaimer requirements at § 422.2267(e)(34) to require plans to include clear information about SSBCI eligibility criteria in marketing and communications materials that mention SSBCI, including by listing the chronic conditions an enrollee must have in order to be eligible for particular SSBCI. These actions and the changes to the regulation finalized here demonstrate the importance of transparency as it applies to SSBCI eligibility.</P>
                    <P>
                        Currently, as permitted by § 422.504(f)(2), CMS may review SSBCI eligibility criteria by requesting it from plans. This is done on a case-by-case basis. Since there is no public posting of a plan's criteria for determining how enrollees qualify for SSBCI, this lack of transparency limits potential enrollees' ability to review and determine what SSBCI are available to them. CMS received numerous comments in response to the Medicare Program; Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly; Health Information Technology Standards and Implementation Specifications proposed rule (herein after referred to as the “November 2023 proposed rule”) requesting that plans post their objective eligibility criteria for SSBCI on a public-facing website to increase transparency for potential enrollees. In response to these comments, CMS noted that CMS would consider taking this action in future rulemaking (89 FR 30558).
                        <SU>72</SU>
                        <FTREF/>
                         CMS believes having MA plan SSBCI eligibility criteria publicly available will improve transparency, promote good governance of the Medicare Trust Fund, and allow enrollees' participation in their care and awareness of their eligibility for benefits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             
                            <E T="03">https://www.federalregister.gov/d/2024-07105/p-1069.</E>
                        </P>
                    </FTNT>
                    <P>
                        Therefore, in the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule (hereinafter referred to as the Contract Year 2026 proposed rule) (89 FR 99340), CMS proposed that plans must publish the objective eligibility criteria on their public-facing website. Specifically, CMS proposed that MA plans must post on their public-facing website their objective criteria for determining that an enrollee is a chronically ill enrollee within the statutory and regulatory definition and is eligible to receive SSBCI offered by the plan. CMS reminded MA plans of their digital accessibility obligations as recipients of Federal assistance under section 504 of the Rehabilitation Act. CMS proposed to 
                        <PRTPAGE P="17481"/>
                        codify this requirement in the regulation text at § 422.102(f)(4)(iii)(C).
                    </P>
                    <P>
                        Next, in the Contract Year 2026 proposed rule, CMS proposed several technical changes that align with the statute to clarify SSBCI eligibility requirements and ensure that plans and providers have a clear understanding about which enrollees qualify for SSBCI. When reviewing SSBCI eligibility criteria, CMS discovered that several plans offering SSBCI benefits do not determine eligibility in an objective manner, as required at § 422.102(f)(4)(iii)(A).
                        <SU>73</SU>
                        <FTREF/>
                         For example, allowing an enrollee to self-attest that they are eligible for SSBCI without additional criteria or any verification from the plan of this eligibility status would not meet CMS requirements. Additionally, CMS has observed that some plans determine what SSBCI to cover and pay for without consultation with a doctor or other medical professional to determine the clinical appropriateness of the items and services offered under the SSBCI benefit. CMS has also identified instances where plans, when determining eligibility, are not properly evaluating enrollees using all three components of the definition for “chronically ill enrollee” as defined in section 1852(a)(3)(D)(iii) of the Act. CMS has identified that the current regulation text (§ 422.102(f)(1)(i)(A)) may need further clarification for plans. It was never the Agency's intention to imply that the presence of a chronic illness or chronic condition alone is sufficient to satisfy all three of the statutory criteria to qualify as a chronically ill enrollee. Therefore, CMS proposed to clarify that having a medically complex chronic condition or comorbidity by itself is insufficient to satisfy the requirements in § 422.102(f)(1)(i)(A)(1), (f)(1)(i)(A)(2), and (f)(1)(i)(A)(3) with a technical edit. Specifically, CMS proposed to amend § 422.102(f)(1)(i)(A) and (f)(1)(i)(A)(1) through (3) to specify that “a chronically ill enrollee is an individual enrolled in the MA plan who meets all of the following:
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             Prior to the effective date of the April 2024 final rule, this requirement was codified at 42 CFR. 422.102(f)(3)(iii). The April 2024 final rule slightly reorganized § 422.102(f) as part of amendments to adopt new requirements.
                        </P>
                    </FTNT>
                    <P>• Has one or more comorbid and medically complex chronic conditions that is life threatening or significantly limits the overall health or function of the enrollee.</P>
                    <P>• Has a high risk of hospitalization or other adverse health outcomes.</P>
                    <P>• Requires intensive care coordination.</P>
                    <P>This is consistent with the statute, which defines a “chronically ill enrollee” at section 1852(a)(3)(D)(iii) of the Act as an enrollee who: (1) has one or more comorbid and medically complex chronic conditions that is life threatening or significantly limits the overall health or function of the enrollee; (2) has a high risk of hospitalization or other adverse health outcomes; and (3) requires intensive care coordination. This clarification will allow the definition of a chronically ill enrollee at § 422.102(f)(1)(i)(A)(1) through (3) to mirror the statutory language at section 1852(a)(3)(D)(iii) of the Act as intended in the 2020 final rule.  </P>
                    <P>
                        Next, CMS proposed that plans must demonstrate that an enrollee has met all three of the criteria set forth in § 422.102(f)(1)(i)(A) through the use of an objective process (for example, either a health risk assessment, a claims review, or other similar means). This proposed requirement would help to ensure that the MA plan responsibilities at § 422.102(f)(4)(1)(i)(A) are fully realized while retaining the flexibility plans have in choosing between methods that determine whether enrollees have met all three criteria. For example, a plan could establish that to be eligible for certain SSBCI, an enrollee must have a confirmed diagnosis of diabetes by their primary care physician, and must also have been admitted to the hospital in the last 90 days. Under this example, the diagnosis of a chronic illness is sufficient to satisfy the first criterion (as proposed), that the enrollee, “has one or more comorbid and medically complex chronic conditions that is life threatening or significantly limits the overall health or function of the enrollee 
                        <SU>74</SU>
                        <FTREF/>
                        .” However, the plan must also determine that the enrollee has met the second and third criteria: (2) has a high risk of hospitalization or other adverse health outcomes; and (3) requires intensive care coordination. The plan may determine that an enrollee meets the second requirement by being hospitalized in the last 90 days. The plan may reason that enrollees who have been hospitalized in the last 90 days are at high risk of readmission and so meet the second statutory requirement of having a high risk of hospitalization. The plan may further decide that the enrollee would require intensive care coordination to prevent further hospitalization and thus would satisfy the third regulatory requirement. In this hypothetical scenario, the plan has determined through an objective process that the chronically ill enrollee meets all three requirements at § 422.102(f)(1)(i)(A).
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             As previously noted, the list of chronic conditions that qualify as comorbid and medically complex chronic conditions that are life threatening or significantly limit the overall health or function of an enrollee for purposes of SSBCI eligibility can be found within the definition of “severe or disabling chronic condition” in CMS's regulations at § 422.2.
                        </P>
                    </FTNT>
                    <P>As described previously, it has become evident through CMS's routine monitoring that MA plans have not consistently applied the statutory requirements to determine eligibility for SSBCI. To address this, CMS also proposed to add regulation text to § 422.102(f)(1)(i)(C). This additional regulation text reiterates that: (1) having one or more comorbidities and medically complex chronic conditions alone is not sufficient to demonstrate that an enrollee meets all three criteria set forth in paragraph (f)(1)(i)(A) and (2) MA plans must (through health risk assessments, review of claims data, or other similar means) demonstrate that enrollees meet all three criteria set forth in paragraph (f)(1)(i)(A). This technical correction would codify existing policy regarding SSBCI eligibility and would not impose any new collection of information requirements.</P>
                    <P>Finally, CMS proposed to restructure paragraph (f)(4)(iii) to clarify the requirements by adding, “Have objective criteria for SSBCI. Specifically, the plan must” and then listing the requirements in paragraphs (f)(4)(iii)(A) through (C).</P>
                    <P>CMS believes these updates, will provide greater transparency and consistency to the eligibility determination process for potential enrollees and will enhance enrollees' ability to understand what benefits would likely be available to them and thus their ability to make informed decisions about their enrollment. CMS reminds MA organizations that § 422.102(f)(4)(v) requires MA plans to maintain their evidentiary standards or objective criteria for enrollee eligibility for the entire coverage year.</P>
                    <P>CMS received the following comments on this proposal and responses follow.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were supportive of the proposal to require reporting of SSBCI eligibility criteria on a plan's public-facing website.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their support of this proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters mentioned concerns that CMS proposed to restrict a member's ability to self-attest to eligibility for SSBCI.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS did not propose a new prohibition on the ability of members to self-attest to SSBCI eligibility; rather, as 
                        <PRTPAGE P="17482"/>
                        stated in the Contract Year 2026 proposed rule, enrollees never had such ability and the use of self-attestation is out of compliance with current requirements. CMS has pursued compliance actions against plans that used self-attestation as a method to confirm SSBCI eligibility. Section 422.102(f)(4)(iii)(A) states that plans must have objective criteria for making SSBCI eligibility determinations, and self-attestation is not objective.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were concerned that claims review or other verification of eligibility may delay coverage of certain SSBCI. Some of the commenters also requested a grace or deeming period wherein plans may provide SSBCI coverage while the plan verifies eligibility.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for this feedback and understands the concerns about the potential for delays in coverage. However, as outlined in the preamble, it is, and has always been, the MA plan's responsibility to verify that an enrollee meets the eligibility criteria for SSBCI prior to administering the benefit. Moreover, CMS believes the inherent risk of waste and potential for abuse in administering benefits to ineligible enrollees when providing benefits before determining eligibility outweighs the possibility of delayed coverage. If plans are already performing the intensive care coordination that is required for the enrollee to be eligible for SSBCI, any delay due to verification of eligibility should be minimal.
                    </P>
                    <P>Finally, CMS does not consider a grace or deeming period to be appropriate because in the event an ineligible enrollee is permitted to access SSBCI during the grace period, this would create a situation where MA plans are out of compliance with their statutory obligation and increase the chance of plans inadvertently providing payment for non-covered items.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS clarify that MA plans have the flexibility to determine that enrollees have met the three-part “chronically ill” definition for SSBCI if they have an approved chronic condition code and a documented food/nutrition, housing/living environment, and/or transportation need. Additionally, several commenters conflated the two determinations MA plans are required to make when evaluating SSBCI eligibility.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments. As outlined in the preamble, CMS reiterates that MA plans are required to make two determinations when evaluating SSBCI eligibility. The first determination is that an enrollee is chronically ill-as per the statutory definition in section 1852(a)(3)(D)(iii) of the Act. To make this determination plans must verify that enrollees have met the three-pronged definition for a chronically ill enrollee.
                    </P>
                    <P>The second determination, per section 1852(a)(3)(D)(ii)(I), is that each particular SSBCI “have a reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollee.” Food/nutrition, housing, and transportation needs are all considerations that should be taken into account in this second determination when a plan decides which specific benefits may maintain or improve the overall health or function of the enrollee. Once a plan has confirmed that an enrollee is chronically ill per the statute, the plan may then refer to their objective eligibility criteria for each specific SSBCI.</P>
                    <P>The following example outlines how a plan may make this determination: The enrollee is diabetic and has been hospitalized in the past 90 days. The plan determines that the enrollee is at high risk of readmission and requires intensive care coordination to prevent further hospitalization, and therefore meets the statutory definition of “chronically ill.” The enrollee is then observed during an in-home health risk assessment (HRA) using a walker to get around their two-story home. The plan's criteria for “structural home modification” is that the enrollee requires assistance navigating the home (for example, a cane, walker, etc.) and that the home has stairs. In this case, the plan may reasonably recommend a “structural home modification” benefit to install a chair lift to assist that enrollee in navigating the home more easily. This example shows how the plan uses objective criteria (that the enrollee requires assistance to walk and live in a home with stairs). The plan may also conclude that the chair lift has a reasonable expectation of improving or maintaining the health or overall function of the enrollee as the use of the chair lift may prevent the enrollee from falls, or from injuries that may cause health complications. This example demonstrates how a plan can meet CMS's requirements of making two separate determinations in order to adequately comply with 42 CFR 422.102(f)(4)(i) and 422.102(f)(4)(iii)(A).  </P>
                    <P>CMS has already made allowances for plans to consider social determinants of health (SDOH) when identifying enrollees whose health or condition could be improved or maintained with SSBCI. This is set forth in the regulations at 42 CFR 422.102(f)(2)(iii). CMS notes however that plans may not use SDOH as the sole basis for determining SSBCI eligibility.</P>
                    <P>Finally, CMS clarifies that the proposed requirement is such that MA plans must publicly post their objective criteria for both steps of the SSBCI process. Specifically, MA plans must publicly post their criteria for determining that someone has met the definition of a chronically ill enrollee and their specific SSBCI benefit eligibility criteria. To clarify this, CMS is finalizing the proposal with a modification to refer to 42 CFR 422.102(f)(4)(iii)(A).</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that certain chronic conditions such as end-stage renal disease (ESRD), diabetes and chronic obstructive pulmonary disease (COPD) should automatically qualify enrollees for SSBCI due to their high hospitalization risks.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While CMS agrees that many ESRD, diabetes and COPD patients would likely meet the three-pronged definition of a chronically ill enrollee and potentially be eligible for several SSBCI items and services, CMS is not finalizing any automatic eligibility based on chronic condition diagnosis at this time. CMS notes that some patients with these conditions, or others on the chronic condition list set forth at § 422.2, may be able to manage their conditions well, and not be at high risk of hospitalization or other adverse health outcomes or require intensive care coordination. Such enrollees would not meet the chronically ill enrollee definition. It would therefore not be prudent to automatically confirm chronically ill status or SSBCI eligibility based on a singular chronic condition.
                    </P>
                    <P>CMS acknowledges that many patients with the noted chronic conditions may meet the eligibility standards based on an HRA, which SNPs are required to complete within 90 days, before or after enrollment in a plan. Since many enrollees with these conditions are enrolled in C-SNPs, CMS notes that plans may use these HRAs to determine: (1) chronically ill enrollee status and (2) particular SSBCI items and services that would meet the reasonable expectation standard. However, CMS reiterates its commitment to allowing plans to have the flexibility to determine the form and manner of confirming “chronically ill” status and SSBCI eligibility criteria. CMS noted in the Contract Year 2026 proposed rule that HRAs and claims reviews were merely two examples by which a plan may confirm these.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS exempt C-SNPs from SSBCI eligibility criteria publication.
                        <PRTPAGE P="17483"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this suggestion, however CMS is not finalizing any exemptions to the public posting requirement at this time. It is the Agency's intention to increase the transparency of SSBCI benefits for enrollees. By exempting C-SNPs from the proposed requirement, CMS would exclude a vulnerable population from receiving this important information regarding SSBCI benefits. While many potential C-SNP enrollees may meet the chronically ill statutory definition, the lack of transparency on the eligibility requirements could be a deterrent to them during the enrollment period. For example, a C-SNP enrollee could choose a different plan with benefits less suited to them. The result of such a choice could have negative outcomes for all parties.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted concerns with being required to post proprietary SSBCI eligibility criteria on the plan's website.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS understands that plans may have concerns about competitive advantage with new requirements to publish this information on a public-facing website. CMS notes however that listing eligibility criteria may provide for additional open competition in the marketplace, further incentivizing MA plans to offer supplemental benefits that are valued by enrollees in a clear and consistent manner. CMS has therefore determined that the potential benefit to enrollees far outweigh concerns about posting SSBCI eligibility information.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS rely on the subset of chronic diseases identified by the Agency itself that allow for the current provision of SSBCI and enrollment in C-SNPs to determine eligibility. They urged CMS not to finalize limitations on SSBCI eligibility by requiring plans to impose an “objective process” to ensure beneficiaries meet three criteria to receive SSBCI.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment and attempts to clarify here. The requirement for plans to have and apply objective criteria for determining a chronically ill enrollee's eligibility to receive a particular SSBCI is already a regulatory requirement and has been since the inception of SSBCI in the MA program (85 FR 9013).
                    </P>
                    <P>The commenter suggests that enrollees with chronic conditions identified by CMS meet the chronically ill enrollee definition and qualify for SSBCI solely on the basis of having one of those conditions. As CMS noted in a previous response, this is not the case and plans are required to have further criteria to make such determinations. CMS reminds commenters that this proposal was a technical update to emphasize the existing statutory and regulatory requirements, and CMS has held this standard since the inception of SSBCI.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended that CMS consider providing detailed directions on what information must be included on the plan's public-facing website to ensure consistency between plans and help beneficiaries more easily compare their choices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this concern and may consider providing additional guidance if, in practice, there is evidence that inconsistency among MA plan websites cause beneficiary confusion.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS provide a comprehensive list of acceptable methodologies that would meet the definition of “objective process” for purposes of determining SSBCI eligibility. This commenter urged CMS to include the review and identification factors that influence disease progression. They suggested that these factors include, but not be limited to, race, ethnicity, socioeconomic status, comorbidities, and recent acute care utilization.
                    </P>
                    <P>Similarly, another commenter asked that plans be allowed to use low-income status (LIS) and dual-eligibility as part of the objective criteria to support that a member is at risk for hospitalizations or adverse health outcomes and thereby requires care management.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this recommendation. Per section 1852(a)(3)(D)(iii)(III) of the Act, for purposes of SSBCI, a chronically ill enrollee must “require[ ] intensive care coordination.” CMS reiterates that in the June 2020 Final Rule, CMS did not define “intensive care coordination” to allow plans flexibility in determining what the phrase meant to best serve their specific enrollee population. However, CMS noted some examples of methods through which plans may determine an enrollee required intensive care coordination, such as conducting an HRA, performing a retrospective claims review for an enrollee, or by other means the plan deems necessary. CMS reaffirms its position stated in the June 2020 final rule, that objective criteria which utilize the above mechanisms for meeting the three-pronged definition are present in the medical community and may be readily accessible to the plan.
                    </P>
                    <P>CMS reminds commenters that an enrollee's high risk of hospitalization, does not necessarily affirmatively establish that the enrollee will also require intensive care coordination, as these are separate factors to evaluate in determining whether an enrollee meets the statutory definition of “chronically ill” for purposes of SSBCI.</P>
                    <P>CMS notes that the commenters listed several factors that may be useful in meeting CMS' requirements. It is at the plans' discretion to determine their objective criteria for determining whether an enrollee meets the definition of “chronically ill” for purposes of SSBCI, based on their specific enrollee population and any other relevant considerations that may be unique to the plan. CMS does not wish to limit the flexibility of MA organizations to determine which objective criteria are best for a particular plan, or their enrollees.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter believed that CMS' proposed provision regarding posting criteria for determining chronically ill enrollee status on a public-facing website would increase administrative burden on plans and provide little to no value to enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges that this requirement will place administrative burden on plans to implement and discusses the burden in the Collection of Information section of this final rule. CMS proposed to make SSBCI criteria publicly available in response to numerous comments received during previous rulemaking. Commenters expressed the need for such transparency in order for potential enrollees to make informed choices when choosing an MA plan to join and to have a better understanding of their current care options while enrolled. Such transparency will have an overall positive impact on enrollee experience and choice as it fosters enrollee empowerment and competition in the MA market.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that CMS not require hospitalization in the past 90 days to meet the second and third criteria that chronically ill enrollees have a “high risk of hospitalization or other adverse health outcomes” and “require intensive care coordination” respectively. Specifically, a commenter mentioned that I-SNP enrollees are inherently at high risk due to their clinical and care needs and recommended that CMS consider adjusting the eligibility criteria for this population to better reflect the goals of preventative care in long-term care settings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this feedback. CMS clarifies that the discussion pertaining to hospitalization in the past 90 days in the Contract Year 
                        <PRTPAGE P="17484"/>
                        2026 proposed rule and in this section of the final rule is meant to serve only as an example of objective criteria an MA plan might apply in determining chronically ill enrollee status. CMS did not propose and will not be finalizing a requirement that MA enrollees must have been hospitalized in the past 90 days in order to be eligible to receive SSBCI.
                    </P>
                    <P>CMS also appreciates the commenter drawing attention to I-SNP enrollees specifically. CMS agrees that many I-SNP enrollees would likely meet the chronically ill enrollee definition. CMS therefore notes, if plans were to use a qualifying chronic condition diagnosis in conjunction with enrollee utilizing institutional level of care (LOC) to satisfy the 3-pronged criteria for chronically ill enrollee, this would meet CMS requirements and expectations, as the need for an institutional LOC could indicate a high risk of hospitalization or other adverse health outcomes and a need for intensive care coordination.  </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that if finalized, the implementation of the public posting of chronically ill enrollee criteria be delayed at least one year to allow adequate time to inform beneficiaries while minimizing any potential disruptions to care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these concerns regarding the timing of these requirements. CMS notes that MA organizations will have until January 2027 to implement these requirements. Additionally, MA plans should already be utilizing objective criteria for both determining that an enrollee meets the definition of a chronically ill enrollee and that a specific SSBCI has a reasonable expectation of improving or maintaining the enrollee's overall health or function. Therefore, requiring MA organizations to post this information on their plan's website should present minimal challenges regarding timeliness and should not require a full year to finalize.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter requested that CMS allow plans to proactively approve members for SSBCI benefits prior to their effective date with a plan. This approach would help ensure vulnerable members have access to the support they need as soon as possible, which is essential for improving their health outcomes. They also recommended that plans be allowed to use multiple chronic conditions (MCC) files as a method of SSBCI eligibility verification.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this commenter's feedback and notes that this proactive approval process would be allowable. For example, many plans choose to complete HRAs before the beginning of the coverage year. The information obtained from the HRA can then be used to help confirm the chronically ill status of an enrollee prior to the plan's effective date. CMS agrees that plans should utilize data streams that provide the most utility in accordance with the resources available to them.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter requested additional clarification of the requirements for objective criteria given that some HRAs are self-attested.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment and the opportunity to clarify. Self-attested HRAs include questions about an enrollee's habits, environment, or other pertinent information. The enrollee is answering questions which are specific in nature, and do not rely on the enrollee's judgement to self-diagnose or make SSBCI eligibility determinations about themselves. An MA organization may use an enrollee's HRA responses in determining, based on objective criteria, the enrollee's eligibility for SSBCI. If, by contrast, an enrollee was to certify their own eligibility for SSBCI by checking a box, for example, without first receiving an independent determination by the MA organization that objective criteria for eligibility are met, this would not be compliant with CMS' rules. It is the responsibility of the MA organization (not enrollees) to understand and abide by CMS requirements.
                    </P>
                    <P>An MA organization cannot delegate its responsibility to make objective eligibility determinations to the enrollee, given that the enrollee may have a strong financial incentive to certify themselves eligible for SSBCI and may not fully understand the applicable criteria. Consider an example where the plan provides money for gas as “transportation for non-medical benefits” SSBCI which is administered through a debit card or “flex card” and the enrollee is asked to check a box if they are “eligible to receive a gas card.” Allowing an enrollee to self-attest or self-certify to SSBCI eligibility in this scenario is inconsistent with the MA organizations' responsibility for ensuring objective SSBCI eligibility determinations. This scenario is distinguishable from self-attested responses to questions on an HRA, which can then be used by the MA organization to determine, based on objective criteria, whether the enrollee is eligible for SSBCI. As a result, self-attestation of eligibility for SSBCI is not permissible, but MA organizations may use self-attested HRA responses in determining eligibility for SSBCI.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS not finalize its proposed requirement for plans to publicly post their SSBCI eligibility criteria as they believed it would be duplicative of information provided in the Evidence of Coverage (EOC) and is also required in any marketing of the SSBCI benefits as finalized in the April 2024 final rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment and agrees that best practices in providing EOC materials and other plan documents would include this information. CMS stated in the June 2020 final rule that it is expected that plans communicate to enrollees information in a clear manner about the scope of SSBCI that the MA plan covers and who is eligible for those benefits (
                        <E T="03">85 FR 33803</E>
                        ). The EOC requirements in § 422.111(b)(2) require the inclusion of information about the benefits offered under a plan, including applicable conditions and limitations. In the April 2024 final rule, CMS modified the disclaimer requirements at § 422.2267(e)(34) to require plans to include clear information about SSBCI eligibility criteria in marketing and communications materials that mention SSBCI, including by listing the chronic conditions an enrollee must have in order to be eligible for the SSBCI. However, this regulation does not explicitly state that plans must list their SSBCI eligibility criteria apart from specific chronic conditions that might qualify for SSBCI. Some MA organizations have neglected to include such additional eligibility criteria in their plan's EOC and other documents. For plans that already list the information elsewhere, there will be a lower associated burden. Plans that do not provide this information anywhere in enrollee-facing documentation will be providing an additional level of transparency into their operations that may improve patient experience.
                    </P>
                    <P>CMS is finalizing the proposal with the following modifications: First, for the reasons discussed in this section, § 422.102(f)(4)(iii)(C) will be finalized as follows, “For each SSBCI, list all the written policies and objective criteria on which the policies are based, as noted in paragraph (f)(4)(i) and (f)(4)(iii)(A) of this section, on their public-facing website.” Second, CMS is finalizing non-substantive technical changes at 42 CFR 422.102(f)(4)(iii)(A)-(C) for structure and clarity.</P>
                    <P>
                        Finally, CMS notes that while this provision was originally proposed in the Contract Year 2026 proposed rule, it is being finalized in the Contract Year 2027 final rule. Therefore, this provision will be applicable January 1, 2027.
                        <PRTPAGE P="17485"/>
                    </P>
                    <HD SOURCE="HD2">L. Administration of Supplemental Benefits Coverage Through Debit Cards §§ 422.102, 422.111, and 422.2263</HD>
                    <P>The following provisions were proposed in the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule (hereinafter referred to as the Contract Year 2026 proposed rule) (89 FR 99340). This section discusses what was proposed and the modifications being made in this final rule.</P>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>
                        Section 1852(a)(3)(A) of the Act gives Medicare Advantage (MA) organizations the ability to offer supplemental benefits to plan enrollees, subject to the Secretary's approval. CMS has adopted rules—primarily in §§ 422.100(c)(2) and 422.102—to regulate how those supplemental benefits, such as vision, dental, gym membership, and others, must be offered. For example, in the Medicare Program, Establishment of the Medicare Advantage Program Final Rule,
                        <SU>75</SU>
                        <FTREF/>
                         which appeared in the 
                        <E T="04">Federal Register</E>
                         on January 28, 2005, CMS established at § 422.102(a)(4) that an MA organization could offer as a mandatory supplemental benefit a reduction in cost sharing below the actuarial value specified in section 1854(e)(4)(B) of the Act (70 FR 4617). Later, in the Medicare and Medicaid Programs; Contract Year 2022 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicaid Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly Final Rule 
                        <SU>76</SU>
                        <FTREF/>
                         (January 19, 2021; 86 FR 5913) (hereinafter referred to as the January 2021 final rule), CMS further clarified the scope of supplemental benefits that reduce cost sharing by adding rules at § 422.102(a)(5) and (a)(6)(i) and (ii) to clarify the different circumstances under which an MA plan may reduce cost sharing for covered items and services as a mandatory supplemental benefit and the mechanisms by which an MA plan may make such reductions in cost sharing available to enrollees. Mandatory supplemental benefits are benefits that are included in the plan and are generally available to all enrollees with no additional premiums. As described in § 422.102(b), optional supplemental benefits are purchased at the discretion of the enrollee and are available to all plan enrollees who choose to pay an additional premium in order to receive those benefits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2005/12/23/05-24446/medicare-program-establishment-of-the-medicare-advantage-program</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             
                            <E T="03">https://www.govinfo.gov/content/pkg/FR-2021-01-19/pdf/2021-00538.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>In the January 2021 final rule, CMS explained that MA plans may choose to structure mandatory supplemental benefits in a few ways (86 FR 5913). For example, an MA plan may offer, as a mandatory supplemental benefit, the use of a debit card to administer reduced cost sharing for plan-covered services or to provide coverage of 100 percent of the cost of plan-covered items or services. This may include reduced cost sharing for dental and vision services (when offered as a mandatory supplemental benefit—not as an optional benefit) where a claim for additional payment is submitted to the plan, and/or coverage by the plan (through use of the card) of all or part of the cost of OTC items, fitness-related benefits, food and produce, transportation, and utilities support. With respect to a mandatory supplemental benefit in the form of reduced cost sharing, a beneficiary may receive a debit card to use to pay for any applicable cost sharing when receiving a basic benefit or mandatory supplemental benefit, including Special Supplemental Benefits for the Chronically Ill (SSBCI). For example, if the plan provides a transportation service as a covered benefit and provides a debit card to be used to reduce cost sharing for those defined transportation services, the beneficiary could use the debit card to pay for those services. However, MA organizations that choose to use a debit card to administer mandatory supplemental benefits must do so in a manner that ensures the debit card can only be used towards plan-covered items and services. To the extent these items and services are mandatory supplemental benefits, they must also meet all the regulatory supplemental benefit standards at §§ 422.100(c)(2) and 422.102(a) through (f). CMS reminds readers that reduced cost sharing is not permitted as an optional supplemental benefit (that is a supplemental benefit that a beneficiary would select in exchange for additional premiums) (see 86 FR 5913). Thus, this mechanism of using debit cards is not permitted to administer optional supplemental benefits (that is, an optional dental or vision service package).</P>
                    <P>The use of debit cards is permitted for administering both mandatory supplemental benefits for all MA enrollees and mandatory supplemental benefits available as SSBCI as defined at § 422.102(f). CMS also explained in the January 2021 final rule that debit cards may only be used to administer coverage of items and services that are identified in the MA plan's bid and marketing and communication materials as covered benefits (86 FR 5913). Consistent with guidance in Chapter 4 of the Medicare Managed Care Manual (MCM), § 40.3, CMS stated that debit cards used for plan-covered benefits must be exclusively linked to only the covered items and drugs specified by the MA organization and that MA organizations are not permitted to offer use of a debit card to enrollees for purchasing items or services that are not plan-covered (86 FR 5913). In addition, the use of the debit card to pay cost sharing or pay for covered items and services must be tied to the period of coverage, that is the specific plan year or part of a plan year during which the enrollee is enrolled with and covered by the MA plan. (MA organizations may include a maximum dollar limit on a per-month basis, per-year basis, or other periodicity within the plan year tied to the benefit maximum.) The debit card itself is not a supplemental benefit; rather, it is a tool used to administer coverage to an enrollee for identified plan-covered items and services at a reduced cost. Plan-covered items and services that are paid for by a debit card must meet the requirements and standards for mandatory supplemental benefits or be basic benefits in the case of reduced cost sharing for a Part A or B covered benefit, as specified in the January 2021 final rule (86 FR 5913).</P>
                    <P>
                        Since the January 2021 final rule, many MA organizations have disclosed the use of debit cards to administer a benefit in their annual bid notes. In reviewing annual bids, CMS has observed that MA organizations appear to regularly use debit cards to administer several mandatory supplemental benefits, including reductions in cost sharing for dental and vision services and/or payment for OTC items, fitness-related benefits, food and produce, transportation, and utilities support. In recent years, based on questions from stakeholders, including beneficiaries, CMS has also become aware that there is some confusion around the use of debit cards. For example, many stakeholders have submitted questions requesting CMS clarify what these cards are and how they can be used. CMS has also received complaints from enrollees who tell us that they are confused when trying to use their debit card. Often these individuals do not receive guidance on 
                        <PRTPAGE P="17486"/>
                        which plan covered supplemental benefits can be purchased with their debit card or where and how they can use them. Additionally, stakeholders have raised concerns that there are not enough guardrails on how these cards are used and how purchases are tracked, especially at large box stores that carry non-covered items and services (for example, Costco or Walmart) that would be inappropriate for the MA plan to cover as supplemental benefits. For example, there are concerns that the enrollee may use the plan debit card to purchase items and services that are not covered or that do not meet the requirements for MA supplemental benefits.
                    </P>
                    <P>To provide further clarity to both MA organizations and beneficiaries on the parameters around the appropriate use of plan debit cards, in the Contract Year 2026 proposed rule, CMS proposed requirements on the proper administration of supplemental benefits. Based on CMS's authority under section 1856(b)(1) of the Act to establish standards for MA organizations, along with the authority in section 1857(e)(1) of the Act to adopt additional terms and conditions for MA contracts that are not inconsistent with the Part C statute and that are necessary and appropriate for the MA program, CMS proposed to codify in regulation text the requirements and limitations discussed in the preamble of the January 2021 final rule and later in the May 6, 2024 HPMS memo titled, “Final Contract Year (CY) 2025 Standards for Part C Benefits, Bid Review and Evaluation” regarding the administration of supplemental benefits, including the use of debit cards. CMS believes codifying these standards will also ensure that MA requirements regarding supplemental benefits are applied uniformly across the MA industry and for all supplemental benefits: both standard (that is, primarily health-related) supplemental benefits and non-primarily health-related SSBCI. CMS also proposed to expand on these requirements by adopting additional disclosure and access guardrails to increase transparency, protect access to plan-covered services for MA enrollees, and ensure that MA plans cover (that is, provide, furnish, and/or pay for) only those items and services that are permissible MA benefits.</P>
                    <P>Specifically, CMS proposed to add a new paragraph (g) at § 422.102 to codify existing guidelines for administering supplemental benefits, including the use of debit cards to administer plan-covered benefits, and add new guardrails to ensure that beneficiaries are fully aware of covered supplemental benefits and how to access those benefits.</P>
                    <HD SOURCE="HD2">2. The Administration of Supplemental Benefits</HD>
                    <P>CMS regulations at § 422.100(c)(2) define a mandatory or optional supplemental health care benefit (with the exception SSBCI as defined at § 422.102(f)) as an item or service: (1) not covered by original Medicare; (2) that is primarily health-related; and (3) for which the plan must incur a non-zero direct medical cost. The 2022 Final Rule further clarified at § 422.100(c)(2)(ii)(A) that to be considered primarily health-related, a supplemental benefit must be to diagnose, prevent, or treat an illness or injury; compensate for physical impairments; act to ameliorate the functional/psychological impact of injuries or health conditions; or reduce avoidable emergency and health care utilization. Additionally, CMS has codified numerous requirements that MA organizations must comply with when delivering supplemental benefits at § 422.102(a) through (e). More recently, CMS codified standards for SSBCI benefits at § 422.102(f), which include the requirements that SSBCI may only be offered to chronically ill enrollees as defined by section 1852(a)(3)(D) of the Act, must incur a non-zero non-administrative cost, and must have a reasonable expectation of improving or maintaining the health or overall function of the enrollee. SSBCI may include benefits that are not primarily health-related per § 422.100(c)(2)(ii)(A) but must have a reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollee. Additionally, per section 1852(a)(3)(D)(ii)(II) of the Act, CMS has authority to waive the uniformity requirements that usually apply for all MA benefits so that SSBCI can be offered non-uniformly.</P>
                    <P>CMS proposed in the Contract Year 2026 proposed rule that MA organizations must have processes for delivering all MA plan-covered supplemental benefits to enrollees that ensure compliance with §§ 422.100(c)(2) and 422.102(a) through (f) and appropriate access to suppliers and providers in accordance with § 422.112(a) as applicable. Per § 422.112(a), MA coordinated care plans may specify the networks of providers from whom enrollees may obtain services if the MA organization ensures that all covered services, including supplemental services contracted for by (or on behalf of) the Medicare enrollee, are available and accessible under the plan. The MA organization may therefore contract with providers or vendors to furnish covered services, including supplemental benefits administered via a debit card or otherwise. For example, a plan may contract with a particular vendor to provide their food and produce benefit. In this scenario, that specific vendor is the network provider for furnishing the food and produce benefit. CMS noted that section 1854(a)(6)(B)(iii) of the Act, commonly known as the “non-interference clause,” prohibits CMS from requiring any MA organization to contract with a particular provider to furnish covered items and services. Therefore, CMS does not specify which vendors MA organizations contract with to furnish covered items and services. (Note, however, that § 422.204(b)(3) requires that providers that furnish covered Part A and B benefits must meet the applicable requirements of Title XVIII of the Act and that certain types of institutional providers must have participation agreements with Medicare.)</P>
                    <P>
                        CMS also noted that all coordinated care plans are required to cover benefits, including supplemental benefits, at in-network cost sharing when an in-network provider or benefit is unavailable or inadequate to meet an enrollee's medical needs in accordance with the standards set forth in rules and regulations.
                        <SU>77</SU>
                        <FTREF/>
                         This is required for all benefits, regardless of how they are administered.
                    </P>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             § 422.112 (a)(1)(iii); Chapter 4, section 30.2 of the Medicare Managed Care Manual; 88 FR 22200.
                        </P>
                    </FTNT>
                    <P>If an in-network provider is unavailable or inadequate to administer covered plan benefits, whether Parts A and B or supplemental benefits, the MA organization should have a plan or process in place to ensure that the requirements under § 422.112(a)(1)(iii) are met. However, given inconsistencies in how supplemental benefits are provided, CMS believes it is necessary to clarify this requirement in regulatory text. Therefore, in the Contract Year 2026 proposed rule, CMS proposed and sought comment on new § 422.102(g)(1) that would require MA organizations to have processes for delivering all MA organization covered supplemental benefits to enrollees that ensure compliance with §§ 422.100(c)(2) and 422.102(a) through (f) and appropriate access to all covered services in accordance with § 422.112(a).</P>
                    <HD SOURCE="HD3">3. New Guardrails for Plan Debit Cards</HD>
                    <P>
                        In the Contract Year 2026 proposed rule, CMS proposed to include a clarification in § 422.102(g)(1) requiring 
                        <PRTPAGE P="17487"/>
                        that MA organizations have processes for delivering all MA organization covered supplemental benefits to enrollees that ensure compliance with §§ 422.100(c)(2) and 422.102(a) through (f) and appropriate access to all covered services per § 422.112(a). Thus, CMS believes it is necessary to specify that this requirement would apply to all plan-covered supplemental benefits, including supplemental benefits administered through debit cards. Under this proposal, plans must have a process in place to maintain enrollee access to these benefits. When plans offer debit cards to assist with the cost sharing for covered benefits or otherwise administer supplemental benefits, the MA organization must ensure that the access requirements at § 422.112(a) are met. This means regardless of the mode of delivery (for example, debit card or other means), MA organizations must ensure that all covered services, including supplemental benefits, and SSBCI for eligible enrollees, contracted for by (or on behalf of) enrollees, are available and accessible under the plan.
                    </P>
                    <P>
                        In addition, CMS requires that plan-covered benefits be disclosed in the plan's evidence of coverage (EOC). Section 422.111 requires that MA organizations disclose all benefits offered under an MA plan, including applicable conditions and limitations, and any other conditions associated with receipt or use of benefits. These requirements are applicable to all benefits, including those administered via debit card. CMS also noted that MA organizations are required to send an Explanation of Benefits (EOB) to an enrollee that captures all claims activity that occurs during a reporting period (monthly or quarterly cycle). The EOB must include claims information for all Part C claims processed during the reporting period, including all claims for Part A and Part B covered items and services, mandatory supplemental benefits, optional supplemental benefits, and SSBCI.
                        <SU>78</SU>
                        <FTREF/>
                         The EOB must disclose for each claim a descriptor, billing code and amount billed, total cost approved for reimbursement, share of the total cost paid by the plan, and share of the total cost for which the enrollee is liable. Additionally, the EOB must include certain year-to-date information such as the amount an enrollee has incurred toward the Maximum Out-of-Pocket (MOOP) limit.
                        <SU>79</SU>
                        <FTREF/>
                         These EOB requirements include supplemental benefits that MA plans elect to cover through a debit card.
                    </P>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             
                            <E T="03">https://www.ecfr.gov/current/title-42/part-422/section-422.111#p-422.111(k)</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             
                            <E T="03">https://www.ecfr.gov/current/title-42/part-422/section-422.111#p-422.111(k)</E>
                            .
                        </P>
                    </FTNT>
                    <P>However, given stakeholder and enrollee feedback, CMS believes additional clarity and more specific guardrails regarding the use of debit cards are necessary to ensure that enrollees are adequately aware of the benefits that are available to them from their plan through a debit card and how to access them.</P>
                    <P>In the January 2021 final rule, CMS stated that consistent with current guidance in section 40.3 of Chapter 4 of the Medicare MCM, debit cards may only be used for plan-covered benefits under the condition that the card is exclusively linked to the covered items. CMS also suggested in the January 2021 final rule (86 FR 5913) that MA organizations may accomplish this by providing a debit card that is linked to an appropriate merchant and item/service codes so that the enrollee may pay the cost sharing at the point of service. CMS believes such a link is necessary to ensure that the debit card is used for the permissible purpose—to reduce the enrollee's cost sharing for a covered item or service or to pay for an item or service that is covered by the MA plan at up to 100 percent of the cost. Therefore, CMS proposed at § 422.102(g)(2)(i) the following requirements that MA organizations must meet if they choose to administer reductions in cost sharing or provide coverage of 100 percent of the cost of a mandatory supplemental benefit. CMS proposed at § 422.102(g)(2)(i) that when administering a mandatory supplemental benefit through plan debit cards, an MA organization must provide debit cards that are electronically linked to plan covered benefits through a real-time identification mechanism to verify eligibility of plan covered benefits at the point of sale. This means that a plan-issued debit card must be electronically linked to the covered benefit through a real-time mechanism that ensures the enrollee is only able to receive covered items or services that they are eligible to receive at the point of sale. The debit card must include some sort of mechanism that ensures the enrollee may only use the card to purchase the covered item or service. For example, an MA organization could provide a debit card linked to covered benefits through the use of item/service codes so that the enrollee is only able to pay the cost sharing for those select items at the point of sale. In this scenario, the MA organization would have to ensure that the enrollee is only able to purchase items or services they are specifically eligible to receive. This is necessary to ensure that enrollees only receive benefits they are eligible to receive and that MA organizations do not inadvertently furnish non-covered benefits. The debit card is intended only to facilitate or administer certain covered benefits and may not be used to pay for non-covered items or services. CMS did not propose to prescribe exactly how plans effectuate the proposed requirements at § 422.102(g)(2)(i) because CMS believes flexibility for plans to innovate around these processes will be beneficial to the industry. However, if an MA organization provides a debit card that is not electronically linked to covered items and services and does not include checks to ensure that the enrollee may only receive covered benefits they are eligible to receive, the MA organization would be in violation of these requirements.</P>
                    <P>Next, CMS proposed at § 422.102(g)(2)(ii) to require MA organizations that use debit cards to administer a supplemental benefit to provide instructions for debit card use and customer service support to enrollees to answer questions or help with issues related to the administration of the card. For example, if an MA organization provides a food and produce benefit that may be accessed via a debit card, the plan must provide eligible enrollees with instructions on how to use the debit card and provide customer support service to beneficiaries who have questions about how to use the debit card. This support service must include instructions to beneficiaries on the process to access these benefits if not accessible by debit card, in accordance with § 422.112(a). CMS believes this is necessary to ensure that enrollees are fully aware of their benefits and how to properly access those benefits, particularly those living in rural areas with limited access to broadband/internet for communication. Finally, all benefits must be limited to the specific plan year. Therefore, the Contract Year 2026 proposed rule proposed to state at § 422.102(g)(2)(iv) that MA organizations must ensure the use of a debit card to administer a covered benefit is limited to the specific plan year.</P>
                    <P>
                        In the January 2021 final rule, CMS amended § 422.102(a)(6) to state that an MA organization may offer reduced cost sharing as a mandatory supplemental benefit through the use of reimbursement, through a debit card or other means. In order to further support the proposed requirements at § 422.102(g)(1), in the Contract Year 2026 proposed rule, CMS also proposed to revise § 422.102(a)(6) by removing “or 
                        <PRTPAGE P="17488"/>
                        other means” and adding “manual” before reimbursement to ensure that reductions in cost sharing as a supplemental benefit are clearly limited to either manual reimbursement or to a debit card governed by the proposed rules under § 422.102(g) for covered items and services. CMS explained that “other means” could be interpreted to allow an unrestricted card or other vague mechanisms, which would conflict with CMS requirements that a debit card be exclusively linked to covered benefits and limited to the plan year or the requirements being proposed at § 422.102(g)(1)(i).
                    </P>
                    <P>
                        While CMS proposed to remove “or other means,” CMS also solicited comment on what other means, outside of manual reimbursement or a debit card, would be unintentionally removed as options to plans should this proposed revision be finalized. CMS solicited comment on how these other means or mechanisms may still guarantee compliance with existing requirements at § 422.102(a)(6) and the requirements proposed at §§ 422.102(g) and 422.111(b)(6) (discussed in section III.H.2 of the Contract Year 2026 proposed rule). For example, it was not CMS's intent that the proposed changes at § 422.102(a)(6) would prohibit an organization from using a stored value card,
                        <SU>80</SU>
                        <FTREF/>
                         provided the use of these cards by MA plans complies with the requirements at § 422.102(g). Therefore, CMS solicited comment on whether the use of stored value cards meets the requirements at § 422.102(g). Specifically, CMS solicited comment on whether the mechanisms available and used with stored valued cards are sufficient so that the purchases made through such cards can be electronically linked to plan covered items through a real-time identification mechanism that verifies the eligibility of plan covered benefits at the point of sale, and can restrict the time period allowed for the use of the stored value card to the plan year only. CMS also solicited comment on whether stored value cards should be explicitly added to § 422.102(a)(6) and § 422.102(g) as an acceptable means of administering reductions in cost sharing and the coverage of supplemental benefits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             
                            <E T="03">https://www.fiscal.treasury.gov/stored-value-card/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Access</HD>
                    <P>While an MA organization may utilize a debit card to administer a benefit, this does not exempt the plan from ensuring access and network adequacy is preserved for the benefit if there is an issue with the vendor or a technical issue with the debit card. As discussed earlier, the regulations at § 422.112(a)(1)(iii) specify that coordinated care plans must arrange for, and cover any, medically necessary (clinically appropriate for non-primarily health-related SSBCI) covered benefit outside of the plan provider network, but at in-network cost sharing, when an in-network provider or benefit is unavailable or inadequate to meet an enrollee's medical needs. Additionally, long-standing guidance under section 40.3.1 of Chapter 4 of the Medicare MCM states, “Every MA plan, independent of the payment method it chooses, must also allow—under circumstances which it describes (for example, when the debit card network is not operating correctly)—for manual reimbursement for the purchase of OTC items based on submitted receipts.” CMS included this language in the Medicare MCM Chapter 4 to ensure enrollee access by requiring plans to have an alternative method (for example, reimbursement based on submitted receipts) for enrollees to receive their OTC benefits if there was an issue with the contracted vendor or an operational issue with the debit card. CMS believed that it was important to propose a similar policy here to maintain enrollee access for all benefits administered through a debit card, not just OTC benefits.</P>
                    <P>Therefore, CMS proposed at § 422.102(g)(2)(iii) that a plan must have an alternative process that allows for reimbursement of eligible expenses for plan covered benefits. CMS believed this proposal would allow enrollees to maintain access to covered benefits that are administered through the offering of a debit card should the real-time identification mechanism fail or otherwise be unavailable. This would allow enrollees to be reimbursed for the purchase of eligible plan covered benefits if they are unable to use their plan debit cards. CMS believed that requiring plans to allow this alternative will ensure that the enrollee has access to the benefit if there is an issue with the vendor, a technical issue with the debit card, or any other situation in which the use of a debit card is unfeasible for the enrollee. This may include non-technical issues, such as when an enrollee is having trouble understanding how to use the debit card or is otherwise running into non-technical obstacles to its use. This alternative reimbursement process could also apply if there are failures with the electronic processing system used by the provider. This includes situations where a permitted transaction is erroneously declined. In other words, in the case that the debit card is not operating correctly or as intended, there is an issue with the vendor, or any other situation in which the use of a debit card is unfeasible for the enrollee, the MA plan must allow enrollees to be reimbursed for the purchase of the covered benefit based on submitted receipts. This also includes situations in which a contracted vendor is not easily accessible due to an enrollee's transportation constraints. This requirement would protect enrollee access to benefits that they are entitled to receive regardless of issues that may arise from a plan's chosen mode of delivery (for example, plan debit card).</P>
                    <P>CMS proposed that this alternative process must be in place for both in-network and out-of-network access to the benefit where necessary (for example, in the event that in-network providers and/or vendors are unavailable or inadequate to meet the enrollee's needs). In this scenario, the plan is still responsible for ensuring out-of-network access at in network cost sharing. Under this requirement, MA organizations would be expected to adequately disclose the process by which reimbursement may be made to enrollees and to ensure that the process is accessible to all enrollees. CMS also encouraged MA organizations to be mindful of enrollees in rural areas, especially those who have limited access to broadband or internet communication, when implementing this requirement and when disclosing information about how to effectuate a reimbursement to plan enrollees.</P>
                    <P>
                        CMS also noted that MA plans that are PPOs are required to provide reimbursement for all covered services, regardless of whether the items are provided within the network of providers under § 422.4(a)(1)(v). Regarding reimbursement, § 422.4(a)(1)(v)(B) requires PPOs to provide for “reimbursement for all covered benefits regardless of whether the benefits are provided within the network of providers.” This applies to all supplemental benefits, including those administered through a debit card (it was noted that in this scenario, an enrollee may be subject to increased cost sharing). For example, an MA organization may contract with a particular grocery store to furnish their food and produce benefit. However, in a PPO, enrollees may purchase eligible food and produce at another non-contracted grocer (out-of-network provider) and be reimbursed for those covered items. CMS expects MA PPOs to have processes to verify out-of-network reimbursement is only made 
                        <PRTPAGE P="17489"/>
                        for plan-covered services and to indicate to enrollees the process by which reimbursement can be made. As noted above, that process should be mindful of enrollees in rural or remote areas with limited access to providers and internet-based communication methods.
                    </P>
                    <P>Finally, CMS reminded MA plans that the regulations at § 422.112(b)(3) provide for coordinated care MA plans to include community-based services in their plans for coordination and continuity of care for enrollees. In addition, § 422.112(b)(3) specifically states that MA coordinated care plans are required to “coordinate MA benefits with community and social services generally available in the area served by the MA plan.” MA plans may contract with community-based organizations to provide supplemental benefits that are compliant with the statutory and regulatory requirements. The Agency strongly encouraged, for example, an MA plan that elects to offer a food and produce supplemental benefit to do so via a community-based organization that is able to process the benefit through a debit card. CMS understands that in some areas there may be a limited number of community-based providers, including small businesses. However, plans were strongly encouraged to partner with community-based providers or other local, smaller businesses when offering supplemental benefits, particularly regarding food and produce benefits that may be offered to chronically ill enrollees under SSBCI regulations at § 422.102(f). Encouraging plans to contract with community-based providers will improve enrollee access to benefits. With covered benefits available in their communities, enrollees will be able to more readily and easily obtain and use covered benefits and thus have the potential to improve their overall health.</P>
                    <HD SOURCE="HD3">5. Additional Disclosure Guardrails</HD>
                    <P>To increase transparency for beneficiaries accessing plan-covered benefits, CMS also proposed to add additional disclosure requirements specific to supplemental benefits under § 422.111. Section 422.111(b) currently requires MA organizations to disclose mandatory and optional supplemental benefits and the premium for those benefits. Additionally, CMS proposed to amend § 422.111(b)(6) to state that MA organizations must disclose any mandatory supplemental benefits (including reductions in cost sharing) or optional supplemental benefits, the premium for optional supplemental benefits, and any applicable conditions and limitations associated with receipt or use of supplemental benefits. CMS also proposed to clarify that this disclosure must include eligible OTC items and, where supplemental benefits are administered through a debit card, must specify which benefits may be accessed using the debit card. CMS believes that such disclosure is necessary to ensure transparency considering the growth of the scope of supplemental benefits and authorized administrative flexibilities, such as the use of plan-furnished debit cards to administer certain supplemental benefits. This will help ensure that plan enrollees are sufficiently aware of what covered benefits may be accessed through any debit card they receive from their plan.</P>
                    <P>Lastly, regarding OTC items, longstanding CMS guidance (section 40.1 of Chapter 4 of the Medicare MCM) defines OTC items as health related items and medications that are available without a prescription, and § 422.102(c)(2) provides that permissible supplemental benefits are items and services that are not covered by Medicare Part A, Part B or Part D. Per § 422.100(c)(2), plans may never offer as a supplemental benefit something that is covered under Part B or Part D for the plan's enrollees, including an OTC item or medication. Additionally, while the 2022 Final Rule did include OTC items as an example of permissible primarily health-related supplemental benefits (86 FR 5971), it did not include a non-exhaustive list of acceptable and non-acceptable items. CMS has also received feedback that a non-exhaustive list could provide further clarity for MA organizations. Therefore, CMS included a non-exhaustive list of acceptable and non-acceptable items here. Examples of permitted primarily health-related OTC items that have been reviewed and approved by CMS during the bid review process include, but are not limited to: amplified phones, analgesics, antacids, anti-bacterial grooming products (when recommended by a provider), antihistamines, anti-inflammatories, antiseptics, blood pressure cuffs, callous/wart remover, custom made compression garments (if furnished under circumstances when it would not be covered by the Part B benefit), contact lens solution and cases, over the counter contraceptives (such as condoms and over the counter, non-prescription birth control pills), cotton swabs, COVID-19 tests (over the counter), decongestants, dressing and eating aids, extension grabbers or reaching aids, facial cleaners (including acne wash), feminine hygiene products (such as douche, lubricants, pads, tampons, wipes), fiber supplements, first aid supplies, energy protein bars and power drinks, nutritional drinks/shakes, hand sanitizer, hearing aid batteries, hearing amplifiers, herbal supplements, hip kits, dietary supplements (such as CoQ10, garlic, gingko biloba, melatonin, and saw palmetto), incontinence supplies (such as adult diapers and under pads), insulin refrigeration units, and lip soothers/balms (non-medicated), low vision aids, magnifying glasses, medicine dispensers, mouth/oral care products (such as toothbrush/paste, floss, mouthwash, denture adhesives/cleaners), naloxone (if furnished under circumstances when it would not be covered by Medicare Part B or Part D), night lights, nicotine replacement therapy (NRT), pain relief products (such as Epsom salt and ice packs), pill bottle openers, pill/tablet boxes, cutters, and crushers, pulse oximeters, probiotics, nonprescription reading glasses, shoe insoles/inserts/arch supports, skin moisturizers for dry skin, skin protectant (such as diaper rash ointment, moleskin, mosquito repellent and petroleum jelly), witch hazel, sleep aids, soap (doctor recommended antibacterial/antimicrobial), sunscreen, supportive items (such as compression hosiery, rib belts and elastic knee support), toilet lights, vitamins and minerals, nonprescription weight loss items, weight scales, and disposable face masks (to protect against respiratory illnesses). Although this is not considered to be an exhaustive list of acceptable OTC items, CMS solicited comment on whether there are additional items that stakeholders believe should be included on this list.</P>
                    <P>
                        CMS has also reviewed items that have been determined not to be permissible MA supplemental benefits because they do not meet the requirement that the item or service be primarily health-related. Such OTC items that cannot be covered as MA supplemental benefits include air conditioners, baby items, bad breath remedies (gum and breath mints), bagging fees, body scrubs, cleaning products (Clorox and Lysol), clocks, dehumidifiers, deodorant, grooming/shaving supplies, hair care (shampoo, conditioner, dye, bleach, hair removal and hair growth products), humidifiers, jar openers, paper products (tissue, toilet paper and paper towels), perfume, pest control, skin moisturizers used for anti-aging, teeth whiteners, water bottles, and personal coolers. It was noted that items such as air conditioners, cleaning products, dehumidifiers, humidifiers, grooming supplies to assist with hygiene, paper 
                        <PRTPAGE P="17490"/>
                        products (tissue, toilet paper and paper towels), and pest control may be permissible as a non-primarily health-related SSBCI provided the item has a reasonable expectation of improving or maintaining the health or overall function of the enrollee and meets the standards at § 422.102(f). For example, research indicates that air conditioners may improve the breathing of patients with COPD and asthma.
                        <SU>81</SU>
                        <FTREF/>
                         CMS solicited comment on these listed items.
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             
                            <E T="03">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5291496/.</E>
                        </P>
                    </FTNT>
                    <P>
                        CMS reiterated that the list of permissible primarily health-related OTC items set forth in the Contract Year 2026 proposed rule was non-exhaustive. CMS also included a non-exhaustive list of items that are not primarily health-related but could be offered as a non-primarily health-related SSBCI, provided the requirements under § 422.102(f) are met. CMS reviews bids each year to ensure that proposed supplemental benefits meet the applicable regulatory and statutory standards.
                        <SU>82</SU>
                        <FTREF/>
                         For example, MA organizations may propose to offer OTC items not on this list and CMS may come across items in the future, not listed here, that CMS believes do not meet the definition of a supplemental benefit per § 422.100(c)(2) or are not primarily health-related per § 422.100(c)(2)(ii). However, the Agency believes including these lists in this preamble discussion will help MA organizations consistently apply the requirements at §§ 422.100(c)(2) and 422.100(c)(2)(ii) and assist MA organizations when planning and preparing their annual bid packages.
                    </P>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             MA organizations that are looking to cover new or novel benefits are strongly encouraged to raise those to CMS well in advance of bid submission to allow ample time for the MA organization to provide, and CMS to review, information explaining how the applicable statutory and regulatory standards are met for the proposed benefits without the time pressures of the bid review process.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">6. Marketing Supplemental Benefits</HD>
                    <P>Another consideration related to debit cards is MA organizations' marketing tactics. CMS has become aware of certain advertisements that solely mention debit cards, or marketing terms such as “Medicare flex cards,” with an alluring value attached to them, potentially giving false impressions that the card itself is the benefit.</P>
                    <P>In the Contract Year 2026 proposed rule, CMS raised concerns with these advertisements, articulating that there could be a risk that a beneficiary might view this type of advertisement and make an enrollment decision based on the belief that, by enrolling in the plan, they will automatically receive a card with “free” money to spend wherever they choose. CMS proposed new parameters for MA organizations' marketing of supplemental benefits. Specifically, CMS proposed to add new paragraph (b)(11) to § 422.2263, prohibiting MA organizations from marketing the dollar value of a supplemental benefit or the method by which a supplemental benefit is administered, such as use of a debit card by the enrollee to provide the plan's payment to the provider for the covered services. CMS solicited comment on all aspects of this proposal.</P>
                    <P>CMS thanks commenters for their input on CMS's proposed changes to requirements for the administration of supplemental benefits coverage through debit cards. CMS received the following comments and provided responses as follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         While several commenters supported the proposed rule, a number of commenters raised concerns about potential member confusion related to various aspects of debit card use. One commenter expressed concern that the “combined benefit option” may be confusing, as beneficiaries might not understand they are using their allowance on food at the expense of other benefits like vision and dental. Some commenters also raised concerns that enrollees may unwittingly use cards for uncovered services and be found liable later. Given these concerns about confusion and potential liability, many commenters also expressed support for the proposed additional disclosure requirements around supplemental benefits and how to access them via debit cards. Several commenters also supported the requirements for customer service and support around using debit cards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for sharing their concerns and support of this rule. CMS has heard from various stakeholders that enrollees are often confused when using plan debit cards. The clarifications being finalized at 42 CFR 422.111(b)(6) and the disclosure and customer service requirements under new subsection 422.102(g) address these concerns. As stated in the Contract Year 2026 proposed rule, plans are currently required to disclose all covered benefits. Given the rapid growth of MA plans' use of debit cards to furnish covered benefits, CMS is requiring that this disclosure must include eligible OTC items and, where supplemental benefits are administered through a debit card, specify which benefits may be accessed using the debit card. Requiring plans to provide debit card usage instructions and customer service support will significantly improve the enrollee experience. While many plans already have customer service processes in place, CMS is requiring that these processes include assistance with debit card access to benefits when necessary. These requirements are expected to enhance the enrollee experience, and CMS will continue to monitor outcomes.
                    </P>
                    <P>CMS also thanks commenters for noting confusion around the “combined benefit option,” also referred to as a maximum plan allowance for a package of supplemental benefits under § 422.102(a)(6)(ii). MA plans have long been able to structure benefits that allow enrollees to choose from a group of covered, eligible supplemental benefit options. However, CMS acknowledges that when plans use this structure in combination with debit cards, it can create confusion as enrollees may not realize that using the card for one benefit means foregoing another. To address this, CMS emphasizes throughout this rule that plans are required to disclose all benefits and accompanying limitations to their enrollees. Specifically, CMS proposed and is finalizing an amendment to § 422.111(b)(6) to require disclosure of the applicable conditions and limitations associated with the receipt or use of supplemental benefits. When offering a “combined benefit option,” plans must clearly communicate any associated limitations to enrollees, including that selecting one benefit means foregoing another benefit under this benefit structure.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters raised concerns about the feasibility and administrative burden of the real-time verification requirement. Some commenters argued that requiring real-time verification with SKU codes for all items would limit access and use of cards, and that plans are at different operational levels regarding their ability to perform point-of-sale verification. Some commenters also asserted that various types of debit cards exist, each with distinct functionalities and operational characteristics that may have varying levels of compatibility with these requirements. Several commenters asserted that even for plans already taking verification steps through third-party fintech card administrators, operational changes could add significant burden given the variety of retailer hierarchies of product identification. A commenter expressed concern that the point-of-sale verification may have the unintended consequence of detracting from the beneficiary experience, with beneficiaries potentially facing 
                        <PRTPAGE P="17491"/>
                        additional steps with added confusion at the point of sale. A commenter noted that dental benefit and eligibility verification through current HIPAA-mandated standards are insufficient to support the real-time identification mechanism of covered services as described. Another commenter stated that real-time verification technology may be incompatible with certain benefits. Some commenters requested that CMS provide examples of permissible methods of meeting the real-time identification requirements. Other stakeholders supported the real-time verification requirements, emphasizing that these processes are necessary to ensure beneficiaries receive the correct benefits and to enhance the enrollee experience. Another commenter, while supportive of real-time verification, requested that CMS permit either electronic or manual verification of plan-covered benefits at point-of-sale.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for feedback. CMS also reminds commenters that there is longstanding precedent requiring plan debit cards to be explicitly linked to covered items. CMS guidance (Medicare MCM Chapter 40.3) states that debit cards must be electronically linked to eligible, covered items. In the January 2021 Final Rule (86 FR 5913), CMS explained that MA organizations must properly restrict debit cards to appropriate providers and covered benefits to ensure compliance with §§ 422.100(c)(2) and 422.102(a). CMS stated directly that if a plan cannot implement such restrictions—for example, through merchant codes, inventory approval system codes, or other mechanisms—then debit cards may not be an appropriate mechanism for that plan to use (86 FR 5913). It has been and continues to be CMS's expectation that if a plan cannot appropriately restrict debit cards to actual covered benefits, this mechanism should not be used. The codifications in this rule formalize and expand upon these existing expectations for greater clarity given the growth of debit card usage.
                    </P>
                    <P>Regarding real-time verification specifically, this capability is necessary to ensure ease of access, transparency, proper payment, and fraud prevention, aligning with the Administration's commitment to combating fraud, waste, and abuse in federal programs. Real-time verification helps eliminate fraud by preventing unauthorized purchases, ensuring that benefits are used only for their intended purpose, and reduces the chances of plans inadvertently providing payment for non-covered items, thus ensuring compliance with CMS requirements. Additionally, real-time verification removes uncertainty at the point of sale for plan enrollees and provides assurance that the purchase is aligned with plan rules, which is particularly important for a population that may be dealing with reduced functionality.</P>
                    <P>CMS's primary concern is that benefits are furnished appropriately to beneficiaries. While debit cards offer one method to administer benefits, they are not the only option available to plans, nor mandatory. Plans may administer supplemental benefits through other methods, including but not limited to, manual claims processing and online claims submission forms. In fact, plans may find these processes more operationally appropriate for certain benefits. CMS originally allowed debit cards as a flexibility to give plans additional options for benefit administration. However, if it is impractical, unfeasible, or difficult to effectuate a particular supplemental benefit through a debit card, CMS does not expect a debit card to be used. Plans should choose the method—whether debit cards, receipt-based reimbursement, electronic catalogs, home delivery, or other approaches—that best enable them to furnish benefits in compliance with program requirements.</P>
                    <P>In response to the request for examples of permissible methods of meeting the real-time identification requirements, CMS refers commenters to the January 2021 Final Rule, which noted that plans could use merchant codes, inventory approval system codes, or other similar mechanisms (86 FR 5914). CMS recognizes that health plans have successfully utilized debit cards to deliver healthcare benefits for many years and that the industry has developed substantial expertise in this area. CMS anticipates continued technological advancement and therefore refrains from prescribing specific technological solutions or providing exhaustive examples. It is not CMS's intent to dictate the technology employed, but rather to establish clear expectations for outcomes: enrollees should experience seamless front-end user experiences that preserve both ease of access and transparency. Finally, regarding the request to permit either electronic or manual verification of plan-covered benefits at point-of-sale: CMS does not consider manual verification to be real-time verification. Electronic verification requires automated, system-to-system data exchange and validation processes that occur without manual intervention. However, plans may certainly use manual verification as a troubleshooting alternative when experiencing technological issues with their electronic verification systems. This approach can serve as a temporary workaround to ensure continuity of operations while technical problems are being resolved.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Similarly, some commenters stated that difficulties could arise at small or independently-owned retail stores that do not have the same technological infrastructure or capacity as larger national chain stores. Another commenter explained that in many cases, plans do not have a contractual relationship with retail stores where debit cards are commonly used, as there is often a financial technology company in the middle. They explained that these plans select products that should be covered, then the third-party administrator and the retail store match products to SKUs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for sharing their concerns and providing additional insight into how plans operationalize the furnishing of covered supplemental benefits through debit cards. It is important to reiterate that MA operates under a particular structure governed by statutory and regulatory rules. MA plans that offer coordinated care plans may specify the networks of providers from whom enrollees may obtain services, including supplemental benefits. Furthermore, MA organizations have the discretion to choose with whom they contract to furnish services. Section 1854(a)(6)(B)(iii) of the Act, commonly known as the “non-interference clause,” prohibits CMS from requiring an MA plan to contract with a particular health care provider, including vendors, to furnish a benefit. This applies to supplemental benefits as well. CMS recognizes that the technological landscape has evolved and many plans no longer contract directly with retailers. Instead, they partner with financial technology companies to oversee card usage, which impacts which vendors can participate. These arrangements are acceptable, provided that plans comply with CMS requirements, especially disclosure requirements which describe the applicable conditions and limitations associated with the use of supplemental benefits. Finally, CMS reiterates that debit cards are not unrestricted cash cards. Section 1851(h)(4)(A) of the Act prohibits plans from providing cash to enrollees. Instead, debit cards serve as one mechanism that plans may use to furnish covered benefits. Consistent with the MA program structure—in which plans furnish services through a 
                        <PRTPAGE P="17492"/>
                        network of providers or vendors—debit cards are not intended to be usable everywhere.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed support for having alternative reimbursement processes available to protect enrollee access to benefits. Some plans acknowledged that they already have processes in place for alternative reimbursement and one plan requested that CMS recognize these existing practices while clearly stating any intended changes to standard industry practices. Another commenter supported the proposal but recommended that for geographic areas where vendor capacity for alternative processes does not currently exist, CMS should allow adequate timeframe for vendors to build out this function.
                    </P>
                    <P>However, other commenters raised concerns about the administrative burden that may be associated with manual receipt reimbursement processes as an alternative to debit cards. Some plans stated that supplemental benefits like OTC and food allowances rely on CMS-approved product listings comprising thousands of items, and that the automated nature of debit cards ensures real-time validation at the point of sale. Several commenters indicated that mandating a manual reimbursement process would require extensive administrative effort, including additional full-time staff to individually review each item. Some plans stated that current card vendors lack infrastructure to manage receipt reimbursements, meaning the burden would fall entirely on plans. Another commenter expressed concern that requiring an alternative reimbursement process could lead to member confusion, as the debit card enables members to know at the point of service whether a product is eligible, whereas after-the-fact filing could result in situations where purchases made in good faith are not actually reimbursable. Some commenters requested examples from CMS of permissible alternate payment methods that would comply with requirements, as well as examples of issues that would warrant using an alternate process. Several commenters expressed concern that allowing alternative processes would set a precedent with members that they could obtain other plan services through non-contracted locations or providers.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their feedback. As described in the Contract Year 2026 proposed rule, longstanding guidance at Section 40.3.1 of Chapter 4 of the Medicare MCM requires plans to allow manual reimbursement for OTC purchases via submitted receipts in certain situations. To maintain enrollee access for all benefits administered through a debit card, CMS proposed to codify at § 422.102(g)(2)(iii) that plans must have an alternative reimbursement process for eligible expenses. This would include technical issues such as difficulty using the debit card, provider system failures, erroneous transaction declines, or other situations where debit card use is unfeasible. However, based on feedback from commenters, CMS agrees that the requirement as proposed could inadvertently cause confusion among enrollees regarding how to access in-network benefits. Therefore, CMS will amend § 422.102(g)(2)(iii) to more specifically state that plans must have an alternative process that allows for reimbursement of eligible expenses for plan covered benefits in circumstances where the debit card is unusable at the point of sale, including but not limited to debit card malfunction.
                    </P>
                    <P>As noted throughout this rule, plans must ensure that beneficiaries maintain access to covered supplemental benefits regardless of the payment mechanism used to administer those benefits. Whether a plan provides access through a debit card or another payment method, the underlying benefit must remain available to eligible enrollees. The manual reimbursement requirement serves as a safeguard to ensure access to eligible services in situations where the debit card becomes unusable due to malfunction, damage, or other technical failures. This requirement protects beneficiaries from losing access to their covered benefits simply because the payment mechanism is temporarily unavailable.</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that CMS reconsider its proposal to allow PPO supplemental benefits to be used at any retailer, noting that expanding benefits to any retailer would require plans to manage approvals and validations manually, significantly increasing administrative complexity. Another commenter asked CMS not to finalize the out-of-network reimbursement requirement. Some commenters expressed concern that CMS's requirement for plans to provide all benefits at in-network cost-sharing rates when no in-network provider is available could expose the program and plans to potential bad actors, as many supplemental benefit providers are not Medicare-enrolled medical providers and are vetted through contractual agreements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Regarding PPO out-of-network reimbursement, CMS notes that current regulations at § 422.4(a)(1)(v) require MA plans that are PPOs to provide reimbursement for all covered services, regardless of whether the services are furnished within the plan's contracted network. As CMS stated in the 2005 final rule (70 FR 4598) establishing this requirement, CMS intended that local and regional PPOs reimburse enrollees for all covered benefits, regardless of whether those benefits are provided within the network of providers. This longstanding requirement applies regardless of the mechanism through which a benefit is furnished.
                    </P>
                    <P>Additionally, while plans may maintain established systems for administering supplemental benefits—such as limiting debit card functionality to contracted vendors—supplemental benefits remain covered benefits, and PPOs must still provide reimbursement for covered services obtained out-of-network. CMS has long articulated a similar expectation in sub-regulatory guidance. For example, section 40.3.1 of Chapter 4 of the Medicare MCM states that MA plans, regardless of the payment method used to furnish OTC benefits, must provide a mechanism for manual reimbursement under described circumstances (such as when a debit card network is not functioning). This guidance reflects CMS's longstanding expectation that the method used to administer a benefit does not alter a plan's obligation to ensure access to and reimbursement for covered supplemental benefits in certain situations.</P>
                    <P>To provide additional clarity, CMS will further amend § 422.102(g)(2)(iii) to specify that plans must establish an alternative process that permits reimbursement of eligible expenses in circumstances where the debit card is unusable at the point of sale, as described earlier in this section, as well as when a beneficiary is entitled to obtain covered benefits out-of-network. As a best practice, plans retain the discretion to implement appropriate verification procedures and safeguards to ensure reimbursement is provided only for actual covered items. CMS recommends that plans consider these requirements when deciding whether a debit card is the most appropriate mechanism for furnishing certain covered benefits.</P>
                    <P>
                        For Health Maintenance Organization (HMO) plans specifically, it is important to note that “eligible expenses” under the manual reimbursement requirement refer exclusively to covered services obtained in accordance with the plan's network requirements. In an HMO, manual reimbursement does not extend to purchases made from out-of-network providers or vendors or suppliers, as 
                        <PRTPAGE P="17493"/>
                        such services would not constitute eligible covered benefits under an HMO plan structure. The intent of this provision is to protect beneficiary access to covered benefits when the debit card payment mechanism fails, not to expand coverage to out-of-network services that fall outside the plan's benefit design. CMS reminds readers, however, that even if an MA plan chooses to administer supplemental benefits through a debit card, the plan must still arrange for and cover any medically necessary covered benefit outside of the plan provider network, at in-network cost sharing, when an in-network provider or benefit is unavailable or inadequate to meet an enrollee's medical needs under 42 CFR 422.112(a)(1)(iii).
                    </P>
                    <P>Finally, in response to the request that CMS not finalize the requirement that MA plans provide all benefits at in-network cost-sharing rates when no in-network provider is available, CMS again notes that this is an existing requirement at 42 CFR 422.112(a)(1)(iii) and is applicable to all covered benefits, including supplemental benefits, regardless of delivery method. This requirement applies only when a plan lacks an adequate contracted provider or vendor to furnish a covered benefit—a situation expected to be rare. It does not require plans to always cover benefits outside the provider network at in-network cost sharing.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS not finalize the removal of the proposed language “or other means” at proposed § 422.102(a)(6)(i), stating that it would unnecessarily restrict plans from using alternatives such as stored value cards or future technological developments like mobile applications.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for this feedback. The Contract Year 2026 proposed rule proposed to remove “or other means” from the regulation and solicited comments on which alternative delivery methods beyond manual reimbursement or debit cards might be unintentionally eliminated, and whether stored value cards can meet the requirements at § 422.102(g), specifically regarding real-time point-of-sale verification and plan-year-only restrictions.  
                    </P>
                    <P>CMS clarifies that, as explained in the January 2021 rule, the cost-sharing reduction flexibilities authorized at § 422.102(a)(6)(i) and (ii) do not exclude stored value cards, provided they can be programmed to permit their use only for the purchase of specific, covered items and services. The changes proposed at § 422.102(a)(6) were not intended to prohibit stored value cards, provided they comply with the requirements at § 422.102(g). CMS solicited comment on whether to remove the phrase “or other means” from § 422.102(a)(6)(i) and instead specify the types of cards or mechanisms that would satisfy the proposed requirements under § 422.102(g).</P>
                    <P>CMS received no direct comments on these questions but appreciates the commenter noting the possible unintended consequences of removing “or other means.” Therefore, CMS will not finalize the removal of “or other means” in § 422.102(a)(6)(i). Stored value cards will continue to be permitted as a mechanism to administer reduced cost sharing and covered benefits, provided such cards comply with the requirements under § 422.102(g). CMS anticipates continued innovation in this technological space and welcomes opportunities to engage with stakeholders on emerging advancements.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters requested clarification on various technical aspects of the proposal, including: examples of how plans can meet disclosure requirements and model documents; whether plans may use the same physical card year to year with only the amount expiring; whether a plan can disclose categories of OTC items as opposed to each individual OTC item; and more detailed specifications for customer service requirements. Several commenters stated that MA organizations already have processes in place for delivering plan-covered supplemental benefits and providing education to enrollees, and that the objective of the new proposed requirements is unclear.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the comments received and acknowledges that many plans are likely to have processes in place to meet several of the proposed requirements in this rule. As stated throughout this rule, many of these requirements primarily codify and further clarify existing expectations. In response to requests for clarification on whether plans may use the same physical card year to year with only the benefit amount expiring, CMS proposed and is finalizing at § 422.102(g)(2)(iv) that supplemental benefits administered through debit cards must be limited to the plan year. Plans may allow enrollees to use the same physical debit card in subsequent plan years; however, the dollar amounts or benefit allocations associated with the card cannot carry over from one plan year to the next. This ensures that each plan year's benefits are utilized within the designated plan year period.
                    </P>
                    <P>
                        Regarding whether a plan can disclose categories of OTC benefits as opposed to listing each individual benefit, the listing of categories of covered OTC benefits is permissible provided the plan discloses any limitations and is able to provide more specific details to the enrollee if necessary. CMS declines to provide more prescriptive guidance, as the purpose of these requirements (
                        <E T="03">e.g.,</E>
                         adequate transparency and enrollee support) is clear, and CMS does not wish to be overly restrictive to plans that may already have adequate processes in place. CMS will continue to engage in dialogue with plans and may provide additional guidance at a later date as necessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that cards function as inducements and that beneficiaries may make enrollment decisions based on having a “card” rather than the overall benefit package.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in the Contract Year 2026 proposed rule, CMS shares concerns that beneficiaries may base enrollment decisions on perceived debit card access rather than the comprehensive benefits package. CMS encourages all enrollees and potential enrollees to consider the full benefits package when selecting a plan. The increased disclosure requirements in this rule are designed to improve transparency and support informed enrollment decisions, and CMS will continue to monitor developments in this area and welcomes ongoing stakeholder feedback.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern about lack of transparency surrounding delivery and use of benefits. While supporting the proposal, another commenter noted concerns that it would not allow other agencies or entities to monitor whether plan-provided debit cards are being used only for items that meet criteria. Another commenter suggested that CMS should work to ensure MA plans share information with providers on supplemental benefits available to patients in real time, at the point of care, and in a standardized manner. A commenter, while supporting the proposal, expressed concern that the proposed guardrails do not prevent someone other than the beneficiary from using the card.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for sharing their concerns. It is noted that existing requirements mandate MA plans to disclose all supplemental benefits. The new requirements clarify that such disclosures must include all applicable conditions and limitations associated with the receipt or use of supplemental benefits, and that this disclosure applies to all benefits, including those administered through a 
                        <PRTPAGE P="17494"/>
                        debit card. The existing requirements, along with the proposed disclosure clarifications regarding applicable conditions and limitations and benefits furnished through debit cards, are sufficient to ensure transparency. Additionally, per § 422.2267(e)(34), plans offering CMS-approved SSBCI are required to include the SSBCI disclaimer in all marketing and communications materials that mention SSBCI. In the SSBCI disclaimer, plans must list the chronic condition(s) the enrollee must have in order to be eligible for the SSBCI (in accordance with CMS requirements). Plans must also convey in the SSBCI disclaimer that even if the enrollee has a listed chronic condition, the enrollee will not necessarily receive the benefit because other eligibility and coverage criteria also apply. Additionally, in section IV.L. of this rule, CMS is finalizing a requirement that MA organizations post their SSBCI eligibility criteria on their plan websites. CMS believes this requirement, together with existing transparency requirements, will enhance overall transparency regarding SSBCI benefits.
                    </P>
                    <P>Regarding comments about provider transparency, CMS expects MA plans to ensure that contracted providers are informed about covered benefits and plan policies relevant to the furnishing and coordination of care. Such information-sharing supports appropriate benefit administration and care coordination between the plan and its network providers. Lastly, CMS thanks the commenter for raising concerns that the proposed guardrails do not prevent non-enrollees from using the debit card. CMS shares these concerns about potential abuse and will further evaluate this issue for possible additional guardrails in future rulemaking.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed CMS requiring debit card transactions to be included in the Explanation of Benefits (EOB).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Thank you for the comment. As explained in the Contract Year 2026 proposed rule, MA organizations must send enrollees an Explanation of Benefits (EOB) monthly or quarterly that includes all Part C claims activity—covering basic benefits, mandatory and optional supplemental benefits, and SSBCI. Each claim must show a descriptor, billing code, amount billed, approved reimbursement, plan payment, and enrollee liability. EOBs must also include year-to-date information such as amounts toward the Maximum Out-of-Pocket (MOOP) limit. These existing requirements apply to all benefits, including those accessed via a plan debit card, regardless of delivery method. Plans experiencing operational challenges in meeting these requirements when using debit cards may wish to evaluate whether an alternative mechanism would be more suitable for furnishing covered benefits.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested additional items be added to the allowable OTC list and expressed concerns that non-allowable examples—such as grooming supplies, shampoo, lotion, and hygiene-related items—are overly restrictive. These commenters argued that requiring these items to be available only to members with certain chronic conditions would limit access to many members and increase benefit complexity, making it more difficult to use. They asserted that requiring some OTC items to be offered to all enrollees as primarily health-related supplemental benefits, while allowing others to be limited to chronically ill enrollees as SSBCI, could lead plans to reduce the overall scope of their OTC offerings. Another commenter requested that if CMS proceeds with codifying these changes, the Agency should provide an exhaustive list of allowed and prohibited OTC products to ensure all plans operate under consistent expectations. Additionally, a commenter suggested that only oral health products bearing the ADA Seal of Acceptance should be included as eligible OTC items for purchase with debit cards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their suggestions. As explained in the Contract Year 2026 proposed rule, plans have indicated that a non-exhaustive list would provide further clarity for MA organizations and would assist in their bid preparations. Such lists were common in previous sub-regulatory guidance, making this an appropriate opportunity to provide an updated list of items CMS has previously approved. CMS declines to add more items to this list because an item's absence does not prohibit a plan from proposing to offer it. CMS also declines to provide an exhaustive list, as this would inhibit plans' ability to further innovate in this area. Regarding the comment that plans only provide oral health products bearing the ADA Seal of Acceptance, plans may propose to offer any OTC provided they meet CMS requirements, particularly those at § 422.100(c)(2) and under § 422.102. Further delineations, such as products endorsed by specific independent advisory groups, are at the discretion of the plan. With respect to grooming supplies, shampoo, lotion, and similar hygiene-related items, a supplemental benefit is not primarily health-related if the item or service is used solely or primarily for cosmetic, comfort, general use, or social determinant purposes (86 FR 5971). CMS considers such items to be general use items that do not qualify as primarily health-related benefits. Alternatively, plans may propose to offer these items as SSBCI benefits, provided all requirements under § 422.102(f) are met.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that CMS allow food, housing, and transport as primarily health-related, and another commenter requested a non-exhaustive list of allowable special supplemental benefits for the chronically ill. Some commenters raised concerns about cards counting towards resources in federal programs and suggested CMS should issue a rule clarifying that these benefits are not income for purposes of Medicaid and other federally funded programs. A commenter recommended CMS regularly analyze and report plan-level data on supplemental benefits to assess their impact on health expenditures and outcomes. Another commenter suggested that CMS expand supplemental benefit data reporting. Others expressed concerns regarding the potential consequences of VBID sunsetting, particularly the inability of plans to transition certain VBID benefits in MA. Some FQHCs requested CMS update Medicare Claims Processing Manual guidance concerning supplemental payments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments. However, they are out of scope of this regulation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Regarding comments on CMS's proposal to prohibit MA organizations from marketing the dollar value of a supplemental benefit or the method by which a supplemental benefit is administered, most comments were not supportive. The majority of commenters argued that prohibiting marketing of supplemental benefit dollar values would reduce transparency and harm informed decision-making. They stated beneficiaries have a right to know benefit values before enrolling, that supplemental benefits were often the most important reference point, and that the restrictions would create “secret benefits.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for their feedback. In consideration of the comments received, at this time, CMS has decided not to finalize the proposed amendment to § 422.2263, regarding MA organizations' marketing of supplemental benefits.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters also questioned how beneficiaries would obtain this information beyond dense 
                        <PRTPAGE P="17495"/>
                        Evidence of Coverage documents and noted that failing to disclose benefit values was itself potentially misleading. Commenters noted that without benefit value information, beneficiaries could not differentiate between similar plans or compare value across MA organizations. which could create distrust and cause beneficiaries to decline plans they might otherwise prefer. In addition, some commenters were concerned that the proposal would burden seniors by requiring them to call multiple plans for critical information, potentially leading to more complaints, unwitting enrollment, and benefit misuse.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these additional concerns raised by commenters. As noted previously, CMS is not finalizing the proposed supplemental benefits marketing provision.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that low-income seniors and dual-eligible beneficiaries would be particularly affected if the proposal to restrict debit card marketing were finalized. For example, commenters noted that in Puerto Rico, where over 45 percent of MA enrollees were dual eligible, debit card availability and benefit dollar values were most relevant to low-income seniors. Commenters stated that supplemental benefits filled gaps in federal benefits, helped cover Part B premiums, reduced pharmacy costs, and provided food and nutrition services, and furthermore, beneficiaries with specific health needs relied on supplemental benefits existing only in MA plans. In addition, a few commenters believed CMS's proposed debit card marketing restrictions would disincentivize plan innovation and stated it was not within CMS legal authority to impose judgment on which benefits were most significant to beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS again thanks commenters for this valuable input. In light of concerns raised by the commenters and as previously discussed, CMS is not finalizing the marketing proposal at this time.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Other commenters urged CMS to focus on bad actors rather than broadly restricting all plans. They recommended revising guidance to provide clear examples of prohibited misleading marketing, working with plans to develop clearer communication standards, requiring disclaimers when marketing benefit values, and establishing limits on card amounts and approved services.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks commenters for these ideas and may take them under consideration for future policymaking regarding supplemental benefit marketing issues.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported prohibiting marketing of administration methods but opposed prohibiting marketing of dollar values, arguing this deprived beneficiaries of critical decision-making information. They understood CMS concerns about consumer confusion but believed these should be addressed with more information and transparency, not less. They also noted that not providing information on benefit access could result in beneficiary confusion contrary to CMS transparency efforts and could negatively impact Star Ratings measures based on the Complaints Tracking Module.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this feedback. While CMS is opting not to finalize this aspect of the proposal at this time, the Agency may take this feedback into consideration for future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported CMS efforts to prevent misleading advertising that interfered with beneficiaries' plan selection, particularly ads suggesting “free money” without restrictions. They endorsed prohibiting marketing of benefit administration methods. Commenters reported instances where flex card advertising induced individuals to disenroll from PACE or switch plans, resulting in loss of care. A few commenters recommended additional safeguards requiring ads to identify coverage limits, covered items, and eligibility restrictions in the same font or volume as the main content. Other commenters recommended limiting television, billboard, and radio marketing mentioning debit card amounts while allowing such information in plan materials with appropriate disclaimers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS again thanks commenters for their comments and recommendations on these various issues. CMS is not finalizing the marketing proposal at this time but will consider the comments received for future policymaking.
                    </P>
                    <HD SOURCE="HD3">Summary of Regulatory Changes</HD>
                    <P>After considering the comments received and for the reasons outlined in the Contract Year 2026 proposed rule and in responses to comments, CMS is taking the following actions in this final rule:</P>
                    <P>1. Finalizing § 422.111(b)(6) as proposed, which requires MA plans to disclose all supplemental benefits, including applicable conditions and limitations, eligible over-the-counter items, and benefits accessible through debit cards.</P>
                    <P>2. Finalizing the new subparagraph § 422.102(g) with modifications, specifically amending § 422.102(g)(2)(iii) to state that plans must have an alternative process that allows for reimbursement of eligible expenses for plan covered benefits in circumstances where the debit card is unusable at the point of sale, including but not limited to debit card malfunction or when a beneficiary is entitled to obtain covered benefits out-of-network.</P>
                    <P>3. Not finalizing the proposed amendment to § 422.102(a)(6)(i), which would have eliminated “or other means” as an acceptable way to administer cost-sharing reductions.</P>
                    <P>4. Not finalizing the proposed amendment to § 422.2263, which would have prohibited MA organizations from marketing the dollar value of a supplemental benefit or the method by which a supplemental benefit is administered, such as use of a debit card by the enrollee to provide the plan's payment to the provider for the covered services.  </P>
                    <HD SOURCE="HD1">V. Medicare Advantage/Part C and Part D Prescription Drug Plan Quality Rating System (Star Ratings) (§§ 422.162, 422.164, 422.166, 423.182, 423.184, and 423.186)</HD>
                    <HD SOURCE="HD2">A. Introduction</HD>
                    <P>
                        CMS develops and publicly posts a 5-star rating system for Part C,
                        <SU>83</SU>
                        <FTREF/>
                         more commonly referred to as Medicare Advantage (MA), and Part D plans as part of its responsibility to disseminate comparative information, including information about quality, to beneficiaries under sections 1851(d) and 1860D-1(c) of the Act. The Part C and D Star Ratings system is used to determine quality bonus payment (QBP) ratings for MA plans under section 1853(o) of the Act and the amount of MA beneficiary rebates under section 1854(b) of the Act. We use multiple data sources based on the collection of different types of quality data under section 1852(e) of the Act to measure the quality and performance of contracts, such as CMS administrative data, surveys of enrollees, and information provided directly from health and drug plans. CMS regulations, including §§ 417.472(j) and (k), 422.152(b), 423.153(c), and 423.156, require plans to report on quality improvement and quality assurance and to provide data that help beneficiaries 
                        <PRTPAGE P="17496"/>
                        compare plans. The methodology for the Star Ratings system for the MA/Part C and Part D programs is codified at §§ 422.160 through 422.166 and 423.180 through 423.186, respectively, and we have specified the measures used in setting Star Ratings through rulemaking. In addition, the cost plan regulation at § 417.472(k) requires cost contracts to be subject to the Parts 422 and 423 MA and Part D Prescription Drug Program Quality Rating System. As a result, the regulatory changes proposed here will apply to the quality ratings for MA plans and cost plans.
                    </P>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             We generally use “Part C” to refer to the quality measures and ratings system that apply to MA plans and cost plans.
                        </P>
                    </FTNT>
                    <P>
                        We have continued to identify enhancements to the Star Ratings program to ensure it is aligned with the CMS Quality Strategy as that Strategy 
                        <SU>84</SU>
                        <FTREF/>
                         evolves over time to increase the health and wellbeing of enrollees. In this final rule, we are finalizing most of the changes proposed to simplify and refocus the areas included in the Star Ratings, including changes to the measure set, with the exception of the proposal to remove the Diabetes Care—Eye Exam measure from the Star Ratings. We also are finalizing our proposal to not move forward with the implementation of the Health Equity Index reward and to continue to include the historical reward factor in the Star Ratings methodology. We are finalizing adding additional information about the data available to MA organizations and Part D sponsors during the plan preview periods before each Star Ratings release. We also solicited comments in the Contract Year 2027 proposed rule on ways to further simplify and modify the Star Ratings program to further drive improved quality of care, and whether there are ways to streamline the timeline from measure development to implementation. In this rule we are also finalizing a technical clarification proposed in the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on December 10, 2024, to provide details about how the enrollment-weighted measure score is calculated when a consumed or surviving contract is missing data for a measure. We also solicited additional feedback related to Star Ratings in the Request for Information on Future Directions in Medicare Advantage in section 6 of the Contract Year 2027 proposed rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             
                            <E T="03">https://www.cms.gov/medicare/quality/meaningful-measures-initiative/cms-quality-strategy.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Adding, Updating, and Removing Measures (§§ 422.164 and 423.184)</HD>
                    <P>
                        In the “Medicare Program; Contract Year 2019 Policy and Technical Changes to the Medicare Advantage, Medicare Cost Plan, Medicare Fee-for-Service, the Medicare Prescription Drug Benefit Programs, and the PACE Program” final rule which appeared in the 
                        <E T="04">Federal Register</E>
                         on April 16, 2018 (83 FR 16532) (“Contract Year 2019 final rule”), we stated we are committed to continuing to improve the Part C and D Star Ratings system and anticipated that over time measures would be added, updated, and removed. We also specified at §§ 422.164(d) and 423.184(d) rules for measure updates based on whether they are substantive or non-substantive. The regulations, at paragraph (d)(1), list examples of non-substantive updates. (See also 83 FR 16534 through 16537.) Due to the regular updates and revisions made to measures, CMS does not codify a list in regulation text of the measures (and their specifications) adopted for the Part C and D Star Ratings program. CMS lists the measures used for the Star Ratings each year in the Medicare Part C &amp; D Star Ratings Technical Notes or similar guidance issued with publication of the Star Ratings.
                    </P>
                    <P>The regulations at §§ 422.164 and 423.184 specify the criteria and procedures for adding, updating, and removing measures for the Part C and D Star Ratings program. As has been historically operationalized and as described at 83 FR 16533, measure removals are proposed and finalized through rulemaking unless they meet the requirements at §§ 422.164(e)(1) and 423.184(e)(1), which allow for measure removals through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act. This subregulatory process for measure removal was codified at §§ 422.164(e)(1) and 423.184(e)(1) to allow CMS to remove measures quickly, and without separate rulemaking, in certain circumstances where it is appropriate and necessary to do so. We proposed language at §§ 422.164(e)(3) and 423.184(e)(3) to clarify our existing policy that removal of measures for any other reasons not stated in paragraph (e)(1) will be proposed and finalized through rulemaking. We also proposed language at §§ 422.164(e)(2) and 423.184(e)(2) to clarify that removals for the reasons stated in paragraph (e)(1) will either be announced through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act or proposed and finalized through rulemaking. This language would reflect that where one of the bases for measure removal identified in paragraph (e)(1) applies, we would pursue removal using the process that allows for the most expedient notice to MA organizations and Part D sponsors at that time. For example, if a measure steward announces a measure retirement, we would use the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act or rulemaking depending on the timing of the announcement so that we can provide this information as quickly as possible to MA organizations and Part D sponsors.</P>
                    <P>We received several comments on our proposal to clarify existing policies and procedures on measure removal. A discussion of these comments follows, along with our responses and final decision.</P>
                    <P>
                        <E T="03">Comment:</E>
                         All commenters expressed support for the proposed language to clarify the process of measure removal.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the support received for the proposed clarification and thank the commenters for their feedback.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters emphasized the importance of transparency and the value of stakeholder engagement as part of the comment process for measure removal, particularly for high-impact clinical measures, including those affecting common chronic conditions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with these commenters and highlight here that removals for the reasons stated in §§ 422.164(e)(1) and 423.184(e)(1) will either be announced through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act (that is, the annual Advance Notice and Rate Announcement) or proposed and finalized through rulemaking. We intend to use whichever process allows for the most expedient notification to MA organizations and Part D sponsors. We appreciate the value of robust stakeholder engagement and note that stakeholders will continue to have an opportunity to provide input regarding measure removals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter urged CMS to ensure that MA enrollees are not harmed by any measure removal and that the needs of enrollees and their providers take priority in decision-making concerning MA and Part D.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS monitors the Part C and D Star Ratings and display page 
                        <PRTPAGE P="17497"/>
                        measures for quality improvement, relevance, and necessity. CMS publishes display measures on 
                        <E T="03">www.cms.gov</E>
                         each year, including measures that have been transitioned from the Star Ratings, new measures that are tested before inclusion in the Star Ratings, or measures displayed for informational purposes only. This listing of measures is separate and distinct from CMS's Part C and D Star Ratings. If CMS identifies the need to remove a measure from the Part C and D Star Ratings program for any of the reasons stated in §§ 422.164(e)(1) and 423.184(e)(1), measure removal will be announced in a timely manner either through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act or proposed and finalized through rulemaking. CMS will consider public input on measure removals, including any impact on enrollees and providers.
                    </P>
                    <P>After consideration of the comments received and for the reasons outlined in the Contract Year 2027 proposed rule and our response to comments, we are finalizing the proposal at §§ 422.164(e)(2), 422.164(e)(3), 423.184(e)(2), and 423.184(e)(3) without modification. Since this codification is consistent with current practice and policy, it will apply immediately on the effective date of the final rule and to the 2027 Star Ratings.</P>
                    <HD SOURCE="HD3">1. Removing Measures  </HD>
                    <P>
                        As the Part C and D Star Rating program continues to evolve and align with the measures included in the Universal Foundation,
                        <SU>85</SU>
                        <FTREF/>
                         a strategy to align measures across the agency's quality and value-based care goals, we proposed to simplify and refocus the measure set on clinical care, outcomes, and patient experience of care measures where performance is not topped out and where there is more variation in performance across contracts. Reducing the number of measures would increase the focus on the remaining measures, including those consistent with the Make America Healthy Again (MAHA) initiative, such as Reducing the Risk of Falling and Monitoring Physical Activity. Additionally, reducing the number of measures is consistent with recommendations from MedPAC 
                        <SU>86</SU>
                        <FTREF/>
                         and other interested parties that CMS consider having fewer measures in the Part C and D Star Ratings program. This is also consistent with the Universal Foundation which attempts, among other things, to focus attention on measures that are meaningful for the health of broad segments of the population and to reduce provider burden by streamlining and aligning measures—in other words, to focus the measure set on clinical care, outcomes, and patient experience of care measures. We initially solicited feedback on simplifying and refocusing the measure set in the Advance Notice of Methodological Changes for Calendar Year (CY) 2026 for Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies (“2026 Rate Announcement”),
                        <SU>87</SU>
                        <FTREF/>
                         as well as from the Star Ratings Technical Expert Panel (TEP) in October 2024.
                        <SU>88</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             
                            <E T="03">https://www.cms.gov/medicare/quality/cms-national-quality-strategy/aligning-quality-measures-across-cms-universal-foundation.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             Replacing the Medicare Advantage quality bonus program—MedPAC.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             
                            <E T="03">https://www.cms.gov/files/document/2026-advance-notice.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             
                            <E T="03">https://www.rand.org/pubs/conf_proceedings/CFA3973-1.html.</E>
                        </P>
                    </FTNT>
                    <P>Although the TEP recommended keeping the measure set as large as possible to avoid the ratings being influenced by a single measure, the TEP did support rethinking the measures included. Overall, the TEP supported measures from the current Healthcare Effectiveness Data and Information Set (HEDIS), Consumer Assessment of Healthcare Providers and Systems (CAHPS), Health Outcomes Survey (HOS), and some of the operational measures. Suggestions included the following: adding more evidence-based, clinical outcomes measures or redesigning current measures to assess patient outcomes (such as medication adherence); considering relevance, reliability, and the small denominator for some measures; considering “gameability,” attribution issues, provider burden, and the sensitivity of measures to small changes; and considering measures focused on trust enrollees have in the plan and network issues.</P>
                    <P>
                        After taking into consideration feedback from the TEP and from interested parties that commented on the Advance Notice of Methodological Changes for Calendar Year (CY) 2026 for Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies,
                        <SU>89</SU>
                        <FTREF/>
                         we proposed to remove seven Star Ratings measures focused on operational and administrative performance, three additional measures focused on process of care, and two additional measures focused on patient experience of care. There is a balance between streamlining the measure set and continuing to include enough measures to assess performance across the range of health care quality and to avoid contracts “teaching to the test” or focusing performance improvement efforts on a limited number of measured areas. We aim to achieve this balance by proposing initially to remove measures focused on operational and administrative performance, along with some additional process and patient experience of care measures with high performance and less variability across contracts, while retaining many measures focused on clinical care, outcomes, and patient experience and continuing to see where we can add additional outcomes measures in the future.
                    </P>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             See pages 107-110 at 
                            <E T="03">https://www.cms.gov/files/document/2026-announcement.pdf</E>
                             for a summary of comments.
                        </P>
                    </FTNT>
                    <P>There are various measures currently in the Part C and D Star Ratings measure set that focus on operational performance or on completion of required administrative processes. While these measures have been invaluable to CMS's efforts to monitor and improve plan performance and compliance in critical operational areas, many of these measures may be better suited as measures to monitor plan performance and compliance rather than as quality measures in the Part C and D Star Ratings program, especially since ratings for many of these measures are sensitive to small changes in performance because they have smaller denominators, such that small changes in the numerator can have a large impact on the measure Star Rating. Additionally, we have seen improvement on these measures since the inception of the Part C and D Star Ratings program, and MA organization and Part D sponsor performance rates are consistently fairly high.</P>
                    <P>
                        We also proposed to remove three additional process measures (Diabetes Care—Eye Exam, Statin Therapy for Patients with Cardiovascular Disease, and Members Choosing to Leave the Plan) and two patient experience of care measures (Customer Service and Rating of Health Care Quality) to further streamline the Star Ratings measure set. We want to focus more on clinical care, outcomes, and patient experience of care measures where performance is not topped out and where there is more variability in performance across contracts. This is where there is more room for improvement and measures where we see MA organization and Part D sponsors need more incentives to perform well. Additionally, when there is little variation in performance across contracts for a measure, this does not provide meaningful information to beneficiaries or their caregivers when choosing a plan. One purpose of providing quality and performance information is to highlight differences in 
                        <PRTPAGE P="17498"/>
                        performance across contracts that can impact the care and services provided by the plan. Reducing the number of operational and administrative measures and removing some additional process and patient experience of care measures would also increase the relative weight of the outcome measures in the summary and overall ratings.
                    </P>
                    <P>We proposed to remove the 12 measures in Table 3 beginning with the Star Ratings year shown in the table for each measure. As stated in the Contract Year 2027 proposed rule, we expect that removing these measures would result in an overall decrease in ratings since performance on many of these measures is very high; however, we also expect that the proposed removal of the Health Equity Index (HEI; also called Excellent Health Outcomes for All) reward along with keeping the historical reward factor, discussed in more detail in section V.D. of this final rule, would generally increase ratings. We provide the estimated combined impact of the final Star Ratings policies in section XI.C.6. of this final rule.</P>
                    <P>CMS is also considering removing additional measures in the future as we continue to simplify and refocus the program. Removal of any additional measures would need to be proposed and finalized through rulemaking.</P>
                    <GPH SPAN="3" DEEP="160">
                        <GID>ER06AP26.032</GID>
                    </GPH>
                    <P>We solicited feedback on all of the potential measure removals discussed in the Contract Year 2027 proposed rule, including feedback on the timing of measure removals and received many comments. A discussion of general measure removal comments, along with our responses follows. Comments about specific measures and our responses are summarized below each specific measure discussion.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported streamlining and refocusing the Star Ratings measure set. These commenters supported a focus on clinical care, outcomes, and patient experience.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank these commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters were concerned that removing measures will reduce oversight and transparency of plan performance. Several commenters recommended that the measures continue to be reported on the display page. Some commenters were also concerned about the potential loss of quality gains if the measures are removed.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that continued transparency and oversight are important when measures are removed from Star Ratings. Thus, CMS will continue to publicly report removed measures on the display page, which are displayed separately on cms.gov and not on Medicare Plan Finder, and will continue to monitor plan performance through its existing oversight and compliance activities. Where CMS identifies that an MA organization has failed to comply with the terms of its contract, we will continue to take appropriate compliance actions per 42 CFR 422.504(m)(3) and publicly post warning letters and corrective action plan requests (CAPs). If an organization receives too many compliance actions, CMS may deny applications for new contracts or service area expansions under 42 CFR 422.502(b)(1) for failure to perform in accordance with CMS contractual requirements. This approach preserves oversight of plans and transparency for beneficiaries and other interested parties while allowing the Star Ratings program to focus on measures that more meaningfully differentiate performance across contracts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern about removing administrative measures and noted that it may distort competition in MA by disproportionately harming smaller or regional plans and SNPs, and increase revenue volatility. They cautioned that outcomes-based measures alone are often harder for plans to control, and that administrative measures provide a stabilizing counterbalance within the Star Ratings system.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' perspectives regarding the potential programmatic impacts of removing administrative measures from the Star Ratings program. CMS recognizes that outcomes-based measures can be more challenging for plans and that administrative measure scores have historically remained stable within the Star Ratings system given the high performance across all contracts. However, measures included in Star Ratings should meaningfully differentiate performance across contracts. Measures with little variation across contracts do not provide meaningful comparative information for potential enrollees when choosing a plan. CMS will continue to evaluate the mix of measures included in the Star Ratings program and its impact on plans of varying sizes. With regard to smaller plans or SNPs, in simulations of the impact of the proposed changes, we did not find that there were disproportionate impacts to these types of plans (see the Impact of Proposed and Finalized Changes section for more details).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported simplification of the Star Ratings, but cautioned against wholesale removal of measures without replacement. They recommended that if measures are removed from Star Ratings, CMS should consider beneficiary impacts and maintain robust, transparent compliance monitoring, enhanced CAHPS 
                        <PRTPAGE P="17499"/>
                        questions, or public reporting to preserve accountability. Many of these commenters emphasized that the removed measures should still be publicly reported, even if CMS restructures how they are measured or incentivized.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' support for simplifying the Star Ratings program while maintaining accountability. CMS agrees that continued transparency and oversight are important when measures are removed from Star Ratings. Thus, CMS will publicly report removed measures on the display page and will continue to monitor plan performance through its existing oversight and compliance activities. This approach preserves transparency for beneficiaries and other interested parties while allowing the Star Ratings program to focus on measures that more meaningfully differentiate performance across contracts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that as CMS makes changes to the Star Ratings including proposing to eliminate the HEI reward, and adding and removing measures, CMS should ensure that changes are communicated to beneficiaries in an accessible way, including with State Health Insurance Assistance Programs (SHIPs) assistance. The commenter also stated that educational and training materials should be provided to SHIP counselors to help them understand and interpret the changes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree it is important for beneficiaries to understand the Star Ratings and we are considering how to best present the Star Ratings to make it easier for beneficiaries to understand. For example, we are reviewing how the ratings are presented on the Medicare Plan Finder website.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters raised concerns about Star Ratings volatility, destabilizing the Star Ratings system, and downstream impacts to QBPs if CMS removes multiple administrative measures at the same time. These commenters also raised concerns about making the remaining measure set smaller and more sensitive to single-measure changes. Some commenters were concerned about removing too many measures too fast and recommended a phased approach for removal of measures. Commenters also raised concerns about program disruption, which they believe will undermine the predictability and stability of the program and impact beneficiary experience.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS does not agree that removal of measures destabilizes the Star Ratings program. The measures we proposed for removal have topped out (
                        <E T="03">i.e.,</E>
                         have very high performance across all contracts such that cut points for the measure are very close together and do not reflect meaningful differences in performance), are duplicative, or no longer provide meaningful differentiation across plans. Retaining such measures reduces the impact of measures that better distinguish differences in plan quality and performance. Removing these measures in a timely manner strengthens the Star Ratings program and supports informed beneficiary choice.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters recommended changing measure specifications or redesigning measures rather than removing measures. Other commenters proposed alternative approaches to deal with a “topped-out” measure apart from removing it from Star Ratings, including increasing the cut points, penalizing contracts if performance is not maintained, creating a composite measure of operational performance, and reassessing whether or how high-scoring measures should impact payment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed in the Contract Year 2027 proposed rule, the Part C and D Star Ratings program continues to evolve and align with the measures included in the Universal Foundation. As such, we proposed simplifying and refocusing the measure set to focus on measures of clinical care, outcomes, and patient experience where performance is not topped out and where there is more variation in performance across contracts. Reducing the number of measures would increase the focus on the remaining measures, including those consistent with the MAHA initiative. Our proposal aimed to strike a balance between streamlining the measure set and maintaining enough measures to assess performance across the range of health care quality.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that the removal of measures will create a substantial shift in how the measures are weighted, stating that 44 percent of the weighting would shift to member survey results for CAHPS and HOS. The commenter stated that these surveys are often unduly influenced by factors such as timing of the survey, memory recall bias, and survey fatigue. The commenter also stated that there is randomness, unpredictability, and volatility inherent in survey measures and how they are scored does not correlate to actual plan performance.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's concern regarding the potential impact of removing certain measures on the weighting of remaining measures, including the increased contribution of CAHPS and HOS survey measures. We disagree that these survey measures are unduly volatile or fail to reflect actual plan performance.
                    </P>
                    <P>CAHPS and HOS are standardized, validated instruments designed to capture beneficiary experience and health outcomes. CMS employs multiple methodological safeguards, including standardized survey administration, large sample sizes, and case-mix adjustment to ensure reliable information that is comparable across contracts.</P>
                    <P>CAHPS and HOS measures provide information that complements clinical and administrative measures. Incorporating beneficiary-reported measures also aligns with CMS's commitment to evaluating beneficiaries' experiences of care and ensures that quality measurement reflects aspects of care that are best assessed by beneficiaries themselves. Accordingly, we find that the weighting of CAHPS and HOS measures remains appropriate.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that administrative measures were within plan control rather than health care provider control and should be retained. Another commenter recommended that CMS evaluate measures based on the degree of plan-level control and overlap with existing incentives in order to help prioritize measures where Star Ratings are most likely to produce improvements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS does not agree that non-administrative measures are not within plan control. The measures included in the Star Ratings are evaluated at the contract level and reflect the collective performance of the organization, including the organization's provider network. For each of its contracts, MA organizations are responsible for establishing provider networks, designing benefits, furnishing care management and care coordination services, and implementing quality improvement strategies to support measure performance.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported the idea of simplifying the measure set in concept but did not support the proposal because of the associated increase in Medicare spending. The commenter stated that if CMS streamlines the measure set in future rulemaking, it should do so in a way that does not add cost.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we stated in the Contract Year 2027 proposed rule, we expect that removing these measures would result in an overall decrease in ratings since performance on many of these measures is very high; however, we also expect that not implementing the HEI reward, along with keeping the 
                        <PRTPAGE P="17500"/>
                        historical reward factor, would generally increase ratings. While the combination of these two proposals results in net costs, the measure removal proposal on its own would result in savings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters raised concerns about the ability of I-SNPs to have data for enough measures to receive an overall Star Rating. A commenter also stated that the measures proposed for removal are in areas where these plans typically perform well, noting that their removal would magnify the impact of the remaining measures which the commenter believes are not well-suited for long-term care populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate this commenter's concerns about I-SNPs having data for enough measures to qualify for an overall rating. We will continue to monitor this and will consider what additional measures may be available for I-SNP only contracts. With regard to I-SNPs performing well on the measures proposed for removal, we note that this is also true of plans more broadly because performance on many of the measures is very high.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter raised concerns that removing too many operational and administrative measures may weaken the program's ability to capture aspects of performance that are most relevant to beneficiaries, and that removing the measures may shift focus away from day-to-day experiences that shape beneficiary satisfaction and trust. Another commenter disagreed that the measures proposed for removal are not meaningful to beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS will continue to closely monitor any measure removed from Star Ratings through existing oversight and compliance activities and will publicly report these measures on the display page. This approach preserves transparency for beneficiaries and other interested parties while allowing the Star Ratings program to focus on measures that more meaningfully differentiate performance across contracts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that some measures that appear topped out are actually influenced by gaming among plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's concern. CMS is not aware of evidence of widespread gaming across Star Ratings measures. However, CMS agrees that measures that are vulnerable to manipulation or no longer meaningfully differentiate plan performance are not appropriate for continued inclusion in the Star Ratings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended using statistical tests of variation over time to determine whether a measure should be removed and implementing a cap in the number of measures removed in a year.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates this comment; however, we have evaluated performance on the measures proposed for removal and find that it is appropriate to remove them now in line with our goal of streamlining and refocusing the measure set.
                    </P>
                    <HD SOURCE="HD3">a. Plan Makes Timely Decisions about Appeals (Part C) and Reviewing Appeals Decisions (Part C)</HD>
                    <P>We proposed removing the Plan Makes Timely Decisions about Appeals (Part C) and Reviewing Appeals Decisions (Part C) measures because average performance on these measures has increased from 90 to 96 percent and 88 to 95 percent from the 2015 to 2025 Star Ratings, respectively. There is also not a lot of variation across the vast majority of contracts on these measures and the measures can have small denominators for some contracts, both of which can lead to shifts in ratings as a result of small changes in the numerator. Since the appeals process is critical to monitor as it impacts access to care, CMS would continue to monitor plan performance and issue compliance actions based on appeals data as needed and would continue to monitor access issues through the CAHPS survey measures.</P>
                    <P>We solicited comment on removing the appeals measures from the 2029 Star Ratings. A discussion of Part C appeals measure removal comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters opposed removing appeals-related measures from the Star Ratings, emphasizing that these measures are essential indicators of access to care. They argued that appeals measures capture utilization management problems, including inappropriate denials, delays in post-acute care, and failure to process or forward appeals appropriately. Other commenters stressed that these measures are not merely administrative but directly tied to care continuity, discharge planning, transitions of care, and prevention of avoidable complications, hospitalizations, or functional decline. Several commenters emphasized that Star Ratings are the primary enforcement and accountability mechanism for the appeals measures within MA. They stated that because Star Ratings drive financial bonuses, enrollment growth, and marketing advantages, they significantly influence plan behavior. Some commenters also noted that appeals measures included in Star Ratings create tangible incentives for plans to reduce inappropriate denials, process appeals correctly, and comply with beneficiary protection requirements. Removing these measures would, in their view, erode accountability and shift reliance to oversight mechanisms that may lack sufficient resources or enforcement power.
                    </P>
                    <P>Some commenters raised concerns about vulnerable populations, including individuals with complex medical needs, dually eligible individuals, and patients requiring specialized or time-sensitive care such as cancer treatment, post-acute services, or chronic disease management. For these populations, delays in appeals decisions can lead to irreversible harm. These commenters argued that maintaining appeals measures is especially important to ensure these groups are not disproportionately disadvantaged.  </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the thoughtful comments regarding the removal of appeals-related measures from the Star Ratings. We agree that the appeals process is a critical beneficiary protection and plays an important role in ensuring access to medically necessary care for all enrollees. Appeal rights are a core component of MA requirements, and plans remain fully accountable for appropriately administering the appeals process for all enrollees, regardless of whether specific appeals measures are included in the Star Ratings.
                    </P>
                    <P>While CMS is removing the appeals-related measures from the Star Ratings, this action does not diminish plans' obligations under existing regulations at 42 CFR part 422, subpart M to comply with appeals requirements, including timely, accurate, and complete processing of appeals. CMS will continue to actively monitor plans' appeals adjudication through multiple oversight mechanisms, including audits, monitoring activities, and compliance actions. Where CMS identifies noncompliance, we will take appropriate compliance actions per 42 CFR 422.504(m)(3), publicly post warning letters and corrective action plan requests (CAPs), and if an organization receives too many compliance actions may deny applications for new contracts or service area expansions under 42 CFR 422.502(b)(1) for failure to perform in accordance with CMS contractual requirements.</P>
                    <P>
                        CMS recognizes commenters' concerns that appeals measures reflect issues related to utilization management, inappropriate denials, and 
                        <PRTPAGE P="17501"/>
                        care delays, and that failures in appeals processing can affect care continuity, discharge planning, and transitions of care. CMS also acknowledges the particular importance of an effective appeals process for vulnerable populations, including individuals with complex medical needs, dually eligible individuals, and those requiring specialized or time-sensitive care. Plans are expected to appropriately administer the appeals process for all enrollees, including these populations, as part of their fundamental responsibility to provide access to covered benefits.
                    </P>
                    <P>Although Star Ratings serve as one mechanism to promote accountability, they are not the sole means by which CMS ensures compliance with MA requirements. CMS will continue to use its full range of oversight and compliance authorities to hold plans accountable for appeals-related failures and to protect beneficiaries' access to care. Appeals are not optional administrative functions; they are a core responsibility of MA plans, and CMS expects plans to administer appeals processes appropriately, consistently, and in compliance with all applicable requirements.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported removal of the appeals measures, citing methodological concerns such as disproportionate impact on smaller plans due to a smaller number of appeals and the lack of a volume adjustment. Other commenters supported removing the measures because they are operational, topped out, or poorly differentiated across contracts. These commenters argued the measures no longer meaningfully reflect quality, can be excessively burdensome, and are better suited for compliance monitoring than Star Ratings. These commenters supported shifting the Star Ratings program's focus toward clinical outcomes and value-based measures, with appeals oversight handled through audits, CAHPS surveys, or internal CMS monitoring instead of financial incentives.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' support for the removal of the appeals-related measures from the Star Ratings program. CMS agrees that these measures no longer meaningfully differentiate performance across contracts due to consistently high performance levels and limited variation, and can be burdensome in that small changes in performance can have an impact on ratings given the measures are topped out. Consistent with commenters' feedback, CMS agrees that these appeals measures are better suited for compliance and program oversight rather than inclusion in Star Ratings as quality measures tied to financial incentives. Appeals processes remain an important safeguard for beneficiaries; however, CMS will conduct oversight of these activities through other monitoring efforts. By removing these measures from Star Ratings, CMS intends to refocus the program on measures that more effectively assess clinical care and beneficiary experience, while continuing to ensure robust oversight of appeals processes through other established channels.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that removing appeals measures from Star Ratings could disadvantage smaller, regional, or single-state plans that often excel in member experience, while benefiting large national plans. Other commenters argued that the appeals measures create uneven operational burden and do not reliably differentiate plan performance, particularly for plans near minimum thresholds.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS has found that the appeals measures generally have high performance across all types of contracts which limits their ability to meaningfully distinguish differences in plan performance across contracts, regardless of plan size. For a measure to be useful for a beneficiary choosing a contract, it needs to have variation across contracts to be able to highlight differences in performance. Nevertheless, it will be critical to still calculate, monitor, and publicly report these measures since appeals processing is critical for the success of the MA program. As a reminder, CMS calculates the scores for the appeals measures from data contained in the Independent Review Entity (IRE) data system; thus, there is no burden to plans in these calculations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters stated that high performance on appeals measures may be misleading rather than proof that the measures are no longer needed. Commenters described plan practices that artificially inflate performance, such as overturning denials early to avoid independent review, mislabeling valid beneficiary appeals as provider disputes, or improperly asserting that certain denials are not appealable. These tactics can block access to the IRE and obscure inappropriate denials from CMS oversight.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters'concerns that high performance on the appeals measures may not accurately reflect beneficiary protections and that tying these measures to Star Ratings may create incentives for plans to focus on appeals measure performance rather than meaningful access to the appeals process. CMS strongly objects to inappropriate practices by plans, such as overturning denials to avoid independent review or misclassifying appeals that can obscure access issues and limit visibility into inappropriate denials. Due to concerns regarding gaming, CMS implemented scaled reductions for the appeals measures to try to ensure all requisite appeals are sent to the IRE. By moving the appeals measures to the display page, CMS intends to reduce incentives to game measure performance while maintaining transparency into plans' appeals performance for beneficiaries and other interested parties. CMS will continue to monitor appeals and address inappropriate denials outside of the Star Ratings and QBP programs and hold plans accountable through compliance strategies as described in the section about general comments regarding measure removals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern that plans may deny more services, knowing fewer denials will be challenged or scrutinized. This would increase administrative costs for providers, delay care, and undermine CMS's goals of value-based care and program integrity. A few commenters emphasized that the “Reviewing Appeals Decisions” measure is particularly important for ensuring that plans do not shield indefensible denials from independent oversight.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS shares commenters' concerns about inappropriate service denials and agrees that it is important to continue close oversight of plan appeals processing. While CMS is removing the appeals measures from the Star Ratings program, CMS will continue to monitor appeals through program audits and other oversight and compliance activities and will publicly report these measures on the display page. Removing these operational measures from the Star Ratings reduces administrative burden for CMS in the calculation of the ratings and allows the Star Ratings program to focus on measures with greater variation across contracts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters argued that improved performance over time should be viewed as evidence that these measures are working, not as justification for elimination. These commenters suggested that sustained increases in appeals timeliness and review scores are attributed to the incentives created by Star Ratings. These commenters suggested that removing the appeals measures risks reversing years of progress and sending a signal that timely, fair appeals are no 
                        <PRTPAGE P="17502"/>
                        longer a priority, even as utilization management and prior authorization remain major sources of access barriers. These commenters emphasized that removing the appeals measures would reduce plans' focus on appeals timeliness and accuracy, likely leading to backsliding, longer delays, and increased inappropriate denials. Several commenters emphasized that when financial and reputational incentives are removed, plans tend to redirect resources away from appeals processing.
                    </P>
                    <P>Other commenters stressed that the high or “topped-out” performance on these measures reflects the success of the Star Ratings program rather than evidence that oversight is no longer needed. Commenters also noted recent declines in performance and persistent outliers at the contract level, arguing these trends show it is premature to remove the measures.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' views that improved and sustained performance on the appeals measures reflects the effectiveness of the Star Ratings program and the incentives it creates. CMS agrees that timely and accurate appeals processing remains an important beneficiary protection and that continued oversight is necessary. However, the consistently high performance and limited differentiation across contracts indicate that these measures no longer function effectively as Star Ratings quality measures. We have not seen a decline in measure scores over the past year. For the 2026 Star Ratings, Plan Makes Timely Decisions about Appeals had an average score of 98%, and Reviewing Appeals Decisions had an average score of 97%, up from 96% and 95%, respectively, from the prior year.
                    </P>
                    <P>While CMS is removing the appeals measures from Star Ratings, this does not diminish the importance of appeals timeliness or accuracy nor does it mean that CMS will stop calculating these measures. CMS will continue to closely monitor appeals processing and will publicly report these measures on the display page. Existing MA oversight processes such as program audits and contract monitoring will also continue to apply to the appeals processing measures. This approach maintains accountability and transparency while allowing the Star Ratings program to focus on measures that better differentiate performance.  </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters urged refinement rather than removal of these measures from Star Ratings to help improve differentiation across contracts. Some commenters focused on methodological and data issues, acknowledging CMS's concerns about small denominators and limited variation. Other commenters recommended standardizing IRE determinations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' thoughtful suggestions to refine the appeals measures to improve differentiation across contracts. We will take these comments into consideration if we make future changes to these measures after moving them to the display page. The process of standardizing how the IRE makes decisions is outside the scope of the Star Ratings program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters advocated for expanded public reporting and transparency if CMS proceeds with removal of the appeals measures, including requiring plans to publish annual reports on appeals timeliness, independent review outcomes, and overturned denial rates with stratification by service type. Other commenters suggested that CAHPS surveys and compliance monitoring cannot replace appeals measures in Star Ratings. While CAHPS provides valuable high-level patient experience data, commenters expressed it is lagged and lacks the operational specificity needed to detect real-time access barriers or improper plan practices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' recommendations regarding expanded transparency and public reporting following removal of the appeals measures from Star Ratings. CMS agrees that transparency remains important and will continue to publicly report appeals-related measures on the display page, while maintaining oversight and compliance through various monitoring activities. While CMS acknowledges commenters' views regarding limitations of CAHPS surveys for identifying real-time operational issues, CMS will use a combination of public reporting and existing oversight mechanisms to provide appropriate visibility into appeals processing.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the Plan Makes Timely Decisions about Appeals (Part C) and Reviewing Appeals Decisions (Part C) measures beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">b. Special Needs Plan (SNP) Care Management (Part C)</HD>
                    <P>We proposed removing the SNP Care Management (Part C) measure as part of our effort to increase the focus on patient experience and outcome measures. This administrative-focused process measure indicates how often a contract completed the required health risk assessment. The goal of this assessment is to then use the results to help enrollees get the care they need. CMS is ultimately interested in whether enrollees receive needed care as indicated by this assessment and not only whether the assessment is completed. We proposed removing this measure since the current measure does not provide any information about whether enrollees received care as indicated by their assessments. We would move this measure to the display page.</P>
                    <P>We solicited comment on removing the SNP Care Management measure from the 2029 Star Ratings. A discussion of SNP Care Management measure removal comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported the removal of the SNP Care Management measure, primarily because it is an administrative measure that tracks the percentage of members with a completed a Health Risk Assessment (HRA), as opposed to a more meaningful clinical outcome measure. Several other commenters simply appreciated the simplification of the Star Ratings measures, or recommended monitoring care management through other mechanisms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the support for removing the SNP Care Management measure.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters opposed removal of this measure since they were concerned that removal would reduce plan oversight and they claimed there is already underutilization of HRAs. Several commenters were specifically concerned about how proposed Star Ratings changes would impact SNP contracts, concerned that the removal would have a negative impact on dually eligible individuals as well as I-SNP enrollees, who are typically sicker and have more complex care needs. There were also concerns expressed about specific groups, such as those with kidney disease; commenters emphasized the importance of ensuring access to services for all vulnerable populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS recognizes that HRAs are an important tool for providers and care teams in determining enrollee needs and ensuring access to appropriate services, particularly for vulnerable populations, including individuals with chronic or complex conditions such as kidney disease. The removal of the SNP Care Management measure from Star Ratings is not intended to reduce the use or importance of HRAs, nor to diminish 
                        <PRTPAGE P="17503"/>
                        the quality of care delivered to SNP enrollees.
                    </P>
                    <P>The removal of this measure from Star Ratings does not eliminate the requirement for SNPs to conduct HRAs at 42 CFR 422.101(f)(1)(i) and (ii). HRAs remain a required component of SNP model of care requirements and are critical for identifying enrollees' clinical, functional, and cognitive needs, as well as for informing individualized care planning and ongoing care management. Additionally, the SNP Care Management measure will remain available on the display page so performance information will continue to be publicly reported.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested ways to modify the current measure. For example, CMS could work with SNPs and other stakeholders to develop a more meaningful measure, including a measure about whether the care identified in the HRA was provided. Other suggestions included expanding the SNP Care Management measure to all MA members and reporting at the geographic level. Another commenter expressed the need for clearer alignment between the NCQA Model of Care accreditation process and any future measures in this area.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the suggestions regarding changes to the SNP Care Management measure. We will take these suggestions into consideration for any future updates to this measure after moving it to the display page. We agree that it would be useful to measure whether care was provided since currently the measure just notes whether an HRA was completed and not if the information collected was used to develop and deliver a care plan.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the SNP Care Management measure beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">c. Call Center—Foreign Language Interpreter and TTY Availability (Part C and D)</HD>
                    <P>We proposed removing the Call Center—Foreign Language Interpreter and TTY Availability (Part C and D) measures. Average performance on these measures in the 2025 Star Ratings was very high at 94 percent on the Part C measure, and 94 percent for MA-PD contracts and 97 percent for PDP contracts on the Part D measure. Additionally, there is not a lot of variation across the vast majority of contracts on these measures, and the measures have relatively small denominators, both of which can lead to shifts in ratings as a result of small changes in the numerator. If these measures were removed, CMS would continue to monitor plan performance and issue compliance actions, and the Star Ratings would continue to capture similar issues related to customer service through the CAHPS survey measures.</P>
                    <P>We solicited comment on removing the Call Center measures from the 2028 Star Ratings. A discussion of Call Center measure removal comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported the removal of the call center measures, noting that their continued inclusion in the Star Ratings system does not meaningfully distinguish plan quality or drive further improvement. Other commenters supported removal since performance is topped out. Some commenters noted the reduction in administrative burden with the removal of these measures and that the current high-performance rates indicate that these measures may no longer be necessary. A few commenters agreed that the focus of Star Ratings should shift to measures that more directly impact clinical outcomes and patient experience. A commenter mentioned that these measures should be removed due to litigation around these measures and volatility in scores due to small denominators.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the support for removing the Part C and D Call Center—Foreign Language Interpreter and TTY Availability measures.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters opposed the removal of these measures, stating that they are essential for ensuring meaningful language access and communication for non-native English speakers and those with disabilities. Some of these commenters emphasized the importance of maintaining measures that assess beneficiary experience with plan operations and policy. They stated that removing these measures could reduce oversight and accountability, ultimately harming beneficiary outcomes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that it is critical to continue to monitor performance on these measures to ensure that enrollees who speak languages other than English and those that are hearing impaired have access to plan call centers. CMS plans to move these measures to the display page so information on performance will still be publicly available. We will also closely monitor performance, issue compliance actions per 42 CFR 422.504(m)(3) and 423.505(n)(3), publicly post warning letters and corrective action plan requests (CAPs), and if an organization receives too many compliance actions may deny applications for new contracts or service area expansions under 42 CFR 422.502(b)(1) and 423.503(b)(1) for failure to perform in accordance with CMS contractual requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A handful of commenters highlighted the potential negative impact on dually eligible individuals and I-SNP enrollees, who are often sicker and have more complex care needs. They emphasized the importance of maintaining transparency and accountability for measures that ensure access to services for these vulnerable populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that it is important to continue to monitor performance on these measures for all contracts, including those that serve vulnerable populations. We will be adding these measures to the display page so we can continue to monitor and make publicly available information about how contracts perform.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that CMS provide information on how it will continue to monitor and ensure compliance with language access and TTY requirements if the measures are removed. They urged CMS to maintain robust monitoring and transparency to safeguard beneficiaries' access to these critical services. Some commenters suggested moving these measures to the display page. Some commenters stressed the importance of ensuring equitable access to healthcare services for non-native English speakers and individuals with disabilities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that monitoring compliance with language access and TTY requirements is critical and is committed to continuing to monitor performance and utilize compliance processes per 42 CFR 422.504(m)(3) and 423.505(n)(3) in this area. We are planning to move these measures to the display page and will continue to carefully review performance and issue compliance actions as needed if we do see poor performance on these measures.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters urged CMS to consider alternative approaches to measuring performance that preserve accountability and support meaningful access to language and communication services. A few commenters suggested modifying the call center measures to address concerns about small sample sizes rather than removing them entirely. Other commenters offered specific recommendations for making changes to the call center measures, such as using a multi-year approach for scoring, setting revised minimum denominator rules, or combining Part C 
                        <PRTPAGE P="17504"/>
                        and D measures into a single measure to improve stability and consistency. Other commenters suggested that CMS consider regional language prevalence and contract-level demographic composition when assessing language access. A commenter suggested breaking contracts into groups based on size and demographics to provide a more accurate assessment of a plan's ability to support all of its members. Other commenters suggested calling the current member line versus the prospective member line or calling outside of the annual and open enrollment periods.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the suggestions for potential future changes to the Part C and D Call Center—Foreign Language Interpreter and TTY Availability measures, but making changes to measure specifications is out of scope for this final rule. We will take these suggestions into consideration for any future updates to these measures following moving them to the display page.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the call center measures beginning with the 2028 Star Ratings.</P>
                    <HD SOURCE="HD3">d. Complaints About the Health/Drug Plan (Part C and D)</HD>
                    <P>We proposed removing the Complaints about the Health/Drug Plan (Part C and D) measure. We stated that this measure demonstrated exceptionally high performance with limited variation across contracts. Average performance on this measure was high at 0.23 percent for MA-PD contracts and 0.04 percent for PDP contracts in the 2025 Star Ratings (lower scores are better). The volume of complaints has significantly decreased since this measure was first introduced, and there is also minimal variation in performance across contracts. CMS would continue to monitor plan performance and issue compliance actions as needed, and the Star Ratings would continue to capture similar issues related to access to care and patient experience through the CAHPS survey measures.</P>
                    <P>We solicited comment on removing the complaints measure from the 2029 Star Ratings. A discussion of the complaints measure removal comments, along with our responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         The majority of commenters opposed the removal of the Complaints about the Health/Drug Plan (“complaints measure”) from the Star Ratings. Many commenters expressed concern that removal would weaken a key accountability mechanism and incentive for plan sponsors to address issues impacting beneficiaries and providers, and stated the measure is a transparent indicator of plan performance and insight into beneficiary experience and access to care. Several commenters believed that the complaints measure was not just an administrative process measure but a beneficiary protection measure, and the complaints process reflects the final recourse for beneficiaries when the plan does not meet their needs.
                    </P>
                    <P>A couple of commenters stated that oversight and quality incentives are not mutually exclusive, but complement each other, as a reason to retain the measure in the Star Ratings. Some cited CMS's changes to ensure uniform entry of provider complaints into the Complaints Tracking Module (CTM), and marketing and oversight reforms, as more reasons to keep the measure. Some commenters defended the complaints data as important information regarding providers' experience with plans' utilization management tools. Some commenters stated the complaints process fosters cooperation between plans and providers to resolve beneficiary issues or emphasized the complaints measure included direct feedback from beneficiaries and providers.</P>
                    <P>Other commenters said that uniformly high performance is evidence of success and the measure's effectiveness in incentivizing plans to improve their processes, rather than a justification for elimination. Commenters expressed concern that CMS was removing a measure they do well in, is within the plans' control, or that acted as a deterrent to non-compliant behavior by plans.</P>
                    <P>A few commenters believed that removing the complaints measure would weaken a key incentive for plans to maintain adequate staffing, systems, and operational capacity to resolve complaints effectively. One commenter stated that plans may be less likely to take proactive actions to address beneficiary and provider issues if the complaints measure is removed from the Star Ratings, which could unintentionally increase burdens on beneficiaries, providers, and CMS.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the thoughtful comments regarding the importance of the complaints measure for plan accountability and beneficiary protection. We acknowledge that it has historically served as an important tool for monitoring plan performance and promoting member-centered customer service. However, the high performance across contracts and minimal variation indicate that this measure no longer effectively differentiates plan quality in the Star Ratings system. The Star Ratings program is most effective when it focuses on measures where meaningful performance differences exist that can inform beneficiary choice and drive continued improvement.
                    </P>
                    <P>Removal of this measure from Star Ratings does not eliminate CMS's oversight of complaints or our commitment to beneficiary protections. It also does not diminish plans' accountability for researching and resolving complaints, which may include coordination with beneficiaries, providers, or others.</P>
                    <P>
                        CMS developed the CTM in the Health Plan Management System (HPMS) to track complaints received by CMS from beneficiaries, providers, and their representatives regarding specific MA organizations, Cost Plans, and Part D sponsors. Complaints are recorded in the CTM and assigned to the appropriate plan. Data may be populated into the CTM from various sources, such as 1-800-MEDICARE, CMS staff or contractors, Medicare Ombudsman, SHIPs, the Medicare.gov online complaint form for beneficiaries at 
                        <E T="03">https://www.medicare.gov/my/medicare-complaint,</E>
                         or the provider complaint form (regarding MA organizations) at 
                        <E T="03">https://www.cms.gov/medicare/health-drug-plans/provider-complaints-form.</E>
                    </P>
                    <P>As required under the contract provisions established at 42 CFR 422.504(a)(15) and 423.505(b)(22), plans are required to address and resolve the complaints received by CMS against them in the CTM. Plans must adhere to the timelines to resolve complaints in compliance with 42 CFR 422.125 and 423.129. The January 6, 2025 HPMS memorandum, Updated Complaints Tracking Module Standard Operating Procedures, provides information to sponsors on handling, resolving, and documenting complaints. Given the time-sensitive nature of many of the complaints, plans should continuously access, view, respond, and resolve the complaint(s) assigned to their organization in the CTM. CMS expects plans to enter periodic casework notes, including initial and subsequent contacts, developments, or research.  </P>
                    <P>
                        Furthermore, requirements for resolution of complaints received in the CTM do not override requirements related to the handling of appeals and grievances set forth in 42 CFR part 422 subpart M (which apply to cost plans as well as MA organizations per § 417.600) and Part 423 subpart M, for Part D sponsors. Rather, CTM requirements 
                        <PRTPAGE P="17505"/>
                        supplement the appeals and grievance requirements by specifying how organizations must handle complaints received by CMS in the CTM and passed along to the plan. In accordance with the regulations at 42 CFR 422.564 and 423.564, plans must provide meaningful procedures for the timely hearing and resolving of enrollee grievances. As such, beneficiaries are encouraged first to contact their plan directly to file a complaint (
                        <E T="03">i.e.,</E>
                         grievance). See the Parts C &amp; D Enrollee Grievances, Organization/Coverage Determinations, and Appeal Guidance 
                        <SU>90</SU>
                        <FTREF/>
                         for information about grievance procedures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             Available at: 
                            <E T="03">https://www.cms.gov/medicare/appeals-grievances/managed-care.</E>
                        </P>
                    </FTNT>
                    <P>CMS will continue to closely monitor complaint trends, and how complaints were resolved in CTM casework notes, to ensure that plans maintain appropriate grievance and complaint processes regardless of whether this measure is included in Star Ratings, and CMS will continue to review plan practices for compliance. The complaints provide early warning signs of problems through feedback from beneficiaries and providers, and CMS will continue to calculate complaint rates and resolution timeliness to identify plan outliers for corrective action as necessary.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the removal of the complaints measure, agreeing that performance has reached high levels with minimal variation among plans and that complaints are better suited for compliance oversight. A commenter stated that the measure is heavily influenced by factors outside of the plan control, and another pointed out that the measure is prone to manipulation. A couple of commenters agreed that the complaints measure is duplicative of CAHPS measurement. A commenter felt that the measure has systemic biases, and that biases due to plan design or geography could inflate performance.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the support for removal of the complaints measure from the Star Ratings to focus on measures with meaningful variation, which is consistent with recommendations from the Medicare Payment Advisory Commission (MedPAC) 
                        <SU>91</SU>
                        <FTREF/>
                         and our broader goals of reducing administrative burden while maintaining focus on outcome-oriented quality measures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             Replacing the Medicare Advantage quality bonus program—MedPAC available at: 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/import_data/scrape_files/docs/default-source/reports/jun20_ch3_reporttocongress_sec.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters asserted that CAHPS survey measures capture general satisfaction but not specific or real-time feedback about operational issues like the complaints measure. Commenters stated CAHPS and complaints data are complementary rather than duplicative. A few commenters noted that the CAHPS survey-based measures rely on sampling and member recall, but the complaints measures capture direct beneficiary feedback from all beneficiaries. A commenter pointed out that the breadth and specificity of the CTM complaint categories highlights that the CTM captures issues are not reflected in CAHPS. Another commenter stated that measuring access to care and patient experience through the CAHPS survey measures is not meaningful because survey results are not actionable (like complaints are), as questions are broad and ambiguous. A commenter did not want CMS to solely rely on CAHPS survey measures as an indicator of beneficiary experience.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that CAHPS survey measures and complaint data capture feedback on member experience and access to care in different ways. However, the complaints measure no longer supports the purpose of the Star Ratings program, which is to differentiate plan performance in areas where meaningful variation exists. As noted in the response directly above, CMS will continue to monitor complaint data outside of Star Ratings and use this real-time, actionable information for compliance and oversight purposes. This approach allows us to maintain robust oversight while focusing the Star Ratings program on measures that effectively differentiate plan quality. Several measures will remain in the Star Ratings that capture beneficiary satisfaction, care coordination, and quality of care.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended delaying the removal of the complaints measure to allow for further evaluation of its impact on plan behavior and beneficiary protection. Some commenters suggested that CMS should implement enhanced monitoring or alternative accountability mechanisms before removing the measure from Star Ratings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have carefully considered the timing of this change and find that implementing the removal beginning with the 2029 Star Ratings (based on 2027 measurement year data) provides adequate notice to plans and stakeholders to prepare for the change.
                    </P>
                    <P>CMS will continue to monitor complaint data and maintain robust oversight mechanisms outside of the Star Ratings program. We do not find that delaying implementation is necessary given the historically low complaints volume and the continued availability of other accountability tools.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested changes to the CTM measure specifications. For example, some commenters recommended CMS exclude certain complaints, such as duplicates or provider complaints from the measure; reflect root cause of beneficiary complaints; remove Tukey outlier deletion when calculating this measure's cut points; calculate complaint rates by geographic area instead of by contract; create a new measure solely based on provider complaints or a measure that places a higher weight on provider complaints; or distinguish complaints about inpatient admissions, denials, and post-acute care delays from general customer service issues.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the suggestions and will consider them for future measure development or internal oversight metrics.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters urged CMS to make CTM complaint data more publicly accessible, including the substance of complaints and plan responses or total complaints stratified by complaint type, to help showcase true beneficiary experience and assist prospective enrollees in comparing plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these suggestions and recognize the value of transparency in helping beneficiaries make informed enrollment decisions. We will continue to evaluate opportunities to enhance the transparency and accessibility of complaint data while balancing privacy considerations and administrative feasibility.
                    </P>
                    <P>However, these transparency efforts are separate from the Star Ratings program and do not affect our decision to remove the complaints measure from Star Ratings because of its limited value as a quality measure in light of the lack of variability across contracts.</P>
                    <P>When the complaints measure is removed from the Star Ratings, the measure will be moved to the display page and continue to be publicly reported.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that more information be shared by CMS about the complaints process itself, so that beneficiaries and providers are able to navigate the system effectively.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Information on how to file a complaint with 1-800-MEDICARE is available in multiple Medicare publications and online references. An online complaints form is available, and CMS recently released a provider 
                        <PRTPAGE P="17506"/>
                        complaint form to improve consistent intake of those issues. We will continue to work with stakeholders to improve the visibility of these important avenues for beneficiaries and providers to contact CMS.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the complaints measure beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">e. Medicare Plan Finder (MPF) Price Accuracy (Part D)</HD>
                    <P>We proposed removing the MPF Price Accuracy (Part D) measure. Average scores on this measure were very high at 98 for MA-PD contracts and 97 for PDP contracts in the 2025 Star Ratings. Additionally, there is not a lot of variability across most contracts on this measure. If this measure were removed, CMS would continue to monitor plan performance related to drug prices posted on MPF.</P>
                    <P>We solicited comment on removing the MPF Price Accuracy measure from the 2029 Star Ratings. A discussion of the MPF Price Accuracy measure removal comments, along with our responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported the removal of this measure. Most supporters mentioned their agreement with the reasons for removal stated in the Contract Year 2027 proposed rule, such as high average scores and limited variability across contracts, which limits ability to distinguish between plan performance. A few commenters mentioned that removal of this measure would reduce administrative burden, with a couple mentioning resources could be redirected to patient outcomes. Another commenter stated that the measure does not meaningfully reflect quality.
                    </P>
                    <P>Several commenters supportive of removal also noted that they agreed with CMS's plan to continue to monitor these data outside of Star Ratings. One commenter specifically stated that CMS's announcement of MPF monitoring in the October 31, 2024 HPMS memorandum with the subject “Medicare Plan Finder Part D Drug Pricing Data Submission Monitoring” was an important step for drug price monitoring, and recommended CMS continue to improve the methodology of this measure when it is removed from the Star Ratings.</P>
                    <P>A couple of commenters stated that this measure has methodology issues, with one offering ideas to improve the measure if it is not removed. A commenter also stated there was potential “gaming” of this measure through artificial adjustments of pricing files. Another stated that several large national insurance providers “control” the measure due to their dominance in the Pharmacy Benefit Manager (PBM) market, so removal of the measure would create a more level playing field.</P>
                    <P>
                        <E T="03">Response:</E>
                         We thank these commenters for their support.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters opposed the removal of this measure. Most of these commenters noted the importance of accurate data on the MPF so that beneficiaries can make informed choices about their drug coverage. Several noted that the measure is important for holding plans accountable for transparent and accurate pricing data. A commenter noted that lower-income beneficiaries would be especially impacted by removal of the measure since they are more sensitive to price changes. A commenter stated that removing the financial incentive that this measure provides for plans to provide accurate pricing data could reverse progress toward beneficiary protection.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that transparent and accurate data on the MPF are critical for all beneficiaries to make informed decisions about coverage. We would like to assure commenters that CMS will continue to monitor the accuracy of plans' MPF pricing data when this measure is removed from the Star Ratings. This measure will be moved to the display page, and CMS will explore potential future improvements to the measure methodology. CMS will follow up with plan sponsors with poor performance on the MPF price accuracy display measure as necessary.
                    </P>
                    <P>CMS also performs validations when the pricing data are submitted to CMS for the MPF. The May 27, 2025 HPMS memorandum titled “Contract Year (CY) 2026 Part D Pricing Data Submission Guidance” states that HPMS uses a multi-tiered approach when validating the in-bound drug pricing file submissions from plan sponsors. These validations are tools used by CMS to identify potential inaccuracies prior to display on MPF and may prompt CMS to contact a sponsor for clarification of the accuracy of its submission.</P>
                    <P>CMS will suppress the display of a sponsor's information when the sponsor fails to correct its data, confirm the accuracy of its data, or respond to a CMS inquiry. Sponsors may be subject to Part D program compliance actions because of MPF suppressions or inaccurate data submissions.</P>
                    <P>Validations may be added or updated based on CMS's monitoring of the MPF drug pricing data.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters that opposed removal of the measure noted that beneficiary experience with MPF in the 2025 Annual Enrollment Period (AEP) was difficult due to the prices constantly changing from week to week, and that this pricing information needs to remain reliable.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS notes that the MPF Price Accuracy measure does not use data from AEP (October-December). CMS has a separate monitoring initiative for price changes between AEP and the contract year (CY), as announced in the HPMS memorandum dated October 31, 2024 with subject “Medicare Plan Finder Part D Drug Pricing Data Submission Monitoring”.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that this measure is important for small plans to distinguish their plan performance for prospective enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This measure has high average scores and limited variability across contracts, limiting its ability to distinguish between plan performance.
                    </P>
                    <P>After consideration of the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are finalizing the removal of the MPF Price Accuracy measure for the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">f. Diabetes Care—Eye Exam (Part C)</HD>
                    <P>We proposed removing the Diabetes Care—Eye Exam (Part C) measure as part of our effort to streamline the Star Ratings measure set and increase the focus on patient experience and outcome measures. There are several other measures currently in the Star Ratings that focus on diabetes care, thus, covering a similar topic area as this measure. Given the importance of diabetes care, we proposed to move this measure to the display page.</P>
                    <P>We solicited comment on removing the Diabetes Care—Eye Exam measure from the 2029 Star Ratings. A discussion of the Diabetes Care—Eye Exam measure removal comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Most commenters opposed the removal of the Diabetes Care—Eye Exam measure from the Star Ratings. Some commenters noted that diabetic retinopathy is a leading cause of preventable blindness and that routine eye exams are essential for early detection of asymptomatic disease and timely intervention preventing severe vision loss. They also emphasized that the eye exam measure captures a clinically distinct and non-duplicative aspect of diabetes care that is not 
                        <PRTPAGE P="17507"/>
                        addressed by other Star Ratings measures related to glycemic control, medication adherence, or kidney health. Other commenters noted that these exams serve as one of the most efficient and non-invasive tools for identifying broader health concerns. A number of commenters argued that preventing vision loss helps avoid expensive late-stage ophthalmic treatment, caregiver and long-term services and supports costs, functional decline and institutionalization.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the extensive feedback received on the Diabetes Care—Eye Exam measure and agrees with commenters that routine retinal screening is a critical component of comprehensive diabetes care. We agree that retinal examinations can identify broader health concerns and that preventing vision loss may help avoid costly late-stage treatment, functional decline, caregiver burden, and long-term services and supports. CMS also agrees that these considerations are consistent with the goals of the Star Ratings program to promote preventive care, preserve functional independence, and support whole-person care.
                    </P>
                    <P>After careful consideration of public comments, CMS is retaining the Diabetes Care—Eye Exam measure in the Star Ratings program. Continued inclusion of this measure will help maintain plan accountability, support access to preventive screening, and encourage care coordination and innovation in screening approaches, particularly for high-risk and underserved populations.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters stated that removing this measure would create a vision-care gap in the Star Ratings program, as this measure is the only ophthalmic/vision-focused measure. They argued that downgrading the measure to display-only would lead to fewer screenings and more avoidable blindness, as well as other economic and public-health repercussions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges commenters' concerns regarding the importance of monitoring vision-related preventive care for beneficiaries with diabetes and agrees that diabetic eye exams are a critical component of comprehensive diabetes management. Regardless of whether the measure is included in the Star Ratings calculation, MA plans and their contracted providers remain responsible for ensuring beneficiaries have access to clinically appropriate preventive services and supporting beneficiaries in obtaining recommended care, including diabetes-related eye exams. After consideration of the comments received, we are retaining this measure in Star Ratings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters argued that Star Ratings measures drive outreach, provider engagement, care-gap closing, benefit design, and investment, whereas display-only measures receive far less operational prioritization. Many commenters stressed that if the measure is no longer included in Star Ratings, plans may redirect resources away from screening programs even if coverage technically remains.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS recognizes that inclusion as a Star Ratings measure can influence plan prioritization, operational focus, and investment. At the same time, the Star Ratings program cannot encompass every facet of clinical care, and the absence of a specific measure from the ratings calculation does not diminish the clinical importance of the service. Eye exams are a critical component of high-quality diabetes care regardless of whether the measure is included in Star Ratings. CMS expects plans to support appropriate screening, outreach, and provider engagement to ensure beneficiaries receive recommended diabetes-related eye exams consistent with established standards of care.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters disputed that the measure is topped out or no longer differentiates plans. They pointed to continued gaps in screening rates and variation across plans, arguing plan performance still has room to improve and the measure still functions as an accountability lever.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees with commenters that performance on this measure has not topped out and continues to show variation across plans. As discussed in the Contract Year 2027 proposed rule, CMS proposed to remove this measure as part of a broader effort to streamline the Star Ratings measure set in areas where multiple measures address diabetes care. However, after consideration of public comments, CMS is retaining the Diabetes Care—Eye Exam measure in the Star Ratings program because it captures a clinically distinct and preventive aspect of diabetes care that is not fully addressed by other measures.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern that removing the measure from the Star Ratings program could reduce MA plans' outreach, care coordination, and investment in screening programs, potentially leading to declines in screening rates. Commenters emphasized that the measure is particularly important for SNP (D-SNP, C-SNP, and I-SNP) populations with complex chronic conditions, as well as beneficiaries in rural communities facing provider shortages, transportation challenges, and other access barriers. Commenters also noted that homebound, low-mobility, and underserved beneficiaries often rely on in-home, mobile, and community-based screening programs, which are frequently structured around closing Star Ratings measure gaps and may be scaled back if the measure is no longer scored.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that ensuring access to recommended diabetes-related preventive services is especially important for beneficiaries with complex needs and those facing access barriers, including SNP enrollees and beneficiaries in rural or institutional settings. Regardless of whether a measure is included in Star Ratings, plans remain responsible for ensuring all beneficiaries have access to appropriate preventive services and supporting timely diabetes-related screenings. CMS will be keeping this measure in Star Ratings since routine retinal screening is a critical component of comprehensive diabetes care and can identify broader health concerns. As we have considered the comments received, we agree this measure focuses on a clinically distinct and preventive aspect of diabetes care that is not fully addressed by other measures.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters stated that inclusion of this measure in the Star Ratings program has been a significant driver of innovation in care delivery. Commenters noted that the measure has incentivized MA plans and providers to adopt new screening models such as teleophthalmology, mobile and in-home screening services, point-of-care retinal imaging in primary care settings, and FDA-cleared autonomous artificial intelligence technologies to help expand access to diabetic eye exams. Commenters emphasized that these innovations have helped overcome workforce shortages, transportation barriers, and specialist access challenges, particularly in rural and underserved communities, while improving efficiency and reducing administrative burden. Several commenters expressed concern that removing the measure from the Star Ratings calculation could slow or reverse investment in these innovative approaches.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' perspectives on the role of this measure in encouraging innovation and expanding screening access. As previously explained, CMS is retaining this measure in the Star Ratings program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters offered alternatives to removal, 
                        <PRTPAGE P="17508"/>
                        including refining or strengthening the measure rather than deleting it (
                        <E T="03">i.e.,</E>
                         adjusting weighting, improving reporting alignment), adding follow-up care or care coordination after abnormal results, adopting hybrid or chart review approaches, and revisiting exclusions and/or measurement scope for certain populations (
                        <E T="03">e.g.,</E>
                         ESRD patients and members who receive optical care through other benefits or coverage). These commenters suggest delaying removal until a suitable replacement exists. A commenter supported moving the measure to the display page but urged ongoing monitoring and possible reassessment if screening rates decline.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the recommendations for potential future refinements, including approaches related to follow-up care, exclusions, and measurement methodology. We will take these suggestions into consideration for potential future updates to this measure.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported removing this measure, stating that diabetes care is already represented in Star Ratings through other measures and that removing this process measure supports streamlining and refocusing on outcome and patient experience measures.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates support for streamlining the Star Ratings measure set and focusing on measures that best reflect outcomes and beneficiary experience related to diabetes care. We agree that several existing diabetes measures capture important aspects of diabetes clinical management and treatment outcomes. Collectively, these measures provide meaningful insight into plan performance in managing diabetes. At the same time, after consideration of public comments, CMS is retaining the Diabetes Care—Eye Exam measure in the Star Ratings program because it captures a clinically distinct and preventive aspect of diabetes care that is not fully addressed by other measures.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters raised concerns about persistent data gaps, challenges capturing eye exams completed outside MA plan networks or channels, coding and interoperability limitations between primary care and vision providers, and confusion regarding what services qualify for measure compliance. Commenters stated that these issues may limit the measure's ability to fully reflect true care delivery or plan performance and may contribute to administrative burden.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the feedback regarding data collection, measurement reliability, operational burden, and clarity of measure specifications. CMS recognizes the challenges associated with capturing services furnished across multiple care settings and providers, including those outside plan-contracted networks, as well as coding and interoperability limitations. CMS will continue to evaluate data sources and measurement approaches and consider opportunities for improvement.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are not finalizing this proposal to remove the Diabetes Care—Eye Exam measure from the Star Ratings.</P>
                    <HD SOURCE="HD3">g. Statin Therapy for Patients With Cardiovascular Disease (Part C)</HD>
                    <P>We proposed removing the Statin Therapy for Patients with Cardiovascular Disease (Part C) measure as part of our effort to streamline the Star Ratings measure set and increase the focus on patient experience and outcome measures. There is not a lot of variation in performance across contracts on this measure, and there are other measures, such as Medication Adherence for Cholesterol (Statins), currently in the Star Ratings that cover a similar topic area as this measure. As noted in the Announcement of Calendar Year (CY) 2026 Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies, the National Committee for Quality Assurance (NCQA) reevaluated the Statin Therapy for Patients with Cardiovascular Disease (Part C) measure for the 2026 measurement year. The changes finalized by NCQA expand the eligible population and are considered a substantive change to the measure. In light of this substantive change, the Statin Therapy for Patients with Cardiovascular Disease measure was already set for removal to the 2028 display page following the process described at § 422.164(d)(2), and any adoption of the updated measure would need to be proposed and finalized through future rulemaking. While § 422.164(d)(2) gives CMS the discretion to continue to use a legacy measure in Star Ratings while a substantively updated version is on the display page, use of the legacy measure was not feasible here due to the nature of the substantive changes. CMS will monitor changes in performance for this measure, as updated and included on the display page, since statin therapy is important in lowering cholesterol and reducing the risk of cardiovascular disease.</P>
                    <P>We solicited comment on removing the Statin Therapy for Patients with Cardiovascular Disease measure from the 2028 Star Ratings. A discussion of the Statin Therapy for Patients with Cardiovascular Disease measure removal comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported removing this measure due to minimal performance variation and the availability of similar measures already in Star Ratings, such as Medication Adherence for Cholesterol (Statins). Commenters highlighted significant clinical limitations with the measure, such as that it captures prescriptions but not adherence, inadequately accounts for statin intolerance, creates administrative burden, and encourages coding behaviors that conflict with clinical judgment. A commenter also emphasized that a single prescription is insufficient for cardioprotective benefits, with some commenters adding that the measure excludes alternative cholesterol-lowering treatments, such as diet, exercise, or alternative medications. Commenters also noted the measure would remain on the 2028 display page as another reason for their support.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank these commenters for their support of our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters opposed removing the measure, emphasizing its importance for the health and quality of life of patients with cardiovascular disease. Commenters noted that statin therapy is evidence-based for this population and linked to reduced mortality. Others urged CMS to delay removal until another validated outcome-based measure is introduced.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This measure will be on the display page so it will still be publicly reported and used for monitoring. Given the substantive change for the 2026 measurement year for this measure, the measure has to be moved to the display page for at least two years following the process described at § 422.164(d)(2). The updated measure would need to be proposed through rulemaking. We do not have data for the legacy measure to continue to include in the Star Ratings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended replacing the Statin Therapy for Patients with Cardiovascular Disease process measure with a low-density lipoprotein cholesterol (LDL-C) control or LDL-C response outcome measure. These alternative measures would account for statin intolerance while expanding the denominator to include all patients who could benefit from cholesterol-lowering therapy. Additionally, rather than 
                        <PRTPAGE P="17509"/>
                        removing the measure, a commenter recommended considering a complimentary measure focused on medication access, affordability, and utilization since statins remain underused in peripheral arterial disease. Another commenter recommended that CMS eliminate the exclusion of individuals aged 66 and above to align with the Statin Use in Persons with Diabetes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the suggestions and will take them into consideration as we consider future measure changes. If we were to introduce an alternative measure in the future, it would need to be proposed and finalized through the rulemaking process. It is important that providers and plans provide appropriate care for Medicare beneficiaries with cardiovascular disease whether the Star Ratings includes the Statin Therapy for Patients with Cardiovascular Disease measure or not.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted that despite an apparent performance ceiling for this measure at the contract level, substantial disparities in statin initiation and adherence persist among older adults, women, and racial/ethnic minorities, populations disproportionately represented in MA organizations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This measure will be on the display page so performance on this measure will still be publicly available. While Part C and D Star Ratings cannot measure every aspect of care delivery, providers and plans should still deliver clinically appropriate care to all populations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters argued that removal of this measure is premature given NCQA's recent substantive specification changes expanding the eligible population. They urged CMS to evaluate the updated measure's performance before removal. Some commenters urged CMS to reintroduce the measure after the two-year display period, with one commenter arguing that the measure is more robust at identifying high risk patients than the Statin Use in Persons with Diabetes (Part D) measure and more methodologically sound as it includes clinically justified exclusions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The measure will be on the display page starting with the 2028 Star Ratings due to the substantive change made by NCQA discussed above. CMS is committed to continuing to monitor performance on the updated measure. If CMS were to bring back this measure into Part C Star Ratings, it would have to be proposed through future rulemaking.  
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the Statin Therapy for Patients with Cardiovascular Disease beginning with the 2028 Star Ratings.</P>
                    <HD SOURCE="HD3">h. Members Choosing To Leave the Plan (Part C and Part D)</HD>
                    <P>We proposed removing the Members Choosing to Leave the Plan (Part C and D) measure as part of our effort to streamline the Star Ratings measure set and increase the focus on patient experience and outcome measures. We proposed removing the measure based on previous feedback from Part C and D sponsors that they would prefer this measure be at the parent organization level versus the contract level or that they would like additional exclusions for the measure such as exclusions for terminations of provider networks. Additionally, without knowing the reasons for disenrollment, it is hard for enrollees to interpret what this measure score means and make meaningful comparisons between contracts. The current measure at the contract level would move to the display page.</P>
                    <P>We solicited comment on removing the Members Choosing to Leave the Plan measure from the 2029 Star Ratings. A discussion of the Members Choosing to Leave the Plan measure removal comments, along with our responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported removing the measure, emphasizing that disenrollment can be driven by non-quality factors and can be hard for beneficiaries to interpret without context on why members left. Common reasons for supporting removal included cost or price shopping, broker or marketing dynamics, competitors, geographic moves, policy changes, and other external forces.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and agrees there can be challenges in interpreting why beneficiaries may leave a plan and the extent to which disenrollments may be influenced by factors not solely related to plan quality.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters argued that voluntary disenrollment is one of the most straightforward indicators of whether a plan is meeting member needs so should remain in Star Ratings. They stated that disenrollment rates serve as the best proxy for beneficiary dissatisfaction by reflecting members' decisions to leave a plan. Many of these commenters contrasted this measure with the CAHPS survey, noting that CAHPS relies on survey sampling and captures reported perceptions rather than observed enrollment behavior.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments regarding the value of voluntary disenrollment as an objective, behavior-based indicator that may reflect enrollee experience with the plan. Although the Members Choosing to Leave the Plan measure may reflect beneficiary dissatisfaction to an extent, it is difficult to interpret from an overall disenrollment rate why beneficiaries are leaving a contract, so it is less useful as a quality measure. Disenrollments do not necessarily reflect issues with the quality of care provided. We know that beneficiaries disenroll for many reasons, including financial reasons, issues receiving needed care, coverage related to doctors, hospitals, and prescriptions, and issues getting information and help from the plan. The most common reasons for disenrollment are financial reasons and doctors, clinics, and hospitals not belonging to the enrollee's plan network. CMS plans to continue publicly reporting this measure on the display page so overall information about voluntary disenrollment remains transparent and available to beneficiaries and other interested parties.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted that the Members Choosing to Leave the Plan measure functions as an accountability and oversight mechanism, and that reporting it on the display page does not create the same incentive for plans to fix root causes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters emphasized that the disenrollment measure is especially important for high-need populations (particularly individuals diagnosed with end-stage renal disease (ESRD) and SNP enrollees) because disenrollment can indicate serious mismatches between plan design and member needs. Some of these commenters urged CMS to retain the measure and refine it with these vulnerable groups in mind.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments. CMS will continue public reporting of this measure on the display page and will take into consideration recommendations for future measure updates.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that we retain the measure in Star Ratings but modify the technical specifications to better measure voluntary disenrollments. Several commenters argued that evaluating disenrollment at the contract level can misclassify switching within the same parent organization as negative performance. They encouraged CMS to evaluate disenrollment at the parent 
                        <PRTPAGE P="17510"/>
                        organization level. Other commenters urged CMS to refine exclusions by excluding disenrollments tied to state Medicaid eligibility or policy changes affecting dual status and using reason codes to better capture true voluntary disenrollment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments. CMS will publicly report this measure on the display page and take into consideration recommendations for future measure updates.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters raised concerns that if the Members Choosing to Leave the Plan measure is removed from Star Ratings, plans might face less pressure to avoid practices that frustrate members. A commenter specifically warned that removing this measure could enable plans to adopt policies that drive away members and could distort CAHPS survey participation (since members who leave may not be captured as intended).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS disagrees that retiring this measure will meaningfully reduce plan incentives to address disenrollment-related issues, as plans have existing financial and operational incentives separate from Star Ratings to retain enrollees and maintain high-quality performance. Additionally, we will continue to monitor performance on this measure over time.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the Members Choosing to Leave the Plan measure beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">i. Customer Service and Rating of Health Care Quality (Part C)</HD>
                    <P>We proposed removing the Customer Service and Rating of Health Care Quality (Part C) measures as part of our effort to streamline the Star Ratings measure set. Compared to other patient experience of care measures, there is less variation in performance across contracts on these measures. We would continue to collect these data for quality improvement purposes and report the measures on the display page.</P>
                    <P>We solicited comment on removing the Customer Service and Rating of Health Care Quality measures from the 2029 Star Ratings. A discussion of the Customer Service and Rating of Health Care Quality measure removal comments, along with our responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported the removal of the Customer Service and Rating of Health Care Quality measures, noting there is minimal variation in performance across contracts and that cut points have been stable for many years. A couple of commenters noted that these measures often reflect factors outside a health plan's direct control.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the support for removing the Part C Customer Service and Rating of Health Care Quality measures. As stated in the Contract Year 2027 proposed rule, we are proposing removal as part of an effort to streamline the Star Ratings. We disagree, however, that these measures are outside of health plans' control. Consumer experiences with customer service and perceptions of health care quality are important aspects of a patient's experience. The MA and PDP CAHPS surveys have been rigorously developed and tested to assess enrollee experiences on domains that enrollees have reported to be important to them in defining high quality care from Medicare health and drug plans.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters opposed the removal of the Customer Service and Rating of Health Care Quality measures, noting the importance of measures that reflect member experience. Commenters stated that excluding these measures from Star Ratings calculations diminishes their value and ability to incentivize health plans to invest in high-quality beneficiary experiences. Some commenters stated these measures are important for individuals selecting a health plan to consider, as well as for CMS to measure the overall quality of care provided by plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees these measures capture important areas of plan performance. The measures will still be collected through the MA and PDP CAHPS Survey and results will be included in the CAHPS health plan reports provided each year to plans to support their quality improvement efforts and reported as display measures on 
                        <E T="03">CMS.gov</E>
                        . Also, the Rating of Health Plan measure that will remain in the Star Ratings will capture these areas of performance.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed concern that removing the Customer Service measure assessing beneficiary experience with MA plan operations will reduce MA plan oversight to ensure enrollees are receiving timely and quality access to their respective benefits and coverage. Commenters recommend that CMS consider opportunities to better measure customer service, rather than removing the measure entirely from the Star Ratings program.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' emphasis on the importance of customer service and beneficiary experience with MA plan operations. CMS agrees that timely, accurate, and high-quality customer service is essential to ensuring enrollees' access to benefits, regardless of whether such measures are included in the Star Ratings program. Removing the Customer Service measure from Star Ratings does not reduce CMS's expectations that MA plans will provide high-quality customer service to their enrollees. CMS will continue to report this measure on the display page and continue to monitor performance. CMS also remains committed to evaluating opportunities to better measure beneficiary experience and customer service.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the removal of the Customer Service and Rating of Health Care Quality measures beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">2. Adding Measure</HD>
                    <HD SOURCE="HD3">a. Depression Screening and Follow-Up (Part C)  </HD>
                    <P>We are committed to continuing to improve the Part C and D Star Ratings system by focusing on improving clinical and other health outcomes. Consistent with §§ 422.164(c)(1) and 423.184(c)(1), we continue to review measures that are nationally endorsed and in alignment with the private sector as described at 83 FR 16533. For example, we regularly review measures developed by NCQA and the Pharmacy Quality Alliance (PQA). As we continue to align with the Universal Foundation, we also proposed to add the Part C Depression Screening and Follow-Up (DSF) measure to the 2029 Star Ratings (measurement year 2027). CMS began reporting the DSF measure on the display page for the 2026 Star Ratings. As provided at §§ 422.164(c)(3) and (4) and 423.184(c)(3) and (4), as new performance measures are developed and adopted they are initially posted on the display page for at least two years.</P>
                    <P>
                        We solicited feedback regarding whether to add the DSF measure to the 2026 Star Ratings display page (using data from the 2024 measurement year) in the Advance Notice of Methodological Changes for Calendar Year (CY) 2024 for Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies and noted that it would need to go through rulemaking to be added to the Star Ratings.
                        <SU>92</SU>
                        <FTREF/>
                         DSF 
                        <PRTPAGE P="17511"/>
                        measures the percentage of eligible MA plan members who were screened for clinical depression using a standardized instrument and, if screened positive, received follow-up care within 30 days. This aligns with the U.S. Preventive Services Task Force recommendations regarding screening and follow-up for depression,
                        <SU>93</SU>
                        <FTREF/>
                         supports CMS's efforts to implement the Universal Foundation set of measures across quality programs, and focuses on improving the well-being of beneficiaries as well as MAHA priorities by encouraging MA health plans to screen for depression and follow-up with appropriate care. Although this is a process measure, health outcomes can be improved by identifying individuals with depression and providing treatment. There are currently no measures specific to behavioral health care in the Part C and D Star Ratings, so adding this measure would fill an important gap.
                    </P>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             See page 162 at 
                            <E T="03">https://www.cms.gov/files/document/2024-announcement-pdf.pdf</E>
                             for a summary of comments.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             
                            <E T="03">https://www.uspreventiveservicestaskforce.org/uspstf/recommendation/screening-depression-suicide-risk-adults.</E>
                        </P>
                    </FTNT>
                    <P>
                        Depression is a common mental disorder that occurs in people of all ages, and estimates of major depression were 13.1 percent in people age 12 and older and 8.7 percent in people age 60 and older during the period from August 2021 through August 2023.
                        <SU>94</SU>
                        <FTREF/>
                         Depression can exacerbate other chronic medical conditions, and it increases the risk of morbidity and mortality. There is evidence that screening tools used in primary care settings can accurately identify depressed individuals and treatment can improve depression outcomes.
                        <SU>95</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             
                            <E T="03">https://www.cdc.gov/nchs/data/databriefs/db527.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             
                            <E T="03">https://pmc.ncbi.nlm.nih.gov/articles/PMC7661597/</E>
                             and 
                            <E T="03">https://www.amjmed.com/article/S0002-9343(22)00524-1/fulltext.</E>
                        </P>
                    </FTNT>
                    <P>
                        We submitted the DSF measure through the 2024 Pre-rulemaking Review Process for review by the Measures Application Partnership, which is a multi-stakeholder partnership that provides recommendations to HHS on the selection of quality and efficiency measures for CMS programs, and the Measures Application Partnership provided support for this measure.
                        <SU>96</SU>
                        <FTREF/>
                         Consensus was not reached on this measure. The committee recommended that the Merit-based Incentive Payment System (MIPS) program consider replacing their similar measure with this one to improve alignment across quality programs 
                        <SU>97</SU>
                        <FTREF/>
                         and to report the screening and follow-up rates separately. The HEDIS measure differs slightly from the MIPS measure since the specification is at the health plan level and also focuses on examining follow-up actions when positive screenings occur. CMS will display separate rates for screening and follow-up on the display page and take an average of the rates for the Star Ratings measure.
                    </P>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             
                            <E T="03">https://p4qm.org/sites/default/files/2025-02/PRMR-2024-2025-MUC-Recommendations-Report-Final.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             The MIPS measure differs from the NCQA one in that the MIPS version requires a qualifying encounter, whereas the NCQA-stewarded version looks for a screen at any time in the measurement period; the follow-up component of the MIPS version entails documentation of a follow-up plan, whereas the NCQA-stewarded version is more intensive requiring follow-up care; the follow-up timeframe in the MIPS version is on or up to 2 days after the date of the qualifying encounter, whereas the NCQA-stewarded measure uses a timeframe of on or up to 30 days after the date of the positive screen; and the MIPS version only excludes individuals with a diagnosis of bipolar disorder, whereas the NCQA version excludes individuals with bipolar disorder or a current diagnosis of depression.
                        </P>
                    </FTNT>
                    <P>We solicited comment on adding the Depression Screening and Follow-Up measure to the 2029 Star Ratings. A discussion of the Depression Screening and Follow-Up measure addition comments, along with our responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported adding the DSF measure to the Star Ratings program. Commenters noted that this measure would encourage MA plans to screen for depression and follow up with appropriate care and to expand access to behavioral health services. Some commenters noted that the DSF measure would fill a gap in the Star Ratings program related to behavioral health and is aligned with the Universal Foundation set of measures across quality programs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters were concerned with the administrative burden related to the DSF measure, such as the investment needed to set up the data structures and workflows to track and report depression screening and follow-up data. Other commenters noted challenges implementing the measure due to inconsistent availability of data and issues with the interoperability of electronic data. Specifically, a few commenters had concerns with the measure requiring the use of Logical Observation Identifiers Names and Codes (LOINC) codes, which they claimed are inconsistently used and not always transmitted to plans. Some commenters recommended expanding the measure to include hybrid reporting or use of any digital data source including both claims and clinical data including CPT and HCPCS codes such as 96127, 96160, 96161, and G0444 (Annual Depression Screening). A commenter further suggested that CMS should work with smaller practices and community-based organizations to address technical barriers they face with Electronic Clinical Data Systems (ECDS) reporting and LOINC codes. Another commenter recommended that CMS: (1) publish detailed ECDS specifications, including accepted standardized instruments, LOINC tables, and mapping examples for common EMRs, (2) issue an electronic medical records (EMR)/Health Information Exchange (HIE) readiness checklist and provider toolkit that include clinical workflow, documentation, and data flow, and (3) offer technical assistance with measure testing, data ingestion pilots, and feedback on cases.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the feedback on the challenges of implementing this measure. ECDS is a HEDIS reporting method for health plans to collect and submit quality measures. The DSF measure uses the ECDS reporting method, which was developed to allow for better tracking of patient outcomes across systems and to reduce the burden on providers to conduct manual chart reviews by pulling in data across EHRs, HIEs, clinical registries, and claims data. While we understand that this ECDS measure will require upfront investment in setting up the IT and workflow infrastructure, over time the ECDS, rather than traditional or hybrid reporting, will decrease the burden on providers. The ECDS reporting method used in DSF requires the use of electronic data standards and that all data be stored in structured fields in a standard layout. The data sources for ECDS reporting include electronic health records/personal health records, health information exchange/clinical registry, case managements systems, and data from administrative claims. Given the need for structured data, DSF requires the use of LOINC codes. To allow some flexibility, HEDIS does allow mapping to the measure's specified LOINC codes as appropriate. For example, if the questions of a specified instrument are used, but are labeled with the name of a different instrument (
                        <E T="03">e.g.,</E>
                         PHQ-2 questions within the PHQ-A), mapping to one of the specified LOINC codes is acceptable.
                    </P>
                    <P>
                        CMS appreciates the commenters' recommendations regarding additional technical resources to support implementation of this measure. The measure specifications are developed and maintained by NCQA, the measure steward, and include the technical requirements necessary for reporting. Detailed specifications, including 
                        <PRTPAGE P="17512"/>
                        coding and data element guidance, are available through NCQA's established measure maintenance processes. CMS encourages stakeholders to refer to NCQA resources for the most current technical guidance. CMS is not prescribing EMR- or HIE-specific implementation tools, workflow guidance, or mapping examples through regulation, given the significant variation in health IT systems, data sources, and clinical workflows across MA organizations and provider settings. MA organizations remain responsible for working with their providers and vendors to operationalize measure reporting within their existing infrastructure.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters were concerned about their ability to track whether follow-up care occurred, noting limitations such as state-specific legal barriers to accessing behavioral health data and limited visibility into care delivered outside their network. A couple of commenters further suggested that CMS conduct an impact analysis of how federal and state privacy laws may affect data availability given stricter limits on sharing mental health records in some places.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS acknowledges that data availability and access to behavioral health information may vary based on state law, privacy requirements, and whether care is furnished outside of a given organization's network. However, CMS does not agree that these considerations warrant modification of the finalized policy. This measure does not require access to detailed psychotherapy or mental health treatment records. The measure is designed to allow reporting based on information reasonably available to health plans, including documentation of referral, care coordination, or other appropriate follow-up actions consistent with existing legal and operational constraints. CMS notes that similar considerations apply broadly across quality measurement and care coordination activities and are not unique to depression screening or follow-up care.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters stated their belief that this measure will disproportionately burden physicians and indicated that the responsibility for strong performance is primarily the responsibility of providers rather than MA plans. These commenters requested that CMS hold MA plans accountable for providing support and increasing access to behavioral health resources. Another commenter suggested that CMS help ensure community mental health and substance use provider organizations are seamlessly able to contract with MA plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS does not agree that the measure inappropriately places the burden of performance solely on physicians or other individual providers. The DSF measure is reported at the MA contract level and reflects the collective performance of the MA organization's provider network. MA contracts are responsible for establishing provider networks, designing benefits, furnishing care management and care coordination services, and implementing quality improvement strategies to support measure performance. Accordingly, MA organizations retain primary accountability for ensuring that their networks are equipped to conduct depression screening and facilitate appropriate follow-up care.
                    </P>
                    <P>MA organizations already have multiple mechanisms to support providers and improve access to behavioral health services, including network adequacy requirements, utilization management policies, care coordination programs, supplemental benefits, and quality improvement initiatives. The measure is intended to encourage MA organizations to leverage these existing tools to strengthen screening and follow-up processes, including addressing gaps in access to behavioral health resources, and to collaborate with providers.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters request that CMS delay implementation of this measure to give plans and providers more time to get systems and processes in place to meet requirements. A commenter specifically asked for phasing in follow-up requirements over time.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This measure was reported on the 2026 display page. This measure will be on display for three years prior to it being added to the 2029 Star Ratings. This provides sufficient time for MA organizations to prepare for inclusion of this measure in Star Ratings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters were concerned about inadequate behavioral health resources in communities that already face significant behavioral health workforce and capacity shortages, potentially limiting their ability to provide follow-up care for those who screen positive for depression. These commenters requested that CMS monitor behavioral health network adequacy before implementing this measure.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the health care workforce shortages facing many communities, particularly in the field of behavioral health. Measuring depression screening and follow-up care will increase focus on behavioral health and likely lead to MA plans expanding access to behavioral health care. In addition, the measure specifications allow for telehealth or virtual appointments so that enrollees with limited access to follow-up care in their local vicinity may be able to access services in a virtual setting.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended that CMS report the depression screening and follow-up rates separately because averaging the rates may discourage depression screening since plans that screen fewer people may more easily achieve high follow-up rates. A commenter also suggested a higher weight for the follow-up rate.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is incentive to do well on both rates. For the screening rate, performance will be worse if fewer individuals are screened since the measure focuses on screening among the general population. We will display the rates for screening and follow-up separately on the display page so this information is publicly available. For the Star Ratings program, CMS plans to take an average of the rates to minimize the number of measures displayed on Medicare Plan Finder. We will monitor the rates for both the screening and follow-up measures and may propose changes over time if we see issues with combining the rates.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters recommended including telehealth and home-based depression screening and follow-up care in the measure.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We clarify that telehealth visits and home-based visits can count toward this measure if other requirements are met.
                        <SU>98</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             NCQA HEDIS Measurement Year 2026 Volume 2.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended restricting the measure denominator to the subset of patients with at least one valid encounter during the measurement year to increase the likelihood of screening being performed by a provider with an established relationship with the patient and minimize the need for population-wide outreach by health plans or other providers with no previously established relationship.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's recommendation to restrict the measure denominator to patients with at least one valid encounter during the measurement year. The inclusive denominator is intentionally designed to encourage comprehensive preventive care for all enrolled members, regardless of their recent utilization patterns. This 
                        <PRTPAGE P="17513"/>
                        ensures that screening opportunities are not inadvertently limited to only those individuals who have already accessed care during the measurement year.
                    </P>
                    <P>While we recognize the commenter's concern regarding the administrative burden of outreach to members without established provider relationships, proactive engagement with all enrollees is a fundamental component of effective preventive care delivery. Members who have not had recent encounters may represent a population at higher risk for unmet health needs and would benefit most from targeted outreach and screening initiatives.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters requested CMS provide clear guidance about what counts as “appropriate follow-up care.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Follow-up care includes outpatient, telephone, e-visits, or virtual check-in follow-up visits; depression case management encounters; behavioral health encounters including assessment, therapy, collaborative care, or medication management; an encounter for exercise counseling; or a dispensed antidepressant medication.
                        <SU>99</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             NCQA HEDIS Measurement Year 2026 Volume 2.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         Out of concern for the impact of this measure on medically complex individuals, a commenter recommended applying a case-mix adjustment that includes geography, LIS/DE status, and other demographic data. Another commenter recommended tracking rates across demographic groups.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Since this is a process measure, there is no case-mix adjustment so as not to set different performance standards for different groups or to mask differences in the quality of care across parts of the country. We encourage contracts to analyze their data and track and address differences in performance across subpopulations in their contract.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested flexibility as to who may administer the screening, especially for rural and underserved areas.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The HEDIS specifications for the depression screening rate are focused on screening using a standardized instrument rather than who administers the screening. The specifications also indicate that depression screening captured in health risk assessments or other types of health assessments are allowed if the questions align with a specific instrument that is validated for depression screening.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended avoiding duplicative requirements such as rescreening patients already diagnosed with depression.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The HEDIS specifications for the DSF measure already exclude individuals with a history of bipolar disorder or a current diagnosis of depression.
                        <SU>100</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             NCQA HEDIS Measurement Year 2026 Volume 2.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         As an alternative to the proposed measure, a commenter recommended implementing the Follow Up After Hospitalization for Mental Illness (FUH) measure. Another commenter recommended using a measure of Medicare Annual Wellness Visit (AWV) since depression screening often occurs at wellness appointments. Another commenter suggested moving to an outcome performance measure such as improvement in depression as measured by the Patient Health Questionnaire (PHQ-9).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the recommendations, but we disagree that these measures are feasible alternatives. The DSF measure was chosen over the FUH measure because of the focus on earlier identification and intervention for depression in an outpatient setting. The DSF measure is also part of the Universal Foundation set of measures across quality programs, which focuses on improving the well-being of beneficiaries. It is also aligned with MAHA priorities by encouraging MA health plans to screen for depression and follow up with appropriate care. Wellness visits are often an encounter where depression screening occurs, yet this alone is an insufficient way to measure depression screening. It also does not address a key component of DSF which is follow-up care for those who screen positive for depression within 30 days. Although DSF is a process measure, health outcomes can be improved by identifying those with depression early and giving them access to treatments for depression.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters recommend that CMS exclude patients with Major Neurocognitive Disorder (dementia) from this measure because the PHQ-9 is an invalid tool for this population. Another commenter recommended that CMS incorporate clinically appropriate exclusions for grief and loneliness, which may be prevalent in the Medicare population.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the feedback from commenters. Depression is prevalent among older adults, including individuals with Major Neurocognitive Disorder (dementia), and appropriate screening and treatment may improve quality of life, reduce morbidity, and help manage symptoms. While the PHQ-9 is a commonly used and validated screening instrument, it is not the only tool that may be used to meet the depression screening requirement under the DSF measure. Clinicians may use other standardized, validated depression screening instruments that are appropriate for the patient's cognitive status and clinical circumstances, consistent with accepted clinical practice.
                    </P>
                    <P>We also acknowledge commenters' recommendations regarding grief and loneliness. Grief and loneliness are recognized risk factors for clinical depression and are prevalent in the Medicare population. Their presence does not preclude depression screening; rather, it underscores the importance of screening to identify individuals who may benefit from further assessment, monitoring, or treatment. Accordingly, we do not find that categorical exclusions for dementia, grief, or loneliness are warranted, as the DSF measure is intended to support clinically appropriate, whole-person care and relies on provider judgment to determine the most suitable screening approach for each patient.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter indicated the measure is misaligned with MAHA principles and suggested using the MAHA Elevate model that emphasizes lifestyle and prevention over medicalized screening.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their feedback; however, we disagree that the DSF measure is misaligned with MAHA principles. There is a transparent process for adding measures to the Part C Star Ratings described at § 422.164(c). Any new measure first needs to go through the Pre-Rulemaking Review process and initial input is solicited through the Advance Notice process before being proposed through formal rulemaking. New measures must be on the display page for at least two years prior to inclusion in the Star Ratings. The DSF measure supports MAHA priorities by promoting whole-person care through early identification of depression and timely, appropriate follow-up, which are foundational to prevention and long-term health. Depression screening is a well-established, evidence-based preventive service that enables clinicians to identify individuals who may benefit from a range of interventions, including lifestyle-based, psychosocial, and clinical approaches.
                    </P>
                    <P>
                        Follow-up care under the DSF measure is not prescriptive or one-size-fits-all. Appropriate follow-up for individuals with a positive depression screen may include outpatient, telephone, e-visits, or virtual check-in 
                        <PRTPAGE P="17514"/>
                        follow-up visits; depression case management encounters; behavioral health encounters including assessment, therapy, collaborative care, or medication management; an encounter for exercise counseling; or a dispensed antidepressant medication. By supporting early detection and flexible, patient-centered follow-up, the DSF measure advances prevention, wellness, and individualized care consistent with MAHA principles.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the measure encourages MA plans to interfere with the patient-physician relationship by incentivizing MA plans to screen for depression and provide appropriate follow-up care.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for this feedback, yet we disagree. This measure should encourage collaboration between the plan and the provider to ensure the enrollee gets the care they need.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters request CMS align the DSF measure with other CMS quality programs, such as the DSF measure used in the Merit-based Incentive Payment System (MIPS), before implementation to avoid conflicting specifications, duplicative reporting, and additional administrative burden on providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the efforts to align measures across CMS quality programs. In the 2024 Pre-rulemaking Measure Review Process (PRMR), the committee recommended that the MIPS program consider replacing their measure with the one used for Medicare health plans to improve alignment across quality programs.
                        <SU>101</SU>
                        <FTREF/>
                         There are key factors that make the NCQA-stewarded version of the DSF measure more appropriate for the Star Ratings program, including that the specification is at the health plan level. The follow-up component of the MIPS version entails documentation of a follow-up plan, whereas the NCQA-stewarded version is more intensive, requiring follow-up care. Regarding clinical exclusions, the MIPS version only excludes individuals with a diagnosis of bipolar disorder, whereas the NCQA-stewarded version excludes individuals with bipolar disorder or a current diagnosis of depression.
                    </P>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">https://p4qm.org/sites/default/files/2025-02/PRMR-2024-2025-MUC-Recommendations-Report-Final.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that depending on the denominator definition and exclusions, the DSF measure may disproportionately limit applicability for I-SNP and Institutional Equivalent (IE)-SNPs, which may exacerbate measurement gaps for these plan types.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for the feedback. As long as an I-SNP only contract meets the denominator requirements for the measure, it will have a score for this measure. If an I-SNP is part of a larger contract that has non I-SNP enrollees, the measure score will include I-SNP and non I-SNP enrollees.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters stated that the large number of measures proposed for removal, as discussed in section V.B of this final rule, may negatively impact plans and that CMS should not implement a new measure at the same time.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Removing multiple measures should help reduce burden for plans and help them focus on new areas where there is significant room for improvement in clinical care. Depression screening is a serious and common mental disorder that occurs in people of all ages. The lifelong prevalence of depressive disorders is estimated to range from 10 to 15 percent.
                        <SU>102</SU>
                        <FTREF/>
                         Depression can exacerbate other chronic medical conditions and it increases the risk of morbidity and mortality. There is evidence that screening tools used in primary care settings can accurately identify depressed individuals and treatment can improve depression outcomes.
                        <SU>103</SU>
                        <FTREF/>
                         The addition of the DSF measure to the Star Ratings program will encourage screening and follow-up care for depression.
                    </P>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             Lépine, J.P., M. Briley. 2011. “The Increasing Burden of Depression.” 
                            <E T="03">Neuropsychiatric Disease and Treatment</E>
                             7(suppl 1): 3-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             O'Connor, E.A., E.P. Whitlock, T.L. Beil, B.N. Gaynes. 2009. “Screening for Depression in Adult Patients in Primary Care Settings: A Systematic Evidence Review.” 
                            <E T="03">Annals of Internal Medicine</E>
                             151(11):793-803.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended implementing the DSF measure through coordinated, interdisciplinary workflows that integrate physical therapy (PT), occupational therapy (OT), and speech-language pathology (SLP) due to their high frequency touchpoints with patients and to leverage existing data sources to minimize administrative burden. Another commenter recommended alternative screening options such as voice-based and modality-agnostic tools, which may be appropriate for older adults and those with limited English proficiency.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their recommendations. The DSF measure is provider and team agnostic, so implementation through coordinated interdisciplinary workflows is accepted and encouraged. For alternative screening options, if there is evidence that alternative screening mechanisms are clinically validated, these options will be considered for inclusion in the future.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to the comments, we are finalizing the addition of the Depression Screening and Follow-Up measure to the Star Ratings beginning with the 2029 Star Ratings.</P>
                    <HD SOURCE="HD3">3. Summary of Measure Changes for the Part C and Part D Star Ratings</HD>
                    <P>
                        Table 4 summarizes the additional measure addressed in this final rule, beginning with the 2029 Star Ratings. The measure description listed in this table is a high-level description. The annual Star Ratings measure specifications supporting document, the 
                        <E T="03">Medicare Part C &amp; D Star Ratings Technical Notes,</E>
                         provides detailed specifications for each measure. Detailed specifications include, where appropriate, more specific identification of a measure's: (1) numerator, (2) denominator, (3) calculation, (4) timeframe, (5) case-mix adjustment, and (6) exclusions. The Technical Notes document is updated annually. The annual Star Ratings are produced in the fall of the prior year. For example, Star Ratings for the year 2029 are produced in the fall of 2028. If a measurement period is listed as “the calendar year 2 years prior to the Star Ratings year” and the Star Ratings year is 2029, the measurement period is referencing the January 1, 2027 to December 31, 2027 period. As noted earlier in section V.B. of this final rule, CMS does not codify the specific measures for the Part C and D Quality Rating System in regulation; doing so would be unnecessarily lengthy and cumbersome due to the relative regularity with which measure specifications are updated.
                    </P>
                    <GPH SPAN="3" DEEP="143">
                        <PRTPAGE P="17515"/>
                        <GID>ER06AP26.033</GID>
                    </GPH>
                    <HD SOURCE="HD2">C. Streamlining the Methodology, Further Incentivizing Quality Improvement, and Suggestions for New Measures</HD>
                    <P>Finally, we solicited feedback on ways to streamline and modify the Star Ratings methodology to further incentivize quality improvement and suggestions for new outcomes measures to promote prevention and wellness of health and drug plan enrollees to make the Star Ratings program more aligned with MAHA efforts related to healthy aging, such as nutrition and patient well-being. We also solicited feedback on additional measures that could be removed in future years.</P>
                    <P>
                        Commenters broadly supported CMS's goal to streamline the Part C and D Star Ratings program and shift towards more outcome-focused and prevention-oriented measures, but many commenters cautioned against rapid, large-scale changes that could destabilize plans, reduce competition, and disproportionately harm plans serving high-need, complex, or vulnerable populations (
                        <E T="03">e.g.,</E>
                         SNPs, dually eligible individuals, and ESRD beneficiaries). Commenters urged CMS to phase in changes slowly, preserve stability tools in the methodology (guardrails, hold harmless, predictable cut points), and ensure fair benchmarking through stratification by plan type, population, and geography. Many commenters recommended reducing reliance on process and survey-based measures that have small samples or high volatility, while expanding outcome measures tied to chronic disease management, functional status, behavioral health access, nutrition/food-as-medicine, primary care investment, provider experience, and care transitions. Across commenters, there are comments related to aligning measures across programs, reducing administrative burden, improving transparency, and ensuring that quality incentives reflect plan-driven actions that improve beneficiary health, access, and well-being.
                    </P>
                    <P>We will take all comments received into consideration as we consider ways to streamline and modify the Star Ratings methodology and continue to review the Star Ratings measure set. Any additional changes to the methodology and measure set would need to go through the rulemaking process.</P>
                    <HD SOURCE="HD2">D. Health Equity Index Reward (§§ 422.166(f)(3) and 423.186(f)(3))</HD>
                    <P>
                        In the “Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly” final rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on April 12, 2023 (88 FR 22120) (“Contract Year 2024 final rule”), we finalized the addition of the Health Equity Index (HEI) reward (also called the Excellent Health Outcomes for All (EHO4all) reward) 
                        <SU>104</SU>
                        <FTREF/>
                         along with the removal of the historical reward factor at the same time. The HEI reward was intended to further incentivize Part C and D contracts to focus on improving care for enrollees that are dually eligible, receive a low-income subsidy, or are disabled because these groups are at risk for poor health outcomes and Star Ratings data show gaps in the quality of care for these enrollees. This reward was finalized at 42 CFR 422.166(f)(3) and 423.186(f)(3) to be implemented beginning with the 2027 Star Ratings using data from the 2024 and 2025 measurement years. The historical reward factor, which incentivizes consistent high performance across Star Ratings measures, was finalized at §§ 422.166(f)(1) and 423.186(f)(1) to be removed from the Star Ratings methodology with the implementation of the HEI reward in the 2027 Star Ratings using data from the 2025 measurement year. The historical reward factor was included in the Star Ratings beginning with the 2009 Star Ratings with the purpose of adding incentives for contracts to achieve high and stable relative performance across all measures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             In the 2026 Rate Announcement, we began to rebrand the Health Equity Index reward with a new name, the EHO4all reward. 
                            <E T="03">https://www.cms.gov/medicare/payment/medicare-advantage-rates-statistics/announcements-and-documents/2026.</E>
                        </P>
                    </FTNT>
                    <P>Since the Contract Year 2024 final rule, we have reviewed the HEI reward consistent with the Executive Order 14192, “Unleashing Prosperity Through Deregulation” and proposed to remove the HEI reward from the Star Ratings methodology. We proposed not to implement the HEI reward with the 2027 Star Ratings and instead continue the historical reward factor. Rather than incentivizing improvement among certain populations like those included in the HEI, CMS would instead incentivize improvement efforts on clinical care, outcomes, and patient experience, in line with the policy finalized in section V.B. of this final rule to refocus the Star Ratings measure set. We recognize that some health plans may have already expended resources on performance improvement focused on the populations included in the HEI reward; however, any improvements in performance among these populations will still contribute to higher performance on the Star Ratings by increasing measure-level scores even without the implementation of the HEI reward. Higher measure-level scores benefit health plans by improving overall performance on the Star Ratings.</P>
                    <P>
                        This shift is part of a broader effort to refocus the Star Ratings on clinical care, outcomes, and patient experience. In section V.B. of this final rule, we provide more detail about the efforts to refocus the measurement set. Improvements in clinical care can lead to better patient outcomes and, ultimately, higher Star Ratings.
                        <PRTPAGE P="17516"/>
                    </P>
                    <P>This shift also aligns with our focus on exploring ways to simplify and modify the Star Ratings methodology to further drive quality improvement. Rather than implement the change to the methodology to add the HEI reward and remove the historical reward factor, we instead proposed to keep the methodology consistent for now as we explore ways to simplify the methodology in the future. See section V.C., where we solicited comment on ways to simplify and modify the Star Ratings methodology to further drive quality improvement. Any such simplifications or modifications would be proposed in future rulemaking.  </P>
                    <P>Typically, CMS has proposed and finalized changes to the Star Ratings methodology in advance of the measurement year (which aligns with the rules for measure updates). However, this proposal would avoid the need for updates to the Star Ratings methodology, including a significant amount of programming, as well as updates to the Star Ratings technical documentation and data display in the HPMS, to reflect the temporary addition of the HEI reward and removal of the historical reward factor. Therefore, we proposed to not implement the HEI reward and to continue to implement the historical reward factor beginning with the 2027 Star Ratings. To remove the HEI reward and revert to the historical reward factor in the Star Ratings methodology, we proposed to remove the paragraphs at §§ 422.166(f)(3) and 423.186(f)(3), and to modify §§ 422.166(f)(1) and 423.186(f)(1) to remove “Through the 2026 Star Ratings.”</P>
                    <P>We invited public comment on this proposal and received several comments. A discussion of these comments, along with our responses follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported not implementing the HEI reward and adding back the historical reward factor in the 2027 Star Ratings. These commenters cited many reasons for support including:
                    </P>
                    <P>• perceived unfairness of the HEI reward enrollment thresholds and not all contracts being able to qualify for the HEI reward factor,</P>
                    <P>• perceived disadvantage to smaller, regional, or provider-owned plans in meeting enrollment thresholds compared to larger plans and the potential for anti-competitive dynamics as a result,</P>
                    <P>• perceived geographic bias against states that have not expanded Medicaid, because of dual eligibility being one of the main social risk factors included in the HEI,</P>
                    <P>• state policies in some states requiring D-SNP only contracts,</P>
                    <P>• some states have expanded or more generous Medicaid eligibility, while other states use a more limited definition of low income;</P>
                    <P>• continued recognition of consistent high performance on the Star Ratings through inclusion of the historical reward factor,</P>
                    <P>• inadequate understanding of methodology and performance outcomes associated with the HEI,</P>
                    <P>• request for predictability and stability of the Star Ratings and associated QBPs while CMS considers broader simplifications to the Star Ratings methodology,</P>
                    <P>• reduced administrative burden and complexity,</P>
                    <P>• exclusion of some groups with social risk factors such as rural enrollees,</P>
                    <P>• belief that the Star Ratings already incentivized plans to invest in improving health outcomes for enrollees with social risk factors,</P>
                    <P>• perceived ability for plans to better maintain supplemental benefits, have more resources for quality improvement initiatives and member services, and avoid increasing premiums and potential loss of coverage for some enrollees,</P>
                    <P>• perceived ability for plans to invest in prevention and management of chronic disease, and avoid placing additional strain on local healthcare systems,</P>
                    <P>• focus on overall quality for all members, and</P>
                    <P>• belief that improvements made among the populations included in the HEI will help overall Star Ratings performance.</P>
                    <P>Commenters also appreciated CMS's responsiveness to previous stakeholder feedback recommending not implementing the HEI reward and retaining the historical reward factor.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these commenters' support. We agree that not implementing the HEI reward and continuing the historical reward factor will result in more stability in the Star Ratings as we consider other changes to refocus the measure set and simplify the Star Ratings methodology. Additionally, we agree that any improvements made by contracts among populations included in the HEI reward will only help with performance on the Star Ratings more broadly, and such improvements should be made regardless of the Star Ratings methodology. We also feel it is important to be responsive to concerns raised by commenters as we have received feedback consistent with these comments over the past few years, including in response to the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule and the Advance Notice of Methodological Changes for Calendar Year (CY) 2026 for Medicare Advantage (MA) Capitation Rates and Part C and Part D Payment Policies.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters encouraged CMS to continue to look for ways to evaluate health equity and address social risk factors, cultural competency, and complex care needs in the Star Ratings. Commenters expressed that it is important to ensure vulnerable populations do not have barriers to care and to hold MA plans accountable for improving the care of vulnerable populations. A commenter stated that future proposals in this area should be supported by a clear policy rationale, transparent methodology, and robust stakeholder engagement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and will take them into consideration as we continue to consider future changes to the Star Ratings methodology. Any changes to the Star Ratings methodology will be proposed through the rulemaking process and would include a policy rationale and impact analysis of the proposed changes and an opportunity for stakeholder feedback.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters encouraged CMS to implement a one-year or multiple-year hold harmless policy starting with the 2027 Star Ratings where contracts would earn the better of the HEI reward and the historical reward factor, or a phased transition for removing the HEI reward.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS does not agree that such a hold harmless or phased transition is necessary, because any improvements contracts made among the populations included in the HEI are consistent with existing program goals and expectations to provide high quality care to all enrollees, including those that are dually eligible (DE), receive a low-income subsidy (LIS), or are disabled. Improvements made for these populations are not isolated to the HEI reward and will only help contracts in their performance on the Star Ratings more broadly. Contracts can earn five stars for the overall rating without either the HEI reward or the historical reward factor, and adding back the historical reward factor does not penalize contracts because it is an upside only reward. Additionally, implementing the 
                        <PRTPAGE P="17517"/>
                        HEI reward for only one year would be operationally complex and it would be potentially confusing for plans and beneficiaries for the methodology to change for just one year only to then revert back to the prior methodology. Additionally, all of this would happen at the same time that we are considering ways to simplify the methodology in the future.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters supported removing the HEI reward but did not support adding back the historical reward factor. A few other commenters suggested changes to the historical reward factor methodology. A commenter stated their belief that some measures included in the Star Ratings are flawed or may be influenced by administrative scale, vertical integration, or extensive outreach, and they argued for the historical reward factor to be sunset or narrowed. The commenter also stated that the reward factor favors plans with resources to optimize across a large measure set. A couple commenters believed the historical reward factor should not be based on variance in performance either because they believed this penalizes plans or because the ratings are dynamic in terms of the measure set and cut points. A commenter stated that the historical reward factor creates a cliff problem, because it includes cut offs for mean and variance, and further stated that CMS should develop a continuous reward that incentives excellent performance.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS will consider whether the historical reward factor should continue to be part of the Star Ratings in the future. However, performing consistently well across the full set of Star Ratings measures is an indicator of overall plan quality. This is consistent with the Star Ratings methodology as a whole, which emphasizes the importance of performing well across a variety of measures and showing improvements from the prior year. This is also reflected in how we set cut points each year based on industry performance, include the improvement measures, and include a measure set focused on a range of clinical care, outcome, and patient experience measures. Contracts should not focus on performing well on only a few measures.
                    </P>
                    <P>CMS also appreciates the suggestions for changes to the historical reward factor methodology. We are continuing to implement the historical reward factor under the current methodology at this time while we consider ways to simplify and modify the Star Ratings methodology to further drive quality improvement. Any changes to the historical reward factor methodology would need to be proposed through rulemaking.</P>
                    <P>Finally, we note that the historical reward factor is intended to reward consistent high performance across the Star Ratings measures. If a contract has high variance in performance, it will not receive a reward under the historical reward factor. Since the intent is to reward contracts with both high mean and high variance, cut offs are required to define high mean and high variance. CMS will take the comments related to a continuous reward factor into consideration; however, it would not be appropriate to assign a reward factor to all contracts regardless of the level and consistency of performance as this is inconsistent with the intent of the reward factor. We also note that no contracts are penalized by the reward factor because it is upside only.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters opposed removing the HEI reward and adding back the historical reward factor. Several commenters raised concerns about the timing of this proposal since it is not in advance of the measurement years for the HEI reward and historical reward factor for the 2027 Star Ratings. Commenters argued plans have made investments in improving care for populations included in the HEI reward. A couple of commenters noted negative financial implications for plans that invested in improving care as a result of the HEI reward. Other commenters raised concerns about removing incentives for plans to invest in care models, improved access, and high quality care for populations with high needs and social risk factors. A few commenters stated that plans are consistently denying patients needed care and the historical reward factor does not address this, and that therefore CMS should allow plans to move forward with efforts to implement the HEI. A commenter stated that it reasonably relied on the finalized HEI provisions in its planning.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS expects that plans will invest in improving care for all enrollees regardless of the Star Ratings and QBPs, including among enrollees that may have higher needs, such as the populations included in the HEI reward. This expectation is appropriate and consistent with MA statutory and regulatory requirements under section 1852 of the Social Security Act (the Act) and implementing regulations at 42 CFR part 422. Under section 1852(a)(1)(A) of the Act and § 422.101(a), MA organizations must furnish, with limited exceptions, all Medicare-covered benefits to enrollees. Section 1852(e) of the Act and § 422.152 further require MA organizations to maintain ongoing quality improvement programs designed to improve the quality of care provided to all enrollees, while section 1852(d) of the Act and § 422.112 require that MA organizations offering network-based coordinated care plans ensure that covered services are available and accessible to each enrolled individual with reasonable promptness and continuity of care. Collectively, these provisions establish that MA organizations must ensure equitable access to high-quality care for all enrollees, including dually eligible, low-income, and disabled beneficiaries. While CMS recognizes that plans have made investments to improve care for populations included in the HEI reward, these investments should not be viewed as contingent on the continuation of a specific reward mechanism, as improvements in care delivery, access, and outcomes for these populations are foundational to the MA program and remain important regardless of the Star Ratings structure. Improvements in performance among these populations will still contribute to higher performance on the Star Ratings by increasing measure-level scores even if the HEI reward is not implemented. Furthermore, as previously explained, maintaining the historical reward factor instead of implementing the HEI reward will incentivize improvement efforts on clinical care, outcomes, and patient experience for all enrollees, rather than incentivizing improvement for only certain populations. This consideration outweighs concerns about any potential reliance by plans on a future policy that had not yet been implemented. CMS expects that plans will work to provide high quality care to all enrollees and address instances where lower quality care may be provided to certain groups of enrollees. CMS expects this regardless of the Star Ratings methodology and incentives. Further, any improvements plans made in anticipation of a future HEI reward are for the benefit of enrollees and have the potential to boost the plan's Star Ratings performance, whether the HEI reward is included in the Star Ratings or not. While CMS acknowledges the commenter's statement regarding reliance on the inclusion of the HEI reward, CMS notes that plans remain responsible for meeting existing quality requirements and delivering appropriate care to all enrollees. Removal of the HEI provisions do not negate or undermine investments made to improve care, as such efforts continue to advance quality improvement goals and overall 
                        <PRTPAGE P="17518"/>
                        performance under the Star Ratings program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters stated that removing the HEI reward from the 2027 Star Ratings is impermissibly retroactive or a retroactive policy change.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS disagrees with the commenters' assertion that removing the HEI reward from the 2027 Star Ratings is retroactive. There are no retroactive effects on past Star Ratings. That is, all Star Ratings that have already been calculated stay exactly the same. This change only affects how Star Ratings will be calculated in the future, starting with the 2027 Star Ratings.
                    </P>
                    <P>Removing the HEI reward is a methodology change, not a measure specification change. At §§ 422.164(c) through (e) and 423.184(c) through (e), CMS lays out rules for adding, removing and updating measures and what needs to be finalized prior to the measurement year. In this case, we are not changing any measure specifications or the data plans must collect or report to CMS. We are updating how a reward will be calculated using existing data.</P>
                    <P>Pursuant to our authority under sections 1856(b) and 1860D-12 of the Act to adopt standards to carry out the Part C and D programs, CMS may update and improve the Star Ratings methodology over time. This methodology change is being made through the notice-and-comment rulemaking process, which means plans and other stakeholders were given advance notice, had the chance to submit comments, and are receiving a formal response in this preamble. CMS did take into consideration that some plans may have made investments based on the HEI reward being implemented; however, these investments should still be reflected in the measure scores and benefit contracts that showed significant improvement in the care that they provided to the populations includes in the HEI reward.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters stated that removing the HEI and continuing the historical reward factor risks allowing plans to improve on average while not improving or potentially worsening disparities in performance among high-need and socially disadvantaged populations. One commenter stated if CMS does not move forward with the HEI it should replace it with stratified reporting or weighting for dual eligible/LIS enrollees so that plans can't improve on average while neglecting high-need populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these suggestions for modifying the Star Ratings methodology to account for dual eligible/LIS enrollees and will take them into consideration as we consider future changes to the Star Ratings methodology. CMS expects that plans will work to provide high quality care to all enrollees and address instances where a lower quality of care may be provided to certain groups of enrollees. CMS expects this regardless of the Star Ratings methodology and incentives. Plans remain responsible for meeting existing quality requirements and delivering appropriate care to all enrollees.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters did not support rewarding historical performance through the historical reward factor. A commenter stated that tying incentives to historical performance may result in plans focusing on preserving existing metrics rather than making forward-looking investments in care coordination, preventive services, and community-based supports that are important for socially complex populations. The commenter further stated that without adjusting for social risk, the historical reward factor may dampen incentives for innovation among plans serving more complex populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These commenters may have misunderstood what we meant by historical reward factor. This reward factor does not rely on historical data. The use of historical was meant only to clarify that we were referring to the reward factor that has been in the Star Ratings since the 2009 Star Ratings and to distinguish this reward factor from the HEI reward. The historical reward factor uses the same, most recently available data as the rest of the Star Ratings calculations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated their belief that removing the HEI would perpetuate D-SNPs being penalized by the Star Ratings as a result of the impact of non-medical risk factors on enrollees' health. The commenter supported continuing the HEI or making changes to the Categorial Adjustment Index (CAI) for D-SNPs. The commenter also stated the Star Ratings do not adjust for member mix effectively.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and will take them into consideration as we continue to consider future changes to the Star Ratings methodology. CAHPS and HOS measures are adjusted for case mix, and the Part D medication adherence measures will be adjusted for case mix beginning with the 2028 Star Ratings. Other measures are included in the CAI, as described at §§ 422.166(f)(2) and 423.186(f)(2), which adjusts for within-contract performance differences associated with the percentages of beneficiaries that receive an LIS or are dual eligible or have disability status.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that the historical reward factor embeds disparate quality standards that favor more resourced, healthier populations. A couple of commenters also stated that removing the HEI reward and adding back the historical reward factor would mask gaps in care and remove the focus on fixing such gaps.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and will take them into consideration as we consider future changes to the Star Ratings methodology. CMS expects that plans will work to provide high quality care to all enrollees and address instances where a lower quality of care may be provided to certain groups of enrollees. CMS expects this regardless of the Star Ratings methodology and incentives. Plans remain responsible for meeting existing quality requirements and delivering appropriate care to all enrollees.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that without the HEI reward there is an unfair advantage for larger plans compared to smaller regional plans that results in perpetuating disparities and weakening incentives for plans that serve vulnerable populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments and will take them into consideration as we consider future changes to the Star Ratings methodology.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters stated that removing the HEI reward and adding back the reward factor is not consistent with the objective of shifting the Star Ratings toward outcome-based measures and away from operational incentives, because the reward factor is unrelated to improving clinical care, outcomes, or patient experience.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS disagrees that the reward factor is unrelated to clinical care, outcomes, and patient experience. The reward factor incentivizes high, consistent performance across all measures included in the Star Ratings, including those focused on clinical care, outcomes, and patient experience. As we consider how to simplify and modify the methodology and refocus the measure set, we will continue to focus on how to incentivize improvements in clinical care, outcomes, and patient experience.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter did not support adding back the historical reward factor, stating that it benefits a small subset of plans and does not recognize improvement because it is intended to only reward plans that have consistently high Star Ratings across multiple years. Another commenter 
                        <PRTPAGE P="17519"/>
                        stated that the reward factor may distort ratings by making them less responsive to changes in quality.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The reward factor is not based on multiple years of performance; it is based on consistent, high performance across measures in a single Star Ratings year. As such, the historical reward factor was in fact intended to incentivize improvement because plans must have high performance during the measurement year across the measure set in order to qualify.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the only rationale provided for removing the HEI reward is that it aligns with our focus on exploring ways to simplify and modify the Star Ratings methodology. A few commenters stated that simplicity should not be the key factor in performance measure selection or come at the expense of meaningful measurement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our rationale for removing the HEI reward, as stated in the Contract Year 2027 proposed rule, is to incentivize improvement efforts on clinical care, outcomes, and patient experience in line with our proposed changes to the measure set, rather than incentivizing improvement among certain populations. We also noted that we are exploring ways to simplify and modify the methodology, and we proposed to keep the methodology consistent for now while we conduct this exploration. Finally, as we explained in our responses to comments above, we are also being responsive to stakeholder feedback received over the past several years.
                    </P>
                    <P>When we consider changes to the methodology and measure set, the key factors we consider are consistent with the guiding principles for making enhancements and updates to the Star Ratings we stated in the Medicare Program; Contract Year 2019 Policy and Technical Changes to the Medicare Advantage, Medicare Cost Plan, Medicare Fee-for-Service, the Medicare Prescription Drug Benefit Programs, and the PACE Program final rule at 83 FR 16521. The MA and Part D Star Ratings are designed to align with CMS's Quality Strategy and to fairly, accurately, and transparently reflect plan quality and beneficiary experience, using reliable data and consensus-based measures that are stable over time and largely within plans' control. The system is intended to support public accountability, informed beneficiary choice, and quality improvement while minimizing unintended consequences and incorporating meaningful stakeholder input.</P>
                    <P>In addition, the Star Ratings methodology has become more complex over time, prompting us to consider ways to simplify and modify the methodology to maintain statistical rigor while making the methodology easier to understand and implement. Simplifying the methodology may also improve how well the Star Ratings incentivize quality improvement.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed our proposal to not implement the HEI reward and add back the historical reward factor, stating that policies should support, not penalize, clinicians and plans serving high-risk populations and should encourage investment in primary care, care coordination, and community-based interventions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates these comments; however, the historical reward factor is an upside-only reward that encourages consistent, high performance across Star Ratings measures and does not penalize plans or clinicians. CMS expects that plans will invest in improving care for all enrollees regardless of the Star Ratings and QBPs, including among enrollees that may have higher needs, such as the populations included in the HEI reward. This expectation is appropriate and consistent with MA statutory and regulatory requirements under section 1852 of the Social Security Act (the Act) and implementing regulations at 42 CFR part 422. Under section 1852(a)(1)(A) of the Act and § 422.101(a), MA organizations must furnish, with limited exceptions all Medicare-covered benefits to enrollees. Section 1852(e) of the Act and § 422.152 further require MA organizations to maintain ongoing quality improvement programs designed to improve the quality of care provided to all enrollees, while section 1852(d) of the Act and § 422.112 require that Medicare organizations offering network-based coordinated care plans ensure that covered services are available and accessible to each enrolled individual with reasonable promptness and continuity of care. Collectively, these provisions establish that MA organizations must ensure equitable access to high-quality care for all enrollees, including dually eligible, low-income, and disabled beneficiaries.
                    </P>
                    <P>After consideration of the public comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are removing the paragraphs at §§ 422.166(f)(3) and 423.186(f)(3) and modifying §§ 422.166(f)(1) and 423.186(f)(1) to remove “Through the 2026 Star Ratings.”</P>
                    <HD SOURCE="HD2">E. Plan Preview of Star Ratings (§§ 422.166(h)(2) and 423.186(h)(2))</HD>
                    <P>We proposed to add additional information about the data available to MA organizations and Part D sponsors during the plan preview periods before each Star Ratings release described at §§ 422.166(h)(2) and 423.186(h)(2). During the first plan preview, CMS expects Part C and D sponsors to closely review the methodology and their posted numeric data for each measure in HPMS prior to display on MPF. The second plan preview provides an opportunity for Part C and D sponsors to review any updates from the first plan preview and preliminary Star Ratings for each measure, domain, summary rating, and overall rating. When the Star Ratings methodology was first codified in the Contract Year 2019 final rule, we anticipated that the plan preview periods would continue to evolve and it was not necessary to codify the specific display content. As the plan previews have continued to evolve, CMS has added de-identified contract-level sample data for one of each type of measure needed for MA organizations and Part D sponsors to replicate the calculation of the measure-level cut points (that is, one CAHPS measure, one measure for Part C and one for Part D that use clustering, and any measures requiring a different type of calculation such as Complaints about the Plan). These data allow MA organizations and Part D sponsors to validate CMS's cut point calculations. The same cut point programming is used for all other measures as the sample measures, so de-identified contract-level data for only the sample measures are displayed in HPMS during the second plan preview. We proposed to codify our current practice of providing sample data for one of each type of measure during the second plan preview described at §§ 422.166(h)(2) and 423.186(h)(2).</P>
                    <P>We solicited comment on this proposal. In this section, we summarize the comments we received and provide our responses and final decisions.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A majority of commenters expressed support for CMS's proposal to codify its current practice of providing sample data during the plan preview periods. Some commenters stated that increased transparency will help plans more accurately review, validate, and understand their Star Ratings calculations, ultimately improving the integrity of Star Ratings and leading to improved quality assurance and better outcomes for beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the support for the proposed codification of 
                        <PRTPAGE P="17520"/>
                        our current practice of providing sample data for one measure of each type during the second plan preview period. CMS agrees this approach aligns with our goals of promoting accountability, improving the integrity of Star Ratings, and leading to better outcomes for beneficiaries.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended CMS expand the current practice of providing sample data for one of each measure type by providing sample data for all measures. They stated that without full access to the underlying data for all measures, plans cannot fully validate CMS's methodologies and calculations. Another commenter noted that much of the data already exists and asked that CMS provide a list on the HPMS Star Ratings website of all data sets available to plans and where to obtain them.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the Contract Year 2027 proposed rule, CMS provides de-identified contract-level sample data for one measure of each type so MA organizations and Part D sponsors can replicate calculation of the measure-level cut points. Because the same cut point programming is used for all measures of the same type, only de-identified contract-level data for the sample measures are needed to validate CMS's cut point methodology. Adding de-identified contract-level data for all measures would be burdensome to implement, and data provided during the plan preview are preliminary. The purpose of the plan preview is for Part C and D sponsors to closely review their own Star Ratings data, including preliminary Star Rating assignments. Contracts are not entitled to review other contracts' preliminary Star Ratings data before they are public. Adding a list of all data sets available to plans and where to obtain them may be easier to implement and CMS will take this suggestion under consideration as a future enhancement.
                    </P>
                    <P>After consideration of the public comments we received and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are finalizing §§ 422.166(h)(2) and 423.186(h)(2) as proposed without modification.</P>
                    <HD SOURCE="HD2">F. Impact of Proposed and Finalized Changes</HD>
                    <P>Simulations of the impact of removing the HEI reward, keeping the historical reward factor, and removing the 12 measures as proposed in section V.B. of the Contract Year 2027 proposed rule, using data from the 2025 Star Ratings (2022 and 2023 measurement years) but updating the measure set and measure weights for changes consistent with the 2026 Star Ratings (for example, reducing the weight of patient experience/complaints and access measures from 4 to 2) show most contracts (62 percent) would have no change in the overall rating. The overall rating would increase by a half star for 13 percent of contracts, would decrease by a half star for 25 percent of contracts, and would decrease by one star for one contract. Five percent of contracts would gain QBPs, and four percent of contracts would lose QBPs.</P>
                    <P>
                        As described in this final rule, we are adding and removing certain Star Ratings measures. The new measure entails moving an existing measure from the display page to Star Ratings, which would have no impact on plan burden. The measures being removed are either calculated from administrative data 
                        <SU>105</SU>
                        <FTREF/>
                         or would still be submitted by plan sponsors and, as such, there would be no decrease in plan burden. The finalized provisions would not change any respondent requirements or burden pertaining to any of CMS's Star Ratings related PRA packages, including: OMB control number 0938-0732 for CAHPS (CMS-R-246), OMB control number 0938-1028 for HEDIS (CMS-10219), and OMB control number 0938-1054 for Part C Reporting Requirements (CMS-10261). Since the provisions would not impose any new or revised information collection requirements or burden, we are not making changes under any of the aforementioned control numbers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             The following measures proposed for removal are calculated from administrative data: Plan Makes Timely Decisions about Appeals, Reviewing Appeals Decisions, Complaints about the Health/Drug Plan, Medicare Plan Finder Price Accuracy, Members Choosing to Leave the Plan.
                        </P>
                    </FTNT>
                    <P>We solicited feedback on the impact of these proposed changes.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS conduct an impact analysis that separates out SNP from non-SNP plans. The commenter also requested an analysis broken out by region and size of enrollment. The commenter stated that these analyses would ensure that the proposed changes do not inadvertently harm vulnerable populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the tables below, we break out the impacts for MA contracts by SNP-only contracts, partial SNP contracts (those with both SNP and non-SNP plans), and non-SNP contracts and by contract enrollment size. These tables show the impacts of the changes finalized in this final rule (
                        <E T="03">i.e.,</E>
                         removing 11 measures as finalized in section V.B. of this final rule, removing the HEI reward, and keeping the historical reward factor). We do not provide a breakout of the impacts by region because some contracts have broad service areas.
                    </P>
                    <GPH SPAN="3" DEEP="182">
                        <GID>ER06AP26.034</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="192">
                        <PRTPAGE P="17521"/>
                        <GID>ER06AP26.035</GID>
                    </GPH>
                    <P>After consideration of the public comments we received, and for the reasons outlined in the Contract Year 2027 proposed rule and our responses to comments, we are finalizing all Star Ratings proposals from the Contract Year 2027 proposed rule, except for the removal of the Diabetes Care—Eye Exam (Part C) measure. The impact of the finalized changes based on the simulations using data from the 2025 Star Ratings and accounting for changes implemented in the 2026 Star Ratings, as explained at the beginning of this section, show most contracts (63 percent) would have no change in their overall rating. The overall rating would increase by a half star for 13 percent of contracts, and would decrease by a half star for 24 percent of contracts. Four percent of contracts would gain QBPs, and three percent of contracts would lose QBPs.</P>
                    <HD SOURCE="HD2">G. Contract Consolidations (§§ 422.162(b)(3) and 423.182(b)(3))</HD>
                    <P>
                        In the Medicare and Medicaid Programs; Contract Year 2026 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly proposed rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on December 10, 2024, we proposed a technical clarification of existing policy at § 422.162(b)(3)(iv)(A)(2) and (B)(2) and § 423.182(b)(3)(ii)(A)(2) and (B)(2) to provide details about how the enrollment-weighted measure score is calculated when a consumed or surviving contract is missing data for a measure. In the first year of the consolidation when a measure score for a consumed or surviving contract is missing as a result of not having enough data to meet the measure technical specification or for a CAHPS measure having reliability less than 0.6, CMS proposed to treat this measure score as missing in the calculation of the enrollment-weighted measure score. Similarly, in the second year of the consolidation for all measures, except HEDIS, HOS, CAHPS, and call center measures, when a measure score for a consumed or surviving contract is missing as a result of not having enough data to meet the measure technical specification, CMS proposed to treat this measure score as missing in the calculation of the enrollment-weighted measure score. For § 423.182(b)(3)(ii)(A)(2) and (B)(2) we also removed reference to § 423.184(g)(1)(ii) since it was reserved in the Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024—Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE) final rule (pages 30639- 30642).
                    </P>
                    <P>We solicited comment on this proposal.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple commenters supported this technical clarification, noting that it is consistent with other similar approaches for calculations and will help prevent gaming. No commenters opposed the clarification.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank these commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter encouraged CMS to continue to take a uniform and consistent approach to data standards for contract consolidations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank this commenter for their support of a uniform and consistent approach to data standards for consolidations and find that the current methodology for consolidations and the proposed technical clarification align with this approach.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested clarification that CMS will exclude missing data from the weighted average calculation, noting that some software will give missing values as the final output when missing data are included in calculations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS confirms that missing data would be excluded consistent with the proposed technical clarification.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested CMS assess potential impacts and confirm the clarification accurately reflects plan performance and quality of care for impacted populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Excluding missing data from the calculation of measure scores for the surviving contracts of consolidations for measures with low reliability or that do not have enough data to meet the measure technical specifications more accurately reflects plan performance and the quality of care provided.
                    </P>
                    <P>After consideration of the comments we received and for the reasons outlined in the Contract Year 2026 proposed rule and our responses to comments, we are finalizing the technical clarification at §§ 422.162(b)(3) and 423.182(b)(3). As this is a technical clarification, CMS is applying it immediately on the effective date of the final rule and to the 2027 Star Ratings.  </P>
                    <HD SOURCE="HD2">A. Model of Care (MOC) Off-Cycle Submission Window (42 CFR 422.101)</HD>
                    <P>
                        Congress first authorized special needs plans (SNP) through the enactment of the Medicare Prescription Drug, Improvement, and Modernization 
                        <PRTPAGE P="17522"/>
                        Act of 2003 (Pub. L. 108-173). The law authorized CMS to contract with Medicare Advantage (MA) coordinated care plans that are specifically designed to provide targeted care to individuals with special needs. Section 1859(f)(5)(A) of the Act, as added by section 164 of the Medicare Improvements for Patients and Providers Act (
                        <E T="03">Pub. L. 110-275</E>
                        ), imposes specific care management requirements for all SNPs effective January 1, 2010. As a result, all SNPs are required to implement care management requirements which have two explicit components: a National Committee for Quality Assurance (NCQA) approved, evidence-based model of care (MOC) and a series of care management services.
                        <SU>106</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             For more discussion of the history of SNPs, please see Chapter 16B of the Medicare Managed Care Manual (MMCM).
                        </P>
                    </FTNT>
                    <P>All SNPs must submit their MOCs to CMS for NCQA evaluation and approval and an MA organization sponsoring multiple SNPs must develop a separate MOC to meet the needs of the targeted population for each SNP type it offers as required at §§ 422.4(a)(1)(iv), 422.101(f)(3)(i), and 422.152(g). The NCQA MOC evaluation and approval process scores each of the clinical and non-clinical elements of the MOC. The Institutional Special Needs Plan (I-SNPs) and Dual-Eligible Special Needs Plan (D-SNPs) MOCs that receive a passing score from NCQA are then approved for one-, two-, or three-year periods as set forth at § 422.101(f)(3)(iii). A Chronic Condition Special Needs Plan (C-SNP) MOC that receives a passing score is approved for one year as required by section 1859(f)(5)(B)(iv) of the Act. As the MOC approval periods end, SNPs submit new MOCs to CMS for NCQA evaluation and approval during an annual renewal MOC submission window. This ensures that all operating SNPs have a current, NCQA approved, MOC in place.</P>
                    <P>CMS has acknowledged in the past that to more effectively address the specific needs of its enrollees, a SNP may need to modify its processes and strategies for providing care during its approved MOC timeframe. A SNP that seeks to revise a MOC before the end of the MOC approval period may do so between June 1st and November 30th of each calendar year via the “off-cycle MOC submission process” outlined at § 422.101(f)(3)(iv). A D-SNP or I-SNP that decides to make revisions to their existing approved MOC may submit a summary of their off-cycle MOC changes, along with the red-lined MOC, in the Health Plan Management System (HPMS) Model of Care module for NCQA review and approval. The off-cycle submission requirements apply to substantial changes in policies or procedures as described at § 422.101(f)(3)(iv)(B)(1) and other revisions identified at § 422.101(f)(3)(iv)(B)(2) to (5). These types of MOC changes are at the discretion of the applicable MA organization offering the SNP, and it is the responsibility of the MA organization to notify CMS of revisions and electronically submit their summary of changes to their MOC in HPMS for review and approval.</P>
                    <P>Since the beginning of the MOC approval process, CMS has developed, issued, and updated guidance on the MOC to support plan performance and assist in improved health outcomes. CMS had previously required initial and renewal MOCs to be submitted mid-February of the preceding plan contract year, aligning with the MA application deadline. However, as announced in an HPMS email titled “Contract Year 2027 Model of Care Submission Timeline Updates” on September 3, 2025, CMS has moved the initial and renewal MOC submission deadline to the Friday before the first Monday of June, starting with the contract year (CY) 2027 MOC submission period. The new MOC submission deadline and subsequent NCQA evaluation overlap with the current off-cycle MOC submission window. To accommodate the CY 2027 MOC submission deadline change and ensuing operational considerations both for NCQA and CMS's HPMS, a new timeline for the off-cycle submission process is needed. As such, CMS proposed that for CY 2027 and subsequent years, D-SNPs and I-SNPs seeking to revise their NCQA-approved MOC during the MOC approval period must submit updates and corrections between January 1st and March 31st and October 1st and December 31st of each calendar year. This will functionally provide SNPs with two separate windows of opportunity to submit off-cycle MOC changes each year. Of note, SNPs currently have a six-month window to update or correct their MOCs; this new proposed timeline will split that period to accommodate the operational needs of CMS and NCQA as staff review initial and annual MOC submissions.</P>
                    <P>CMS expects there will be no change in the estimated burden from this changed timeline for SNPs submitting off-cycle MOC changes. Additionally, there will be no new collection of information for this rule, only maintenance of past expectations around the off-cycle MOC process.</P>
                    <P>CMS invited public comment on this proposal and received several comments in support. CMS received no comments opposing this proposal, but several commentors offered support with suggested modifications. The comments and responses are as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported CMS' proposed change, but requested CMS continue to look at greater alignment with state Medicaid contracting windows where possible.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenters' support of this proposed change and agrees that the timing of MOC deadlines should align with state Medicaid contracting windows when possible. The shift in timing of the annual renewal and initial MOC submission process reflects feedback CMS has received over the years from plans and state Medicaid agencies. In some instances, CMS is restricted by the operational practicalities related to NCQA's review and approval of SNP MOCs in relation to finalizing all MA plan requirements for the upcoming contract year. However, CMS will continue to review the MOC submission process and its impact on plans and state partners.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the proposal but suggested keeping the SNP MOC submission portal open year-round to give SNPs more time to make corrections and submit changes. They noted that this is particularly necessary when there are significant policy changes or mandates made at the state level. Commenters stated that an enhanced open portal timing would further reduce burden since plans are prohibited from making care management and some operational changes until NCQA has approved the SNP's off-cycle MOC submission. Another noted that the window should remain open from October 1st to March 31st of the next contract year.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenter's concerns and have taken plan burden into consideration when developing this proposal. As noted in the previous comment response, however, CMS is limited by operational considerations specific to NCQA's review process in relation to finalizing all MA plan requirements for the upcoming contract year. While this proposal represents the best balance of all these considerations, CMS will continue to review the MOC review process for future refinement opportunities.
                    </P>
                    <P>
                        Regarding the potential extension of the off-cycle window from October 1st to March 31st of the next contract year, this proposal is essentially providing the opportunity the commenter is 
                        <PRTPAGE P="17523"/>
                        seeking. The text of the proposal is written to align with current regulatory practices in mind as many of our current regulations are consistent with a contract year framework, which is why CMS framed the proposal around two separate portions of the same contract year.
                    </P>
                    <P>After reviewing and responding to all comments, CMS is finalizing revisions to § 422.101(f)(3)(iv)(B) and (G) without modification.  </P>
                    <HD SOURCE="HD2">B. Passive Enrollment by CMS (§ 422.60)</HD>
                    <P>Individuals who are dually eligible for both Medicare and Medicaid typically face significant challenges in navigating the two programs, which include separate or overlapping benefits and administrative processes. Fragmentation between the two programs can result in a lack of coordination for care delivery, potentially resulting in unnecessary, duplicative, or missed services. One method for overcoming this challenge is through integrated care, which provides dually eligible individuals with the full array of Medicaid and Medicare benefits for which they are eligible through a single delivery system, thereby improving quality of care, beneficiary satisfaction, care coordination, and reducing administrative burden.</P>
                    <P>Integrated care options are increasingly available for dually eligible individuals, which include a variety of integrated D-SNPs. Integrated D-SNPs can provide greater integration of Medicare and Medicaid services and experiences than enrollees would otherwise receive in other MA plans or Original Medicare, particularly when an individual is enrolled in both a D-SNP and Medicaid managed care organization (MCO) offered by the same organization. When referring to integrated D-SNPs, we are referring to: applicable integrated plans (AIPs), which include fully integrated dual eligible special needs plans (FIDE SNPs), many highly integrated dual eligible special needs plans (HIDE SNPs), and a small subset of coordination-only D-SNPs. These D- SNP types meet higher standards of integration, quality, and performance benchmarks, and for AIPs, exclusively aligned enrollment (when enrollment in a parent organization's D-SNP is limited to individuals with aligned enrollment), which we believe is a critical part of improving experiences and outcomes for dually eligible individuals. These D-SNP types more meaningfully integrate Medicare and Medicaid services and administrative processes (such as unified appeals and grievances) than coordination-only D-SNPs that are not also AIPs.</P>
                    <P>While enrollment in integrated care options continues to grow, there are instances in which enrollees may face disruptions in coverage in integrated care plans. These disruptions can result from numerous factors, including market forces that impact the availability of integrated D-SNPs and State re-procurements of affiliated Medicaid MCOs. Such disruptions can result in enrollees being enrolled with two separate health plan organizations for their Medicaid and Medicare benefits, thereby losing the benefits of integration achieved when the same health plan organization offers both benefit packages. In an effort to protect the continuity of integrated care for dually eligible individuals, in the April 2018 final rule (83 FR 16502), we finalized a limited expansion of our regulatory authority to initiate passive enrollment for certain dually eligible individuals in instances where integrated care coverage would otherwise be disrupted.</P>
                    <P>Section 1851(c)(1) of the Act authorizes us to develop mechanisms for enrollees to elect MA enrollment, and in the April 2018 final rule (83 FR 16502), we amended the regulation at § 422.60(g) by adding § 422.60(g)(1)(iii) and (g)(2) to allow passive enrollment for full-benefit dually eligible enrollees from a non-renewing integrated D-SNP into another comparable plan. A beneficiary who is offered a passive enrollment is deemed to have elected enrollment in the designated plan if he or she does not elect to receive Medicare coverage in another way.</P>
                    <P>In the April 2018 final rule, we finalized language authorizing CMS to passively enroll certain dually eligible individuals currently enrolled in an integrated D-SNP into another integrated D-SNP, after consulting with the State Medicaid agency that contracts with the D-SNP, when CMS determines that the passive enrollment will promote continuity of care and integrated care under § 422.60(g)(1)(iii). We also finalized, under § 422.60(g)(2), requirements an MA plan would have to meet to qualify to receive passive enrollments under paragraph (g)(1)(iii). However, in multiple situations where we have attempted to implement these requirements, we have encountered difficulty with receiving integrated D-SNPs meeting the requirement in § 422.60(g)(2)(ii) that they have provider networks and facility networks that are substantially similar to those of the relinquishing integrated D-SNP. In our attempts to utilize passive enrollment, we found that while prospective receiving integrated D-SNPs had Medicare provider and facility networks that met the MA network adequacy criteria at § 422.116, these networks weren't substantially similar to the provider and facility networks in the relinquishing integrated D-SNPs.</P>
                    <P>
                        We acknowledge that the substantially similar provider and facility networks requirement that is used to assess receiving integrated D-SNPs is undefined in regulation. On August 1, 2018, we published a Health Plan Management System (HPMS) memo (hereafter referred to as August 2018 HPMS memo) that provided technical guidance on how we would assess for substantially similar networks.
                        <SU>107</SU>
                        <FTREF/>
                         Even with the additional operational guidance, a network comparison between the relinquishing and receiving plans did not result in networks that we could consider substantially similar. As such, we have not been able to implement passive enrollment as outlined in § 422.60(g).
                    </P>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             CMS, HPMS Memorandum titled “Guidance on the Process for Implementing Passive Enrollment Flexibilities to Protect Continuity of Integrated Care for Dual Eligible Beneficiaries”, August 2018. Retrieved from: 
                            <E T="03">https://www.cms.gov/research-statistics-data-and-systems/computer-data-and-systems/hpms/hpms-memos-archive-weekly-items/syshpms-memo-2018-week1-aug-1-3</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        We continue to find value in the concept of allowing passive enrollment for full-benefit dually eligible enrollees from a non-renewing or terminating integrated D-SNP to another comparable integrated D-SNP, and we continue to hear from States interested in using this provision. In order to operationalize this function, in the Contract Year 2027 proposed rule, we proposed to amend § 422.60(g)(2)(ii) to remove the requirement that the receiving integrated D-SNPs have substantially similar networks to the relinquishing integrated D-SNPs and, instead, require receiving integrated D-SNPs to provide continuity of care for all incoming enrollees for a minimum of 120 days. Specifically, we proposed to replace the current language in § 422.60(g)(2)(ii) with the requirement that a receiving integrated D-SNP provide continuity of care for all incoming enrollees that complies with § 422.112(b)(8)(i)(B), except that the minimum transition period would be 120 days. We noted that this proposed requirement would not affect a receiving integrated D-SNP's requirement to meet network adequacy standards per § 422.116, or potential compliance actions that may result from a failure to meet those requirements. We also proposed to amend § 422.60(g)(2)(vi) to specify that an integrated D-SNP receiving passive enrollment must have the care coordinator staffing capacity to 
                        <PRTPAGE P="17524"/>
                        receive dually eligible enrollees through passive enrollment. We expect this coordinator staffing capacity to be sufficient to conduct required enrollee onboarding activities such as health risk assessments (HRAs) and care plans and meet ongoing D-SNP care coordination requirements, including those outlined at § 422.107(c). Lastly, in an effort to use consistent and accurate language throughout our processes and documentation, we proposed to amend § 422.60(g)(2)(i) to instead describe the MA plans that can receive passive enrollment as plans that operate as an applicable integrated plan (AIP) as described at § 422.561.
                    </P>
                    <P>We proposed to amend § 422.60(g)(2)(ii) to require that the plan receiving passive enrollment provide continuity of care to all incoming enrollees for 120 days because we believe that this length of time for continuity of care would address the issue that we attempted to address at 83 FR 16504 in the April 2018 final rule, namely that the provider network comparability analysis would minimize the number of enrollees whose provider relationships are disrupted as a result of passive enrollment and encourage retention following enrollees' transition to a new integrated D-SNP, while creating an approach that can be more feasibly implemented than the current substantially similar network requirement.</P>
                    <P>We specifically tied the proposed amendment in § 422.60(g)(2)(ii) to § 422.112(b)(8)(i)(B), which currently requires MA coordinated care plans to provide a minimum 90-day transition period for basic benefits when an enrollee currently undergoing treatment switches to a new MA plan. This provision requires that for a minimum of 90 days, when an enrollee switches to a new MA coordinated care plan, any active course of treatment must not be subject to any prior authorization requirements. A more detailed discussion of this proposal is available at 90 FR 54971 of the proposed rule.</P>
                    <P>We believe that the requirements captured in § 422.112(b)(8)(i)(B) are consistent with the intention behind passive enrollment at § 422.60(g), and as such, we proposed to apply the requirements at § 422.112(b)(8) to § 422.60(g)(2)(ii), except that continuity of care would be applicable for 120 days as opposed to 90 days, as is currently required at § 422.112(b)(8). This proposal was an attempt to balance the current 90-day requirement applicable to all coordinated care plans with the intention behind the current regulation at § 422.60(g) to minimize the number of enrollees whose provider relationships are disrupted as a result of passive enrollment.</P>
                    <P>Additionally, we would like to note that in our proposed revision of § 422.60(g)(2)(ii), we also proposed to remove the language that requires the receiving plan to have substantially similar Medicare and Medicaid-covered benefits as the relinquishing integrated D-SNP. Integration levels are defined both in statute and in regulation at §§ 422.2 and 422.107(d), and Medicare Part A, B, and D benefits and Medicaid benefits do not tend to differ across D-SNPs with the same integration level within a State. As such, we do not believe that a specific assessment for substantially similar coverage of Medicare and Medicaid covered benefits is required. In such a situation where passive enrollment is implemented, we believe that an assessment of level of integration between the relinquishing and receiving integrated D-SNPs would suffice.</P>
                    <P>Our continued goal with passive enrollment is to ensure that the integrated D-SNPs receiving passive enrollments provide high-quality care, coverage and administration of benefits. Passive enrollments benefit a plan by providing an enrollee and associated payments without the plan having to successfully market to the enrollee. Thus, we continue to believe that it is important that these enrollments are limited to plans that have demonstrated commitment to quality and are able to provide longer continuity of care to minimize service disruption for receiving dually eligible enrollees, who have complex and unique care needs. We did not propose any other changes to § 422.60(g) or the process; receiving plans would still be held to all other standards set forth at § 422.60(g)(2). Similarly, we did not propose changes to the current regulation at § 422.60(g)(4) regarding beneficiary notification requirements. Further, passively enrolled enrollees would still have the opportunity to opt out of the receiving plan, and § 422.60(g)(5), which describes an enrollee's access to the special election period at § 423.38(c)(10), would still be in effect.</P>
                    <P>We welcomed comments on the changes we proposed at § 422.60(g)(2)(i) and (ii). Similarly, we solicited comment on our proposed revision to § 422.60(g)(2)(vi) which would require that an integrated D-SNP receiving passive enrollment have the care coordinator staffing capacity to receive dually eligible enrollees through passive enrollment. Our proposal did not define a minimum staffing capacity threshold in order to give integrated D-SNPs flexibility in implementing this proposed change. We invited comment on the feasibility of this proposed requirement and requested suggestions for potential refinement.</P>
                    <P>We received the following comments on this proposal and respond to them:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including MedPAC and MACPAC, generally supported the proposal to remove the requirement for the receiving D-SNP and the relinquishing D-SNP to have substantially similar networks and instead replace it with a period of continuity of care of 120 days as well as the requirement that the receiving D-SNP have care coordinator staffing capacity to receive dually eligible enrollees through passive enrollment. The commenters noted that these changes would allow for the passive enrollment option to be more readily used and facilitate continued enrollment in an integrated plan for eligible beneficiaries. Some commenters also noted that the proposed changes to passive enrollment would safeguard integrated coverage for dually eligible individuals and would allow passive enrollment to function as intended without imposing unrealistic alignment standards on States with complex delivery systems. A few commenters mentioned the effect of market changes and State re-procurement decisions on the landscape of integrated care and noted that passive enrollment between a non-renewing integrated D-SNP and a comparable D-SNP can help increase enrollment and retention in integrated D-SNPs.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the comments and support for the proposed changes to the passive enrollment process. We agree with the commenters that these changes will help streamline the passive enrollment process and help retain enrollment in integrated D-SNPs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters opposed our proposal based on their assertion that CMS's proposal to remove the requirement for substantially similar networks due to not being able to implement such a requirement is an indication that passive enrollment should not be used, and that a slightly extended period for continuity of care does not make up for a future inability to see chosen providers. These commenters further reasoned that allowing passive enrollment could lead to override of an individual's plan enrollment decision, and that the noticing provided to enrollees alerting them that they are being passively enrolled in a new D-SNP with the option to opt out is not enough. A commenter also opined that there is no research to provide evidence that D-SNPs provide improvement in care 
                        <PRTPAGE P="17525"/>
                        coordination for dually eligible enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge the commenters' perspectives on the proposal. We would like to reiterate that passive enrollment is an opportunity for enrollees in an integrated D-SNP to transition to another integrated D-SNP when their original plan is non-renewing or terminating. As we stated in preamble to the proposed rule (90 FR 54971) and as set forth in § 422.60(g)(1)(iii) and described in the April 2018 final rule, and in the August 2018 HPMS memo 
                        <SU>108</SU>
                         that provided further technical assistance to D-SNPs on passive enrollment, such a transition would only occur after consulting with the State Medicaid agency that contracts with the D-SNP and when CMS determines that the passive enrollment will promote continuity of care and integrated care. Under the notice requirements at § 422.60(g)(4), enrollees who are passively enrolled will receive a first notice from the integrated D-SNP receiving enrollment at least 60 days before the first day of enrollment in the receiving D-SNP, and a second notice at least 30 days before the first day of enrollment in the receiving D-SNP. Each of these notices will alert enrollees that they have the opportunity to opt out of the enrollment into the receiving integrated D-SNP. In the Contact Year 2027 proposed rule, we did not propose amendments to § 422.60(g)(5), which describes an enrollee's access to the special enrollment period (SEP) at § 423.38(c)(10). We stated that § 422.60(g)(5) would still be in effect. As such, this SEP would also be accessible to enrollees who are interested in switching their coverage (90 FR 54972). Enrollees in D-SNPs also have access to the one-time-per month SEP for dually eligible individuals and other LIS eligible individuals to elect Original Medicare and a standalone PDP and the integrated care SEP which allows full-benefit dually eligible individuals to elect an integrated D-SNP on a monthly basis. We believe that the passive enrollment mechanism, coupled with ample opportunity for an enrollee to switch coverage, does not amount to override of enrollee decision making.
                    </P>
                    <P>Further, since the inception of the passive enrollment process at § 422.60(g)(1)(iii), CMS's decision to implement passive enrollment has been discretionary, not mandatory, and subject to a deliberative process. As we noted in the August 2018 HPMS memo, in order to implement D-SNP passive enrollment under § 422.60(g)(1)(iii), CMS must consult with the applicable State, CMS must determine that passive enrollment will promote integrated care and continuity of care, and the receiving integrated D-SNP must meet certain requirements. Though our proposal will amend some of the requirements, we did not intend to, nor do we believe that we proposed an amendment to the passive enrollment process that will, dilute our goal to promote integration and continuity of care. We continue to believe that integrated D-SNPs can provide greater integration of Medicare and Medicaid services and experiences than enrollees would otherwise receive in other MA plans or Original Medicare, particularly when an individual is enrolled in both a D-SNP and Medicaid managed care organization (MCO) offered by the same organization.</P>
                    <P>
                        Although research has not yet uniformly shown an advantage for dually eligible individuals enrolling in D-SNPs with Medicare and Medicaid integration, preliminary evidence suggests that dually eligible individuals enrolled in integrated plans, on average, experience, reduced emergency department and inpatient hospital admissions, fewer long-term nursing facility stays, greater use of patient care, and slightly better experience and clinical outcomes than those in non-integrated plans.
                        <SU>109</SU>
                        <FTREF/>
                         In their March 2024 Report to Congress, MedPAC highlighted a HEDIS measure to exemplify care coordination. MedPAC's review of HEDIS data on follow-up after emergency department visits for people with multiple high risk chronic conditions showed that coordination-only D-SNPs, HIDE SNPs and FIDE SNPs performed better than other MA plans for enrollees ages 65 years and older and HIDE SNPs and FIDE SNPs performed better than other MA plans for enrollees ages 18-64 years.
                        <SU>110</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             Roberts ET, Duggan C, Stein R, Jonnadula S, Johnston KJ, Figueroa JF. Quality, spending, utilization, and outcomes among dual-eligible Medicare-Medicaid beneficiaries in integrated care programs: a systematic review. JAMA Health Forum. July 2024. Available from: 
                            <E T="03">https://jamanetwork.com/journals/jama-health-forum/fullarticle/2821202;</E>
                             Feng Z, Wang J, Gadaska A, Knowles M, Haber S, Ingber M, Grouverman, V. Comparing Outcomes for Dual Eligible Beneficiaries in Integrated Care: Final Report, September 2021. Available from: 
                            <E T="03">https://aspe.hhs.gov/sites/default/files/documents/9739cab65ad0221a66ebe45463d10d37/dual-eligible-beneficiaries-integrated-care.pdf;</E>
                             and 
                            <E T="03">https://www.macpac.gov/wp-content/uploads/2019/07/Evaluations-of-Integrated-Care-Models-for-Dually-Eligible-Beneficiaries-Key-Findings-and-Research-Gaps.pdf;</E>
                             and MACPAC Evaluations of Integrated Care Models for Dually Eligible Beneficiaries: Key Findings and Research Gaps, August 2020. Available from: 
                            <E T="03">https://www.macpac.gov/wp-content/uploads/2019/07/Evaluations-of-Integrated-Care-Models-for-Dually-Eligible-Beneficiaries-Key-Findings-and-Research-Gaps.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             MedPAC. Report to Congress: Medicare Payment Policy, Chapter 14, March 2024. Retrieved from: 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2024/03/Mar24_Ch14_MedPAC_Report_To_Congress_SEC.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         We received many comments supporting our proposal to amend § 422.60(g)(2)(ii) to require that the D-SNP receiving passive enrollment provide continuity of care to all incoming enrollees for 120 days, with some commenters noting that the proposed amendment would reduce the risk of disrupting patient-provider relationships and help ensure that enrollees continue to receive essential medications and treatments during their plan transition.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received some comments opposing our proposal to amend § 422.60(g)(2)(ii) to require that the D-SNP receiving passive enrollment provide continuity of care to all incoming enrollees for 120 days. The commenters cited State requirements, and that 120 days would be operationally difficult to achieve. Some of these commenters suggested changing the 120-day proposed requirement to a requirement of 90-to-120 day transition period, suggesting that a period of 90 to 120 days would enable receiving D-SNPs to work with transitioning enrollees without an across-the-board minimum exposure for non-contracted and potentially unmanaged care. A commenter opined that an additional 30-day requirement of continuity of care beyond the currently required 90 days per § 422.112(b)(8)(i)(B) could result in unaccounted for cost trends for the receiving D-SNP. Some commenters requested that CMS further define expectations related to continuity of care and provide clear guidance on how D-SNPs should operationalize continuity requirements, especially in States with multiple Medicaid product types to help ensure that passive enrollment policies advance integration goals without causing confusion or disruption for beneficiaries. For example, one commenter questioned whether, during the continuity of care period, D-SNPs receiving passive enrollment would be required to enter into single case agreements with providers unwilling to join their network.
                    </P>
                    <P>
                        Commenters further requested that CMS remind all MA plans of their obligations regarding continuity of care under this policy and take enforcement action when MA plans fail to comply. Finally, some commenters suggested that CMS consider strengthening the continuity of care policy by mandating a requirement for the relinquishing D-SNP to provide timely exchange of 
                        <PRTPAGE P="17526"/>
                        clinical and care management information to the receiving D-SNP, including current treatment plans, authorizations, medications, etc.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We welcome these perspectives. We remind commenters that our proposal relates to passive enrollment under a narrow set of circumstances when a State has a non-renewing or terminating integrated D-SNP with full-benefit dually eligible enrollees and seeks to transition these enrollees to another comparable integrated D-SNP with the goal of maintaining integrated coverage. Furthermore, we would like to make the distinction that our proposed amendment to the passive enrollment process at § 422.60(g)(2) is specific to D-SNPs and would not affect enrollees in other types of MA plans, including I-SNPs. We understand that under the Financial Alignment Initiative (FAI), full-benefit dually eligible individuals in some States were able to be passively enrolled into Medicare-Medicaid Plans (MMPs) from different types of plans. That authority was specific to MMPs under the FAI and is separate from the existing D-SNP passive enrollment regulation at § 422.60(g)(2), which we proposed to amend. Section 422.60(g)(2) only applies to integrated D-SNPs where the D-SNP is non-renewing or terminating and the State affirms its interest in transitioning these enrollees to another comparable integrated D-SNP with the goal of maintaining integrated coverage.
                    </P>
                    <P>Given that the integrated D-SNP is terminating or non-renewing, there is no opportunity for an enrollee to remain in that D-SNP. We defer to D-SNPs receiving passive enrollees on approaches to contract with providers during the continuity of care period, but a single case agreement would be one such option. We appreciate the commenters' perspectives on potential unforeseen cost trends associated with the proposed 120-day continuity of care requirement. In the August 2018 HPMS memo, we stated that the applicable MA plan must meet certain requirements related to, among other things, coverage, cost, and operational capacity, and agree to receive passive enrollments. If a potential receiving D-SNP does not believe it is able to meet these requirements, it is under no obligation to accept passive enrollment if presented the option.</P>
                    <P>As stated earlier in this section, enrollees subject to passive enrollment would receive notices 60 days and 30 days in advance of the effective date of enrollment in the receiving integrated D-SNP, providing notice of their ability to opt out of the passive enrollment and choose different coverage. Further, as we discussed earlier in this preamble and in the preamble to the Contract Year 2027 proposed rule, we did not propose amendments to § 422.60(g)(5), which describes an enrollee's access to the SEP at § 423.38(c)(10). As such, this SEP would also be accessible to enrollees who are interested in switching their coverage (90 FR 54972). Enrollees in integrated D-SNPs also have access to the one-time-per month SEP for dually eligible individuals and other LIS eligible individuals to elect Original Medicare and a standalone PDP and the integrated care SEP, which allows full-benefit dually eligible individuals to elect an integrated D-SNP on a monthly basis. An individual passively enrolled has ample opportunities to make a different election should they choose not to enroll or remain enrolled in the receiving integrated D-SNP. Any integrated D-SNP that agrees to accept passively enrolled full-benefit dually eligible individuals will be required to comply with the continuity of care requirements.  </P>
                    <P>
                        Finally, we appreciate the comment regarding mandating a requirement to provide timely exchange of clinical and care management information. Such a requirement does not currently exist and was not proposed in the Contract Year 2027 proposed rule, but we note that § 
                        <E T="03">422.119</E>
                         requires an MA plan to implement and maintain a standards-based application programming interface (API) that—with enrollee approval and direction—allows third party applications to retrieve certain information as specified in § 422.119(b). Additionally, in some instances, State Medicaid agency contracts (SMACs) may require an exchange of information as well. While we are not finalizing any additional requirements under this rule, we may take this comment into consideration in future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested that CMS extend the proposed continuity of care provisions beyond 120 days for residents of nursing facilities and assisted living communities, or other high-need groups.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the request for lengthening the proposed continuity of care requirement to beyond 120 days, we believe increasing the existing 90-day continuity of care requirement to 120 days allows D-SNPs receiving passive enrollment sufficient time to maintain an existing course of treatment and educate providers outside of their networks about joining the D-SNP provider network.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received some comments that supported our proposal to remove the requirement that receiving integrated D-SNPs meet the requirement in current § 422.60(g)(2)(ii) to have provider networks and facility networks that are substantially similar to those of the relinquishing integrated D-SNP. Some commenters noted that removing the substantially similar network requirement would remove the imposition of unrealistic alignment standards on complex delivery systems, and that this change represents a practical, beneficiary-centered way to maintain continuity of enrollment in integrated care when the D-SNP landscape changes within a State, minimizing disruptions and preserving the benefits of aligned Medicare-Medicaid coverage and care coordination.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of this proposed revision. We agree that the proposed changes to § 422.60(g)(2)(ii) will allow D-SNPs to use passive enrollment as intended and safeguard integrated coverage for full-benefit dually eligible individuals when their existing D-SNP terminates or does not renew, and CMS determines, after consulting the State Medicaid agency, that passive enrollment will promote integrated care and continuity of care.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Similarly, we received some comments that opposed our proposal to remove the requirement that receiving integrated D-SNPs have provider and facility networks that are substantially similar to those of the relinquishing integrated D-SNP. A few commenters encouraged CMS to consider how passive enrollment may cause enrollees to lose access to their existing provider networks, asserting that the value of passive enrollments does not outweigh the value of beneficiary access to the facility network they chose, and that enrollee choice should be maximized during any passive enrollment. Another commenter expressed how this provision may affect a State, noting that a State may have focused on aligning the Medicaid and Medicare provider networks in a way that ensures dually eligible enrollees have continued access to services as they transition from Medicaid into Medicare and that the provider networks are fully available to the populations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' perspectives on this issue. Our intention in proposing changes to the D-SNP passive enrollment process is to provide a process by which full-benefit dually eligible enrollees are able to maintain access to integrated care. As passive enrollment would only be used in situations where an enrollee's 
                        <PRTPAGE P="17527"/>
                        integrated D-SNP is terminating or non-renewing, and considering the required opt out language and the SEPs that were discussed previously in this section, we believe that those enrollees who wish to select their enrollment based on specific providers or facilities will still be able to do so.
                    </P>
                    <P>We note that more States are including provisions in their SMACs that address alignment of Medicaid and Medicare provider networks between a Medicaid MCO and its affiliated D-SNP. This alignment of provider networks is distinct from the existing substantially similar network language that we proposed to remove at § 422.60 and replace with an extended continuity of care period. The substantially similar network requirement sought to compare networks between different MA organizations offering integrated D-SNPs whereas the alignment the commenter referenced is specific to the provider network between affiliated entities. As such, we do not believe that the change in the D-SNP passive enrollment provision will have any impact on how States are assessing the alignment of Medicaid and Medicare provider networks.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received some comments in support of our proposal to require that an integrated D-SNP receiving passive enrollment have the care coordinator staffing capacity to receive dually eligible enrollees through passive enrollment. Some commenters noted that effective care coordination is essential and that flexibility in staffing models allows D-SNPs to tailor care coordination approaches to the unique needs of dually eligible enrollees, State-specific integration requirements, and existing Medicaid managed long-term services and supports (LTSS) delivery systems, while still ensuring that D-SNPs are appropriately resourced to support new enrollees. Commenters noted that integrated D-SNPs receiving passive enrollment would need adequate notice of the impending passive enrollment in order to meet any staffing update requirements and recommended that CMS provide notice of at least 90 days to the receiving D-SNP prior to the passive enrollment effective date, which would allow sufficient time to increase care coordinator staff levels. Other commenters requested that CMS provide additional information on how it would measure and evaluate adequate care coordination capacity under the proposed requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support of this proposal. We agree that if a D-SNP were to receive passive enrollment, it should be appropriately resourced to support new enrollees and to tailor care coordination approaches to the unique needs. As noted earlier in this preamble and outlined in the August 2018 HPMS memo, CMS's decision to allow passive enrollment for D-SNPs under § 422.60(g)(1)(iii) is intended to be a deliberative process done in consultation with the respective State. We decline the suggestion for CMS to provide a 90-day notice to potential receiving D-SNPs because we do not find it necessary. Potential receiving D-SNPs will be in communication with CMS and the State to determine if the receiving D-SNP meets the regulatory criteria, has the capacity, and agrees to take on the additional enrollment. We do not intend to establish specific standards for care coordination, but we do highlight the necessity of care coordination when transitioning new enrollees who may or may not have high level of need.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters opposed our proposal to require that an integrated D-SNP receiving passive enrollment have the care coordinator staffing capacity to receive dually eligible enrollees through passive enrollment. These commenters noted that there are already care coordination requirements outlined at § 422.107(c) and the potential for additional care coordination requirements that State Medicaid agencies include as part of their SMAC arrangement or establish as an expectation in their policy guides. Another commenter suggested that CMS refrain from issuing policies that dictate care coordination staffing ratios. Commenters further requested that CMS clarify the definition of “care coordinator staff.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the thoughtfulness of the commenters' responses to this proposed provision. We note that our proposal did not define a minimum staffing capacity threshold to give integrated D-SNPs flexibility in implementing this proposed change, and we are not intending to prescribe a specific standard or ratio at this time. Further, as the commenters noted, there are already care coordination requirements outlined at § 422.107(c). It was not our intention to amend how care coordination requirements are implemented by D-SNPs as required per § 422.107(c), including how many staff would be enough to fit the needs of the D-SNP's beneficiaries. We did not propose nor are we finalizing any additional language in this regard.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters specifically objected to our overall proposal to amend the passive enrollment regulation at § 422.60(g) based on their understanding of how it would affect enrollment in institutional special needs plans (I-SNPs) or enrollees that reside in nursing facilities and assisted living communities. The commenters noted that passively enrolling these enrollees into D-SNPs without comparable networks would undermine these investments and disadvantage I-SNPs that have demonstrated strong performance in serving high-need populations. Commenters also suggested that CMS use tags on enrollment processes as an exclusion criterion for passive enrollment. Commenters advised that if applied, then the enrollment flag or facility site of care should be used to ensure that beneficiaries residing in nursing facilities or assisted living communities are only passively enrolled into plans that can maintain continuity of care within their current care setting. In addition, some commenters recommended that CMS simplify opt-out processes and allow beneficiaries who have opted out of passive enrollment to remain in their chosen plan without having to re-opt-out annually.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their perspectives and appreciate the consideration paid to vulnerable populations. As we discussed previously in this preamble, we would like to make the distinction that our proposed amendment to the passive enrollment process at § 422.60(g)(2) is specific to D-SNPs and would not affect enrollees in other types of MA plans, including I-SNPs. We understand that under the FAI, full-benefit dually eligible individuals in some States could be passively enrolled into MMPs from different types of plans. That authority was specific to MMPs under the FAI and is separate from what we proposed in the Contract Year 2027 proposed rule, which only applies to integrated D-SNPs where the D-SNP is non-renewing or terminating and the State affirms its interest in transitioning these enrollees to another comparable integrated D-SNP with the goal of maintaining integrated coverage. Under § 422.60(g), CMS implements D-SNP passive enrollment only after consulting with the State Medicaid agency that contracts with the D-SNP, and requires the MA organization receiving passive enrollment to provide two notices of opt-out opportunities to enrollees at least 30 and 60 days prior to the enrollment effective date. Under our proposed amendment to § 422.60(g)(2), the MA organization must also provide continuity of care with a minimum 
                        <PRTPAGE P="17528"/>
                        transition period of 120 days. We do not believe an opt-out flag is needed since we expect any passive enrollment under § 422.60(g)(1)(iii) would be a one-time occurrence in response to an integrated D-SNP non-renewing or terminating. Individuals passively enrolled have multiple opportunities to switch their enrollment to align with their preferred provider or facility, if they so choose, as detailed earlier in this section.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters suggested ideas for involving the State Medicaid agency in passive enrollment. Some of these commenters recommended that CMS clarify the flexibilities available to State Medicaid agencies when permitting passive enrollment, including opportunities for the States to establish higher standards for D-SNPs to participate in passive enrollment. Other commenters advised CMS to amend the proposal to allow passive enrollment if State-specific requirements for continuity and transitions of care, detailed in SMACs, are met. The commenters further suggested that CMS defer to States for individual beneficiary assignments, as States are in the best position to understand which D-SNP provides the least disruptive transition option for its members. Some of the commenters recommended that CMS establish clear criteria for integration, such as aligned enrollment, robust Medicaid contracts, coordinated care management, and shared data systems. The commenters believed that passive enrollment should be permitted when the State Medicaid agency confirms that the receiving D-SNP maintains or improves integration compared to alternatives. Commenters also encouraged CMS to collaborate closely with States to ensure enrollees are informed of any enrollment changes due to the passive enrollment process and have meaningful opportunities to select their preferred plan, such as through State-based actions to waive any Medicaid managed care lock-in policies and issuing notices that outline the remaining integrated D-SNP options.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these suggestions. As we mentioned earlier in this preamble, since the inception of the passive enrollment process at § 422.60(g)(1)(iii), CMS's decision to implement passive enrollment has been discretionary, not mandatory, and subject to a deliberative process. We expect the circumstances for passive enrollment under § 422.60(g)(1)(iii) to generally occur when a State selects a new Medicaid MCO that has an affiliated D-SNP. When the State selects a new Medicaid MCO, an existing Medicaid MCO with an affiliated D-SNP may not be selected. In this circumstance, the State may want to passively enroll full-benefit dually eligible individuals from the relinquishing D-SNP into the receiving D-SNP. As we noted in the August 2018 HPMS memo that provided further technical assistance to D-SNPs on passive enrollment, in order to implement D-SNP passive enrollment under § 422.60(g)(1)(iii), CMS must consult with the applicable State, CMS must determine that passive enrollment will promote integrated care and continuity of care, and the receiving integrated D-SNP must meet certain requirements. In light of these requirements and our own longstanding practice, we have every intention of working with States to ensure that passive enrollment is in line with State goals and promotes integrated care. To this end, we note that the proposed amendment at § 422.60(g)(2) does not preclude a State from including in their SMAC additional criteria for passive enrollment from an integrated D-SNP that meets the criteria at § 422.60(g)(2). The additional SMAC criteria could include some of the suggestions advanced by the commenters. Further, a State could include such criteria in its request for proposal that is used to select Medicaid MCOs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments suggesting that we include specific information regarding provider or facility types that would be included in the proposed continuity of care requirement. These comments included setting specific requirements for physical therapists, occupational therapists, speech language pathologists, facility-based rehabilitation, home health and hospice providers. A commenter suggested that passive enrollment should emphasize flexibility to allow States and U.S. Territories, particularly those facing ongoing provider shortages in key service areas, such as behavioral health, long-term services and supports, or specialty care, to better protect continuity of care and avoid passive enrollment into plans with weaker or less adequate networks. A commenter suggested CMS clarify that, for therapy, continuity of care includes continuity of the therapeutic relationship, providers, and locations subject to medical necessity and consistent with the plan of care. Other commenters suggested that CMS implement stronger requirements around wait-times for new appointments and/or provider availability. The commenter further suggested that CMS could require any D-SNPs receiving passive enrollment to conduct a provider disruption analysis and share it with the State Medicaid agency prior to passive enrollment. Other commenters requested that CMS require D-SNPs to make reasonable efforts to contract with providers with which they have entered into continuity of care arrangements, to improve the provider network.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these commenters' perspectives. We note that the continuity of care period included in the proposed amendment to § 422.60(g)(2)(ii) would require any integrated D-SNP receiving passive enrollment to provide continuity of care consistent with § 422.112(b)(8)(i)(B) for a minimum of 120 days. Section 422.112(b)(8)(i)(B) applies to any active course(s) of treatment when an enrollee has enrolled in an MA plan after starting a course of treatment, even if the service is furnished by an out-of-network provider. Under our proposal, the integrated D-SNP receiving passive enrollment must not disrupt or require reauthorization for an active course of treatment for new plan enrollees for a period of at least 120 days. To that end, any integrated D-SNP receiving passive enrollment should not impose new administrative hurdles (
                        <E T="03">e.g.,</E>
                         new evaluations solely for coverage purposes) that functionally delay care transitions and undermine continuity of care. We emphasize that enrollees who are passively enrolled from a non-renewing or terminating integrated D-SNP into a comparable integrated D-SNP may opt out of the passive enrollment or choose other coverage via an SEP. We believe that the specific suggestions for establishing additional provider network and continuity of care requirements are out of scope for this rulemaking and we are not making any changes to the final rule related to those suggestions.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters suggested that CMS establish additional opportunities around when a dually eligible individual who is passively enrolled into a D-SNP can enroll in another plan, and that CMS establish processes to monitor functional outcomes for these dually eligible enrollees. These comments included suggestions for CMS to allow movement from integrated plans to Original Medicare, rather than only to another integrated D-SNP, or to create additional SEPs to allow enrollment in MA. A commenter specifically requested that CMS clarify in regulation that the exemption at § 422.60(g)(3)(ii) applies to individuals who have affirmatively selected a standalone prescription drug plan. Other commenters emphasized the continued 
                        <PRTPAGE P="17529"/>
                        importance of enrollees having sufficient notification about upcoming passive enrollments, the opportunity to make active plan selections during the passive enrollment process and through any applicable SEP.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters' perspectives about the importance of advance notification to enrollees during the D-SNP passive enrollment process as well as the opportunities to make other coverage selections. As articulated earlier in this section, D-SNP passive enrollment under § 422.60(g)(1)(iii) is only implemented after CMS consults with the State Medicaid agency that contracts with the D-SNP, and requires the MA organization receiving passive enrollment to provide enrollees with two separate notices, at least 30 and 60 days prior to the enrollment effective date, of the opportunity to opt out. If a passively enrolled full-benefit dually eligible individual wanted to make a change after the effective date of enrollment into the receiving integrated D-SNP, they could do so through the one-time-per month SEP for dually eligible individuals and other LIS eligible individuals to elect Original Medicare and a standalone PDP or the integrated care SEP which allows full-benefit dually eligible individuals to elect an integrated D-SNP on a monthly basis. Further, as we discussed earlier in this preamble and in the preamble to the Contract Year 2027 proposed rule, we did not propose amendments to § 422.60(g)(5), which describes an enrollee's access to the SEP at § 423.38(c)(10). As such, this SEP would also be accessible to enrollees who are interested in switching their coverage (90 FR 54972).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments offering support for our proposal that receiving D-SNPs operate as applicable integrated plans. Other suggestions included establishing a definition for “new integrated plan” and allowing all D-SNPs that meet strong integration standards, not just AIPs, to be eligible for passive enrollment, arguing that non-AIP D-SNPs can still provide significantly better coordination of Medicare and Medicaid services than other MA plans or Medicare FFS. Commenters also recommend that CMS clarify how the level of integration would be assessed if provider network adequacy and benefits are no longer criteria for passive enrollment and suggested adding to the proposed requirement that the receiving D-SNP must offer a substantially similar service array. A commenter recommended that CMS consider distributing enrollment among remaining qualified D-SNPs when a D-SNP exits the market.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We proposed to amend § 422.60(g)(2)(i) to describe the integrated D-SNPs that can receive passive enrollment as plans that operate as an AIP as described at § 422.561 in an effort to use consistent and accurate language throughout our processes and documentation. We proposed this change since, as stated in the Contract Year 2027 proposed rule (90 FR 54970) and earlier in this section, AIPs meet higher standards of integration, quality, and performance benchmarks than non-AIPs, and have exclusively aligned enrollment (when enrollment in a parent organization's D-SNP is limited to individuals with aligned enrollment), which we believe is a critical part of improving experiences and outcomes for dually eligible individuals. These D-SNP types more meaningfully integrate Medicare and Medicaid services and administrative processes (such as unified appeals and grievances) than HIDE SNPs that are not AIPs or coordination-only D-SNPs that are not also AIPs. Under our proposal, any integrated D-SNPs that meet the requirements in proposed § 422.60(g)(2) could receive passive enrollment from the non-renewing or terminating D-SNP. Additionally, in the August 2018 HPMS memo that provided further technical assistance to D-SNPs on passive enrollment, we did not state that only one plan may be selected to receive enrollees through passive enrollment. As we work with the State through the process, it could be possible for multiple integrated D-SNPs to receive passive enrollment.
                    </P>
                    <P>Further, as we discussed in the Contract Year 2027 proposed rule, since integration levels are defined both in statute at section 1859(f)(8)(D) of the Act and in regulation at §§ 422.2 and 422.107(d), and Medicare Part A, B, and D benefits and Medicaid benefits do not tend to differ across D-SNPs with the same integration level within a State, we do not believe that a specific assessment for substantially similar coverage of Medicare and Medicaid covered benefits or service array is required. In such a situation where passive enrollment is implemented, we believe that an assessment of level of integration between the relinquishing and receiving integrated D-SNPs would suffice (90 FR 54972). For example, if a HIDE SNP that is an AIP is non-renewing in the upcoming plan year, if the State agrees to a passive enrollment process, the receiving D-SNP would most likely also be a HIDE SNP that is an AIP. In the same State, the array of benefits offered by HIDE SNPs that are AIPs would most likely not be meaningfully different.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments that were outside of the scope of this proposal. Commenters suggested that CMS should require D-SNPs serving beneficiaries with serious mental illness to include licensed mental health professionals—whether mental health counselors, marriage and family therapists, clinical social workers, or other qualified behavioral health specialists—directly in care coordination teams or ensure immediate access to behavioral health consultation for care managers. Some commenters suggested using Medicaid managed care contracts to require Medicaid managed care plans to offer HIDE SNPs. Other commenters requested more information about default enrollment. The commenters opined that there is very little public data about default enrollment including total numbers of individuals default enrolled and whether default enrollment opt-out notices follow language and disability preferences of the enrollee. Commenters request data to understand whether default enrollment is working for people and truly reflecting their preferences.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their input. While we consider the comments outside the scope of this rulemaking, we take the opportunity to point commenters to information we made available regarding default enrollment. We provide data on the number of D-SNPs approved to participate in default enrollment under § 422.66(c)(2) and the annual number of individuals default enrolled 
                        <E T="03">https://www.cms.gov/medicare/enrollment-renewal/managed-care-eligibility-enrollment.</E>
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the proposed rule and our responses to comments, we are finalizing the proposed amendments to § 422.60(g)(2) without modification.</P>
                    <HD SOURCE="HD2">C. Continuity in Enrollment for Full-Benefit Dually Eligible Individuals in a D-SNP and Medicaid Fee-for-Service (§§ 422.107 and 422.514)</HD>
                    <P>
                        The Contract Year 2025 Medicare Advantage and Part D final rule, which appeared in the 
                        <E T="04">Federal Register</E>
                         on April 23, 2024 (hereafter referred to as the April 2024 final rule; 89 FR 30448), included several provisions to simplify options for dually eligible individuals and promote greater alignment of D-SNPs and Medicaid MCOs. We explained at 89 FR 30675 that, despite progress, there remain a significant number of enrollees who receive Medicare services through one managed 
                        <PRTPAGE P="17530"/>
                        care entity and Medicaid services through a different entity (misaligned enrollment), rather than from one organization delivering both Medicare and Medicaid services (aligned enrollment). As expressed in the April 2019 final rule (84 FR 15699 through 15730), we continue to believe that aligned enrollment, and especially exclusively aligned enrollment, is a critical part of improving the experiences and outcomes of dually eligible individuals.
                    </P>
                    <P>In the April 2024 final rule, we finalized a package of provisions at §§ 422.503(b)(8), 422.504(a)(20), and 422.514(h) that require that, beginning in contract year 2027, where an MA organization offers a D-SNP and the MA organization, its parent organization, or any entity that shares a parent organization with the MA organization also contracts with a State as a Medicaid MCO that enrolls full-benefit dual eligible individuals in the same service areas (even if there is only partial overlap of the service areas), the MA organization: (a) may only offer, or have a parent organization or share a parent organization with another MA organization that offers, one D-SNP for full-benefit dual eligible individuals, except as otherwise provided in § 422.514(h)(3); and (b) must limit new enrollment in the D-SNP to individuals enrolled in, or in the process of enrolling in, the Medicaid MCO. Per § 422.514(h)(2), beginning in contract year 2030, such D-SNPs must only enroll (or continue to enroll) individuals enrolled in (or in the process of enrolling in) the affiliated Medicaid MCO, except that such D-SNPs may continue to implement deemed continued eligibility requirements as described in § 422.52(d). To minimize enrollment disruption associated with achieving compliance, in the April 2024 final rule, we finalized a provision at § 422.530(c)(4)(iii) that would provide a new crosswalk exception to allow one or more MA organizations that share a parent organization and offer D-SNPs subject to the new limits to crosswalk enrollees (within the same parent organization and among consistent plan types) when the MA organization chooses to non-renew or consolidate its current D-SNPs to comply with the new rules at §§ 422.504(a)(20) and 422.514(h).</P>
                    <P>In addition, in the April 2024 final rule, we codified at § 422.514(h)(3) two exceptions to the requirements at § 422.514(h)(1) and (2) for instances where (a) the State Medicaid agency contract (SMAC) with the MA organization differentiates enrollment into D-SNPs by age group or to align enrollment in the D-SNP with the eligibility or benefit design used in the State's Medicaid managed care program and (b) the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization offers both HMO D-SNPs and PPO D-SNPs. To promote integrated care through aligned Medicare and Medicaid products, at § 422.514(h)(3)(ii) we finalized that the MA organization, its parent organization, or another MA organization that shares a parent organization with the MA organization may only accept new enrollment in one D-SNP for full-benefit dually eligible individuals in the same service area as an affiliated Medicaid MCO, and such new enrollment is limited to the full-benefit dually eligible individuals who are enrolled (or are enrolling) in the Medicaid MCO.</P>
                    <P>As articulated in the April 2024 final rule (89 FR 30680), overall, these changes would have several benefits. These include boosting the percentage of D-SNP enrollees in aligned enrollment, and—over time—exclusively aligned enrollment, increasing access to the comprehensive coordination of care, unified appeal processes across Medicare and Medicaid, continuation of Medicare services during an appeal, and integrated materials that come with enrollment in one or more of the various types of integrated D-SNPs; prompting MA organizations to consolidate PBPs down to a single PBP for full-benefit dually eligible individuals that is aligned with their Medicaid MCO that fully or partially overlaps with the D-SNP service area; removing some incentives for agents and brokers to target dually eligible individuals; lessening assistance needed from advocates and SHIP counselors to correct enrollment issues; and simplifying provider billing and lowering the risk of inappropriate billing.</P>
                    <P>In response to our proposals in the November 2023 proposed rule, a number of commenters suggested that the enrollment limitations could create barriers to care for dually eligible individuals in States where they are not required to be in or are explicitly carved out from Medicaid managed care (89 FR 30689 through 30690). For example, in New York, only dually eligible individuals with significant long-term care needs are required to enroll in Medicaid managed care, with the majority of dually eligible individuals remaining in Medicaid fee-for-service (FFS). These commenters noted that D-SNPs that also contract with States as Medicaid MCOs can currently enroll individuals into their D-SNP that are enrolled in Medicaid FFS but, under the requirements finalized in the April 2024 final rule, those D-SNPs would not be able to enroll these individuals beginning in 2027 and would be required to disenroll them as of 2030. Commenters indicated that these individuals are better served in D-SNPs where they receive coordination of their Medicare and Medicaid FFS services. The commenters offered several suggestions for how CMS could address these concerns: (a) limiting the proposal to States that require mandatory enrollment for dually eligible individuals, including those who do not receive long-term care services, (b) implementing a limited exception process for States that would allow MA organizations with an affiliated Medicaid MCO to offer at least one D-SNP PBP that is not exclusively aligned and that can enroll dually eligible individuals who maintain Medicaid FFS coverage and (c) phasing in the proposal over time.</P>
                    <P>
                        In the April 2024 final rule, we did not adopt any of the suggestions put forth by commenters. At 89 FR 30690, we outlined potential drawbacks to limiting the § 422.514(h) provisions to only States that require mandatory Medicaid managed care enrollment for dually eligible individuals. These drawbacks included narrowing the number of States in which these policies would apply, thus reducing the extent to which we would achieve the benefits. It would also raise potential complexity in States where certain subpopulations of dually eligible individuals are mandatorily enrolled, but others are not. We further stated that allowing each MA organization with an affiliated Medicaid MCO to offer at least one D-SNP that is not exclusively aligned with its affiliated Medicaid MCO for the purpose of enrolling dually eligible individuals who are enrolled in Medicaid FFS would similarly reduce the extent to which we would achieve the benefits described in the proposed rule, create additional operational complexity for States and CMS to administer and monitor, and would likely be more complicated to explain from a beneficiary communications and messaging perspective compared to the proposal that we finalized in the April 2024 final rule. Finally, we stated our belief that the phase-in of the policy would provide ample time for transition; the finalized requirement limits new enrollment to individuals enrolled in both a D-SNP and affiliated Medicaid MCO offered under the same 
                        <PRTPAGE P="17531"/>
                        parent organization starting in 2027 and then disenrolling those enrollees who do not have aligned enrollment in the D-SNP's affiliated Medicaid MCO in 2030. MA organizations would have two bid cycles and contract years (2025 and 2026) during which D-SNPs with affiliated Medicaid MCOs may prepare for the first phase of enrollment limitations.
                    </P>
                    <P>Since we codified the package of provisions in the April 2024 final rule, we have continued to receive feedback from stakeholders on some challenges in implementing these provisions in States without mandatory Medicaid managed care for the dual eligible population. For example, New York does not require mandatory Medicaid managed care for its Integrated Benefits for Dually Eligible Enrollees (IB-Duals) program. Participating HIDE SNPs may enroll full-benefit dually eligible individuals who are enrolled in Medicaid FFS or an unaffiliated Medicaid MCO. These HIDE SNPs do not have aligned enrollment. Without any change, in 2030, these HIDE SNPs would need to disenroll any enrollees who do not have aligned enrollment in the HIDE SNP's affiliated Medicaid MCO. In other words, beginning in 2027, these HIDE SNPs could no longer enroll any new dually eligible individuals who are enrolled in Medicaid FFS or an unaligned Medicaid MCO, and, in CY 2030, these HIDE SNPs would need to disenroll Medicaid FFS enrollees and any individuals enrolled in an unaligned Medicaid MCO.</P>
                    <P>In States that do not require mandatory Medicaid managed care for all of their full-benefit dually eligible individuals, we are also concerned about the § 422.514(h) requirements potentially disadvantaging MA organizations offering coordination-only D-SNPs and HIDE SNPs that both enroll full-benefit dually eligible individuals in the same service areas. The requirements at § 422.514(h) do not apply to MA organizations in a State that only offers coordination-only D-SNPs if these MA organizations, their parent organizations, or any entity that shares a parent organization with the MA organization does not also contract with the State as a Medicaid MCO that enrolls full-benefit dually eligible individuals. However, the § 422.514(h) requirements do apply to a State's HIDE SNPs if the MA organization also contracts with the State as a Medicaid MCO that enrolls full-benefit dually eligible individuals. In the Contract Year 2027 proposed rule, we provided a specific example in Pennsylvania to describe how § 422.514(h) requirements would potentially be disadvantaging to MA organizations offering coordination-only D-SNPs and HIDE SNPs that both enroll full-benefit dually eligible individuals in the same service areas. Please refer to 90 FR 54974 for the full discussion, and to our response to comments later on in this preamble which provide a correction to this example.</P>
                    <P>In 2027, in a State that does not mandate Medicaid managed care, those MA organizations offering a HIDE SNP with unaligned enrollment will no longer be permitted to enroll unaligned full-benefit dually eligible individuals into the HIDE SNP or allow full-benefit dually eligible individuals to enroll in the coordination-only D-SNP, unlike those MA organizations that only offer coordination-only D-SNPs in the State and do not contract with the State as a Medicaid MCO. In 2030, MA organizations with unaligned HIDE SNPs would need to disenroll any unaligned full-benefit dually eligible individuals from their HIDE SNP. In a State that does not mandate Medicaid managed care, we believe that our regulation as-is at § 422.514(h) could create an incentive for MA organizations to terminate their HIDE SNP and transition dually eligible enrollees to the coordination-only D-SNP, which could continue to enroll full-benefit dually eligible individuals regardless of whether an enrollee receives their Medicaid coverage through Medicaid FFS or an unaligned Medicaid managed care plan, allowing such a plan to maintain maximum enrollment. For these reasons, we believe that the application of § 422.514(h) to the MA organizations with unaligned HIDE SNPs and coordination-only D-SNPs puts them at a disadvantage in comparison to those MA organizations with only coordination-only D-SNPs, since full-benefit dually eligible individuals are able to, and do, remain in Medicaid FFS in States without mandatory Medicaid managed care. This is an unintended consequence of § 422.514(h), inconsistent with our goals to promote integrated care. While our goal is to have full-benefit dually eligible individuals enrolled in integrated D-SNPs, we do not want to inadvertently prevent integrated D-SNPs from continuing to enroll full-benefit dually eligible individuals who are enrolled in Medicaid FFS.</P>
                    <P>In the Contract Year 2027 proposed rule, we proposed to amend §§ 422.107(d)(1) and 422.514(h) to allow D-SNPs that serve full-benefit dually eligible individuals in a HIDE SNP or coordination-only D-SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where those individuals are enrolled in Medicaid FFS. In the Contract Year 2027 proposed rule at 90 FR 54974, we explained that these proposed changes would address the challenges of MA organizations complying with the requirements at § 422.514(h) in States where there is no mandatory Medicaid managed care program and avoid the need for MA organizations in those States to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and start disenrolling those members in 2030 as currently required under § 422.514(h).</P>
                    <P>We proposed to amend SMAC requirements at § 422.107(d)(1) through adding a new (i). For any SMACs that allow coordination-only D-SNPs (as established under § 422.107(d)(1)) to enroll full-benefit dually eligible individuals, proposed paragraph (i) would require the SMAC to stipulate that such full-benefit dually eligible beneficiaries cannot be enrolled in a Medicaid MCO that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization. In other words, the proposed amendment to § 422.107(d)(1) would permit coordination-only D-SNPs that enroll full-benefit dually eligible individuals to enroll full-benefit dually eligible individuals who are enrolled in Medicaid FFS.</P>
                    <P>
                        At § 422.514(h)(3), we proposed to add new (iii) and (iv). For any SMACs that permit full-benefit dually eligible individuals to enroll in (a) a coordination-only D-SNP per the proposed amendment at § 422.107(d)(1)(i) or (b) a HIDE SNP with a majority of individuals enrolled in Medicaid FFS, the new paragraph proposed at § 422.514(h)(3)(iii) would allow the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization to offer one or more additional D-SNPs for full-benefit dually eligible individuals in the same service area. We explained that our belief was that limiting the proposed exception at § 422.514(h)(3) to HIDE SNPs with a majority of enrollees in Medicaid FFS would prevent application of this exception to HIDE SNPs with a minority of Medicaid FFS enrollees and a majority of Medicaid managed care enrollees whose Medicaid MCO is unaligned with the HIDE SNP. HIDE SNPs with a majority of enrollees in unaligned Medicaid MCOs would have less incentive to achieve aligned membership and detract from the intended goals of § 422.514(h). We 
                        <PRTPAGE P="17532"/>
                        proposed adding a new (iv) at § 422.514(h)(3) that would require MA organizations with D-SNPs subject to § 422.514(h)(3)(iii) to comply with care coordination responsibilities at § 422.562(a)(5). Per § 422.562(a)(5)(i), D-SNPs must offer to assist an enrollee in that D-SNP with obtaining Medicaid-covered services and resolving grievances, including requesting authorization of Medicaid services, as applicable, and navigating Medicaid appeals and grievances in connection with the enrollee's own Medicaid coverage, regardless of whether such coverage is in Medicaid FFS or a Medicaid managed care plan, such as a Medicaid MCO, prepaid inpatient health plan (PIHP), or prepaid ambulatory health plan (PAHP) as defined in § 438.2. If the enrollee accepts the offer of assistance, the plan must provide the assistance. Examples of such assistance are outlined at § 422.562(a)(5)(i)(A). We considered amending § 422.562(a)(5)(i)(A) to require MA organizations with D-SNPs subject to proposed § 422.514(h)(3)(iii) to report to CMS on the proactive outreach they provide to Medicaid FFS enrollees, the type of assistance they offered to these enrollees, and whether these enrollees received the relevant Medicaid services. We did not propose to require MA organizations with D-SNPs subject to proposed § 422.514(h)(3)(iii) to report their efforts to meet § 422.562(a)(5)(i) to CMS since such reporting would add burden for MA organizations and we may be able to leverage existing oversight mechanisms, such as models of care (MOCs), CMS program audits, monthly calls between MA organizations and CMS account managers, and existing State Medicaid FFS reporting to CMS instead of adding new plan reporting requirements. We solicited comments on whether we should amend § 422.562(a)(5)(i)(A) to require MA organizations with D-SNPs to report on their activities for assisting Medicaid FFS enrollees in obtaining Medicaid covered services instead of or in addition to the existing oversight mechanisms outlined.
                    </P>
                    <P>In the Contract Year 2027 proposed rule, we stated our position that these proposals at §§ 422.107(d)(1)(i) and 422.514(h)(3) would benefit MA organizations operating multiple D-SNPs that enroll full-benefit dually eligible individuals in States without mandatory Medicaid managed care. The intent of our proposed changes was to remove the disadvantage some MA organizations that offer HIDE SNPs will encounter starting (a) in 2027, when they would need to stop enrolling full-benefit dually eligible individuals into HIDE SNPs that enroll Medicaid FFS enrollees and (b) in 2030, when they would need to disenroll full-benefit dually eligible individuals from HIDE SNPs that enroll Medicaid FFS enrollees. Similarly, our proposed changes were intended to address the disadvantage MA organizations that offer HIDE SNPs and coordination-only D-SNPs will encounter starting (a) in 2027, when they would need to stop enrolling full-benefit dually eligible individuals into coordination-only D-SNPs and (b) in 2030, when they would need to disenroll full-benefit dually eligible individuals from coordination-only D-SNPs that enroll Medicaid FFS enrollees. We explained in the Contract Year 2027 proposed rule that we do not believe these changes would detract from the goal of the provisions we codified in the April 2024 final rule, which was to increase the percentage of D-SNP enrollees in aligned enrollment, and—over time—exclusively aligned enrollment. When Medicaid FFS is available and HIDE SNPs can enroll individuals who are in Medicaid FFS, exclusively aligned enrollment cannot be achieved.</P>
                    <P>In the April 2024 final rule, we received comments concerning the applicability of the enrollment limitation policies at § 422.514(h) on unique Medicaid managed care programs. Among others, commenters raised specific questions about the applicability of this rule to D-SNPs in Puerto Rico (89 FR 30697). We responded to these comments and noted that MA organizations that offer multiple D-SNPs participating in the Platino program in Puerto Rico would be required to only offer one D-SNP starting in 2027 for full-benefit dually eligible individuals in a service area where an MA organization, its parent organizations, or an entity that shares a parent organization with the MA organization also offers an affiliated Medicaid MCO unless those D-SNPs meet the exception finalized at § 422.514(h)(3).</P>
                    <P>Currently, Puerto Rico is the only U.S. Territory that offers D-SNPs. We note that the U.S. Territories, including Puerto Rico, are unique, as the Medicaid program in the U.S. Territories differs from Medicaid programs operating in the States and the District of Columbia in several notable ways. The Medicare Savings Programs (MSPs), as defined at section 1144(c)(7) of the Act and 42 CFR 435.4, are Medicaid eligibility groups through which Medicaid assists low-income Medicare beneficiaries with their Part A and/or Part B premiums, and for many enrollees, cost-sharing. The MSPs are mandatory Medicaid eligibility groups for the 50 States and the District of Columbia, but optional for the U.S. Territories per section 1905(p)(4)(A) of the Act. Currently, no U.S. Territory has adopted the MSPs. Additionally, per section 1860D-14(a)(3)(F) of the Act and 42 CFR 423.907(a)(1), low-income Part D eligible individuals who reside in the U.S. Territories are ineligible for the Part D low-income subsidy, which provides cost-sharing and premium assistance to low-income Part D-eligible in the 50 States and the District of Columbia in accordance with section 1860D-14 of the Act and 42 CFR part 423 subpart P. While traditional funding sources for Medicare premiums are unavailable in the U.S. Territories, D-SNPs have the discretion to apply their MA rebate toward the Part B premium amount. (For CY 2026, we note that D-SNPs in Puerto Rico differentiate their plan benefit packages by level of Part B premium reduction amount and supplemental benefits.) Additionally, premiums for Part D are covered by the Enhanced Allotment Plan (section 1935(e) of the Act), a specific source of funding for prescription drugs for the U.S. Territories.</P>
                    <P>Upon further consideration and given the unique landscape in the U.S. Territories, including Puerto Rico, we proposed an exception at § 422.514(h)(3)(v). The proposed exception would exempt MA organizations operating in U.S. Territories that have not adopted MSP from the requirements at § 422.514(h)(1)(i) that otherwise would require—beginning in contract year 2027—the MA organization to only offer, or have a parent organization or share a parent organization with another MA organization that offers, one D-SNP for full-benefit dual eligible individuals.</P>
                    <P>
                        We acknowledged in the Contract Year 2027 proposed rule that this proposal is a change from what we previously stated in response to comments in the April 2024 final rule. We also acknowledged that upon further consideration and review, we may, in future rulemaking, reconsider this proposed exception at § 422.514(h)(3)(v). These proposed changes target MA organizations in States with voluntary Medicaid managed care enrollment and seek to level the playing field in the marketplace for impacted D-SNPs. The proposed change at § 422.514(h)(3)(v) is intended to acknowledge the uniqueness of D-SNP landscapes in the U.S. Territories.
                        <PRTPAGE P="17533"/>
                    </P>
                    <P>We solicited comments on all aspects of our proposal, including whether the advantages of the proposed changes would excessively detract from the original goal of the provisions codified in the April 2024 final rule. For example, we stated that we were interested in stakeholders' perspectives on the value of non-AIP HIDE SNPs with a majority of Medicaid FFS enrollees and whether we should establish an exception for them at proposed § 422.514(h)(3)(iii) at all or limit that exception to a shorter period of time, such as 2027 through 2029. While in the Contract Year 2027 proposed rule we identified a few States that we expected would benefit from our proposals, we invited commenters to identify other States that could benefit or be negatively impacted. As outlined earlier in this section, we also solicited comments on whether we should amend § 422.562(a)(5)(i)(A) to require MA organizations with D-SNPs subject to proposed § 422.514(h)(3)(iii) to report on their activities to assist Medicaid FFS enrollees with obtaining Medicaid covered services. Further, we solicited comment on the likely effectiveness of our proposed regulation in balancing the roles of D-SNPs in the U.S. Territories to fill the gaps of MSP and Part D LIS while also providing robust Medicare benefits to dually eligible individuals. We also stated our interest in perspectives on how limiting D-SNPs in the U.S. Territories would affect enrollees and the consumer choice in U.S. Territories.</P>
                    <P>We received the following comments on this proposal and respond to them below:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters, including MACPAC, expressed their support for our proposal to amend §§ 422.107(d)(1) and 422.514(h) to allow D-SNPs that serve full-benefit dually eligible individuals in a HIDE SNP or coordination-only D-SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where those individuals are enrolled in Medicaid FFS. Commenters opined that this proposal accommodates diversity in State Medicaid managed care requirements while preserving opportunities for integrated care for all dually eligible individuals. Commenters expressed that while significant integration cannot be achieved for dually eligible enrollees in Medicaid FFS, D-SNPs might still provide helpful support to Medicaid FFS enrollees, including in obtaining Medicaid-covered services and navigating Medicaid appeals and grievances processes. MACPAC explained that the proposal recognized CMS's efforts to accommodate States' varying managed care landscapes and the challenges States and plans face as they work toward greater integration of Medicare and Medicaid benefits.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support for this proposal. As we stated in the Contract Year 2027 proposed rule, our intention in proposing this exception was to address the challenges of MA organizations complying with the requirements at § 422.514(h) in States where there is no mandatory Medicaid managed care program and avoid the need for MA organizations in those States to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and disenroll unaligned members in 2030 as currently required under § 422.514(h). We appreciate the commenters' confirmation of our understanding that the varied Medicaid managed care landscapes necessitate an exception for when Medicaid FFS is available and exclusively aligned enrollment cannot be achieved.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters objected to the proposal to amend §§ 422.107(d)(1) and 422.514(h). These commenters expressed their belief that this proposal would reduce the scope of or limit enrollment in coordination-only D-SNPs or that this proposed language could result in a D-SNP having more than one health plan under the same MA organization operating in the same service area with different networks, offering different benefits, and requiring different premiums, causing market confusion for dually eligible individuals.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their attention to this proposal, and we appreciate the opportunity to clarify aspects of what we proposed. We would like to reiterate that the intention of this proposal is to address the challenges that some MA organizations may have in complying with the requirements at § 422.514(h) in States where there is no mandatory Medicaid managed care program for all full-benefit dually eligible enrollees. As our stated goal has been to promote integrated care, the purpose of the proposal put forth in the Contract Year 2027 proposed rule is to avoid the need for MA organizations in States without mandatory Medicaid managed care to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and disenroll those members in 2030 as would be required under existing § 422.514(h). Further, under our proposal at § 422.514(h)(3), for any SMACs that permit full-benefit dually eligible individuals to enroll in (a) a coordination-only D-SNP per proposed amendment at § 422.107(d)(1)(i) or (b) a HIDE SNP with a majority of individuals enrolled in Medicaid FFS, the new paragraph proposed at § 422.514(h)(3)(iii) would allow the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization to offer one or more additional D-SNPs for full-benefit dually eligible individuals in the same service area. Also, the proposed amendment to § 422.107(d)(1) would permit coordination-only D-SNPs that are affected by the requirements at § 422.514(h) to enroll full-benefit dually eligible individuals who are enrolled in Medicaid FFS. We respectfully disagree with the commenters' assumptions that the proposed rule would limit coordination-only D-SNPs in any way. In fact, we believe that this policy would have positive implications for coordination-only D-SNPs that are affected by the current § 422.514(h) language. We also emphasize that the requirements at § 422.514(h) do not apply to MA organizations in a State that only permits plans to offer coordination-only D-SNPs if these MA organizations, their parent organizations, or any entity that shares a parent organization with the MA organization does not also contract with the State as a Medicaid MCO that enrolls full-benefit dually eligible individuals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments from States and advocates on how the proposed provisions would affect populations that are excluded from mandatory Medicaid managed care enrollment, or who have the choice to enroll in Medicaid managed care, in a particular State. Commenters were supportive of the proposal to allow these populations to enroll, or continue to be enrolled, in a D-SNP affected by requirements of § 422.514(h), but noted that the “majority of” threshold proposed at § 422.514(h)(3)(iii) may not have the intended impact for beneficiaries in States where carve-outs are for a small population, and would be unable to meet the “majority of” threshold.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the responses from commenters illuminating how some States carve certain populations out of mandatory Medicaid managed care. Our intention in proposing this provision was to remove the disadvantage that MA organizations that offer coordination-only D-SNPs with an affiliated Medicaid managed care plan and HIDE SNPs could encounter starting (a) in 2027, when they would need to stop enrolling full-benefit dually eligible 
                        <PRTPAGE P="17534"/>
                        individuals into the D-SNP that enrolls Medicaid FFS enrollees and (b) in 2030, when they would need to disenroll full-benefit dually eligible individuals from the D-SNP that enrolls Medicaid FFS enrollees. We agree that the inclusion of “majority of” in the proposed language at § 422.514(h)(3)(iii) could cause HIDE SNPs in States with small populations of full-benefit dually eligible individuals carved out of mandatory Medicaid managed care to not qualify for the proposed exception. For example, States that have carved-out individuals with intellectual and development disabilities from mandatory Medicaid managed care may have a coordination-only D-SNP or HIDE SNP enrolling the carved-out population. Because the carved-out population is relatively small, the HIDE SNP would not likely meet the proposed “majority of” requirement, and these D-SNPs would need to cease enrolling these full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and disenroll those members in 2030, as currently required under § 422.514(h). In light of these concerns, we are modifying the language proposed in § 422.514(h)(3)(iii) that would require a “majority of” HIDE SNP enrollees to be full-benefit dually individuals enrolled in Medicaid FFS in order to qualify for the proposed exception. We provide more detail on this proposed modification below.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received many comments on our proposed amendment to § 422.514(h)(3), which would add new paragraph (iii) stipulating in part that the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization that has a HIDE SNP with a majority of individuals enrolled in Medicaid FFS, would be able to offer one or more additional D-SNPs for full-benefit dually eligible individuals in the same service area. Commenters expressed their belief that the proposed exception at § 422.514(h)(3)(iii) extends beyond the stated intent in the preamble and may create confusion for States and health plans, since the proposed amendment did not include corresponding limitations or qualifiers.
                    </P>
                    <P>Some commenters requested clarification on the use of the term “majority,” while other commenters suggested removing the “majority” threshold altogether. Commenters who suggested its removal stated that such a requirement could create operational challenges for D-SNPs whose enrollment fluctuates near the threshold or it could create unintended incentives for D-SNPs to avoid transitioning eligible members into integrated D-SNPs. Other commenters suggested that we revise the “majority” threshold requirement to avoid impeding aligned enrollment efforts if States transition their Medicaid FFS enrollees to Medicaid managed care.</P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their thoughtful opinions and questions. As we explained in the Contract Year 2027 proposed rule, our intention with the proposed language at §§ 422.514(h)(3)(iii) and 422.107(d)(1)(i) was to address the challenges of MA organizations complying with the requirements at § 422.514(h) in States where there is no mandatory Medicaid managed care program for full-benefit dually eligible individuals and avoid the need for MA organizations in those States to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and disenroll those members in 2030 as currently required under § 422.514(h) (90 FR 54974). We proposed that this exception would apply where enrollment of full-benefit dually eligible individuals represents a majority of the HIDE SNP's enrollees, to avoid the proposed exception applying to HIDE SNPs with only small proportion of enrollees in Medicaid FFS.
                    </P>
                    <P>Upon consideration of the numerous comments received on the impact of the proposed “majority” threshold for HIDE SNPs and to clarify the scope of the proposal, we are modifying some of the language at § 422.107(d)(1)(i) and finalizing as proposed other portions of § 422.107(d)(1)(i). First, we are finalizing as proposed the language at § 422.107(d)(1)(i) providing that in order to trigger the stipulation requirement described in § 422.107(d)(1)(i), the SMAC must include language allowing enrollment of full-benefit dually eligible individuals into the D-SNP. Second, we are finalizing as proposed the language at § 422.107(d)(1)(i) that the SMAC must stipulate that such full-benefit dually eligible individual cannot be enrolled in a Medicaid MCO that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization. Third, based on comments we received, we are modifying the proposed language at § 422.107(d)(1)(i) to specify that such an exception is available to a HIDE SNP as well as a coordination-only D-SNP that operates in a State where the State Medicaid agency does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals. We believe that this language appropriately addresses D-SNPs that are subject to § 422.514(h) requirements and operate in a State with voluntary Medicaid managed care and addresses the concerns expressed by commenters on this proposal.  </P>
                    <P>
                        In response to numerous comments we received and to more effectively achieve the intent of the proposal, we are modifying some of the language at § 422.514(h)(3)(iii) and finalizing as proposed other portions of § 422.514(h)(3)(iii). We are finalizing as proposed that the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization subject to this new exception may offer one or more additional D-SNPs for full-benefit dually eligible individuals who are enrolled in Medicaid FFS. We are modifying the provision by removing the threshold requirement that the majority of HIDE SNP enrollees must be enrolled in Medicaid FFS in order to qualify for the new exception. We are replacing the majority threshold with language specifying that (1) if the MA organization subject to § 422.514(h)(1) holds a State Medicaid agency contract with a State that does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals and (2) if the State Medicaid agency contract allows enrollment of full-benefit dually eligible individuals who are enrolled in Medicaid FFS, the MA organization may enroll, in a coordination-only D-SNP or HIDE SNP, full-benefit dually eligible individuals who are enrolled in Medicaid FFS. This modification will remove the proposed majority threshold that raised concerns for the commenters, while ensuring that the exception is only available to the extent a D-SNP operates in a State that does not require mandatory Medicaid managed care for all of its dually eligible enrollees and is allowed, via the State Medicaid agency contract, to enroll Medicaid FFS enrollees. This change is consistent with our intent, as stated in the proposed rule, to allow HIDE SNPs and coordination-only D-SNPs to continue enrollment of dually eligible individuals in a D-SNP in service areas where those individuals are enrolled in Medicaid FFS (90 FR 54974). As we stated in the proposed rule, we did not want to inadvertently prevent integrated D-SNPs from continuing to enroll full-benefit dually eligible individuals who are enrolled in Medicaid FFS. Additionally, in response to public comments seeking clarification on which enrollees D-SNPs subject to this exception may enroll, we are adding language stating that (3) D-SNPs may not enroll full-benefit dually eligible individuals who are enrolled in 
                        <PRTPAGE P="17535"/>
                        a Medicaid MCO that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization. This language mirrors the language we are finalizing at § 422.107(d)(1).
                    </P>
                    <P>We are making these modifications in light of concerns raised by many commenters that the “majority of” threshold was ambiguous and difficult to achieve. Having considered these comments in light of the intent of the exception as described in the proposed rule, we have determined that the modified language for § 422.514(h)(3)(iii) would more effectively result in the desired outcome, as it would allow enrollment of smaller populations that States exclude from Medicaid managed care enrollment, or who have a choice to enroll in Medicaid managed care. Commenters noted that such enrollees may only represent a minority of coordination-only D-SNP or HIDE SNP enrollees and thus tying the new exception to a “majority of” enrollees in Medicaid FFS would exclude such full-benefit dually eligible individuals from enrolling into a HIDE SNP as set forth in State policy. As stated in the proposed rule, our goal is to avoid the need for MA organizations in those States to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and avoid the need to disenroll those members in 2030 as currently required under § 422.514(h) in States that do not mandate enrollment in Medicaid managed care. (90 FR 54974) Furthermore, the requirements set forth in the SMAC will ensure that only coordination-only D-SNPs and HIDE SNPs with Medicaid FFS enrollment operating in States that do not mandate Medicaid managed care for all full-benefit dually eligible individuals and are approved by the State would have the option to use the exception finalized at 422.514(h)(3)(iii) for Medicaid FFS enrollees. Moreover, consistent with CMS's stated intent to allow D-SNPs to continue enrolling Medicaid FFS enrollees, the exception would not allow for the enrollment of individuals enrolled in unaligned Medicaid managed care. Thus, we do not believe it is necessary to limit the exception to HIDE SNPs that have a majority of its enrollees in Medicaid FFS.</P>
                    <P>Taken together, the modifications that we are finalizing at §§ 422.107(d)(1)(i) and 422.514(h)(3)(iii) more effectively alleviate the concerns documented in the Contract Year 2027 proposed rule with regard to § 422.514(h) requirements potentially disadvantaging MA organizations offering coordination-only D-SNPs and HIDE SNPs that enroll full-benefit dually eligible individuals in the same service areas where those individuals are enrolled in Medicaid FFS (90 FR 54974). Based on the numerous comments we received, we would like to reiterate that this exception is only applicable to 1) D-SNPs that are subject to the requirements of § 422.514(h) and that 2) operate in a State that does not mandate that all full-benefit dually eligible individuals enroll in Medicaid managed care.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Other commenters questioned our inclusion, in the Contract Year 2027 proposed rule, of Pennsylvania as an example of a State that does not mandate Medicaid managed care for full-benefit dually eligible individuals. Commenters clarified that although the State does not have 100-percent mandated Medicaid managed care, most Medicaid beneficiaries are enrolled in mandated managed care, and very few Medicaid beneficiaries are in FFS. Those enrolled in Medicaid FFS are limited to individuals under a particular Medicaid waiver authority, enrolled in PACE, or residents of State hospitals and intermediate care facilities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their clarification of Pennsylvania's landscape. As discussed earlier in this section, we are modifying the scope of the provisions to apply to coordination-only D-SNPs and HIDE SNPs that are subject to the requirements of § 422.514(h) and that operate in a State that does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals. As finalized, the exception at § 422.514(h)(3)(iv) would allow MA organizations that offer both a coordination-only D-SNP and HIDE SNP in Pennsylvania to continue to enroll full-benefit dually eligible individuals that are in Medicaid FFS should the State allow such enrollment in the SMAC.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received other comments seeking clarification on the intended impact of this proposal. Some commenters sought clarification on what was proposed in the Contract Year 2027 proposed rule, including whether CMS intends for the proposed language at § 422.514(h)(3)(iii) to allow enrollment of full-benefit dually eligible individuals in Medicaid FFS to also include full-benefit dually eligible individuals who are enrolled in a Medicaid MCO through a parent company that differs from the coordination-only D-SNP or HIDE SNP.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the opportunity to clarify what types of enrollees would be eligible for enrollment under this exception. As we discussed earlier in this preamble, if the State Medicaid agency contract allows enrollment of full-benefit dually eligible individuals who are enrolled in Medicaid FFS, the MA organization may enroll, in a coordination-only D-SNP or HIDE SNP, full-benefit dually eligible individuals who are enrolled in Medicaid FFS. Additionally, we are also finalizing language at § 422.107(d)(1)(i) and adding similar language at § 422.514(h)(3)(iii) stating that D-SNPs may not enroll full-benefit dually eligible individuals who are enrolled in a Medicaid MCO that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization. We further note that this language would allow eligible D-SNPs to enroll new Medicaid FFS enrollees and continue enrollment for any current enrollees who also have Medicaid FFS.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments seeking clarification or making recommendations about whether this proposed exception at § 422.514(h)(3)(iii) would be a permanent exception. Commenters questioned whether the proposed flexibilities end in 2030 and suggested that this proposal be a time-limited transition mechanism, rather than a permanent policy solution.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the commenters' interest in making the proposed exception at § 422.514(h)(3)(iii) a time-limited transition mechanism, our proposal was to make this exception permanent. We appreciate the consideration that commenters paid to evolving landscapes in States and how this may affect future enrollment. As we discussed previously in this preamble, coordination-only D-SNPs and HIDE SNPs subject to § 422.514(h)(3)(iii) will be allowed to retain full-benefit dually eligible enrollees in Medicaid FFS and newly enroll full-benefit dually eligible enrollees in Medicaid FFS to the extent that such enrollment is allowed via the State Medicaid agency contract per § 422.107(c)(2) and the contract is with a State that does not mandate Medicaid managed care for all full-benefit dually eligible individuals. States retain the option to stipulate enrollment and eligibility requirements in their State Medicaid agency contracts. Nothing in this final rule precludes a State from adding requirements to their State Medicaid agency contracts through § 422.107(c) that would prohibit or 
                        <PRTPAGE P="17536"/>
                        place a time limit on the enrollment of full-benefit dually eligible individuals enrolled in Medicaid FFS by the D-SNP.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments in response to our proposal to add specific language at § 422.514(h)(3)(iv) regarding the proposed requirement that MA organizations with D-SNPs subject to paragraph (h)(3)(iii) must comply with responsibilities at existing § 422.562(a)(5). Also, commenters responded to our request for comment on whether to amend § 422.562(a)(5)(i)(A) to require MA organizations with D-SNPs to report on their activities for assisting Medicaid FFS enrollees in obtaining Medicaid covered services instead of or in addition to the existing oversight mechanisms outlined in § 422.562(a)(5). A few commenters requested that we provide more specificity regarding potential reporting requirements. Many other commenters were opposed to the suggestion of additional reporting requirements, with a commenter stating that there could be confusion among plans as to what is required, given that § 422.562(a)(5)(i)(A) is currently applicable to all D-SNPs. A commenter objected to our proposal to add language at § 422.514(h)(3)(iv), stating their belief that such an action would require CMS to pursue Congressional action to redefine these Medicaid FFS coordination-only D-SNPs and HIDE SNPs separate from D-SNPs in statute.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their consideration of the proposed regulation text at § 422.514(h)(3)(iv) and the request for comment considering potential reporting requirements for obligations proposed in § 422.514(h)(3)(iv). Our intention in proposing to add text at § 422.514(h)(3)(iv) stating that MA organizations with D-SNPs subject to proposed § 422.514(h)(3)(iii) must comply with responsibilities at § 422.562(a)(5) was to underscore the obligation that D-SNPs have to assist an enrollee in their plan with obtaining Medicaid covered services and resolving grievances, including requesting authorization of Medicaid services, as applicable, and navigating Medicaid appeals and grievances in connection with the enrollee's own Medicaid coverage. This obligation applies to all D-SNPs and their enrollees regardless of enrollment in Medicaid managed care or Medicaid FFS. Upon further review, we agree with commenters that adding a reference to § 422.562(a)(5) at § 422.514(h)(3)(iv) would be redundant since all D-SNPs are subject to the existing requirements at § 422.562(a)(5), so we are not finalizing our proposal to add that language in § 422.514(h)(3)(iv). We further appreciate the comments received in response to our request for comment on whether to amend § 422.562(a)(5)(i)(A) to require MA organizations with D-SNPs to report on their activities for assisting Medicaid FFS enrollees in obtaining Medicaid covered services instead of or in addition to the existing oversight mechanisms outlined in § 422.562(a)(5). We are not taking any action on this comment solicitation in this rulemaking, but we may consider exploring opportunities for potential future rulemaking on this topic.
                    </P>
                    <P>Finally, we appreciate the viewpoint that the proposed regulatory amendment may be perceived as defining coordination-only D-SNPs and HIDE SNPs with Medicaid FFS enrollees as a separate type of D-SNP. However, we do not believe this to be the case. Through this proposal, we are providing an exception for coordination-only D-SNPs and HIDE SNPs that are subject to the requirements of § 422.514(h) and that operate in a State that does not mandate all full-benefit dually eligible individuals to enroll in Medicaid managed care. We are neither proposing nor finalizing another category of integration. As such, we respectfully disagree with commenters that Congressional action would be needed.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received many other comments seeking clarification on the intended impact of this proposal. Some commenters sought clarification on how this proposed policy would be operationalized, if finalized. Commenters sought clarification on who is eligible to enroll in a D-SNP under this proposed exception, including how individuals enrolled in prepaid inpatient health plans (PIHPs) and prepaid ambulatory health plans (PAHPs) would be factored in. Other commenters sought information on how these proposed changes would affect how many PBPs a MA organization could have, whether plans would be allowed to consolidate existing coordination-only D-SNP PBPs into their HIDE-SNP PBPs in their Medicaid MCO service areas, whether plans would be required to create new coordination-only D-SNPs or MA organization contracts or use existing coordination-only D-SNPs and MA organization contracts to take advantage of the proposed exception in addition to whether MA organizations could expand their coordination-only D-SNPs into areas outside of their Medicaid MCO service area. We also received questions regarding crosswalking enrollees between coordination-only D-SNPs and HIDE SNPs, and how proposed changes would affect segmented PBPs. Commenters expressed concern that the proposed language could be read to impose an overall limit on enrollment of individuals in coordination-only D-SNPs and non-affiliated Medicaid MCOs, including those in non-overlapping service areas.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the questions raised by the commenters. We would like to reiterate that in the April 2024 final rule, we finalized a package of provisions at §§ 422.503(b)(8), 422.504(a)(20), and 422.514(h) that require that, beginning in contract year 2027, where an MA organization offers a D-SNP and the MA organization, its parent organization, or any entity that shares a parent organization with the MA organization also contracts with a State as a Medicaid MCO that enrolls full-benefit dually eligible individuals in the same service areas (even if there is only partial overlap of the service areas), the MA organization: (a) may only offer, or have a parent organization or share a parent organization with another MA organization that offers, one D-SNP for full-benefit dual eligible individuals, except as otherwise provided in § 422.514(h)(3); and (b) must limit new enrollment in the D-SNP to individuals enrolled in, or in the process of enrolling in, the Medicaid MCO. If a D-SNP, or the D-SNP's parent organization, does not contract with the State as a Medicaid MCO, then the D-SNP would not be affected by the provisions in § 422.514(h) and would be able to enroll anyone eligible for their plan per the provisions at § 422.107(c)(2). To the extent that a State does not require enrollment of all full-benefit dually eligible individuals into Medicaid managed care and to the extent that enrollment of full-benefit dually eligible enrollees in Medicaid FFS is allowed via the State Medicaid agency contract per § 422.107(c)(2), the MA organization would be permitted to have coordination-only D-SNPs or HIDE SNPs that enroll or continue to enroll such individuals who are in Medicaid FFS. We therefore disagree with concern that the proposed language could be read to impose an overall limit on enrollment of individuals in coordination-only D-SNPs and non-affiliated Medicaid MCOs, including those in non-overlapping service areas.
                    </P>
                    <P>
                        We appreciate commenters' concern regarding the application of this proposed exception. We note that we will respond to some of the more detailed operational questions in an updated version of the Frequently Asked Questions (FAQs) and 
                        <PRTPAGE P="17537"/>
                        Enrollment Scenarios for § 422.514(h).
                        <SU>111</SU>
                        <FTREF/>
                         However, we appreciate the opportunity to offer some clarification in terms of scope. In response to comments in the April 2024 final rule, we noted that we believed that applying the provisions at § 422.514(h) to D-SNPs where there is an affiliated PIHP or PAHP could create incentives that are disruptive yet do not significantly further the goals of our proposals. As a result, we did not extend the enrollment limitation policies in § 422.514(h)(1) and (2) beyond Medicaid MCOs or beyond D-SNPs that enroll full-benefit dually eligible individuals, meaning that an MA organization offering a D-SNP in the same area where it, its parent organization, or an entity (or entities) that share a parent organization with the MA organization contracts with the State only as a PIHP or PAHP, would not be subject to the enrollment limitations at §§ 422.503(b)(8), 422.504(a)(20), or 422.514(h). Following the reasoning from the April 2024 final rule, D-SNPs with an affiliated PIHP or PAHP not subject to § 422.514(h) would have no need to take advantage of the proposed exception at § 422.514(h)(3)(iii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             Frequently Asked Questions (FAQs) and Enrollment Scenarios for § 422.514(h). Found at: 
                            <E T="03">https://www.cms.gov/files/document/cy2025madsnpsfaqs.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>We would also like to take this opportunity to note that if the exception we are finalizing at § 422.514(h)(3)(iii) is applicable to a D-SNP, the State in the State Medicaid agency contract should, through existing requirements at § 422.107(c)(2), specify if there must be a separate PBP for enrollees who are enrolled in Medicaid FFS.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters recommended that CMS provide technical assistance to States and urged CMS to produce enrollee-facing materials for individuals to understand their D-SNP enrollment choices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestion. We intend to continue to provide technical assistance on all aspects of D-SNP policy, including implementation of § 422.514(h), to interested States. We will update CMS-produced enrollee-facing materials with appropriate information reflecting the exceptions to § 422.514(h) finalized in this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the proposed exception at § 422.514(h)(3)(v), which would exempt MA organizations operating in U.S. Territories that have not adopted MSP from the requirements at § 422.514(h)(1)(i). Some commenters noted that this proposed exception recognized the unique Medicare and Medicaid landscapes in the U.S. Territories, including them not having adopted MSP and using their MA rebate to reduce Part B premiums and provide supplemental benefits. Several commenters mentioned that the proposed exception would maintain beneficiary choice, minimize beneficiary disruption, preserve operational flexibility in the Puerto Rico D-SNP market, in particular. A few of these commenters suggested that CMS consider other standards to trigger the exception to § 422.514(h)(1)(i), allowing the proposed exception to still apply should Puerto Rico adopt MSP in the future. A commenter offered the example of CMS applying the proposed exception in regions where state or local law requires D-SNPs to be fully integrated.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these perspectives and agree that the unique landscape in the U.S. Territories, including Puerto Rico, necessitates the proposed exception from the requirements at § 422.514(h)(1)(i). Without the proposed exception, beginning in contract year 2027, the MA organizations offering D-SNPs to full-benefit dually eligible individuals in the U.S. Territories that have not adopted MSP could only offer, or have a parent organization or share a parent organization with another MA organization that offers, one D-SNP for full-benefit dual eligible individuals. We believe that triggering the proposed exception to § 422.514(h)(1)(i) based on participation in MSP is appropriate since should a U.S. Territory, such as Puerto Rico, adopt MSPs there would be less need for D-SNPs to differentiate their plan benefit packages by level of Part B premium reduction amount and supplemental benefits. We are not persuaded to change the requirements for the proposed exception. We clarify that for purposes of this exception, U.S. Territory means any Territory of the United States, including the Commonwealth of Puerto Rico, the Virgin Islands of the United States, Guam, the Commonwealth of the Northern Mariana Islands, and American Samoa.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed the exception proposed in § 422.514(h)(3)(v), explaining that MA organizations that do not adopt MSP may have higher premiums and cost sharing, making care less affordable for dually eligible individuals. The commenter further stated that allowing MA organizations to offer multiple D-SNPs in the same service area could cause market confusion and lead to less robust plan benefit packages, forcing individuals to choose between the benefits they need in different plans based on affordability rather than one plan that offers all services needed.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Given the unique landscape of the U.S. Territories with no adoption of MSPs, we believe more flexibility is needed to differentiate D-SNP plan benefit packages. We believe the benefits of additional differentiation by level of Part B premium reduction and supplemental benefits outweigh the additional plan benefit packages full-benefit dually eligible individuals would need to review. We will continue to monitor the D-SNP market in the U.S. Territories and consider future rulemaking, as needed.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Additionally, we received several comments that were out of scope of this proposal, including suggestions on how to support the success of D-SNPs in rural and remote areas, enrollment periods, arguments against exclusively aligned enrollment, upcoding and truncating services, requiring States to align enrollment timelines during the transition to integrated enrollment, and incorporating Federal quality reporting. We received a suggestion that the Medicaid FFS model should be required to coordinate care, but that the State remain responsible for coverage and reimbursement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their questions and concerns and appreciate the breadth of engagement. We appreciate the recommendations; however, these comments are outside the scope of this rulemaking. We will consider exploring opportunities for potential future rulemaking to address some of these issues.
                    </P>
                    <P>
                        After considering the comments we received and for the reasons outlined above and our responses to comments, we are finalizing our proposal with a few modifications. First, we are finalizing proposed language at § 422.107(d)(1)(i) with modifications to specify that such an exception is available to a HIDE SNP as well as a coordination-only D-SNP that operates in a State where the State Medicaid agency does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals. Second, we are finalizing portions of the language at § 422.514(h)(3)(iii) as proposed; this exception would allow an eligible MA organization, its parent organization, or an entity that shares a parent organization with the MA organization to offer one or more additional D-SNPs for full-benefit dually eligible individuals who are enrolled in Medicaid fee-for-service. We 
                        <PRTPAGE P="17538"/>
                        are also finalizing other modifications: we are removing the language referring to a “majority of” enrollees and replacing it with language specifying that (1) if the MA organization subject to § 422.514(h)(1) holds a State Medicaid agency contract with a State that does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals and (2) if the State Medicaid agency contract allows enrollment of full-benefit dually eligible individuals who are enrolled in Medicaid FFS, the MA organization may enroll in a HIDE SNP or coordination-only D-SNP, full-benefit dually eligible individuals who are enrolled in Medicaid FFS. We are also adding language stating that (3) D-SNPs may not enroll full-benefit dually eligible individuals who are enrolled in a Medicaid managed care organization that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization. Third, we are not finalizing the proposed language at 422.514(h)(3)(iv). Fourth, we are finalizing our exception to § 422.514(h)(3)(v) as proposed, which will be located at § 422.514(h)(3)(iv).
                    </P>
                    <HD SOURCE="HD2">D. Contract Modifications for D-SNPs Following State Medicaid Agency Contract Termination (§ 422.510)</HD>
                    <P>
                        MA organizations are required to have contracts with CMS to operate each year. Section 1857(h)(2) of the Act provides authority for the Secretary to immediately terminate a contract with an MA organization in instances where the Secretary determines that a delay in termination resulting from compliance with the procedures in section 1857(h)(1) of the Act would pose an imminent and serious risk to the health of enrolled Medicare beneficiaries. In the final rule titled “Medicare Program; Establishment of the Medicare+Choice Program,” which appeared in the 
                        <E T="04">Federal Register</E>
                         on June 26, 1998 (hereafter referred to as the June 1998 final rule; 63 FR 35018), we finalized regulations at § 422.510 which outline processes for terminations of contracts by CMS, while providing conditions in which contracts may be found terminable. Such conditions include failure to carry out the contract, carrying out the contract in a manner that is inconsistent with the efficient and effective administration of MA regulations, and no longer being able to meet the applicable conditions put forth in MA regulations. In the decades since this rule was first finalized, we have continued to refine the conditions in which CMS may terminate an MA contract at § 422.510 and elsewhere in Part 422.
                    </P>
                    <P>
                        D-SNPs are MA plans that coordinate the delivery of Medicare and Medicaid services for individuals who are eligible for such services and enrolled in the plan. In addition to the standard contract an MA organization must have with CMS to operate, per section 1859(f)(3)(D) of the Act, MA organizations offering D-SNPs must also have a contract with the State Medicaid agency to provide benefits, or arrange for benefits to be provided, for individuals entitled to Medicaid. Because D-SNPs are required to have State Medicaid agency contracts (SMACs), States have significant control over the availability of D-SNPs in their markets given the State's discretion in contracting with D-SNPs in combination with the State's control over its Medicaid program. We discussed this relationship between States and MA organizations in the final rule titled “Medicare Program; Contract Year 2023 Policy and Technical Changes to the Medicare Advantage and Medicare Prescription Drug Benefit Programs; Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency; Additional Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency,” which appeared in the 
                        <E T="04">Federal Register</E>
                         on May 9, 2022, specifically at 87 FR 27763.
                    </P>
                    <P>Because of the relationship between the State and the D-SNP, the provision and continuation of SMACs are sensitive to State policy changes and operational choices. To illustrate this, we look to Medicaid MCO procurement timelines and decisions. The timeline and duration for these procurements is distinct to each State and may operate off-cycle from MA contracting at the Federal level, meaning that if a State decides not to contract with a particular Medicaid MCO, which may occur off-cycle from the calendar year, such a procurement decision may require termination of a Medicaid MCO contract. Termination of the Medicaid MCO contract would trigger termination of the SMAC, if the terminating Medicaid MCO is an affiliated entity with a D-SNP that has a SMAC in effect.</P>
                    <P>As was noted earlier in this preamble, D-SNPs are statutorily required to have a SMAC to operate in a State. In the example given previously, if a Medicaid MCO that is an affiliated entity with a D-SNP loses a State procurement or otherwise has its Medicaid MCO contract terminated, the State also terminates the SMAC and the D-SNP cannot continue to operate. This action requires that the contract between the D-SNP and CMS be terminated. As more States move towards integrated care and contract with Medicaid MCOs through the result of procurements, we have encountered instances where a SMAC is terminated by a State during the plan year. In those instances, CMS has worked with the respective State and the MA organization whose SMAC is being terminated to mutually terminate the contract per § 422.508, a process by which CMS, the State and the D-SNP agree on a timeline for termination and the provision of notice to enrollees of such termination, in an effort to create a smoother transition to an alternative plan for the plan's enrollees.  </P>
                    <P>However, an MA organization with a terminating SMAC is not required to seek a mutual termination of its MA contract with CMS. Absent the cooperation of the MA organization to mutually terminate in situations where the MA organization no longer holds a SMAC with the State, we are concerned that enrollees may experience harm by losing access to their integrated care, including access to known providers and care plans, as the D-SNP in which they are enrolled is no longer able to provide benefits, or arrange for benefits to be provided, for individuals entitled to Medicaid. In these instances, CMS will need to seek immediate termination to protect beneficiaries.</P>
                    <P>At § 422.510(a)(4), we first proposed to add a new paragraph (xvii) to establish that CMS may terminate a contract if the MA organization is no longer eligible to offer a D-SNP because the MA organization does not hold a contract with the State Medicaid agency consistent with § 422.107(b). Our goal in adding this new clause was to codify that the loss of a SMAC constitutes a valid basis for contract termination under CMS authority per section 1859(f)(3)(D) of the Act.</P>
                    <P>
                        Secondly, at § 422.510(b)(2)(i), we proposed to add paragraph (D) to state that the procedures specified in paragraph (b)(1), related to when CMS notifies the MA organization and when the MA organization must notify its enrollees and the general public, do not apply if the contract is being terminated based on the proposed addition of § 422.510(a)(4)(xvii). We proposed that when a D-SNP contract is terminated because the State has terminated the affiliated contract with the Medicaid MCO or the State has terminated the SMAC, it is cause for CMS to make the MA contract termination immediate. When a State terminates the Medicaid MCO affiliated with the D-SNP or terminates the SMAC, D-SNP enrollees who are otherwise entitled to medical 
                        <PRTPAGE P="17539"/>
                        assistance under a State plan under title XIX of the Act would be in jeopardy of not having access to the Medicaid services to which they are entitled, given that, as required by § 422.2, D-SNPs coordinate the delivery of Medicare and Medicaid services for eligible individuals and may provide coverage of Medicaid services. It is our belief that a delay in D-SNP contract termination could disrupt access to Medicaid benefits for those who are eligible, which would pose an imminent and serious risk to the health of the organization's enrollees, rising to the standard put forth in section 1857(h)(2) of the Act and warranting immediate termination of contract by CMS. We stated that where the MA organization does not agree to a mutual termination in coordination with the termination of the affiliated Medicaid MCO contract and/or SMAC, an immediate termination would be appropriate. However, we noted that our proposed amendments to §§ 422.510(a)(4)(xvii) and (b)(2)(i)(D) did not preclude a MA organization from seeking termination of a contract by mutual consent, per § 422.508.
                    </P>
                    <P>We noted that when an MA organization has multiple plans under one contract, per § 422.503(e) CMS may sever the D-SNP from the rest of the contract, in effect allowing CMS to renew only the portion of the contract that does not include the D-SNP affiliated with the terminated SMAC.</P>
                    <P>Proposed § 422.510(b)(2)(i)(D) would codify the process of immediate termination of contract by CMS when the D-SNP does not have a SMAC. We stated that the MA organization in this situation does not need and would not benefit from an opportunity to develop and implement a corrective action plan as required at § 422.510(c)(1) given that the only way to correct the issue would be to execute a SMAC with the State. States have the ability to issue corrective action plans to the D-SNPs with whom they hold contracts. Many States, in their SMACs, include language to this effect. Additionally, as in the example given previously, if a Medicaid MCO that is an affiliated entity with a D-SNP loses a State procurement, the State also terminates the SMAC. In either of these instances, allowing D-SNPs the opportunity to develop and implement a corrective action plan per § 422.510(c)(1) would not provide the D-SNP with an avenue to correct any underlying issue that resulted in the State's termination of the SMAC. The SMAC termination, including any related opportunity to pursue a corrective action plan offered by the State, will have already occurred by the time the MA contract is terminated. Moreover, State procurement decisions operate separately from MA contracting decisions through CMS and would not be amenable to a cure or a corrective action plan as described in § 422.510(c)(1). Furthermore, any further delay in termination of the D-SNP contract poses imminent and serious risk to the health of the organization's enrollees as previously described in this preamble, rising to the standard put forth in section 1857(h)(2) of the Act. As such, we proposed that termination of a SMAC be included as an exception to the opportunity for plans to develop and implement a corrective action plan, at § 422.510(c)(2)(iv).</P>
                    <P>We requested comment on this proposal, including but not limited to whether this package of provisions would accomplish the goals we have laid out in this preamble and whether there should be any other additional modifications to consider.</P>
                    <P>We received the following comments on this proposal and respond to them below:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported CMS' proposal to codify in regulation at § 422.510(a)(4) that CMS may terminate a contract if the MA organization is no longer eligible to offer a D-SNP because the MA organization does not hold a contract with the State Medicaid agency consistent with § 422.107(b). Commenters expressed their appreciation for CMS clarifying the administrative process in such situations and stated that the proposed provision would provide clarity and codify necessary Federal authority when State contract terminations occur off-cycle from MA contracting.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support of this proposal and agree that the proposed language provides clarity on the administrative process when an MA organization is no longer eligible to offer a D-SNP due to not holding the required SMAC.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters opposed our proposal, stating that immediate terminations would cause disruption of care for vulnerable populations and create obstacles for beneficiaries to transition to new plans. Commenters further opined that CMS should establish reasonable transitional periods to ensure beneficiaries' continued access to medical services.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' concern for possible disruption of care and beneficiary well-being. We would like to reiterate that the purpose of this proposal was to codify that loss of a SMAC is a valid basis for contract termination under CMS authority per section 1859(f)(3)(D) of the Act. As we discussed in the preamble to the Contract Year 2027 proposed rule, in some instances where a SMAC was terminated by a State during the plan year, CMS has worked with the respective State and the MA organization whose SMAC is being terminated to mutually terminate the contract per § 422.508. This is a process by which CMS, the State and the D-SNP are able to mutually agree on a timeline for termination and the provision of notice to enrollees of such termination, in an effort to create a smoother transition to an alternative plan for the plan's enrollees. (90 FR 54976). This process will continue to be available. Our goal in adding new (xvii) at § 422.510(a)(4) is to establish a an express pathway by which CMS may immediately terminate contracts based on termination of a SMAC, since, as discussed in preamble to the Contract Year 2027 proposed rule, an MA organization with a terminating SMAC is not required to seek a mutual termination of its MA contract with CMS. (90 FR 54977). Our proposed language does not preclude an eligible plan from seeking mutual termination, per § 422.508. We believe that where the MA organization does not agree to a mutual termination in coordination with the termination of the affiliated Medicaid MCO contract and/or SMAC, an immediate termination would be appropriate and could limit potential disruption of beneficiary access to integrated care.
                    </P>
                    <P>Further, we would like to take the opportunity to clarify that while we refer to this process as an “immediate termination,” as stated previously in this section and in the Contract Year 2027 proposed rule, we generally receive advance notice when a State is terminating or ending a Medicaid MCO contract or their SMAC contract. In instances where an MA organization does not agree to a mutual termination, or where the timeline of a mutual termination would pose risks to beneficiaries, an immediate termination allows us to accommodate an orderly shutdown of operations. An immediate termination does not mean that a termination would occur without notice but rather allows for a more expedited process when necessary to protect enrollee health and safety.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed their view that the provision that was proposed was too broad. Commenters believed that there was not a clear enough connection between the preamble language and the regulatory text, stating that the preamble language 
                        <PRTPAGE P="17540"/>
                        that used Medicaid MCO procurement timelines presented a narrower scope than the language proposed in regulation at § 422.510(a)(4)(xvii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback on this, though we respectfully disagree. In the Contract Year 2027 proposed rule, we emphasize that D-SNPs are statutorily required to have a SMAC to operate in a State per section 1859(f)(3)(D) of the Act. In the preamble to the Contract Year 2027 proposed rule, we used Medicaid MCO procurement timelines as an example to illustrate how the relationship between the State and the D-SNP and the provision and continuation of SMAC, are sensitive to State policy changes and operational choices. (90 FR 54976) However, our use of State procurement decisions as an example of a scenario in which a D-SNP may lose its SMAC does not mean that that is the only process by which a SMAC can be terminated, or in turn, an MA contract can be terminated. Ultimately, per § 422.107(a), a SMAC is a contract between an MA organization and the State Medicaid agency. If the State or the MA organization terminate the contract, then the MA organization is statutorily prohibited from operating that D-SNP in the State.
                    </P>
                    <P>
                        Further, in the Contract Year 2027 proposed rule, we pointed to the final rule titled “Medicare Program; Contract Year 2023 Policy and Technical Changes to the Medicare Advantage and Medicare Prescription Drug Benefit Programs; Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency; Additional Policy and Regulatory Revisions in Response to the COVID-19 Public Health Emergency,” which appeared in the 
                        <E T="04">Federal Register</E>
                         on May 9, 2022, specifically to draw attention to previous preamble that discussed how States have significant control over the availability of D-SNPs in their markets. (see 90 FR 54976 (citing 87 FR 27763)) Therefore, we do not believe there to be a mismatch between our proposed regulatory text and the preamble in the Contract Year 2027 proposed rule.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments objecting to the proposed provision, stating that while the regulatory language ties immediate termination to the loss of a SMAC, the preamble suggests that CMS intends to apply immediate termination authority when an affiliated Medicaid MCO contract is terminated, even where the SMAC itself remains in effect. Commenters suggested that termination of the affiliated Medicaid MCO contract would not necessarily prevent the D-SNP from continuing to meet its obligations to coordinate Medicare and Medicaid benefits under § 422.2 or from supporting CMS' broader goals of continuity of coverage and beneficiary stability. Other commenters suggested that this proposal should only apply to AIP D-SNPs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for engaging with this proposal. As we explained in the Contract Year 2027 proposed rule, termination of the Medicaid MCO contract would trigger termination of the SMAC, if the terminating Medicaid MCO is an affiliated entity with a D-SNP that has a SMAC in effect (90 FR 54976). If the Medicaid MCO is terminated and is not an affiliated entity with a D-SNP, then it would not trigger a SMAC termination, since there would be no SMAC to terminate. Additionally, we respectfully disagree with the commenters that suggest that this proposal only be applicable to AIP D-SNPs. Per section 1859(f)(3)(D) of the Act, all MA organizations offering D-SNPs must have a contract with the State Medicaid agency to provide benefits, or arrange for benefits to be provided, for individuals entitled to Medicaid. Therefore, this policy would apply to all D-SNPs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters opined on the concept of immediate termination. Commenters noted that immediate termination of a D-SNP contract has the potential to increase the risk of beneficiary confusion or disruption in care and access, and that alternatively, mutual termination allows CMS, States, and MA organizations to prepare for enrollee transitions and reduce care disruptions. Other commenters recommended that CMS wait until the end of the plan year for a contract termination to take effect, or at the very least, CMS should work closely with the State Medicaid agencies to determine a reasonable termination date and consider defining “immediate” as a mutually agreed upon termination date between CMS and the D-SNP. Other commenters encouraged CMS to avoid immediate contract terminations and only invoke the ability to immediately terminate a D-SNP contract after significant efforts have been made to collaborate with the State Medicaid agency and the respective MA plan.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' concern and share their interest in minimizing risk of beneficiary confusion or disruption in care and access. As discussed previously in this preamble, the preamble to the Contract Year 2027 proposed rule included reference to actual instances where a SMAC has been terminated by a State during the plan year, and CMS has worked with the respective State and the MA organization whose SMAC was being terminated to mutually terminate the contract per § 422.508. This is a process by which CMS, the State and the D-SNP are able to agree on a timeline for termination and notice to enrollees of such termination, in an effort to create a smooth transition to an alternative plan for the plan's enrollees (90 FR 54976). Our goal in proposing paragraph (xvii) at § 422.510(a)(4) is to codify an express pathway by which CMS may immediately terminate contracts based on termination of a SMAC, since, as discussed in preamble to the Contract Year 2027 proposed rule, an MA organization with a terminating SMAC is not required to seek a mutual termination of its MA contract with CMS (90 FR 54977). As stated previously in this section, an immediate termination allows for a more expedited process when necessary to protect enrollee health and safety and accommodate an orderly shutdown of operations.
                    </P>
                    <P>Our intent is to minimize enrollee disruption to the extent possible and collaborate with the State Medicaid agency and the respective MA plan in instances where a contract must be terminated. Our proposed language does not preclude an eligible plan from seeking mutual termination, per § 422.508, which would be our preference, and we welcome working with State Medicaid agencies and plans to minimize enrollee disruption where possible.</P>
                    <P>
                        <E T="03">Comment:</E>
                         We received many comments regarding the relationship between States and plans. Several commenters supported the overall proposal, noting that finalizing such a provision would improve a State's ability to engage in D-SNP oversight or empower States to have more control over which D-SNPs are offered in their State and support further Medicare-Medicaid integration and increased enrollment in integrated D-SNPs. These commenters noted that when plan performance leads to low quality of care, States should be able to terminate that D-SNP. A few commenters objected to our proposal, opining that the proposed provision could provide States with additional motivation to negotiate midyear changes to the terms of the SMAC with the penalty of rescinding the SMAC if the new terms are not accepted. The commenters strongly urged CMS to view this proposal considering the negotiation dynamics between health plans and States.
                        <PRTPAGE P="17541"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' thoughts on this matter. However, we would like to take this opportunity to underscore that this proposed language does not confer any new or different power on the State with regard to their ability to contract with D-SNPs. As discussed in preamble to the Contract Year 2027 proposed rule, in addition to the standard contract an MA organization must have with CMS to operate, per section 1859(f)(3)(D) of the Act, MA organizations offering D-SNPs must also have a contract with the State Medicaid agency to provide benefits, or arrange for benefits to be provided, for individuals entitled to Medicaid (90 FR 54976). Federal requirements for SMACs are codified in CMS regulations at § 422.107, but as stated at § 422.107(a), the SMAC is an agreement between an MA organization and the State Medicaid agency. At § 422.510(a)(4), we proposed to add a new paragraph (xvii) to establish that CMS may terminate a contract if the MA organization is no longer eligible to offer a D-SNP because the MA organization does not hold a contract with the State Medicaid agency consistent with § 422.107(b). We note that under § 422.510(a)(4)(ix), CMS already has the authority to terminate a contract for failure to comply with regulatory requirements in 42 CFR part 422. Our goal in adding this new clause is to specifically codify that the loss of a SMAC constitutes a valid basis for contract termination under CMS authority per section 1859(f)(3)(D) of the Act. We did not propose nor are we finalizing any new language with regard to how SMACs are negotiated, carried out, or entered into.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters opposed our proposal to not apply noticing requirements if CMS executes an immediate contract termination. Commenters noted that noticing requirements could help to avoid beneficiary confusion, and immediate termination of a D-SNP contract could create significant beneficiary disruption, especially if termination occurs before enrollment transitions or communications are complete. Another commenter recommended that CMS include some form of beneficiary notification requirement even if that process must be abridged and aligned with State Medicaid notification requirements in the circumstance of an immediate contract termination. Commenters mentioned that contract terminations should be implemented with appropriate transition protections to preserve beneficiary stability.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their responses and appreciate the attention regarding enrollees in a terminating D-SNP contract. We reiterate our previous responses to comments where we noted that our proposed language at § 422.510 does not preclude an eligible D-SNP from seeking mutual termination, per § 422.508, and we prefer working with State Medicaid agencies and D-SNPs on mutual terminations to minimize enrollee disruption, where possible. However, as an MA organization with a terminating SMAC is not required to seek a mutual termination of its MA contract with CMS, we proposed language that would codify CMS's ability to provide an immediate termination of the contract the D-SNP has with CMS. In an instance where an MA organization with a terminating SMAC does not seek mutual termination when the affiliated Medicaid MCO contract and/or SMAC terminates and CMS immediately terminates the MA organization's MA contract, pursuant to 42 CFR 422.510(b)(2)(iii), CMS notifies the MA organization's Medicare enrollees in writing of CMS's decision to terminate the MA organization's contract. This notice occurs no later than 30 days after CMS notifies the plan of its decision to terminate the MA contract. CMS simultaneously informs the Medicare enrollees of alternative options for obtaining Medicare services, including alternative MA organizations in a similar geographic area and original Medicare.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters suggested that CMS align the effective date of the Medicare contract termination with the SMAC termination date established by the Medicaid agency and consult with the Medicaid agency when such terminations occur.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their consideration for the operational aspects of this policy proposal. We reiterate our previous responses to comments where we noted that our proposed language at § 422.510 does not preclude an eligible D-SNP from seeking mutual termination, per § 422.508, where applicable, and we welcome working with State Medicaid agencies and plans on mutual terminations to minimize enrollee disruption where possible. However, an MA organization with a terminating SMAC is not required to seek a mutual termination of its MA contract with CMS, and there are circumstances in which a State may immediately terminate a SMAC, such as where there is beneficiary harm. Thus, we proposed language that would codify CMS's ability to provide an immediate termination of the contract the D-SNP has with CMS, as it is our belief that a delay in D-SNP contract termination could disrupt access to Medicaid benefits for those who are eligible. (90 FR 54978)
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters encouraged CMS to work with States to better structure Medicaid procurement opportunities. Commenters noted that State Medicaid procurement processes are not subject to Federal procurement rules or CMS oversight and can be opaque. Another commenter suggested that for a D-SNP designated as an AIP, where there is an aligned Medicaid MCO or D-SNP that is implemented after a procurement award, there be a run out period to prevent any unintended beneficiary disruption.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the opinions expressed by commenters. State Medicaid procurement processes are not subject to Federal procurement rules or CMS oversight, and thus these suggestions are outside of our purview. If a State requested our input on their Medicaid MCO procurement timelines and processes, we would provide any insight we may have at that time.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a few comments that were out of scope. Some commenters expressed concern regarding how the proposed provision would affect MA contract lockout periods for the terminated plan, suggesting that CMS should have the discretion to not impose a lockout period at all.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestion. We believe the commenters are referring to regulations, such as those at § 422.502, where CMS may deny an application for a new MA contract or service area expansion based on the applicant's substantial failure to comply with the requirements of the Part C program. The parameters for application denials are outside the scope of the proposed regulation.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined above and our responses to comments, we are finalizing language at § 422.510(a)(4)(xvii), (b)(2)(i)(D), and (c)(2)(iv) as proposed.  </P>
                    <HD SOURCE="HD2">E. Limitation on D-SNP-Only Contracts Submitting Materials Under the Multi-Contract Entity and Multi-Plan Process (§§ 422.2261 and 423.2261).</HD>
                    <P>
                        Sections 422.2261(a) and 423.2261(a) require MA organizations and Part D sponsors to submit all marketing materials, all election forms, and certain designated communication materials for CMS review. These regulations state that the HPMS Marketing Module is the primary system of record for the collection, review, and storage of materials that must be submitted for 
                        <PRTPAGE P="17542"/>
                        CMS review. They also specify that materials must be submitted to the HPMS Marketing Module by the MA organization or Part D sponsor or, where materials have been developed by a Third Party Marketing Organization (TPMO) for multiple MA organizations or plans, by a TPMO with prior review of each MA organization on whose behalf the materials were created or will be used. In addition, §§ 422.2262(d) and 423.2262(d) describe how MA organizations and Part D sponsors must use a standardized method of identification for oversight and tracking for materials received by beneficiaries including the MA organization's contract or Multi-Contract Entity (MCE) number (such as an “H” number for MA plans or “Y” number for an MCE).
                    </P>
                    <P>Under § 422.107(e), a State Medicaid agency may require MA organizations offering D-SNPs with exclusively aligned enrollment to do both of the following: (1) apply for, and seek CMS approval to establish and maintain, one or more MA contracts that only include one or more D-SNPs with a service area limited to the State; and (2) use required materials that integrate Medicare and Medicaid content including, at a minimum, the Summary of Benefits, Formulary, and combined Provider and Pharmacy Directory that meets Medicare and Medicaid managed care requirements consistent with applicable regulations in parts 422, 423, and 438 of Title 42 of the CFR. We refer to MA contracts that only include one or more D-SNPs with a service area limited to the State as D-SNP-only contracts. If a State elects to require D-SNP-only contracts under § 422.107(e)(1), per § 422.107(e)(3)(i), CMS grants State Medicaid agency officials access to HPMS for purposes of oversight and information sharing for these D-SNP- only contracts. This State oversight includes access to the HPMS Marketing Module for purposes of reviewing materials submitted by D-SNP-only contracts. These States only have access to review materials submitted under the contract number (H number) in HPMS for D-SNP-only contracts.</P>
                    <P>For material oversight, per § 438.10(c)(5), States are required to ensure, through their Medicaid managed care contracts, that each managed care organization (MCO), prepaid inpatient health plan (PIHP), prepaid ambulatory health plan (PAHP), and primary care case management (PCCM) entity provides the information to each enrollee consistent with § 438.10(f)-(i), as applicable. In addition, per § 438.104(b), MCO, PIHP, PAHP, PCCM, or PCCM entities cannot distribute marketing materials without first obtaining State approval. The entity's contract with the State must also specify the methods by which the entity ensures that marketing, including plans and materials, is accurate and does not mislead, confuse, or defraud the beneficiaries or the State Medicaid agency.</P>
                    <P>Since contracts with exclusive alignment of Medicare and Medicaid must meet the material requirements of both CMS and the State, prior to the adoption of § 422.107(e), MA organizations were required to submit materials to the State and CMS separately. However, States requiring D-SNP-only contracts have access to HPMS for reviewing these materials, and they can require the MA organizations offering D-SNP-only contracts to submit materials in the HPMS marketing module for State review. This State access decreases plan burden by allowing the D-SNP to submit the material once in HPMS for concurrent joint review by CMS and the State, as applicable, rather than having to separately submit materials to the State for review and then to CMS. This can also shorten the total review time for the MA organization and give it more time to meet tight timeframes for releasing materials to enrollees.</P>
                    <P>If an MA organization were to submit a material under an MCE number that applies to multiple contracts, the applicable State Medicaid agency would not be able to either view or review that material in the HPMS Marketing Module. States only have access to information in HPMS for the specific D-SNP-only contracts in their State. Because MCE numbers cover multiple contracts across multiple States, CMS doesn't allow State staff to access materials submitted under an MCE number, even if an MA organization includes materials for their State. MA organizations could potentially submit a substantial number of materials in HPMS under the MCE number, including their D-SNP-only contracts, but the State would not be able to view any of them due to their submission under the MCE number. To address this challenge, CMS has programmed the HPMS marketing module so that D-SNP-only contracts cannot submit materials under an MCE number. In addition, States with D-SNP-only contracts have added language in their SMACs to prohibit submission of materials in the HPMS Marketing Module under the MA organization's MCE number. Instead, States are requiring that MA organizations with D-SNP-only contracts submit materials for review under their contract ID number.</P>
                    <P>To ensure that D-SNP-only contracts are meeting the material requirements of both Medicare and Medicaid, we proposed to clarify that MA organizations with D-SNP-only contracts cannot submit materials using the MA organization's MCE number for D-SNP-only contracts, nor can TPMOs submit materials on behalf of the MA organization for D-SNP-only contracts using an MCE number. This requirement applies to all plan benefit packages within D-SNP-only contracts under § 422.107(e)(1). Since States have already been requiring this approach through their SMACs and the HPMS Marketing Module is set up to prevent D-SNP-only contracts from submitting materials under an MCE number, we stated that we do not expect this update to add burden for any MA organizations; the current process will not change.</P>
                    <P>Under our authority to interpret, implement, and carry out the Part C and D programs under sections 1851(h), 1851(j), 1852(c), 1860D-1(b)(1)(B)(vi), 1860D-4(a), and 1860D-4(l) of the Act, we proposed to add a requirement at §§ 422.2261(a)(3) and 423.2261(a)(3) that MA organizations offering D-SNPs with exclusively aligned enrollment subject to § 422.107(e) must submit all materials for the contract in HPMS under the MA organization's contract number. MA organizations and TPMOs may not submit materials for the contract under the organization's MCE number as described in §§ 422.2262(d)(2)(i) and 423.2262(d)(2)(i). We received the following comments on our proposal and our responses are as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported our proposal at §§ 422.2261(a)(3) and 423.2261(a)(3). They appreciated that it supports joint reviews of materials and integrated care. They stated it would allow States to provide better oversight of D-SNP-only contracts and take actions necessary to ensure enrollees receive quality materials. A commenter noted that the requirement would help ensure that MA organizations can better meet tight deadlines to provide materials to enrollees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support for our proposal to require that D-SNPs with exclusively aligned enrollment subject to § 422.107(e) submit all materials for the contract in HPMS under the MA organization's contract number. We believe that the proposal will help clarify the material submission process in HPMS for D-SNP-only contracts and help streamline the State and CMS material review process for these D-SNPs.
                        <PRTPAGE P="17543"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters suggested that CMS consider ways to encourage states to adopt consistent, streamlined review timelines to improve the timeliness of reviews. They noted inconsistent use of HPMS across States with some States implementing multi-step submission processes through both a State portal and HPMS. These commenters suggested that CMS consider a universal 45-day deeming period across all States and a 5-day file and use approach or a 10-day review period for all required materials. They also recommended increased education to States on how to use HPMS to improve their understanding and ability to review materials in HPMS as well as the ability for States to be exempt from the process if they choose.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their perspectives. Only those States with D-SNP-only contracts can utilize the joint review process in HPMS if they choose to do so. States are not required to utilize this process. Each State Medicaid program is different, so the States that do participate in the process can determine which materials they want to review and if they want to review them in 10 days or 45 days, or as file and use which are the same review periods as for other MA materials per §§ 422.2261(b) and 423.2261(b). This is similar to the review process used for Medicare-Medicaid Plans under the Financial Alignment Initiative demonstration. Also, for States utilizing the joint review process, we provide education on the use of HPMS marketing module annually and are available to provide technical assistance to States throughout the year. We will continue to provide this training and focus on areas where we find further education is needed.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that for States that have multiple plan benefit packages (PBPs) for the D-SNP-only contract, materials are submitted to the State for the D-SNP PBP designated as an AIP. These States do not require submission of materials when the PBP is not an AIP. The commenter also stated that HPMS's review is at the PBP level and not at the contract level. The commenter articulated that submitting materials for AIP PBPs and non-AIP PBPs when States do not need to review the non-AIP PBP materials can create an administrative burden for both plans and the State. The commenter noted that it would welcome working with CMS to improve the process going forward.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's perspective on this issue. It is true that MA organizations with D-SNP-only contracts must submit materials under the contract ID number in HPMS for all PBPs within the contract and that States with D-SNP-only contracts to date have chosen not to review the non-AIP PBP materials. However, the plans still must submit materials for every PBP within the contract for State review because there is no technical mechanism within HPMS to have the State only review one PBP within a contract and not the other PBP. As a workaround, States have been approving the non-AIP PBP materials and noting that they did not review the remaining PBP materials since they are for a non-AIP PBP.
                    </P>
                    <P>While this is an extra step for States, the majority of the material categories for D-SNP-only contract States are submitted at the contract level and not PBP level. For example, for the State of South Carolina, MA organizations with D-SNP-only contracts can submit materials for 12 out of 47 material categories at the PBP level. Materials for the other 35 categories are submitted at the contract ID level. In addition, for any non-AIP PBPs, D-SNPs only have to submit into HPMS those materials for which CMS review is required for MA plans. There are 5 material categories that CMS reviews for MA where plans can submit materials at the PBP level. Two of these material categories are for errata documents that MA plans rarely submit. As a result, we understand that while this process may be an extra step for States, the extent of the PBP level submissions is limited. We appreciate the commenter's offer to work with CMS to improve the process going forward.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS not require MA plans to file national D-SNP marketing materials that do not include State-specific elements in HPMS under each individual contract number. The commenter stated that this approach would result in multiple submissions of identical materials under different contract numbers and material IDs, significantly increasing the volume of duplicate materials subject to CMS review without corresponding regulatory benefit. The commenter also opined that managing feedback from multiple States while attempting to produce a single unified material would be operationally challenging and burdensome. The commenter noted that even if all States were to agree on a single document version through separate reviews, it remains unclear how plans should reflect multiple material IDs. The commenter recommended that CMS consider adding unique category codes or creating an AIP D-SNP MCE contract number that could be used for national AIP D-SNP materials that do not contain State-specific content. If CMS finalized this regulation as proposed, the commenter suggested that CMS enhance HPMS to allow users to select multiple States from a dropdown menu and bundle submissions for standard templates, rather than requiring individual State submissions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's perspective on this issue. For D-SNP-only contracts, States can only review those materials that are submitted under the D-SNP-only contracts that are located within their State. While a specific material may not contain State-specific content, we believe that every State has a right to review all materials submitted for the contract if they choose to do so. We understand that this may result in duplicate submissions of certain materials, however, organizations have a contract with both CMS and the State Medicaid agency for these exclusively aligned plans, and every State has different areas of focus for materials. If there are materials reviewed under multiple contracts that have no difference after review, the MA organization can add multiple material ID numbers to the bottom of the material. As a result, we disagree with adding unique category codes to HPMS or creating an AIP D-SNP MCE contract number. We will consider for the future the commenter's recommendation to allow MA organizations to select multiple States from a drop-down menu and bundle submissions for standard templates in HPMS.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether “MA organizations offering D-SNPs with exclusively aligned enrollment subject to § 422.107(e) must submit all materials for the contract in HPMS under the MA organization's contract number” will be the exact language used for the proposed requirements at §§ 422.2261(a)(3) and 423.2261(a)(3). The commenter believed the intent to be “subject to § 422.107(e)” was meant to be “subject to § 422.107(e)(1)” as the former largely focuses on the relationship between State Medicaid agencies and CMS, whereas the latter is specific to MA organizations with exclusively aligned enrollment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their question. We will be finalizing the regulation text as proposed as we believe that it is beneficial to use § 422.107(e) as it describes all aspects of D-SNP-only contracts, such as State access to HPMS which allows for joint reviews of materials, whereas § 422.107(e)(1) only includes some of 
                        <PRTPAGE P="17544"/>
                        the steps that States must take for D-SNP-only contracts in the State.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters provided comments that were out of scope of this proposed provision. Commenters requested that CMS require all D-SNPs to register under their own contract number and not be grouped together with other D-SNPs or MA plans. The commenter suggested that such a structure would allow for greater transparency for States, as well as better monitoring for compliance and better-quality metric reporting. The commenters asserted that combining D-SNPs with other plans in the same contract number muddles data and accountability.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their suggestion. We appreciate these recommendations; however, these comments are outside the scope of this rulemaking. We will consider exploring opportunities for potential future rulemaking to address some of these issues.
                    </P>
                    <P>After considering the comments we received and additional review, we are finalizing the provisions proposed at §§ 422.2261(a)(3) and 423.2261(a)(3) with an update. In the Contract Year 2027 proposed rule, we inadvertently referred to the number for TPMO submissions in HPMS as the MCE number whereas it is a Multi-Plan number. We are correcting this technical error to clarify that MA organizations may not submit materials for the contract under the organization's MCE number and third-party marketing organizations may not submit materials under the Multi-Plan number as described in §§ 422.2262(d)(2)(i) and 423.2262(d)(2)(i). This change does not alter the intended scope of the regulatory requirement.  </P>
                    <HD SOURCE="HD2">F. Request for Information: C-SNP and I-SNP Growth and Dually Eligible Individuals</HD>
                    <P>In the Contract Year 2027 proposed rule (90 FR 54978 through 54984), we included a request for information regarding growth of chronic condition special needs plans (C-SNPs) and institutional special needs plans (I-SNPs) and dually eligible enrollment in those plans. This section summaries the RFI.</P>
                    <P>Per the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (Pub. L. 108-173), chronic condition special needs plans (C-SNPs), dual eligible special needs plans (D-SNPs), and institutional special needs plans (I-SNPs) are MA plans that are specifically designed to provide targeted care and limit enrollment to special needs individuals. C-SNPs restrict enrollment to special needs individuals with specific severe or disabling chronic conditions as defined at § 422.2. The April 2024 final rule amended the definition of severe or disabling chronic conditions at § 422.2 by outlining the specific co-morbid and medically complex chronic conditions that qualify for C-SNP enrollment (89 FR 30661 through 30666). I-SNPs restrict enrollment to MA eligible individuals who meet the definition of institutionalized and institutionalized- equivalent per § 422.2. The April 2024 final rule added three additional I-SNP subtypes: facility-based institutional special needs plan (FI-SNP), hybrid institutional special needs plan (HI-SNP), and institutional-equivalent special needs plan (IE-SNP). (89 FR 30649 through 30653) D-SNPs are specialized MA plans for individuals who are entitled to medical assistance under a State plan under Title XIX, per § 422.2.</P>
                    <HD SOURCE="HD3">1. Growth in C-SNPs With High Proportion of Dually Eligible Enrollees</HD>
                    <P>The number of C-SNPs offered by MA organizations and the number of dually eligible individuals enrolled in C-SNPs increased from CY 2021 through CY 2025 as outlined at 90 FR 54979. Over the same timeframe, the number of C-SNPs with a high proportion of dually eligible enrollees increased as shown at 90 FR 54979 through 54980. Per § 422.514(d), we defined D-SNP look-alikes as non-SNP MA plans with 60 percent or more dually eligible enrollment. We used this threshold to identify C-SNPs in CY 2021 through CY 2025 with a similarly high level of dually eligible enrollees. At 90 FR 54979 through 54980, we provided more detail on C-SNPs with a high concentration of dually eligible individuals in California, Arizona, Illinois, and New Mexico given these States have the largest number of such C-SNPs during the CY 2021 through CY 2025 timeframe.</P>
                    <HD SOURCE="HD3">2. Growth in I-SNPs With High Proportion of Dually Eligible Enrollees</HD>
                    <P>At 90 FR 54981, we noted that compared to C-SNPs, the number of I-SNPs offered by MA organizations has remained relatively consistent in recent years. Dually eligible individuals represented the vast majority of I-SNP enrollees at approximately 90 percent of total enrollment each year. For a more detailed discussion of dually eligible individuals enrolled in I-SNPs, see 90 FR 54981.</P>
                    <HD SOURCE="HD3">3. Challenges With C-SNPs and I-SNPs With High Proportion of Dually Eligible Enrollees</HD>
                    <P>Dually eligible individuals encounter fragmentation in the health care system as they navigate the Medicare and Medicaid programs. CMS has been working to address these fragmented experiences through policies that integrate care for dually eligible individuals. Integrated care refers to delivery system and financing approaches that (1) maximize person- centered coordination of Medicare and Medicaid services; (2) mitigate cost- shifting incentives between the two programs; and (3) create a seamless experience for dually eligible individuals. Our efforts in recent years have increased opportunities for enrollment in D-SNPs that are aligned with Medicaid managed care plans operated through a common parent organization (integrated D-SNPs).</P>
                    <P>
                        The challenges with C-SNPs and I- SNPs enrolling high proportion of dually eligible individuals are similar to the challenges of D-SNP look-alikes. CMS established contracting limitations on D-SNP look-alikes at § 422.514(d) whereby CMS does not (a) enter into a contract for a new non-SNP MA plan that projects, in its bid submitted under § 422.254, that 60 percent or more of its enrollees are dually eligible or (b) renew a contract with a non-SNP MA plan that has 60 percent or more dually eligible enrollees. We established these contract limitations to address proliferation and growth of D-SNP look-alikes in the final rule titled “Medicare Program; Contract Year 2021 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, and Medicare Cost Plan Program,” which appeared in the 
                        <E T="04">Federal Register</E>
                         on June 2, 2020 (hereafter referred to as the June 2020 final rule; 85 FR 33805 through 33806) to ensure full implementation of requirements for D-SNPs, such as SMACs, a minimum integration of Medicare and Medicaid benefits, care coordination through health risk assessments (HRAs), and evidence-based models of care (MOCs). These requirements promote coordination of care. Additionally, the SMAC requirement allows States the flexibility to require greater integration of Medicare and Medicaid benefits from the D-SNPs in their markets. Through their annual SMACs, States are implementing intentional strategies to better coordinate care for dually eligible individuals.
                    </P>
                    <P>
                        As discussed in the Contract Year 2027 proposed rule at 90 FR 54982 
                        <PRTPAGE P="17545"/>
                        through 54983, C-SNPs could be serving as a workaround to Federal and State integration efforts. Like D-SNPs, C-SNPs and I-SNPs must have approved MOCs and develop HRAs and individualized care plans (ICPs), but C-SNPs and I-SNPs are not subject to State contracting requirements applicable to D-SNPs nor do they reflect the key elements of integrated care: maximized person-centered coordination of Medicare and Medicaid services; mitigation of cost-shifting incentives between the two programs; and a seamless experience for dually eligible individuals. Although research has not yet uniformly shown an advantage for dually eligible individuals enrolling in plans with Medicare and Medicaid integration, preliminary evidence suggests that dually eligible individuals enrolled in integrated plans, on average, experience, reduced emergency department and inpatient hospital admissions, fewer long-term nursing facility stays, greater use of patient care, and slightly better experience and clinical outcomes than those in non-integrated plans.
                        <SU>112</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             Roberts ET, Duggan C, Stein R, Jonnadula S, Johnston KJ, Figueroa JF. Quality, spending, utilization, and outcomes among dual-eligible Medicare-Medicaid beneficiaries in integrated care programs: a systematic review. JAMA Health Forum. July 2024. Available from: 
                            <E T="03">https://jamanetwork.com/journals/jama-health-forum/fullarticle/2821202;</E>
                             Feng Z, Wang J, Gadaska A, Knowles M, Haber S, Ingber M, Grouverman, V. Comparing Outcomes for Dual Eligible Beneficiaries in Integrated Care: Final Report, September 2021. Available from: 
                            <E T="03">https://aspe.hhs.gov/sites/default/files/documents/9739cab65ad0221a66ebe45463d10d37/dual-eligible-beneficiaries-integrated-care.pdf;</E>
                             and 
                            <E T="03">https://www.macpac.gov/wp-content/uploads/2019/07/Evaluations-of-Integrated-Care-Models-for-Dually-Eligible-Beneficiaries-Key-Findings-and-Research-Gaps.pdf;</E>
                             and MACPAC Evaluations of Integrated Care Models for Dually Eligible Beneficiaries: Key Findings and Research Gaps, August 2020. Available from: 
                            <E T="03">https://www.macpac.gov/wp-content/uploads/2019/07/Evaluations-of-Integrated-Care-Models-for-Dually-Eligible-Beneficiaries-Key-Findings-and-Research-Gaps.pdf.</E>
                        </P>
                    </FTNT>
                    <P>C-SNPs and I-SNPs are currently exempt from the D-SNP look-alike contracting limitations. As stated in the June 2020 final rule (85 FR 33813) and April 2024 final rule (89 FR 30722), we excluded SNPs from evaluation against the prohibition on D-SNP look-alikes. Our rationale for the exclusion was to allow for the predominant dually eligible enrollment that characterizes D-SNPs, I-SNPs, and some C-SNPs by virtue of the populations that the statute expressly permits each type of SNP to exclusively enroll. Nonetheless, we stated that we would monitor enrollment in other types of SNPs to assess whether such plans are structured primarily to serve dually eligible enrollees without meeting D- SNP requirements. In their comments on the Contract Year 2025 proposed rule (89 FR 30719), MACPAC suggested that we monitor growth in enrollment of dually eligible beneficiaries in other types of SNPs, including C-SNPs and I- SNPs, and identify any potential effects on integration efforts. The number of D-SNP look-alikes transitioning enrollees to C-SNPs has increased in recent years. That increase could, at least in part, be driven by the exclusion of C-SNPs from the D-SNP look-alike prohibition.</P>
                    <HD SOURCE="HD3">4. Potential Policy Changes for Comment Solicitation</HD>
                    <P>We solicited comments on potential policy changes to support integrated care and improved health outcomes given the significant growth of dually eligible individuals enrolling in C-SNPs and I-SNPs.</P>
                    <P>First, we solicited comment on establishing a SMAC requirement similar to the existing requirement for D-SNPs. We solicited comments on whether or not we should adopt a SMAC requirement for C-SNPs and/or I-SNPs with high concentrations of dually eligible individuals as well as potential Federal requirements for those SMACs.  </P>
                    <P>Second, we solicited comments on methods to increase care coordination for dually eligible individuals enrolled in C-SNPs and I-SNPs. At 90 FR 54983, we stated that we were considering whether to extend any of these existing D-SNP care coordination requirements to C-SNPs and I-SNPs given the high proportion of dually eligible individuals enrolled in these plans. We solicited comments on whether we should (a) adopt any new care coordination requirements for dually eligible C-SNP and/or I-SNP enrollees; (b) add any MOC requirements for these SNP types; and (c) what those care coordination or MOC requirements should include.</P>
                    <P>Third, we solicited comment on three approaches to applying the D-SNP look-alike contracting limitations at § 422.514(d) through (g) to C-SNPs. We solicited comments on the potential approaches to apply the D-SNP look-alike contracting limitations as is to C- SNPs and excluding partial-benefit dually eligible individuals from the 60-percent threshold calculation. We welcomed comments on the benefits and challenges of C-SNP enrollees transitioning to non-SNP MA plans and Original Medicare and a standalone Part D plan as well as other suggestions for potential transitions.</P>
                    <P>Fourth, we requested that stakeholders submit for our consideration any other policy suggestions that could help ensure that there are appropriate protections in place to support high-quality, integrated care for dually eligible enrollees given the increasing proportion of them enrolling in C-SNPs and I-SNPs.</P>
                    <P>Fifth, we welcomed comments on the policy ideas outlined in this section to help inform potential future regulatory action.</P>
                    <P>Finally, we noted our interest in how to support improved access to treatment and care coordination for individuals with mental health conditions or substance use disorders as we believe SNPs could be situated to perform a critical role in supporting the improvement of care provided to individuals with serious mental illness (SMI). We invited public comment on the difficulties of creating C-SNPs focused on these conditions, as well as recommended incentives, outcome- based measures, or strategies that would make it easier for MA plans to design and offer these plans. In addition, we welcomed comments on how other SNP types, such as D-SNPs and I-SNPs, are serving this population and what improvements could be made to ensure individuals with SMI are connected to appropriate services. We also invited comments on the advantages and disadvantages of dually eligible individuals with SMI receiving care through enrollment in a C-SNP where we would expect extra emphasis on addressing mental health needs versus through enrollment in a D-SNP that would coordinate Medicare and Medicaid benefits that may also be helpful in addressing mental health needs. Finally, CMS welcomed commenters to share any other considerations or regulatory changes they believe may be necessary to support the availability of high-quality SNPs to serve individuals with SMI.</P>
                    <P>We received numerous comments in response to this request for information from a broad array of stakeholders, reflecting the strong interest in the issue of C-SNP and I-SNP growth and enrollment of dually eligible individuals in those plans. We appreciate commenters sharing these perspectives. While we will not be responding to the comments submitted in this final rule, we will consider the comments and suggestions for future rulemaking.</P>
                    <HD SOURCE="HD1">VII. Reducing Regulatory Burden and Costs in Accordance With Executive Order (E.O.) 14192</HD>
                    <P>
                        As noted previously, we sought public input on approaches and opportunities to streamline regulations and reduce administrative burdens on providers, suppliers, beneficiaries, and other interested parties participating in 
                        <PRTPAGE P="17546"/>
                        the Medicare program. Please refer to the RFI at 
                        <E T="03">https://www.cms.gov/medicare-regulatory-relief-rfi</E>
                         and submit all comments via this link.
                    </P>
                    <HD SOURCE="HD2">A. Exclusion of Account-Based Medical Plans From Entities Required To Make Disclosures of Creditable Coverage (§ 423.56)</HD>
                    <P>
                        Section 1860D-13(b)(6)(B)(i) of the Act provides that each entity that offers prescription drug coverage of the type described in subparagraphs (B) through (H) of section 1860D-13(b)(4) of the Act shall provide for disclosure, to the Secretary and Part D eligible individuals, of whether the coverage is creditable coverage, that is, equals or exceeds the actuarial value of standard prescription drug coverage (as determined under section 1860D-11(c) of the Act), or whether such coverage is changed so it no longer meets such requirement. Section 1860D-13(b)(6)(B)(ii) of the Act requires such entities to disclose if coverage does not meet such requirement, and that the disclosure to Part D eligible individuals shall include information that there are limitations on the periods in a year in which the individual may enroll in Part D coverage, and that any such enrollment is subject to a Part D late enrollment penalty (LEP). In addition, section 1860D-13(b)(4)(H) of the Act provides the Secretary with the flexibility to identify “other coverage” that could be considered creditable coverage. The types of coverage that are subject to the creditable coverage requirements and the procedures to determine and document creditable status of prescription drug coverage were codified at § 423.56 in the final rule entitled “Medicare Program; Medicare Prescription Drug Benefit (Part D final rule)” that appeared in the January 28, 2005, 
                        <E T="04">Federal Register</E>
                         (70 FR 4532).
                        <SU>113</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2005/01/28/05-1321/medicare-program-medicare-prescription-drug-benefit.</E>
                        </P>
                    </FTNT>
                      
                    <P>
                        Section 1860D-13(b)(4)(C) of the Act includes Group Health Plans (GHPs) as entities that are required to provide creditable coverage disclosures. The statute states that GHPs include health benefits plans under chapter 89 of title 5 (commonly known as the Federal Employees Health Benefits Program) and qualified retiree prescription drug plans as defined at section 1860D-22(a)(2) of the Act. The term, “Group Health Plan” was codified at § 423.882 in the 2005 Part D final rule (70 FR 4577),
                        <SU>114</SU>
                        <FTREF/>
                         and this definition includes account-based medical plans such as health reimbursement arrangements (HRAs) as defined in Internal Revenue Service (IRS) Notice 2002-45, 2002-28 I.R.B. 93, health Flexible Spending Arrangements (FSAs) as defined in Internal Revenue Code (Code) section 106(c)(2), health savings accounts (HSAs) as defined in Code section 223, or an Archer MSA as defined in Code section 220, to the extent they are subject to ERISA as employee welfare benefit plans providing medical care (or would be subject to ERISA but for the exclusion in ERISA section 4(b) (29 U.S.C. 1003(b)) for governmental plans or church plans).
                    </P>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2005/01/28/05-1321/medicare-program-medicare-prescription-drug-benefit.</E>
                        </P>
                    </FTNT>
                    <P>Section 1860D-13(b)(6)(B)(i) of the Act requires “entities that offer prescription drug coverage” to provide for these creditable coverage disclosures to the Secretary and Part D eligible individuals, but account-based plans (for example, HRAs, FSAs, HSAs, etc.) do not actually offer prescription drug coverage; rather, they are arrangements created by employers and designed to provide individuals savings on healthcare costs through pre-tax contributions and reimbursements, that are often provided to supplement other coverage, such as another group health plan or individual market coverage. Therefore, the benefit design of account-based plans makes concepts, such as disclosure of creditable coverage, inapplicable to those arrangements.</P>
                    <P>
                        As an example, HRAs,
                        <SU>115</SU>
                        <FTREF/>
                         which are arrangements that are paid solely by the employer, reimburse employees only for their, their spouse's, and their dependents' medical care expenses 
                        <SU>116</SU>
                        <FTREF/>
                         (including premiums), provide reimbursements up to a maximum dollar amount, and carry forward unused balances in the arrangement from one year to the next. Individual Coverage HRAs (ICHRAs), which were more recently recognized by the Labor, Health and Human Services, and Treasury Departments in the June 20, 2019 final rule titled, “Health Reimbursement Arrangements and Other Account-Based Group Health Plans” (84 FR 28888),
                        <SU>117</SU>
                        <FTREF/>
                         are also a type of reimbursement arrangement; however, to receive reimbursements for medical care expenses from an ICHRA, employees and any covered dependents must actually be enrolled in individual health insurance coverage or Medicare Parts A and B, or Part C.
                    </P>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             HRAs were first recognized in 2002 in guidance—Internal Revenue Service (IRS), “Health Reimbursement Arrangements,” Notice 2002-45, at 
                            <E T="03">https://www.irs.gov/pub/irs-drop/n-02-45.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             IRC § 213; IRS, “Medical and Dental Expenses,” Publication 502, January 11, 2022, at 
                            <E T="03">https://www.irs.gov/pub/irs-pdf/p502.pdf;</E>
                             and IRS, Health Savings Accounts and Other Tax-Favored Health Plans, IRS Publication 969, February 11, 2021, p. 18, at 
                            <E T="03">https://www.irs.gov/pub/irs-pdf/p969.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             
                            <E T="03">https://www.govinfo.gov/app/details/FR-2019-06-20/2019-12571.</E>
                        </P>
                    </FTNT>
                    <P>HRAs, including ICHRAs, are group health plans that are not, as section 1860D-13(b)(6)(B)(i) of the Act requires, entities that offer prescription drug coverage. Comparing a reimbursement arrangement, such as an HRA, against the intricacies of a prescription drug plan, including whether the reimbursement provided equates to coverage that would be considered creditable (that is, offers coverage at least as good as the Medicare standard drug benefit), is not an `apples to apples' comparison because account-based plans are fundamentally different from prescription drug plans. While account-based plans generally only provide a financial benefit to employees, for example, tax savings, prescription drug coverage conveys numerous benefits to beneficiaries.</P>
                    <P>
                        As discussed previously, section 1860D-13(b)(6)(B)(i) of the Act requires that “entities that offer prescription drug coverage” must provide creditable coverage disclosures. Given that account-based entities do not offer such coverage, we proposed to revise § 423.56(b)(3) so that account-based entities are not required to provide the creditable coverage disclosures. Furthermore, requiring account-based plans, such as HRAs, including ICHRAs, to determine if their coverage is creditable, and requiring them to report the creditable status of that coverage, unduly increases administrative burden on these entities by causing them to expend additional resources and expertise that they may not possess. If these entities disclose that they do not offer creditable coverage (because they do not directly offer prescription drug coverage) while the individual's plan that directly offers the prescription drug benefit coverage discloses that it does offer creditable coverage, the recipient of the information could find the dual messaging potentially contradictory and confusing. Ultimately, this confusion disadvantages the Part D Medicare-eligible individual in their ability to make an informed choice about their prescription drug coverage, and ensuring that beneficiaries receive clear information is crucial. As the number of account-based plans has grown in recent years, we have received feedback from organizations who offer these products that they believe the requirement to report creditable coverage does not comport with the account-based model. We proposed to exclude account-based plans from making these disclosures as 
                        <PRTPAGE P="17547"/>
                        these account-based plans do not offer prescription drug coverage and to provide clarity for Medicare-eligible individuals regarding whether their coverage is creditable. The proposal also aligned with the President's January 31, 2025, Executive Order (E.O.), titled 
                        <E T="03">Unleashing Prosperity Through Deregulation,</E>
                         as, if finalized, it would eliminate the need to acquire and maintain resources and expertise to comply with federal regulations to provide creditable coverage disclosures.
                    </P>
                    <P>Therefore, we proposed to modify regulations at § 423.56(b)(3) to codify that account-based plans, such as HRAs and ICHRAs, are excluded from group health plans that are required to make creditable coverage disclosures.</P>
                    <P>We received comments from health plans, professional organizations, benefit specialist advisors, SHIPs, and a State Department of Insurance on our proposal to exclude account-based medical plans from creditable coverage disclosure requirements. The comments we received on this proposal and our responses follow.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Most commenters supported our proposal to exclude account-based medical plans from the creditable coverage disclosure requirements. Commenters cited several reasons for their support of this proposal. Commenters stated that these disclosures are not appropriate for account-based arrangements because such plans do not provide comprehensive prescription drug coverage and therefore do not function as substitutes for Part D coverage. Several commenters indicated that the proposal appropriately aligns disclosure requirements with the nature of the coverage offered.
                    </P>
                    <P>Many commenters further noted that applying creditable coverage disclosure requirements to account-based medical plans creates confusion for beneficiaries and imposes administrative burden without a corresponding consumer benefit. One commenter explained that the purpose of creditable coverage disclosures is to inform beneficiaries about the equivalency of prescription drug coverage, and that extending these requirements to account-based arrangements goes beyond that intent and diminishes the usefulness of the disclosures.</P>
                    <P>A couple of commenters also stated that codifying the exclusion would promote greater consistency and clarity across stakeholders. A commenter representing beneficiary assistance programs reported that SHIP counselors frequently encounter beneficiary confusion resulting from disclosures associated with account-based plans and must spend significant time clarifying that these arrangements do not replace Part D coverage. The commenter stated that exempting account-based medical plans from the disclosure requirement would reduce unnecessary counseling complexity and improve efficiency. Another commenter noted that beneficiaries would remain protected because group health plans that provide prescription drug coverage, including those that also offer account-based arrangements, would continue to be subject to the creditable coverage disclosure requirements.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support of this proposal and agree with the points the commenters raise.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported the proposal but recommended that CMS revise § 423.56(b)(3) to clarify that any group health plan offering prescription drug coverage, including plans that also include account-based medical coverage, must comply with the disclosure and notification requirements in paragraphs (c) through (g) of that section.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's suggestion. We agree that group health plans offering prescription drug coverage, including those that also include account-based medical coverage, remain subject to the creditable coverage disclosure and notification requirements under § 423.56(c) through (g). We believe existing regulations sufficiently reflect this requirement and therefore are not making additional regulatory changes at this time.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A small number of commenters opposed the proposal to exclude account-based medical plans from the creditable coverage disclosure requirements. These commenters stated that disclosures help beneficiaries distinguish between coverage that does and does not satisfy Medicare requirements and expressed concern that exempting account-based plans could reduce beneficiary awareness of whether such coverage meets Medicare creditable coverage standards. One commenter noted that it is not obvious to beneficiaries that account-based arrangements used to pay for prescription drugs do not constitute creditable prescription drug coverage. Another commenter asserted that the administrative burden on account-based plans is minimal, as plan sponsors already know that these arrangements do not meet creditable coverage standards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' concerns. As discussed above, account-based medical plans do not provide comprehensive prescription drug coverage and therefore do not satisfy Medicare creditable coverage standards. We agree that disclosures play an important role in informing beneficiaries; however, we believe that applying creditable coverage disclosure requirements to arrangements that are not, and cannot be, creditable has contributed to beneficiaries receiving potentially contradictory and confusing information. Beneficiaries will continue to receive creditable coverage disclosures from group health plans that provide prescription drug coverage, including plans that also offer account-based arrangements.
                    </P>
                    <P>After consideration of the comments received on this provision by a broad range of stakeholders, we are finalizing this policy as proposed without modification.  </P>
                    <HD SOURCE="HD2">B. Deregulate § 422.102(e) Pathway for Certain D-SNPs To Offer Supplemental Benefits (§ 422.102)</HD>
                    <P>
                        We provide several avenues for MA plans to provide enrollees with supplemental benefits. In the final rule titled “Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Programs for Contract Year 2013 and Other Changes,” which appeared in the 
                        <E T="04">Federal Register</E>
                         on April 12, 2012 (hereafter referred to as the April 2012 final rule), we codified § 422.102(e). As we described in the preamble to the April 2012 final rule (77 FR 22075), § 422.102(e) specifies that, subject to our approval, and as specified annually by us, certain D-SNPs that meet integration and performance standards may offer additional Medicare supplemental benefits beyond those we currently allowed other MA plans to offer at the time of publication, where we find that the offering of such benefits could better integrate care for the dually eligible population. Such benefits may include nonskilled nursing services, personal care services, and other long-term care services and supports designed to keep dually eligible beneficiaries out of institutions.
                    </P>
                    <P>
                        In the Announcement of CY 2019 Medicare Advantage Capitation Rates and Medicare Advantage and Part D Payment Policies and Final Call Letter issued on April 2, 2018, we announced its expanded interpretation of the “primarily health related” standard applied to supplemental benefits in light of section 1852(a)(3) of the Act, which requires supplemental benefits to be “health care benefits.” Under the expanded interpretation, for an item or service to be considered as primarily health related, it must diagnose, 
                        <PRTPAGE P="17548"/>
                        prevent, or treat an illness or injury, compensate for physical impairments, act to ameliorate the functional/psychological impact of injuries or health conditions, or reduce avoidable emergency and healthcare utilization. In the call letter, we expressed the belief that the expanded standard for “primarily health related” provided MA plans with more flexibility in designing and offering supplemental benefits that can enhance beneficiaries' quality of life and improve health outcomes.
                        <SU>118</SU>
                        <FTREF/>
                         CMS codified this standard at § 422.100(c)(2)(ii)(A).
                    </P>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             CMS, Announcement of Calendar Year 2019 Medicare Advantage Capitation Rates and Medicare Advantage and Part D Payment Policies and Final Call Letter, page 208. Retrieved from: 
                            <E T="03">https://www.cms.gov/Medicare/Health-Plans/MedicareAdvtgSpecRateStats/Downloads/Announcement2019.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Additionally, the Bipartisan Budget Act of 2018 (Pub. L. 115-123) amended section 1852(a) of the Act to expand the types of supplemental benefits that may be offered by MA plans to chronically ill enrollees, called special supplemental benefits for the chronically ill (SSBCI). We codified the parameters for SSBCI at § 422.102(f) in the June 2020 final rule. (85 FR 33800) SSBCI includes supplemental benefits that are not primarily health related and may be offered non-uniformly to eligible chronically ill enrollees. MA plans can offer a “non-primarily health related” item or service to chronically ill enrollees if the SSBCI has a reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollee.</P>
                    <P>
                        We noted in the Contract Year 2027 proposed rule that, in recent years, few MA plans have used § 422.102(e) to provide supplemental benefits. A table showing supplemental benefits offered through § 422.102(e) for contract years 2013-2026 can be found at 90 FR 54986. Our analysis of the bid data from 2013 to 2026 shows that the supplemental benefits D-SNPs have offered through § 422.102(e) are meals benefits and assistive devices for home safety. We note that these benefits can currently be covered under the expanded definition of primarily health related supplemental benefits and SSBCI. Specifically, the April 2019 HPMS memo titled “Implementing Supplemental Benefits for Chronically Ill Enrollees” refers to Chapter 4 of the Medicare Managed Care Manual that indicates that meals are a primarily health related supplemental benefit (PBP category B13c) in limited situations: when provided to enrollees for a limited period immediately following surgery, or an inpatient hospitalization, or for a limited period due to a chronic illness. In those situations, a meals supplemental benefit is permissible if the meals are: (1) needed due to an illness; (2) consistent with established medical treatment of the illness; and (3) offered for a short duration. Meals may be offered beyond a limited basis as a non-primarily health related supplemental benefit (PBP category B19b/13i) to chronically ill enrollees. Meals may be home-delivered and/or offered in a congregate setting.
                        <SU>119</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             CMS, HPMS Memorandum, “Implementing Supplemental Benefits for Chronically Ill Enrollees”. Retrieved from: 
                            <E T="03">https://www.cms.gov/research-statistics-data-and-systems/computer-data-and-systems/hpms/hpms-memos-archive-weekly-items/syshpms-memo-2019-week4-apr-22-26.</E>
                        </P>
                    </FTNT>
                    <P>We believe the small number of D-SNPs offering supplemental benefits through § 422.102(e) is due to the availability of other pathways to provide the same supplemental benefits that can be covered under § 422.102(e). Based on this experience, we believed that § 422.102(e) was no longer needed and proposed to remove and reserve § 422.102(e) for future rulemaking. The two D-SNPs offering supplemental benefits through § 422.102(e) in CY 2025 have 27,888 enrollees as of June 2025. For CY 2026, no plan requested to offer supplemental benefits through § 422.102(e).</P>
                    <P>We explained in the Contract Year 2027 proposed rule that we did not anticipate any adverse consequences to removing § 422.102(e) since D-SNPs could offer the same benefits in their annual bid through primarily health related supplemental benefits or SSBCI. We anticipated that deregulating § 422.102(e) could streamline the bid submission process for D-SNPs and us by simplifying the avenues for offering supplemental benefits.</P>
                    <P>We solicited comments on our proposal. We requested that commenters consider whether there is any value to us retaining § 422.102(e), such as whether there are any Medicare supplemental benefits that could only be offered under § 422.102(e) and not through primarily health related supplemental benefits or SSBCI. We also recognize that participating D-SNPs will no longer be able to offer benefits through the MA Value-Based Insurance Design (VBID) model beginning in CY 2026 and solicited comments on whether § 422.102(e) provides any advantages in D-SNPs offering supplemental benefits previously offered under VBID.</P>
                    <P>We received the following comments on this proposal and respond to them below:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters outlined support to remove § 422.102(e), referencing low utilization of the § 422.102(e) pathway and the availability of other pathways for D-SNPs to provide supplemental benefits, such as primarily health related supplemental benefits and SSBCI. A few of these commenters stated that removing the § 422.102(e) pathway would reduce regulatory complexity without constraining benefit design. While supporting the proposal, a commenter emphasized that when States do not provide Medicaid benefits for dually eligible individuals, D-SNPs need flexibility to provide additional benefits to enrollees with complex needs and such benefits cannot always be provided through primarily health related supplemental benefits or SSBCI. A commenter suggested that CMS develop a publicly shared document that displays benefits historically offered under § 422.102(e) with other supplemental benefits pathways and provide guidance for D-SNPs to operationalize any transition away from the § 422.102(e) pathway.
                    </P>
                    <P>Other commenters opposed removing § 422.102(e), noting lack of D-SNP awareness of the § 422.102(e) supplemental benefits pathway and that removing the § 422.102(e) pathway could constrain innovation in State and D-SNP supplemental benefits design to advance more integrated D-SNPs. A commenter stated that the § 422.102(e) pathway may not have been used previously due to the VBID model and could be useful to D-SNPs now that the VBID model is no longer available. Another commenter recommended that CMS issue guidance to plans that reinterprets § 422.102(e) to allow additional supplemental benefits, such as food and grocery allowances, that are responsive to the needs of dually eligible individuals. The commenter also suggested that CMS consider ways to expand § 422.102(e) beyond its applicability to HIDE SNPs and FIDE SNPs. In addition, a commenter raised concerns that removing the § 422.102(e) pathway could negatively impact D-SNP enrollees.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters perspectives on our proposal to remove § 422.102(e) as an additional pathway for D-SNPs to offer supplemental benefits. Although a small number of D-SNPs have offered supplemental benefits through § 422.102(e), we are persuaded by comments regarding the lack of awareness of § 422.102(e), the potential for § 422.102(e) to be an alternative to the recently ended VBID program, and the potential for § 422.102(e) to provide 
                        <PRTPAGE P="17549"/>
                        a pathway to develop innovative supplemental benefits for dually eligible individuals. We will retain the § 422.102(e) supplemental benefits pathway and monitor utilization of this pathway in future bids to inform future rulemaking.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined previously and our responses to comments, we are not finalizing the proposal to remove § 422.102(e) and instead retaining § 422.102(e) as a pathway for D-SNPs to offer supplemental benefits.  </P>
                    <HD SOURCE="HD2">C. Rescind Mid-Year Supplemental Benefits Notice (§§ 422.111(l) and 422.2267(e)(42))</HD>
                    <P>
                        The “Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024—Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE)” final rule appeared in the April 23, 2024 
                        <E T="04">Federal Register</E>
                         (89 FR 30448), hereinafter referred to as the April 2024 final rule, which included a new requirement, beginning January 1, 2026, that MA organizations must notify enrollees mid-year of any unused supplemental benefits available to them (89 FR 30561). The notice, referred to as the Mid-Year Notice, was to list any supplemental benefits not utilized by the enrollee during the first six months of the plan year.
                    </P>
                    <P>The Mid-Year Notice was intended to address what appeared to be a gap in enrollee awareness and utilization of supplemental benefits for which MA organizations designate rebate dollars. After further review of interested parties' feedback and more current data on supplemental benefit utilization, CMS later determined that the frequency of utilization was higher than previously believed. CMS also developed concerns about the administrative and financial burden, especially on smaller MA organizations, and determined the new requirement was duplicative of already existing requirements. As a result, via the Agency's authority to establish standards consistent with, and to carry out, Part C under section 1856(b)(1) of the Act, CMS proposed in the Contract Year 2027 proposed rule to rescind the Mid-Year Notice of Supplemental Benefits requirement established in §§ 422.111(l) and 422.2267(e)(42) (90 FR 54987).</P>
                    <P>Rescission of this requirement is consistent with E.O. 14192, “Unleashing Prosperity through Deregulation.” E.O. 14192 instructed federal agencies to review all regulations to alleviate unnecessary regulatory burdens placed on the American people. CMS reviewed this regulation in accordance with E.O. 14192 and determined that it was unnecessary and would impose a significant burden on MA organizations that outweighs the intended benefit. As documented in the April 2024 final rule responses to public comments, MA organizations expressed numerous concerns about the burden and complexity of compliance. The requirement necessitated the development, implementation, and maintenance of tracking systems to monitor individual enrollee utilization of each supplemental benefit from January 1st to June 30th of the plan year. It then required MA organizations to compile and send the individualized information to each corresponding enrollee in paper format between June 30th and July 31st of the plan year, providing about a 1-month window to mail information to potentially millions of enrollees. Additionally, MA organizations predicted the substantial task of printing and mailing several pages of individualized documents within a compressed time frame would exceed CMS's original estimate for administrative costs. The impact would be substantially higher for smaller MA organizations and could contribute to competitive disadvantages that result in reduced plan choice for MA enrollees.</P>
                    <P>Further, with respect to MA organizations of all sizes, the administrative complexity and operational costs associated with meeting the Mid-Year Notice requirement would consume resources that could be better utilized for activities with more direct impact on enrollee health outcomes and satisfaction. Instead, the Mid-Year Notice risked diversion of organizational capacity away from more beneficial work such as patient care coordination or quality improvement activities—both of which are required under statute.</P>
                    <P>Another factor considered in the proposal was the unnecessary duplication of information already provided to enrollees through existing statutory disclosure requirements. Section 1852(c)(1) of the Act requires MA organizations to provide detailed descriptions of all plan provisions, including supplemental benefits, in a clear, accurate, and standardized form through the Evidence of Coverage (EOC) document. MA organizations must already furnish this information to enrollees at the time of enrollment and annually thereafter. As specified in regulation at § 422.2267(e)(42), the Mid-Year Notice was to include, for each unused mandatory and optional supplemental benefit, the information that appears for those benefits in the EOC. The Mid-Year Notice would therefore be redundant of information that enrollees already received about their benefits no more than six months earlier.</P>
                    <P>
                        Finally, the original justification for implementing the Mid-Year Notice requirement is not supported by the most current evidence available. In a recent survey 
                        <SU>120</SU>
                        <FTREF/>
                         of 1,846 MA enrollees, 70 percent of respondents reported they had used at least one supplemental benefit in the past year; 19 percent reported they did not use their supplemental benefits because they did not need them. These findings suggest enrollees are generally aware of their supplemental benefits and are using them, although CMS acknowledges that at this time, information on MA enrollee use of supplemental benefits is limited. It should be noted, however, that CMS is working to address this data gap; the Agency introduced the Supplemental Benefit Utilization and Costs section in the Part C Reporting Requirements for contract year (CY) 2024 and made additional changes effective for CY 2025 and subsequent years. This will allow CMS to review and compare a chronological sequence of CY data sets to help the Agency better understand supplemental benefit utilization trends in the Part C program.
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             
                            <E T="03">https://www.commonwealthfund.org/publications/surveys/2024/feb/what-do-medicare-beneficiaries-value-about-their-coverage.</E>
                        </P>
                    </FTNT>
                    <P>
                        Market competition naturally incentivizes MA organizations to ensure enrollees are aware of and use the supplemental benefits that differentiate their plans. MA organizations have demonstrated that they can effectively promote awareness and utilization of supplemental benefits through existing channels. Moreover, a requirement to send additional information to enrollees, promoting benefits they will not necessarily be eligible for, could lead to enrollee confusion. Current care coordination activities, existing communication requirements, and proactive, voluntary outreach programs have proven successful in promoting supplemental benefit utilization. The particular regulatory requirement for a Mid-Year Notice would likely not result in improved communication of 
                        <PRTPAGE P="17550"/>
                        supplemental benefits information and would create undue burden for MA organizations. Further, recent evidence suggests that enrollees are utilizing supplemental benefits when they need them. For the aforementioned reasons, CMS proposed to rescind the Mid-Year Notice requirement at §§ 422.111(l) and 422.2267(e)(42).
                    </P>
                    <P>CMS invited public comment on the proposed removal of this regulatory requirement and received mixed comments. A discussion of the comments received, along with CMS's responses, follows.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern that MA enrollees could be unaware of the full slate of supplemental benefits available to them, and that enrollees would not be informed of their supplemental benefits as a result of the removal of the Mid-Year Notice requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed in the preamble, the Mid-Year Notice duplicates existing communication requirements such as the EOC. MA organizations are required to send an EOC annually to each individual enrolled in their MA plans. The EOC includes detailed information about the supplemental benefits covered by the plan such as benefit descriptions, copays, coinsurance, and eligibility criteria when applicable. Further, many MA organizations already communicate availability of supplemental benefits through their care coordination services, newsletters, and other enrollee education efforts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters stated that enrollees do not always understand that they must meet particular eligibility requirements to receive certain supplemental benefits, and that a failure to rescind the Mid-Year Notice requirement would result in confusion when enrollees receive information about benefits for which they are not eligible.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS agrees that a new, targeted communication method that presents an individualized menu of supplemental benefits options (
                        <E T="03">i.e.</E>
                         the enrollee's unused supplemental benefits) but may not exclude benefits the enrollee is ineligible or not necessarily eligible for, could be confusing and would likely result in frustration for enrollees and increased costs for MA organizations. CMS believes that the EOC already makes clear distinctions between types of supplemental benefits and their corresponding eligibility criteria in a way that is easy to understand.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters stated that enrollees choose plans based on supplemental benefits, and MA plans receive rebates to fund those supplemental benefits. Thus, CMS should promote enrollee utilization of supplemental benefits to ensure government funds are responsibly spent.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS is committed to ensuring that taxpayer money is spent responsibly, transparently, and appropriately across all CMS programs. Continuous oversight and thoughtful consideration for the use of government funds, including in MA, are an ongoing Agency priority. While, as these commenters stated, enrollees should be encouraged to use their supplemental benefits, CMS does not believe that the duplicative effort of sending a bulk of information to enrollees that they have already received six months earlier will achieve this result.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters gave their support for removal of the Mid-Year Notice requirement due to the logistical challenges and administrative and operational costs associated with its implementation and noted that the information sent would be largely duplicative of information sent six months earlier in the EOC. A subset of those commenters further noted that the complexity of these challenges would put smaller MA organizations at a disadvantage.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the feedback and acknowledges the challenges MA organizations, including small MA organizations, face when new regulatory requirements emerge. CMS also acknowledges the importance of maintaining an environment that gives smaller MA organizations a fair chance to compete, with the ultimate goal being a wide variety of plan choices for enrollees each year. As such, it is important to ensure that every new requirement can offer enough benefit to offset the burden it imposes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that in some cases, the Mid-Year Notice would require great effort but produce little value. As an example, the commenter pointed out that some provider-led Institutional Special Needs Plans (I-SNPs) already ensure enrollees maximize their available supplemental benefits, and as a result, the enrollees of those SNPs are unlikely to have improved access to care and health outcomes because they received a Mid-Year Notice.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the thoughtful response by this commenter and acknowledges the commenter's assessment that if a MA plan such as an I-SNP is already designed to help enrollees maximize their use of supplemental benefits, it is unlikely that any improvement in health outcomes would result from the distribution of a Mid-Year Notice. This example demonstrates that aside from being duplicative of existing communication requirements, the requirement may also be overly broad because of its application to all MA plan-types.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted the dearth of available data on supplemental benefit usage and stated that CMS should obtain such data and use it for future policy refinements with respect to supplemental benefit communications. For example, a commenter pointed out the hypothetical potential for a discharge team to use electronic tools, suggestive of the interoperability infrastructure of which implementation began during the first Trump administration, to connect a patient with post-discharge support that could help reduce the likelihood of rehospitalization.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Use of interoperability tools by providers for the purpose of connecting patients to supplemental benefits is intriguing, but beyond the scope of this rule. CMS appreciates the thoughtful nature of these comments and will take this input into consideration for future rulemaking.
                    </P>
                    <P>After careful consideration of the comments received, CMS will move forward with the proposal, without modification, and rescind the Mid-Year Notice of Supplemental Benefits.</P>
                    <HD SOURCE="HD2">D. Revisions to Ensuring Equitable Access to Medicare Advantage (MA) Services (§ 422.112(a)(8))</HD>
                    <P>
                        Under § 422.112(a)(8), MA organizations are required to ensure that services are provided in a culturally competent manner to all enrollees. In the final rule titled “Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly” (88 FR 22120) (hereinafter referred to as the April 2023 final rule), CMS retitled the paragraph heading from “Cultural considerations” to “Ensuring Equitable Access to Medicare Advantage (MA) Services” and added more populations to the existing list of groups in the regulation. These changes were implemented in accordance with the previous administration's E.O. 13985: “Advancing Racial Equity and Support for Underserved Communities Through the Federal Government,” (E.O. 13985) issued on January 20, 2021. CMS explained in the preamble that the list of populations was clarifying in nature, non-exhaustive, and was intended to provide additional examples of populations MA organizations should be mindful of in 
                        <PRTPAGE P="17551"/>
                        their plan designs. CMS emphasized that the protections of the provision were already in effect prior to the proposed change and that MA organizations must provide all enrollees, without exception, accommodations to access services (88 FR 22152 and 22153). CMS determined there was no additional regulatory impact to MA organizations in terms of burden, resources for implementation, or collection information as MA organizations were already held to and in compliance with these requirements.
                    </P>
                    <P>
                        On January 20, 2025, E.O. 14148: “Initial Rescissions of Harmful Executive Orders and Actions” was issued and revoked E.O. 13985. Additionally, on January 31, 2025, E.O. 14192, “Unleashing Prosperity through Deregulation” was issued, which instructed Federal agencies to review regulations in their jurisdiction to alleviate unnecessary regulatory burdens placed on the American people. CMS has reviewed § 422.112(a)(8) in accordance with E.O.s 14148 and 14192 and determined that the revisions made in the April 2023 final rule were unnecessary as they did not change the underlying requirements for MA organizations and the modification of the regulatory text created additional and unnecessary complexity in interpreting the provision. In the Contract Year 2027 proposed rule (90 FR 54988), CMS proposed to amend the regulation at § 422.112(a)(8) to revert to the prior paragraph heading and text which reads, “
                        <E T="03">Cultural considerations.</E>
                         Ensure that services are provided in a culturally competent manner to all enrollees, including those with limited English proficiency or reading skills, and diverse cultural and ethnic backgrounds.” This change will streamline the regulatory text and avoid confusion about the list of different sub-populations in implementation, while maintaining the protections for access to services for all enrollees.
                    </P>
                    <P>CMS received the following comments on this proposal, and our responses follow:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter agreed with the proposal, as they were supportive of the aims of E.O. 14148 and the removal of sex-based terminology.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenter for their support for our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters were opposed to the proposal and shared concerns about the proposed change to § 422.112(a)(8). Concerns included that the change would impede plans' ability to address social risk factors and other barriers that impact care delivery and management, as well as that the generality of the language would lead to inconsistent implementation which would potentially worsen health disparities. Several commenters noted support for enumerating groups that have experienced poor health care experiences and that it was a specific, inclusive, and helpful guide for plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters sharing their concerns. However, CMS disagrees with this position, as plans will still be required to ensure all enrollees, without exception, are provided with accommodations to access services, as they were required to do even before the April 2023 updates to § 422.112(a)(8). Further, this action does not prohibit plans (including special needs plans) from identifying health disparities, addressing barriers that impact care delivery, and developing strategies for different sub-populations to ensure high-quality care if they choose to do so. Plans can continue to develop their own lists of sub-populations of focus, continue quality improvement programs that work to improve health outcomes, and address disparities observed among their enrollees.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter urged that CMS ensure that the language requiring culturally competent services for those with limited English proficiency or reading skills is implemented robustly, with this including requirements for qualified interpreter services, translated written materials, and other accommodations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenter sharing this suggestion. CMS believes that plans can determine what strategies, such as translation or interpreter services, work best to ensure culturally competent care for their enrollees. Of note, plans are also held to the Health and Human Services Office for Civil Rights (OCR) notice of availability of language assistance services and auxiliary aids and services requirements (currently at 45 CFR 92.11).
                    </P>
                    <P>After consideration of the public comments CMS received, and for the reasons outlined here and in the Contract Year 2027 proposed rule, CMS is finalizing as proposed revisions to § 422.112(a)(8).</P>
                    <HD SOURCE="HD2">E. Rescinding the Annual Health Equity Analysis of Utilization Management Policies and Procedures (§ 422.137(c)(5), (d)(6) and (d)(7))</HD>
                    <P>
                        The final rule titled “The Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly” appeared in the April 12, 2023 
                        <E T="04">Federal Register</E>
                         (88 FR 22120) (hereinafter referred to as the April 2023 final rule). The April 2023 final rule required that Medicare Advantage (MA) plans establish a Utilization Management (UM) Committee to annually review all UM policies and procedures, including for the use of prior authorization, and ensure that these policies are consistent with the coverage requirements, including Original Medicare's current national and local coverage decisions and guidelines.
                    </P>
                    <P>Subsequently, CMS made and proposed additional changes to the UM Committee requirements, which are detailed in the Contract Year 2027 proposed rule. This includes changes made in April 2024, when CMS issued the Medicare Program; Changes to the Medicare Advantage and the Medicare Prescription Drug Benefit Program for Contract Year 2024-Remaining Provisions and Contract Year 2025 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly (PACE) final rule (89 FR 30448) (hereinafter referred to as the April 2024 final rule).</P>
                    <P>Specifically, at § 422.137(c)(5) CMS finalized a requirement that beginning in 2025, the UM Committee must include at least one member with “expertise in health equity.” In addition, at § 422.137(d)(6), CMS finalized a requirement that the UM Committee must conduct an annual health equity analysis on the use of prior authorization by examining the impact of prior authorization, at the plan level, on enrollees with one or more specified Social Risk Factors (SRFs). In response to comments, CMS took the position that while changes to the health equity analysis requirement would be helpful to provide a more in-depth analysis, the health equity analysis requirement, as proposed and finalized, would provide a useful baseline of data. CMS also signaled the intent to consider further changes to these requirements in subsequent rulemaking based on comments received.</P>
                    <P>
                        CMS implemented the additional UM Committee requirements in the April 2024 final rule based on the previous administration's health equity-related initiatives, which have since been revoked by E.O. 14148: “Initial 
                        <PRTPAGE P="17552"/>
                        Rescissions of Harmful Executive Orders and Actions.” 
                        <SU>121</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/01/28/2025-01901/initial-rescissions-of-harmful-executive-orders-and-actions.</E>
                        </P>
                    </FTNT>
                    <P>
                        Moreover, as discussed in the Contract Year 2027 proposed rule, the health equity requirements implemented in the April 2024 final rule increased regulatory burden for MA organizations by requiring the addition of a member of the UM Committee with expertise in health equity, additional data collection, and the public posting of an annual health equity analysis. The increased regulatory burden is inconsistent with E.O. 14192, “Unleashing Prosperity Through Deregulation,” issued on January 31, 2025.
                        <SU>122</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             
                            <E T="03">https://www.federalregister.gov/documents/2025/02/06/2025-02345/unleashing-prosperity-through-deregulation.</E>
                        </P>
                    </FTNT>
                    <P>Since the issuance of the April 2024 final rule, the CMS position on the health equity analysis requirement has changed. CMS now believes that this analysis is not the best vehicle to obtain baseline data on the use of prior authorization and that there are more effective ways to gain this information, including through robust interoperability efforts. CMS will continue to explore ways to collect data regarding the use of prior authorization in a manner that best represents all MA enrollees. CMS is taking steps to reduce the regulatory burdens imposed by the UM Committee requirements implemented in the April 2024 final rule consistent with the focus on streamlining regulations and reducing administrative burdens for those participating in the Medicare program. In response to interested parties concerns about the limited impact on health equity, the questionable utility of the required data analysis, and the additional administrative burden, deregulating the requirements at § 422.137(c)(5), (d)(6), and (d)(7) aligns with CMS policy goals and E.O.s 14148 and 14192.</P>
                    <P>Additionally, on June 16, 2025, CMS released a Health Plan Management System (HPMS) memorandum exercising enforcement discretion regarding the requirements under § 422.137(c)(5), (d)(6), and (d)(7) until further notice. As explained in the HPMS memorandum, CMS received numerous questions and requests for guidance regarding the implementation of the requirements and determined that a temporary pause in enforcement was necessary to reevaluate the requirements and consider potential changes.</P>
                    <P>In the Contract Year 2027 proposed rule, CMS proposed to remove the requirement at § 422.137(c)(5) that the UM Committee include at least one member with expertise in health equity. In addition, CMS proposed to remove § 422.137(d)(6), which requires that the UM Committee conduct an annual health equity analysis of the use of prior authorization. Finally, CMS proposed to remove § 422.137(d)(7), which requires the health equity analysis to be posted on the plan's website in a prominent manner that is publicly accessible.</P>
                    <P>CMS received the following comments on this section of the Contract Year 2027 proposed rule, and provided responses as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed support for CMS' proposal to rescind the requirements for MA organizations' UM Committees at § 422.137(c)(5), (d)(6), and (d)(7). The commenters stated that the analysis was duplicative, offered limited value, and could present a misleading picture of health equity due to inconsistences in data reporting. Commenters also indicated that simplifying and streamlining the requirements would reduce administrative costs and burden on MA organizations. A commenter stated prior authorization denial rates are not necessarily attributable to an enrollee's SRF status. Another commenter expressed concerns that statistics alone would not describe the entirety of MA plans approach to supporting beneficiaries access to care. Finally, a commenter expressed concerns that there would be data inconsistencies in the absence of reporting guidance defining data elements or a standard template.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenters' support and thanks them for their comments.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported the requirement that MA organizations release an annual health equity analysis of utilization management policies. These commenters stated that the burden associated with producing the analysis would be minimal and that the resulting data would provide important transparency, information, and accountability around the use of UM on different populations.
                    </P>
                    <P>Numerous commenters further asserted that the analysis would strengthen CMS oversight of the MA program by helping to prevent inappropriate denials, barriers to care, harmful clinical delays, and clinician burnout. They emphasized that the reporting would support efforts to identify and address health disparities and improve access to care for underserved populations.</P>
                    <P>Several commenters expressed concerns about removing health equity reporting requirements when Medicare's population is increasingly diverse and disparities in access to care are well documented. Commenters also stated that MA organizations' prior authorization practices lead to inappropriate denials, care delays, and administrative burden. These commenters stated that the analysis would provide a deeper understanding of the real-world impacts of prior authorization and help ensure that MA organizations are meeting coverage requirements. A commenter stated that removing the requirement would allow a critical information gap to persist, while another commenter expressed concerns that eliminating the requirement would undermine prior authorization reform efforts.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS considered commenters' views regarding transparency, oversight, and the importance of analyzing UM policies in an increasingly diverse Medicare population. As outlined in the Contract Year 2027 proposed rule and this final rule, CMS continues to believe that the burden associated with producing the annual health equity analysis is not minimal and that the analysis would not meaningfully strengthen oversight of UM practices in the MA program.
                    </P>
                    <P>CMS' decision to rescind the requirements for MA organizations' UM Committees at § 422.137(c)(5), (d)(6), and (d)(7) reflects CMS' assessment that the requirements would have limited effectiveness in advancing health equity, while imposing additional administrative burden associated with collecting and publishing the data. This decision is also consistent with CMS' broader regulatory approach, including the decision not to finalize proposed expansions to the health equity analysis requirements in the April 2025 final rule.</P>
                    <P>CMS believes there are more efficient and effective ways to obtain information on the impact of UM requirements on MA enrollees, including through ongoing interoperability initiatives and other data collection mechanisms. CMS remains committed to ensuring that MA organizations comply with coverage and UM requirements and will continue to evaluate options for collecting data that more accurately reflect the experiences of all MA enrollees.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged CMS not to rescind the annual requirement for MA organizations to release an annual health equity analysis without first establishing an alternative data collection mechanism. These commenters recommended that CMS 
                        <PRTPAGE P="17553"/>
                        retain the health equity analysis requirement until service level determination and appeal data are fully operational.
                        <SU>123</SU>
                        <FTREF/>
                         Commenters also recommended that CMS adopt a less burdensome alternative methodology, collect baseline data through interoperability, or expand data reporting to better understand how prior authorization policies affect access to care across beneficiary populations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             In a December 16, 2025, HPMS memorandum, CMS announced its plans to conduct a voluntary pilot to collect service level data on MA plan initial determinations and appeals in 2026, with the intent to expand the data collection to all MA plans beginning in 2027.
                        </P>
                    </FTNT>
                    <P>Multiple commenters proposed specific alternative methodologies for monitoring MA organizations' UM policies and practices. Some commenters encouraged CMS to extend reporting requirements to Part D plans to improve understanding of how UM policies affect access to care and help inform beneficiaries' and caregivers' coverage decisions. A commenter further urged CMS to conduct a study examining whether utilization management policies contribute to poorer health outcomes. Another commenter encouraged CMS to require states to develop standardized tools to measure the impact of UM policies on access to Medicaid services for dually eligible individuals.</P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates commenters' recommendations regarding ways to retain and strengthen the annual health equity analysis. While CMS acknowledges commenters' concerns about eliminating the reporting requirements without an alternative approach, the Agency does not believe that the annual health equity analysis, as finalized in prior rulemaking, is the most effective or efficient mechanism for establishing baseline data on the impacts of UM practices across MA enrollee populations. CMS is therefore rescinding the requirements while continuing to consider other approaches to obtaining more timely, standardized, and actionable data.
                    </P>
                    <P>CMS also considered commenters' suggested alternative methodologies for monitoring MA organizations' UM policies and practices. CMS believes the proposed alternative analysis methodologies would offer limited practical utility and impose additional administrative burden on MA organizations. CMS is committed to taking steps to reduce the regulatory burdens imposed by the UM Committee requirements, consistent with the focus on streamlining regulations and reducing administrative burden. However, CMS may consider other approaches to monitoring UM policies and practices in future rulemaking.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged CMS not to remove the requirement that the UM Committee include at least one member with health equity expertise. The commenters stated that the requirement supports MA organizations' ability to monitor the impact of prior authorization on specific patient groups, identify disparities, and address any inequities in access to care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS carefully considered commenters' views regarding the inclusion of a UM Committee member with health equity expertise and the role such expertise may play in monitoring the effects of UM on specific patient populations. In the MA program, access to care is monitored through multiple oversight mechanisms, and MA organizations are already required to maintain policies, procedures, and safeguards to ensure timely access to covered items and services. Therefore, CMS does not believe that a prescriptive UM Committee composition requirement is necessary to monitor the impact of prior authorization on specific patient groups, address inequities in access to care, or ensure access to services for all MA enrollees.
                    </P>
                    <P>After considering the public comments received, and for the reasons discussed in the Contract Year 2027 proposed rule and in this response to comments, the proposals to rescind the requirements for MA organizations' UM Committees at § 422.137(c)(5), (d)(6), and (d)(7), are being finalized as proposed, consistent with the cited E.O.s., and in response to interested parties' concerns about the requirements' rationale, feasibility, and administrative burden. This aligns with CMS' broader regulatory approach, including the decision not to finalize proposed expansions to the health equity analysis requirements in the April 2025 final rule.</P>
                    <P>CMS also requested comments on ways to reduce administrative burdens associated with other UM Committee requirements for consideration in future rulemaking. CMS appreciates the comments and suggestions received and will take the feedback into consideration for future policy development.  </P>
                    <HD SOURCE="HD2">F. Rescinding the Quality Improvement Program Health Disparities Requirement (§ 422.152(a)(5))</HD>
                    <P>
                        In accordance with section 1852(e) of the Act, all MA organizations must have an ongoing Quality Improvement (QI) Program for the purpose of improving the quality of care provided to enrollees. QI program requirements appear at 42 CFR 422.152. In April 2023, the “Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly final rule” appeared in the 
                        <E T="04">Federal Register</E>
                         (88 FR 22120), hereinafter referred to as the April 2023 final rule. In the April 2023 final rule, CMS added a requirement at § 422.152(a)(5) that directs MA organizations to incorporate one or more activities that reduce disparities in health and health care as part of their QI program to comply with health equity mandates stemming from E.O. 13985, “Advancing Racial Equity and Support for Underserved Communities Through the Federal Government.”
                    </P>
                    <P>On January 20, 2025, E.O. 14148, “Initial Recission of Harmful Executive Orders and Actions,” revoked several executive orders, including E.O. 13985. Additionally, on January 31, 2025, E.O. 14192, “Unleashing Prosperity Through Deregulation,” was issued to address the significant burden that complex Federal regulations impose on Americans, and hinder economic growth, innovation, and global competitiveness.</P>
                    <P>Consistent with E.O.s 14148 and 14192, CMS proposed to eliminate the regulatory requirement for QI programs under § 422.152(a)(5) for the reasons outlined in detail in the Contract Year 2027 proposed rule issued in November 2025 (90 FR 54990).</P>
                    <P>CMS did not propose to modify the QI Program requirements under § 422.152(a)(1) through (4), which are required to meet the requirements of section 1852(e) of the Act. The statute is clear and no further regulatory language to specify reducing health disparities is necessary to carry out the QI program. Additionally, this final rule aligns with the directives of E.O. 14192, to deregulate and reduce the administrative burden on MA organizations while preserving quality.</P>
                    <P>
                        MA organizations retain the flexibility to implement quality initiatives that address the needs of all enrollees, including the option to continue their current QI program or otherwise make their own determinations regarding whether and how to target health disparities. This ensures services are delivered with equal dignity and respect to each individual and that MA organizations are not required to direct federal resources towards services limited to specific mandated subsets of enrollees. This finalized deregulation reflects CMS' continued commitment to high-quality health care, while reducing 
                        <PRTPAGE P="17554"/>
                        unnecessary administrative burden associated with the prior regulatory requirements, including those established under earlier directives that prioritized narrow equity-focused initiatives driven by exclusively equity-focused executive orders.
                    </P>
                    <P>CMS received the following comments on this section of the Contract Year 2027 proposed rule, and responses follow:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed concerns that removing requirements in MA quality improvement programs for the inclusion of activities to reduce disparities may exacerbate the prevalence of chronic illness and noted the well-documented correlation between health disparities and chronic illness. Commenters expressed concerns that removing this requirement would widen the health care gaps affecting marginalized and underrepresented populations. Some voiced concerns that if this requirement is revoked, insurers would use discriminatory practices to improve overall quality scores. They also urged CMS to continue naming specific groups that have historically experienced discrimination (such as people with disabilities, LGBTQI individuals, racial and ethnic minorities, rural residents, and those affected by persistent poverty) to provide necessary clarity, accountability, and direction to MA plans to ensure equitable access to care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the commenters sharing their concerns. The QI Program requirements under § 422.152(a)(1) through (4) will remain in effect, including the requirement to have a chronic care improvement program (CCIP). Additionally, as discussed in the proposal, MA plans may continue with their current quality improvement initiatives and retain the ability to incorporate activities that address health disparities within their QI programs. CMS remains committed to sustained improvement in patient health outcomes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged CMS to either keep the provision at § 422.152(a)(5) or come up with an alternative policy that would ensure quality care and health equity for MA enrollees from underserved communities.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While CMS acknowledges the commenters' suggestion, the remaining QI Program requirements are sufficient to address the concerns regarding enrollee access to quality health care while reducing burden for MA organizations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter indicated that in Massachusetts, the requirement at § 422.152(a)(5) has functioned as a backstop against unfair or discriminatory prior authorization practices. They went on to urge CMS to strengthen the link between civil rights compliance and Star Ratings, using the ratings to reform utilization management to support timely, fair access to care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS appreciates the suggestion for reforming utilization management practices through the Star Ratings. However, this comment is outside the scope of this regulation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters wrote in support of rescinding the provision at § 422.152(a)(5), noting that it would reduce administrative burden.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS thanks the commenters for their support.
                    </P>
                    <P>After consideration of the public comments received, and for the reasons set forth in the Contract Year 2027 proposed rule and in the above responses to comments, CMS is finalizing the removal of § 422.152(a)(5) as proposed.</P>
                    <HD SOURCE="HD2">G. Deregulate Special Rule for Non-Compliant D-SNPs (§ 422.752)</HD>
                    <P>The Bipartisan Budget Act of 2018 (BBA of 2018; Pub. L. 115-123) amended section 1859 of the Act to establish new minimum standards for all D-SNPs related to integration with Medicaid services (section 1859(f)(8)(D)(i) of the Act). The BBA of 2018 also amended section 1859 of the Act to authorize the Secretary to impose an enrollment sanction on an MA organization offering a D-SNP that has failed to meet at least one of the new integration standards in plan years 2021 through 2025 (section 1859(f)(8)(D)(ii) of the Act). In the April 2019 final rule (84 FR 15719 through 15720), we codified this enrollment sanction at § 422.752(d). From plan years 2021 through 2025, we used this sanction authority in numerous instances and found it helpful for States and new D-SNPs since it created a mechanism to suspend enrollment for D-SNPs when contracting with the State Medicaid agency is unexpectedly delayed. However, since the statutory authority for the enrollment sanction expired at the end of plan year 2025, we proposed to remove § 422.752(d) as articulated in the Contract Year 2027 proposed rule (90 FR 54990).</P>
                    <P>We received the following comments on this proposal and respond to them below:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few stakeholders commented on our proposal. A commenter noted that retaining an expired enforcement authority in regulation is unnecessary and potentially confusing and that removing this language would improve regulatory clarity while preserving CMS oversight tools. While not opposed to removing the expired enforcement authority, another commenter recommended that CMS work with Congress to extend the expiring statutory authority. This commenter explained that an intermediate sanction can be less disruptive for enrollees than an intermediate termination and reinstating the statutory authority would allow CMS to engage in enrollment sanctions for non-compliant D-SNPs in the future.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments in support of our proposal to remove § 422.752(d). We agree that the sanction authority was useful for States and new D-SNPs since it created a mechanism to suspend enrollment for D-SNPs when SMACs were delayed. While we appreciate the interest in extending the enforcement authority in statute, we have been able to work with all applicable States to include, where appropriate, language in the SMACs that provides the same result as the limited enrollment enforcement authority from CMS.
                    </P>
                    <P>After considering the comments we received and for the reasons outlined in the proposed rule and our responses to comments, we are finalizing the proposed removal of § 422.752(d) without modification.  </P>
                    <HD SOURCE="HD2">H. Waiver of Part D Customer Call Center Hours for All Regions Served by LI NET (§ 423.2536)</HD>
                    <P>Division CC, title I, subtitle B, section 118 of the Consolidated Appropriations Act, 2021 (CAA) (Pub. L. 116-260) amended section 1860D-14 of the Act by redesignating subsection (e) of section 1860D-14 of the Act as subsection (f) and by establishing a new subsection (e) Limited Income Newly Eligible Transition (LI NET) Program. Subsection (e)(1) directs the Secretary to carry out a program to provide transitional coverage for covered Part D drugs for LI NET eligible individuals no later than January 1, 2024. We published the Medicare Program; Contract Year 2024 Policy and Technical Changes to the Medicare Advantage Program, Medicare Prescription Drug Benefit Program, Medicare Cost Plan Program, and Programs of All-Inclusive Care for the Elderly final rule (88 FR 22342) in April 2023 establishing the LI NET program as a permanent part of Medicare Part D at 42 CFR part 423 subpart Y, beginning at § 423.2500.</P>
                    <P>
                        Sections 1860D-14(e)(4) and (5) of the Act require that the program be administered through a contract with a single program administrator and 
                        <PRTPAGE P="17555"/>
                        exempt the LI NET program from certain beneficiary protection requirements for qualified prescription drug coverage under section 1860D-4 of the Act. Further, the Secretary may waive other such requirements of title XVIII of the Act as necessary to carry out the purpose of the program. Under our authority under section 1860D-14(e)(5)(B) of the Act, we proposed to codify a waiver for the LI NET program with respect to customer call center hours of operation for all regions served by LI NET.
                    </P>
                    <P>Under § 423.128(d), a Part D sponsor is required to have mechanisms for providing specific information on a timely basis to current and prospective enrollees upon request. Specifically, § 423.128(d)(1)(i)(A) requires that for coverage beginning on and after January 1, 2022, such mechanisms include a toll-free customer call center that is open at least from 8:00 a.m. to 8:00 p.m. in all regions served by the Part D plan. Due to the nature of the LI NET program, maintaining a toll-free customer call center that is open Monday through Friday, except holidays, from 8:00 a.m. to 7:00 p.m. Eastern Time (ET) is sufficient because the customer call volume for LI NET after 7:00 p.m. ET has historically been low due to automatic enrollment of beneficiaries, the transitional nature of LI NET coverage, and LI NET's open formulary. The majority (for example, 90 to 95 percent) of LI NET beneficiaries are enrolled automatically by us and, as such, prospective enrollees rarely require customer call center assistance. Further, the requirement at § 423.128(d)(1)(i)(B) requires that any call center serving pharmacists or pharmacies be open so long as any network pharmacy in that region is open. Accordingly, these calls centers are available to address the majority of inquiries for the LI NET program and ensures that there is no impact on access. This proposal also aligns with the President's January 31, 2025, E.O., titled Unleashing Prosperity Through Deregulation, as we estimate that waiving the requirement for customer call center hours in all regions served by LI NET will save the program approximately $800,000 to $1,000,000 a year.</P>
                    <P>We proposed to add the customer call center hours of operation for all regions served by the Part D plan in § 423.128(d)(1)(i)(A) to the list of Part D requirements waived for the LI NET program at § 423.2536.</P>
                    <P>We do not believe that the changes to the regulatory text will adversely impact the LI NET sponsor, individuals' access to prescription drug benefits, the Medicare Trust Fund, or result in a paperwork burden.</P>
                    <P>The following is a summary of the comments we received and our responses.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters expressed support for the proposal to waive requirements related to customer call center extended hours of operation for the LI NET program. They agreed that the removal of this requirement appropriately reflects the unique structure of the LI NET program and avoids duplicative requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters expressed concern that shorter call center hours may limit access to medications and prescription reimbursement assistance, especially for those with work, caregiving, or transportation constraints. Shorter hours may also inconvenience those with less flexible schedules. A few of the same commenters stated the importance of maintaining phone service for individuals without smartphones or internet access.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we acknowledge the concerns raised by the commenters, we do not believe enrollees' access to medications will be affected. As discussed previously, § 423.128(d)(1)(i)(B) requires that any call center serving pharmacists or pharmacies be open so long as any network pharmacy in that region is open. Consequently, LI NET enrollees have access to a call center as long as the enrollee's pharmacy is open. In addition, the number of calls made to the call center after 7:00 p.m. ET has historically been low due to the short-term nature of LI NET enrollment and the relatively open formulary employed by the LI NET program, which indicates that the call center hours of operation are sufficient to accommodate individuals with limited schedules or lacking internet access.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that the proposed LI NET call center hours waiver does not apply to every plan.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge this comment and agree that the waiver only applies to LI NET. All other plans must follow the extended call center hour requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter acknowledged the significance of telephonic and digital enrollment models in increasing beneficiary access and encouraged uniform safeguards and equivalent scrutiny to ensure beneficiary protection as it pertains to call centers and digital enrollment models.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is out of scope with respect to this proposal to waive requirements related to customer call center extended hours of operation for the LI NET program.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing this proposal without modification.  </P>
                    <HD SOURCE="HD1">VIII. Request for Information on Future Directions in Medicare Advantage (Risk Adjustment and Quality Bonus Payments)</HD>
                    <HD SOURCE="HD2">A. Introduction</HD>
                    <P>
                        The MA program has grown considerably in the past two decades and now covers over half of all Medicare beneficiaries.
                        <SU>124</SU>
                        <FTREF/>
                         In light of this growth, CMS was interested in exploring opportunities for modernizing and strengthening the program, including with regard to payment, risk adjustment, and quality policy, with the aim of supporting competition and maximizing the value of the program for beneficiaries and taxpayers. Specifically, CMS believes that meaningful opportunities exist for enhancing the risk adjustment system and the quality bonus payment (QBP) program, consistent with findings from multiple studies by the Medicare Payment Advisory Commission (MedPAC) 
                        <E T="51">125 126</E>
                        <FTREF/>
                         and other researchers.
                        <E T="51">127 128 129</E>
                        <FTREF/>
                         CMS was particularly interested in changes that can enhance competition in the MA 
                        <PRTPAGE P="17556"/>
                        program; level the playing field for smaller, regional, and less well-resourced MA plans; and address factors that may place these types of plans at a competitive disadvantage. Enhancements to competition in MA would be expected to yield substantial benefits for beneficiaries, taxpayers, health plans, and the Medicare program as a whole. For example, leveling the playing field in MA can translate into greater innovation in benefit design and care models, including greater use of high-value supplemental benefits, reduced use of low-value benefits and services, and improved health outcomes for beneficiaries.
                    </P>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             Medicare Payment Advisory Commission. (March 2025). “Report to the Congress: Medicare Payment Policy, Chapter 11, The Medicare Advantage Program: Status Report.” 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2025/03/Mar25_Ch11_MedPAC_Report_To_Congress_SEC.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             Medicare Payment Advisory Commission. (March 2023). “Report to the Congress: Medicare Payment Policy, Chapter 11, The Medicare Advantage Program: Status Report.” 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2023/03/Ch11_Mar23_MedPAC_Report_To_Congress_SEC.pdf</E>
                            .
                        </P>
                        <P>
                            <SU>126</SU>
                             Medicare Payment Advisory Commission. (2024). “Report to the Congress: Medicare Payment Policy, Chapter 13, Estimating Medicare Advantage coding intensity and favorable selection,” 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2024/03/Mar24_Ch13_MedPAC_Report_To_Congress_SEC.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             Kronick, R., &amp; Chua, F. M. (2021). Industry-wide and sponsor-specific estimates of Medicare Advantage coding intensity. 
                            <E T="03">Available at SSRN 3959446.</E>
                        </P>
                        <P>
                            <SU>128</SU>
                             Markovitz, A. A., Ayanian, J. Z., Sukul, D., &amp; Ryan, A. M. (2021). The Medicare Advantage Quality Bonus Program Has Not Improved Plan Quality: Study examines the impact of the Medicare Advantage quality bonus program. 
                            <E T="03">Health Affairs, 40</E>
                            (12), 1918-1925.
                        </P>
                        <P>
                            <SU>129</SU>
                             Layton, T. J., &amp; Ryan, A. M. (2015). Higher incentive payments in Medicare advantage's pay‐for‐performance program did not improve quality but did increase plan offerings. 
                            <E T="03">Health services research, 50</E>
                            (6), 1810-1828.
                        </P>
                    </FTNT>
                    <P>
                        CMS could pursue changes in MA through two possible channels. The first is through rulemaking or other means authorized under law (for example, the annual announcement of methodological changes to MA payment rates through the Advance Notice and Rate Announcement pursuant to section 1853(b) of the Act), which institute changes that are national in scale. The second channel is by testing a model under section 1115A of the Act through which the CMS Innovation Center can test innovative payment and service delivery models on either a regional or national scale. Section 1115A(c) of the Act authorizes the Secretary to expand the scope and duration of the tested model if such expansion is expected to reduce spending without reducing the quality of care or improve the quality of patient care without increasing spending; the Chief Actuary for CMS certifies the expansion would reduce or not increase program spending, and the Secretary determines that such expansion would not deny or limit the coverage or provision of benefits under the applicable title for applicable individuals. If these requirements are met, the model can be expanded nationally to all relevant stakeholders in a mandatory fashion through rulemaking. Examples of expanded CMS Innovation Center models include the Diabetes Prevention Program,
                        <E T="51">130 131</E>
                        <FTREF/>
                         the Home Health Value-Based Purchasing Model,
                        <SU>132</SU>
                        <FTREF/>
                         and Prior Authorization of Repetitive, Scheduled Non-Emergent Ambulance Transport (RSNAT),
                        <SU>133</SU>
                        <FTREF/>
                         which were found to reduce costs, improve quality, and reduce adverse medical events under Original Medicare. Throughout its history, the CMS Innovation Center has implemented only one MA-specific model, the Value-Based Insurance Design (VBID) model,
                        <SU>134</SU>
                        <FTREF/>
                         which terminates effective December 31, 2025.
                        <SU>135</SU>
                        <FTREF/>
                         A CMS Innovation Center Model can be a channel for testing policy ideas that would benefit from testing, for example, if a policy has uncertain implications. The Innovation Center has the resources and flexibility to identify, develop, rapidly test and encourage voluntary, widespread adoption of innovative care and payment models. A CMS Innovation Center model is also an option for testing innovations that require the statutory authority of the Innovation Center model, for example, statutory waivers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             Centers for Medicare &amp; Medicaid Services. Medicare Diabetes Prevention Program (MDPP): Expanded Model Fact Sheet. 
                            <E T="03">https://www.cms.gov/files/document/mdpp-expansion-fact-sheet.pdf</E>
                            .
                        </P>
                        <P>
                            <SU>131</SU>
                             Centers for Medicare &amp; Medicaid Services. (December 2024). Medicare Diabetes Prevention Program Expanded Model. 
                            <E T="03">https://www.cms.gov/files/document/mln34893002-medicare-diabetes-prevention-program-expanded-model.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             Centers for Medicare &amp; Medicaid Services. Home Health Value-Based Purchasing Model. 
                            <E T="03">https://www.cms.gov/priorities/innovation/innovation-models/home-health-value-based-purchasing-model</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             Centers for Medicare &amp; Medicaid Services. Prior Authorization of Repetitive, Scheduled Non-Emergent Ambulance Transport. 
                            <E T="03">https://www.cms.gov/data-research/monitoring-programs/medicare-fee-service-compliance-programs/prior-authorization-and-pre-claim-review-initiatives/prior-authorization-repetitive-scheduled-non-emergent-ambulance-transport-rsnat</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             Centers for Medicare &amp; Medicaid Services. 
                            <E T="03">https://www.cms.gov/priorities/innovation/innovation-models/vbid</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             Centers for Medicare &amp; Medicaid Services. (2024). Medicare Advantage Value-Based Insurance Design (VBID) Model to End after Calendar Year 2025: Excess Costs Associated with the Model Unable to be Addressed by Policy Changes. 
                            <E T="03">https://www.cms.gov/blog/medicare-advantage-value-based-insurance-design-vbid-model-end-after-calendar-year-2025-excess-costs</E>
                            .
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Risk Adjustment</HD>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>
                        Risk adjustment shapes many aspects of the MA program. Risk adjustment constitutes a key part of the payment process and can influence the MA program in a number of direct as well as indirect ways. MA plan payments are calculated at an individual level to account for a beneficiary's expected health care costs, based on their specific demographic and health characteristics. Risk adjustment is accomplished through the calculation of the risk score, a number representing the ratio between a specific enrollee's predicted Original Medicare costs and average costs within Original Medicare. Ultimately, because risk adjustment has such an important role in payment policy, it can influence the types of enrollees that MA plans target for enrollment, how they market to enrollees, the types of supplemental benefits that plans offer, the prescription drugs that they cover, the providers they contract with, and the types of care that MA enrollees receive.
                        <SU>136</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             Medicare Payment Advisory Commission. (June 2023). “Report to the Congress: Medicare Payment Policy, Chapter 4, The Medicare Advantage Program: Status Report.” 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2023/06/Jun23_Ch4_MedPAC_Report_To_Congress_SEC.pdf</E>
                            .
                        </P>
                    </FTNT>
                      
                    <P>
                        Moreover, risk adjustment impacts competition between MA organizations and may impose inherent disadvantages on certain types of organizations over others.
                        <SU>137</SU>
                        <FTREF/>
                         The existing risk adjustment model relies on medical diagnoses to predict health care costs, in addition to demographic factors, which could lead plans to code more intensely than what is observed in Original Medicare. And while risk adjustment policies are intended to adequately compensate MA plans for their enrollees' expected costs, higher payments associated with higher risk scores may encourage MA organizations to prioritize investments in coding activities over care management or treatment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             Kronick, R., Chua, F. M., Krauss, R., Johnson, L., &amp; Waldo, D. (2025). Insurer-Level Estimates of Revenue From Differential Coding in Medicare Advantage. 
                            <E T="03">Annals of internal medicine, 178</E>
                            (5), 655-662.
                        </P>
                    </FTNT>
                    <P>
                        To account for differences in coding patterns between MA and Original Medicare, section 1853(a)(1)(C)(ii) of the Act requires CMS to apply a coding adjustment factor each year when risk adjusting payments. In 2019 and subsequent years, the adjustment must be at least 5.9 percent. Nevertheless, the higher rates of coding in MA relative to Original Medicare may increase taxpayer expenditures and impose administrative burdens on plans, without any accompanying improvements to quality of care.
                        <SU>138</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             Medicare Payment Advisory Commission. (March 2025). “Report to the Congress: Medicare Payment Policy, Chapter 11, The Medicare Advantage Program: Status Report.” 
                            <E T="03">https://www.medpac.gov/wp-content/uploads/2025/03/Mar25_Ch11_MedPAC_Report_To_Congress_SEC.pdf</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        CMS, therefore, requested feedback in the CY 2027 Proposed Rule on options for risk adjustment, including near-term changes to the existing risk adjustment methodology and entirely new approaches for risk adjustment, such as those that account for recent advances in technology. For example, CMS previously contemplated including MA encounter data in the calibration of risk adjustment models, rather than solely relying on FFS data, to better capture patterns specific to the MA population. CMS sought ideas for additional data sources and data elements for risk adjustment, and for how those data sources should best be incorporated, particularly to minimize opportunities for gaming by MA organizations, 
                        <PRTPAGE P="17557"/>
                        incentivize positive health outcomes, and minimize administrative burden for plans and providers. In particular, CMS sought ideas for risk adjustment approaches that do not rely on collection of diagnoses data and, instead, incorporate alternative factors to infer a patient's health risk as well as the severity of that risk. Finally, CMS was interested in risk adjustment approaches that advance competition and foster a level playing field between different types of MA plans and MA organizations.
                    </P>
                    <HD SOURCE="HD3">2. Solicitation of Comments</HD>
                    <P>We solicited comments on opportunities for improving risk adjustment, inviting comments from a broad range of stakeholders and interested parties, including MA organizations, beneficiary advocates, healthcare providers, and industry experts. We were particularly interested in comments on how to achieve the following goals with risk adjustment, relative to the current state:</P>
                    <P>• Advancing competition, removing anti-competitive barriers, and ensuring a level playing field for regional, smaller, and less well-resourced plans.</P>
                    <P>• Reducing manipulability of the risk adjustment system as well as the day-to-day administrative burden for both plans and providers.</P>
                    <P>• Ensuring accurate payments for sicker beneficiaries, while rewarding effective treatment and favorable patient outcomes.</P>
                    <P>• Mitigating unintended consequences and effectively navigating tradeoffs. (For example, how to approach a situation where a potential input to the risk adjustment model improves the predictive accuracy of the model but would also directly disincentivize valuable treatments for patients.)</P>
                    <P>• Incentivizing provision of tangible and high-value benefits and services and maximizing the value that beneficiaries, as well as taxpayers, get from payments to MA plans.</P>
                    <P>We also solicited more specific comments on potential methods for improving the MA risk adjustment program through the following questions:</P>
                    <P>• Which diagnoses are most essential for CMS to include in its MA risk adjustment model? In certain instances, should CMS limit the use of diagnoses in risk adjustment based on a minimum threshold of disease severity or to patient encounters within specific settings? Should CMS require diagnoses to be substantiated by follow-up encounters or treatments? Similarly, should CMS exclude diagnoses from plan-initiated encounters that do not lead to follow-up care, such as those resulting from in-home health risk assessments, or diagnoses not linked to specific services furnished to an enrollee?</P>
                    <P>• Over what timeframes should CMS incorporate diagnostic data for risk adjustment purposes? How can CMS account for certain illnesses and injuries that are likely to persist but may not be captured within a given data year by a patient encounter? Similarly, how should CMS account for past conditions that are no longer active, but continue appearing as diagnoses?</P>
                    <P>• When incorporating diagnostic data from particular encounters, should CMS account for the payment status of the services associated with that encounter? For example, should the risk adjustment model include diagnoses from encounters where a payment was denied, or approved and later found to be improper?</P>
                    <P>• CMS has publicly discussed the prospect of moving towards a risk adjustment model calibrated based on encounter data. In addition to these efforts, should CMS consider testing new risk adjustment methods that replace the current Hierarchical Condition Category (HCC)-based risk adjustment model, such as an inferred risk adjustment model? How should CMS think about a model that is not primarily or solely based off medical diagnoses, but instead uses other types of information, such as utilization of medical services to infer both the presence and the severity of different conditions? What are alternative inputs that CMS should consider, which would be effective at predicting future health care spending by a patient, incentivizing appropriate care, while not being readily susceptible to gaming and manipulation? Likewise, how can a next generation risk adjustment model be structured to minimize unnecessary administrative burden for plans and providers, and structured to minimize the sensitivity of risk scores to administrative effort or administrative skill? How should a model be structured to best support competition and to ensure a level playing field for all MA plans?</P>
                    <P>• How might CMS utilize technological innovations, such as artificial intelligence (AI) and machine learning, in calibrating current or future risk adjustment methodologies? What are the benefits and risks of shifting from the existing linear regression methodology to one that utilizes AI and/or machine learning? Do plans have best practices when using AI? What types of protections need to be established to ensure the use of AI is fair? Can the efficiencies of AI be leveraged so as to reduce fraud, waste, and abuse?</P>
                    <P>• As part of either the existing HCC model or a next generation risk adjustment model, should CMS draw on additional elements within existing data sources, as well as entirely new sources of data? For example, should CMS incorporate prescription drug event data, beneficiary survey data, electronic medical record data, or lab data to infer an MA patient's expected health care spending and the severity of their medical conditions? What kinds of data elements should CMS draw on within existing data sources, specifically from medical claims and beneficiary characteristics files (for example, procedure information)? Should CMS incorporate additional adjustments for a patient's place of residence to account for variation in costs within individual counties? How should CMS think about potential data sources that are not currently readily accessible or usable for the full population of Medicare beneficiaries, such as electronic medical record data? How should CMS go about making such novel data sources accessible and usable for risk adjustment, given that they would need to be accessible for every Medicare beneficiary?</P>
                    <P>• What other policy approaches should CMS consider to ensure that risk adjustment maximizes incentives for offering high-quality coverage rather than investment in coding practices that may not improve enrollee health?</P>
                    <HD SOURCE="HD2">C. Quality Bonus Payments in Medicare Advantage</HD>
                    <P>In this RFI, we solicited information from stakeholders and all interested parties to inform future policy development and potential refinement to the QBP structure for MA plans as authorized under section 1853(o) of the Act and the impact of QBPs on rebates as authorized under section 1854(b) of the Act.  </P>
                    <P>
                        The solicitation was meant to build upon information obtained from and issues that surfaced under past RFIs. For example, in the 2024 Consolidation in Health Care Markets RFI 
                        <SU>139</SU>
                        <FTREF/>
                         jointly released by the Federal Trade Commission, the Department of Justice, and the Department of Health and Human Services, some respondents notably requested reforms to address potential gaming of risk and quality scores. Also, this solicitation was 
                        <PRTPAGE P="17558"/>
                        intended to address issues previously documented by MedPAC, academic researchers, and others, and in public comments on the annual Advance Notice of Methodological Changes for MA Capitation Rates and Part C and Part D Payment Policies (the Advance Notice).
                    </P>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             Request for Information on Consolidation in Health Care Markets. (June 2024). 
                            <E T="03">https://www.regulations.gov/docket/FTC-2024-0022/document</E>
                            .
                        </P>
                    </FTNT>
                    <P>It takes several years to test, validate, propose, and add a new measure to the Part C and Part D Star Ratings. Separately, for measures that are already implemented, a 2-year lag exists between the end of the measurement period and actual payment to the MA plan. CMS would like to explore potential options to shorten the timeline for implementation of new measures, as well as the lag between measurement and payment for existing measures.</P>
                    <P>The regulations at 42 CFR 422.164(c)(2) and 42 CFR 423.184(c)(2) require CMS to announce potential new measures and solicit feedback through the Advance Notice and Rate Announcement process described in section 1853(b) of the Act and subsequently propose and finalize new measures through rulemaking. In addition, 42 CFR 422.164(c)(3) and 423.184(c)(3) require measures be on the display page on the CMS website for a minimum of 2 years prior to being finalized as Star Ratings measures used for payment. We, therefore, solicited comments on potential methods to condense the timeline to add a new measure to the Star Ratings, for example, by reducing the display period for new measures.</P>
                    <P>For existing measures, the lag between the Star Ratings measurement year and payment year is due to the statutory requirements at sections 1853(o) and 1854(b)(1)(C)(v)-(vi) of the Act, which link the MA bid process to QBP ratings. Since section 1854(a)(1)(A) of the Act requires that MA plans submit their bids not later than the first Monday in June prior to the start of the contract year (which is more than 6 months prior to the start of the contract year), and an MA plan's quality bonus amount impacts their bid submission, CMS uses the latest QBP ratings available as of that date. The QBP ratings thus employed as of the time of the bid involve a measure period from two calendar years prior, ultimately translating into up to a three-year overall lag between measurement and payment. Meanwhile, the time lag between the measurement and payment years creates a disconnect between the quality and financial reward, as MA plans receive bonuses based on their quality performance two years prior, which does not reflect any remediation since that time. To that effect, CMS also solicited information on whether CMS should test an Innovation Center model that would delink QBPs from MA bids, with the aim of further incentivizing health plans to improve quality and providing beneficiaries with more timely and actionable quality information. Specifically, CMS solicited comments on the following questions:</P>
                    <P>• What could an alternative policy look like, if one is needed at all?</P>
                    <P>• What are the potential advantages and disadvantages of the suggested alternative?</P>
                    <P>• When should bonus payments be finalized and disbursed? More broadly, how might CMS better incentivize cost containment within the MA program, while improving care quality?</P>
                    <P>Commenters broadly supported updating MA risk adjustment and the Quality Bonus Payment/Star Ratings framework to better align payments and incentives with beneficiary needs and meaningful outcomes. For risk adjustment, many urged CMS to improve payment accuracy and reduce incentives for coding intensity, including by strengthening the underlying data and better accounting for persistent chronic conditions while avoiding continued credit for conditions that are no longer clinically active. Commenters emphasized transparency, testing, and phased implementation to prevent unintended impacts on high-need populations and program stability.</P>
                    <P>For QBP/Star Ratings, commenters recommended refining measure selection, weighting, and program design to better reflect outcomes and beneficiary experience, improve alignment with other CMS quality programs, and reduce timing lags between measurement and payment. Some raised concerns about overall spending and whether QBP should be budget neutral, while others cautioned against abrupt changes that could disrupt plan benefits and supplemental offerings.</P>
                    <P>We appreciate the feedback received on MA risk adjustment and the Quality Bonus Payment/Star Ratings programs. We will consider these comments as we evaluate future policy directions for the MA program.</P>
                    <HD SOURCE="HD2">D. Well-Being and Nutrition</HD>
                    <P>CMS requested comments on well-being and nutrition policy changes for the MA program, including tools and policies that improve overall health, happiness, and life satisfaction through complementary and integrative health approaches, as well as strategies to achieve optimal nutrition and preventive care, with particular emphasis on improving incentives to ensure MA organizations bear long-term risk for beneficiary health and well-being.</P>
                    <P>CMS received numerous comments in response to this RFI. Comments were overwhelmingly supportive of CMS's focus on nutrition and well-being in MA. Commenters expressed strong support for recognition of nutrition as foundational to preventive care, focus on well-being and nutrition policy development, and efforts to integrate nutrition interventions into Medicare Advantage programs. Comments reflected strong support for integrating nutrition and holistic well-being into Medicare policy, with emphasis on prevention, expanded coverage, and addressing social determinants of health. Comments recommend expanding access to nutrition-related services including medical nutrition therapy (MNT) for malnutrition, obesity, cancer, heart disease, and other conditions affecting nutritional status. Additional recommendations included home-delivered medically tailored meals, oral nutrition supplements for food-insecure populations, produce prescriptions, virtual and in-home visits from multidisciplinary teams, and education opportunities such as grocery store tours and cooking classes.</P>
                    <P>CMS thanks the commenters for expressing their support and sharing their recommendations for comprehensive health, nutrition, and preventive care in the MA program.</P>
                    <HD SOURCE="HD1">IX. Technical Changes to Terminology in Risk Adjustment and in Payments to Sponsors of Retiree Prescription Drug Plans</HD>
                    <P>We proposed to update our regulations related to Medicare Advantage and the Medicare Prescription Drug Program to align with E.O. 14168—Defending Women From Gender Ideology Extremism and Restoring Biological Truth to the Federal Government, issued on January 20, 2025. Per this E.O., we proposed to replace the word “gender” with “sex” in §§ 422.308(c)(1) and 423.884(c)(2)(v)(D).</P>
                    <P>As these terms have no discernable operational difference in meaning with regard to risk adjustment and applications for qualified retiree prescription drug plans, there is no associated burden. Therefore, we did not include a discussion of this provision in the COI section of this rule.</P>
                    <P>We did score this provision in the Regulatory Impact Analysis section because this technical change has no impact on program operations.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters stated that the technical change will create 
                        <PRTPAGE P="17559"/>
                        barriers to care for gender-diverse beneficiaries. A commenter was concerned that the terminology change will create confusion across Medicare Advantage and Medicare Part D payer policies, leading to variability in the interpretation and application of coverage requirements by plans. This commenter also noted that the policy change may lead to confusion in practices because it is not consistent with coding and medical documentation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the concerns raised by the commenters. However, these terms have no discernable operational difference in meaning with regard to risk adjustment and applications for qualified retiree prescription drug plans.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the technical change as proposed.  </P>
                    <HD SOURCE="HD1">X. Collection of Information Requirements</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ), we are required to provide notice in the 
                        <E T="04">Federal Register</E>
                         and solicit public comment before a “collection of information,” as defined under 5 CFR 1320.3(c) of the PRA's implementing regulations, is submitted to the Office of Management and Budget (OMB) for review and approval. To fairly evaluate whether an information collection requirement should be approved by OMB, section 3506(c)(2)(A) of the PRA requires that we solicit comment on the following issues:
                    </P>
                    <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency.</P>
                    <P>• The accuracy of our estimate of the information collection burden.</P>
                    <P>• The quality, utility, and clarity of the information to be collected.</P>
                    <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques.</P>
                    <P>
                        In the Contract Year 2027 proposed rule (90 FR 54894), we solicited public comment on each of these issues for the following sections of the rule that contained information collection requirements. Such comments were received for the provisions proposed under ICR #2 (Strengthened Documentation Standards for Part D Plan Sponsors) and ICR #4 (Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits). A summary of the comments and our responses follow under the applicable ICR section of this final rule. Separately, we received a comment on our use of BLS's National Occupational Employment and Wage Estimates to calculate costs. A summary of that comment and our response follow under section X.A. (
                        <E T="03">Wage Data</E>
                        ) of this final rule.
                    </P>
                    <P>While a number of requirements were finalized on April 15, 2025 (90 FR 15792) under CMS-4208-F (RIN 0938-AV40), the proposed information collection requirement in section VI.B.9. of the Contract Year 2026 proposed rule CMS-4208-P (89 FR 99340) titled “ICRs Regarding Eligibility for Supplemental Benefits for the Chronically Ill (SSBCI) (§ 422.102(f)(4)(iii)(C))” was not finalized at that time. As indicated throughout this preamble, this provision is being finalized in this CMS-4208-F3 rule.</P>
                    <HD SOURCE="HD2">A. Wage Data</HD>
                    <P>
                        To derive average (mean) costs, we are using data from the most current U.S. Bureau of Labor Statistics' (BLS's) National Occupational Employment and Wage Estimates for all salary estimates (
                        <E T="03">https://www.bls.gov/oes/tables.htm</E>
                        ), which, at the time of publication of this final rule, provides May 2024 wages. In this regard, table 6 presents BLS's mean hourly wage, our estimated cost of fringe benefits and other indirect costs (calculated at 100 percent of salary), and our adjusted hourly wage.
                    </P>
                    <GPH SPAN="3" DEEP="108">
                        <GID>ER06AP26.036</GID>
                    </GPH>
                    <P>
                        In response to the commenter's recommendation to use BLS's Employer Costs for Employee Compensation data, we use BLS's National Occupational Employment and Wage Estimates, which provide more job-specific details and categories of employees. In addition, the employer costs shown in both datasets are fairly comparable. For example, the BLS's ECEC dataset for September 2025 estimates the total hourly compensation for management, professional, and related occupations at $77.26/hour.
                        <SU>140</SU>
                        <FTREF/>
                         By contrast, BLS's OEW dataset for May 2024 for management occupations (occupational code 11-0000) reflects a mean hourly wage of $68.15. To account for the cost of fringe benefits and other indirect costs, we doubled the OEW mean hourly wage, yielding a total hourly compensation estimate of $136.30. Our use of BLS's OEW data yields a conservative estimate of labor costs while providing greater specificity in distinguishing wage estimates across job titles and occupational classifications. Accordingly, this rule relies on BLS's OEW data as the basis for the occupational wage estimates used in calculating the burden costs associated with the provisions in this final rule. We will continue to evaluate estimation methods and policy implementation timelines, as appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             U.S. Bureau of Labor Statistics, Employer Costs for Employee Compensation, 
                            <E T="03">https://www.bls.gov/web/ecec.supp.toc.htm.</E>
                        </P>
                    </FTNT>
                    <P>After consideration of the public comments we received, we are finalizing the proposed collection of information requirements using BLS's mean hourly wages doubled for fringe benefits and other indirect costs to estimate the adjusted mean hourly wages.</P>
                    <HD SOURCE="HD2">B. Information Collection Requirements (ICRs)</HD>
                    <P>
                        The following ICRs are listed in the order of appearance within the preamble of this final rule.
                        <PRTPAGE P="17560"/>
                    </P>
                    <HD SOURCE="HD3">1. ICRs Regarding Manufacturer Discount Program (§ 423.100 and §§ 423.2700 Through 423.2768)</HD>
                    <P>
                        As described in section II.C. of the Contract Year 2027 proposed rule, we proposed to codify the policies established under the Manufacturer Discount Program Final Guidance,
                        <SU>141</SU>
                        <FTREF/>
                         with certain refinements, as new subpart AA of part 423.
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             Available at: 
                            <E T="03">https://www.cms.gov/files/document/revised-manufacturer-discount-programfinal-guidance122024.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Codification of the Manufacturer Discount Program policies in this final rule have no impact on the requirements or burden estimates that are currently approved by OMB under control number 0938-1451 (CMS-10846). The collection of information requirements/burden in the Final Guidance are active and properly accounted for in CMS-10846 without the need for change. In this regard, our finalized provisions are not subject to the requirements of the PRA.</P>
                    <P>We received no comments regarding information collection requirements for the Manufacturer Discount Program. We are finalizing the regulatory policies for the Manufacturer Discount Program largely as proposed, with limited modifications, which are described in greater detail in section II.C. of this final rule.</P>
                    <HD SOURCE="HD3">2. ICRs Regarding Strengthened Documentation Standards for Part D Plan Sponsors (§ 423.505)</HD>
                    <P>Under section 1860D-12(b)(3)(C) of the Act and § 423.505(d) and (e), Part D plan sponsors are required to maintain certain categories of documentation for specified periods of time. Specifically, § 423.505(d) requires that the contract between a Part D plan sponsor and CMS include an agreement by the Part D plan sponsor to maintain books, records, documents, and other evidence of accounting procedures and practices for 10 years that are sufficient to meet certain requirements, including enabling CMS to evaluate the quality, appropriateness, and timeliness of services performed under the contract and to audit the services performed or determinations of amounts payable under the contract. In addition, § 423.505(e) requires that Part D plan sponsors agree to HHS, the Comptroller General or their designee to evaluate through audit, inspection, or other means (1) the quality, appropriateness, and timeliness of those services furnished to Medicare enrollees; (2) compliance with CMS requirements for maintaining the privacy and security of protected health information and other personally identifiable information of Medicare enrollees; (3) facilities of the Part D sponsor; and (4) enrollment/disenrollment records for the current contract period and 10 prior periods. Furthermore, §§ 423.568(a)(3), 423.570(c)(2), and 423.584(c)(1) outline requirements for Part D plan sponsors to establish and maintain a method of documenting and to retain documentation for oral requests for coverage determinations under standard timeframes, expedited timeframes, and redeterminations respectively.</P>
                    <P>In the Contract Year 2027 proposed rule, CMS proposed to standardize the documentation requirements that plan sponsors must maintain, in regulation at § 423.505, to ensure that Part D plan sponsors provide CMS with all the information that the plan sponsors use for determining payment responsibility under the Part D benefit. CMS proposed to standardize the documentation requirements because information currently obtained from and relied upon during coverage determinations, or point-of-sale (POS) edits, utilized to determine payment responsibility, are not always maintained in the necessary detail by the Part D plan sponsors to allow CMS to evaluate if the PDE record was covered and paid under the Medicare Part D benefit in compliance with CMS policy or policies.</P>
                    <P>CMS proposed to modify § 423.505 to further clarify and set expectations on the specific type of information needed to support final payment determinations for coverage determinations, and POS edits to determine payment responsibility under the Part D benefit. We proposed documentation requirements that include certain written, verbal, and electronic communications, such as the date and time the request was received; the name and title of the individual who submitted or verified the request; and the information used to make the coverage determination.</P>
                    <P>Based on the current regulations and plan sponsor expectations, CMS believes that this proposal is exempt from PRA requirements as such recordkeeping is a usual and customary business practice (5 CFR 1320.3(b)(2)). The ability of the plan sponsor to demonstrate their compliance with the rules and regulations of the Medicare Part D program is a basic requirement upon entering a contractual relationship with CMS. Plan sponsors are expected to maintain documentation and produce that documentation upon request by CMS to evaluate the appropriateness of the services provided to the Medicare enrollee in accordance with the requirements at § 423.505. Based upon our past audit experience, plan sponsors maintain documentation to varying degrees and in some instances the documentation maintained is not sufficient for CMS to have confidence that the PDE record was covered and paid under the Part D benefit in accordance with CMS policy(ies). As such, CMS proposed the documentation standards to allow CMS to perform the task of evaluating the appropriateness of the Medicare Part D coverage provided by plan sponsors for coverage determinations and POS edits that determine coverage. The documentation requirements must also be provided to CMS, in accordance with requirements at § 423.505 that allow CMS the right to evaluate and provide oversight of the program though audit. As such, we believe the proposed documentation standards that provide clarification of current expectations are exempt from any PRA.</P>
                    <P>As indicated, comments were received. A summary of the comments and our response follow.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters mentioned that the documentation standard proposed may cause increased administrative burden for Part D plan sponsors.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have included minor updates to the proposed language and addressed comments for documentation standards, including commenters' concerns surrounding burden for plan sponsors in this rule's provision for “Strengthened Documentation Standards for Part D Plan Sponsors”. CMS provided clarification that plan sponsors (1) do not need to maintain audio recordings and that transcripts or call notes suffice, (2) only need to maintain communications that 
                        <E T="03">they</E>
                         have with pharmacists, prescribers, enrollees or other stakeholders entities and not communications between these entities, and (3) do not need to perform additional outreach if information available clearly illustrates how a decision for Part D coverage was made.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the proposed provisions with minor modifications in the original draft language to clarify plan sponsor expectations.</P>
                    <HD SOURCE="HD3">3. ICRs Regarding Removing Rules on Time and Manner of Beneficiary Outreach (§§ 422.2264(c) and 423.2264(c))</HD>
                    <P>
                        CMS is finalizing three deregulatory changes to §§ 422.2264(c) and 423.2264(c) to remove rules on the time and manner of beneficiary outreach. The changes are designed to improve the plan decision making process by 
                        <PRTPAGE P="17561"/>
                        creating a more convenient, beneficiary-friendly outreach experience and to reduce burden on beneficiaries, plans, and agents/brokers. The deregulatory changes concern: (1) marketing events following educational events in the same location; (2) the timing of a personal marketing appointment after Scope of Appointment (SOA) form completion; and (3) SOA forms at educational events.
                    </P>
                    <HD SOURCE="HD3">a. Marketing Events Following Educational Events in Same Location</HD>
                    <P>For the elimination of the requirement for a 12-hour delay between an educational and marketing event at §§ 422.2264(c)(2)(i) and 423.2264(c)(2)(i), this rule removes the one-time burden to change the MA organization's policies and procedures. With 697 contracts and 15 minutes (0.25 hr) per response at $88.82/hr for a business operations specialist, we estimate a reduction of minus 174 hours (697 contracts × 0.25 hr) and minus $15,477 (174 hr × $88.82/hr).</P>
                    <HD SOURCE="HD3">b. Timing of Personal Marketing Appointment After Scope of Appointment (SOA) Form Completion</HD>
                    <P>For the elimination of the 48-hour waiting period required between the SOA completion and a personal marketing appointment at §§ 422.2264(c)(3)(i) and 423.2264(c)(3)(i), this rule removes the one-time burden to change the MA organization's policies and procedures. With 697 contracts and 15 minutes (0.25 hr) per response at $88.82/hr for a business operations specialist, we estimate a reduction of minus 174 hours (697 contracts × 0.25 hr) and minus $15,477 (174 hr × $88.82/hr).</P>
                    <HD SOURCE="HD3">c. Scope of Appointment (SOA) Forms at Educational Events</HD>
                    <P>For the elimination of the prohibition of the collection of SOA forms at educational events at §§ 422.2264(c)(1)(ii)(D) and 423.2264(c)(1)(ii)(D), this rule removes the one-time burden to change the MA organization's policies and procedures. With 697 contracts and 15 minutes (0.25 hr) per response at $88.82/hr for a business operations specialist, we estimate a reduction of minus 174 hours (697 contracts × 0.25 hr) and minus $15,477 (174 hr × $88.82/hr).</P>
                    <HD SOURCE="HD3">d. Burden Summary</HD>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="61">
                        <GID>ER06AP26.037</GID>
                    </GPH>
                    <P>We did not receive any comments related to the aforementioned collection of information requirements and burden estimates and are finalizing them in this rule as proposed.  </P>
                    <HD SOURCE="HD3">4. ICRs Regarding Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits (Part 423, Subpart Z)</HD>
                    <P>The effort associated with our finalized requirements under part 423, subpart Z consists of the time for plan sponsors to prepare and submit the appeal requests for: (1) reconsiderations; (2) hearing official review; and (3) review by the Administrator. However, the burden associated with the preparation and submission of appeals is exempt from the requirements of the PRA since such appeals would be submitted in response to an administrative action (5 CFR 1320.4(a)(2) and (c)).</P>
                    <P>We also believe that there would be no need for plan sponsors to establish a new appeals process or revise an existing appeals process.</P>
                    <P>As indicated, comments were received. A summary of the comments and our response follow.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters mentioned that the appeals process may cause increased administrative burden for Part D plan sponsors.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS has addressed comments for the appeals process, including commenters' concerns surrounding burden for plan sponsors in this rule's provision for “Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits”.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing the proposed provisions without modification.</P>
                    <HD SOURCE="HD3">5. ICRs Regarding Eligibility for Supplemental Benefits for the Chronically Ill (SSBCI) (§ 422.102(f)(4)(iii)(C))</HD>
                    <P>The following changes will be submitted to OMB for approval under control number 0938-0753 (CMS-R-267). </P>
                    <P>As outlined in the CY 2026 proposed rule, for each SSBCI, the plan must post the written policies and objective criteria on which the policies are based to a public-facing website. For web developers and programmers to annually post the required information on the plan website, we estimate it will take 2 hours at $130.68/hr (89 FR 99392). We estimate that there are 697 plans including local and regional CCPs, MSA, and PFFS. In aggregate, we estimate an annual burden of 1,394 hours (697 plans * 2 hr/plan) at a cost of $182,168 (1,394 hr * $130.68) Medicare Cost plans are excluded from the count since they are not permitted to offer SSBCI.</P>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="61">
                        <GID>ER06AP26.038</GID>
                    </GPH>
                    <PRTPAGE P="17562"/>
                    <P>We did not receive any comments related to the aforementioned collection of information requirements and burden estimates. We are finalizing our estimates in this rule based on the proposed methodology but with more current data for wages and MA contracts. Our original estimates used wage data and a count of MA contracts that are no longer accurate.</P>
                    <HD SOURCE="HD3">6. ICRs Regarding Passive Enrollment by CMS (§ 422.60)</HD>
                    <P>
                        The requirement and burden change for D-SNPs will be submitted to OMB for approval under control number 0938-TBD (CMS-10953). At this time, the OMB control number has yet to be determined. However, it will be assigned by OMB upon their approval of this collection of information request. The public can monitor the status of our request at 
                        <E T="03">reginfo.gov</E>
                         under Information Collection Review.
                    </P>
                    <P>In our April 2018 final rule, we finalized language authorizing CMS to passively enroll certain dually eligible individuals currently enrolled in an integrated D-SNP into another integrated D-SNP, after consulting with the State Medicaid agency that contracts with the D-SNP or other integrated managed care plan, when CMS determines that the passive enrollment will promote continuity of care and integrated care under § 422.60(g)(1)(iii). We also finalized, under § 422.60(g)(2), requirements an MA plan will have to meet to qualify to receive passive enrollments under paragraph (g)(1)(iii). However, in multiple situations where we have attempted to implement these requirements, we have encountered difficulty with receiving integrated D-SNPs meeting the portion of § 422.60(g)(2)(ii) requiring that receiving integrated D-SNPs have provider networks and facility networks that are substantially similar to the relinquishing integrated D-SNP. In our attempts to utilize passive enrollment, we found that while prospective receiving integrated D-SNPs had Medicare provider and facility networks that meet the MA network adequacy criteria at § 422.112, these networks were not substantially similar to the provider and facility networks in the relinquishing integrated D-SNPs.</P>
                    <P>To address this issue, we are finalizing an amendment at § 422.60(g)(2)(ii) to require that the integrated D-SNP receiving passive enrollment provide a continuity of care to all incoming enrollees for 120 days. We believe that this extended continuity of care period will address the issue that we attempted to address at 83 FR 16504 in the April 2018 final rule, namely that the provider network comparability analysis will minimize the number of enrollees whose provider relationships are disrupted as a result of passive enrollment.</P>
                    <P>
                        Based on July 2025 total D-SNP enrollment, we estimated 6,168,649 D-SNP enrollees per 949 D-SNPs or a CY 2025 average of 6,500 enrollees per D-SNP (6,168,649 D-SNP enrollees/949 D-SNPs).
                        <SU>142</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             CMS, SNP Comprehensive Report, July 2025. Available from: 
                            <E T="03">https://www.cms.gov/data-research/statistics-trends-and-reports/medicare-advantagepart-d-contract-and-enrollment-data/special-needs-plan-snp-data/snp-comprehensive-report-2025-07.</E>
                        </P>
                    </FTNT>
                    <P>We assumed the following costs include paper, toner, envelopes, and postage (envelope weight is normally considered negligible when citing these rates and is not included) for hard-copy mailings:</P>
                    <P>
                        • 
                        <E T="03">Paper:</E>
                         $3.50 for a ream of 500 sheets. The cost for one page is $0.007 ($3.50/500 sheets).
                    </P>
                    <P>
                        • 
                        <E T="03">Toner:</E>
                         $70 for 10,000 pages. The toner cost per page is $0.007 ($70/10,000 pages).
                    </P>
                    <P>
                        • 
                        <E T="03">Envelope:</E>
                         Bulk envelope costs are $440 for 10,000 envelopes or $0.044 per envelope.
                    </P>
                    <P>
                        • 
                        <E T="03">Postage:</E>
                         The cost of first-class metered mail is $0.73 per letter up to 1 ounce. We estimated that a sheet of paper weighs 0.16 ounces (10.0 lb/1,000 sheets × 16 oz/lb), and did not anticipate additional postage for mailings in excess of 1 ounce.
                    </P>
                    <P>We estimated the aggregate cost per mailed notice is $0.802 ([$0.007 for paper * 2 pages] + [$0.007 for toner * 2 pages] + $0.73 for postage + $0.044 per envelope). We assumed a maximum of 2 double-sided pages (generally, weighing less than 1 ounce) would be needed for a passive enrollment notice. Because preparing and generating a hard-copy enrollment notice is automated once the systems have been developed, we did not estimate any labor costs. Therefore, we estimated a total mailing cost by sponsors of $114,686 (6,500 enrollees/D-SNP * 2 mailings * 11 D-SNPs * $0.802/mailing).</P>
                    <P>We did not receive comments on the information collection requirements associated with our proposal and, therefore, are finalizing the information collection requirements without modification.</P>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="103">
                        <GID>ER06AP26.039</GID>
                    </GPH>
                    <HD SOURCE="HD3">7. ICRs Regarding Continuity in Enrollment for Full-Benefit Dually Eligible Individuals in a D-SNP and Medicaid Fee-for-Service (§§ 422.107(d)(1) and 422.514(h))</HD>
                    <P>
                        The following changes will be submitted to OMB for approval under control number 0938-0753 (CMS-R-267). While the control number has expired, we are setting out this rule's collection of information requirements/burden to score the impact of such changes. We intend to use the standard PRA process (which includes the publication of 60- and 30-day non-rule 
                        <E T="04">Federal Register</E>
                         notices) to reinstate the control number with change. The initial 60-day notice will publish sometime after the publication of this final rule.
                    </P>
                    <P>
                        We are amending §§ 422.107(d)(1) and 422.514(h) to allow D-SNPs that serve full-benefit dually eligible individuals in a coordination-only D-SNP or HIDE SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where 
                        <PRTPAGE P="17563"/>
                        those individuals are enrolled in Medicaid FFS. As discussed in section VI.C. of this final rule, we are revising specific provisions from the April 2024 final rule, which limited enrollment in certain D-SNPs to those individuals who are also enrolled in an affiliated Medicaid managed care organization (MCO), and limited the number of D-SNP plan benefit packages an MA organization, its parent organization, or entity that shares a parent organization with the MA organization, could offer in the same service area as an affiliated Medicaid MCO. The provisions that we are finalizing at §§ 422.107(d)(1) and 422.514(h) will create another exception to allow D-SNPs that serve full-benefit dually eligible individuals in a HIDE SNP or coordination-only D-SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where those individuals are enrolled in Medicaid FFS.
                    </P>
                    <P>In the information collection requirements in the April 2024 final rule (89 FR 30784), we stated that the provisions we finalized would create burden for MA organizations that offer multiple D-SNPs in a service area with a Medicaid MCO, noting that impacted MA organizations would need to non-renew or (more likely) combine plans and update systems as well as notify enrollees of plan changes. Using BLS's May 2022 wage data, we also stated in the April 2024 final rule that we expected that MA organizations would need two software engineers with each working 4 hours (or a total of 8 hours) at $127.82/hr to update software in the first year with no additional burden in future years and one business operations specialist working 4 hours at $79.50/hr to update plan policies and procedures in the first year with no additional burden in future years. In aggregate, we estimated a one-time burden (for plan year 2027) of 600 hours (50 plans * 12 hr/plan) at a cost of $67,028 (50 plans × [(8 hr * $127.82/hr) + (4 hr * $79.50/hr)]).</P>
                    <P>The modifications that we are finalizing in section VI.C. of this rule to §§ 422.107(d)(1) and 422.514(h) will allow D-SNPs that serve full-benefit dually eligible individuals in a coordination-only D-SNP or HIDE SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where those individuals are enrolled in Medicaid FFS, and as such, will change which D-SNPs will be required to non-renew or combine plans, affecting the burden estimates finalized in the April 2024 final rule. Given the landscape of States that do not require mandatory Medicaid managed care for all of their full-benefit dually eligible individuals, we believe that based on our estimates, 15 MA organizations would be affected by this finalized exception. To account for the reduction in affected MA organizations under this finalized change to §§ 422.107(d)(1) and 422.514(h) as compared to the finalized burden estimates in the April 2024 final rule, we are reducing the previous burden calculation of 50 MA organizations by 15 MA organizations.</P>
                    <P>Because we estimate that amendments to §§ 422.107(d)(1) and 422.514(h) will reduce the number of impacted MA organizations by 15 as compared to our finalized estimate in the April 2024 final rule, we are providing our estimate in the reduction of burden that would result in finalizing the amendments to §§ 422.107(d)(1) and 422.514(h). The wage estimates reflect May 2024 BLS National Occupational Employment and Wage Estimates, whereas our estimates in the April 2024 final rule used BLS National Occupational Employment and Wage Estimates from May 2022.</P>
                    <P>Using BLS's May 2024 wage data, we continue to expect that MA organizations would need two software engineers with each working 4 hours at $139.00/hr to update software in the first year with no additional burden in future years and one business operations specialist working 4 hours at $88.82/hr to update plan policies and procedures in the first year with no additional burden in future years. In aggregate, we estimated a revised one-time burden (for plan year 2027) of 420 hours (35 plans * 12 hr/plan) at a cost of $51,355 (35 plans × [(8 hr * $139.00/hr) + (4 hr * $88.82/hr)]).</P>
                    <P>In this regard, we estimated a burden reduction of minus 180 hours (420 hr revised−600 hr active) and minus $15,673 ($51,355 revised−$67,028 active).</P>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="56">
                        <GID>ER06AP26.040</GID>
                    </GPH>
                    <P>We did not receive comments on the information collection requirements associated with this proposal and are finalizing the information collection requirements without modification.</P>
                    <HD SOURCE="HD3">8. ICRs Removing Account-Based Medical Plans From Entities Required To Provide Creditable Coverage Disclosures</HD>
                    <P>The following changes will be submitted to OMB for approval under control number 0938-1013 (CMS-10198).</P>
                    <P>As described in section VII.A. (90 FR 54984) of the Contract Year 2027 proposed rule, account-based plans, such as HRAs, including ICHRAs, are group health plans that are not, as section 1860D-13(b)(6)(B)(i) of the Act requires, entities that offer prescription drug coverage. Therefore, the benefit design of account-based plans makes concepts, such as disclosure of creditable coverage, inapplicable to those arrangements. This rule's finalized provision to exclude account-based plans from the group health plans that are required to disclose creditable coverage status to the Secretary and to Medicare-eligible individuals as required under § 423.56 will reduce private expenditures required to comply with federal regulations to provide creditable coverage disclosures, by avoiding duplicative efforts, and eliminating the need for these account-based plans to acquire additional resources and expertise to provide these disclosures.</P>
                    <P>
                        The disclosure to the Secretary is required for certain entities listed at § 423.56(b) that are not excluded at § 423.56(e). The entities exempted under § 423.56(e) include PDPs, MA-PD plans, and PACE or cost-based HMOs or CMPs that provide “qualified Part D coverage” within the meaning of § 423.100. Among the plans that are required to submit this disclosure are group health plans (offered by employers, union/Taft-Hartley plans, church, State and local government, and other group-sponsored plans) including the Federal Employees Health Benefits Program; and qualified retiree prescription drug plans as defined in 
                        <PRTPAGE P="17564"/>
                        section 1860D-22(a)(2) of the Act. As described in section VII.A. of the Contract Year 2027 proposed rule (90 FR 54984), the term, “Group Health Plan” (GHP) was codified at § 423.882 in the 2005 Part D final rule (70 FR 4577), and this definition includes account-based medical plans. The CMS online disclosure system allows entities to select the general type of GHP they offer (for example, employer-sponsored plans). However, the system does not provide for further subsets of the plan type. For example, account-based plans are not sub-categorized under the GHP category. Therefore, CMS does not have specific data on the number of account-based plans that may be making creditable coverage disclosures.
                    </P>
                    <P>
                        As stated in section VII.A. of the Contract Year 2027 proposed rule, ICHRAs, a type of HRAs, are account-based plans that were more recently recognized by the Labor, Health and Human Services, and Treasury Departments in the June 20, 2019 final rule titled, “Health Reimbursement Arrangements and Other Account-Based Group Health Plans” (84 FR 28888). Generally, the impetus for this proposal to not require account-based plans to provide creditable coverage disclosures was from feedback that CMS received from stakeholders asking if ICHRAs were required to provide creditable coverage disclosures. To date, CMS has received minimal to no inquiries on the requirement for other types of account-based plans to make creditable coverage disclosures. Therefore, we attempted to show a decrease in burden by comparing the number of ICHRA plans compared to the total universe of health plans, (about 5 percent), and inputting that percentage to estimate the number of ICHRA plans that are potentially making creditable coverage disclosures to the Secretary.
                        <SU>143</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             According to the 2024 KFF Employer Health Benefits Survey (available at 
                            <E T="03">https://www.kff.org/health-costs/report/2024-employer-health-benefits-survey/</E>
                            ), of firms offering health benefits, 4 percent provide employees funds to purchase non-group coverage (such as through an ICHRA). Of firms not offering health benefits, 7 percent similarly provide employees funds to purchase non-group coverage (such as through an ICHRA). Based on these survey estimates, the weighted number of firms offering health benefits (1,670,244), and the estimated weighted number of firms not offering health benefits (1,589,106), it is estimated that there are 178,047 ICHRA plans in total. This is calculated as (1,670,244*0.04) + (1,589,106*0.07) = 178,047.
                        </P>
                    </FTNT>
                    <P>Using this data, we estimate that about 5 percent of the 140,974 GHPs, or about 7,049 entities (140,974 × 0.05) in our active burden estimates would not be required to make creditable coverage disclosures to the Secretary. Taking approximately 5 total minutes (0.083 hr) for either a Human Resources Manager at $154.30/hr or a Compensation and Benefits Manager at $150.22/hr (whichever individual/occupational title is assigned by the plan) to complete the online disclosure form, we estimate a burden reduction of minus 585 hours (7,049 * 0.083 hr) and minus $90,266 (585 * $154.30/hr for a Human Resources Manager) or minus $87,879 (585 * $150.22/hr for a Compensation and Benefits Manager). We used the higher of our two cost estimates (namely, $90,266) to score our total burden estimates.</P>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="38">
                        <GID>ER06AP26.041</GID>
                    </GPH>
                    <P>We received no comments on this proposal and therefore are finalizing this provision without modification.</P>
                    <HD SOURCE="HD3">9. ICRs Regarding Rescinding the Annual Health Equity Analysis of Utilization Management (UM) Policies and Procedures (§ 422.137(c)(5), (d)(6), and (d)(7))</HD>
                    <P>Section 422.137(c)(5) requires a member of the UM Committee to have expertise in health equity. CMS estimated it takes 30 minutes at $81.72/hr for a compliance officer to update the policies and procedures. By removing this requirement, CMS estimates a one-time burden of 348 hours (697 contracts * 0.5 hr) and $28,438 (348 hr * $81.72/hr).</P>
                    <P>Section 422.137(d)(6) requires the UM Committee to conduct an annual health equity analysis of the use of prior authorization. CMS estimated it takes 8 hours at $139.00/hr for a software developer to collect and aggregate the health equity analysis data required to produce the report. By removing this requirement, CMS estimates an annual burden reduction of minus 5,576 hours (697 contracts * 8 hr/plan) and minus $775,064 (5,576 hr * $139.00/hr).</P>
                    <P>Finally, § 422.137(d)(7) requires that annually, the health equity analysis must be produced and posted to the plan's website. CMS estimated it takes 10 minutes (0.1667 hr) at $88.82/hr for a business operations specialist to produce, inspect, and post the report. By removing this requirement, CMS estimates an annual burden reduction of minus 116 hours (697 contracts * 0.1667 hr/plan) and minus $10,303 (116 hr * $88.82/hr).</P>
                    <P>The following table summarizes our burden estimates.</P>
                    <GPH SPAN="3" DEEP="66">
                        <GID>ER06AP26.042</GID>
                    </GPH>
                    <P>We did not receive any comments related to the aforementioned collection of information requirements and burden estimates and are finalizing them in this rule as proposed.</P>
                    <HD SOURCE="HD2">C. Summary of Information Collection Requirements and Associated Burden</HD>
                    <BILCOD>BILLING CODE P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17565"/>
                        <GID>ER06AP26.043</GID>
                    </GPH>
                    <PRTPAGE P="17566"/>
                    <BILCOD>BILLING CODE C</BILCOD>
                    <HD SOURCE="HD1">XI. Regulatory Impact Analysis</HD>
                    <HD SOURCE="HD2">A. Statement of Need</HD>
                    <P>This final rule addresses several critical needs in the Medicare Advantage (Part C), Medicare Prescription Drug Benefit (Part D), and Medicare cost plan programs that require regulatory action to ensure program integrity, beneficiary protection, and statutory compliance. The provisions finalized in this rule are intended to codify statutory requirements of the Inflation Reduction Act of 2022 (IRA) (Pub. L. 117-169), and provide greater clarity on the Star Ratings system for plans operating in the MA and Part D spaces.</P>
                    <P>One of the primary drivers for this rulemaking is the statutory mandate to codify changes made by the IRA. The IRA fundamentally restructured the Part D benefit design and established new payment obligations for enrollees, Part D plan sponsors, pharmaceutical manufacturers, and CMS. Without regulatory implementation of these statutory changes, the Medicare program cannot comply with Federal law or provide the intended beneficiary protections and cost savings provided under statute. Specifically, the IRA requires CMS to codify changes to Part D benefit phases, including the deductible, initial coverage limit, coverage gap, and the annual out-of-pocket threshold, as well as to sunset the Coverage Gap Discount Program and to establish the Medicare Part D Manufacturer Discount Program.</P>
                    <P>The changes to Star Ratings address the ongoing need to simplify and refocus quality measurement, improving transparency for MA organizations and Part D sponsors. The current Star Ratings system has grown in complexity over time, and stakeholders have requested streamlining to focus on the most impactful quality measures. The modifications being finalized respond to these requests and should make the Star Ratings system more comprehensible and predictable.</P>
                    <P>The absence of regulatory action would result in statutory non-compliance regarding IRA implementation, ongoing operational inefficiencies, and missed opportunities for program improvement and innovation. Therefore, this rulemaking is necessary to ensure the Medicare program operates effectively, efficiently, and in compliance with Federal law while serving the best interests of Medicare beneficiaries.</P>
                    <HD SOURCE="HD2">B. Overall Impact Analysis</HD>
                    <P>We have examined the impacts of this final rule as required by Executive Order 12866 on Regulatory Planning and Review (September 30, 1993); Executive Order 13132, “Federalism”; Executive Order 14192, “Unleashing Prosperity Through Deregulation”; the Regulatory Flexibility Act (RFA) (Pub. L. 96-354); section 1102(b) of the Act; and section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4).</P>
                    <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and distributive impacts). Section 3(f) of Executive Order 12866 defines a “significant regulatory action” as an any regulatory action that is likely to result in a rule that may: (1) have an annual effect on the economy of $100 million or more, or adversely affect in a material way a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or Tribal governments or communities; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impacts of entitlement grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, or the President's priorities.</P>
                    <P>A regulatory impact analysis (RIA) must be prepared for a regulatory action that is significant under section 3(f)(1) of E.O. 12866. Based on our estimates, OIRA has determined this rulemaking is significant under section 3(f)(1) of E.O. 12866.</P>
                    <HD SOURCE="HD2">C. Detailed Economic Analysis</HD>
                    <P>Many provisions of this final rule have negligible impact either because they are technical provisions or clarifications. Throughout the preamble we have noted when we estimated that provisions have no impact. Additionally, this Regulatory Impact Analysis discusses several provisions with either zero impact or impact that cannot be quantified. The remaining provisions' effects are estimated in section X. of this final rule, which estimates costs associated with paperwork burden resulting from this rule. Where appropriate, when a group of provisions have both paperwork and non-paperwork impact, this RIA cross-references impacts from section X. of this final rule in order to arrive at the total impact. Table 7 summarizes the estimated transfers and costs associated with the various provisions in this final rule over a 10-year period. Further details are provided later in this RIA.</P>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="17567"/>
                        <GID>ER06AP26.044</GID>
                    </GPH>
                      
                    <PRTPAGE P="17568"/>
                    <HD SOURCE="HD3">1. Effects of Part D Redesign: Redesigned Part D Benefit</HD>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify changes to the Part D benefit made by section 11201 of the IRA related to the deductible, the initial coverage limit, the coverage gap, the annual out-of-pocket (OOP) threshold, and alternative prescription drug coverage options.</P>
                    <P>
                        The CMS Office of the Actuary estimated the impacts of the drug provisions of the IRA using the 2024 President's Budget as a baseline early in calendar year 2023. These estimates were made prior to many policy decisions to implement the law, and independently from other components of CMS. Since the majority of these provisions have already been implemented through program instruction,
                        <SU>144</SU>
                        <FTREF/>
                         this estimate should be taken only in its historical context, not as a reflection on the experience since the provisions' effectuation. Additionally, these estimates measure the overall impact of the IRA on Medicare, whereas this regulation codifies only certain provisions of the law. We will highlight certain components of this estimate where recent experience has diverged from our initial assumptions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             This includes the Medicare Drug Price Negotiation Program Guidance with respect to initial price applicability years 2026, 2027, and 2028; the Part D Redesign Program Instructions for CY 2025 and 2026 (as discussed in section II.A. of this final rule); and the Medicare Part D Manufacturer Discount Program Final Guidance for CYs 2025 and 2026 (as discussed in section II.C. of this final rule).
                        </P>
                    </FTNT>
                    <P>The IRA has a range of Medicare provisions, including restraining price growth and negotiating drug prices for certain drugs payable under Part B and covered under Part D, as well as redesigning the Part D benefit structure to decrease beneficiary out-of-pocket costs. The provisions of the IRA take effect over several years, resulting in very different effects by year. Much of the Part D benefit redesign became effective in 2025, for example, before the Negotiation Program provisions can have any offsetting effects.</P>
                    <P>To model the Negotiation Program provisions of the IRA, we first determined which drugs would be selected for negotiation in accordance with sections 11001 and 11002 of the IRA. Using 2022 experience for Part B and Part D claims, we ranked drugs by Part B and Part D expenditures and then applied the eligibility criteria specified in the IRA—verifying, in particular, that the ranked drugs had been on the market long enough to qualify for negotiation. From this list, we generated the potential list of drugs to be negotiated in each year for Part B and Part D.</P>
                    <P>To estimate the impact of negotiation and to measure the differences between the current prices and the ceiling price and other pricing parameters laid out in the IRA, we used 2021 data from a variety of sources, including PDE records, Medicaid Average Manufacturer Price data, and Part B ASP data. We assumed, after comparing the Medicare prices to the ceiling prices in each projection year, that Medicare would be able to negotiate slightly below the ceiling price in Part D. We then adjusted for generic and biosimilar launches that, should they happen after the selection process, would potentially limit the impact of the maximum fair price. Lastly, we adjusted for changes in the percentage of spending that the selected drugs would represent over time. The discounts relative to total 2021 Part D allowed cost, prior to manufacturer rebates and total Part B allowed cost, are shown in Table 8.</P>
                    <GPH SPAN="3" DEEP="61">
                        <GID>ER06AP26.045</GID>
                    </GPH>
                    <P>For Part D, the benefit is considerably enriched under the IRA redesign, and the most impactful changes took effect in 2025. To estimate these effects inclusive of the Negotiation Program impacts, we incorporated the negotiated price at the drug level into a beneficiary- and claim-level detailed model. Then, we recalculated the new benefit on the negotiated prices to determine the combined result under the defined standard benefit design by year. To protect beneficiaries from large premium increases, the IRA limits the premium change in years 2024 through 2029 before ultimately readjusting the base beneficiary premium percentage to a minimum of 20 percent in 2030 and later years. The major benefit changes and beneficiary premium protections by year are shown in Table 9.</P>
                    <GPH SPAN="3" DEEP="182">
                        <PRTPAGE P="17569"/>
                        <GID>ER06AP26.046</GID>
                    </GPH>
                    <P>To complete the modeling of the Negotiation Program, prescription drug inflation rebates, and benefit provisions, we applied the results from the Part D claim-level detailed simulation to our total Part D benefit model. This model also incorporated changes to the per capita cost trends to reflect: (i) the impact of most existing brand-name drugs moving to a CPI-level increase; (ii) the expected growth in new drug costs; and (iii) the expected induced utilization due to the enriched benefit. We assumed that drugs with a significant amount of spending in Part D would temper their price increases rather than pay the inflation rebates required by the IRA. Additionally, we reduced manufacturer rebates to compensate for the lower negotiated prices and lower price growth on existing drugs.</P>
                    <P>For drugs payable under Part B, we applied the negotiated price discounts to the OM spending for separately payable Part B drugs. We further adjusted these results to account for the impact to private health plan expenditures to obtain a total impact. While there are also inflation rebates required for certain drugs payable under Part B drugs under the IRA, price increases on existing drugs payable under Part B historically have been close to the CPI in aggregate, and therefore we did not project an effect for this provision in the drugs payable under Part B. We also incorporated other, less significant changes from the IRA, such as the lower cost sharing for insulins furnished under durable medical equipment and the temporary payment increase for biosimilar products.  </P>
                    <P>Our assumptions on the impacts of the IRA differed from those used in other public estimates in a few critical ways. Most importantly, we assumed that the inflation rebates required by the IRA would result in manufacturers paying relatively small inflation rebate amounts for drugs covered under Part D and nothing for drugs payable under Part B. We assumed that manufacturers would prefer to have lower price trends that would incentivize greater use than pay publicly reported fees for price increases that exceed inflation. Under this assumption, the effects of the inflation rebate provisions of the IRA are changed because the difference in price is shared across the benefit rather than accruing directly to the government. In other words, lower list price trends will reduce prices paid at the pharmacy relative to the baseline, which results in lower beneficiary cost sharing and lower state clawback payments, thereby increasing the federal cost for the Part D benefit. To compensate for the loss of price increases, we expected manufacturers to reduce rebates offered to plan sponsors.</P>
                    <P>Additionally, we expected that the initial pool of drugs covered under Part D selected for negotiation would have a large proportion of heavily rebated drugs. In these cases, we expected that the price net of rebate will be substantially lower than the other ceiling prices described in the IRA. We further estimated that the effect of negotiation in the early years would be similar to the impact of shifting rebates to the point of sale. This shift reduces beneficiary cost sharing as the price at the point of sale is lower, but increases bid amounts and increases federal expenditures.</P>
                    <P>In summary, the total effects were to reduce government expenditures for Part B, to increase expenditures for Part D through 2030, and to decrease Part D expenditures beginning in 2031. Part B savings were primarily due to: (i) the substantial lowering of payments, relative to current payment, as a result of negotiated prices; and (ii) small impacts from other provisions. Part D ultimately generated cost savings at the end of the budget window, but many of the gains from negotiated prices and lower trends were initially spent on increased benefits and the loss of manufacturer rebates. The impact on benefits and premiums and the impact in total are shown in Table 10 using the 2024 President's Budget as a basis.</P>
                    <GPH SPAN="3" DEEP="348">
                        <PRTPAGE P="17570"/>
                        <GID>ER06AP26.047</GID>
                    </GPH>
                    <P>Since we produced these estimates, both the Part B and Part D programs have had large increases in drug expenditures. Part D trends have accelerated dramatically, with the per capita gross drug cost increasing more than 18 percent in 2025 over 2024, driven by higher glucagon-like peptide-1 (GLP-1) and specialty drug usage. Meanwhile Part B drug trends have also increased, although the primary driver was skin substitutes that were not FDA-approved drugs. There are a variety of other causes contributing to observed changes in expenditures for both programs.</P>
                    <P>The Part D trends in per capita gross costs are shown in table 11. Much of the IRA Part D benefit redesign took effect in 2025, including limiting annual out of pocket expenditures to $2,000 per enrollee for 2025 (to be annually increased by the annual percentage increase, as described in section 1860D-2(b)(6) of the Act). While this new feature could have induced spending beyond the assumption we included in our initial estimate, it is worth noting that the 2024 benefit structure under the IRA also eliminated cost-sharing in the catastrophic phase of the benefit, effectively implementing an out-of-pocket maximum without a pronounced increase in costs. Additionally, some of the increase may be attributable to manufacturers reducing spending on patient assistance programs, which would cause more claims to run through the Part D program. Expanded indications for cancer drugs also contributed to the increase.</P>
                    <GPH SPAN="3" DEEP="219">
                        <PRTPAGE P="17571"/>
                        <GID>ER06AP26.048</GID>
                    </GPH>
                    <P>The observed discounts from maximum fair prices for selected drugs also differed from what we initially assumed. For initial price applicability year 2026, the projected negotiated discount impact on allowed costs—ingredient cost, dispensing fee, and sales tax—using 2025 experience data is 11.3 percent, while the projected impact for initial price applicability year 2027 is 18.2 percent. Compared with the original estimated effects shown in Table 8, the actual negotiated discounts are more than two percent greater than the original modeling results. These differences reflect the deviation in price levels, updated information about generic and biosimilar launches, and the percentage of expense the negotiated drugs represent for each year. Part B negotiated prices for initial price applicability year 2028 are not currently available, so we do not quantify the change from our original assumptions. We also had assumed that maximum fair prices for initial price applicability years 2026 and 2027 would also apply to Part B utilization. Final policies for those years contained the maximum fair prices to the Part D benefit. This change from our assumption did not meaningfully affect overall estimates, due to multiple factors including limited observed utilization of most IPAY 2026 and IPAY 2027 drugs in Part B and the timing of certain generic or biosimilar entrants.</P>
                    <P>Part D drug inflation rebates were higher than originally assumed. Converting the published inflation rebates owed from the applicable period to a calendar year basis, 2023 inflation rebates were over $500 million dollars. This is higher than the $400 million dollar estimate shown in Table 10. This implies that drug prices increased slightly faster than originally assumed, generating higher inflation rebates. As a percentage of gross drug costs, the original estimate represents 0.01 percent, while the actual amount was 0.02 percent.</P>
                    <P>For Part B, our original estimates assumed that the drug inflation rebates would be negligible. Actual Part B drug inflation rebates due for calendar years 2023 and 2024 were $14 million and $121 million, respectively. These amounts represent approximately 0.01 percent and 0.04 percent of the incurred charges for OM in 2023 and 2024. Since drug inflation rebates are not incurred on MA utilization, this is the most appropriate comparison.</P>
                    <P>Other, more nuanced elements of the IRA changes also differed from our original expectations. For example, the Manufacturer Discount Program is likely larger than we initially assumed, but the PDE reporting is not yet complete for the discount's first year. Similarly, the impacts of the IRA on Part D DIR are unknown, as Part D plan sponsors have not yet submitted the 2025 DIR reports. These elements may have larger effects on overall Part D expense than the other assumption deviations described previously.  </P>
                    <P>The costs and transfers attributable to the Part D redesign are attributable to the IRA and are not a result of this rule.</P>
                    <P>We received no comments on the impacts of the Part D redesign proposals. We are finalizing those provisions without modification, as discussed in section II.A. of this final rule.</P>
                    <HD SOURCE="HD3">2. Effects of Part D Redesign: Specialty Tier</HD>
                    <HD SOURCE="HD3">a. Limit on Specialty-Tier Cost Threshold Adjustment (§ 423.104(d)(2)(iv)(B))</HD>
                    <P>In the Contract Year 2027 proposed rule, we proposed to revise § 423.104(d)(2)(iv)(B)(1) and (2) to allow CMS to reduce the specialty-tier cost threshold under certain circumstances, in addition to the current authority to increase the threshold. This change will provide CMS with additional flexibility to reduce the threshold in response to market conditions, such as potential reductions in Part D drug costs resulting from the Medicare Drug Price Negotiation Program.</P>
                    <P>The methodology for determining whether a threshold adjustment is warranted remains the same (at least 10 percent change from the prior year), and the rounding methodology remains unchanged. This provision does not impose new requirements on Part D sponsors or change existing operational processes.</P>
                    <P>
                        This provision codifies a conforming change made in response to the redesigned Part D benefit; thus, the impact analysis of the redesigned Part D benefit discussed in section XI.C.1. of this final rule does not relate to this provision. We do not anticipate that this provision will have a measurable economic impact on Part D sponsors, beneficiaries, or the Medicare program, as it is only providing CMS with flexibility in making threshold adjustments without altering the underlying methodology or operational requirements.
                        <PRTPAGE P="17572"/>
                    </P>
                    <HD SOURCE="HD3">b. Specialty-Tier Maximum Allowable Cost Sharing (§ 423.104(d)(2)(iv)(D))</HD>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify the methodology for determining the specialty-tier coinsurance/deductible ranges that was established in the Final CY 2025 Part D Redesign Program Instructions. This provision will update the existing calculation methodology to align with the redesigned Part D benefit structure implemented under the IRA, which eliminated the initial coverage limit.</P>
                    <P>The methodology maintains the existing 25 percent minimum and 33 percent maximum coinsurance for specialty tiers. While the underlying calculation has been updated to reflect the redesigned Part D benefit, the range of allowable coinsurance percentages remains unchanged. Part D sponsors must continue to ensure their benefit designs are actuarially equivalent to the defined standard benefit, as required under existing regulations.</P>
                    <P>Because this provision codifies a conforming change made in response to the redesigned Part D benefit, the impact analysis of the redesigned Part D benefit discussed in section XI.C.1. of this final rule does not relate to this provision. In the Contract Year 2022 final rule (86 FR 6078), we codified the specialty-tier maximum allowable cost-sharing methodology and concluded that the specialty-tier provisions, including those permitting Part D sponsors to structure their benefits with a second, “preferred” specialty tier were unlikely to have a material impact on Part D costs. Likewise, we do not anticipate that finalizing our update to this methodology to align with the redesigned Part D benefit will have a measurable economic impact on Part D sponsors, beneficiaries, or the Medicare program, as it maintains the same coinsurance ranges that are currently in effect.</P>
                    <P>We received no comments on the impacts of this proposal and are finalizing this provision without modification.</P>
                    <HD SOURCE="HD3">3. Effects of the Medicare Coverage Gap Discount Program (§§ 423.100, and 423.2300 through 423.2345 (Subpart W))</HD>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify the sunset of the Coverage Gap Discount Program, which was enacted under the Affordable Care Act and began on January 1, 2011. The Part D benefit redesign under section 11201 of the IRA, which eliminated the coverage gap phase of the Part D benefit, included sunsetting the Coverage Gap Discount Program on January 1, 2025, and, with respect to applicable drugs dispensed prior to such date, continue to apply on and after January 1, 2025.</P>
                    <P>The costs and transfers attributable to the Part D benefit redesign, including sunsetting the Coverage Gap Discount Program, are attributable to the IRA, as described in greater detail in section C.1 of this Detailed Economic Analysis, and are not a result of this rule.</P>
                    <P>We received no comments on the impacts of the proposals related to the Coverage Gap Discount Program, which we are finalizing without modification.</P>
                    <HD SOURCE="HD3">4. Effects of the Medicare Part D Manufacturer Discount Program (§§ 423.1, 423.100, 423.505(b), 423.1000, 423.1002, and 423.2700 through 423.2768 (Subpart AA))</HD>
                    <P>In the Contract Year 2027 proposed rule, we proposed to codify policies implementing the Manufacturer Discount Program, established under section 11201 of the IRA as part of the Part D benefit redesign. Section 11201(f) of the IRA directed CMS to implement the Manufacturer Discount Program using program instruction or other forms of program guidance for 2025 and 2026. The Manufacturer Discount Program began on January 1, 2025, and we proposed to codify the policies that have been in place since the program's implementation, with refinements.</P>
                    <P>The costs and transfers attributable to the Part D Redesign, including codifying the Manufacturer Discount Program, are attributable to the IRA, as described in greater detail in section C.1. of this Detailed Economic Analysis, and are not a result of this rule.</P>
                    <P>We received no comments on the impacts of the Manufacturer Discount Program proposals. We are finalizing the policies largely as proposed, with limited modifications, which are described in greater detail in section II.C. of this final rule.</P>
                    <HD SOURCE="HD3">5. Effects of Third-Party Marketing Organization (TPMO) Oversight: Revising the Record Retention Requirements for Marketing and Sales Call Recordings</HD>
                    <P>This provision proposed to reduce the amount of time that MA organizations and Part D sponsors are required to retain recordings for sales and marketing calls from 10 to 6 years, which was originally established in the May 2022 final rule (87 FR 27704) and subsequently modified in the April 2023 final rule (88 FR 22120) which required an MA organization or a Part D sponsor's contract, written arrangement and/or agreement with the aforementioned entities to ensure that marketing, sales, and enrollment calls with beneficiaries are recorded in their entirety. In addition, CMS has advised that marketing, sales, and enrollment call recordings must comply with the record retention requirements at §§ 422.504(d) and 423.505(d). As finalized, CMS is reducing the overall retention time from 10 to 6 years. Years 1 through 3 must be audio recordings, and years 4 through 6 can be either audio recordings or transcripts. This will take effect on October 1, 2026, to coincide with the beginning of the 2027 plan year marketing, as defined under §§ 422.2263(a) and 423.2263(a).</P>
                    <P>To determine the cost of the existing requirement and thus estimate the cost savings, CMS reviewed different types of storage costs. The first type is cloud storage where an entity pays per gigabyte or terabyte and the cost is determined based on the amount of data and how accessible the entity wants the data to be (for example, standard storage, cold line storage, archive storage, etc.). CMS also reviewed other options available for TPMOs, especially individual agents or small agencies, to record and store calls. In this review, CMS found that the industry created or marketed (or both) different recording tools available to agents and brokers. These tools have a wide range of costs, ranging from free recording services to other tools that are structured around monthly or yearly fees. Moreover, based on information gleaned from previous regulatory work, CMS has also been made aware that field marketing organizations (FMOs) may provide agents and brokers with access to call recording technology at a reduced cost or otherwise factor it into agent/broker contractual arrangements. Finally, CMS noted that many of these tools are proprietary and total costs may not be fully transparent until a purchase (or contractual agreement) is made. All told, the variability made it more difficult to establish the savings associated with this provision.  </P>
                    <P>
                        In this final rule, CMS is finalizing a requirement that agent and broker marketing and sales audio call recordings to be stored for years 1 through 3 and permits either audio call recordings or transcripts for years 4 through 6. To estimate the cost savings associated with revising the call recording retention requirement, CMS had to estimate both the cost to record and retain audio recordings as well as the cost to transcribe calls and retain the transcriptions. In estimating costs, CMS assumes MA plans and Part D sponsors will retain documentation through the use of transcripts for years 4 through 6.
                        <PRTPAGE P="17573"/>
                    </P>
                    <P>
                        CMS used the same methodology as in the Contract Year 2027 proposed rule for estimating the costs of call recordings. CMS first estimated the number of licensed and appointed agents to sell Medicare products, including MA plans and PDPs, to be 100,000.
                        <SU>145</SU>
                        <FTREF/>
                         CMS acknowledged that there is a range of how each agent accesses call recordings and storage and how much each will pay for these features. CMS also acknowledged that the typical cost to agents combines both the recording and the storage costs into one fee. With these challenges acknowledged, for the Contract Year 2027 proposed rule, CMS used an average cost of $35 per month, or $420 per year for call recording tools based on the median of the costs that agency was able to identify.
                        <E T="51">146 147 148 149</E>
                        <FTREF/>
                         Further, CMS estimated that approximately 60 percent of the cost is attributed to the recording costs while the other 40 percent is attributed to the cost of storage ($14 is storage [35*0.4]). The Contract Year 2027 proposed rule for a 6-year audio recording retention period estimated a savings of $5.6 per month ($14*0.4), resulting in a savings of $67.2 per year per agent. Using the $67.2 per year, combined with the estimated 100,000 agents and brokers licensed and appointed to sell Medicare products, CMS estimated that this provision would save an estimated $6.72 million per year ($67.2 [savings per agent per year] * 100,000 [agents]), or $67.2 million over a 10-year period.
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             
                            <E T="03">https://www.sparkadvisors.com/resource/where-agents-become-pawns-the-dark-side-of-fmo-contracting-and-what-it-means-for-agents</E>
                            .
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             
                            <E T="03">https://www.claap.io/blog/chorus-pricing.</E>
                        </P>
                        <P>
                            <SU>147</SU>
                             
                            <E T="03">https://www.nextiva.com/x20/lpGVDT11_i?utm_source=getvoip&amp;utm_medium=affiliate&amp;utm_campaign=lpgvdt&amp;utm_term=nextiva%20plans.</E>
                        </P>
                        <P>
                            <SU>148</SU>
                             
                            <E T="03">https://www.zoom.us/pricing/zoom-phone.</E>
                        </P>
                        <P>
                            <SU>149</SU>
                             CMS recognizes that some of the tools do not include unlimited, 10-year storage. Storage may be an additional cost.
                        </P>
                    </FTNT>
                    <P>
                        To estimate the cost to capture and retain calls via a transcript, CMS reviewed the cost and processes associated with converting calls into transcripts. Converting recorded calls into transcripts range from $0.10 to $0.30 per minute for AI generated transcripts while human generated transcripts beginning at $1.25 per minute.
                        <SU>150</SU>
                        <FTREF/>
                         These costs were based on transcriptions being completed after the call, using the original call recording.
                    </P>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             
                            <E T="03">https://rev.outgrow.us/rev-pricing-calculator; https://www.scribbl.co/post/cost-for-transcription-services; https://www.gmrtranscription.com/prices#GenTranscription; https://www.dittotranscripts.com/blog/how-much-do-human-transcription-services-cost/#:~:text=How%20Much%20Does%20Human%20Transcription,and%20thus%20incur%20higher%20fees</E>
                            .
                        </P>
                    </FTNT>
                    <P>
                        While reviewing the costs to transcribe calls, CMS identified other methods of recording and transcribing calls. In the current marketplace, applications are available to simultaneously record and transcribe calls. These applications vary in pricing, with the estimated cost ranging from $109 per year to $300 per year, depending on whether the agent/broker is using a “standard” or “pro version”.
                        <SU>151</SU>
                        <FTREF/>
                         Using these updated costs, CMS is revising our final cost estimate for the final regulation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             
                            <E T="03">https://www.withallo.com/blog/best-call-transcription-software-apps.</E>
                        </P>
                    </FTNT>
                    <P>Using the originally proposed number of agents at 100,000 and an average of the updated cost of $204.5 [109+300)/2], CMS estimates that the final regulation will save $20.5 million per year ($204.5*100,000) or $205 million over the course of 10 years. Based on the previous noted limitations, CMS specifically requested comments on these estimates and welcomed additional data that may help the Agency to further quantify the savings associated with this provision. We requested comments on our assumptions of savings, taking into account the continued requirement for the recording of a beneficiary's enrollment into a plan.</P>
                    <P>We did not receive comments on the impact of this provision in the Contract Year 2027 proposed rule. Based on CMS's updated information the provision is being finalized with the modifications identified previously.  </P>
                    <HD SOURCE="HD3">6. Effects of Medicare Advantage/Part C and Part D Prescription Drug Plan Quality Rating System (§§ 422.164, 422.166, 423.184, and 423.186)</HD>
                    <P>We proposed to add and remove certain measures from the Part C and D Star Ratings program. Historically, measure additions and removals are routine, and such routine changes have had very little or no impact on the highest ratings (that is, overall rating for MA-PD contracts, Part C summary rating for MA-only contracts, and Part D summary rating for PDPs). However, given the number of measure removals finalized in this rule, we have estimated the impact of the measure removals on the Medicare Trust Fund in this rule. We also proposed to not move forward with the implementation of the Health Equity Index (HEI) reward and to continue to include the historical reward factor in the Star Ratings methodology. Beyond the Medicare Trust Fund, there may be effects on supplemental benefits, premiums, and plan profits. These impacts will likely vary significantly from plan to plan (or contract to contract) based on the business strategies and the competitive landscape for each plan and contract.</P>
                    <P>We simulated the cumulative impact of the finalized changes on MA contracts using the 2025 Star Ratings data. We calculated the net impacts summarized in Table 7 due to these finalized Star Ratings updates by quantifying the difference in the MA organization's final Star Rating with the finalized changes and without the finalized changes. We assume Medicare Trust Fund impacts due to the Star Ratings changes associated with these finalized revisions to the measure set and methodology. Not moving forward with the implementation of the HEI and continuing to include the historical reward factor will be effective for the 2027 Star Ratings and will impact the 2028 plan payments and 2028 Quality Bonus Payments (QBPs). The removal of the Call Center—Foreign Language Interpreter and TTY Availability (Part C), Call Center—Foreign Language Interpreter and TTY Availability (Part D), and Statin Therapy for Patients with Cardiovascular Disease (Part C) measures will be effective also for the 2028 Star Ratings and will impact the 2029 plan payments and 2029 QBPs. The removal of the remaining measures (with the exception of the Diabetes Care—Eye Exam measure which will remain in the Star Ratings, as discussed in section V.B. of this final rule) will be effective for the 2029 Star Ratings and will impact the 2030 plan payments and 2030 QBPs.</P>
                    <P>All impacts are considered transfers, but we requested comments on the extent to which provision of goods or services would increase or decrease in association with the payment changes. The impact analysis for the Star Ratings updates takes into consideration the final quality ratings for those MA contracts that would have Star Ratings changes under this final rule impact analysis. There are two ways that Star Ratings changes will impact the Medicare Trust Fund:</P>
                    <P>• A Star Rating of 4.0 or higher will result in a QBP for the MA contract, which, in turn, leads to a higher benchmark for the MA plans offered by the MA organization under that contract. MA organizations that achieve an overall Star Rating of at least 4.0 qualify for a QBP that is capped at 5 percent (or 10 percent for certain counties).</P>
                    <P>
                        • The rebate share of the savings will be higher for those MA organizations that achieve a higher Star Rating. The 
                        <PRTPAGE P="17574"/>
                        rebate share of savings amounts to 50 percent for plans with a rating of 3.0 or fewer stars, 65 percent for plans with a rating of 3.5 or 4.0 stars, and 70 percent for plans with a rating of 4.5 or 5.0 stars.
                    </P>
                    <P>In order to estimate the impact of the Star Ratings updates, baseline assumptions are updated with the assumed Star Ratings changes described in this final rule. We estimated the cumulative impact of the finalized changes to the Star Ratings calculations since there are interactions between the changes. We updated the estimated impacts from the Contract Year 2027 proposed rule because, as discussed in section V.B. of this final rule, we are retaining the Diabetes Care—Eye Exam measure in the Star Ratings. The impacts are shown in Table 12. For the Star Ratings updates, the net impact is estimated to be between $5.02 billion in 2028 and $1.89 billion in 2036, resulting in a 10-year net impact estimate of $18.56 billion, which equates to 0.21 percent of the Medicare payments to private health plans for the years 2027 through 2036.</P>
                    <GPH SPAN="3" DEEP="249">
                        <GID>ER06AP26.049</GID>
                    </GPH>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters requested that CMS update the modeling using data from the 2026 Part C and D Star Ratings, with a commenter noting that this would take into account the three new measures added to the 2026 Star Ratings. These commenters also requested that CMS clarify the measures and weights used in the modeling.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The impact analysis included in the Contract Year 2027 proposed rule was based on modeling that used data from the 2025 Star Ratings but accounted for measure and measure weight changes that occurred in the 2026 Star Ratings. Based on this, CMS does not believe it is necessary to update the modeling using data from the 2026 Star Ratings. The modeling included the three measures added to the 2026 Star Ratings (Improving or Maintaining Physical Health, Improving or Maintaining Menth Health, and Kidney Health Evaluation for Patients with Diabetes) and the weight changes for the patient experience, complaints, and access measures from 4 to 2. In other words, the modeling used the measure set and measure weights from the 2026 Star Ratings. Measure changes for years beyond the 2026 Star Ratings were not included.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter estimated the impact of the proposed changes and came to substantially different estimates than CMS shared in the Contract Year 2027 proposed rule. This commenter estimated the net impact would be savings of billions of dollars to the Medicare Trust Fund rather than the cost estimated by CMS.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate this commenter's analysis of the impact of the proposed changes; however, this commenter would not have all necessary data available to estimate the impact of the proposed changes. For example, while contracts have data on their own performance on the reward factor and simulated HEI reward, the commenter would not have data on the HEI or the reward factor for the full set of contracts included in the Star Ratings as CMS has not made those data publicly available.
                    </P>
                    <P>After consideration of the public comments we received, we are finalizing all of the Star Ratings provisions except the proposal to remove the Diabetes Care—Eye Exam measure (Part C).</P>
                    <HD SOURCE="HD3">7. Effects of Continuity in Enrollment for Full-Benefit Dually Eligible Individuals in a D-SNP and Medicaid Fee-for-Service (§§ 422.107 and 422.514)</HD>
                    <P>
                        In the April 2024 final rule, we finalized a package of provisions at §§ 422.503(b)(8), 422.504(a)(20), and 422.514(h) that require that, beginning in contract year 2027, where an MA organization offers a D-SNP and the MA organization, its parent organization, or any entity that shares a parent organization with the MA organization also contracts with a State as a Medicaid MCO that enrolls full-benefit dual eligible individuals in the same service areas (even if there is only partial overlap of the service areas), the MA organization: (a) may only offer, or have a parent organization or share a parent organization with another MA organization that offers, one D-SNP for full-benefit dual eligible individuals, except as otherwise provided in § 422.514(h)(3); and (b) must limit new enrollment in the D-SNP to individuals enrolled in, or in the process of 
                        <PRTPAGE P="17575"/>
                        enrolling in, the Medicaid MCO. Per § 422.514(h)(2), beginning in contract year 2030, such D-SNPs must only enroll (or continue to enroll) individuals enrolled in (or in the process of enrolling in) the affiliated Medicaid MCO, except that such D-SNPs may continue to implement deemed continued eligibility requirements as described in § 422.52(d). We also codified at § 422.514(h)(3) two exceptions to the requirements at § 422.514(h)(1) and (2) for exceptions related to instances where (a) the State Medicaid agency contract (SMAC) with the MA organization differentiates enrollment into D-SNPs by age group or to align enrollment in the D-SNP with the eligibility or benefit design used in the State's Medicaid managed care program and (b) the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization offers both HMO D-SNPs and PPO D-SNPs.
                    </P>
                    <P>In the April 2024 final rule at 89 FR 30802 through 30805, we stated that our changes would yield an overall annual estimate of net Part C costs ranging from −$6 million in contract year 2027 to −$207 million in contract year 2034 with total net Part C costs of −$961 million from contract years 2027 through 2034. We estimated an overall annual estimate of net Part D costs would range from −$7 million in contract year 2027 to −$286 million in contract year 2034 with total net Part D costs of −$1,341 million from contract years 2027 through 2034. In the April 2024 final rule (89 FR 30803), we explained that the regulatory change would shift enrollment from less integrated D-SNPs to more integrated D-SNPs over time as more D-SNPs align with Medicaid MCOs. For more context regarding the estimation methodology, see the April 2024 final rule (89 FR 30802 through 30805).</P>
                    <P>In this final rule, we are finalizing a third exception at § 422.514(h)(3) to allow D-SNPs that serve full-benefit dually eligible individuals in a coordination-only D-SNP or HIDE SNP to continue enrollment of full-benefit dually eligible individuals in a D-SNP in the same service area where those individuals are enrolled in Medicaid FFS. These changes will address the challenges of MA organizations complying with the requirements at § 422.514(h) in States where there is no mandatory Medicaid managed care program and avoid the need for MA organizations in those States to cease enrolling full-benefit dually eligible individuals who are in Medicaid FFS starting in 2027 and to begin disenrolling those members in 2030 as currently required under § 422.514(h).</P>
                    <P>We expect that establishing a third exception at § 422.514(h)(3) will slightly reduce the savings estimates included in the April 2024 final rule since the number of D-SNPs and enrollees impacted by the existing requirement at § 422.514(h) will be reduced. We note that we are also finalizing a fourth exception at § 422.514(h)(3) to exempt U.S. Territories that have not adopted Medicare Savings Programs (as defined at § 435.4) from the requirements at § 422.514(h)(1)(i), but we do not expect this exception to have an impact on savings estimates in the April 2024 final rule. The methodologies and baseline data used in the estimates presented in Table 10 are consistent with those used in the April 2024 final rule estimates, except the Tables 10 and 11 estimates exclude certain coordination-only D-SNPs and HIDE SNPs that would be exempt under this final rule.</P>
                    <P>For our third exception at § 422.514(h)(3), as shown in Table 13, we estimate the Part C costs to the Medicare Trust Funds range from $0 million in 2027 to $3 million in 2036, summing to $18 million for the years 2027 through 2036. These estimated costs mean our overall expected Part C savings from implementation of § 422.514(h) would be $943 million (rather than $961 million) over 10 years.</P>
                    <GPH SPAN="3" DEEP="97">
                        <GID>ER06AP26.050</GID>
                    </GPH>
                    <P>Table 14 shows the estimated Part D costs of the amendment to § 422.514(h) range from $0 million in 2027 to $4 million in 2036, summing to $24 million for the years 2027 through 2036. These estimated costs mean our overall expected Part D savings from implementation of § 422.514(h) would be $1,317 million (rather than $1,341 million) over 10 years.</P>
                    <GPH SPAN="3" DEEP="195">
                        <PRTPAGE P="17576"/>
                        <GID>ER06AP26.051</GID>
                    </GPH>
                    <P>We did not receive comments on the regulatory impact analysis associated with this proposal and, therefore, are finalizing the regulatory impact analysis without modification. We respond to public comments received on other aspects of our proposal in section IV.C. of this final rule. We are finalizing the amendments to §§ 422.107(d)(1) and 422.514(h) largely as proposed, with some modifications, which are described in detail in section IV.C. of this final rule.</P>
                    <HD SOURCE="HD3">8. Effects of Rescinding the Mid-Year Supplemental Benefits Notice</HD>
                    <P>This provision rescinds the requirement established in the April 2024 final rule (89 FR 30448) that required MA organizations to provide annual mid-year notices to enrollees regarding unused supplemental benefits. The requirement was to take effect on January 1, 2026, and required MA organizations to mail a notice between June 30 and July 31 of each plan year to enrollees listing any supplemental benefits they had not utilized during the first 6 months of the plan year. Note that on September 8, 2025, CMS announced its decision to delay enforcement of the requirements under §§ 422.111(l) and 422.2267(e)(42) until further notice. MA organizations were not expected to complete the Mid-Year Supplemental Benefits Notice requirements for the 2026 plan year.</P>
                    <HD SOURCE="HD3">a. Information Collection Requirements  </HD>
                    <P>In anticipation of this rescission, CMS removed the associated information collection requirements from PRA package CMS R-267 prior to its submission to OMB for review. Therefore, there are no current information collection requirements associated with this provision that require OMB review or approval for rescission.</P>
                    <P>The rescission of this requirement will prevent the burden that would have been imposed on MA organizations. Based on updated BLS wage data, this will prevent approximately $498,522 in one-time costs for system updates and policy changes, and approximately $1,355,520 annually in printing and mailing costs.</P>
                    <HD SOURCE="HD3">b. Updated One-time Cost Prevention</HD>
                    <P>The rescission of this requirement will prevent approximately $499,091 in one-time costs for system updates and policy changes across 774 prepaid contracts. This includes $430,344 (774 prepaid contracts * 4 hours * $139.00/hour) for software system updates performed by software developers, and $68,747 (774 prepaid contracts * 1 hour * $88.82/hour) for policy and procedure updates performed by business operations specialists.</P>
                    <HD SOURCE="HD3">c. Annual Cost Prevention</HD>
                    <P>The rescission of this requirement will prevent approximately $1,355,520 per year in printing and mailing costs across 774 prepaid contracts serving 32 million enrollees. This includes $451,840 (32,000,000 notices × $0.01412/page) for single-page mailings, with an estimated average of 3 pages per enrollee resulting in total annual cost prevention of $1,355,520 (32,000,000 notices × 3 pages × $0.01412/page).</P>
                    <P>Over a 10-year period from 2027 to 2036, we estimated this provision will save approximately $14.1 million (approximately $1.4 million per year), primarily from the elimination of printing and mailing costs that would have been incurred annually, plus the one-time system and policy update costs prevented.</P>
                    <P>This rescission is consistent with E.O. 14192, “Unleashing Prosperity through Deregulation,” which instructs federal agencies to review regulations to alleviate unnecessary regulatory burdens. After reviewing stakeholder feedback and current data on supplemental benefit utilization, CMS determined that the Mid-Year Notice requirement imposes a significant administrative burden on MA organizations that outweighs the intended benefit. Additionally, recent evidence suggests that enrollees are utilizing supplemental benefits when they need them, with 70 percent of MA enrollees in a recent survey reporting they had used at least one supplemental benefit in the past year.</P>
                    <P>CMS received no comments regarding the impacts of this proposal and is finalizing this provision without modification.</P>
                    <HD SOURCE="HD3">9. Effects of Waiver of Part D Customer Call Center Hours for All Regions Served by LI NET</HD>
                    <P>This provision adds a new waiver to the list of Part D requirements waived for the LI NET program by exempting the customer call center hours of operation requirements in § 423.128(d)(1)(i)(A). Currently, Part D sponsors are required to maintain toll-free customer call centers open from 8:00 a.m. to 8:00 p.m. in all regions served by the Part D plan. This waiver allows the LI NET program to operate its customer call center Monday through Friday, except holidays, from 8:00 a.m. to 7:00 p.m. Eastern Time.</P>
                    <P>
                        We estimate that this waiver will result in cost savings of approximately $800,000 to $1,000,000 annually for the LI NET program. These savings result from reduced operational costs 
                        <PRTPAGE P="17577"/>
                        associated with maintaining extended customer call center hours.
                    </P>
                    <P>The reduced hours are appropriate for the LI NET program due to several factors: low call volume after 7:00 p.m. ET historically; automatic enrollment of 90 to 95 percent of LI NET beneficiaries by CMS, reducing the need for prospective enrollee assistance; the transitional nature of the LI NET program; LI NET's open formulary structure; availability of a 24-hour call center serving pharmacists and pharmacies to address the majority of inquiries.</P>
                    <P>This provision would not adversely impact the LI NET sponsor, individuals' access to prescription drug benefits, or the Medicare Trust Fund. The 24-hour pharmacy call center ensures continued access to necessary support, while the reduced customer call center hours align with actual usage patterns.</P>
                    <HD SOURCE="HD2">D. Alternatives Considered</HD>
                    <P>In this section, CMS includes discussions of alternatives considered. Several provisions of this final rule codify existing policy where we have evidence, as discussed in the appropriate preamble sections, that the codification of existing policy would not affect compliance. In such cases, the preamble typically discusses the effectiveness metrics of these provisions for public health.</P>
                    <HD SOURCE="HD3">1. Waiver of Part D Customer Call Center Hours for All Regions Served by LI NET (§ 423.2536)</HD>
                    <P>The first alternative we considered would maintain the current customer call center hours requirement. The LI NET program would comply with the existing customer call center hours requirement in § 423.128(d)(1)(i)(A), maintaining operations from 8:00 a.m. to 8:00 p.m. in all regions served by the Part D plan. This alternative would result in continued operational costs of approximately $800,000 to $1,000,000 annually compared to the proposed waiver. We reject this alternative because maintaining extended hours is not cost-effective given the historically low call volume after 7:00 p.m. ET. The automatic enrollment process for 90 to 95 percent of LI NET beneficiaries significantly reduces customer service needs, making the extended hours unnecessary. The continued availability of 24-hour pharmacy support ensures adequate access to assistance.</P>
                    <P>The second alternative we considered would eliminate the customer call center requirements for LI NET. The LI NET program would be completely exempt from maintaining any customer call center, relying solely on the 24-hour pharmacy call center. This alternative would result in maximum cost savings but could potentially impact beneficiary access to customer service. We reject this alternative because it could create access barriers for the 5 to 10 percent of LI NET beneficiaries who are not automatically enrolled and may need customer service assistance. Maintaining customer call center operations during standard business hours (8:00 a.m. to 7:00 p.m. ET) provides an appropriate balance between cost efficiency and beneficiary access to support services.</P>
                    <P>The finalized provision represents the optimal balance between operational efficiency and beneficiary protection, providing necessary customer service access while eliminating unnecessary costs associated with low-utilization hours.</P>
                    <P>We did not receive comments on this proposal and are finalizing this provision without modification.</P>
                    <HD SOURCE="HD2">E. Regulatory Review Costs</HD>
                    <P>
                        If regulations impose administrative costs on reviewers, such as the time needed to read and interpret this final rule, then we should estimate the cost associated with regulatory review. We received approximately 42,632 comments specific to the provisions in this final rule, and we estimate that a similar number will review this rule upon publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>
                        Using the BLS wage information for medical and health service managers (code 11-9111), we estimate that the cost of reviewing this final rule is $132.44 per hour, including fringe benefits, overhead, and other indirect costs (
                        <E T="03">http://www.bls.gov/oes/current/oes_nat.htm</E>
                        ). Assuming an average reading speed, we estimate that it will take approximately 10 hours for each person to review this final rule. For each entity that reviews the rule, the estimated cost is therefore $1,324.40 (10 hours × $132.44). Therefore, we estimate that the maximum total cost of reviewing the final rule is $56.4 million ($1,324.40 × 42,632 reviewers). However, we expect that many reviewers, for example pharmaceutical companies and PBMs, will not review the entire rule but review just the sections that are relevant to them. We expect that on average (with fluctuations) 10 percent of the proposed rule will be reviewed by an individual reviewer; we therefore estimate the total cost of reviewing to be $5.6 million.
                    </P>
                    <P>We noted that this analysis assumes one reader per contract. Some alternatives included assuming one reader per parent organization. Using parent organizations instead of contracts would reduce the number of reviewers. However, we believe it is likely that review will be performed by contract. The rationale for this is that a parent organization might have local reviewers assessing potential region-specific effects from the rule.</P>
                    <HD SOURCE="HD2">F. Accounting Statement and Table</HD>
                    <P>
                        The following table summarizes costs, savings, and transfers by provision. As required by OMB Circular A-4 (available at 
                        <E T="03">https://trumpwhitehouse.archives.gov/sites/whitehouse.gov/files/omb/circulars/A4/a-4.pdf,</E>
                         in Table 15, we have prepared an accounting statement showing the transfers and costs associated with the provisions of this rule over an 11-year period or for contract years 2026 through 2036.
                    </P>
                    <GPH SPAN="3" DEEP="111">
                        <GID>ER06AP26.052</GID>
                    </GPH>
                    <PRTPAGE P="17578"/>
                    <HD SOURCE="HD2">G. Impact on Small Businesses—Regulatory Flexibility Analysis (RFA)</HD>
                    <P>The RFA, as amended, requires agencies to analyze options for regulatory relief of small businesses if a rule has a significant impact on a substantial number of small entities. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions.</P>
                    <P>
                        We believe this final rule will have a direct economic impact on beneficiaries, health insurance plans, and third-party marketing organizations (TPMOs). Based on the size standards set by the Small Business Administration (SBA) effective March 17, 2023, (for details, see the Small Business Administration's website at 
                        <E T="03">https://www.sba.gov/document/support-table-size-standards</E>
                        ), Direct Health and Medical Insurance Carriers, classified using the NAICS code 524114, have a $47 million threshold for “small size.” Many Medicare Advantage organizations (about 30 to 40 percent) are not-for-profit,
                        <SU>152</SU>
                        <FTREF/>
                         which allows them to qualify as “small entities” so long as they are independently owned and operated and nondominant in their field. We believe all of the not-for-profit organizations qualify as small under the aforementioned criteria. Of the 1,071 businesses using this NAICS code, we believe 799 (or 74.6 percent) are small businesses. Third party marketing organizations, which CMS has usually determined to belong to the category of Insurance Agencies and Brokerages (NAICS code of 524210), have a small size threshold of $15 million. In total, 99.7 percent (424,395 out of 425,715) are considered small.
                        <SU>153</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             Medicare Advantage/Part D Contract and Enrollment Data, 
                            <E T="03">https://www.cms.gov/data-research/statistics-trends-and-reports/medicare-advantagepart-d-contract-and-enrollment-data.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             US Census Bureau, 2022 SUSB Annual Data Tables by Establishment Industry, 
                            <E T="03">https://www.census.gov/data/tables/2022/econ/susb/2022-susb-annual.html;</E>
                             and US Census Bureau, 2022 Nonemployer Statistics Datasets, 
                            <E T="03">https://www.census.gov/programs-surveys/nonemployer-statistics/data/datasets.html?text-list-d6a8ce0de1%3Atab=2022#text-list-d6a8ce0de1.</E>
                        </P>
                    </FTNT>
                    <P>
                        The RFA does not define the terms “significant economic impact” or “substantial number.” The SBA advises that this absence of statutory specificity allows what is “significant” or “substantial” to vary, depending on the problem that is to be addressed in the rulemaking, the rule's requirements, and the preliminary assessment of the rule's impact. Nevertheless, HHS typically considers a “significant economic impact” to be 3 to 5 percent or more of the affected entities' costs or revenues, and a “substantial number” to mean 5 percent or more of affected small entities within a given industry.
                        <SU>154</SU>
                        <FTREF/>
                         To explain our position, we will first note certain operational aspects of the Medicare program.
                    </P>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             U.S. Department of Health and Human Services, Guidance on Proper Consideration of Small Entities in Rulemaking, 
                            <E T="03">https://aspe.hhs.gov/sites/default/files/documents/dd6288d1b8db19ee8a1f37b3ce775003/guidance-proper-consideration-hhs-2003-rulemaking.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Each year, MA organizations submit a bid for each plan for furnishing Parts A and B benefits and the entire bid amount is paid to the plan by the government through the Medicare Trust Funds, if the plan's bid is below an administratively set benchmark. If the plan's bid exceeds that benchmark, the beneficiary pays the difference in the form of a basic premium (note that, historically, only 2 percent of plans bid above the benchmark, and they contain roughly 1 percent of all plan enrollees). Part D sponsors also submit a bid for each plan, and the payments made to stand-alone Part D plans (PDPs) are covered by the Supplementary Medical Insurance Medicare Trust Fund. PACE organizations are paid a capitation amount that is funded by both the Medicare Trust Funds (the Hospital Insurance and Supplementary Medical Insurance trust funds) as well as the State Medicaid programs they contract with.</P>
                    <P>MA plans can also offer enhanced benefits—that is, benefits not covered under Original Medicare. These enhanced benefits are paid for through enrollee premiums, rebates or a combination. Under the statutory payment formula, if the plan bid submitted by an MA organization for furnishing Part A and B benefits is lower than the administratively set benchmark, the government pays a portion of the difference to the plan in the form of a rebate. The rebate must be used to provide supplemental benefits (that is, benefits not covered under Original Medicare) and/or to lower beneficiary cost sharing, Part B or Part D premiums. Some examples of these supplemental benefits include vision, dental, and hearing, fitness and worldwide coverage of emergency and urgently needed services.</P>
                    <P>Part D sponsors submit bids and plans are paid through a combination of Medicare funds and beneficiary premiums. In addition, for enrolled low-income beneficiaries, Part D plans receive special government payments to cover most of premium and cost sharing amounts those beneficiaries would otherwise pay.</P>
                    <P>Thus, the cost of providing services by these insurers is funded by the government and, in some cases, by enrollee premiums. As a result, MA plans, Part D plans, Prescription Drug Plans, and PACE organizations are not expected to incur burden or losses since the private companies' costs are being supported by the government and enrolled beneficiaries. This lack of expected burden applies to both large and small health plans.</P>
                    <P>The preceding analysis shows that meeting the direct cost of the rule does not have a significant economic impact on a substantial number of small entities, as required by the RFA. Besides the direct costs discussed earlier, there are certain indirect consequences of these provisions which also create impact. We have already explained that 98 percent of MA plans (including MA-PD plans) bid below the benchmark. Thus, their estimated costs for the coming year are fully paid by the Federal Government, given that as previously noted, under the statutory payment formula, if a bid submitted by a MA plan for furnishing Part A and B benefits is lower than the administratively set benchmark, the government pays a portion of the difference to the plan in the form of a beneficiary rebate, which must be used to provide supplemental benefits or lower beneficiary cost sharing or both, Part B or Part D premiums. If the plan's bid exceeds the administratively set benchmark, the beneficiary pays the difference in the form of a basic premium. However, as also noted previously, the number of MA plans bidding above the benchmark to whom this burden applies does not meet the RFA criteria of a significant number of firms. If the provisions of the rule were to cause bids to increase and if the benchmark remains unchanged or increases by less than the bid does, the result could be a reduced rebate. Plans have different ways to address this in the short-term, such as reducing administrative costs, modifying benefit structures, or adjusting profit margins. These decisions may be driven by market forces. Part of the challenge in pinpointing the indirect effects is that there are many other factors combining with the effects of the rule, making it effectively impossible to determine whether a particular policy had a long-term effect on bids, administrative costs, margins, or supplemental benefits.</P>
                    <P>
                        As indicated in Table 7, the proposals described in this rule are expected to result in cost savings amounting to approximately $23.4 million in 2027 and $23.5 million in subsequent years. Most affected entities are expected to 
                        <PRTPAGE P="17579"/>
                        have cost savings as a result of this rule. For example, we anticipate that the 697 MA organizations will experience a net cost savings. The provisions on Removing Rules on Time and Manner of Beneficiary Outreach are expected to reduce costs for 697 MA organizations by over $45,000 in 2027, while the provision Rescinding the Annual Health Equity Analysis of Utilization Management Policies and Procedures is expected to lower costs for 697 MA organizations by $756,929 in 2027 and $785,367 annually in subsequent years. Likewise, the provision Rescinding the Mid-Year Supplemental Benefits Notice is estimated to result in $1,854,611 in cost savings for 774 MA organization contracts in 2026 and $1,355,520 annually thereafter, or $2,396 in year one and $1,751 per year after that. For those Medicare Advantage organizations to which all of these provisions apply, expected net cost savings will be $2,396 for 2026, $2,902 for 2027, and $2,878 per year starting in 2028.
                    </P>
                    <P>Many of the other entities affected by the provisions of this final rule are similarly expected to see cost savings, though others will see negligible cost increases. The following table outlines costs savings, the estimated number of entities affected, and aggregate costs and cost savings over the next 10 years:</P>
                    <GPH SPAN="3" DEEP="167">
                        <GID>ER06AP26.053</GID>
                    </GPH>
                    <P>We reiterate our belief that this final rule will not have a significant economic impact on a substantial number of small entities. In the case of TPMOs, though we do not know how many are operating in the Medicare space, this rule is expected to produce cost savings for them. The vast majority of MA organizations are likewise expected to see cost savings as a result of this rule. These cost savings are described in Table 7. Even among the D-SNPs that are expected to incur new net costs through the passive enrollment provision, D-SNPs must agree to receive enrollees through the passive enrollment process. Especially small D-SNPs that cannot incur the additional costs would opt not to participate in passive enrollment. Finally, we also reiterate that Medicare Advantage organizations, including D-SNPs, are expected to include the costs of compliance in their bids. For these reasons, we do not believe these costs result in a significant economic impact on the affected plans.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concerns about the assumptions used in the Regulatory Impact Analysis. The commenter noted that the new out-of-pocket maximum and sunsetting of the Medicare Coverage Gap Discount Program may disproportionately burden smaller plans with limited revenue to absorb increased drug costs. The commenter added that the proposed changes will impact plans differently based on size, type, and populations served, noting that certain Star Ratings changes may harm SNPs and small plans serving vulnerable populations in long-term care facilities. The commenter recommended that CMS conduct a granular analysis of how each change affects small and specialty plans, and to tailor regulations to avoid harming plans serving beneficiaries requiring institutional or institutional-equivalent care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's concerns regarding the potential impact of this rule on small MA organizations and SNPs. However, we consider aspects of the commenter's statement to concern statutory changes and are out of scope, and on the whole we believe that the rule will not have a significant economic impact on most small entities. We reiterate that the vast majority of affected entities, including small plans, are expected to experience net cost savings as a result of this rule. Our analysis of cost estimates and time burdens are specific to each respondent type (
                        <E T="03">i.e.,</E>
                         MA organization, D-SNP, Part D sponsor, group health plan, etc.) to ensure that estimated impacts reflect the burden experienced by each type of entity. Many provisions also do not have an impact on small entities as they do not produce costs or cost savings; therefore, we do not include those provisions in this analysis. In addition, MA organizations are expected to include compliance costs in their bids, ensuring small plans have necessary resources, and can address cost changes through adjusting administrative costs, modifying benefit structures, and adjusting profit margins. CMS remains committed to ensuring all Medicare enrollees, including those served by SNPs and small plans, have access to high-quality, affordable coverage, and we will continue to monitor the impact of these provisions.  
                    </P>
                    <P>We are certifying that this rule will not have a significant economic impact on a substantial number of small entities. The analysis in this rule provides descriptions of the statutory provisions, identifies the policies, and presents rationales for our decisions and, where relevant, alternatives that were considered. The analysis discussed in this section and throughout the preamble of this final rule constitutes our RFA analysis.</P>
                    <HD SOURCE="HD2">H. Unfunded Mandates Reform Act (UMRA)</HD>
                    <P>
                        Section 202 of UMRA also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. 
                        <PRTPAGE P="17580"/>
                        In 2026, that threshold is approximately $193 million. This final rule is not anticipated to have an unfunded effect on State, local, or Tribal governments, in the aggregate, or on the private sector of $193 million or more.
                    </P>
                    <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a rule that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has federalism implications. Since this final rule does not impose any substantial costs on State or local governments, preempt State law or have federalism implications, the requirements of Executive Order 13132 are not applicable.</P>
                    <HD SOURCE="HD2">I. Federalism</HD>
                    <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a rule that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has federalism implications. Since this final rule does not impose any substantial costs on State or local governments, preempt State law or have federalism implications, the requirements of Executive Order 13132 are not applicable.</P>
                    <HD SOURCE="HD2">J. Executive Order (E.O.) 14192, “Unleashing Prosperity Through Deregulation”</HD>
                    <P>E.O. 14192, titled “Unleashing Prosperity Through Deregulation” was issued on January 31, 2025, and requires that “any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations.” This final rule is expected to be an E.O. 14192 deregulatory action. We estimate that this rule generates $19.2 million in annualized cost savings at a 7 percent discount rate, discounted relative to year 2024, over a perpetual time horizon.</P>
                    <HD SOURCE="HD2">K. Conclusion</HD>
                    <P>This final rule will result in net annualized cost savings ranging between $21.2 and $20.7 million for calendar years 2026 to 2036, at the 3 percent and 7 percent discount rates, respectively. These savings are primarily attributable to the provision revising aspects of TPMO oversight. This final rule will also result in net annualized monetized transfers ranging between $1.63 billion and $1.54 billion for calendar years 2026 to 2036, at the 3 percent and 7 percent discount rates respectively. These transfers primarily result from changing aspects of the MA and Part D Plan Quality Ratings System.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>42 CFR Part 422</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health maintenance organizations (HMO), Medicare, Penalties, Privacy, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 423</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health maintenance organizations (HMO), Medicare, Penalties, Privacy, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <P>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services amends 42 CFR chapter IV as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 422—MEDICARE ADVANTAGE PROGRAM</HD>
                    </PART>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>1. The authority for part 422 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P> 42 U.S.C. 1302, 1306, 1395w-21 through 1395w-28, and 1395hh.</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>2. Section 422.60 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising paragraphs (g)(2)(i) and (ii); and</AMDPAR>
                        <AMDPAR>b. In paragraph (g)(2)(vi), removing the phrase “capacity to passively” and adding in its place the phrase “capacity, including care coordinator staffing capacity, to passively”.</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.60 </SECTNO>
                            <SUBJECT>Election process.</SUBJECT>
                            <STARS/>
                            <P>(g) * * *</P>
                            <P>(2) * * *</P>
                            <P>(i) Operate as an applicable integrated plan as defined at § 422.561.</P>
                            <P>(ii) Provide continuity of care for all incoming enrollees that complies with § 422.112(b)(8)(i)(B), with the exception that the minimum transition period is 120 days.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>3. Section 422.62 is amended by revising paragraphs (b)(3) introductory text, (b)(5) introductory text, (b)(20) introductory text, and (b)(27) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.62 </SECTNO>
                            <SUBJECT>Election of coverage under an MA plan.</SUBJECT>
                            <P>(b) * * *</P>
                            <P>(3) This SEP requires CMS approval prior to use. The individual must use a CMS-operated election mechanism, in a form and manner specified by CMS, to make an election using this SEP. To be eligible, the individual must demonstrate to CMS that—</P>
                            <STARS/>
                            <P>(5) The individual is enrolled in an MA plan offered by an MA organization that has been sanctioned by CMS and elects to disenroll from that plan in connection with the matter(s) that gave rise to that sanction. This SEP requires CMS approval prior to use. The individual must receive a notice, as described in paragraph (b)(5)(i) of this section, to make an election using this SEP.</P>
                            <STARS/>
                            <P>(20) The individual was not adequately informed of a loss of creditable prescription drug coverage, or that they never had creditable coverage. CMS determines eligibility for this SEP on a case-by-case basis, based on its determination that an entity offering prescription drug coverage failed to provide accurate and timely disclosure of the loss of creditable prescription drug coverage or whether the prescription drug coverage offered is creditable. This SEP requires CMS approval prior to use. The individual must use a CMS-operated election mechanism, in a form and manner specified by CMS, to make an election using this SEP.</P>
                            <STARS/>
                            <P>(27) The individual meets such other exceptional conditions as CMS may provide. This SEP requires CMS approval prior to use. The individual must use a CMS-operated mechanism, in a form and manner specified by CMS, to make an election using this SEP.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>4. Section 422.66 is amended by adding paragraph (g) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.66 </SECTNO>
                            <SUBJECT>Coordination of enrollment and disenrollment through MA organizations.</SUBJECT>
                            <STARS/>
                            <P>
                                (g) 
                                <E T="03">Elections requiring prior CMS approval—</E>
                                (1) 
                                <E T="03">CMS approval.</E>
                                 SEPs specified in paragraph (g)(2) of this section require CMS approval before an individual can use the SEP to make an election.
                            </P>
                            <P>(i) CMS approval is provided for MA plan elections either through the use of a CMS-operated election mechanism or through the individual's receipt of a notice which explains eligibility for the SEP and election instructions.  </P>
                            <P>(ii) MA plans may not transmit elections to CMS using the specified SEPs without prior CMS approval.</P>
                            <PRTPAGE P="17581"/>
                            <P>
                                (2) 
                                <E T="03">Special election periods.</E>
                                 All of the following SEPs require CMS approval prior to use:
                            </P>
                            <P>(i) SEP for contract violation, § 422.62(b)(3).</P>
                            <P>(ii) SEP for individuals who disenroll in connection with CMS sanction, § 422.62(b)(5).</P>
                            <P>(iii) SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage, § 422.62(b)(20).</P>
                            <P>(iv) SEP for other exceptional circumstances, § 422.62(b)(27).</P>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.101 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>5. Section 422.101 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (f)(3)(iv)(B) removing the phrase “June 1st and November 30th of each calendar year” and adding in its place the phrase “January 1st and March 31st or October 1st and December 31st of each contract year”; and</AMDPAR>
                        <AMDPAR>b. In paragraph (f)(3)(iv)(G) removing the phrase “opportunity to submit a corrected off-cycle revision between June 1st and November 30th of each year.” and adding in its place the phrase “opportunity per contract year to submit a corrected off-cycle revision between January 1st and March 31st or October 1st and December 31st of each contract year”.</AMDPAR>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.102 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>6. Section 422.102 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising paragraph (f)(1)(i)(A);</AMDPAR>
                        <AMDPAR>b. Adding paragraph (f)(1)(i)(C);</AMDPAR>
                        <AMDPAR>c. Revising paragraphs (f)(1)(iii)(G) and (f)(4)(iii); and</AMDPAR>
                        <AMDPAR>d. Adding paragraph (g).</AMDPAR>
                        <P>The revisions and additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.102 </SECTNO>
                            <SUBJECT>Supplemental benefits.</SUBJECT>
                            <STARS/>
                            <P>(f) * * *</P>
                            <P>(1) * * *</P>
                            <P>(i) * * *</P>
                            <P>(A) A chronically ill enrollee is an individual enrolled in the MA plan who meets all of the following:</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Has one or more comorbid and medically complex chronic conditions that is life threatening or significantly limits the overall health or function of the enrollee.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Has a high risk of hospitalization or other adverse health outcomes.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Requires intensive care coordination.
                            </P>
                            <STARS/>
                            <P>(C) An enrollee who has one or more comorbidities and medically complex chronic conditions alone is not sufficient to demonstrate that an enrollee meets all 3 criteria set forth in paragraph (f)(1)(i)(A) of this section. MA plans must, through health risk assessments, review of claims data, or other similar means, demonstrate that enrollees meet all 3 criteria set forth in paragraph (f)(1)(i)(A) of this section.</P>
                            <STARS/>
                            <P>(iii) * * *</P>
                            <P>(G) Cannabis products that are illegal under applicable State or Federal law.</P>
                            <STARS/>
                            <P>(4) * * *</P>
                            <P>(iii) Have objective criteria for SSBCI. Specifically:</P>
                            <P>(A) Have and apply written policies based on objective criteria for determining a chronically ill enrollee's eligibility to receive a particular SSBCI;</P>
                            <P>(B) Document the written policies specified in paragraph (f)(4)(iii)(A) of this section and the objective criteria on which the written policies are based; and</P>
                            <P>(C) For each SSBCI, list all the written policies and objective criteria on which the policies are based, as noted in paragraphs (f)(4)(i) and (f)(4)(iii)(A) of this section, on their public-facing website.</P>
                            <STARS/>
                            <P>
                                (g) 
                                <E T="03">Administration of supplemental benefits</E>
                                —(1) 
                                <E T="03">General rule.</E>
                                 MA organizations must have processes for delivering supplemental benefits to enrollees that ensure compliance with § 422.100(c)(2) and paragraphs (a) through (f) of this section and appropriate access to all covered items and services, in accordance with § 422.112(a).
                            </P>
                            <P>
                                (2) 
                                <E T="03">Provision of benefits through debit card.</E>
                                 MA organizations that administer reductions in cost sharing or provide coverage of 100 percent of the cost of a mandatory supplemental benefit through use of a debit card must do all of the following:
                            </P>
                            <P>(i) Provide debit cards that are electronically linked to plan covered items and services through a real-time identification mechanism to verify eligibility of plan covered benefits at the point of sale.</P>
                            <P>(ii) Provide instructions for debit card use and customer service support to enrollees.</P>
                            <P>(iii) Have an alternative process that allows for reimbursement of eligible expenses for plan covered benefits in circumstances where the debit card is unusable at the point of sale, including but not limited to debit card malfunction or when a beneficiary is entitled to obtain covered benefits out-of-network.</P>
                            <P>(iv) Ensure debit cards are limited to the specific plan year.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>7. Section 422.107 is amended by adding paragraph (d)(1)(i) and reserved paragraph (d)(1)(ii) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.107 </SECTNO>
                            <SUBJECT>Requirements for dual eligible special needs plans.</SUBJECT>
                            <STARS/>
                            <P>(d) * * *</P>
                            <P>(1) * * *</P>
                            <P>(i) In conjunction with § 422.514(h), where the State Medicaid agency does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals, and either the State Medicaid agency contract allows a dual eligible special needs plan established through this paragraph (d)(1) to enroll full-benefit dually eligible individuals or the plan is a highly integrated dual eligible special needs plan, the State Medicaid agency contract must stipulate that such full benefit dually eligible beneficiaries cannot be enrolled in a Medicaid managed care organization that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization.</P>
                            <P>(ii) [Reserved]</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>8. Section 422.111 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising paragraph (b)(6); and</AMDPAR>
                        <AMDPAR>b. Removing paragraph (l).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.111 </SECTNO>
                            <SUBJECT>Disclosure requirements.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>
                                (6) 
                                <E T="03">Supplemental benefits.</E>
                                 Any mandatory supplemental benefits (including reductions in cost sharing) or optional supplemental benefits, the premium for optional supplemental benefits, and the applicable conditions and limitations associated with receipt or use of supplemental benefits. This includes both of the following:
                            </P>
                            <P>(i) Disclosure of eligible over-the-counter items.</P>
                            <P>(ii) If providing supplemental benefits through a debit card, specifying which benefits may be accessed using the debit card.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>9. Section 422.112 is amended by revising paragraph (a)(8) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.112 </SECTNO>
                            <SUBJECT>Access to services.</SUBJECT>
                            <STARS/>
                            <P>(a) * * *</P>
                            <P>
                                (8) 
                                <E T="03">Cultural considerations.</E>
                                 Ensure that services are provided in a culturally competent manner to all enrollees, including those with limited English proficiency or reading skills, and diverse cultural and ethnic backgrounds.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <PRTPAGE P="17582"/>
                        <SECTNO>§ 422.137 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>10. Section 422.137 is amended by removing paragraphs (c)(5) and (d)(6) and (7).</AMDPAR>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.152 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>11. Section 422.152 is amended by removing paragraph (a)(5).</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>
                            12. Section 422.162 is amended by revising paragraphs (b)(3)(iv)(A)(
                            <E T="03">2</E>
                            ) and (b)(3)(iv)(B)(
                            <E T="03">2</E>
                            ) to read as follows:
                        </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.162 </SECTNO>
                            <SUBJECT>Medicare Advantage Quality Rating System.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(3) * * *</P>
                            <P>(iv) * * *</P>
                            <P>(A) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) For contract consolidations approved on or after January 1, 2022, if a measure score for a consumed or surviving contract is missing due to a data integrity issue as described in § 422.164(g)(1)(i) and (ii), CMS assigns a score of zero for the missing measure score in the calculation of the enrollment-weighted measure score. If a measure score for a consumed or surviving contract is missing due to not having enough data to meet the measure technical specification or the reliability is less than 0.6 for a CAHPS measure, CMS treats this measure score as missing in the calculation of the enrollment-weighted measure score.
                            </P>
                            <P>(B) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) For contract consolidations approved on or after January 1, 2022, for all measures except HEDIS, CAHPS, and HOS, if a measure score for a consumed or surviving contract is missing due to a data integrity issue as described in § 422.164(g)(1)(i) and (ii), CMS assigns a score of zero for the missing measure score in the calculation of the enrollment-weighted measure score. For all measures except HEDIS, CAHPS, HOS, and call center measures, if a measure score for a consumed or surviving contract is missing due to not having enough data to meet the measure technical specification, CMS treats this measure score as missing in the calculation of the enrollment-weighted measure score.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>13. Section 422.164 is amended by revising paragraph (e)(2) and adding paragraph (e)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.164 </SECTNO>
                            <SUBJECT>Adding, updating, and removing measures.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(2) CMS will announce the removal of a measure based upon its application of paragraph (e)(1) of this section through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act in advance of the measurement period or will propose and finalize the removal of the measure through rulemaking in advance of the measurement period.</P>
                            <P>(3) CMS will propose and finalize the removal of a measure for any reason not stated in paragraph (e)(1) of this section through rulemaking in advance of the measurement period.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>14. Section 422.166 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (f)(1) removing the phrase “Through the 2026 Star Ratings, this rating-specific” and adding in its place the phrase “This rating-specific”;</AMDPAR>
                        <AMDPAR>b. Removing paragraph (f)(3); and</AMDPAR>
                        <AMDPAR>c. Revising paragraph (h)(2).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.166 </SECTNO>
                            <SUBJECT>Calculation of Star Ratings.</SUBJECT>
                            <STARS/>
                            <P>(h) * * *</P>
                            <P>
                                (2) 
                                <E T="03">Plan preview of the Star Ratings.</E>
                                 CMS will have two plan preview periods before each Star Ratings release during which MA organizations can preview their preliminary Star Ratings data in HPMS prior to display on the Medicare Plan Finder. During the second plan preview, CMS will display de-identified contract-level sample data for one of each type of measure needed to replicate the cut point methodology, as determined by CMS.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.308 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>15. Section 422.308 is amended in paragraph (c)(1) by removing the word “gender” and adding in its place the word “sex”.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>16. Section 422.310 is amended by revising paragraph (f) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.310 </SECTNO>
                            <SUBJECT>Risk adjustment data.</SUBJECT>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Use and release of data.</E>
                                 Regarding the data described in paragraphs (a) through (d) of this section, CMS may use and release the minimum data it determines is necessary in accordance with CMS data sharing procedures and applicable Federal laws, subject to the aggregation of dollar amounts reported for the associated encounter to protect commercially sensitive data, unless authorized by other applicable laws.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>17. Section 422.510 is amended by adding paragraphs (a)(4)(xvii), (b)(2)(i)(D), and (c)(2)(iv) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.510 </SECTNO>
                            <SUBJECT>Termination of contract by CMS.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(4) * * *</P>
                            <P>(xvii) Is no longer eligible to offer a dual eligible special needs plan because the MA organization does not hold a contract consistent with § 422.107(b) with the State Medicaid agency.  </P>
                            <P>(b) * * *</P>
                            <P>(2) * * *</P>
                            <P>(i) * * *</P>
                            <P>(D) The contract is being terminated based on paragraph (a)(4)(xvii) of this section.</P>
                            <P>(c) * * *</P>
                            <P>(2) * * *</P>
                            <P>(iv) The contract is being terminated based on paragraph (a)(4)(xvii) of this section.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>18. Section 422.514 is amended by adding paragraphs (h)(3)(iii) and (iv) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.514</SECTNO>
                            <SUBJECT>Enrollment requirements.</SUBJECT>
                            <STARS/>
                            <P>(h) * * *</P>
                            <P>(3) * * *</P>
                            <P>(iii) If an MA organization subject to paragraph (h)(1) of this section holds a State Medicaid agency contract with a State that does not mandate enrollment in Medicaid managed care for all full-benefit dually eligible individuals and the State Medicaid agency contract allows, the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization may offer one or more additional D-SNPs for full-benefit dually eligible individuals who are enrolled in Medicaid fee-for-service. These D-SNPs may not enroll full-benefit dually eligible individuals who are enrolled in a Medicaid managed care organization that is owned and controlled by an entity other than the MA organization, its parent organization, or an entity that shares a parent organization with the MA organization.</P>
                            <P>(iv) If a U.S. Territory has not adopted Medicare Savings Programs, as defined in 42 CFR 435.4, an MA organization operating in such U.S. Territory is exempt from the requirements in paragraph (h)(1)(i) of this section.</P>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.752</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>19. Section 422.752 is amended by removing and reserving paragraph (d).</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>20. Section 422.2261 is amended by adding paragraph (a)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 422.2261</SECTNO>
                            <SUBJECT>Submission, review, and distribution of materials.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>
                                (3)(i) MA organizations offering dual eligible special needs plans with exclusively aligned enrollment subject 
                                <PRTPAGE P="17583"/>
                                to § 422.107(e) must submit all materials for the contract in HPMS under the MA organization's contract number.
                            </P>
                            <P>(ii) MA organizations may not submit materials for the contract under the organization's Multi-Contract Entity number and third-party marketing organizations may not submit materials under the Multi-Plan number as described in § 422.2262(d)(2)(i).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 422.2262</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>21. Section 422.2262 is amended by removing paragraphs (a)(1)(i) and (ii) and redesignating paragraphs (a)(1)(iii) through (xix) as paragraphs (a)(1)(i) through (xvii), respectively.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>22. Section 422.2264 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (c)(1)(ii)(D), removing the phrase “Cards, but not including Scope” and adding in its place “Cards and Scope”; and</AMDPAR>
                        <AMDPAR>b. Revising paragraphs (c)(2)(i), (c)(3) introductory text, and (c)(3)(i).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.2264</SECTNO>
                            <SUBJECT>Beneficiary contact.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(2) * * *</P>
                            <P>(i) If a marketing event directly follows an educational event, the beneficiary must be notified that the educational event is ending and a marketing event will begin shortly and be given a sufficient opportunity to leave the educational event prior to the start of the marketing event.</P>
                            <STARS/>
                            <P>(3) Personal marketing appointments are those appointments that are tailored to an individual or small group (for example, a married couple) for purposes of discussing marketing topics. Personal marketing appointments are not defined by the location.</P>
                            <P>(i) Prior to the personal marketing appointment, the MA plan (or agent or broker, as applicable) must agree upon and record the Scope of Appointment with the beneficiary(ies). The Scope of Appointment must be in writing for in-person personal marketing appointments.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>23. Section 422.2267 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising paragraphs (e)(5)(ii)(B)(1);</AMDPAR>
                        <AMDPAR>c. Removing and reserving paragraph (e)(31);</AMDPAR>
                        <AMDPAR>d. Revising paragraph (e)(41) introductory text and paragraph (e)(41)(ii); and</AMDPAR>
                        <AMDPAR>e. Removing paragraph (e)(42).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.2267</SECTNO>
                            <SUBJECT>Required materials and content.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(5) * * *</P>
                            <P>(ii) * * *</P>
                            <P>(B) * * *</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Deductible; the initial coverage phase; coverage gap for a year preceding 2025; and catastrophic coverage.
                            </P>
                            <STARS/>
                            <P>
                                (41) 
                                <E T="03">Third-party marketing organization disclaimer.</E>
                                 This is standardized content. If a TPMO does not sell for all MA organizations in the service area the disclaimer consists of the statement: “We do not offer every plan available in your area. Currently we represent [insert number of organizations] organizations which offer [insert number of plans] products in your area. Please contact 
                                <E T="03">Medicare.gov</E>
                                 or 1-800-MEDICARE to get information on all of your options.” If the TPMO sells for all MA organizations in the service area the disclaimer consists of the statement: “Currently we represent [insert number of organizations] organizations which offer [insert number of plans] products in your area. You can always contact 
                                <E T="03">Medicare.gov</E>
                                 or 1-800-MEDICARE for help with plan choices.” The MA organization must ensure that the disclaimer is as follows:
                            </P>
                            <STARS/>
                            <P>(ii) Verbally conveyed during sales calls prior to the discussion of any benefits.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="422">
                        <AMDPAR>24. Section 422.2274 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (b)(3), removing the phrase “prior to meeting with potential enrollees” and adding in its place “prior to a personal marketing appointment”; and</AMDPAR>
                        <AMDPAR>b. Revising paragraphs (c)(9) and (g)(2)(ii).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 422.2274</SECTNO>
                            <SUBJECT>Agent, broker, and other third-party requirements.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(9) Establish and maintain a system for confirming all of the following:</P>
                            <P>(i) Beneficiaries enrolled by agents or brokers understand the product, including the rules applicable under the plan.  </P>
                            <P>(ii) Agents and brokers appropriately complete Scope of Appointment records for all personal marketing appointments (including telephonic and walk-in).</P>
                            <STARS/>
                            <P>(g) * * *</P>
                            <P>(2) * * *</P>
                            <P>(ii) All marketing and sales calls, including the audio portion of calls conducted via web-based technology, must be recorded and retained in their entirety for a minimum period of 6 years. For the first 3 years of the retention period, records must be maintained in audio format. For years 4, 5, and 6, records may be maintained in either audio format or as complete and accurate transcript recordings.</P>
                        </SECTION>
                    </REGTEXT>
                    <PART>
                        <HD SOURCE="HED">PART 423—VOLUNTARY MEDICARE PRESCRIPTION DRUG BENEFIT</HD>
                    </PART>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>25. The authority for part 423 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>42 U.S.C. 1302, 1306, 1395w-101 through 1395w-152, and 1395hh.</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>26. Section 423.1 is amended by adding “1860D-14C. Manufacturer Discount Program.” in numerical order in paragraph (a)(1) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.1</SECTNO>
                            <SUBJECT>Basis and scope.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(1) * * *</P>
                            <P>1860D-14C. Manufacturer Discount Program.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>27. Section 423.4 is amended by adding the definitions of “Geographic area”, “Outlier prescriber of opioids”, “Persistent outlier prescriber of opioids”, and “Specialty” in alphabetical order to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.4</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Geographic area</E>
                                 means the state in which a prescriber is practicing.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Outlier prescriber of opioids</E>
                                 means a prescriber who is a statistical outlier compared to their peers in a specialty and geographic area.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Persistent outlier prescriber of opioids</E>
                                 means an outlier prescriber identified by CMS in three consecutive outlier prescriber notifications.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Specialty</E>
                                 means the National Plan Provider Enumeration System (NPPES) taxonomy of a prescriber.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>28. Section 423.32 is amended by adding paragraph (k) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.32</SECTNO>
                            <SUBJECT>Enrollment process.</SUBJECT>
                            <STARS/>
                            <P>
                                (k) 
                                <E T="03">Enrollments requiring prior CMS approval</E>
                                —(1) 
                                <E T="03">CMS approval.</E>
                                 Special Election Periods specified in paragraph (k)(2) of this section require CMS approval before an individual can use the SEP to make an enrollment election. CMS approval is provided for Part D enrollments either through the use of a CMS-operated election mechanism or through the individual's receipt of a notice which explains eligibility for the SEP and election instructions. Part D 
                                <PRTPAGE P="17584"/>
                                plans may not transmit enrollment elections to CMS using the specified SEPs without prior CMS approval.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Special election periods.</E>
                                 All of the following SEPs require CMS approval prior to use:
                            </P>
                            <P>(i) SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage, § 423.38(c)(2).</P>
                            <P>(ii) SEP for contract violation, § 423.38(c)(8).</P>
                            <P>(iii) SEP for individuals who disenroll in connection with CMS sanction, § 423.38(c)(12).</P>
                            <P>(iv) SEP for other exceptional circumstances, § 423.38(c)(36).</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>29. Section 423.36 is amended by adding paragraph (g) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.36</SECTNO>
                            <SUBJECT>Disenrollment process.</SUBJECT>
                            <STARS/>
                            <P>
                                (g) 
                                <E T="03">Disenrollments requiring prior CMS approval</E>
                                —(1) 
                                <E T="03">CMS approval.</E>
                                 Special Election Periods specified in paragraph (g)(2) of this section require CMS approval before an individual can use the SEP to make a disenrollment election. CMS approval is provided for Part D disenrollments either through the use of a CMS-operated election mechanism or through the individual's receipt of a notice which explains eligibility for the SEP and election instructions. Part D plans may not transmit disenrollment elections to CMS using the specified SEPs without prior CMS approval.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Special election periods.</E>
                                 All of the following SEPs require CMS approval prior to use:
                            </P>
                            <P>(i) SEP for individuals who were not adequately informed of a loss of creditable prescription drug coverage, § 423.38(c)(2).</P>
                            <P>(ii) SEP for contract violation, § 423.38(c)(8).</P>
                            <P>(iii) SEP for individuals who disenroll in connection with CMS sanction, § 423.38(c)(12).</P>
                            <P>(iv) SEP for other exceptional circumstances, § 423.38(c)(36).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>30. Section 423.38 is amended by revising paragraphs (c)(2), (c)(8) introductory text, (c)(12) introductory text, and (c)(36) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.38</SECTNO>
                            <SUBJECT>Enrollment periods.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(2) The individual was not adequately informed, as required by standards established by CMS under § 423.56, that he or she has lost his or her creditable prescription drug coverage, that he or she never had credible prescription drug coverage, or the coverage is involuntarily reduced so that it is no longer creditable prescription drug coverage. This SEP requires CMS approval prior to use. The individual must use a CMS-operated election mechanism, in a form and manner specified by CMS, to make an election using this SEP.</P>
                            <STARS/>
                            <P>(8) This SEP requires CMS approval prior to use. The individual must use a CMS-operated election mechanism, in a form and manner specified by CMS, to make an election using this SEP. The individual must demonstrate to CMS, in accordance with guidelines issued by CMS, that the PDP sponsor offering the PDP substantially violated a material provision of its contract under this part in relation to the individual, including, but not limited to any of the following:</P>
                            <STARS/>
                            <P>(12) The individual is enrolled in a Part D plan offered by a Part D plan sponsor that has been sanctioned by CMS and elects to disenroll from that plan in connection with the matter(s) that gave rise to that sanction. This SEP requires CMS approval prior to use. The individual must receive a notice, as described in paragraph (c)(12)(i) of this section, to make an election using this SEP.</P>
                            <STARS/>
                            <P>(36) The individual meets other exceptional circumstances as CMS may provide. This SEP requires CMS approval prior to use. The individual must use a CMS-operated election mechanism, in a form and manner specified by CMS, to make an election using this SEP.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>31. Section 423.56 is amended by revising paragraphs (a) and (b)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.56</SECTNO>
                            <SUBJECT>Procedures to determine and document creditable status of prescription drug coverage.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Definition.</E>
                                 Creditable prescription drug coverage means any of the following types of coverage listed in paragraph (b) of this section only if the actuarial value of the coverage equals or exceeds the actuarial value of defined standard prescription drug coverage under Part D in effect at the start of such plan year, not taking into account the value of any discount provided under section 1860D-14C of the Act or of any selected drug subsidy under section 1860D-14D of the Act, and demonstrated through—
                            </P>
                            <P>(1) The use of generally accepted actuarial principles and in accordance with CMS guidelines; or  </P>
                            <P>(2) For group health plans not receiving a retiree drug subsidy, meeting the following requirements under the simplified creditable coverage determination methodology:</P>
                            <P>(i) Provision of reasonable coverage for brand name and generic prescription drugs and biological products.</P>
                            <P>(ii) Provision of reasonable access to retail pharmacies.</P>
                            <P>(iii) Is designed to pay on average a minimum percent of participants' prescription drug expenses, with the percent value at 73 percent for 2027 and percent values for subsequent years to be updated by CMS in subregulatory guidance in a time and manner determined by CMS to reflect the actuarial value of defined standard prescription drug coverage under Part D.</P>
                            <P>(b) * * *</P>
                            <P>(3) Coverage under a group health plan (other than an account-based medical plan as defined at § 423.882 (paragraph (4) of the definition of Group health plans)) including the Federal employees health benefits program, and qualified retiree prescription drug plans as defined in section 1860D-22(a)(2) of the Act.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>32. Section 423.100 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising and republishing the definition of “Applicable beneficiary”;</AMDPAR>
                        <AMDPAR>b. Adding the definition of “Applicable discount” in alphabetical order;</AMDPAR>
                        <AMDPAR>c. Revising and republishing the definition of “Applicable drug”;</AMDPAR>
                        <AMDPAR>d. Adding the definition of “Applicable number of calendar days” in alphabetical order;</AMDPAR>
                        <AMDPAR>e. Revising and republishing the definition of “Coverage gap”;</AMDPAR>
                        <AMDPAR>f. Adding the definition of “Date of dispensing” in alphabetical order;</AMDPAR>
                        <AMDPAR>g. Revising and republishing the definition of “Incurred costs”;</AMDPAR>
                        <AMDPAR>f. Adding definitions for “Labeler code”, “Manufacturer”, “Manufacturer Discount Program”, “Manufacturer Discount Program agreement”, “Medicare Coverage Gap Discount Program”, “Medicare Coverage Gap Discount Program agreement”, “National Drug Code (NDC)”, “Non-applicable drug”, “Price applicability period”, “Selected drug”, and “Third Party Administrator (TPA)” in alphabetical order.</AMDPAR>
                        <P>The additions and revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.100</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Applicable beneficiary</E>
                                 means an individual who, on the date of dispensing a covered Part D drug—
                                <PRTPAGE P="17585"/>
                            </P>
                            <P>(1) Is enrolled in a prescription drug plan or an MA-PD plan;</P>
                            <P>(2) Is not enrolled in a qualified retiree prescription drug plan;</P>
                            <P>(3)(i) For the purposes of the Coverage Gap Discount Program—</P>
                            <P>(A) Is not entitled to an income-related subsidy under section 1860D-14(a) of the Act;</P>
                            <P>(B) Has reached or exceeded the initial coverage limit under section 1860D-2(b)(3) of the Act during the year;</P>
                            <P>(C) Has not incurred costs for covered Part D drugs in the year equal to the annual out-of-pocket threshold specified in section 1860D-2(b)(4)(B) of the Act; and</P>
                            <P>(D) Has a claim that—</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Is within the coverage gap;
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Straddles the initial coverage period and the coverage gap;
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Straddles the coverage gap and the annual out-of-pocket threshold; or
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) Spans the coverage gap from the initial coverage period and exceeds the annual out-of-pocket threshold; and
                            </P>
                            <P>(ii) For the purposes of the Manufacturer Discount Program, has incurred costs, as determined in accordance with section 1860D-2(b)(4)(C) of the Act, for covered Part D drugs in the year that exceed the annual deductible specified in section 1860D-2(b)(1) of the Act.</P>
                            <P>
                                <E T="03">Applicable discount,</E>
                                 for purposes of the—
                            </P>
                            <P>(1) Coverage Gap Discount Program, has the meaning set forth at § 423.2305; and</P>
                            <P>(2) Manufacturer Discount Program, has the meaning set forth at § 423.2712.</P>
                            <P>
                                <E T="03">Applicable drug</E>
                                 means a Part D drug that is—
                            </P>
                            <P>(1)(i) Approved under a new drug application under section 505(c) of the Federal Food, Drug, and Cosmetic Act (FDCA); or</P>
                            <P>(ii) In the case of a biological product, licensed under section 351 of the Public Health Service Act (other than, with respect to a plan year before 2019, a product licensed under subsection (k) of such section 351).</P>
                            <P>(2)(i) If the PDP sponsor of the prescription drug plan or the MA organization offering the MA-PD plan uses a formulary, which is on the formulary of the prescription drug plan or MA-PD plan that the applicable beneficiary is enrolled in;</P>
                            <P>(ii) If the PDP sponsor of the prescription drug plan or the MA organization offering the MA-PD plan does not use a formulary, for which benefits are available under the prescription drug plan or MA-PD plan that the applicable beneficiary is enrolled in;</P>
                            <P>(iii) Is provided to a particular applicable beneficiary through an exception or appeal for that particular applicable beneficiary; or</P>
                            <P>(iv) For the purposes of the Manufacturer Discount Program, is provided to a particular applicable beneficiary as a transition fill under § 423.120(b)(3) or as an emergency supply as may be required for an applicable beneficiary who is a long-term care resident.</P>
                            <P>(3) Not a compounded drug product (as described in § 423.120(d)) that contains an applicable drug; and</P>
                            <P>(4) For the purposes of the Manufacturer Discount Program, not a selected drug during a price applicability period with respect to such drug.</P>
                            <P>
                                <E T="03">Applicable number of calendar days</E>
                                 means, with respect to claims for reimbursement submitted electronically, 14 days, and otherwise, 30 days.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Coverage gap</E>
                                 means the period in prescription drug coverage that occurs between the initial coverage limit and the out-of-pocket threshold during the years 2006 through 2024. For purposes of applying the initial coverage limit, Part D sponsors must apply their plan specific initial coverage limit under basic alternative, enhanced alternative or actuarially equivalent Part D benefit designs.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Date of dispensing</E>
                                 means the date of service. For long-term care and home infusion pharmacies, the date of dispensing can be interpreted as the date the pharmacy submits the discounted claim for reimbursement.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Incurred costs</E>
                                 means costs incurred by a Part D enrollee—
                            </P>
                            <P>(1) For—</P>
                            <P>(i) Covered Part D drugs that are not paid for under the Part D plan as a result of application of any annual deductible or other cost-sharing rules for covered Part D drugs prior to the Part D enrollee satisfying the out-of-pocket threshold under § 423.104(d)(5)(iii), including any price differential for which the Part D enrollee is responsible under § 423.124(b); or</P>
                            <P>(ii) Nominal cost-sharing paid by or on behalf of an enrollee, which is associated with drugs that would otherwise be covered Part D drugs, as defined in § 423.100, but are instead paid for, with the exception of said nominal cost-sharing, by a patient assistance program providing assistance outside the Part D benefit, provided that documentation of such nominal cost-sharing has been submitted to the Part D plan consistent with the plan processes and instructions for the submission of such information; and</P>
                            <P>(2) That are paid for—</P>
                            <P>(i) By the Part D enrollee or on behalf of the Part D enrollee by another person, and the Part D enrollee (or person paying on behalf of the Part D enrollee) is not reimbursed through insurance or otherwise, a group health plan, or other third party payment arrangement, or the person paying on behalf of the Part D enrollee is not paying under insurance or otherwise, a group health plan, or third party payment arrangement;</P>
                            <P>(ii) Under State Pharmaceutical Assistance Program (as defined in § 423.464); by the Indian Health Service, an Indian tribe or tribal organization, or urban Indian organization (as defined in section 4 of the Indian Health Care Improvement Act) or under an AIDS Drug Assistance Program (as defined in part B of title XXVI of the Public Health Service); or by a manufacturer as payment for an applicable discount (as defined in § 423.2305) under the Medicare Coverage Gap Discount Program (as defined in § 423.2305); or</P>
                            <P>(iii) Under § 423.782.</P>
                            <P>(3) For 2025 and subsequent years, that are reimbursed through insurance, a group health plan, or certain other third party payment arrangements, but not including the coverage provided by a prescription drug plan or an MA-PD plan that is basic prescription drug coverage or any payments by a manufacturer under the Manufacturer Discount Program under subpart AA of this part.</P>
                            <STARS/>
                            <P>
                                <E T="03">Labeler code</E>
                                 means the first segment of the National Drug Code (NDC) that identifies a particular manufacturer.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Manufacturer</E>
                                 means any entity which is engaged in the production, preparation, propagation, compounding, conversion or processing of prescription drug products, either directly or indirectly, by extraction from substances of natural origin, or independently by means of chemical synthesis, or by a combination of extraction and chemical synthesis. For purposes of the Coverage Gap Discount Program and the Manufacturer Discount Program, such term does not include a wholesale distributor of drugs or a retail pharmacy licensed under State law, but includes entities otherwise engaged in repackaging or changing the container, wrapper, or labeling of any applicable drug product in furtherance of the distribution of the applicable drug from the original place of manufacture to the 
                                <PRTPAGE P="17586"/>
                                person who makes the final delivery or sale to the ultimate consumer or user.
                            </P>
                            <P>
                                <E T="03">Manufacturer Discount Program</E>
                                 means the Medicare Part D Manufacturer Discount Program established under section 1860D-14C of the Act.
                            </P>
                            <P>
                                <E T="03">Manufacturer Discount Program agreement</E>
                                 means the agreement described at section 1860D-14C(b) of the Act.
                            </P>
                            <P>
                                <E T="03">Medicare Coverage Gap Discount Program (or Coverage Gap Discount Program)</E>
                                 means the Medicare Coverage Gap Discount Program established under section 1860D-14A of the Act.
                            </P>
                            <P>
                                <E T="03">Medicare Coverage Gap Discount Program agreement (or Coverage Gap Discount Program agreement)</E>
                                 means the agreement described in section 1860D-14A(b) of the Act.
                            </P>
                            <P>
                                <E T="03">National Drug Code (NDC)</E>
                                 means the unique identifying prescription drug product number that is listed with the Food and Drug Administration (FDA) identifying the product's manufacturer, product and package size and type.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Non-applicable drug</E>
                                 means any Part D drug that is not an applicable drug and not a selected drug during a price applicability period with respect to such drug.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Price applicability period</E>
                                 has the meaning given such term in section 1191(b)(2) of the Act and any applicable regulations and guidance.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Selected drug</E>
                                 has the meaning given such term in section 1192(c) of the Act and any applicable regulations and guidance.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Third Party Administrator</E>
                                 (TPA) means the CMS contractor responsible for administering the requirements established by CMS to carry out sections 1860D-14A and 1860D-14C of the Act.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>33. Section 423.104 is amended by—</AMDPAR>
                        <AMDPAR>
                            a. Revising paragraphs (d)(1) introductory text, (d)(2) heading, (d)(2)(i) introductory text, (d)(2)(iv)(A)(
                            <E T="03">4</E>
                            ), (d)(2)(iv)(B), and (d)(2)(iv)(D)(
                            <E T="03">3</E>
                            );
                        </AMDPAR>
                        <AMDPAR>b. Revising and republishing paragraph (d)(3);</AMDPAR>
                        <AMDPAR>c. Revising paragraphs (d)(4) introductory text, (d)(4)(iii)(C), and (d)(4)(iv)(E).</AMDPAR>
                        <AMDPAR>d. Removing paragraph (d)(4)(iv)(F);</AMDPAR>
                        <AMDPAR>e. Adding paragraph (d)(4)(v);</AMDPAR>
                        <AMDPAR>f. Revising paragraphs (d)(5)(i) introductory text, (d)(5)(i)(A)(2), and (d)(5)(iii)(F);</AMDPAR>
                        <AMDPAR>g. Adding paragraphs (d)(5)(iii)(G) and (H), and (d)(5)(iv);</AMDPAR>
                        <AMDPAR>
                            h. Revising paragraphs (e)(5) introductory text, (e)(5)(i), and (f)(1)(ii)(B)(
                            <E T="03">3</E>
                            ); and
                        </AMDPAR>
                        <AMDPAR>i. Adding paragraph (j).</AMDPAR>
                        <P>The revisions and additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.104 </SECTNO>
                            <SUBJECT>Requirements related to qualified prescription drug coverage.</SUBJECT>
                            <STARS/>
                            <P>(d) * * *</P>
                            <P>
                                (1) 
                                <E T="03">Deductible.</E>
                                 Subject to § 423.120(g) and (h), an annual deductible equal to—
                            </P>
                            <STARS/>
                            <P>
                                (2) 
                                <E T="03">Cost-sharing under prescription drug plans.</E>
                                 (i) Subject to paragraph (d)(4) of this section, coinsurance for actual costs for covered Part D drugs covered under the Part D plan above the annual deductible specified in paragraph (d)(1) of this section, and for each year preceding 2025, up to the initial coverage limit under paragraph (d)(3) of this section, and for 2025 and each subsequent year, up to the annual out-of-pocket threshold specified in paragraph (d)(5)(iii) of this section, that is—
                            </P>
                            <STARS/>
                            <P>(iv) * * *</P>
                            <P>(A) * * *</P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) 
                                <E T="03">Determination.</E>
                                 Except as provided in paragraph (d)(2)(iv)(B) of this section, the amount determined in paragraph (d)(2)(iv)(A)(
                                <E T="03">3</E>
                                ) of this section is the specialty-tier cost threshold for the plan year.
                            </P>
                            <STARS/>
                            <P>
                                (B) 
                                <E T="03">Limit on specialty-tier cost threshold adjustment.</E>
                                 (
                                <E T="03">1</E>
                                ) CMS modifies the specialty-tier cost threshold for a plan year only if the amount determined in paragraph (d)(2)(iv)(A)(
                                <E T="03">3</E>
                                ) of this section for a plan year is at least 10 percent above or below the specialty tier cost threshold for the prior plan year.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) If a modification is made in accordance with this paragraph (d)(2)(iv)(B), CMS rounds the amount determined in paragraph (d)(2)(iv)(A)(
                                <E T="03">3</E>
                                ) of this section to the nearest $10, and the resulting dollar amount is the specialty-tier cost threshold for the plan year.
                            </P>
                            <STARS/>
                            <P>(D) * * *</P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) For Part D plans with a deductible that is greater than $0 and less than the deductible provided under the Defined Standard benefit, the maximum coinsurance percentage is determined as follows:
                            </P>
                            <P>
                                (
                                <E T="03">i</E>
                                ) For years preceding 2025, subtracting the plan's deductible from 33 percent of the initial coverage limit (ICL) under section 1860D-2(b)(3) of the Act, dividing this difference by the difference between the ICL and the plan's deductible, and rounding to the nearest 1 percent.
                            </P>
                            <P>
                                (
                                <E T="03">ii</E>
                                ) For 2025 and each subsequent year, dividing the annual out-of-pocket (OOP) threshold, described in paragraph (d)(5)(iii) of this section, by total drug costs (represented by subtracting the plan deductible from the annual OOP threshold then dividing by the intended specialty-tier coinsurance percentage and adding the plan deductible) such that the result is 33 percent. Using the following equation solved for the deductible, each maximum allowable specialty-tier coinsurance percentage point can be inserted to determine the maximum allowable deductible corresponding to that coinsurance.
                            </P>
                            <HD SOURCE="HD3">
                                Equation 1 to Paragraph (d)(2)(iv)(D)(
                                <E T="03">3</E>
                                )(
                                <E T="03">ii</E>
                                )
                            </HD>
                            <GPH SPAN="3" DEEP="41">
                                <GID>ER06AP26.054</GID>
                            </GPH>
                            <P>
                                (3) 
                                <E T="03">Initial coverage limit.</E>
                                 The initial coverage limit is equal to one of the following:
                            </P>
                            <P>
                                (i) 
                                <E T="03">For 2006.</E>
                                 $2,250.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">For years 2007 through 2024.</E>
                                 The amount specified in this paragraph (d)(3) for the previous year, increased by the annual percentage increase specified in paragraph (d)(5)(iv) of this section, and rounded to the nearest multiple of $10.
                            </P>
                            <P>
                                (iii) 
                                <E T="03">For year 2025 and each subsequent year.</E>
                                 There is no initial coverage limit.
                            </P>
                            <P>
                                (4) 
                                <E T="03">Cost-sharing in the coverage gap for applicable beneficiaries.</E>
                                 For a year preceding 2025, cost-sharing in the coverage gap for applicable beneficiaries is as follows:  
                            </P>
                            <STARS/>
                            <P>
                                (iii) * * *
                                <PRTPAGE P="17587"/>
                            </P>
                            <P>(C) For 2020 through 2024, 25 percent.</P>
                            <P>(iv) * * *</P>
                            <P>(E) For 2019 through 2024, 75 percent.</P>
                            <P>(v) For 2025 and each subsequent year, there is no coverage gap.</P>
                            <P>(5) * * *</P>
                            <P>(i) After an enrollee's incurred costs exceed the annual out-of-pocket threshold described in paragraph (d)(5)(iii) of this section, for 2024 and each subsequent year, cost-sharing equal to $0, and for each year preceding 2024, cost-sharing equal to the greater of—</P>
                            <P>(A) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) For subsequent years through 2023, the copayment amounts specified in this paragraph (d)(5)(i)(A) for the previous year increased by the annual percentage increase described in paragraph (d)(5)(iv) of this section and rounded to the nearest multiple of 5 cents; or
                            </P>
                            <STARS/>
                            <P>(iii) * * *</P>
                            <P>
                                (F) 
                                <E T="03">For 2021 through 2024.</E>
                                 The amount specified in this paragraph (d)(5)(iii) for the previous year, increased by the annual percentage increase specified in paragraph (d)(5)(iv) of this section, and rounded to the nearest $50.
                            </P>
                            <P>
                                (G) 
                                <E T="03">For 2025.</E>
                                 $2,000.
                            </P>
                            <P>
                                (H) 
                                <E T="03">For 2026 and each subsequent year.</E>
                                 The amount specified in this paragraph (d)(5)(iii) for the previous year, increased by the annual percentage increase specified in paragraph (d)(5)(iv) of this section, and rounded to the nearest $50.
                            </P>
                            <STARS/>
                            <P>
                                (iv) 
                                <E T="03">Annual percentage increase in Part D drug expenditures</E>
                                —(A) 
                                <E T="03">General.</E>
                                 The annual percentage increase for each year is equal to the annual percentage increase in average per capita aggregate expenditures for Part D drugs in the United States for Part D eligible individuals and is based on data for the 12-month period ending in July of the previous year.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Calculating the annual percentage increase.</E>
                                 The annual percentage increase is the product of the annual percentage trend (as defined in paragraph (d)(5)(iv)(C) of this section) and a multiplicative update (as defined in paragraph (d)(5)(iv)(D) of this section).
                            </P>
                            <P>
                                (C) 
                                <E T="03">Annual percentage trend.</E>
                                 The annual percentage trend for a given year is the ratio of total Part D drug expenditures in the previous year (numerator) to the total Part D drug expenditures 2 years prior to the given year (denominator).
                            </P>
                            <P>
                                (D) 
                                <E T="03">Multiplicative update.</E>
                                 The multiplicative update for a given year is the ratio of the product of the annual percentage trends for all prior recorded years as revised and updated with the most recently available data (numerator) to the product of annual percentage trends in prior recorded years as published in the previous year's rate announcement (denominator).
                            </P>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(5) Provides coverage that is designed, based upon an actuarially representative pattern of utilization, to provide for the payment, for costs incurred for covered Part D drugs, that are equal to the initial coverage limit under paragraph (d)(3) of this section for a year preceding 2025, or the annual out-of-pocket threshold specified in paragraph (d)(5)(iii) for the year for 2025 and each subsequent year, of an amount equal to at least the product of the following:</P>
                            <P>(i) The amount by which the initial coverage limit described in paragraph (d)(3) of this section for the year, for a year preceding 2025, or the annual out-of-pocket threshold described in paragraph (d)(5)(iii) for the year for 2025 and each subsequent year, exceeds the deductible described in paragraph (d)(1) of this section.</P>
                            <STARS/>
                            <P>(f) * * *</P>
                            <P>(1) * * *</P>
                            <P>(ii) * * *</P>
                            <P>(B) * * *</P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) For a year preceding 2025, an increase in the initial coverage limit described in paragraph (d)(3) of this section.
                            </P>
                            <STARS/>
                            <P>
                                (j) 
                                <E T="03">Drugs not subject to the defined standard deductible.</E>
                                 (1) If a beneficiary has not satisfied their plan deductible but has accumulated sufficient incurred costs, as defined at § 423.100, to satisfy the deductible provided under the Defined Standard benefit, then they will be both an applicable beneficiary under the Manufacturer Discount Program, as defined at § 423.100, and be deemed to have satisfied their plan deductible.
                            </P>
                            <P>(2) If a plan offers a deductible other than the deductible provided under the Defined Standard benefit and a beneficiary accumulates sufficient incurred costs, as defined at § 423.100, to satisfy the plan deductible but has not accumulated incurred costs across all drugs at or above the deductible provided under the Defined Standard benefit, then applicable discounts, as defined at § 423.2712, under the Manufacturer Discount Program are not available for that beneficiary and the plan must cover the portion of the costs that would be covered by the applicable discount if the beneficiary were an applicable beneficiary until the beneficiary's incurred costs exceed the deductible provided under the Defined Standard benefit and they become an applicable beneficiary.</P>
                            <P>(3) If a plan offers a deductible other than the deductible provided under the Defined Standard benefit and a beneficiary accumulates sufficient incurred costs, as defined at § 423.100, to satisfy the plan deductible but has not accumulated incurred costs across all drugs at or above the deductible provided under the Defined Standard benefit, then the selected drug subsidy is not available for that beneficiary and the plan must cover the portion of the costs that would be covered by the selected drug subsidy, as described at § 423.329(e), if the beneficiary were an applicable beneficiary until the beneficiary's incurred costs exceed the deductible provided under the Defined Standard benefit and they become an applicable beneficiary.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>34. Section 423.128 is amended by revising paragraphs (e)(3)(ii) and (e)(7) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.128</SECTNO>
                            <SUBJECT>Dissemination of Part D plan information.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(3) * * *</P>
                            <P>(ii) For a year preceding 2025, the initial coverage limit for the current year.</P>
                            <STARS/>
                            <P>(7) Be provided no later than the end of the month following any month when prescription drug benefits are provided under this part, including, for a year preceding 2025, the covered Part D spending between the initial coverage limit described in § 423.104(d)(3) and the out-of-pocket threshold described in § 423.104(d)(5)(iii).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>
                            35. Section 423.182 is amended by revising paragraphs (b)(3)(ii)(A)(
                            <E T="03">2</E>
                            ) and (b)(3)(ii)(B)(
                            <E T="03">2</E>
                            ) to read as follows:
                        </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.182</SECTNO>
                            <SUBJECT>Part D Prescription Drug Plan Quality Rating System.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(3) * * *</P>
                            <P>(ii) * * *</P>
                            <P>(A) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) For contract consolidations approved on or after January 1, 2022, if a measure score for a consumed or surviving contract is missing due to a data integrity issue as described in § 423.184(g)(1)(i), CMS assigns a score of zero for the missing measure score in the calculation of the enrollment-weighted measure score. If a measure 
                                <PRTPAGE P="17588"/>
                                score for a consumed or surviving contract is missing due to not having enough data to meet the measure technical specification or the reliability is less than 0.6 for a CAHPS measure, CMS treats this measure score as missing in the calculation of the enrollment-weighted measure score.
                            </P>
                            <P>(B) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) For contract consolidations approved on or after January 1, 2022, for all measures except CAHPS, if a measure score for a consumed or surviving contract is missing due to a data integrity issue as described in § 423.184(g)(1)(i), CMS assigns a score of zero for the missing measure score in the calculation of the enrollment-weighted measure score. For all measures except CAHPS and call center measures, if a measure score for a consumed or surviving contract is missing due to not having enough data to meet the measure technical specification, CMS treats this measure score as missing in the calculation of the enrollment-weighted measure score.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>36. Section 423.184 is amended by revising paragraph (e)(2) and adding paragraph (e)(3) to read as follows:  </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.184</SECTNO>
                            <SUBJECT>Adding, updating, and removing measures.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(2) CMS will announce the removal of a measure based upon its application of paragraph (e)(1) of this section through the process described for changes in and adoption of payment and risk adjustment policies in section 1853(b) of the Act in advance of the measurement period or will propose and finalize the removal of the measure through rulemaking in advance of the measurement period.</P>
                            <P>(3) CMS will propose and finalize the removal of a measure for any reason not stated in paragraph (e)(1) of this section through rulemaking in advance of the measurement period.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.186</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>37. Section 423.186 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (f)(1), removing the phrase “Through the 2026 Star Ratings, this rating-specific” and adding in its place the phrase “This rating-specific”;</AMDPAR>
                        <AMDPAR>b. Removing paragraph (f)(3); and</AMDPAR>
                        <AMDPAR>c. Revising paragraph (h)(2).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.186</SECTNO>
                            <SUBJECT>Calculation of Star Ratings.</SUBJECT>
                            <STARS/>
                            <P>(h) * * *</P>
                            <P>
                                (2) 
                                <E T="03">Plan preview of the Star Ratings.</E>
                                 CMS will have two plan preview periods before each Star Ratings release during which Part D plan sponsors can preview their preliminary Star Ratings data in HPMS prior to display on the Medicare Plan Finder. During the second plan preview, CMS will display de-identified contract-level sample data for one of each type of measure needed to replicate the cut point methodology, as determined by CMS.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>38. Section 423.265 is amended by adding paragraph (d)(2)(vi) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.265</SECTNO>
                            <SUBJECT>Submission of bids and related information.</SUBJECT>
                            <STARS/>
                            <P>(d) * * *</P>
                            <P>(2) * * *</P>
                            <P>(vi) The assumptions regarding the selected drug subsidy under § 423.329(e) used in calculating the bid.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>39. Section 423.286 is amended by revising and republishing paragraph (b) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.286</SECTNO>
                            <SUBJECT>Rules regarding premiums.</SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Base beneficiary premium percentage.</E>
                                 (1) The beneficiary premium percentage for any year, except for years 2024 through 2029, is a fraction, the—
                            </P>
                            <P>(i) Numerator of which is 25.5 percent; and</P>
                            <P>(ii) Denominator of which is as follows:</P>
                            <P>(A) 100 percent minus the percentage established in paragraph (b)(1)(ii)(B) of this section.</P>
                            <P>(B) The percentage established in this paragraph (b) equals—</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) The total reinsurance payment that CMS estimates will be paid under § 423.329(c) for the coverage year divided by—
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) The amount estimated under paragraph (b)(2)(ii)(A) of this section for the year plus total payments that CMS estimates will be paid to Part D plans that are attributable to the standardized bid amount during the year, taking into account amounts paid by both CMS and enrollees.
                            </P>
                            <P>(2) The beneficiary premium percentage for the years 2024 through 2029 is the lesser of the beneficiary premium percentage—</P>
                            <P>(i) For the immediately preceding year increased by 6 percent; or</P>
                            <P>(ii) Calculated under the formula computed under paragraph (b)(1) of this section.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>40. Section 423.308 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising the definitions for “Allowable reinsurance costs” and “Gross covered prescription drug costs”; and</AMDPAR>
                        <AMDPAR>b. Adding the definition of “Inflation Reduction Act Subsidy Amount (IRASA)” in alphabetical order.</AMDPAR>
                        <P>The revisions and addition read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.308</SECTNO>
                            <SUBJECT>Definitions and terminology.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Allowable reinsurance costs</E>
                                 means the subset of gross covered prescription drug costs actually paid that are attributable to basic prescription drug coverage for covered Part D drugs only and that are actually paid by the Part D sponsor or by (or on behalf of) an enrollee under the Part D plan and the portion of the negotiated price (as defined in section 1860D-14C(g)(6) of the Act) of an applicable drug (as defined at § 423.100) paid by manufacturers under the Manufacturer Discount Program (as defined at § 423.100). The costs for any Part D plan offering enhanced alternative coverage must be adjusted not only to exclude any costs attributable to benefits beyond basic prescription drug coverage, but also to exclude any costs determined to be attributable to increased utilization over the standard prescription drug coverage as the result of the insurance effect of enhanced alternative coverage in accordance with CMS guidelines on actuarial valuation.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Gross covered prescription drug costs</E>
                                 means those costs incurred under a Part D plan, excluding administrative costs, but including dispensing fees, during the coverage year. They equal the sum of the following:
                            </P>
                            <P>(1) The share of actual costs (as defined at § 423.100) paid by the Part D plan that is received as reimbursement by the pharmacy, or other dispensing entity, reimbursement paid to indemnify an enrollee when the reimbursement is associated with an enrollee obtaining covered Part D drugs under the Part D plan, or payments made by the Part D sponsor to other parties listed in § 423.464(f)(1) with which the Part D sponsor must coordinate benefits, including other Part D plans, or as the result of any reconciliation process developed by CMS under § 423.464.</P>
                            <P>
                                (2) Nominal cost-sharing paid by or on behalf of an enrollee which is associated with drugs that would otherwise be covered Part D drugs, as defined at § 423.100, but are instead paid for, with the exception of said nominal cost-sharing, by a patient assistance program providing assistance outside the Part D benefit, provided that documentation of such nominal cost-
                                <PRTPAGE P="17589"/>
                                sharing has been submitted to the Part D plan consistent with the plan processes and instructions for the submission of such information.
                            </P>
                            <P>(3) All amounts paid under the Part D plan by or on behalf of an enrollee (such as the deductible, coinsurance, cost sharing, or, for years prior to 2025, amounts between the initial coverage limit and the out-of-pocket threshold) in order to obtain Part D drugs that are covered under the Part D plan. If an enrollee who is paying 100 percent cost sharing (as a result of paying a deductible or, for years prior to 2025, because the enrollee is between the initial coverage limit and the out-of-pocket threshold) obtains a covered Part D drug at a lower cost than is available under the Part D plan, such cost-sharing will be considered an amount paid under the plan by or on behalf of an enrollee under the previous sentence of this definition, if the enrollee's costs are incurred costs as defined at § 423.100 and documentation of the incurred costs has been submitted to the Part D plan consistent with plan processes and instructions for the submission of such information. These costs are determined regardless of whether the coverage under the plan exceeds basic prescription drug coverage.</P>
                            <P>(4) All amounts paid by manufacturers under the Manufacturer Discount Program (as defined at § 423.100).</P>
                            <STARS/>
                            <P>
                                <E T="03">Inflation Reduction Act Subsidy Amount (IRASA)</E>
                                 means a temporary retrospective subsidy paid to Part D plan sponsors for contract year 2023 for the statutory reduction in cost-sharing and deductible for covered insulin products or for ACIP-recommended adult vaccines, as defined in § 423.100, and is equal to the difference between the following:
                            </P>
                            <P>(1) The beneficiary cost-sharing for a covered insulin product or an ACIP-recommended adult vaccine under the plan's approved bids submitted under § 423.265 for contract year 2023; and</P>
                            <P>(2) The applicable statutory maximum cost-sharing for the covered insulin product or for the ACIP-recommended adult vaccine for contract year 2023.  </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>41. Section 423.315 is amended by adding paragraph (h) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.315</SECTNO>
                            <SUBJECT>General payment provisions.</SUBJECT>
                            <STARS/>
                            <P>
                                (h) 
                                <E T="03">Selected drug subsidy.</E>
                                 CMS provides selected drug subsidy payments described in § 423.329(e) on a monthly basis during a year based on either estimated or incurred allowable reinsurance costs as provided under § 423.329(e)(2)(i), and final reconciliation to actual allowable reinsurance costs as provided in § 423.343(e).
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>42. Section 423.325 is amended by revising paragraph (a)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.325</SECTNO>
                            <SUBJECT>PDE submission timeliness requirements.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(3) A PDE record for a paid claim transaction associated with a PDE record that was previously rejected by CMS at least once every 90 calendar days from receipt of a rejection until the PDE record is accepted unless the claim associated with the rejected PDE record is reversed or deleted, or the PDE record that was rejected is otherwise found to have been submitted in error.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>43. Section 423.329 is amended by revising paragraph (c)(1) and adding paragraph (e) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.329</SECTNO>
                            <SUBJECT>Determination of payments.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>
                                (1) 
                                <E T="03">General rule—</E>
                                (i) 
                                <E T="03">General rule for years preceding 2025.</E>
                                 The reinsurance payment amount for a Part D eligible individual enrolled in a Part D plan for a coverage year is an amount equal to 80 percent of the allowable reinsurance costs attributable to that portion of gross covered prescription drug costs incurred in the coverage year after the individual has incurred true-out-of-pocket costs that exceed the annual out-of-pocket threshold specified in § 423.104(d)(5)(iii).
                            </P>
                            <P>
                                (ii) 
                                <E T="03">General rule for 2026 and subsequent years.</E>
                                 The reinsurance payment amount for a Part D eligible individual enrolled in a Part D plan for a coverage year is an amount equal to 20 percent for applicable drugs or 40 percent for drugs that are not applicable drugs of the allowable reinsurance costs attributable to that portion of gross covered prescription drug costs incurred in the coverage year after the individual has incurred true-out-of-pocket costs that exceed the annual out-of-pocket threshold specified in § 423.104(d)(5)(iii).
                            </P>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Selected drug subsidy amount</E>
                                —(1) 
                                <E T="03">General rule.</E>
                                 The selected drug subsidy amount is equal to 10 percent of the negotiated price to a covered Part D drug that would otherwise meet the definition of an applicable drug but for being a selected drug during a price applicability period.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Payment method.</E>
                                 Payments under this section are based on a method that CMS determines.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Interim payments.</E>
                                 CMS establishes a payment method by which interim payments of amounts under this section are made during a year based on the selected drug subsidy amount assumptions submitted with plan bids under § 423.265(d)(2)(vi) and negotiated and approved under § 423.272 or by an alternative method that CMS determines.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Final payments.</E>
                                 CMS reconciles the interim payments to actual incurred selected drug subsidy amounts as provided in § 423.343(e).
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>44. Section 423.336 is amended by revising paragraph (c) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.336</SECTNO>
                            <SUBJECT>Risk-sharing arrangements.</SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Payment methods.</E>
                                 CMS makes payments after a coverage year after obtaining all of the cost data information in paragraph (c)(1) of this section necessary to determine the amount of payment. CMS does not make payments under this section if the Part D sponsor fails to provide the cost data information in paragraph (c)(1) of this section.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Submission of cost data.</E>
                                 Within 6 months of the end of a coverage year, the Part D sponsor must provide the information that CMS requires.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Lump sum and adjusted monthly payments.</E>
                                 CMS at its discretion makes either lump-sum payments or adjusts monthly payments in the following payment year based on the relationship of the plan's adjusted allowable risk corridor costs to the predetermined risk corridor thresholds in the coverage year, as determined under this section. In the event adequate data is not provided for risk corridor costs, CMS assumes that the Part D plan's adjusted allowable risk corridor costs are 50 percent of the target amount.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>45. Section 423.343 is amended by revising paragraph (d) and adding paragraph (e) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.343</SECTNO>
                            <SUBJECT>Retroactive adjustments and reconciliations.</SUBJECT>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Low-income cost-sharing subsidy.</E>
                                 CMS makes final payment for low-income cost-sharing subsidies after a coverage year after obtaining all of the information necessary to determine the amount of payment.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Submission of cost data.</E>
                                 Within 6 months of the end of a coverage year, the Part D sponsor must provide the information that CMS requires.
                                <PRTPAGE P="17590"/>
                            </P>
                            <P>
                                (2) 
                                <E T="03">Payments.</E>
                                 CMS at its discretion either makes lump-sum payments or adjusts monthly payments throughout the remainder of the payment year following the coverage year based on the difference between interim low-income cost-sharing subsidy payments and total low-income cost-sharing subsidy costs eligible for subsidy under § 423.782 submitted by the plan for the coverage year. CMS may recover payments made through a lump sum recovery or by adjusting monthly payments throughout the remainder of the coverage year if interim low-income cost-sharing subsidy payments exceed the amount payable under § 423.782 or if the Part D sponsor does not provide the data in paragraph (d)(1) of this section.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Selected drug subsidy.</E>
                                 CMS makes final payment for selected drug subsidies after a coverage year after obtaining all of the information necessary to determine the amount of payment.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Submission of cost data.</E>
                                 Within 6 months of the end of a coverage year, the Part D sponsor must provide the information that CMS requires.  
                            </P>
                            <P>
                                (2) 
                                <E T="03">Payments.</E>
                                 CMS at its discretion either makes lump-sum payments or adjusts monthly payments throughout the remainder of the payment year following the coverage year based on the difference between interim selected drug subsidy payments and total selected drug subsidy costs eligible for subsidy under § 423.329(e) submitted by the plan for the coverage year. CMS may recover payments made through a lump sum recovery or by adjusting monthly payments throughout the remainder of the coverage year if the interim selected drug subsidy payments exceed the amount payable under § 423.329(e) of if the Part D sponsor does not provide the data in paragraph (e)(1) of this section.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>46. Section 423.346 is amended by revising paragraph (a) introductory text to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.346</SECTNO>
                            <SUBJECT>Reopening.</SUBJECT>
                            <P>(a) CMS may conduct a global or targeted reopening to reopen and revise an initial or reconsidered final payment determination, including the following: a determination of the final amount of direct subsidy described at § 423.329(a)(1), final reinsurance payments described at § 423.329(c), final amount of the low income subsidy described at § 423.329(d), final risk corridor payments as described at § 423.336, reconciled Coverage Gap Discount Program payment described at § 423.2320(b), reconciled Inflation Reduction Act Subsidy Amount (IRASA) payment for contract year 2023 described at § 423.308, reconciled Manufacturer Discount Program payment described at § 423.2744(c), and reconciled selected drug subsidy payment described at § 423.343(e)—</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>47. Section 423.350 is amended by—</AMDPAR>
                        <AMDPAR>a. Adding paragraphs (a)(1)(vi) through (viii); and</AMDPAR>
                        <AMDPAR>b. Revising paragraphs (a)(2) and (b)(1).</AMDPAR>
                        <P>The additions and revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.350</SECTNO>
                            <SUBJECT>Payment appeals.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(1) * * *</P>
                            <P>(vi) The reconciled Inflation Reduction Act Subsidy Amount (IRASA) payment for contract year 2023 described at § 423.308.</P>
                            <P>(vii) The reconciled Manufacturer Discount Program payment under § 423.2744(c).</P>
                            <P>(viii) The reconciled selected drug subsidy payment under § 423.343(e).</P>
                            <P>(2) Payment information not subject to appeal. Payment information submitted to CMS under § 423.322 and reconciled or used in the payment calculations for the reconciled IRASA payment for contract year 2023 described at § 423.308 or under § 423.336, § 423.343, § 423.2320(b), or § 423.2744(c) is final and may not be appealed, nor may the appeals process be used to submit new information after the submission of information necessary for CMS to determine retroactive adjustments and reconciliations, including the calculation of risk corridor costs.</P>
                            <P>(b) * * *</P>
                            <P>
                                (1) 
                                <E T="03">Time for filing a request.</E>
                                 The request for reconsideration must be filed within 15 calendar days from the date CMS issues the payment reconciliation report for the payment determination that is being appealed under this section by the Part D plan sponsor.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>48. Section 423.464 is amended by revising paragraph (f)(2)(i)(C) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.464</SECTNO>
                            <SUBJECT>Coordination of benefits with other providers of prescription drug coverage.</SUBJECT>
                            <STARS/>
                            <P>(f) * * *</P>
                            <P>(2) * * *</P>
                            <P>(i) * * *</P>
                            <P>(C) Exclude expenditures for covered Part D drugs made by government-funded health programs or the coverage provided by a prescription drug plan or an MA-PD plan that is basic prescription drug coverage or any payments by a manufacturer under the Manufacturer Discount Program.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>49. Section 423.504 is amended by adding paragraph (f) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.504</SECTNO>
                            <SUBJECT>General provisions.</SUBJECT>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Outlier prescribers of opioids.</E>
                                 (1) CMS will identify and send notifications to outlier prescribers of opioids, which includes information about how the prescriber compares to other specified prescribers and resources on proper prescribing methods.
                            </P>
                            <P>(2) At least annually, CMS will communicate information about persistent outlier prescribers of opioids to all Part D plan sponsors.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>50. Section 423.505 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising paragraph (b)(24);</AMDPAR>
                        <AMDPAR>b. Adding paragraphs (d)(1)(vi) and (d)(2)(xiii); and</AMDPAR>
                        <AMDPAR>c. In paragraph (e)(2), removing the phrase “under the contract, or” and adding in its place the phrase “under the contract, which includes the records containing information identified in paragraph (d) of this section, or “.</AMDPAR>
                        <P>The revisions and additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.505</SECTNO>
                            <SUBJECT>Contract provisions.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(24) Provide applicable discounts on applicable drugs when dispensed to applicable beneficiaries in accordance with the requirements in subpart W of part for the Coverage Gap Discount Program and the requirements in subpart AA of part for the Manufacturer Discount Program.</P>
                            <STARS/>
                            <P>(d) * * *</P>
                            <P>(1) * * *</P>
                            <P>
                                (vi) Enable CMS to review original format documentation or information utilized from all written, electronic, and verbal communications between the plan sponsor and the pharmacist, prescriber, enrollee, or other relevant stakeholders, in addition to what is included on the pharmacy claim, that is relied upon by the Part D plan sponsor to make a coverage determination or otherwise permit a point-of-sale claim adjudication that determine a drug's coverage under the Part D benefit. In instances when a coverage determination is extended, the original coverage determination must be maintained as documentation. The documentation covered by these standards must be made available to CMS during Part D program integrity prescription drug event (PDE) record review audits. Failure to produce sufficient documentation to support Part D coverage will result in an improper Part D audit determination and will be 
                                <PRTPAGE P="17591"/>
                                subject to PDE record deletion in accordance with § 423.325(a)(2).
                            </P>
                            <P>(2) * * *</P>
                            <P>(xiii) Documentation or information from all written, electronic, and verbal communications between the plan sponsor and the pharmacist, prescriber, enrollee, or other relevant stakeholders, in addition to what is included on the pharmacy claim, that is relied upon when Part D plan sponsors make coverage determinations or otherwise permit a point-of-sale claim adjudication that determines coverage of a drug under the Part D benefit, consistent with paragraph (d)(1)(vi) of this section. This includes:</P>
                            <P>(A) Date and time the request for a coverage determination or point-of-sale claim adjudication was received and, when available, the identity of the individual or entity who submitted the request.</P>
                            <P>(B) Name and title, as applicable if additional outreach is made, of the individual the Part D plan contacted to obtain the information needed to complete the request (for example, pharmacist, prescriber, enrollee, or enrollee representative).</P>
                            <P>(C) Information obtained, including the questions asked and responses received, and the final decision rendered.</P>
                            <P>(D) Diagnosis for a coverage determination or point-of-sale claim adjudication when used to determine Part D coverage for a medically accepted indication.</P>
                            <P>(E) Any other information that the Part D plan sponsor utilized to determine the final outcome of the coverage determination or point-of-sale claim adjudication request.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>51. Section 423.782 is amended by—</AMDPAR>
                        <P>a. Revising paragraphs (a)(2) introductory text and (a)(2)(i)(B);</P>
                        <AMDPAR>b. In paragraph (a)(2)(iii)(A), removing the phrase “Index, rounded” and adding in its place the phrase “Index specified in paragraph (d) of this section, rounded”;</AMDPAR>
                        <AMDPAR>c. In paragraph (b)(1), removing the phrase “Part D drugs, rounded to” and adding in its place the phrase “Part D drugs, rounded as specified under § 423.104(d)(5)(iv) to”;</AMDPAR>
                        <AMDPAR>d. In paragraph (b)(3), removing the phrase “in this paragraph (b)(3) for the previous years increased by the annual percentage increase in average per capita aggregate expenditures for covered Part D drugs, rounded” and adding in its place the phrase “in § 423.104(d)(5)(i)(A)(2), rounded”; and</AMDPAR>
                        <AMDPAR>e. Adding paragraph (d).</AMDPAR>
                        <P>The revisions and addition reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.782 </SECTNO>
                            <SUBJECT>Cost-sharing subsidy.</SUBJECT>
                            <STARS/>
                            <P>(a) * * *</P>
                            <P>(2) Reduction in cost-sharing for all covered Part D drugs covered under the PDP or MA-PD plan below the out-of-pocket limit (under § 423.104), including for years preceding 2025, Part D drugs covered under the PDP or MA-PD plan obtained after the initial coverage limit (under § 423.104(d)(4)), as follows:</P>
                            <P>(i) * * *</P>
                            <P>(B) Those individuals who have income for years prior to 2024 under 135 percent, and for 2024 and subsequent years, under 150 percent of the Federal poverty line applicable to the individual's family size who meet the resources test described at § 423.773(b)(2).</P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Annual percentage increase in consumer price index (CPI)</E>
                                —(1) 
                                <E T="03">General.</E>
                                 The annual percentage increase in consumer price index (CPI) for each year is equal to the annual percentage increase in the CPI in the United States for all items per a U.S. city average and is based on data for the 12-month period ending in September of the previous year.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Calculating the annual percentage increase in CPI.</E>
                                 The annual percentage increase is the product of the annual percentage trend (as defined in subparagraph (d)(3) of this section) and a multiplicative update (as defined in subparagraph (d)(4) of this section).
                            </P>
                            <P>
                                (3) 
                                <E T="03">Annual percentage trend.</E>
                                 The annual percentage trend for a given year is the ratio of the CPI in the previous year (numerator) to the CPI 2 years prior to the given year (denominator).
                            </P>
                            <P>
                                (4) 
                                <E T="03">Multiplicative update.</E>
                                 The multiplicative update for a given year is the ratio of the product of the annual percentage trends for all prior recorded years, as revised and updated with the most recent available data (numerator) to the product of the annual percentage trends in prior recorded years as published in the previous year's rate announcement (denominator).
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>52. Section 423.882 is amended by revising the definition of “Allowable retiree costs” and “Gross covered retiree pan-related prescription drug costs and allowable retiree costs” to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.882 </SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Allowable retiree costs</E>
                                 means the subset of gross covered retiree plan-related prescription drug costs actually paid by the sponsor of the qualified retiree prescription drug plan or by (or on behalf of) a qualifying covered retiree under the plan and the portion of the negotiated price (as defined in section 1860D-14C(g)(6) of the Act) of an applicable drug (as defined by § 423.100) paid by manufacturers under the Manufacturer Discount Program (as defined by § 423.100).
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Gross covered retiree plan-related prescription drug costs, or gross retiree costs,</E>
                                 means those Part D drug costs incurred under a qualified retiree prescription drug plan, excluding administrative costs, but including dispensing fees, during the coverage year. They equal the sum of the following:
                            </P>
                            <P>(1) The share of prices paid by the qualified retiree prescription drug plan that is received as reimbursement by the pharmacy or by an intermediary contracting organization, and reimbursement paid to indemnify a qualifying covered retiree when the reimbursement is associated with a qualifying covered retiree obtaining Part D drugs under the qualified retiree prescription drug plan.</P>
                            <P>(2) All amounts paid under the qualified retiree prescription drug plan by or on behalf of a qualified covered retiree (such as the deductible, coinsurance, cost sharing, or, for years prior to 2025, amounts between the initial coverage limit and the out-of-pocket threshold) in order to obtain Part D drugs that are covered under the qualified retiree prescription drug plan.</P>
                            <P>(3) All amounts paid by manufacturers under the Manufacturer Discount Program (as defined at § 423.100).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.884 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>53. Section 423.884 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (c)(2)(v)(D) by removing the word “Gender” and adding in its place the word “Sex.”</AMDPAR>
                        <AMDPAR>b. In paragraphs (d) introductory text, (d)(1)(i) and (ii), and (d)(5)(iii)(C) by removing the phrase “not taking into account the value of any discount or coverage provided during the coverage gap” and replacing it with the phrase “for years prior to 2025, not taking into account the value of any discount or coverage provided during the coverage gap and for 2025 and subsequent years, not taking into account the value of any discount provided under the Manufacturer Discount Program.”</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>54. Section 423.1000 is amended by revising paragraph (a)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.1000 </SECTNO>
                            <SUBJECT>Basis and scope.</SUBJECT>
                            <P>
                                (a) * * *
                                <PRTPAGE P="17592"/>
                            </P>
                            <P>(3)(i) CMS must impose a civil money penalty on a manufacturer that fails to provide applicable discounts for applicable drugs of the manufacturer dispensed to applicable beneficiaries in accordance with the terms of such manufacturer's—</P>
                            <P>(A) Coverage Gap Discount Program agreement, in accordance with section 1860D-14A(e)(2) of the Act; and</P>
                            <P>(B) Manufacturer Discount Program agreement, in accordance with section 1860D-14C(e) of the Act.</P>
                            <P>(ii) The provisions of section 1128A (other than subsections (a) and (b)) of the Act apply to a civil money penalty under paragraph (a)(3)(i) of this section.</P>
                        </SECTION>
                        <AMDPAR>55. Section 423.1002 is amended by revising the definition of “Affected party” to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.1002 </SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Affected party</E>
                                 means any Part D sponsor or, for purposes of the Coverage Gap Discount Program, any manufacturer (as defined in § 423.100), or, for purposes of the Manufacturer Discount Program, any manufacturer that is an agreement holder (as defined in § 423.2704), impacted by an initial determination or, if applicable, by a subsequent determination or decision issued under this part, and “party” means the affected party or CMS, as appropriate.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>56. Section 423.2261 is amended by adding paragraph (a)(3) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.2261 </SECTNO>
                            <SUBJECT>Submission, review, and distribution of materials.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(3)(i) Part D sponsors offering dual eligible special needs plans with exclusively aligned enrollment subject to § 422.107(e) must submit all materials for the contract in HPMS under the Part D sponsor's contract number.</P>
                            <P>(ii) Part D sponsors may not submit materials for the contract under the organization's Multi-Contract Entity number and third-party marketing organizations may not submit materials under the Multi-Plan number as described in § 423.2262(d)(2)(i).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2262 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>57. Section 423.2262 is amended by removing paragraphs (a)(1)(i) and (ii) and redesignating paragraphs (a)(1)(iii) through (xviii) as paragraphs (a)(1)(i) through (xvi), respectively.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>58. Section 423.2264 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (c)(1)(ii)(D), removing the phrase “Cards, but not including Scope” and adding in its place “Cards and Scope”; and</AMDPAR>
                        <AMDPAR>b. Revising paragraphs (c)(2)(i), (c)(3) introductory text, and (c)(3)(i).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2264 </SECTNO>
                            <SUBJECT>Beneficiary contact.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(2) * * *</P>
                            <P>(i) If a marketing event directly follows an educational event, the beneficiary must be notified that the educational event is ending and a marketing event will begin shortly and be given a sufficient opportunity to leave the educational event prior to the start of the marketing event.</P>
                            <STARS/>
                            <P>(3) Personal marketing appointments are those appointments that are tailored to an individual or small group (for example, a married couple) for purposes of discussing marketing topics. Personal marketing appointments are not defined by the location.</P>
                            <P>(i) Prior to the personal marketing appointment, the Part D plan (or agent or broker, as applicable) must agree upon and record the Scope of Appointment with the beneficiary(ies). The Scope of Appointment must be in writing for in-person personal marketing appointments.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>59. Section 423.2267 is amended by—  </AMDPAR>
                        <AMDPAR>a. Revising paragraph (e)(5)(ii)(A)(2);</AMDPAR>
                        <AMDPAR>b. Removing and reserving paragraph (e)(33); and</AMDPAR>
                        <AMDPAR>c. Revising paragraphs (e)(41) introductory text and (e)(41)(ii).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2267 </SECTNO>
                            <SUBJECT>Required materials and content.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(5) * * *</P>
                            <P>(ii) * * *</P>
                            <P>(A) * * *</P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Deductible; the initial coverage phase; coverage gap for a year preceding 2025; and catastrophic coverage.
                            </P>
                            <STARS/>
                            <P>
                                (41) 
                                <E T="03">Third-party marketing organization disclaimer.</E>
                                 This is standardized content. If a TPMO does not sell for all Part D sponsors in the service area the disclaimer consists of the statement: “We do not offer every plan available in your area. Currently we represent [insert number of organizations] organizations which offer [insert number of plans] products in your area. Please contact 
                                <E T="03">Medicare.gov</E>
                                 or 1-800-MEDICARE to get information on all of your options.” If the TPMO sells for all Part D sponsors in the service area the disclaimer consists of the statement: “Currently we represent [insert number of organizations] organizations which offer [insert number of plans] products in your area. You can always contact 
                                <E T="03">Medicare.gov</E>
                                 or 1-800-MEDICARE for help with plan choices.” The Part D sponsor must ensure that the disclaimer is as follows:
                            </P>
                            <STARS/>
                            <P>(ii) Verbally conveyed during sales calls prior to the discussion of any benefits.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>60. Section 423.2274 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (b)(3), removing the phrase “prior to meeting with potential enrollees” and adding in its place “prior to a personal marketing appointment”; and</AMDPAR>
                        <AMDPAR>b. Revising paragraphs (c)(9) and (g)(2)(ii).</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2274 </SECTNO>
                            <SUBJECT>Agent, broker, and other third-party requirements.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(9) Establish and maintain a system for confirming all of the following:</P>
                            <P>(i) Beneficiaries enrolled by agents or brokers understand the product, including the rules applicable under the plan.</P>
                            <P>(ii) Agents and brokers appropriately complete Scope of Appointment records for all personal marketing appointments (including telephonic and walk-in).</P>
                            <STARS/>
                            <P>(g) * * *</P>
                            <P>(2) * * *</P>
                            <P>(ii) All marketing and sales calls, including the audio portion of calls conducted via web-based technology, must be recorded and retained in their entirety for a minimum period of 6 years. For the first 3 years of the retention period, records must be maintained in audio format. For years 4, 5, and 6, records may be maintained in either audio format or as complete and accurate transcript recordings.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>61. Revise and republish § 423.2300 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.2300 </SECTNO>
                            <SUBJECT>Scope.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Scope.</E>
                                 This subpart sets forth the requirements for the Medicare coverage gap discount program based on provisions included in sections 1860D-14A and 1860D-43 of the Act, as follows:
                            </P>
                            <P>(1) Condition for coverage of applicable drugs under Part D.</P>
                            <P>(2) The Medicare Coverage Gap Discount Program Agreement.</P>
                            <P>
                                (3) Coverage gap discount payment processes for Part D sponsors.
                                <PRTPAGE P="17593"/>
                            </P>
                            <P>(4) Provision of applicable discounts on applicable drugs for applicable beneficiaries.</P>
                            <P>(5) Manufacturer audit and dispute resolution processes.</P>
                            <P>(6) Resolution of beneficiary disputes involving coverage gap discounts.</P>
                            <P>(7) Compliance monitoring and civil money penalties.</P>
                            <P>(8) The termination of the Medicare Coverage Gap Discount Program Agreement.</P>
                            <P>
                                (b) 
                                <E T="03">Applicability.</E>
                                 The requirements of this subpart apply before January 1, 2025, and, with respect to applicable drugs dispensed prior to such date, continue to apply on and after January 1, 2025.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>62. Section 423.2305 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising and republishing the introductory text and the definition of “Applicable discount”;</AMDPAR>
                        <AMDPAR>c. Removing the definitions of “Applicable number of calendar days”; “Date of dispensing”; “Labeler code”; “Manufacturer”; “Medicare Coverage Gap Discount Program”; “Medicare Coverage Gap Discount Program Agreement”; and “National Drug Code”;</AMDPAR>
                        <AMDPAR>d. Revising and republishing the definition of “Negotiated price”; and</AMDPAR>
                        <AMDPAR>e. Removing the definition of “Third Party Administrator”.</AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2305 </SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <P>As used in this subpart and for purposes of the Coverage Gap Discount Program, unless otherwise specified—</P>
                            <P>
                                <E T="03">Applicable discount</E>
                                 means, with respect to a plan year before 2019, 50 percent or, with respect to plan year 2019 through plan year 2024, 70 percent of the portion of the negotiated price (as defined in this section) of the applicable drug of a manufacturer that falls within the coverage gap and that remains after such negotiated price is reduced by any supplemental benefits that are available.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Negotiated price</E>
                                 for purposes of the Coverage Gap Discount Program, means the price for a covered Part D drug that—
                            </P>
                            <P>(1) The Part D sponsor (or other intermediary contracting organization) and the network dispensing pharmacy or other network dispensing provider have negotiated as the lowest possible reimbursement such network entity will receive, in total, for a particular drug;</P>
                            <P>(i) Includes all price concessions (as defined in § 423.100) from network pharmacies or other network providers; and</P>
                            <P>(ii) Excludes additional contingent amounts, such as incentive fees, if these amounts increase prices;</P>
                            <P>(2) Is reduced by those discounts, direct or indirect subsidies, rebates, non-pharmacy price concessions, and direct or indirect remuneration that the Part D sponsor has elected to pass through to Part D enrollees at the point-of-sale; and</P>
                            <P>(3) Excludes any dispensing fee or vaccine administration fee for the applicable drug.</P>
                            <P>(4) In connection with applicable drugs dispensed by an out-of-network provider in accordance with the applicable beneficiary's Part D plan out-of-network policies, the negotiated price means the plan allowance as set forth in § 423.124, less any dispensing fee or vaccine administration fee.</P>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2310 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>63. Section 423.2310 is amended in paragraph (a)(1) by removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>64. Section 423.2315 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (a), removing the phrase “Program Agreement (or Discount Program Agreement)” and adding in its place the phrase “Program Agreement”;</AMDPAR>
                        <AMDPAR>b. In paragraphs (b)(5) and (11), removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”;</AMDPAR>
                        <AMDPAR>c. In paragraph (c)(1), removing the phrase “Discount Program Agreement” and adding in its place the phrase “Coverage Gap Discount Program Agreement” each time it appears;</AMDPAR>
                        <AMDPAR>d. Revising paragraph (c)(2); and  </AMDPAR>
                        <AMDPAR>e. In paragraph (c)(3), removing the phrase “Discount Program Agreement” and adding in its place the phrase “Coverage Gap Discount Program Agreement”.</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2315 </SECTNO>
                            <SUBJECT>Medicare Coverage Gap Discount Program Agreement.</SUBJECT>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(2) For 2012 and subsequent years prior to 2025, for a Coverage Gap Discount Program Agreement to be effective for a year, a manufacturer must enter into such Agreement not later than January 30th of the preceding year.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2320 </SECTNO>
                        <SUBJECT> [Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>65. Section 423.2320 is amended in paragraph (b) by removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”.</AMDPAR>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2330 </SECTNO>
                        <SUBJECT> [Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>66. Section 423.2330 is amended in paragraphs (a)(1) and (b)(3) by removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”.</AMDPAR>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2335 </SECTNO>
                        <SUBJECT> [Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>67. Section 423.2335 is amended by removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”.</AMDPAR>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 423.2340 </SECTNO>
                        <SUBJECT> [Amended]</SUBJECT>
                    </SECTION>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>68. Section 423.2340 is amended in paragraphs (a), (b), (c) introductory text, and (c)(1) by removing the phrase “Discount Program Agreement” and adding in its place the phrase “Coverage Gap Discount Program Agreement”.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>69. Section 423.2345 is amended by—</AMDPAR>
                        <AMDPAR>a. Revising the section heading;</AMDPAR>
                        <AMDPAR>b. In paragraph (a)(1)—</AMDPAR>
                        <AMDPAR>i. Removing the phrase “Discount Program Agreement” and adding in its place the phrase “Coverage Gap Discount Program Agreement”; and</AMDPAR>
                        <AMDPAR>ii. Removing the phrase “Discount Program” and adding in its place the phrase “Coverage Gap Discount Program”;</AMDPAR>
                        <AMDPAR>c. In paragraphs (a)(3)(i), (b)(1), (d), and (e), removing the phrase “Discount Program Agreement” and adding in its place the phrase “Coverage Gap Discount Program Agreement”; and</AMDPAR>
                        <AMDPAR>d. Adding paragraph (f).</AMDPAR>
                        <P>The addition reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2345 </SECTNO>
                            <SUBJECT>Termination of Coverage Gap Discount Program Agreement.</SUBJECT>
                            <STARS/>
                            <P>(f) Subject to § 423.2300(b), all Coverage Gap Discount Program Agreements under this subpart are terminated as of January 1, 2025.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>70. Section 423.2420 is amended by adding paragraphs (b)(4)(iii) through (v) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.2420 </SECTNO>
                            <SUBJECT>Calculation of medical loss ratio.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(4) * * *</P>
                            <P>(iii) Prospective Manufacturer Discount Program Payments.</P>
                            <P>(iv) Selected Drug Subsidy Program Payments.</P>
                            <P>(v) Inflation Reduction Act Subsidy Amounts.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>71. Section 423.2536 is amended by adding paragraph (m) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.2536 </SECTNO>
                            <SUBJECT>Waiver of Part D program requirements.</SUBJECT>
                            <STARS/>
                            <PRTPAGE P="17594"/>
                            <P>
                                (m) 
                                <E T="03">Provision of specific information.</E>
                                 Section 423.128(d)(1)(i)(A).
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>71. The heading for subpart Z is revised to read as follows:</AMDPAR>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart Z—Appeals Process for Part D Program Integrity Prescription Drug Event Record Review Audits</HD>
                            <STARS/>
                        </SUBPART>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>72. Section 423.2600 is revised to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 423.2600 </SECTNO>
                            <SUBJECT>Payment appeals.</SUBJECT>
                            <P>Medicare Part D plan sponsors may appeal program integrity prescription drug event record review audit determinations.</P>
                            <P>
                                (a) 
                                <E T="03">Issues eligible for appeal.</E>
                                 (1) CMS's application of Part D policy(ies).
                            </P>
                            <P>(2) Factual or data errors.</P>
                            <P>
                                (b) 
                                <E T="03">Issues ineligible for appeal.</E>
                                 (1) The Part D plan sponsor's failure to submit documentation in the timeframes specified by CMS during the audit.
                            </P>
                            <P>(2) The program integrity prescription drug event record review audit methodology.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>73. Section 423.2605 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (a), removing the phrase “demand letter” and adding in its place the phrase “close out letter”; and</AMDPAR>
                        <AMDPAR>b. Revising paragraph (e).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2605 </SECTNO>
                            <SUBJECT>Request for reconsideration.</SUBJECT>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Notification of decision.</E>
                                 The independent reviewer decides the reconsideration within 60 calendar days after the timeframe for filing a rebuttal has expired, and sends a written decision to the Part D plan sponsor and CMS, explaining the basis for the decision.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>74. Section 423.2610 is amended by—</AMDPAR>
                        <AMDPAR>a. In paragraph (d)(2)(i), removing the phrase “The Part D RAC” and adding in its place the phrase “The CMS”;</AMDPAR>
                        <AMDPAR>b. In paragraph (d)(3), removing the phrase “nor CMS may submit” and adding in its place the phrase “nor CMS is permitted to submit”;</AMDPAR>
                        <AMDPAR>c. In paragraph (e), removing the phrase “60 days” and adding in its place the phrase “60 calendar days after the timeframe for filing a rebuttal has expired”; and</AMDPAR>
                        <AMDPAR>d. Revising paragraph (f).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2610 </SECTNO>
                            <SUBJECT>Hearing official review.</SUBJECT>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Effect of hearing official decision.</E>
                                 The hearing official's decision is final and binding, unless the decision is reversed or modified by the CMS Administrator in accordance with § 423.2615.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>75. Section 423.2615 is amended by—  </AMDPAR>
                        <AMDPAR>a. In paragraph (b)(2), removing the phrase “nor CMS may submit” and adding in its place the phrase “nor CMS is permitted to submit”;</AMDPAR>
                        <AMDPAR>b. In paragraph (d), removing the phase “45 days” and adding in its place “30 calendar days”; and</AMDPAR>
                        <AMDPAR>c. Revising paragraph (e).</AMDPAR>
                        <P>The revision reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 423.2615 </SECTNO>
                            <SUBJECT>Review by the Administrator.</SUBJECT>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Administrator Review.</E>
                                 If the CMS Administrator agrees to review the hearing official's decision, he or she determines, after reviewing the hearing record, and any arguments submitted by the Part D plan sponsor or CMS in accordance with this section, whether the determination should be upheld, reversed, or modified. The CMS Administrator furnishes a written decision, which is final and binding, to the Part D plan sponsor and to CMS within 45 calendar days after the timeframe for filing a rebuttal has expired.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="423">
                        <AMDPAR>76. Add subpart AA to read as follows: </AMDPAR>
                        <CONTENTS>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart AA—Medicare Part D Manufacturer Discount Program</HD>
                                <SECHD>Sec.</SECHD>
                                <SECTNO>423.2700 </SECTNO>
                                <SUBJECT>Basis and scope.</SUBJECT>
                                <SECTNO>423.2704 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <SECTNO>423.2708 </SECTNO>
                                <SUBJECT>Conditions for coverage of drugs under Part D.</SUBJECT>
                                <SECTNO>423.2712 </SECTNO>
                                <SUBJECT>Applicable discounts.</SUBJECT>
                                <SECTNO>423.2716 </SECTNO>
                                <SUBJECT>Phase-in of applicable discount for certain manufacturers.</SUBJECT>
                                <SECTNO>423.2720 </SECTNO>
                                <SUBJECT>Determination of phase-in eligibility.</SUBJECT>
                                <SECTNO>423.2724 </SECTNO>
                                <SUBJECT>Effect of manufacturer acquisition on phase-in eligibility.</SUBJECT>
                                <SECTNO>423.2728 </SECTNO>
                                <SUBJECT>Recalculation of phase-in eligibility determination.</SUBJECT>
                                <SECTNO>423.2732 </SECTNO>
                                <SUBJECT>Use of third party administrator.</SUBJECT>
                                <SECTNO>423.2736 </SECTNO>
                                <SUBJECT>Requirement for point-of-sale discounts.</SUBJECT>
                                <SECTNO>423.2740 </SECTNO>
                                <SUBJECT>Negative invoice payment process for Part D sponsors.</SUBJECT>
                                <SECTNO>423.2744 </SECTNO>
                                <SUBJECT>Prospective payments to Part D sponsors.</SUBJECT>
                                <SECTNO>423.2748 </SECTNO>
                                <SUBJECT>Requirement to use the Health Plan Management System.</SUBJECT>
                                <SECTNO>423.2752 </SECTNO>
                                <SUBJECT>Manufacturer Discount Program agreement.</SUBJECT>
                                <SECTNO>423.2756 </SECTNO>
                                <SUBJECT>Manufacturer requirements.</SUBJECT>
                                <SECTNO>423.2760 </SECTNO>
                                <SUBJECT>Audits.</SUBJECT>
                                <SECTNO>423.2764 </SECTNO>
                                <SUBJECT>Dispute resolution.</SUBJECT>
                                <SECTNO>423.2768 </SECTNO>
                                <SUBJECT>Civil money penalties.</SUBJECT>
                            </SUBPART>
                        </CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart AA—Medicare Part D Manufacturer Discount Program</HD>
                            <SECTION>
                                <SECTNO>§ 423.2700 </SECTNO>
                                <SUBJECT>Basis and scope.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Basis.</E>
                                     This subpart implements section 1860D-14C of the Act and provisions included in section 1860D-43 of the Act.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Scope.</E>
                                     This subpart sets forth the requirements of the Medicare Part D Manufacturer Discount Program, which requires manufacturers to pay discounts for brand-name drugs and biological products when dispensed to Part D enrollees in the initial and catastrophic coverage phases of the Part D benefit, under the terms of an agreement with CMS, in order for such drugs to be coverable under Part D.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2704 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <P>As used in this subpart and for purposes of the Manufacturer Discount Program, unless otherwise specified—</P>
                                <P>
                                    <E T="03">Agreement holder</E>
                                     means a manufacturer that has executed and has in effect its own Manufacturer Discount Program agreement in accordance with § 423.2708(b)(1).
                                </P>
                                <P>
                                    <E T="03">Applicable discount</E>
                                     has the meaning set forth at § 423.2712.
                                </P>
                                <P>
                                    <E T="03">Applicable LIS percent</E>
                                     has the meaning set forth at § 423.2712(d)(1).
                                </P>
                                <P>
                                    <E T="03">Applicable small manufacturer percent</E>
                                     has the meaning set forth at § 423.2712(d)(2).
                                </P>
                                <P>
                                    <E T="03">Covered Part D drug</E>
                                     has the meaning set forth at § 423.100.
                                </P>
                                <P>
                                    <E T="03">Dispute submission deadline</E>
                                     means the date that is 60 calendar days from the date of the invoice containing the information that is the subject of the agreement holder's dispute.
                                </P>
                                <P>
                                    <E T="03">Negotiated price</E>
                                     has the meaning set forth at § 423.100, and with respect to an applicable drug under the Manufacturer Discount Program, such negotiated price includes any dispensing fee and, if applicable, any vaccine administration fee and sales tax.
                                </P>
                                <P>
                                    <E T="03">Network pharmacy</E>
                                     has the meaning set forth at § 423.100.
                                </P>
                                <P>
                                    <E T="03">Part D drug</E>
                                     has the meaning set forth at § 423.100.
                                </P>
                                <P>
                                    <E T="03">Primary manufacturer</E>
                                     has the meaning given such term pursuant to applicable regulations and guidance for the Medicare Drug Price Negotiation Program.
                                </P>
                                <P>
                                    <E T="03">Specified drug</E>
                                     means, with respect to a specified manufacturer, for 2021, an applicable drug that is produced, prepared, propagated, compounded, converted, or processed by the specified manufacturer.
                                </P>
                                <P>
                                    <E T="03">Specified small manufacturer drug</E>
                                     means, with respect to a specified small manufacturer, for 2021, an applicable drug that is produced, prepared, propagated, compounded, converted, or processed by the specified small manufacturer.
                                </P>
                                <P>
                                    <E T="03">Total expenditures</E>
                                     means with respect to—
                                    <PRTPAGE P="17595"/>
                                </P>
                                <P>(1) Part D, the total gross covered prescription drug costs, as defined in § 423.308; and</P>
                                <P>
                                    (2) Part B, the total Medicare allowed amount (
                                    <E T="03">i.e.,</E>
                                     total allowed charges), inclusive of beneficiary cost sharing, for Part B drugs and biologicals, except that expenditures for a drug or biological that are bundled or packaged into the payment for another service are excluded.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2708 </SECTNO>
                                <SUBJECT>Conditions for coverage of drugs under Part D.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General rule.</E>
                                     Except as specified in paragraph (c) of this section, in order for coverage to be available under Part D for a Part D drug of a manufacturer that is an applicable drug or a selected drug during a price applicability period—
                                </P>
                                <P>(1) The FDA-assigned labeler code of such applicable drug or selected drug must be covered by a Manufacturer Discount Program agreement (described at § 423.2752) that is in effect;</P>
                                <P>(2) The manufacturer must participate in the Manufacturer Discount Program in accordance with paragraph (b) of this section; and</P>
                                <P>(3) The manufacturer must have entered into and have in effect a Manufacturer Discount Program agreement in accordance with paragraph (b) of this section.</P>
                                <P>
                                    (b) 
                                    <E T="03">Participation in the Manufacturer Discount Program.</E>
                                     A manufacturer is considered to participate in the Manufacturer Discount Program and to have entered into and have in effect a Manufacturer Discount Program agreement for the purposes of paragraph (a) of this section if the manufacturer does either of the following:
                                </P>
                                <P>(1) Executes and has in effect its own Manufacturer Discount Program agreement.</P>
                                <P>(2) Participates in the Manufacturer Discount Program by means of an arrangement whereby its labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement that is in effect.</P>
                                <P>
                                    (c) 
                                    <E T="03">Exception.</E>
                                     Paragraph (a) of this section does not apply to an applicable drug that is not covered by a Manufacturer Discount Program agreement if CMS has made a determination that the availability of the drug is essential to the health of Part D enrollees. This exception to the general rule in paragraph (a) of this section does not apply to any applicable drug or selected drug of a manufacturer for any period described in section 5000D(c)(1) of the Internal Revenue Code of 1986 with respect to such manufacturer.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Non-applicable drugs.</E>
                                     Coverage under Part D is available for non-applicable drugs (as defined at § 423.100) of a manufacturer regardless of whether the manufacturer participates in the Manufacturer Discount Program or has a Manufacturer Discount Program agreement in effect.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2712 </SECTNO>
                                <SUBJECT>Applicable discounts.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Defined.</E>
                                     For purposes of the Manufacturer Discount Program, applicable discount means, subject to the requirements of this section, with respect to an applicable drug of a manufacturer dispensed during a year to an applicable beneficiary who has—
                                </P>
                                <P>(1) Not incurred costs, as defined at § 423.100, for covered Part D drugs (as defined at § 423.100) in the year that are equal to or exceed the annual out-of-pocket threshold specified at § 423.104(d)(5)(iii) for the year, 10 percent of the negotiated price of such drug; and</P>
                                <P>(2) Incurred costs, as defined in § 423.100, for covered Part D drugs (as defined at § 423.100) in the year that are equal to or exceed the annual out-of-pocket threshold specified at § 423.104(d)(5)(iii) for the year, 20 percent of the negotiated price of such drug.</P>
                                <P>
                                    (b) 
                                    <E T="03">Application of supplemental benefits.</E>
                                     For Part D plans offering supplemental benefits (as defined in § 423.100), the value of any applicable discount under the Manufacturer Discount Program is calculated before the application of supplemental benefits.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Application of other coverage.</E>
                                     The applicable discount is calculated before any coverage or financial assistance under another health or prescription drug benefit plan or program that provides prescription drug coverage or financial assistance.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Application of discount phase-in for specified manufacturers and specified small manufacturers</E>
                                    —(1) 
                                    <E T="03">Applicable LIS percent.</E>
                                     For an applicable drug of a specified manufacturer (as described at § 423.2716(a)) that is marketed as of August 16, 2022 (as described in paragraph (d)(3) of this section) and dispensed for an applicable beneficiary who is a subsidy eligible individual (as defined in section 1860D-14(a)(3) of the Act), the applicable discount is as follows:
                                </P>
                                <P>(i) For the individual who has not incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—  </P>
                                <P>(A) For 2025, 1 percent;</P>
                                <P>(B) For 2026, 2 percent;</P>
                                <P>(C) For 2027, 5 percent;</P>
                                <P>(D) For 2028, 8 percent; and</P>
                                <P>(E) For 2029 and each subsequent year, 10 percent.</P>
                                <P>(ii) For the individual who has incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                                <P>(A) For 2025, 1 percent;</P>
                                <P>(B) For 2026, 2 percent;</P>
                                <P>(C) For 2027, 5 percent;</P>
                                <P>(D) For 2028, 8 percent;</P>
                                <P>(E) For 2029, 10 percent;</P>
                                <P>(F) For 2030, 15 percent; and</P>
                                <P>(G) For 2031 and each subsequent year, 20 percent.</P>
                                <P>
                                    (2) 
                                    <E T="03">Applicable small manufacturer percent.</E>
                                     For an applicable drug of a specified small manufacturer (as described at § 423.2716(b)) that is marketed as of August 16, 2022 (as described in paragraph (d)(3) of this section) and dispensed for an applicable beneficiary, the applicable discount is as follows:
                                </P>
                                <P>(i) For the individual who has not incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                                <P>(A) For 2025, 1 percent;</P>
                                <P>(B) For 2026, 2 percent;</P>
                                <P>(C) For 2027, 5 percent;</P>
                                <P>(D) For 2028, 8 percent; and</P>
                                <P>(E) For 2029 and each subsequent year, 10 percent.</P>
                                <P>(ii) For the individual who has incurred costs equal to or exceeding the annual out-of-pocket threshold for the year—</P>
                                <P>(A) For 2025, 1 percent;</P>
                                <P>(B) For 2026, 2 percent;</P>
                                <P>(C) For 2027, 5 percent;</P>
                                <P>(D) For 2028, 8 percent;</P>
                                <P>(E) For 2029, 10 percent;</P>
                                <P>(F) For 2030, 15 percent; and</P>
                                <P>(G) For 2031 and each subsequent year, 20 percent.</P>
                                <P>(3) An applicable drug of a specified manufacturer or a specified small manufacturer, as applicable, is considered to have been marketed as of August 16, 2022 if the applicable drug had Part D expenditures on or before August 16, 2022, and did not have a marketing end date on the FDA NDC SPL Data Elements File before August 17, 2022.</P>
                                <P>
                                    (e) 
                                    <E T="03">Straddle claims.</E>
                                     In the case of a claim for an applicable drug for an applicable beneficiary that straddles multiple phases of the Part D benefit for claims that do not fall entirely—
                                </P>
                                <P>(1) Above the annual deductible specified at § 423.104(d)(1), the manufacturer provides the applicable discount on only the portion of the negotiated price that falls above the deductible; and</P>
                                <P>
                                    (2) Below or entirely above the annual out-of-pocket threshold specified at § 423.104(d)(5)(iii), the manufacturer provides the applicable discount on each portion of the negotiated price in 
                                    <PRTPAGE P="17596"/>
                                    accordance with this section based on the benefit phase into which each portion of the negotiated price falls.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Claims not subject to discount.</E>
                                     The following claims involving an applicable drug are not subject to discounts under the Manufacturer Discount Program:
                                </P>
                                <P>(1) Medicare Secondary Payer claims.</P>
                                <P>(2) Medicaid Subrogation claims.</P>
                                <P>(3) Non-standard format coordination of benefits claims.</P>
                                <P>(4) Manual claims with a service provider identification qualifier of “Other”.</P>
                                <P>
                                    (g) 
                                    <E T="03">Impact of applicable discount on enrollee cost sharing.</E>
                                     (1) Except as specified in paragraph (g)(2) of this section, the applicable discount does not affect the application of the standard 25 percent coinsurance under § 423.104(d)(2) or the application of the copayment amount under § 423.104(d)(5).
                                </P>
                                <P>(2) If, after the applicable discount is applied to the negotiated price of an applicable drug, the enrollee cost sharing specified under the plan would exceed such negotiated price minus the applicable discount, the enrollee cost sharing is the negotiated price minus the applicable discount.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2716 </SECTNO>
                                <SUBJECT>Phase-in of applicable discount for certain manufacturers.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Specified manufacturer.</E>
                                     Subject to the limitation with respect to manufacturer acquisitions described at § 423.2724, a specified manufacturer is a manufacturer of an applicable drug that, in 2021, had—
                                </P>
                                <P>(1) A Coverage Gap Discount Program agreement, as described at § 423.2315, in effect in accordance with § 423.2720(a)(1);</P>
                                <P>(2) Total expenditures for all of its specified drugs (as defined in § 423.2704) covered by a Coverage Gap Discount Program agreement for 2021 and covered under Part D in 2021 represented less than 1.0 percent of total expenditures for all Part D drugs in 2021; and</P>
                                <P>(3) Total expenditures for all of its specified drugs that are single source drugs and biological products for which payment may be made under Part B in 2021 represented less than 1.0 percent of the total expenditures under Part B for all drugs or biological products in 2021.</P>
                                <P>
                                    (b) 
                                    <E T="03">Specified small manufacturer.</E>
                                     Subject to the limitation with respect to manufacturer acquisition described at § 423.2724, a specified small manufacturer is a manufacturer of an applicable drug that, in 2021—
                                </P>
                                <P>(1) Is a specified manufacturer as described in paragraph (a) of this section; and</P>
                                <P>(2) The total expenditures under Part D for any one of its specified small manufacturer drugs covered under a Coverage Gap Discount Program agreement for 2021 and covered under Part D in 2021 are equal to or greater than 80 percent of the total expenditures for all its specified small manufacturer drugs covered under Part D in 2021.</P>
                                <P>
                                    (c) 
                                    <E T="03">Aggregation rule.</E>
                                     All entities, including corporations, partnerships, proprietorships, and other entities treated as a single employer under subsection (a) or (b) of section 52 of the Internal Revenue Code of 1986 are treated as one manufacturer for purposes of this section.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2720 </SECTNO>
                                <SUBJECT>Determination of phase-in eligibility.</SUBJECT>
                                <P>For each manufacturer with one or more FDA-assigned labeler codes covered by a Manufacturer Discount Program agreement, CMS will determine whether the manufacturer is a specified manufacturer or a specified small manufacturer when the manufacturer executes a Manufacturer Discount Program agreement, or, in the case of a manufacturer whose FDA-assigned labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement, when such labeler code(s) is first added to such agreement. In applying the aggregation rule at § 423.2716(c), CMS will attribute expenditures for a drug to a manufacturer based on the NDC(s) for the drug, as reported on PDE records. Specifically, CMS will match the labeler code extracted from the first 5 digits of each NDC to the manufacturer to whom the labeler code is assigned by the FDA.</P>
                                <P>
                                    (a) 
                                    <E T="03">Identification of specified manufacturers.</E>
                                     (1) A manufacturer is considered to have had a Coverage Gap Discount Program agreement in 2021, as specified at § 423.2716(a)(1), if the manufacturer—
                                </P>
                                <P>(i) Had a Coverage Gap Discount Program agreement in effect during 2021; or</P>
                                <P>(ii) Participated in the Coverage Gap Discount Program in 2021 by means of an arrangement whereby its labeler code(s) was covered by another manufacturer's Coverage Gap Discount Program agreement in effect during 2021.</P>
                                <P>
                                    (2) 
                                    <E T="03">Part D total expenditures.</E>
                                     In calculating the Part D total expenditures for 2021, CMS will include the total expenditures, as defined at § 423.2704, reported on all final action, non-delete PDE records submitted as of June 30, 2022 for all Part D drugs with dates of dispensing in benefit year 2021.
                                </P>
                                <P>(i) For purposes of calculating each manufacturer's Part D total expenditures for applicable drugs and percent share of Part D total expenditures for 2021, CMS will—</P>
                                <P>(A) Identify the relevant NDCs attributable to the manufacturer as reported on the PDE record based on the manufacturer's FDA-assigned labeler code extracted from the first 5 digits of each NDC;</P>
                                <P>(B) Calculate the Part D total expenditures for applicable drugs of the manufacturer by summing the 2021 Part D total expenditures for all relevant NDCs attributable to the manufacturer; and</P>
                                <P>(C) Divide the 2021 Part D total expenditures for all applicable drugs of the manufacturer by the 2021 Part D total expenditures for all Part D drugs, then multiply by 100 to calculate the manufacturer's percent share.</P>
                                <P>(ii) If the manufacturer's Part D total expenditures for its applicable drugs are less than 1.0 percent of the 2021 Part D total expenditures, CMS will consider the manufacturer to have satisfied the Part D total expenditure criterion for specified manufacturer phase-in eligibility, specified at § 423.2716(a)(2).</P>
                                <P>
                                    (3) 
                                    <E T="03">Part B total expenditures.</E>
                                     In calculating the Part B total expenditures for all drugs and biological products for 2021, CMS will include all Part B Carrier, durable medical equipment (DME), and Outpatient Medicare Part B Fee-for-Service claim line items with a drug- or biological product-related Healthcare Common Procedure Coding System (HCPCS) code submitted as of December 31, 2022.
                                </P>
                                <P>(i) For purposes of calculating each manufacturer's Part B total expenditures for applicable drugs that are single source drugs and biological products and each manufacturer's percent share of Part B total expenditures for 2021, CMS will—</P>
                                <P>(A) Map all identified HCPCS codes to NDCs;</P>
                                <P>(B) Identify all mapped HCPCS codes in paragraph (a)(3)(i)(A) of this section that map to NDCs associated with single source drugs or biological products;</P>
                                <P>(C) Identify all mapped HCPCS codes identified in paragraph (a)(3)(i)(B) of this section that map only to NDCs associated with single source drugs or biological products of the same manufacturer, consistent with the aggregation rule at § 423.2716(c), based on the manufacturer's FDA-assigned labeler code(s) extracted from the first 5 digits of each NDC;</P>
                                <P>
                                    (D) Attribute 2021 Part B total expenditures for all applicable drugs that are single source drugs or biological products identified in paragraph (a)(3)(i)(C) of this section to each manufacturer, consistent with the 
                                    <PRTPAGE P="17597"/>
                                    aggregation rule at § 423.2716(c), based on the manufacturer's FDA-assigned labeler code(s) extracted from the first 5 digits of each NDC; and
                                </P>
                                <P>(E) Divide the 2021 Part B total expenditures attributed to each manufacturer in paragraph (a)(3)(i)(D) of this section by the 2021 Part B total expenditures for all drugs and biological products, then multiply by 100 to calculate the manufacturer's percent share.</P>
                                <P>(ii) If the manufacturer's Part B total expenditures for its applicable drugs that are single source drugs and biologicals are less than 1.0 percent of the 2021 Part B total expenditures, CMS will consider the manufacturer to have satisfied the Part B total expenditure criterion for specified manufacturer phase-in eligibility, specified at § 423.2716(a)(3).</P>
                                <P>
                                    (b) 
                                    <E T="03">Identification of specified small manufacturers.</E>
                                     (1) For each specified manufacturer identified in paragraph (a) of this section, CMS will determine if the 2021 total expenditures under Part D for any one of the manufacturer's specified drugs covered under a Coverage Gap Discount Program agreement for 2021, and covered under Part D in 2021, are equal to or greater than 80 percent of the total expenditures for all of its specified drugs covered under Part D in 2021, as required under § 423.2716(b)(2), as follows.
                                </P>
                                <P>
                                    (i) 
                                    <E T="03">Identification of specified small manufacturer drugs.</E>
                                     (A) For purposes of this section, one specified small manufacturer drug includes—
                                </P>
                                <P>
                                    (
                                    <E T="03">1</E>
                                    ) For drug products, all dosage forms and strengths of a drug with the same active moiety and the same holder of the new drug application (NDA), as described in section 505(c) of the Federal Food, Drug, and Cosmetic Act, inclusive of products that are marketed under different NDAs.
                                </P>
                                <P>
                                    (
                                    <E T="03">2</E>
                                    ) For biological products, all dosage forms and strengths of the biological product with the same active ingredient and the same holder of the biologics license application (BLA), as described in section 351(a) of the Public Health Service Act, inclusive of products that are marketed under different BLAs.
                                </P>
                                <P>(B) CMS will identify the holder of the NDA or BLA as reported in Drugs@FDA or the FDA Purple Book, respectively.</P>
                                <P>(C) If a drug is a fixed combination drug, as described in 21 CFR 300.50, with two or more active ingredients or active moieties, the distinct combination of active ingredients or active moieties will be considered one active ingredient or active moiety for the purpose of identifying a specified small manufacturer drug.</P>
                                <P>(D) CMS will attribute 2021 Part D total expenditures for one specified small manufacturer drug, including authorized generic drugs and repackaged and relabeled drugs, as applicable, to a specified manufacturer based on the NDC(s) for the drug, as reported on PDE records, by matching the labeler code extracted from the first 5 digits of each NDC to the manufacturer to whom the labeler code is assigned by the FDA.</P>
                                <P>
                                    (ii) 
                                    <E T="03">Calculation of Part D total expenditures for each drug for 2021.</E>
                                     CMS will calculate the Part D total expenditures for each drug, aggregated in accordance with paragraph (b)(1)(i) of this section, attributable to the manufacturer by summing the Part D total expenditures for all NDCs under each drug as reported on all final action, non-delete PDE records submitted as of June 30, 2022, with dates of dispensing in benefit year 2021.
                                </P>
                                <P>
                                    (iii) 
                                    <E T="03">Calculation of each specified drug's percent share of the specified manufacturer's Part D total expenditures for applicable drugs for 2021.</E>
                                     CMS will divide the 2021 Part D total expenditures for each drug, aggregated in accordance with paragraph (b)(1)(i) of this section, by the 2021 Part D total expenditures for all applicable drugs of the manufacturer, as determined under paragraph (a)(2) of this section, then multiply by 100 to determine the percent share.
                                </P>
                                <P>
                                    (iv) 
                                    <E T="03">Part D total expenditures for a specific drug for 2021 and small manufacturer phase-in eligibility.</E>
                                     If the 2021 Part D total expenditures for one specified drug of the manufacturer are equal to or greater than 80 percent of the manufacturer's 2021 Part D total expenditures for all of its specified drugs, CMS will consider the manufacturer to have satisfied the criterion at § 423.2716(b)(2) for specified small manufacturer phase-in eligibility.
                                </P>
                                <P>(2) [Reserved]</P>
                                <P>
                                    (c) 
                                    <E T="03">Written notice of determination.</E>
                                     (1) CMS will issue a phase-in eligibility determination notice to each manufacturer that has executed and has in effect a Manufacturer Discount Program agreement when such determination is made, delivered by electronic mail, to the primary point of contact as identified by the manufacturer.
                                </P>
                                <P>(2) In the case of a manufacturer that participates in the Manufacturer Discount Program by means of an arrangement whereby its labeler code(s) is covered by another manufacturer's Manufacturer Discount Program agreement, CMS will issue a phase-in eligibility determination notice to the agreement holder.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2724 </SECTNO>
                                <SUBJECT>Effect of manufacturer acquisition on phase-in eligibility.</SUBJECT>
                                <P>For purposes of the Manufacturer Discount Program, when a manufacturer acquires another manufacturer after 2021 (that is, the acquired manufacturer becomes part of such acquiring manufacturer under the aggregation rule at § 423.2716(c)), the acquired manufacturer assumes the phase-in status of the acquiring manufacturer, effective at the beginning of the plan year immediately following the acquisition or, for an acquisition before 2025, effective January 1, 2025.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2728 </SECTNO>
                                <SUBJECT>Recalculation of phase-in eligibility determination.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Right to request a recalculation.</E>
                                     A manufacturer that has received a phase-in eligibility determination notice, as described at § 423.2720(c), may request a recalculation of such determination in accordance with the requirements of this section.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Timeframe and method of filing.</E>
                                     A manufacturer that seeks a recalculation of its phase-in eligibility determination must file the request, in the manner specified by CMS, no later than 30 calendar days from the date the phase-in eligibility determination notice is electronically sent to the manufacturer. In order to receive consideration, the recalculation request must clearly describe the issue(s) forming the basis of the request and must include supporting documentation.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Disposition and notification.</E>
                                     After consideration of the issues raised, CMS will decide whether to perform the recalculation, and will issue a written decision to the manufacturer that will include CMS's decision about whether to perform the requested recalculation and, if such recalculation is performed, the resulting eligibility determination. The decision is final and binding, subject to the requirements of the Manufacturer Discount Program under section 1860D-14C of the Act, this subpart, and the Manufacturer Discount Program agreement.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Limitation.</E>
                                     The recalculation process cannot be used to request or be granted an exception to the requirements set forth in statute that determine eligibility for the specified manufacturer or specified small manufacturer phase-in.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2732 </SECTNO>
                                <SUBJECT>Use of third party administrator.  </SUBJECT>
                                <P>
                                    (a) CMS will engage a third party administrator (TPA) to assist in the administration of the Manufacturer Discount Program, which may include and is not limited to facilitating—
                                    <PRTPAGE P="17598"/>
                                </P>
                                <P>(1) Manufacturer Discount Program invoicing;</P>
                                <P>(2) The receipt and distribution of funds of a manufacturer; and</P>
                                <P>(3) The dispute resolution process described in § 423.2764.</P>
                                <P>(b) Agreement holders must—</P>
                                <P>(1) Enter into and have in effect, under the terms and conditions specified by CMS, an agreement with the TPA in order to participate in the Manufacturer Discount Program. The TPA agreement will only terminate upon the termination of the Manufacturer Discount Program agreement; and</P>
                                <P>(2) Establish and maintain electronic connectivity with the TPA for the purpose of timely transmission of data and funds.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2736 </SECTNO>
                                <SUBJECT>Requirement for point-of-sale discounts.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Point-of-sale discounts.</E>
                                     Part D sponsors must provide applicable discounts on applicable drugs at the point of sale on behalf of the manufacturer. As part of this process, plan sponsors must determine—
                                </P>
                                <P>(1) Whether an enrollee is an applicable beneficiary as described in § 423.100;</P>
                                <P>(2) Whether a drug is an applicable drug as described in § 423.100; and</P>
                                <P>(3) The amount of the discount, in accordance with § 423.2712.</P>
                                <P>
                                    (b) 
                                    <E T="03">Direct member reimbursement (DMR).</E>
                                     Part D sponsors must provide applicable discounts on claims for applicable drugs submitted by applicable beneficiaries as DMRs, including out-of-network and in-network paper claims, if such claims are payable under the Part D plan. While the sponsor must account for the discount in adjudicating the DMR request and the associated PDE submitted to CMS, the point-of-sale requirement does not apply.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Pharmacy prompt payment.</E>
                                     Part D sponsors must reimburse a network pharmacy (as defined in § 423.100) the amount of the applicable discount within the applicable number of calendar days (as defined in § 423.100) of the date of dispensing (as defined in § 423.100) of an applicable drug, consistent with § 423.520.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Prescription drug event (PDE) requirements.</E>
                                     Part D sponsors must report the applicable discounts made available to their enrollees under the Manufacturer Discount Program on the PDE records associated with such discounts.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Retroactive adjustments.</E>
                                     Part D sponsors must make retroactive adjustments to applicable discounts as necessary to reflect applicable changes, including changes to the claim, beneficiary eligibility, or benefit phase determined after the date of dispensing.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2740 </SECTNO>
                                <SUBJECT>Negative invoice payment process for Part D sponsors.</SUBJECT>
                                <P>(a) CMS will invoice negative amounts to Part D sponsors when a PDE(s) which had been previously invoiced is deleted or adjusted such that the reported Manufacturer Discount Program discount amount is less than originally invoiced.</P>
                                <P>(b) Part D sponsors are required to pay such negative invoice amounts in the manner specified by CMS within 38 calendar days of receipt of the invoice.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2744 </SECTNO>
                                <SUBJECT>Prospective payments to Part D sponsors.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General rule.</E>
                                     CMS will provide monthly prospective Manufacturer Discount Program payments to Part D sponsors for sponsors to advance manufacturer discounts as specified in § 423.2736(a) and reimburse network pharmacies as specified in § 423.2736(c).
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Exception.</E>
                                     CMS will not provide prospective Manufacturer Discount Program payments to employer group waiver plans.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Reconciliation.</E>
                                     CMS will reconcile prospective Manufacturer Discount Program payments in accordance with subpart G of this part.
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Manufacturer bankruptcy.</E>
                                     In the event that an agreement holder declares bankruptcy, as described in title 11 of the United States Code, and as a result of such bankruptcy does not pay the invoiced amounts described in § 423.2756(a), CMS will adjust the Manufacturer Discount Program reconciliation amount for affected Part D sponsors to account for the invoiced amounts owed for the contract year being reconciled. The Government reserves the right to file a proof-of-claim and take any other action under bankruptcy law, as appropriate, to attempt to recover such unpaid amounts and any civil money penalties imposed by CMS under this part.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2748 </SECTNO>
                                <SUBJECT>Requirement to use the Health Plan Management System.</SUBJECT>
                                <P>Agreement holders are required to maintain Health Plan Management System (HPMS) access and use the HPMS to—</P>
                                <P>(a) Provide and maintain required information, as specified by CMS;</P>
                                <P>(b) Attest to the completeness and accuracy of data necessary for CMS to determine whether the manufacturer qualifies as a specified manufacturer or specified small manufacturer, as described at § 423.2716;</P>
                                <P>(c) Execute a Manufacturer Discount Program agreement and a TPA agreement; and</P>
                                <P>(d) As otherwise specified by CMS to administer the program.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2752 </SECTNO>
                                <SUBJECT>Manufacturer Discount Program agreement.</SUBJECT>
                                <P>Manufacturers that are agreement holders, as defined in § 423.2704, must comply with all requirements of this section.</P>
                                <P>
                                    (a) 
                                    <E T="03">Requirements of agreement.</E>
                                     The manufacturer must do all of the following:
                                </P>
                                <P>(1) Reimburse, within the required 38-day timeframe, all applicable discounts invoiced to the manufacturer, consistent with the requirements at § 423.2756(b).</P>
                                <P>(2) Provide CMS with all labeler codes covered by the agreement.</P>
                                <P>(3) Ensure that the labeler codes provided to CMS under paragraph (a)(2) of this section include, at a minimum, all labeler codes assigned by the FDA to the manufacturer, in accordance with § 423.2756(c)(3).</P>
                                <P>(4) Comply with the requirements established by CMS for purposes of administering the Manufacturer Discount Program and monitoring compliance with such program, including providing the manufacturer's Employer Identification Number (EIN) and other identifying information to CMS upon request.</P>
                                <P>(5) Comply with the requirements related to the provision and maintenance of data at § 423.2756(c).</P>
                                <P>(6) Enter into and have in effect, under the terms and conditions specified by CMS, an agreement with the TPA, as described at § 423.2732(b)(1), and comply with such agreement and all TPA instructions, processes, and requirements.</P>
                                <P>(7) Provide and attest to information in the manner and form specified by CMS as necessary for CMS to determine eligibility for and implement the specified manufacturer and specified small manufacturer phase-ins described at § 423.2716.</P>
                                <P>
                                    (8) Agree that, no less than 30 days after the date CMS determines that a primary manufacturer of a selected drug has, in accordance with paragraph (c)(1)(ii) of this section, provided notice to CMS of its decision not to enter into or continue its participation in the Medicare Drug Price Negotiation Program and to discontinue its applicable agreements under the Medicaid Drug Rebate Program and the Manufacturer Discount Program, none of the drugs of such primary manufacturer will be covered by the manufacturer's Manufacturer Discount Program agreement.
                                    <PRTPAGE P="17599"/>
                                </P>
                                <P>(9) Comply with all other requirements of the Manufacturer Discount Program.</P>
                                <P>
                                    (b) 
                                    <E T="03">Agreement term and renewal.</E>
                                     (1) A Manufacturer Discount Program agreement described in this section is valid for an initial term of not less than 12 months and automatically renews for a period of 1 year on each subsequent January 1, except as described in paragraph (b)(3) this section, unless terminated in accordance with paragraph (c) of this section.  
                                </P>
                                <P>(2) For calendar year 2025, an agreement holder must enter into such agreement no later than March 1, 2024, and the initial 12-month term of such agreement begins on January 1, 2025 and ends on December 31, 2025.</P>
                                <P>(3) For calendar year 2026 and subsequent years, a Manufacturer Discount Program agreement will become effective on the first day of a calendar quarter as follows:</P>
                                <P>(i) An agreement holder must enter into the agreement no later than the last day of the first month of a calendar quarter in order for the agreement to be effective on the first day of the next calendar quarter.</P>
                                <P>(ii) If an agreement holder enters into the agreement after the last day of the first month of a particular calendar quarter, the agreement becomes effective on the first day of the second calendar quarter after the calendar quarter in which the manufacturer entered into the agreement.</P>
                                <P>(iii) An initial term that begins on January 1 will end on December 31 of the same calendar year. An initial term that begins on April 1, July 1, or October 1 will end on December 31 of the following calendar year.</P>
                                <P>
                                    (c) 
                                    <E T="03">Termination of Manufacturer Discount Program agreement</E>
                                    —(1) 
                                    <E T="03">Termination by CMS.</E>
                                     (i) CMS may terminate a Manufacturer Discount Program agreement for a knowing and willful violation of the requirements of such agreement or other good cause shown in relation to a manufacturer's participation in the Manufacturer Discount Program, including good cause as set forth in paragraph (c)(1)(ii) of this section.
                                </P>
                                <P>
                                    (ii) CMS may terminate a Manufacturer Discount Program agreement for good cause, in the case of a primary manufacturer under the Medicare Drug Price Negotiation Program, upon submission of a request from such manufacturer to terminate its applicable agreements under the Manufacturer Discount Program in connection with a notice of the primary manufacturer's decision that it is unwilling to participate in, or continue its participation in, the Medicare Drug Price Negotiation Program. If CMS determines such a notice complies with all requirements set forth in applicable regulations and guidance for the Medicare Drug Price Negotiation Program, the primary manufacturer's request will constitute good cause under paragraph (c)(1) of this section to terminate the primary manufacturer's applicable agreements under the Manufacturer Discount Program. The primary manufacturer's applicable agreements include any Manufacturer Discount Program agreement for which the primary manufacturer is the agreement holder, as well as any arrangement under § 423.2708(b)(2) in which FDA-assigned labeler codes of the primary manufacturer are covered under the Manufacturer Discount Program agreement of another manufacturer. If applicable, CMS will effectuate termination of coverage of such FDA-assigned labeler codes of the primary manufacturer that are covered under the Manufacturer Discount Program agreement of another manufacturer in accordance with paragraph (c)(1)(v)(A)(
                                    <E T="03">1</E>
                                    ) of this section.
                                </P>
                                <P>(iii) Any termination by CMS must not be effective earlier than 30 days from the date of the notice to the manufacturer of such termination. If a hearing is timely requested by the manufacturer in accordance with paragraph (c)(1)(iv) of this section, such termination must not be effective prior to resolution of timely appeal requests received in accordance with the requirements of this section.</P>
                                <P>(iv) CMS will provide, upon written request, a manufacturer a hearing concerning a termination by CMS as follows:</P>
                                <P>(A) This hearing will take place prior to the effective date of the termination with sufficient time for the termination to be repealed prior to the effective date if CMS determines repeal would be appropriate. If a manufacturer or CMS receives an unfavorable decision from the hearing officer, the manufacturer or CMS may request review by the CMS Administrator within 30 calendar days of receipt of the notification of such determination. The decision of the CMS Administrator is final and binding.</P>
                                <P>(B) A timely request for a hearing before a hearing officer or review by the CMS Administrator will stay termination until the parties have exhausted their appeal rights under the Manufacturer Discount Program, which means either the timeframes to pursue a hearing before a hearing officer or review by the CMS Administrator have passed or a final decision by the Administrator has been issued and there is no remaining opportunity to request further administrative review.</P>
                                <P>(C) In the case of a termination by CMS under paragraph (c)(1)(ii) of this section with respect to a primary manufacturer under the Medicare Drug Price Negotiation Program, the hearing will be held solely on the papers. The only question to be decided in such hearing is whether the primary manufacturer has asked to rescind its request to terminate under paragraph (c)(1)(ii) of this section prior to the effective date of the termination. If so, CMS will automatically grant such request from the primary manufacturer to rescind its request to terminate under paragraph (c)(1)(ii) of this section.</P>
                                <P>(v) In addition to the termination under paragraph (c)(1)(ii) of this section of any Manufacturer Discount Program agreement for which the primary manufacturer is the agreement holder, CMS will effectuate the removal of labeler code(s) that are covered under the Manufacturer Discount Program agreement of another manufacturer and termination of coverage of any specific NDC(s) of applicable drugs and selected drugs of a primary manufacturer that are covered under the Manufacturer Discount Program agreement of another manufacturer as follows:</P>
                                <P>(A) If a primary manufacturer provides notice to CMS that it is unwilling to participate in, or continue its participation in, the Medicare Drug Price Negotiation Program, consistent with paragraph (c)(1)(ii) of this section, no earlier than 30 days from the date CMS sends the notice of termination to the manufacturer in accordance with paragraph (c)(1)(iii) of this section, CMS will effectuate—</P>
                                <P>
                                    (
                                    <E T="03">1</E>
                                    ) The removal of the FDA-assigned labeler code(s) of the primary manufacturer from any Manufacturer Discount Program agreement of another manufacturer whereby such labeler codes of the primary manufacturer are covered in accordance with § 423.2708(b)(2); and
                                </P>
                                <P>
                                    (
                                    <E T="03">2</E>
                                    ) The termination of coverage under any Manufacturer Discount Program agreement specific to NDCs of applicable drugs and selected drugs for which the primary manufacturer is the holder of the new drug application or biologics license application. Such termination of coverage under this paragraph (c)(1)(v)(A)(
                                    <E T="03">2</E>
                                    ) will apply to all applicable drug and selected drug NDCs of the primary manufacturer for which the labeler code is assigned to a manufacturer other than the primary manufacturer and for which the primary manufacturer is the new drug application or biologics license application holder for such drug.
                                    <PRTPAGE P="17600"/>
                                </P>
                                <P>
                                    (B) The removal of labeler code(s) in accordance with paragraph (c)(1)(v)(A)(
                                    <E T="03">1</E>
                                    ) of this section and the termination of coverage specific to NDCs in accordance with paragraph (c)(1)(v)(A)(
                                    <E T="03">2</E>
                                    ) of this section do not affect the agreement holder's responsibility to reimburse Part D sponsors for applicable discounts for applicable drugs with such labeler code(s) or such NDCs that were incurred under the agreement before the effective date of removal or termination.
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Termination by the manufacturer.</E>
                                     An agreement holder may terminate its Manufacturer Discount Program agreement for any reason. The effective date of the termination is as follows:
                                </P>
                                <P>(i) If the agreement holder notifies CMS of its intent to terminate before January 31 of a calendar year, January 1 of the succeeding calendar year.</P>
                                <P>(ii) If the agreement holder notifies CMS of its intent to terminate on or after January 31 of a calendar year, January 1 of the second succeeding calendar year.</P>
                                <P>
                                    (3) 
                                    <E T="03">Post-termination obligations.</E>
                                     Termination of a Manufacturer Discount Program agreement under the requirements of this section does not affect the agreement holder's responsibility to reimburse Part D sponsors for applicable discounts for applicable drugs having NDCs with labeler code(s) covered by such agreement that were incurred under the agreement prior to the effective date of the termination.
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">Reinstatement.</E>
                                     Reinstatement in the Manufacturer Discount Program subsequent to termination is available to a manufacturer only upon payment of any and all outstanding applicable discounts and penalties incurred under any previous Manufacturer Discount Program agreement or Coverage Gap Discount Program agreement. The timing of the reinstatement must be consistent with the requirements at § 423.2752(b).
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Automatic assignment upon change of ownership.</E>
                                     In the event of a change in ownership of a manufacturer that is an agreement holder, the Manufacturer Discount Program agreement is automatically assigned to the new owner, and all terms and conditions of the agreement remain in effect as to the new owner unless terminated in accordance with requirements at § 423.2752(c). The new agreement holder agrees to be bound by and to perform all the duties and responsibilities under the Manufacturer Discount Program, and assumes all obligations and liabilities of, and all claims incurred against, the prior agreement holder under the Manufacturer Discount Program agreement whether arising before or after the effective date of the change of ownership.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2756 </SECTNO>
                                <SUBJECT>Manufacturer requirements.</SUBJECT>
                                <P>Manufacturers that are agreement holders, as defined at § 423.2704, must comply with all requirements of this section.</P>
                                <P>
                                    (a) 
                                    <E T="03">Manufacturer invoicing.</E>
                                     CMS will—
                                </P>
                                <P>(1) Calculate the amounts owed for applicable discounts for applicable drugs having NDCs with a labeler code covered by the agreement holder's Manufacturer Discount Program agreement;</P>
                                <P>(2) Itemize invoices at the NDC level;</P>
                                <P>(3) Invoice the agreement holder on a quarterly basis, consistent with the published invoicing calendar; and</P>
                                <P>(4) Invoice manufacturer discount amounts from accepted PDE data for 37 months following the end of the benefit year.  </P>
                                <P>
                                    (b) 
                                    <E T="03">Requirement for timely payment.</E>
                                     (1) Agreement holders that are invoiced in accordance with paragraph (a) of this section are required to pay invoiced amounts within 38 calendar days of receipt of the invoice, in the manner specified by CMS, except as specified in paragraphs (b)(2) and (3) of this section.
                                </P>
                                <P>(2) If an invoice deadline falls on a Saturday, Sunday, or legal holiday, the payment timeframe is extended to the first day thereafter which is not a Saturday, Sunday, or legal holiday.</P>
                                <P>(3) Agreement holders are not permitted to withhold payment for any invoiced amount, including a disputed amount while a dispute is pending under § 423.2764, except when the basis for the dispute is that the invoiced amount does not correspond to NDCs of labeler codes covered by the agreement holder's Manufacturer Discount Program agreement. If payment is withheld in such an instance, the agreement holder must notify the TPA within 38 calendar days of the manufacturer's receipt of the applicable invoice that payment is being withheld for this reason.</P>
                                <P>
                                    (c) 
                                    <E T="03">Reporting requirements</E>
                                    —(1) 
                                    <E T="03">General.</E>
                                     Agreement holders are required to collect, have available, and maintain appropriate data related to the labeler codes covered by their Manufacturer Discount Program agreement, and maintain such data for a period of not less than 10 years from the date of payment of the invoice.
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Manufacturer ownership.</E>
                                     Agreement holders must—
                                </P>
                                <P>(i) Provide and attest to ownership and other data, in the form and manner specified by CMS, as necessary for CMS to determine eligibility for and implement the discount phase-ins described at § 423.2716;</P>
                                <P>(ii) Notify CMS of a change in their ownership no later than 30 calendar days after the agreement holder executes a legal obligation for such an arrangement and no later than 45 calendar days prior to such change in ownership taking effect; and</P>
                                <P>(iii) If the agreement holder covers the FDA-assigned labeler code(s) of another manufacturer by its Manufacturer Discount Program agreement in accordance with § 423.2708(b)(2), comply with the requirements of paragraphs (c)(2)(i) and (ii) of this section with respect to such other manufacturer.</P>
                                <P>
                                    (3) 
                                    <E T="03">Labeler codes.</E>
                                     (i) An agreement holder is required to cover by its agreement all labeler codes assigned by the FDA to the agreement holder that contain NDCs for the agreement holder's applicable drugs and selected drugs.
                                </P>
                                <P>(ii) Consistent with § 423.2708(b)(2), an agreement holder may cover by its Manufacturer Discount Program agreement applicable drugs or selected drugs with labeler code(s) assigned by the FDA to another manufacturer, provided the other manufacturer has not executed and does not have in effect its own Manufacturer Discount Program agreement in accordance with § 423.2708(b)(1).</P>
                                <P>(iii) Agreement holders must provide to CMS:</P>
                                <P>(A) All labeler codes assigned by the FDA to the agreement holder that contain NDCs for the agreement holder's applicable drugs and selected drugs, consistent with paragraph (c)(3)(iv) of this section.</P>
                                <P>(B) All labeler codes assigned by the FDA to another manufacturer that the agreement holder covers by its Manufacturer Discount Program agreement and for which the agreement holder agrees to pay discounts.</P>
                                <P>(iv) Agreement holders must provide labeler code(s) newly assigned by the FDA to the agreement holder to CMS no later than 3 business days after receiving written notification of the labeler code(s) from the FDA, and in advance of providing any NDCs associated with such newly assigned labeler codes to electronic database vendors.</P>
                                <P>
                                    (v) Agreement holders must maintain the list of labeler codes covered by their Manufacturer Discount Program agreement, in the manner specified by CMS. Failure to update labeler codes covered by a Manufacturer Discount Program agreement in accordance with the requirements in this section and applicable CMS guidance does not change an agreement holder's obligation 
                                    <PRTPAGE P="17601"/>
                                    to pay invoiced amounts for applicable drugs.
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">FDA and related records.</E>
                                     (i) Agreement holders must:
                                </P>
                                <P>(A) Ensure that all of their FDA-assigned labeler codes that contain NDCs for any of their applicable drugs or selected drugs are properly listed on the FDA NDC Directory;</P>
                                <P>(B) Electronically list all NDCs of their applicable drugs or selected drugs with the FDA in advance of commercial distribution of the product(s);</P>
                                <P>(C) Maintain up-to-date electronic FDA registrations and listings of all NDCs, including the timely removal of discontinued NDCs from the FDA NDC Directory; and</P>
                                <P>(D) Maintain up-to-date listings with electronic database vendors to whom they provide their NDCs for pharmacy claims processing.</P>
                                <P>(ii) If such agreement holder's Manufacturer Discount Program agreement covers labeler code(s) that are assigned by the FDA to another manufacturer that participates in the Manufacturer Discount Program in accordance with § 423.2708(b)(2), the agreement holder must ensure that the requirements of this section are met with respect to such labeler codes.</P>
                                <P>
                                    (d) 
                                    <E T="03">Transfer of labeler codes.</E>
                                     Agreement holders are permitted to transfer labeler code(s) from one Manufacturer Discount Program agreement to another provided that the transfer is consistent with the requirements of this subpart and the Manufacturer Discount Program agreement and is approved by CMS.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2760 </SECTNO>
                                <SUBJECT>Audits.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Manufacturer audits of TPA data.</E>
                                     (1) An agreement holder may conduct periodic audits, no more often than annually, of the TPA data and information used to determine discounts for applicable drugs covered by the agreement holder's Manufacturer Discount Program agreement, directly or through third parties.
                                </P>
                                <P>(2) The agreement holder must provide the TPA with 60 calendar days' notice of the reasonable basis for the audit and a description of the information required for the audit.</P>
                                <P>(3) The audit is limited as follows:</P>
                                <P>(i) The data provided to the agreement holder conducting the audit is limited to a statistically significant random sample of data held by the TPA that were used to determine applicable discounts for applicable drugs having NDCs with labeler codes covered by the agreement holder's Manufacturer Discount Program agreement.</P>
                                <P>(ii) Manufacturers are not permitted to audit CMS records or the records of Part D sponsors beyond the data provided to the TPA, which includes claim-level information.</P>
                                <P>(iii) Audits must occur at a location specified by the TPA and, with the exception of work papers, audit data cannot be removed from such specified location.</P>
                                <P>(iv) The auditor for the agreement holder may release only an opinion of the audit results and is prohibited from releasing other information obtained from the audit, including work papers, to its client, employer, or any other party.</P>
                                <P>
                                    (b) 
                                    <E T="03">CMS audits of manufacturers.</E>
                                     (1) An agreement holder is subject to periodic audit by CMS no more often than annually, directly or through third parties, as specified in this section.
                                </P>
                                <P>(2) CMS must provide the agreement holder with 60 calendar days' notice of the reasonable basis for the audit and a description of the information required for the audit.</P>
                                <P>(3) CMS has the right to audit appropriate data, including data related to labeler codes covered by the agreement holder's Manufacturer Discount Program agreement and related NDC last lot expiration dates, utilization, and pricing information relied on by the agreement holder to dispute quarterly invoices, and any other data CMS determines necessary to evaluate compliance with the requirements of the Manufacturer Discount Program.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2764 </SECTNO>
                                <SUBJECT>Dispute resolution.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Initial disputes.</E>
                                     Agreement holders may dispute applicable discounts invoiced to such agreement holder under § 423.2756(a).
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Timeframe and method of filing.</E>
                                     Initial disputes must be filed, in the manner specified by CMS, no later than the dispute submission deadline, as defined at § 423.2704. The agreement holder must explain why it believes the invoiced discount amount is in error and must provide supporting evidence that is material, specific, and related to the dispute.
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Timeframe for making a determination.</E>
                                     CMS will issue a written determination on an initial dispute no later than 60 calendar days from the dispute submission deadline.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Independent review.</E>
                                     An agreement holder that receives an unfavorable determination from CMS on its initial dispute or has not received a determination within 60 calendar days from the dispute submission deadline, may request review by the independent review entity (IRE) contracted by CMS.
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Timeframe and method of filing.</E>
                                     A request for review by the IRE must be filed, in the manner specified by CMS, no later than the earlier of the following:
                                </P>
                                <P>(i) Thirty calendar days from the unfavorable determination on the initial dispute.</P>
                                <P>(ii) Ninety calendar days from the dispute submission deadline, if no determination was made within 60 calendar days of the dispute submission deadline.</P>
                                <P>
                                    (2) 
                                    <E T="03">Information considered.</E>
                                     In addition to the information provided by the agreement holder, the IRE considers information received from CMS, the TPA, the Part D sponsor, or other sources. The IRE may request additional information from the agreement holder for the purpose of considering the appeal. Failure to comply with this request for additional information within the timeframe specified may result in the IRE issuing a denial.
                                </P>
                                <P>
                                    (3) 
                                    <E T="03">Timeframe for making a decision.</E>
                                     The IRE issues a written decision to the agreement holder and to CMS no later than 90 calendar days from receipt of the request.
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">Notice requirements.</E>
                                     The IRE decision must include all of the following:
                                </P>
                                <P>(i) A clear statement indicating whether the decision is favorable or unfavorable to the agreement holder.</P>
                                <P>(ii) An explanation of the rationale for the IRE's decision.</P>
                                <P>(iii) Instructions on how to request a review by the CMS Administrator.  </P>
                                <P>
                                    (5) 
                                    <E T="03">Effect of IRE decision.</E>
                                     A decision by the IRE is binding on all parties unless the agreement holder or CMS files a valid request for review by the CMS Administrator under the process described in paragraph (c) of this section.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Review by the CMS Administrator.</E>
                                     (1) CMS or an agreement holder that receives an unfavorable decision by the IRE may request a review of a determination from the IRE by the CMS Administrator.
                                </P>
                                <P>(2) A request for review by the CMS Administrator must be filed, in the manner specified by CMS, no later than 30 calendar days from the date of the IRE decision.</P>
                                <P>(3) The CMS Administrator issues a written decision to both parties.</P>
                                <P>(4) A decision by the CMS Administrator is final and binding.</P>
                                <P>
                                    (d) 
                                    <E T="03">Adjustment to invoiced amounts.</E>
                                     CMS adjusts future invoices (or implements an alternative reimbursement process if determined necessary) if the dispute is resolved in favor of the agreement holder.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Limitation.</E>
                                     The dispute resolution process described in this section must not be used to dispute a decision by CMS to terminate an agreement holder's 
                                    <PRTPAGE P="17602"/>
                                    participation in the Manufacturer Discount Program under § 423.2752(c)(1) or a decision by CMS about a manufacturer's eligibility for discount phase-ins described at § 423.2720.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 423.2768 </SECTNO>
                                <SUBJECT>Civil money penalties.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General rule.</E>
                                     An agreement holder that fails to provide, in accordance with the terms of its Manufacturer Discount Program agreement and the requirements of the Manufacturer Discount Program, applicable discounts for applicable drugs covered by the agreement holder's Manufacturer Discount Program agreement and dispensed to applicable beneficiaries is subject to a civil money penalty for each such failure.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Notice of non-compliance.</E>
                                     When an agreement holder fails to make a timely payment as required under § 423.2756(b), CMS will issue to the agreement holder a notice of non-compliance with information about the violation. The agreement holder has 5 business days from the date of the notice to respond to CMS.
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Determination of the civil money penalty amounts.</E>
                                     CMS must impose a civil money penalty for each failure equal to the sum of:
                                </P>
                                <P>(1) The amount an agreement holder would have paid with respect to the applicable discount; and</P>
                                <P>(2) Twenty-five percent of such amount.</P>
                                <P>
                                    (d) 
                                    <E T="03">Notice to impose civil money penalties.</E>
                                     If CMS makes a determination to impose a civil money penalty as set forth in paragraph (c) of this section, CMS will send to the agreement holder a written notice of such determination that includes all of the following:
                                </P>
                                <P>(1) A description of the basis for the determination.</P>
                                <P>(2) The basis for the penalty.</P>
                                <P>(3) The amount of the penalty.</P>
                                <P>(4) The date the penalty is due.</P>
                                <P>(5) The agreement holder's right to a hearing as set forth in paragraph (e) of this section.</P>
                                <P>(6) Information about where to file the request for a hearing.</P>
                                <P>
                                    (e) 
                                    <E T="03">Appeal procedures for civil money penalties.</E>
                                     An agreement holder has a right to a hearing following a decision by CMS to impose a civil money penalty according to the administrative appeal process and procedures established in subpart T of this part.
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Collection.</E>
                                     (1) CMS may not collect a civil money penalty until the affected party (as defined in § 423.1002) has received notice and the opportunity for a hearing under section 1128A(c)(2) of the Act.
                                </P>
                                <P>(2) An agreement holder that has received from CMS a notice of determination to impose a civil money penalty must pay such civil money penalty in full within 60 calendar days of the date of the CMS notice of determination, except as provided in paragraph (f)(3) of this section.</P>
                                <P>(3) If the agreement holder requests a hearing to appeal in accordance with subpart T of this part, the civil money penalty is due, as applicable, once the administrative process specified in subpart T has concluded.</P>
                                <P>(4) CMS will initiate the collection of a civil money penalty owed by an agreement holder either following the expiration of 60 days from the date of the CMS notice of determination to impose a civil money penalty, or if later, the conclusion of the administrative process specified in subpart T of this part, as applicable.</P>
                                <P>
                                    (g) 
                                    <E T="03">Other applicable provisions.</E>
                                     The provisions of section 1128A of the Act (except subsections (a) and (b) of section 1128A of the Act) apply to civil money penalties under this section to the same extent that they apply to a civil money penalty or procedures under section 1128A of the Act.
                                </P>
                                <P>
                                    (h) 
                                    <E T="03">Bankruptcy.</E>
                                     In the event an agreement holder declares bankruptcy, as described in title 11 of the United States Code, and as a result of such bankruptcy, fails to pay the total sum of the civil money penalties imposed, the government reserves the right to file a proof-of-claim and take any other action under bankruptcy law, as appropriate, to attempt to recover such unpaid amounts and any civil money penalties imposed by CMS under this part.
                                </P>
                            </SECTION>
                        </SUBPART>
                    </REGTEXT>
                    <SIG>
                        <NAME>Robert F. Kennedy, Jr.,</NAME>
                        <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-06600 Filed 4-2-26; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
</FEDREG>
