{"description":"Documents matching 'intended ensure data providers make'","count":10000,"total_pages":50,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=intended+ensure+data+providers+make&format=json&page=2","results":[{"title":"National Plan and Provider Enumeration System (NPPES) Data Changes","type":"Notice","abstract":"This notice provides information on changes to a data element collected by the National Plan and Provider Enumeration System (NPPES) when a provider applies for a National Provider Identifier (NPI), which changes are made pursuant to provisions of the January 20, 2025, Executive Order, 14168 (90 FR 8615). This notice also provides an explanation of the nature and rationale for the changes, and their effect on public-facing data available in NPPES downloadable files and the query-only database on the internet.","document_number":"2025-14478","html_url":"https://www.federalregister.gov/documents/2025/07/31/2025-14478/national-plan-and-provider-enumeration-system-nppes-data-changes","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-07-31/pdf/2025-14478.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-14478.pdf?1753879512","publication_date":"2025-07-31","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Office of the Secretary"}],"excerpts":"realize that, under our approach subsequent to the March 2024 notice, <span class=\"match\">providers</span> may have submitted information pertaining to this <span class=\"match\">data</span> element to the NPPES; this notice <span class=\"match\">makes</span> <span class=\"match\">providers</span> aware how that <span class=\"match\">data</span> will be treated going forward. In this section, we discuss our prospective approach to the <span class=\"match\">data</span> element, how the previously collected <span class=\"match\">data</span> will be stored and disseminated, and <span class=\"match\">providers</span>' options for updating <span class=\"match\">data</span> elements previously submitted to the <span class=\"match\">provider</span> enumeration system. \n The <span class=\"match\">data</span> element relevant to this notice is listed in Table 1, along with"},{"title":"Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program; Delete, Delete, Delete","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopted a Further Notice of Proposed Rulemaking (FNPRM) that seeks comment on eliminating outdated requirements and ways to enhance the efficiency of the Broadband Data Collection (BDC) while ensuring that the Commission continues to receive accurate, granular data. Building off the infrastructure data-based coverage restoration process established by the Commission in 2024, the FNPRM seeks comment on several approaches suggested by commenters to simplify, streamline, or otherwise reduce burdens on this coverage restoration process. The FNPRM seeks comment on several ways to simplify the collection of fixed and fixed wireless biannual submissions, specifically on: (1) either allowing providers to indicate certain fixed broadband availability data have been \"grandfathered\" or else simply eliminating the collection of these data; (2) eliminating the requirement that a provider report fixed broadband availability data at speeds below 25/3 Mbps as part of its biannual submission; (3) revising the Commission's rules to eliminate the requirement for providers to use and disclose maximum buffer size data in their BDC biannual submissions; and (4) revising the Commission's rules to relax the 7 meter antenna height requirement that fixed wireless providers must use when modeling their coverage. In addition, the FNPRM seeks comment on ending legacy data collections for mobile service, specifically the collection of 3G mobile broadband availability data and mobile voice data as part of a provider's biannual submission, including potential impacts on reporting for Alaska and on relevant USF programs, respectively. Furthermore, the FNPRM seeks comment on current data retention practices to develop a set of best practices instead of adopting any substantive rule. The FNPRM seeks comment on several potential challenge process improvements, specifically on: (1) allowing service providers to presumptively rebut certain types of fixed challenges with infrastructure data and on requiring infrastructure data in response to certain types of fixed challenges; (2) various options for simplifying and reducing the provider response periods for the fixed challenge process; (3) streamlining the mobile challenge process by automatically removing from the National Broadband Map (NBM) all challenged areas that are conceded or upheld; and (4) relaxing or removing some current mobile crowdsourced data requirements to encourage the submission of additional data. The FNPRM seeks comment on mobile verification and audit process improvements. The FNPRM also seeks comment on improvements to the collection of mobile crowdsourced data and the use of drone data. Lastly, the FNPRM seeks comment on revising the Commission's rules to expressly provide that subscription data, the geographic coordinates of mobile or fixed wireless base stations, mobile or fixed wireless link budget parameter rationales, and any infrastructure data submitted in response to a verification request or audit will be always treated as confidential.","document_number":"2026-12767","html_url":"https://www.federalregister.gov/documents/2026/06/24/2026-12767/establishing-the-digital-opportunity-data-collection-modernizing-the-fcc-form-477-data-program","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12767.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12767.pdf?1782218725","publication_date":"2026-06-24","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"wireless biannual submissions, specifically on: (1) either allowing <span class=\"match\">providers</span> to indicate certain fixed broadband availability <span class=\"match\">data</span> have been “grandfathered” or else simply eliminating the collection of these <span class=\"match\">data</span>; (2) eliminating the requirement that a <span class=\"match\">provider</span> report fixed broadband availability <span class=\"match\">data</span> at speeds below 25/3 Mbps as part of its biannual submission; (3) revising the Commission's rules to eliminate the requirement for <span class=\"match\">providers</span> to use and disclose maximum buffer size <span class=\"match\">data</span> in their BDC biannual submissions; and (4) revising the Commission's"},{"title":"Notice of Public Data Asset Release Under the Open, Public, Electronic, and Necessary (OPEN) Government Data Act","type":"Notice","abstract":"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.","document_number":"2026-06618","html_url":"https://www.federalregister.gov/documents/2026/04/06/2026-06618/notice-of-public-data-asset-release-under-the-open-public-electronic-and-necessary-open-government","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-06/pdf/2026-06618.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-06618.pdf?1775160907","publication_date":"2026-04-06","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Centers for Medicare & Medicaid Services","name":"Centers for Medicare & Medicaid Services","id":45,"url":"https://www.federalregister.gov/agencies/centers-for-medicare-medicaid-services","json_url":"https://www.federalregister.gov/api/v1/agencies/45","parent_id":221,"slug":"centers-for-medicare-medicaid-services"}],"excerpts":"disclosure of Federal <span class=\"match\">data</span>. \n CMS has made available the following public <span class=\"match\">data</span> assets with utilization and payment <span class=\"match\">data</span> aggregated by <span class=\"match\">provider</span> and service: \n • Original Medicare Physician &amp; Other Practitioners—By <span class=\"match\">Provider</span> and Service \n • Original Medicare Inpatient Hospitals—By <span class=\"match\">Provider</span> and Service \n • Original Medicare Outpatient Hospitals—By <span class=\"match\">Provider</span> and Service \n \n • Medicare Part D Prescribers—By <span class=\"match\">Provider</span> and Drug\n \n \n • Original Medicare Durable Medical Equipment, Devices and Supplies (DMEPOS)—By Referring <span class=\"match\">Provider</span> and Service \n • Original"},{"title":"Request for Information Regarding Community Banks' Engagement With Core Service Providers and Other Essential Third-Party Service Providers","type":"Notice","abstract":"The OCC is issuing a request for information (RFI) on community bank engagement with their core service providers and other essential third-party service providers. The RFI seeks to better understand how challenges community banks face with such service providers affect these banks' abilities to remain competitive in a rapidly evolving marketplace, as well as what actions the OCC can take to address any of these challenges.","document_number":"2025-21333","html_url":"https://www.federalregister.gov/documents/2025/11/28/2025-21333/request-for-information-regarding-community-banks-engagement-with-core-service-providers-and-other","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-11-28/pdf/2025-21333.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-21333.pdf?1764164713","publication_date":"2025-11-28","agencies":[{"raw_name":"DEPARTMENT OF THE TREASURY","name":"Treasury Department","id":497,"url":"https://www.federalregister.gov/agencies/treasury-department","json_url":"https://www.federalregister.gov/api/v1/agencies/497","parent_id":null,"slug":"treasury-department"},{"raw_name":"Office of the Comptroller of the Currency","name":"Comptroller of the Currency","id":80,"url":"https://www.federalregister.gov/agencies/comptroller-of-the-currency","json_url":"https://www.federalregister.gov/api/v1/agencies/80","parent_id":497,"slug":"comptroller-of-the-currency"}],"excerpts":"innovative solutions offered or marketed by core service <span class=\"match\">providers</span> and other essential third-party service <span class=\"match\">providers</span>, or otherwise achieving visibility into such solutions? How do community banks <span class=\"match\">ensure</span> that the innovative solutions offered by these service <span class=\"match\">providers</span> truly meet their operational and strategic needs? \n 5. What challenges do community banks face in <span class=\"match\">ensuring</span> the availability and quality of post-implementation support from core service <span class=\"match\">providers</span> and other essential third-party service <span class=\"match\">providers</span>? \n 6. What challenges do community banks face in"},{"title":"Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls)","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes steps to strengthen its robocall mitigation framework by enhancing Know-Your-Upstream-Provider (KYUP) requirements, improving oversight of voice service providers by the STIR/SHAKEN Governance Authority, raising caller ID attestation standards, and closing implementation gaps in STIR/SHAKEN implementation. Specifically, the Commission proposes establishing baseline KYUP information-collection, compliance review, verification, monitoring, and responsive-action requirements to ensure providers can identify and cut off bad-actor upstream providers. The Commission also proposes measures to expand the Governance Authority's vetting, enforcement, and reporting responsibilities to prevent misuse of STIR/SHAKEN certificates and to remove noncompliant providers from the authentication ecosystem. The Commission further proposes clarifying and strengthening STIR/SHAKEN attestation rules, including codifying attestation levels, defining improper attestations, and specifying permissible mechanisms for verifying number-to-customer associations. Additionally, the Commission proposes and seeks comment on additional steps to close caller ID authentication gaps, such as refining provider definitions, reconsidering exemptions, requiring providers serving end users to assign STIR/SHAKEN attestations, and ensuring calls maintain authentication information. The Commission also seeks comment on special circumstances, including addressing issues with foreign- originated calls.","document_number":"2026-13874","html_url":"https://www.federalregister.gov/documents/2026/07/09/2026-13874/enhancing-know-your-upstream-provider-requirements-and-strengthening-stirshaken-call-authentication","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-09/pdf/2026-13874.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13874.pdf?1783514714","publication_date":"2026-07-09","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"another voice service <span class=\"match\">provider</span> has refused or discontinued service to the upstream <span class=\"match\">provider</span>. \n We believe that this is the basic amount of information necessary for a <span class=\"match\">provider</span> to be able to know their upstream <span class=\"match\">providers</span>. We also believe this information will help <span class=\"match\">providers</span> determine if an upstream <span class=\"match\">provider</span> is a foreign entity. Are these views correct? Is there additional information we should require <span class=\"match\">providers</span> to obtain? For instance, should we require that <span class=\"match\">providers</span> obtain photos of certain individuals the upstream <span class=\"match\">provider</span> identifies with their"},{"title":"Required Rulemaking on Personal Financial Data Rights","type":"Rule","abstract":"The Consumer Financial Protection Bureau (CFPB) is issuing a final rule to carry out the personal financial data rights established by the Consumer Financial Protection Act of 2010 (CFPA). The final rule requires banks, credit unions, and other financial service providers to make consumers' data available upon request to consumers and authorized third parties in a secure and reliable manner; defines obligations for third parties accessing consumers' data, including important privacy protections; and promotes fair, open, and inclusive industry standards.","document_number":"2024-25079","html_url":"https://www.federalregister.gov/documents/2024/11/18/2024-25079/required-rulemaking-on-personal-financial-data-rights","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-11-18/pdf/2024-25079.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-25079.pdf?1731678320","publication_date":"2024-11-18","agencies":[{"raw_name":"Consumer Financial Protection Bureau","name":"Consumer Financial Protection Bureau","id":573,"url":"https://www.federalregister.gov/agencies/consumer-financial-protection-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/573","parent_id":null,"slug":"consumer-financial-protection-bureau"}],"excerpts":"leverage <span class=\"match\">data</span> <span class=\"match\">providers</span>' existing capabilities. Clarifying the scope of the <span class=\"match\">data</span> access right will also promote consistency in the <span class=\"match\">data</span> made available to consumers, reduce costs of arranging for access to such <span class=\"match\">data</span>, and focus the development of technical standards around such <span class=\"match\">data</span>. \n Access Requirements \n \n The final rule generally requires a <span class=\"match\">data</span> <span class=\"match\">provider</span> to <span class=\"match\">make</span> covered <span class=\"match\">data</span> available to consumers and authorized third parties upon request. The rule includes a number of functional requirements <span class=\"match\">intended</span> to <span class=\"match\">ensure</span> <span class=\"match\">data</span> <span class=\"match\">providers</span> <span class=\"match\">make</span> covered <span class=\"match\">data</span> available"},{"title":"Use of Electronic Payroll Data To Improve Program Administration","type":"Rule","abstract":"Section 824 of the Bipartisan Budget Act of 2015 (BBA) authorizes the Commissioner of Social Security to enter into information exchanges with payroll data providers to obtain wage and employment information. We use wage and employment information to administer the Old-Age, Survivors, and Disability Insurance (OASDI) disability and Supplemental Security Income (SSI) programs under titles II and XVI of the Social Security Act (Act). We are updating our rules pursuant to the BBA, which requires us to prescribe, by regulation, procedures for implementing the access to and use of the information held by payroll data providers. We expect this final rule will support proper use of information exchanges with payroll data providers that will help us administer our programs more efficiently, improve our customers' experience, and prevent improper payments under titles II and XVI of the Act, which can otherwise occur when we do not receive timely and accurate wage and employment information.","document_number":"2024-30593","html_url":"https://www.federalregister.gov/documents/2024/12/31/2024-30593/use-of-electronic-payroll-data-to-improve-program-administration","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-12-31/pdf/2024-30593.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-30593.pdf?1735566310","publication_date":"2024-12-31","agencies":[{"raw_name":"Social Security Administration","name":"Social Security Administration","id":470,"url":"https://www.federalregister.gov/agencies/social-security-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/470","parent_id":null,"slug":"social-security-administration"}],"excerpts":"of the payroll <span class=\"match\">data</span> <span class=\"match\">provider</span> or the employers that report to the payroll <span class=\"match\">data</span> <span class=\"match\">provider</span>. It is up to the individual to correct their personal records with entities outside of SSA. Our Notice of Planned Action (NOPA) and Notice of Proposed Decision will provide contact information for individuals to directly dispute the information with the payroll <span class=\"match\">data</span> <span class=\"match\">provider</span> and request that the payroll <span class=\"match\">data</span> <span class=\"match\">provider</span> flag the <span class=\"match\">data</span> as disputed. If the payroll <span class=\"match\">data</span> <span class=\"match\">provider</span> has flagged <span class=\"match\">data</span> because it is being disputed, we will not post the <span class=\"match\">data</span> to our claims records"},{"title":"Medicare Program; Request for Renewal of Deeming Authority of the National Committee for Quality Assurance (NCQA) for Medicare Advantage Health Maintenance Organizations and Preferred Provider Organizations","type":"Notice","abstract":"This notice announces that the Centers for Medicare & Medicaid Services is considering granting approval of the National Committee for Quality Assurance's renewal application for Medicare Advantage \"deeming authority\" of Health Maintenance Organizations and Preferred Provider Organizations to continue participation in the Medicare program.","document_number":"2026-04593","html_url":"https://www.federalregister.gov/documents/2026/03/10/2026-04593/medicare-program-request-for-renewal-of-deeming-authority-of-the-national-committee-for-quality","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-03-10/pdf/2026-04593.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-04593.pdf?1773060307","publication_date":"2026-03-10","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Centers for Medicare & Medicaid Services","name":"Centers for Medicare & Medicaid Services","id":45,"url":"https://www.federalregister.gov/agencies/centers-for-medicare-medicaid-services","json_url":"https://www.federalregister.gov/api/v1/agencies/45","parent_id":221,"slug":"centers-for-medicare-medicaid-services"}],"excerpts":"stringent as Medicare requirements for MAOs. MAOs that are licensed as health maintenance organizations (HMOs) or preferred <span class=\"match\">provider</span> organizations (PPOs) and are accredited by an approved AO may receive, at their request, “deemed” status for CMS requirements for the deemable areas. These areas include Quality Improvement, Anti-Discrimination, Confidentiality and Accuracy of Enrollee Records, Information on Advance Directives, and <span class=\"match\">Provider</span> Participation Rules. \n At this time, CMS does not recognize accreditation of the following areas: Access to Services"},{"title":"Ensuring Lawful Regulation; Reducing Regulation and Controlling Regulatory Costs","type":"Proposed Rule","abstract":"As part of its implementation of Executive orders issued by the President, including Executive Order 14219, \"Ensuring Lawful Governance and Implementation of the President's `Department of Government Efficiency' Deregulatory Agenda,\" issued on February 19, 2025, and Executive Order 14192, \"Unleashing Prosperity through Deregulation,\" issued on January 31, 2025, the Department of Transportation (DOT) seeks comments and information to assist DOT in identifying existing regulations, guidance, paperwork requirements, and other regulatory obligations that can be modified or repealed, consistent with law, to ensure that DOT administrative actions do not undermine the national interest and that DOT achieves meaningful burden reduction while continuing to meet statutory obligations and ensure the safety of the U.S. transportation system.","document_number":"2025-05557","html_url":"https://www.federalregister.gov/documents/2025/04/03/2025-05557/ensuring-lawful-regulation-reducing-regulation-and-controlling-regulatory-costs","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-04-03/pdf/2025-05557.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-05557.pdf?1743597907","publication_date":"2025-04-03","agencies":[{"raw_name":"DEPARTMENT OF TRANSPORTATION","name":"Transportation Department","id":492,"url":"https://www.federalregister.gov/agencies/transportation-department","json_url":"https://www.federalregister.gov/api/v1/agencies/492","parent_id":null,"slug":"transportation-department"}],"excerpts":"accurate, objective information and <span class=\"match\">data</span> about the costs, burdens, and benefits of existing regulations, guidance, and reporting requirements? Are there existing sources of <span class=\"match\">data</span> DOT can use to evaluate the post-promulgation effects of regulations, guidance, or reporting requirements over time? DOT invites interested parties to provide <span class=\"match\">data</span> that may be in their possession that documents the costs, burdens, and benefits of existing requirements. \n (4) Are there regulations, guidance, or reporting requirements that simply <span class=\"match\">make</span> no sense or have become unnecessary"},{"title":"Resilient Networks; Concerning Disruptions to Communications","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) modernizes the Disaster Information Reporting System (DIRS) to reduce reporting burdens on stakeholders and ensure that the information being collected is useful for disaster response. Our modernization allows manual filers to submit a single, dynamic form instead of multiple worksheets, and enables them to use a \"one-click\" option to easily indicate there is no change from the previous day's report. Further, unnecessary fields and worksheets will be eliminated to ensure that DIRS is collecting the information that is most important for emergency response. This modernization also eliminates the requirement for service providers to file a DIRS final report within 24 hours of DIRS' deactivation, and exempts non-facilities-based providers from DIRS reporting. This document also recognizes the emergence of public safety voice and broadband networks and the critical connectivity they provide to public safety stakeholders by requiring providers of these services to submit DIRS reports on the status of their public safety network infrastructure. Finally, we augment providers' ability to voluntarily submit geospatial information on infrastructure affected by disasters. Together, these changes provide public safety officials with the additional information they need, while also making it easier for service providers to satisfy their reporting obligations.","document_number":"2026-13155","html_url":"https://www.federalregister.gov/documents/2026/06/30/2026-13155/resilient-networks-concerning-disruptions-to-communications","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-30/pdf/2026-13155.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13155.pdf?1782737115","publication_date":"2026-06-30","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"this will provide an incremental time savings to those <span class=\"match\">providers</span> that elect not to complete this field in DIRS, it will enable <span class=\"match\">providers</span> to continue to share this information. ACA Connects supports our rationale for this conclusion and no commenters object to proceeding in this manner.\n \n \n <span class=\"match\">Make</span> Broadband <span class=\"match\">Data</span> User Fields Voluntary. \n We <span class=\"match\">make</span> the collection of broadband access user information voluntary, rather than mandatory, for all DIRS filers except fixed and mobile broadband <span class=\"match\">providers</span> that are stage 2 recipients of the Uniendo a Puerto Rico"},{"title":"National Plan and Provider Enumeration System (NPPES) Data Changes","type":"Notice","abstract":"This notice provides information on changes to data elements that providers are required to submit to the National Plan and Provider Enumeration System (NPPES) to obtain and maintain a National Provider Identifier (NPI). The changes to the required data elements affect the data that is made available to the public from NPPES in downloadable files and in a query-only database on the internet.","document_number":"2024-04517","html_url":"https://www.federalregister.gov/documents/2024/03/04/2024-04517/national-plan-and-provider-enumeration-system-nppes-data-changes","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-03-04/pdf/2024-04517.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-04517.pdf?1709300743","publication_date":"2024-03-04","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Centers for Medicare & Medicaid Services","name":"Centers for Medicare & Medicaid Services","id":45,"url":"https://www.federalregister.gov/agencies/centers-for-medicare-medicaid-services","json_url":"https://www.federalregister.gov/api/v1/agencies/45","parent_id":221,"slug":"centers-for-medicare-medicaid-services"}],"excerpts":"health care <span class=\"match\">provider</span> <span class=\"match\">data</span> elements addressed by this notice: <span class=\"match\">provider</span> first line address location, <span class=\"match\">provider</span> second line address location, and <span class=\"match\">provider</span> gender code. Thirty days after publication of this notice in the \n Federal Register \n , the NPPES system, NPPES Registry, paper form, and associated <span class=\"match\">data</span> files will be updated to begin collecting and disseminating for these health care <span class=\"match\">provider</span> <span class=\"match\">data</span> elements: (1) amend the description of the <span class=\"match\">provider</span> first line location address and second line location address <span class=\"match\">data</span> elements to permit a <span class=\"match\">provider</span> that does"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules that would help ensure that emerging Next Generation 911 (NG911) networks are reliable and interoperable. NG911 is replacing legacy 911 technology across the country with Internet Protocol (IP)-based infrastructure that will support new 911 capabilities, including text, video, and data. However, for NG911 to be fully effective, NG911 networks must safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. When the Commission first adopted 911 reliability rules in 2013, the transition to NG911 was in its very early stages. Since then, many state and local 911 Authorities have made significant progress in deploying NG911 capabilities in their jurisdictions. This Further Notice of Proposed Rulemaking (FNPRM) is the next step in fulfilling the Commission's commitment to facilitate the NG911 transition and to ensure that the transition does not inadvertently create vulnerabilities in the nation's critical public safety networks. The FNPRM proposes to update the definition of \"covered 911 service provider\" in the Commission's existing 911 reliability rules to ensure that the rules apply to service providers that control or operate critical pathways and components in NG911 networks. It also proposes to update the reliability standards for providers of critical NG911 functions to ensure the reliable delivery of 911 traffic to NG911 delivery points, and proposes to establish NG911 interoperability requirements for interstate transfer of 911 traffic between Emergency Services IP Networks (ESInets). In addition, the FNPRM proposes to modify the certification and oversight mechanisms in the current 911 reliability rules to improve reliability and interoperability in NG911 systems while minimizing burdens on service providers, and proposes to empower state and local 911 Authorities to obtain reliability and interoperability certifications directly from covered 911 service providers.","document_number":"2025-09279","html_url":"https://www.federalregister.gov/documents/2025/06/04/2025-09279/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-04/pdf/2025-09279.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-09279.pdf?1748954707","publication_date":"2025-06-04","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"facilitate the NG911 transition and to <span class=\"match\">ensure</span> that the transition does not inadvertently create vulnerabilities in the nation's critical public safety networks. The FNPRM proposes to update the definition of “covered 911 service <span class=\"match\">provider</span>” in the Commission's existing 911 reliability rules to <span class=\"match\">ensure</span> that the rules apply to service <span class=\"match\">providers</span> that control or operate critical pathways and components in NG911 networks. It also proposes to update the reliability standards for <span class=\"match\">providers</span> of critical NG911 functions to <span class=\"match\">ensure</span> the reliable delivery of 911 traffic"},{"title":"Advanced Methods To Target and Eliminate Robocalls","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes steps to improve the availability and accuracy of caller identification information transmitted to consumers to enable them to better understand who is calling and decide whether to answer calls. Specifically, the Commission proposes to enhance the effectiveness of STIR/SHAKEN by requiring terminating providers to transmit verified caller name or other caller identity information for presentation on a consumer's handset whenever they transmit an indication that a call has received an A-level attestation. It also seeks comment on requiring providers to use Rich Call Data (RCD) to transmit verified caller name on IP networks, whether to permit or require use of other solutions, and an alternative option to require that providers implement RCD in their IP networks for all calls. The Commission further proposes to require voice service providers to implement measures to ensure that consumers know which calls originate from outside of the United States and to prohibit spoofing of United States telephone numbers for calls that originate from outside of the United States. Finally, the Commission seeks comment on whether some of its calling-related rules can be simplified, streamlined, or eliminated, perhaps because they are outdated or have not been enforced for a substantial amount of time.","document_number":"2025-22063","html_url":"https://www.federalregister.gov/documents/2025/12/05/2025-22063/advanced-methods-to-target-and-eliminate-robocalls","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-05/pdf/2025-22063.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-22063.pdf?1764855925","publication_date":"2025-12-05","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"adopt to determine whether a <span class=\"match\">provider</span> has implemented RCD? Would any potential measure be different for resellers, originating facilities-based <span class=\"match\">providers</span>, intermediate <span class=\"match\">providers</span>, or terminating <span class=\"match\">providers</span>? If so, why? For example, would an intermediate <span class=\"match\">provider</span> properly be considered to have implemented RCD if it transmits to subsequent <span class=\"match\">providers</span> in the call path the RCD information it receives from the <span class=\"match\">provider</span> immediately before it in the call path? \n 41. If we do adopt an implementation mandate, how quickly can <span class=\"match\">providers</span> implement RCD throughout their"},{"title":"Calendar Year 2027 Home Health Prospective Payment System (HH PPS) Rate Update; Requirements for the HH Quality Reporting Program and the Expanded HH Value-Based Purchasing Model; Medicare Provider Enrollment, Durable Medical Equipment (DME), and DME, Prosthetics, Orthotics, and Supplies (DMEPOS) Policies","type":"Proposed Rule","abstract":"This proposed rule would set forth routine updates to the Medicare home health payment rates in accordance with existing statutory and regulatory requirements. In addition, this proposed rule discusses the behavior adjustment and proposes a temporary behavior adjustment and proposes to recalibrate the case-mix weights and update the functional impairment levels; comorbidity subgroups; and low- utilization payment adjustment (LUPA) thresholds for CY 2027. Additionally, this proposed rule discusses the provision of home health palliative care services and includes a request for information (RFI) on a home health specific wage index. This rule would also propose changes to the Home Health Quality Reporting Program (HH QRP) and summarizes potential initiatives to improve alignment between the HH QRP and expanded Home Health Value Based Purchasing (HHVBP) Model. Lastly, the rule would--clarify the application of the DMEPOS face-to- face encounter requirements for the replacement of DMEPOS items; make changes to the provider and supplier enrollment requirements; make changes regarding DME benefit expansion for infusion pumps and drugs; and discuss collection of information requirement changes regarding the DMEPOS Competitive Bidding Program (CBP) country of origin.","document_number":"2026-13602","html_url":"https://www.federalregister.gov/documents/2026/07/06/2026-13602/calendar-year-2027-home-health-prospective-payment-system-hh-pps-rate-update-requirements-for-the-hh","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-06/pdf/2026-13602.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13602.pdf?1782936912","publication_date":"2026-07-06","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Centers for Medicare & Medicaid Services","name":"Centers for Medicare & Medicaid Services","id":45,"url":"https://www.federalregister.gov/agencies/centers-for-medicare-medicaid-services","json_url":"https://www.federalregister.gov/api/v1/agencies/45","parent_id":221,"slug":"centers-for-medicare-medicaid-services"}],"excerpts":"utilization <span class=\"match\">data</span> available at the time of annual rulemaking. Annual recalibration of the PDGM case-mix weights <span class=\"match\">ensures</span> that the case-mix weights reflect, as accurately as possible, current home health resource use and changes in utilization patterns. To generate the proposed recalibrated CY 2027 case-mix weights, we used CY 2025 home health claims <span class=\"match\">data</span> with linked OASIS <span class=\"match\">data</span> (as of March 15, 2026). These <span class=\"match\">data</span> are the most current and complete <span class=\"match\">data</span> available at the time of rulemaking. We believe that recalibrating the case-mix weights using <span class=\"match\">data</span> from CY"},{"title":"Incarcerated People's Communication Services; Implementation of the Martha Wright-Reed Act; Rates for Interstate Inmate Calling Services","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) seeks additional comment and data from stakeholders on adopting permanent audio and video IPCS rate caps and on whether and how the Commission should refine its IPCS data collections going forward to provide the data needed to ensure rate caps are just and reasonable and fairly compensate IPCS providers. It also seeks comment on how and when the Commission should structure a permanent rate additive to account for the recovery of correctional facility costs incurred in making IPCS available, including an additive that potentially varies by facility type and size. Finally, it proposes to retain the prohibition on ancillary service charges previously adopted by the Commission and seeks further comment on this proposal. In the alternative, it seeks comment on a request to reinstate automated payment fees and third-party financial transaction fees as permissible ancillary service charges.","document_number":"2025-22130","html_url":"https://www.federalregister.gov/documents/2025/12/05/2025-22130/incarcerated-peoples-communication-services-implementation-of-the-martha-wright-reed-act-rates-for","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-05/pdf/2025-22130.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-22130.pdf?1764855937","publication_date":"2025-12-05","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"public, including any <span class=\"match\">data</span> asset, or part thereof, subject to disclosure under the Freedom of Information Act (FOIA).” A “<span class=\"match\">data</span> asset” is “a collection of <span class=\"match\">data</span> elements or <span class=\"match\">data</span> sets that may be grouped together,” and “<span class=\"match\">data</span>” is “recorded information, regardless of form or the media on which the <span class=\"match\">data</span> is recorded.” We delegate authority to the Wireline Competition Bureau, in consultation with the agency's Chief <span class=\"match\">Data</span> and Analytics Officer and after seeking public comment to the extent it deems appropriate, to determine whether any <span class=\"match\">data</span> assets maintained"},{"title":"Lifeline and Link Up Reform and Modernization; Bridging the Digital Divide for Low-Income Consumers; Telecommunications Carriers Eligible for Universal Service Support; Affordable Connectivity Program; Emergency Broadband Benefit Program","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) seeks to ensure that Lifeline services are used to benefit and support eligible low-income Americans, that the program's funding is protected from waste, fraud, and abuse, and that service providers are in compliance with Commission rules. The Commission also seeks to update and streamline Lifeline and related rules.","document_number":"2026-06531","html_url":"https://www.federalregister.gov/documents/2026/04/03/2026-06531/lifeline-and-link-up-reform-and-modernization-bridging-the-digital-divide-for-low-income-consumers","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-03/pdf/2026-06531.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-06531.pdf?1775133915","publication_date":"2026-04-03","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"plus a 15-day cure period. Lifeline subscribers are deemed to have “used” their service if they have completed an outbound call; used <span class=\"match\">data</span>; purchased minutes or <span class=\"match\">data</span> from their participating <span class=\"match\">provider</span>; answered an incoming call from anyone who is not their <span class=\"match\">provider</span> or <span class=\"match\">provider's</span> representative; responded to direct contact from their <span class=\"match\">provider</span> confirming intent to receive Lifeline service; or sent a text message. <span class=\"match\">Providers</span> are responsible for tracking subscriber usage and retaining appropriate usage documentation to demonstrate compliance with the usage"},{"title":"Applications for New Awards; Technical Assistance on State Data Collection-Technical Assistance on State Data Collection-National Technical Assistance Center To Improve State Capacity To Collect, Report, Analyze, and Use Accurate IDEA Part B and Part C Fiscal Data","type":"Notice","abstract":"The Department of Education (Department) is issuing a notice inviting applications for new awards for fiscal year (FY) 2025 for a Technical Assistance on State Data Collection--Technical Assistance on State Data Collection--National Technical Assistance Center to Improve State Capacity to Collect, Report, Analyze, and Use Accurate IDEA Part B and Part C Fiscal Data.","document_number":"2025-11607","html_url":"https://www.federalregister.gov/documents/2025/06/25/2025-11607/applications-for-new-awards-technical-assistance-on-state-data-collection-technical-assistance-on","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-25/pdf/2025-11607.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-11607.pdf?1750769111","publication_date":"2025-06-25","agencies":[{"raw_name":"DEPARTMENT OF EDUCATION","name":"Education Department","id":126,"url":"https://www.federalregister.gov/agencies/education-department","json_url":"https://www.federalregister.gov/api/v1/agencies/126","parent_id":null,"slug":"education-department"}],"excerpts":"proposes to expand the knowledge base for States on— \n (A) Fiscal <span class=\"match\">data</span> management and <span class=\"match\">data</span> system integration needed for IDEA Part B and Part C <span class=\"match\">data</span> collection and reporting; \n (B) IDEA fiscal <span class=\"match\">data</span> validation that leads to improvements in the validity and reliability of fiscal <span class=\"match\">data</span> required by IDEA; and \n \n (C) Effective ways to communicate fiscal <span class=\"match\">data</span> to local consumers (\n e.g., \n parents, LEAs, including public charter schools that are LEAs, EIS programs or <span class=\"match\">providers</span>, the general public);\n \n \n (ii) Its proposed approach to universal, general TA"},{"title":"Personal Financial Data Rights Reconsideration","type":"Proposed Rule","abstract":"The Consumer Financial Protection Bureau (CFPB or Bureau) is seeking comments and data to inform its consideration of four issues related to implementation of section 1033 of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act). These issues are: the proper understanding of who can serve as a \"representative\" making a request on behalf of the consumer; the optimal approach to the assessment of fees to defray the costs incurred by a \"covered person\" in responding to a customer driven request; the threat and cost-benefit pictures for data security associated with section 1033 compliance; and the threat picture for data privacy associated with section 1033 compliance.","document_number":"2025-16139","html_url":"https://www.federalregister.gov/documents/2025/08/22/2025-16139/personal-financial-data-rights-reconsideration","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-08-22/pdf/2025-16139.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-16139.pdf?1755780335","publication_date":"2025-08-22","agencies":[{"raw_name":"Consumer Financial Protection Bureau","name":"Consumer Financial Protection Bureau","id":573,"url":"https://www.federalregister.gov/agencies/consumer-financial-protection-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/573","parent_id":null,"slug":"consumer-financial-protection-bureau"}],"excerpts":"transmission of personal financial <span class=\"match\">data</span> underscore the need to <span class=\"match\">ensure</span> that entities authorized to access that information have appropriate safeguards in place. \n The PFDR Rule attempted to address information security in several ways. It prohibited <span class=\"match\">data</span> <span class=\"match\">providers</span> from relying on a third party's use of screen scraping to access the developer interface required by the rule and discouraging the use of screen scraping by third parties when more secure methods of <span class=\"match\">data</span> access were available; required <span class=\"match\">data</span> <span class=\"match\">providers</span> and third parties to adhere to the applicable"},{"title":"Health Data, Technology, and Interoperability: ASTP/ONC Deregulatory Actions To Unleash Prosperity","type":"Proposed Rule","abstract":"This proposed rule focuses on deregulatory actions identified in HHS regulations regarding Health information technology standards, implementation specifications, and certification criteria and certification programs for health information technology, and information blocking. This proposed rule seeks to reduce burden, offer flexibility to both developers and providers, and support innovation through the removal and revisions of certain certification criteria and regulatory provisions. This proposed rule also seeks to address reported misuse and abuse of information blocking definitions and exceptions.","document_number":"2025-23896","html_url":"https://www.federalregister.gov/documents/2025/12/29/2025-23896/health-data-technology-and-interoperability-astponc-deregulatory-actions-to-unleash-prosperity","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-29/pdf/2025-23896.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-23896.pdf?1766438109","publication_date":"2025-12-29","agencies":[{"raw_name":"DEPARTMENT OF HEALTH AND HUMAN SERVICES","name":"Health and Human Services Department","id":221,"url":"https://www.federalregister.gov/agencies/health-and-human-services-department","json_url":"https://www.federalregister.gov/api/v1/agencies/221","parent_id":null,"slug":"health-and-human-services-department"},{"raw_name":"Office of the Secretary"}],"excerpts":"Final Rule (89 FR 1428), we adopted USCDI v3, which includes <span class=\"match\">data</span> elements for Sex, Sexual Orientation, and Gender Identity. To <span class=\"match\">ensure</span> consistent capture of these <span class=\"match\">data</span> elements across health IT, we made updates to the <span class=\"match\">data</span> elements in § 170.315(a)(5) to incorporate the newly adopted <span class=\"match\">data</span> elements in USCDI v3. Specifically, these same <span class=\"match\">data</span> elements were adopted as “sex” (§ 170.315(a)(5)(i)(C)), “sexual orientation” (§ 170.315(a)(5)(i)(D)), and “gender identity” (§ 170.315(a)(5)(i)(E)). To <span class=\"match\">ensure</span> consistency with our adoption of USCDI v3, we finalized"},{"title":"Call Authentication Trust Anchor","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopts rules that strengthen the Commission's caller ID authentication requirements by establishing clear practices for providers that rely on third parties to fulfill their STIR/SHAKEN implementation obligations. The rules authorize providers with a STIR/ SHAKEN implementation obligation to engage third parties to perform the technological act of digitally \"signing\" calls consistent with the requirements of the STIR/SHAKEN technical standards so long as: the provider with the implementation obligation makes the \"attestation- level\" decisions for authenticating caller ID information; and all calls are signed using the certificate of the provider with the implementation obligation--not the certificate of a third party. The rules also explicitly require all providers with a STIR/SHAKEN implementation obligation to obtain a Service Provider Code (SPC) token from the STIR/SHAKEN Policy Administrator and present that token to a STIR/SHAKEN Certificate Authority to obtain a digital certificate. Additionally, the rules include recordkeeping requirements for third- party authentication arrangements to enable the Commission to monitor compliance with and enforce Commission rules.","document_number":"2025-15809","html_url":"https://www.federalregister.gov/documents/2025/08/19/2025-15809/call-authentication-trust-anchor","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-08-19/pdf/2025-15809.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-15809.pdf?1755521150","publication_date":"2025-08-19","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"that the third party will perform on the <span class=\"match\">provider's</span> behalf and confirm that <span class=\"match\">provider</span> will: (1) <span class=\"match\">make</span> all attestation-level decisions for calls signed pursuant to the agreement, and (2) <span class=\"match\">ensure</span> that all calls will be signed using the <span class=\"match\">provider's</span> certificate. <span class=\"match\">Providers</span> may be required to submit a copy of the agreement to the Commission in connection with a review of the <span class=\"match\">provider's</span> compliance with the Commission's rules or an investigation by the Enforcement Bureau. To the extent that an agreement between a <span class=\"match\">provider</span> with the STIR/SHAKEN implementation obligation"}]}