{"description":"Documents matching 'section adopt several implementation providers utilize third-party authentication requirements'","count":605,"total_pages":31,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=section+adopt+several+implementation+providers+utilize+third-party+authentication+requirements&format=json&page=2","results":[{"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":"accurate caller ID <span class=\"match\">authentication</span>.\n \n A. Authorizing <span class=\"match\">Third-Party</span> <span class=\"match\">Authentication</span> Subject to Limitations To Prevent Abuse \n 1. Defining the Scope of <span class=\"match\">Third-Party</span> <span class=\"match\">Authentication</span> \n \n We first define “<span class=\"match\">third-party</span> <span class=\"match\">authentication</span>” for the purposes of the rules we <span class=\"match\">adopt</span> today, and also delineate the types of <span class=\"match\">providers</span> that are covered by the rules. In the \n Sixth Caller ID <span class=\"match\">Authentication</span> Further Notice \n (88 FR 29035, May 5, 2023), we sought comment on the types of <span class=\"match\">third-party</span> arrangements being used by <span class=\"match\">providers</span>, including whether <span class=\"match\">providers</span> are entering into"},{"title":"Combatting Illegal Robocalls Through FCC Numbering Policies; Implementation of TRACED Act-Knowledge of Customers by Entities With Access to Numbering Resources","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (FCC or Commission) seeks comment on whether to adopt changes to its numbering policies with respect to how assigned numbering resources are utilized, reported, and resold by service providers as part of its continuing effort to combat illegal robocalls. The Commission explores and proposes a broad array of solutions to strengthen the Commission's numbering requirements and policies, particularly as they relate to resellers that use numbering resources to engage in some of the most extensive illegal robocalling schemes.","document_number":"2026-09134","html_url":"https://www.federalregister.gov/documents/2026/05/08/2026-09134/combatting-illegal-robocalls-through-fcc-numbering-policies-implementation-of-traced-act-knowledge","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-08/pdf/2026-09134.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-09134.pdf?1778157911","publication_date":"2026-05-08","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":"propose to further extend the robocall certification <span class=\"match\">requirements</span> to \n all \n service <span class=\"match\">providers</span> that receive numbering resources directly from the North American Numbering Plan Administrator (NANPA), not just interconnected VoIP <span class=\"match\">providers</span>, and also to resellers of telephone numbers. These certification <span class=\"match\">requirements</span> should apply uniformly and not just to interconnected VoIP <span class=\"match\">providers</span> with direct access authorizations, just as many of our robocall rules themselves apply equally to all voice service <span class=\"match\">providers</span>. Further, given the role that at least some resellers"},{"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":"whether a <span class=\"match\">provider</span> has <span class=\"match\">implemented</span> 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 <span class=\"match\">implemented</span> 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 <span class=\"match\">adopt</span> an <span class=\"match\">implementation</span> mandate, how quickly can <span class=\"match\">providers</span> <span class=\"match\">implement</span> RCD throughout their IP networks"},{"title":"Medicare and Medicaid Programs; Patient Protection and Affordable Care Act; Interoperability Standards and Prior Authorization for Drugs for Medicare Advantage Organizations, Medicaid Managed Care Plans, State Medicaid Agencies, Children's Health Insurance Program (CHIP) Agencies and CHIP Managed Care Entities, and Issuers of Qualified Health Plans on the Federally-Facilitated Exchanges","type":"Proposed Rule","abstract":"These proposals are intended to improve the electronic exchange of health care data and streamline processes related to prior authorization by increasing the interoperability of systems used across the health care industry. We are proposing new requirements for Medicare Advantage (MA) organizations, state Medicaid fee-for-service (FFS) programs, state Children's Health Insurance Program (CHIP) FFS programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan (QHP) issuers on the Federally-facilitated Exchanges (FFEs), including issuers that offer small group market QHPs on the Federally-facilitated Small Business Health Options Program (FF- SHOP) Exchanges (hereinafter referred to as \"small group market QHP issuers on the FF-SHOPs\") (collectively \"impacted payers\"), to make available electronic prior authorization for drugs. We are also proposing to extend many existing interoperability requirements for the prior authorization of non-drug items and services to include prior authorizations for drugs to further reduce patient and provider burden. We are also proposing to require impacted payers to report their application programming interfaces (API) endpoints and related information for the Patient Access, Provider Directory, Provider Access, Payer-to-Payer, and Prior Authorization APIs to CMS. To help assess the impact of our policies, we are proposing to collect API usage metrics. In addition, we are proposing to apply the existing interoperability requirements to small group market QHP issuers on the FF-SHOPs as impacted payers. To improve impacted payers' ability to exchange health information while continuing CMS's drive toward interoperability, we are proposing to require certain Health Level Seven (HL7[supreg]) Fast Healthcare Interoperability Resources (FHIR[supreg]) implementation guides (IGs) that are currently recommended. In addition, HHS is proposing to adopt the HL7 FHIR base standard and certain associated specifications and IGs as the Health Insurance Portability and Accountability Act of 1996 (hereinafter referred to as \"HIPAA\") (Pub. L. 104-191, enacted Aug. 21, 1996) standards for dental, professional, and institutional \"referral certification and authorization\" transactions and \"eligibility for a health plan\" transactions associated with prior authorization. We are proposing to add a definition for \"failure to report,\" which would allow CMS to impose a civil monetary penalty (CMP) on applicable manufacturers or applicable group purchasing organizations (GPOs) if those entities fail to grant CMS timely access to documents for the purposes of an audit. Finally, ONC is using this rulemaking to propose to adopt updated versions of certain health information technology (health IT) standards and specifications for HHS use, such as CMS's interoperability requirements, to support a more robust health IT infrastructure.","document_number":"2026-07205","html_url":"https://www.federalregister.gov/documents/2026/04/14/2026-07205/medicare-and-medicaid-programs-patient-protection-and-affordable-care-act-interoperability-standards","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-14/pdf/2026-07205.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-07205.pdf?1775852111","publication_date":"2026-04-14","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"},{"raw_name":"Office of the Secretary"}],"excerpts":"appeared in the \n Federal Register \n on February 8, 2024. In that rule, we finalized <span class=\"match\">requirements</span> for impacted payers to improve the electronic exchange of health care information, not just with patients, but also with <span class=\"match\">providers</span> and other payers. We also finalized <span class=\"match\">requirements</span> for impacted payers to <span class=\"match\">implement</span> and maintain a Prior Authorization API that supports electronic prior authorization between <span class=\"match\">providers</span> and payers.\n 2 \n \n We also finalized general process <span class=\"match\">requirements</span> for prior authorization, such as requiring MA organizations, state Medicaid and"},{"title":"Improving Customer Service and Protecting Consumers Through Onshoring","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) proposes actions that would encourage and facilitate the onshoring of foreign call centers. Specifically, the Commission proposes rules and otherwise explore ways to improve customer service communications and better protect consumers' sensitive personal information by limiting use of foreign call centers and by improving standards applicable to a company's remaining foreign call center operations. It also seeks comment on extending these protections to modes of customer service communications other than calls, such as emails, texts, and on-line chats, and on ideas to deter scam and other unlawful calls made to the United States from foreign countries. Finally, it explore steps we can take to financially deter unlawful foreign-originated calls, such as bond requirements. The Commission proposes to apply these requirements to providers of telecommunications services, CMRS, interconnected VoIP service, cable television service, and DBS services, or affiliates of such providers. It also proposes to apply these requirements to the use of foreign call centers for consumer communications relating to internet access service offered by any of the foregoing providers or their affiliates and seeks comment on whether it should extend some or all of the proposed rules to providers of other types of services.","document_number":"2026-07960","html_url":"https://www.federalregister.gov/documents/2026/04/23/2026-07960/improving-customer-service-and-protecting-consumers-through-onshoring","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-23/pdf/2026-07960.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-07960.pdf?1776861922","publication_date":"2026-04-23","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":"a bond draw down? Can device-based reporting be shared with the terminating <span class=\"match\">provider</span>? If so, would terminating <span class=\"match\">providers</span> seek the bond draw from the ultimate gateway <span class=\"match\">provider</span> or intermediate <span class=\"match\">providers</span> directly, or would terminating <span class=\"match\">providers</span> file reports with the entity administering the bonds on a periodic cadence? \n Which <span class=\"match\">provider's</span> bond would be drawn upon and how could that particular <span class=\"match\">provider</span> be identified, especially if a <span class=\"match\">provider</span> other than the terminating <span class=\"match\">provider</span> were deemed the one to pay? Should the entity administering the bond draws"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability","type":"Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) adopts rules to 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 be designed to safeguard the reliability of critical components and support the interoperability needed to seamlessly transfer 911 calls and data from one network to another. The rules require entities essential to delivering emergency calls in the NG911 environment to implement common sense measures to safeguard the reliability of NG911 networks and reduce the risk of 911 outages, and require certain entities to report on their support for NG911 interoperability. The rules also eliminate unnecessary and burdensome legacy rules to increase flexibility and encourage technical innovation to make NG911 services reliable, interoperable, and accessible to all.","document_number":"2026-13998","html_url":"https://www.federalregister.gov/documents/2026/07/10/2026-13998/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-10/pdf/2026-13998.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13998.pdf?1783601118","publication_date":"2026-07-10","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":"reliability rules because <span class=\"match\">providers</span> of <span class=\"match\">third-party</span> transport and aggregation services did not meet the definition of either CSPs or OSPs.\n 172 \n \n The Commission tentatively concluded that these <span class=\"match\">providers</span> had become sufficiently crucial to the provision of NG911 service that they should be \n \n subject to the same reliability <span class=\"match\">requirements</span> as other <span class=\"match\">providers</span> of covered 911 services.\n 173 \n \n The Commission also proposed to focus reliability <span class=\"match\">requirements</span> on major transport and aggregation <span class=\"match\">providers</span> and not to extend them to smaller <span class=\"match\">providers</span> whose facilities"},{"title":"Revising Non-Over-the-Counter Firearms Transaction Requirements","type":"Proposed Rule","abstract":"Federal law permits federal firearms licensees (\"FFLs\") to transfer firearms to a person residing in the same state but who does not appear in person. These are \"non-over-the-counter\" (\"NOTC\") sales. The Bureau of Alcohol, Tobacco, Firearms, and Explosives (\"ATF\") proposes amending Department of Justice (\"Department\") regulations on NOTC sales. These proposed changes would remove restrictions limiting this option to background check-exempt transfers. The proposed rule would permit FFLs to conduct NOTC transfers while complying with background check requirements and adds remote identity proofing and electronic notices to chief law enforcement officers. These changes would provide greater flexibility for individuals lawfully purchasing firearms.","document_number":"2026-09157","html_url":"https://www.federalregister.gov/documents/2026/05/08/2026-09157/revising-non-over-the-counter-firearms-transaction-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-08/pdf/2026-09157.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-09157.pdf?1778157914","publication_date":"2026-05-08","agencies":[{"raw_name":"DEPARTMENT OF JUSTICE","name":"Justice Department","id":268,"url":"https://www.federalregister.gov/agencies/justice-department","json_url":"https://www.federalregister.gov/api/v1/agencies/268","parent_id":null,"slug":"justice-department"},{"raw_name":"Bureau of Alcohol, Tobacco, Firearms, and Explosives","name":"Alcohol, Tobacco, Firearms, and Explosives Bureau","id":19,"url":"https://www.federalregister.gov/agencies/alcohol-tobacco-firearms-and-explosives-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/19","parent_id":268,"slug":"alcohol-tobacco-firearms-and-explosives-bureau"}],"excerpts":"controls one or more <span class=\"match\">authenticators</span> bound to the person's account.\n 30 \n \n AAL1 provides basic confidence that the claimant controls an <span class=\"match\">authenticator</span> that is bound to the subscriber account. AAL1 requires only single-factor <span class=\"match\">authentication</span> using a wide range of available <span class=\"match\">authentication</span> technologies.\n 31 \n \n AAL2 provides high confidence that the claimant controls one or more <span class=\"match\">authenticators</span> bound to the subscriber account and requires proof that the claimant possesses and controls two distinct <span class=\"match\">authentication</span> factors.\n 32 \n \n <span class=\"match\">Authentication</span> at AAL3 provides"},{"title":"Administrative Simplification; Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures","type":"Rule","abstract":"This final rule implements requirements of the Administrative Simplification subtitle of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and the Patient Protection and Affordable Care Act, as amended by the Health Care and Education Reconciliation Act of 2010, enacted on March 30, 2010--collectively, the Affordable Care Act. Specifically, this final rule adopts standards for health care claims attachments transactions, which will support health care claims transactions, and a standard for electronic signatures to be used in conjunction with health care claims attachments transactions.","document_number":"2026-05676","html_url":"https://www.federalregister.gov/documents/2026/03/24/2026-05676/administrative-simplification-adoption-of-standards-for-health-care-claims-attachments-transactions","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-03-24/pdf/2026-05676.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-05676.pdf?1774037709","publication_date":"2026-03-24","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":"detailed in the <span class=\"match\">sections</span> that follow, we proposed to <span class=\"match\">adopt</span> three X12N TR3 <span class=\"match\">implementation</span> specifications for health care claims attachments (87 FR 78445) and three HL7 IGs for the clinical information embedded in those transactions (87 FR 78445). \n a. Scope of Health Care Claims Attachments Transactions \n <span class=\"match\">Section</span> 1173(a) of the Act requires the Secretary to <span class=\"match\">adopt</span> standards for “health claims attachments,” and <span class=\"match\">section</span> 1104(c)(3) of the Affordable Care Act reiterated that <span class=\"match\">requirement</span>, directing the Secretary to promulgate a final rule to <span class=\"match\">adopt</span> a transaction"},{"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":"Register \n .\n \n \n <span class=\"match\">Section</span> 3004 of the PHSA establishes a process for the adoption of health IT standards, <span class=\"match\">implementation</span> specifications, and certification criteria and authorizes the Secretary to <span class=\"match\">adopt</span> such standards, <span class=\"match\">implementation</span> specifications, and certification criteria. As specified in <span class=\"match\">section</span> 3004(a)(1), the Secretary is required, in consultation with representatives of other relevant federal agencies, to jointly review standards, <span class=\"match\">implementation</span> specifications, and certification criteria endorsed by the National Coordinator in <span class=\"match\">section</span> 3001(c) and"},{"title":"Transparency in Coverage","type":"Proposed Rule","abstract":"These proposed rules set forth proposed requirements that would amend the regulations under the Public Health Service Act, the Employee Retirement Income Security Act of 1974, and the Internal Revenue Code regarding price transparency reporting requirements for non-grandfathered group health plans and health insurance issuers offering non-grandfathered group and individual health insurance coverage. Specifically, these proposed rules would improve the standardization, accuracy, and accessibility of public pricing disclosures in line with the goals of the Executive Order 14221. With respect to the in-network rate and out-of-network allowed amount machine-readable files, these proposed rules would achieve these goals by adding new contextual files and additional data elements like product type, network name, and enrollment counts; changing the reporting level for aggregation of data; removing in-network rates for unlikely provider-to-service mappings; increasing the reporting period and lowering the claims threshold for out-of-network historical data; and reducing the reporting cadence. These proposed rules would also improve the findability of all of the publicly disclosed machine- readable files required under the Transparency in Coverage rules, including the prescription drug file, by requiring a text file and footer with website URLs and contact information for the files. These proposed rules would also require pricing information that is made available through an online consumer tool and paper (upon request), to also be made available by phone, and establish that the satisfaction of such requirement also satisfies the requirements of section 114 of the No Surprises Act (including for grandfathered group health plans and health insurance issuers offering grandfathered group and individual health insurance coverage that are not otherwise subject to these proposed rules).","document_number":"2025-23693","html_url":"https://www.federalregister.gov/documents/2025/12/23/2025-23693/transparency-in-coverage","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-12-23/pdf/2025-23693.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-23693.pdf?1766178909","publication_date":"2025-12-23","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":"Internal Revenue Service","name":"Internal Revenue Service","id":254,"url":"https://www.federalregister.gov/agencies/internal-revenue-service","json_url":"https://www.federalregister.gov/api/v1/agencies/254","parent_id":497,"slug":"internal-revenue-service"},{"raw_name":"DEPARTMENT OF LABOR","name":"Labor Department","id":271,"url":"https://www.federalregister.gov/agencies/labor-department","json_url":"https://www.federalregister.gov/api/v1/agencies/271","parent_id":null,"slug":"labor-department"},{"raw_name":"Employee Benefits Security Administration","name":"Employee Benefits Security Administration","id":131,"url":"https://www.federalregister.gov/agencies/employee-benefits-security-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/131","parent_id":271,"slug":"employee-benefits-security-administration"},{"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"}],"excerpts":"under <span class=\"match\">section</span> 2707(b) of the PHS Act) (as applicable), respectively (and these in-network deductibles and out-of-pocket maximums must be applied) in the same manner as if such cost-sharing payments were made with respect to services furnished by a participating <span class=\"match\">provider</span> or facility.\n 50 \n \n \n \n \n 48 \n  Codified in Code <span class=\"match\">section</span> 9816, ERISA <span class=\"match\">section</span> 716, and PHS Act <span class=\"match\">section</span> 2799A-1.\n \n \n \n \n 49 \n  Codified in Code <span class=\"match\">section</span> 9817, ERISA <span class=\"match\">section</span> 717, and PHS Act <span class=\"match\">section</span> 2799A-2.\n \n \n \n \n 50 \n  Codified in Code <span class=\"match\">sections</span> 9816 and 9817, ERISA <span class=\"match\">sections</span> 716 and"},{"title":"Review of Submarine Cable Landing License Rules and Procedures To Assess Evolving National Security, Law Enforcement, Foreign Policy, and Trade Policy Risks","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission or FCC) adopted a Report and Order that updates the Commission's submarine cable licensing process and adopts rule changes to protect critical U.S. communications infrastructure against foreign adversary threats, specifically those posed by an entity that is owned by, controlled by, or subject to the jurisdiction or direction of a foreign adversary. The Report and Order adopts a requirement for certain licensees to file an annual report about the licensee, submarine cable system ownership, and submarine cable operations. The Report and Order adopts a one-time information collection for licensees to identify, among other things, how many entities currently own or operate submarine line terminal equipment (SLTEs) on existing licensed cable systems. The Report and Order also requires applicants and licensees to certify that they have created, updated, and implemented a cybersecurity and physical security risk management plan and requires applicants to certify that the submarine cable system will not use equipment or services identified on the Commission's Covered List. With respect to the circuit capacity data collection, the Report and Order adopts streamlined rules and eliminates the requirement for licensees to file a cable operator report about the capacity on a cable and clarify the types of capacity that need to be reported on an annual basis.","document_number":"2025-19658","html_url":"https://www.federalregister.gov/documents/2025/10/27/2025-19658/review-of-submarine-cable-landing-license-rules-and-procedures-to-assess-evolving-national-security","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-10-27/pdf/2025-19658.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-19658.pdf?1761309905","publication_date":"2025-10-27","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":"information <span class=\"match\">requirements</span> we <span class=\"match\">adopt</span> relating to <span class=\"match\">third-party</span> service <span class=\"match\">providers</span> would duplicate information that is currently submitted to the Committee. Finally, as discussed below, as an initial step, we <span class=\"match\">adopt</span> a one-time collection that requires licensees to disclose whether they use certain <span class=\"match\">third-party</span> service <span class=\"match\">providers</span>. \n 3. Required Certifications for Applicants and Licensees \n 100. Below, we <span class=\"match\">adopt</span> rules requiring applicants to certify whether or not they exhibit any of the criteria set out in the presumptive disqualifying conditions <span class=\"match\">adopted</span> herein;"},{"title":"Promoting Technological Solutions To Combat Contraband Wireless Device Use in Correctional Facilities","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (FCC or Commission) seeks comment on proposals that would enhance public safety by removing regulatory barriers to the deployment and viability of existing and developing technologies that combat contraband wireless device use in correctional facilities. This document seeks comment on a proposed framework to authorize, for the first time, non-federal operation of radio frequency (RF) jamming solutions in correctional facilities. The Commission seeks to foster a collaborative environment among key stakeholders, including departments of correction, solutions providers, wireless providers, public safety and 911 entities, to explore an expanded range of solutions to a shared problem.","document_number":"2025-21325","html_url":"https://www.federalregister.gov/documents/2025/11/26/2025-21325/promoting-technological-solutions-to-combat-contraband-wireless-device-use-in-correctional","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-11-26/pdf/2025-21325.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-21325.pdf?1764078345","publication_date":"2025-11-26","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":") in GN Docket No. 13-111; FCC 25-65, <span class=\"match\">adopted</span> and released on September 30, 2025. The full text of this document is available for public inspection online at \n https://docs.fcc.gov/public/attachments/FCC-25-65A1.pdf. \n \n \n Paperwork Reduction Act. \n This document may contain potential new or revised information collection <span class=\"match\">requirements</span>. If the Commission <span class=\"match\">adopts</span> any new or modified information collection <span class=\"match\">requirements</span>, they will be submitted to the Office of Management and Budget (OMB) for review under <span class=\"match\">section</span> 3507(d) of the PRA. OMB, the general public"},{"title":"Children's Online Privacy Protection Rule","type":"Rule","abstract":"The Federal Trade Commission amends the Children's Online Privacy Protection Rule (the \"Rule\"), consistent with the requirements of the Children's Online Privacy Protection Act. The amendments to the Rule, which are based on the FTC's review of public comments and its enforcement experience, include one new definition and modifications to several others, as well as updates to key provisions to respond to changes in technology and online practices. The amendments are intended to strengthen protection of personal information collected from children, and, where appropriate, to clarify and streamline the Rule since it was last amended in January 2013.","document_number":"2025-05904","html_url":"https://www.federalregister.gov/documents/2025/04/22/2025-05904/childrens-online-privacy-protection-rule","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-04-22/pdf/2025-05904.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-05904.pdf?1745239507","publication_date":"2025-04-22","agencies":[{"raw_name":"FEDERAL TRADE COMMISSION","name":"Federal Trade Commission","id":192,"url":"https://www.federalregister.gov/agencies/federal-trade-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/192","parent_id":null,"slug":"federal-trade-commission"}],"excerpts":"is not clear).\n \n \n \n \n 33 \n  \n See \n COPPA FAQs, FAQ <span class=\"match\">Sections</span> D.1, D.3, and D.5.\n \n \n \n Other commenters expressed concern that the new definition prevents mixed audience websites and online services from <span class=\"match\">utilizing</span> the exceptions to the COPPA Rule's verifiable parental consent <span class=\"match\">requirement</span> set forth in § 312.5(c).\n 34 \n \n In response, the Commission clarifies that operators of mixed audience websites and online services may <span class=\"match\">utilize</span> the exceptions to the verifiable parental consent <span class=\"match\">requirement</span> set forth in § 312.5(c) of the Rule, as is true for operators"},{"title":"Medicare Program; Strengthening Oversight of Accrediting Organizations (AOs) and Preventing AO Conflicts of Interest, and Related Provisions","type":"Rule","abstract":"This final rule with comment period sets forth provisions to strengthen the oversight of Medicare national accrediting organizations by addressing conflicts of interest, establishing consistent standards, processes, and definitions, and updating the validation and performance standards systems. Additionally, this final rule with comment period revises the psychiatric hospital survey process, adds a limitation on terminated deemed providers and suppliers when reentering the program, and provides technical corrections for End-Stage Renal Disease facilities and Transplant Programs.","document_number":"2026-12069","html_url":"https://www.federalregister.gov/documents/2026/06/16/2026-12069/medicare-program-strengthening-oversight-of-accrediting-organizations-aos-and-preventing-ao","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-16/pdf/2026-12069.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12069.pdf?1781295308","publication_date":"2026-06-16","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":"resource that can help <span class=\"match\">providers</span> and suppliers improve the quality and safety of the care they provide. This does not mean that the <span class=\"match\">providers</span> or suppliers who elect not to receive fee-based consulting from an AO that offers it, or that <span class=\"match\">providers</span> or suppliers that are accredited by an AO that does not offer this service would not provide safe, quality care. \n There are many <span class=\"match\">third-party</span> consultants that offer fee-based consulting across all <span class=\"match\">provider</span> and supplier types. The availability of <span class=\"match\">third-party</span> fee-based consultants give <span class=\"match\">providers</span> and suppliers access"},{"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":"credential. \n While some data <span class=\"match\">provider</span> and <span class=\"match\">third party</span> commenters expressed concern with reliance on bilateral data access agreements to allocate liability, some of these data <span class=\"match\">provider</span> commenters stated that they could be used to address liability concerns. <span class=\"match\">Several</span> data <span class=\"match\">provider</span> commenters recommended that the final rule address liability by clarifying that data <span class=\"match\">providers</span> are not precluded from exercising discretion to comply with prudential safety and soundness obligations, including <span class=\"match\">third party</span> risk management expectations. <span class=\"match\">Several</span> of these commenters recommended"},{"title":"Normalizing Unmanned Aircraft Systems Beyond Visual Line of Sight Operations","type":"Proposed Rule","abstract":"This action proposes performance-based regulations to enable the design and operation of unmanned aircraft systems (UAS) at low altitudes beyond visual line of sight (BVLOS) and for third-party services, including UAS Traffic Management (UTM), that support these operations. The FAA Reauthorization Act of 2024 directs the development of this proposed rule. This proposed rule is necessary to support the integration of UAS into the national airspace system (NAS). This proposed rule is intended to provide a predictable and clear pathway for safe, routine, and scalable UAS operations that include package delivery, agriculture, aerial surveying, civic interest, operations training, demonstration, recreation, and flight testing. TSA proposes to make complementary changes to its regulations to ensure it can continue to impose security measures on these operations under its current regulatory structure for civil aviation.","document_number":"2025-14992","html_url":"https://www.federalregister.gov/documents/2025/08/07/2025-14992/normalizing-unmanned-aircraft-systems-beyond-visual-line-of-sight-operations","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-08-07/pdf/2025-14992.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-14992.pdf?1754484350","publication_date":"2025-08-07","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"},{"raw_name":"Federal Aviation Administration","name":"Federal Aviation Administration","id":159,"url":"https://www.federalregister.gov/agencies/federal-aviation-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/159","parent_id":492,"slug":"federal-aviation-administration"},{"raw_name":"DEPARTMENT OF HOMELAND SECURITY","name":"Homeland Security Department","id":227,"url":"https://www.federalregister.gov/agencies/homeland-security-department","json_url":"https://www.federalregister.gov/api/v1/agencies/227","parent_id":null,"slug":"homeland-security-department"},{"raw_name":"Transportation Security Administration","name":"Transportation Security Administration","id":494,"url":"https://www.federalregister.gov/agencies/transportation-security-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/494","parent_id":227,"slug":"transportation-security-administration"}],"excerpts":"operating rules is contained in <span class=\"match\">section</span> VI.B of this preamble. Lastly, proposed part 108 would also prescribe operating personnel <span class=\"match\">requirements</span> under subpart C, aircraft maintenance and alterations <span class=\"match\">requirements</span> under subpart F, and general procedural <span class=\"match\">requirements</span>—which includes inspection <span class=\"match\">requirements</span> and prohibitions against engaging in fraudulent or deceptive practices—under subpart A of the proposed part.\n 42 \n \n \n \n \n 42 \n  For subpart A, General, see <span class=\"match\">section</span> V of this preamble; for subpart C, Operations Personnel, see <span class=\"match\">section</span> VII of this preamble; for"},{"title":"Call Authentication Trust Anchor","type":"Rule","abstract":"In this document, the Federal Communications Commission (Commission) takes further steps to combat illegally spoofed robocalls by strengthening and expanding caller ID authentication and robocall mitigation obligations and creating new mechanisms to hold providers accountable for violations of the Commission's rules.","document_number":"2023-12142","html_url":"https://www.federalregister.gov/documents/2023/06/21/2023-12142/call-authentication-trust-anchor","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2023-06-21/pdf/2023-12142.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2023-12142.pdf?1687265121","publication_date":"2023-06-21","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":"the Commission's justifications for <span class=\"match\">adopting</span> a mandatory gateway <span class=\"match\">provider</span> <span class=\"match\">authentication</span> <span class=\"match\">requirement</span> apply with equal force to all non-gateway \n \n intermediate <span class=\"match\">providers</span> in the call path. The Commission disagrees. The gateway <span class=\"match\">provider</span> caller ID <span class=\"match\">authentication</span> rules <span class=\"match\">adopted</span> by the Commission in May 2022 apply to the first domestic intermediate <span class=\"match\">provider</span> in the path of a foreign-originated call. The <span class=\"match\">authentication</span> <span class=\"match\">requirement</span> the Commission <span class=\"match\">adopts</span> in this document similarly applies to the first intermediate <span class=\"match\">provider</span> in the path of a U.S.-originated call"},{"title":"Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements","type":"Proposed Rule","abstract":"The Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA), as amended, requires the Cybersecurity and Infrastructure Security Agency (CISA) to promulgate regulations implementing the statute's covered cyber incident and ransom payment reporting requirements for covered entities. CISA seeks comment on the proposed rule to implement CIRCIA's requirements and on several practical and policy issues related to the implementation of these new reporting requirements.","document_number":"2024-06526","html_url":"https://www.federalregister.gov/documents/2024/04/04/2024-06526/cyber-incident-reporting-for-critical-infrastructure-act-circia-reporting-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-04-04/pdf/2024-06526.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-06526.pdf?1711543528","publication_date":"2024-04-04","agencies":[{"raw_name":"DEPARTMENT OF HOMELAND SECURITY","name":"Homeland Security Department","id":227,"url":"https://www.federalregister.gov/agencies/homeland-security-department","json_url":"https://www.federalregister.gov/api/v1/agencies/227","parent_id":null,"slug":"homeland-security-department"}],"excerpts":"that is facilitated through or caused by either a compromise of a cloud service <span class=\"match\">provider</span>, managed service <span class=\"match\">provider</span>, other <span class=\"match\">third-party</span> data hosting <span class=\"match\">provider</span>, or a supply chain compromise. CISA is further proposing that a substantial cyber incident resulting in one of the listed impacts include any cyber incident regardless of cause, including, but not limited to, a compromise of a cloud service <span class=\"match\">provider</span>, managed service <span class=\"match\">provider</span>, or other <span class=\"match\">third-party</span> data hosting <span class=\"match\">provider</span>; a supply chain compromise; a denial-of-service attack; a ransomware attack; or"},{"title":"Implementation of Dynamic Line Ratings","type":"Proposed Rule","abstract":"The Federal Energy Regulatory Commission (Commission) is issuing an advance notice of proposed rulemaking presenting potential reforms to implement dynamic line ratings and, thereby, improve the accuracy of transmission line ratings. These potential reforms would require transmission line ratings to reflect solar heating based on the sun's position and forecastable cloud cover and require transmission line ratings to reflect forecasts of wind conditions on certain transmission lines. The potential reforms would also ensure transparency in the development and implementation of dynamic line ratings and enhance data reporting practices related to congestion in non-regional transmission organization/independent system operator regions to identify candidate transmission lines for the requirement to reflect forecasts of wind conditions. The Commission invites all interested persons to submit comments on the potential reforms and in response to specific questions.","document_number":"2024-14666","html_url":"https://www.federalregister.gov/documents/2024/07/15/2024-14666/implementation-of-dynamic-line-ratings","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-07-15/pdf/2024-14666.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-14666.pdf?1720788321","publication_date":"2024-07-15","agencies":[{"raw_name":"DEPARTMENT OF ENERGY","name":"Energy Department","id":136,"url":"https://www.federalregister.gov/agencies/energy-department","json_url":"https://www.federalregister.gov/api/v1/agencies/136","parent_id":null,"slug":"energy-department"},{"raw_name":"Federal Energy Regulatory Commission","name":"Federal Energy Regulatory Commission","id":167,"url":"https://www.federalregister.gov/agencies/federal-energy-regulatory-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/167","parent_id":136,"slug":"federal-energy-regulatory-commission"}],"excerpts":"\n \n \n 6. Confidence Levels \n 169 \n \n \n B. Compliance and Transition and <span class=\"match\">Implementation</span> Timelines \n 174 \n \n \n \n 1. \n Pro forma \n OATT Revisions and <span class=\"match\">Implementation</span>\n \n 174 \n \n \n 2. <span class=\"match\">Implementation</span> Timeframe for the Solar <span class=\"match\">Requirement</span> \n 176 \n \n \n 3. Phased-In <span class=\"match\">Implementation</span> Timeframe for the Wind <span class=\"match\">Requirement</span> \n 177 \n \n \n a. Annual Wind <span class=\"match\">Requirement</span> <span class=\"match\">Implementation</span> Cycles \n 177 \n \n \n b. Transmission <span class=\"match\">Provider</span> Compliance <span class=\"match\">Requirement</span> \n 180 \n \n \n c. Compliance for Transmission <span class=\"match\">Providers</span> That Are Subsidiaries of the Same Public Utility Holding Company \n 182 \n"},{"title":"Wireless E911 Location Accuracy Requirements","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) proposes rules to strengthen wireless 911 location accuracy rules and to put more actionable location information in the hands of Public Safety Answering Points (PSAPs) and first responders.","document_number":"2025-06865","html_url":"https://www.federalregister.gov/documents/2025/05/07/2025-06865/wireless-e911-location-accuracy-requirements","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-05-07/pdf/2025-06865.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-06865.pdf?1746535509","publication_date":"2025-05-07","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":"each technology in the <span class=\"match\">provider's</span> subscriber base? Should CMRS <span class=\"match\">providers</span> be allowed to certify their compliance based on an average of the handset distribution of multiple <span class=\"match\">providers</span>? How should non-nationwide CMRS <span class=\"match\">providers</span> that do not conduct their own testing in the test bed use the test bed data to certify their compliance with the proposed testing and validation <span class=\"match\">requirements</span>? \n 75 \n \n Should non-nationwide CMRS <span class=\"match\">providers</span> be allowed to use performance data from the test bed in a different manner from nationwide CMRS <span class=\"match\">providers</span> to certify their compliance"}]}