{"description":"Documents matching 'implementation technical validation detailed architectural'","count":1179,"total_pages":50,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=implementation+technical+validation+detailed+architectural&format=json&page=2","results":[{"title":"Expansion of Validated End User Authorization: Data Center Validated End User Authorization","type":"Rule","abstract":"In this rule, the Department of Commerce, Bureau of Industry and Security (BIS), amends the Export Administration Regulations (EAR) to expand the Validated End User Authorization (VEU) program to include VEU Authorization for data centers located in specified destinations (\"Data Center VEU\" or \"Data Center VEU Authorization\"). This expansion of the VEU program to include Data Center VEU is intended to facilitate quick and reliable export or reexport of items on the Commerce Control List necessary for a data center, including advanced computing items, to preapproved trusted end users. Data Center VEU adopts much of the framework of the existing VEU program, with additional requirements. This expansion of eligibility is intended to update the VEU program to recognize the advancement and benefits of artificial intelligence. As under the original VEU Authorization Program, the U.S. government will rigorously review Data Center VEU candidates' applications subject to detailed and verifiable criteria.","document_number":"2024-22587","html_url":"https://www.federalregister.gov/documents/2024/10/02/2024-22587/expansion-of-validated-end-user-authorization-data-center-validated-end-user-authorization","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-10-02/pdf/2024-22587.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-22587.pdf?1727700348","publication_date":"2024-10-02","agencies":[{"raw_name":"DEPARTMENT OF COMMERCE","name":"Commerce Department","id":54,"url":"https://www.federalregister.gov/agencies/commerce-department","json_url":"https://www.federalregister.gov/api/v1/agencies/54","parent_id":null,"slug":"commerce-department"},{"raw_name":"Bureau of Industry and Security","name":"Industry and Security Bureau","id":241,"url":"https://www.federalregister.gov/agencies/industry-and-security-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/241","parent_id":54,"slug":"industry-and-security-bureau"}],"excerpts":"supplement no. 7 to this part are country-specific. Authorization as a <span class=\"match\">validated</span> end-user for one country specified in paragraph (b) of this section does not constitute authorization as a <span class=\"match\">validated</span> end-user for any other country specified in that paragraph. \n \n \n (e) \n Certification and recordkeeping. \n Prior to an initial export or reexport to a <span class=\"match\">validated</span> end-user under General or Data Center VEU Authorization, exporters or reexporters must obtain certifications from the <span class=\"match\">validated</span> end-user regarding end-use and compliance with VEU requirements. Such"},{"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":"what problems remain to be addressed ignores demonstrated risks to 911 reliability and needlessly delays <span class=\"match\">implementation</span> of available solutions.\n 83 \n \n The stakeholder community has already developed <span class=\"match\">detailed</span> and well-established <span class=\"match\">technical</span> <span class=\"match\">architecture</span> and commonly accepted standards for NG911 systems,\n 84 \n \n and the reliability framework we adopt today is based on well-documented best practices for IP networks that can readily be <span class=\"match\">implemented</span> by CSPs as part of their network build-outs.\n \n \n \n 80 \n  Association of Public-Safety Communications Officials"},{"title":"Event Data Recorders","type":"Rule","abstract":"This final rule amends NHTSA's regulation governing Event Data Recorders (EDR or EDRs) to delay the implementation schedule for expanded pre-crash data capture requirements. In response to petitions for reconsideration of a final rule published on December 18, 2024, the agency is adopting a four-year phase-in compliance schedule that begins September 1, 2028. This action ensures the increased pre-crash data capture requirements are integrated into the vehicle fleet in a manner that aligns with manufacturer production cycles and technical feasibility.","document_number":"2026-09849","html_url":"https://www.federalregister.gov/documents/2026/05/18/2026-09849/event-data-recorders","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-18/pdf/2026-09849.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-09849.pdf?1778849114","publication_date":"2026-05-18","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":"National Highway Traffic Safety Administration","name":"National Highway Traffic Safety Administration","id":345,"url":"https://www.federalregister.gov/agencies/national-highway-traffic-safety-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/345","parent_id":492,"slug":"national-highway-traffic-safety-administration"}],"excerpts":"ignores globally vetted <span class=\"match\">technical</span> solutions already <span class=\"match\">implemented</span> by 60 other nations.\n 18 \n \n IEEE-VTS asserts that the “heavy lifting” for these standards has already been completed through the development of Std-IEEE-1616.1: Data Storage System for Automated and Autonomous Driving (DSSAD). IEEE-VTS commented that the DSSAD provides a “Scientific Witness” that distinguishes between human and machine operation, a critical necessity given the 112 daily road fatalities in the U.S. IEEE-VTS disputes the industry's claims of <span class=\"match\">technical</span> burden, noting that"},{"title":"Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041)","type":"Rule","abstract":"DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to incorporate contractual requirements related to the final Cybersecurity Maturity Model Certification program rule, titled Cybersecurity Maturity Model Certification Program. This final DFARS rule also partially implements a section of the National Defense Authorization Act for Fiscal Year 2020 that directed the Secretary of Defense to develop a consistent, comprehensive framework to enhance cybersecurity for the U.S. defense industrial base.","document_number":"2025-17359","html_url":"https://www.federalregister.gov/documents/2025/09/10/2025-17359/defense-federal-acquisition-regulation-supplement-assessing-contractor-implementation-of","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-10/pdf/2025-17359.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-17359.pdf?1757421911","publication_date":"2025-09-10","agencies":[{"raw_name":"DEPARTMENT OF DEFENSE","name":"Defense Department","id":103,"url":"https://www.federalregister.gov/agencies/defense-department","json_url":"https://www.federalregister.gov/api/v1/agencies/103","parent_id":null,"slug":"defense-department"},{"raw_name":"Defense Acquisition Regulations System","name":"Defense Acquisition Regulations System","id":97,"url":"https://www.federalregister.gov/agencies/defense-acquisition-regulations-system","json_url":"https://www.federalregister.gov/api/v1/agencies/97","parent_id":103,"slug":"defense-acquisition-regulations-system"}],"excerpts":" With regard to the enclave approach, the contractor determines the systems(s) that will be used in performance of a DoD contract and the assessment scope that must be specified in advance of an assessment at any CMMC level, as <span class=\"match\">detailed</span> in 32 CFR part 170.19. \n Regarding the phased <span class=\"match\">implementation</span> plan, the <span class=\"match\">implementation</span> requirements for the phase-in of CMMC were codified at 32 CFR part 170.3. \n With regard to reassessments, the final rule affecting 32 CFR part 170 was modified to clarify that reassessments may be required based on post-assessment"},{"title":"Defense Federal Acquisition Regulation Supplement: Modifications to Printed Circuit Board Acquisition Restrictions (DFARS Case 2022-D011)","type":"Proposed Rule","abstract":"DoD is seeking information that will assist in the development of a revision to the Defense Federal Acquisition Regulation Supplement (DFARS) to implement sections of the National Defense Authorization Acts for Fiscal Years 2021 and 2022 that address the prohibition on the acquisition of covered printed circuit boards from a covered nation.","document_number":"2026-13375","html_url":"https://www.federalregister.gov/documents/2026/07/02/2026-13375/defense-federal-acquisition-regulation-supplement-modifications-to-printed-circuit-board-acquisition","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-07-02/pdf/2026-13375.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13375.pdf?1782909915","publication_date":"2026-07-02","agencies":[{"raw_name":"DEPARTMENT OF DEFENSE","name":"Defense Department","id":103,"url":"https://www.federalregister.gov/agencies/defense-department","json_url":"https://www.federalregister.gov/api/v1/agencies/103","parent_id":null,"slug":"defense-department"},{"raw_name":"Defense Acquisition Regulations System","name":"Defense Acquisition Regulations System","id":97,"url":"https://www.federalregister.gov/agencies/defense-acquisition-regulations-system","json_url":"https://www.federalregister.gov/api/v1/agencies/97","parent_id":103,"slug":"defense-acquisition-regulations-system"}],"excerpts":"controlled by a covered nation (\n i.e., \n the People's Republic of China, the Russian Federation, the Islamic Republic of Iran, the Democratic People's Republic of North Korea). DoD intends to <span class=\"match\">implement</span> this prohibition by focusing on the geographic point of fabrication for bare boards or partially manufactured boards and by utilizing a tiered trust <span class=\"match\">architecture</span>.\n \n Furthermore, any rulemaking that may follow this advance notice of proposed rulemaking (ANPR) would put into operation the mandate in section 224 of the NDAA for FY 2020, which requires"},{"title":"Patient Protection and Affordable Care Act, HHS Notice of Benefit and Payment Parameters for 2027; and Basic Health Program","type":"Rule","abstract":"This final rule contains provisions to improve implementation of the Patient Protection and Affordable Care Act, including payment parameters and provisions related to the HHS-operated risk adjustment and risk adjustment data validation (HHS-RADV) programs, as well as 2027 user fee rates for issuers offering qualified health plans (QHPs) through Federally-facilitated Exchanges (FFEs) and State-based Exchanges on the Federal platform (SBE-FPs). This final rule also includes provisions related to civil money penalties (CMPs) for noncompliant issuers and other responsible entities; standards governing agents, brokers, and web-brokers; the expansion and codification of hardship exemption eligibility; implementation of the State Exchange Improper Payment Measurement (SEIPM); provider access standards and essential community provider standards for QHP certification; QHP certification of non-network plans; a prohibition on issuers from including routine non-pediatric dental services as an Essential Health Benefit (EHB); requirements related to defrayal for the cost of any State-required benefits in addition to the EHB; cost- sharing flexibilities for catastrophic and individual market bronze plans; establishment of catastrophic plans with plan terms of up to 10 consecutive plan years; QHP issuer quality improvement strategies (QISs); and revisions affecting which enrollees are included in Federal Basic Health Program (BHP) payment calculations to States. This final rule also includes amendments to implement certain provisions of the Working Families Tax Cut (WFTC) legislation.","document_number":"2026-10050","html_url":"https://www.federalregister.gov/documents/2026/05/20/2026-10050/patient-protection-and-affordable-care-act-hhs-notice-of-benefit-and-payment-parameters-for-2027-and","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-20/pdf/2026-10050.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-10050.pdf?1779135308","publication_date":"2026-05-20","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":"changes to the provisions and parameters <span class=\"match\">implemented</span> through prior rulemaking to <span class=\"match\">implement</span> the Patient Protection and Affordable Care Act and are also finalizing updates to <span class=\"match\">implement</span> new provisions.\n 1 \n \n These requirements are published under the authority granted to the Secretary of HHS (the Secretary) by the Affordable Care Act and the Public Health Service (PHS) Act.\n 2 \n \n In this document, we are finalizing changes related to some of the Affordable Care Act provisions and parameters we previously <span class=\"match\">implemented</span> under the authority granted to the Secretary"},{"title":"Patient Protection and Affordable Care Act, HHS Notice of Benefit and Payment Parameters for 2027; and Basic Health Program","type":"Proposed Rule","abstract":"This proposed rule contains provisions to improve implementation of the Patient Protection and Affordable Care Act, including payment parameters and provisions related to the HHS-operated risk adjustment and risk adjustment data validation (HHS-RADV) programs, as well as 2027 user fee rates for issuers offering qualified health plans (QHPs) through Federally-facilitated Exchanges (FFEs) and State-based Exchanges on the Federal platform (SBE-FPs). This proposed rule also includes provisions related to civil money penalties (CMPs) for noncompliant issuers and other responsible entities; standards governing agents, brokers, and web-brokers; the expansion and codification of hardship exemption eligibility; implementation of the State Exchange Improper Payment Measurement (SEIPM); provider access standards and essential community provider standards for QHP certification; QHP certification of non-network plans; a prohibition on issuers from including routine non-pediatric dental services as an Essential Health Benefit (EHB); cost-sharing flexibilities for catastrophic and individual market bronze plans; establishment of catastrophic plans with plan terms of up to 10 consecutive years; QHP issuer quality improvement strategies (QISs); revisions affecting which enrollees are included in Federal Basic Health Program (BHP) payment calculations to States; and seeks comment on potential adjustments to other Federal standards, including the Federal medical loss ratio (MLR) standard in the individual market. This proposed rule also includes amendments to implement certain provisions of the Working Families Tax Cut (WFTC) legislation.","document_number":"2026-02769","html_url":"https://www.federalregister.gov/documents/2026/02/11/2026-02769/patient-protection-and-affordable-care-act-hhs-notice-of-benefit-and-payment-parameters-for-2027-and","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-02-11/pdf/2026-02769.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-02769.pdf?1770671709","publication_date":"2026-02-11","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":"propose changes to the provisions and parameters <span class=\"match\">implemented</span> through prior rulemaking to <span class=\"match\">implement</span> the Patient Protection and Affordable Care Act and propose to <span class=\"match\">implement</span> new provisions.\n 1 \n \n These requirements are published under the authority granted to the Secretary of HHS (the Secretary) by the Affordable Care Act and the Public Health Service (PHS) Act.\n 2 \n \n In this document, we are proposing changes related to some of the Affordable Care Act provisions and parameters we previously <span class=\"match\">implemented</span> under the authority granted to the Secretary by"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Location-Based Routing for Wireless 911 Calls","type":"Rule","abstract":"In this document, the Federal Communications Commission (the FCC or Commission) adopted a Report and Order to advance the nationwide Next Generation 911 (NG911) transition rules that define the responsibilities and set deadlines for originating service providers (OSPs) to implement NG911 capabilities on their networks and deliver 911 calls to NG911 systems established by 911 authorities. In addition, the rules preserve the authority of state, territorial, regional, Tribal, and local government to adopt alternative approaches to the configuration, timing, and cost responsibility for NG911 implementation within their jurisdictions.","document_number":"2024-18603","html_url":"https://www.federalregister.gov/documents/2024/09/24/2024-18603/facilitating-implementation-of-next-generation-911-services-ng911-location-based-routing-for","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-09-24/pdf/2024-18603.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-18603.pdf?1727095514","publication_date":"2024-09-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":"connectivity at the ESInet is “not always necessary for the PSAP and its NG911 vendor to migrate to NG911” and that “full NG911 <span class=\"match\">implementation</span> is a viable and potentially better alternative to the two-stage approach,” the record indicates that most 911 Authorities have <span class=\"match\">implemented</span> or plan to <span class=\"match\">implement</span> IP connectivity as a transitional step in their <span class=\"match\">implementation</span> of NG911. For OSPs that wish to deliver Phase 2 without <span class=\"match\">implementing</span> Phase 1 first, we note that OSPs and 911 Authorities may mutually agree on such an approach. As our goal is a prompt transition"},{"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":"WG 1 Report \n at 115 (“Network Operators . . . should <span class=\"match\">implement</span> a continuous engineering process to identify and record single points of failure and any components that are critical to the continuity of the infrastructure . . . [and] pursue <span class=\"match\">architectural</span> solutions to mitigate the identified risks . . . .”), p. 124 (providers should “design networks with redundant interconnectivity to” ESInets), p. 122 (“Network Operators . . . should identify and manage critical network elements and <span class=\"match\">architecture</span> that are essential for network connectivity and subscriber"},{"title":"Federal Motor Vehicle Safety Standards; FMVSS No. 305a Electric-Powered Vehicles: Electric Powertrain Integrity Global Technical Regulation No. 20 Incorporation by Reference","type":"Rule","abstract":"Consistent with a Global Technical Regulation on electric vehicle safety, NHTSA is establishing Federal Motor Vehicle Safety Standard (FMVSS) No. 305a to replace FMVSS No. 305, \"Electric-powered vehicles: Electrolyte spillage and electrical shock protection.\" Among other improvements, FMVSS No. 305a applies to light and heavy vehicles and includes performance requirements for the propulsion battery. NHTSA is also establishing a new regulation, part 561, \"Documentation for Electric-powered Vehicles,\" that requires manufacturers to compile risk mitigation documentation and to submit standardized emergency response information to assist first and second responders handling electric vehicles.","document_number":"2024-28707","html_url":"https://www.federalregister.gov/documents/2024/12/20/2024-28707/federal-motor-vehicle-safety-standards-fmvss-no-305a-electric-powered-vehicles-electric-powertrain","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-12-20/pdf/2024-28707.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-28707.pdf?1734615913","publication_date":"2024-12-20","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":"National Highway Traffic Safety Administration","name":"National Highway Traffic Safety Administration","id":345,"url":"https://www.federalregister.gov/agencies/national-highway-traffic-safety-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/345","parent_id":492,"slug":"national-highway-traffic-safety-administration"}],"excerpts":"the IPX6 level. \n \n With regard to submersion concerns, commenters generally agreed that further research is necessary, and some urged NHTSA to commit to a <span class=\"match\">technical</span> amendment. Auto Innovators said that more analysis is needed before determining whether additional test requirements should be <span class=\"match\">implemented</span> and recommended harmonizing with UNECE R100. EDTA recommended that NHTSA commit to a <span class=\"match\">technical</span> amendment and collaborate with stakeholders in collecting data to establish a test requirement addressing real-world flooding scenarios. MEMA, NEMA, and Eaton"},{"title":"Framework for Artificial Intelligence Diffusion","type":"Rule","abstract":"With this interim final rule, the Commerce Department's Bureau of Industry and Security (BIS) revises the Export Administration Regulations' (EAR) controls on advanced computing integrated circuits (ICs) and adds a new control on artificial intelligence (AI) model weights for certain advanced closed-weight dual-use AI models. In conjunction with the expansion of these controls, which BIS has determined are necessary to protect U.S. national security and foreign policy interests, BIS is adding new license exceptions and updating the Data Center Validated End User authorization to facilitate the export, reexport, and transfer (in-country) of advanced computing (ICs) to end users in destinations that do not raise national security or foreign policy concerns. Together, these changes will cultivate secure ecosystems for the responsible diffusion and use of AI and advanced computing ICs.","document_number":"2025-00636","html_url":"https://www.federalregister.gov/documents/2025/01/15/2025-00636/framework-for-artificial-intelligence-diffusion","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-01-15/pdf/2025-00636.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-00636.pdf?1736775933","publication_date":"2025-01-15","agencies":[{"raw_name":"DEPARTMENT OF COMMERCE","name":"Commerce Department","id":54,"url":"https://www.federalregister.gov/agencies/commerce-department","json_url":"https://www.federalregister.gov/api/v1/agencies/54","parent_id":null,"slug":"commerce-department"},{"raw_name":"Bureau of Industry and Security","name":"Industry and Security Bureau","id":241,"url":"https://www.federalregister.gov/agencies/industry-and-security-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/241","parent_id":54,"slug":"industry-and-security-bureau"}],"excerpts":"government have determined that, in the hands of <span class=\"match\">validated</span> entities operating under secure conditions, dual-use AI models have the potential to create significant economic and social benefits in the United States and across the globe. As BIS explained in a previous rule, dual-use AI models hold the potential to increase access to healthcare, education, and food and assist with combatting complex problems such as climate change. \n See \n Expansion of <span class=\"match\">Validated</span> End User Authorization: Data Center <span class=\"match\">Validated</span> End User Authorization, 89 FR 80,080 (Oct. 2,"},{"title":"Event Data Recorders","type":"Proposed Rule","abstract":"NHTSA published a final rule on December 18, 2024, in response to a mandate of the Fixing America's Surface Transportation Act (FAST Act) to establish the appropriate recording period in NHTSA's Event Data Recorder (EDR) regulation (49 CFR part 563). The final rule amended the pre-crash data capture requirements of EDRs by increasing the recording duration and sample rate from 5 seconds at 2 Hz to 20 seconds at 10 Hz. The agency received three petitions for reconsideration from the Alliance of Automotive Innovation, the EDR Committee of SAE International, and FCA US LLC (a subsidiary of Stellantis N.V.) in response to the final rule. NHTSA is proposing to delay the compliance date from September 1, 2027, to September 1, 2028, and implement a phase-in period for EDRs to meet the new requirements.","document_number":"2025-21506","html_url":"https://www.federalregister.gov/documents/2025/11/28/2025-21506/event-data-recorders","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-11-28/pdf/2025-21506.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-21506.pdf?1764164735","publication_date":"2025-11-28","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":"National Highway Traffic Safety Administration","name":"National Highway Traffic Safety Administration","id":345,"url":"https://www.federalregister.gov/agencies/national-highway-traffic-safety-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/345","parent_id":492,"slug":"national-highway-traffic-safety-administration"}],"excerpts":"Control Module (ACM) \n 5 \n \n <span class=\"match\">architecture</span> changes within their current model development cycles without disrupting existing product plans. The agency's proposal balances the need for enhanced crash data, as mandated by the FAST Act, with practical industry constraints to ensure these safety advancements can be <span class=\"match\">implemented</span> effectively across the entire vehicle fleet. However, NHTSA is not proposing to adjust the recording duration and sample rate requirements for EDRs as finalized in the December 2024 final rule. These <span class=\"match\">technical</span> specifications represent"},{"title":"Patient Protection and Affordable Care Act; HHS Notice of Benefit and Payment Parameters for 2026; and Basic Health Program","type":"Rule","abstract":"This final rule includes payment parameters and provisions related to the HHS-operated risk adjustment and risk adjustment data validation (HHS-RADV) programs, as well as 2026 benefit year user fee rates for issuers that participate in the HHS-operated risk adjustment program and the 2026 benefit year user fee rates for issuers offering qualified health plans (QHPs) through Federally-facilitated Exchanges (FFEs) and State-based Exchanges on the Federal platform (SBE-FPs). This final rule also includes requirements related to modifications to the calculation of the Basic Health Program (BHP) payment; and changes to the Initial Validation Audit (IVA) sampling approach and Second Validation Audit (SVA) pairwise means test for HHS-RADV. It also addresses HHS' authority to engage in compliance reviews of and take enforcement action against lead agents of insurance agencies for violations of HHS' Exchange standards and requirements; HHS' system suspension authority to address noncompliance by agents and brokers; an optional fixed-dollar premium payment threshold; permissible plan-level adjustment to the index rate to account for cost-sharing reductions (CSRs); reconsideration standards for certification denials; changes to the approach for conducting Essential Community Provider (ECP) certification reviews; a policy to publicly share aggregated, summary- level Quality Improvement Strategy (QIS) information on an annual basis; and revisions to the medical loss ratio (MLR) reporting and rebate requirements for qualifying issuers that meet certain standards.","document_number":"2025-00640","html_url":"https://www.federalregister.gov/documents/2025/01/15/2025-00640/patient-protection-and-affordable-care-act-hhs-notice-of-benefit-and-payment-parameters-for-2026-and","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-01-15/pdf/2025-00640.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-00640.pdf?1736802922","publication_date":"2025-01-15","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":"finalizing maintaining the PAF value at 1.188 for States that have fully <span class=\"match\">implemented</span> BHP and are using Second Lowest Cost Silver Plan (SLCSP) premiums from a year in which BHP was fully <span class=\"match\">implemented</span>. As previously clarified, for States in their first year of <span class=\"match\">implementing</span> BHP and choosing to use prior year SLCSP premiums to determine BHP payment, the PAF value will be set to 1.00. We are finalizing that if a State is using SLCSP premiums from a year in which BHP was not fully <span class=\"match\">implemented</span>, the PAF is calculated by determining the CSR adjustment that QHP issuers"},{"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":"Volume Two—Templates and Supporting Material, June 2019—The standard specifies the <span class=\"match\">detailed</span> template definitions and supporting <span class=\"match\">technical</span> specifications for <span class=\"match\">implementing</span> Consolidated Clinical Document <span class=\"match\">Architecture</span> (C-CDA) clinical documents. This volume defines the structure, constraints, and required data elements for specific clinical document templates, sections, and entries used to represent patient clinical information using the HL7 Clinical Document <span class=\"match\">Architecture</span> Release 2 framework. The standard also enables health care providers, health information"},{"title":"Notice of Issuance of Final Determination Concerning FLY Server","type":"Notice","abstract":"This document provides notice that U.S. Customs and Border Protection (CBP) has issued a final determination concerning the country of origin of the FLY Server. Based upon the facts presented, CBP has concluded that the last substantial transformation of the FLY Server occurs in the United States.","document_number":"2025-17123","html_url":"https://www.federalregister.gov/documents/2025/09/08/2025-17123/notice-of-issuance-of-final-determination-concerning-fly-server","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-08/pdf/2025-17123.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-17123.pdf?1757076313","publication_date":"2025-09-08","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"},{"raw_name":"U.S. Customs and Border Protection","name":"U.S. Customs and Border Protection","id":501,"url":"https://www.federalregister.gov/agencies/u-s-customs-and-border-protection","json_url":"https://www.federalregister.gov/api/v1/agencies/501","parent_id":227,"slug":"u-s-customs-and-border-protection"}],"excerpts":"technologies backed by a common <span class=\"match\">technical</span> infrastructure that is used to provide intranet portals, document and file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence. They also have system integration, process integration, and workflow automation capabilities. \n The FLY Server product simplifies the migration of content from legacy systems into SharePoint and/or Microsoft 365. The FLY Server has a browser-based interface and a fully distributed <span class=\"match\">architecture</span> that offers data transfer capabilities"},{"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":"Registry, Version \n \n 3.0, December 8, 2008 IBR approved for § 170.205.\n \n (3) [Reserved] \n (4) CMS <span class=\"match\">Implementation</span> Guide for Quality Reporting Document <span class=\"match\">Architecture</span>: Category I; Hospital Quality Reporting <span class=\"match\">Implementation</span> Guide for 2020; published December 3, 2019, IBR approved for § 170.205(h). \n (5) CMS <span class=\"match\">Implementation</span> Guide for Quality Reporting Document <span class=\"match\">Architecture</span>: Category III; Eligible Clinicians and Eligible Professionals Programs <span class=\"match\">Implementation</span> Guide for 2020; published April 30, 2020, IBR approved for § 170.205(k). \n \n (d) Council of State"},{"title":"Strengthening and Promoting Innovation in the Nation's Cybersecurity","type":"Presidential Document","abstract":null,"document_number":"2025-01470","html_url":"https://www.federalregister.gov/documents/2025/01/17/2025-01470/strengthening-and-promoting-innovation-in-the-nations-cybersecurity","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-01-17/pdf/2025-01470.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-01470.pdf?1737054015","publication_date":"2025-01-17","agencies":[{"raw_name":"EXECUTIVE OFFICE OF THE PRESIDENT","name":"Executive Office of the President","id":538,"url":"https://www.federalregister.gov/agencies/executive-office-of-the-president","json_url":"https://www.federalregister.gov/api/v1/agencies/538","parent_id":null,"slug":"executive-office-of-the-president"}],"excerpts":"attestation forms. CISA shall continuously <span class=\"match\">validate</span> a sample of the complete attestations using high-level artifacts in the RSAA. \n (v) If CISA finds that attestations are incomplete or artifacts are insufficient for <span class=\"match\">validating</span> the attestations, the Director of CISA shall notify the software provider and the contracting agency. The Director of CISA shall provide a process for the software provider to respond to CISA's initial determination and shall duly consider the response. \n (vi) For attestations that undergo <span class=\"match\">validation</span>, the Director of CISA shall inform"},{"title":"Reporting on Border Gateway Protocol Risk Mitigation Progress; Secure Internet Routing","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) seeks to increase the security of the information routed across the internet by proposing certain reporting obligations on providers of broadband internet access service (BIAS providers) and their use of the Border Gateway Protocol (BGP). Internet traffic can be disrupted, intercepted, and blackholed--when a service provider drops traffic addressed to a targeted IP address or range of addresses by redirecting it to a null route--due to either accidental or deliberate adversarial manipulation of security vulnerabilities inherent to BGP. Together, the intended effect of the plans, filings, and measures the Commission proposes would be to mitigate such threats. BIAS providers would be required to develop BGP Routing Security Risk Management Plans that describe their plans for and progress in implementing security measures that utilize the Resource Public Key Infrastructure (RPKI). Nine of the largest service providers would be required to file specific additional data on a quarterly basis. The FCC also seeks comment on issues related to implementing RPKI-based security measures.","document_number":"2024-13048","html_url":"https://www.federalregister.gov/documents/2024/06/17/2024-13048/reporting-on-border-gateway-protocol-risk-mitigation-progress-secure-internet-routing","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-06-17/pdf/2024-13048.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-13048.pdf?1718369113","publication_date":"2024-06-17","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":"discussion among the academic and standards community and are not ready for <span class=\"match\">implementation</span>. Although this \n NPRM \n focuses on issues with origin <span class=\"match\">validation</span> and the techniques currently available to address them, achieving a truly secure routing system will involve steps beyond deploying RPKI-based origin <span class=\"match\">validation</span>. We do not propose at this time to require service providers to <span class=\"match\">implement</span> measures or disclose efforts regarding path <span class=\"match\">validation</span>, but we note that their <span class=\"match\">implementation</span> is expected to be a critical, future step that service providers would"},{"title":"Implementation of Additional Due Diligence Measures for Advanced Computing Integrated Circuits; Amendments and Clarifications; and Extension of Comment Period","type":"Rule","abstract":"BIS is revising the Export Administration Regulations (EAR) in response to requests from the public to provide additional due diligence procedures regarding advanced computing integrated circuits (ICs). This interim final rule (IFR) will protect the national security of the United States and assist foundries and Outsourced Semiconductor Assembly and Test (\"OSATs\") companies in complying with provisions of the EAR pertaining to advanced computing ICs in the supply chain. This IFR also revises the EAR to make amendments and clarifications to the EAR for changes made to the EAR in an IFR released by BIS on December 2, 2024, \"Foreign-Produced Direct Product Rule Additions, and Refinements to Controls for Advanced Computing and Semiconductor Manufacturing Items,\" (FDP IFR), including extending the deadline for written comments for the FDP IFR to March 14, 2025.","document_number":"2025-00711","html_url":"https://www.federalregister.gov/documents/2025/01/16/2025-00711/implementation-of-additional-due-diligence-measures-for-advanced-computing-integrated-circuits","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-01-16/pdf/2025-00711.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-00711.pdf?1736948727","publication_date":"2025-01-16","agencies":[{"raw_name":"DEPARTMENT OF COMMERCE","name":"Commerce Department","id":54,"url":"https://www.federalregister.gov/agencies/commerce-department","json_url":"https://www.federalregister.gov/api/v1/agencies/54","parent_id":null,"slug":"commerce-department"},{"raw_name":"Bureau of Industry and Security","name":"Industry and Security Bureau","id":241,"url":"https://www.federalregister.gov/agencies/industry-and-security-bureau","json_url":"https://www.federalregister.gov/api/v1/agencies/241","parent_id":54,"slug":"industry-and-security-bureau"}],"excerpts":"Computing ICs \n Accordingly, on October 7, 2022, BIS released the IFR, “<span class=\"match\">Implementation</span> of Additional Export Controls: Certain Advanced Computing and Semiconductor Manufacturing Items; Supercomputer and Semiconductor End Use; Entity List Modification” (October 7 IFR) (October 13, 2022, 87 FR 62186), which amended the EAR to <span class=\"match\">implement</span> controls on certain ICs, computer commodities that contain such ICs, and certain semiconductor manufacturing items, and to make other EAR changes to <span class=\"match\">implement</span> appropriate related controls, including on certain “U.S. person”"},{"title":"Virtualization Reliability Standards","type":"Proposed Rule","abstract":"The Federal Energy Regulatory Commission (Commission) proposes to approve four new definitions and 18 modified definitions in the North American Electric Reliability Corporation (NERC) Glossary of Terms Used in Reliability Standards. The Commission also proposes to approve eleven modified Critical Infrastructure Protection (CIP) Reliability Standards. NERC, the Commission-certified electric reliability organization, submitted the proposed modifications to update the CIP Reliability Standards to enable the application of virtualization and other new technologies in a secure manner.","document_number":"2025-18395","html_url":"https://www.federalregister.gov/documents/2025/09/23/2025-18395/virtualization-reliability-standards","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-23/pdf/2025-18395.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-18395.pdf?1758545114","publication_date":"2025-09-23","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":"approval by submitting an application to the ERO that includes justification for the <span class=\"match\">technical</span> feasibility exception, plans for alternative mitigation, and remediation plans to eventually eliminate use of the <span class=\"match\">technical</span> feasibility exception.\n 37 \n \n Order No. 706 also required that the ERO submit to the Commission an annual report on the use of <span class=\"match\">technical</span> feasibility exceptions and reliability impacts. NERC developed and the Commission approved the directed <span class=\"match\">technical</span> feasibility procedures.\n 38 \n \n \n \n \n 36 \n  \n Mandatory Reliability Standards for Critical"}]}