{"description":"Documents matching 'Data Integration rulemaking'","count":8598,"total_pages":50,"next_page_url":"https://www.federalregister.gov/api/v1/documents?conditions%5Bterm%5D=Data+Integration+rulemaking&format=json&page=2","results":[{"title":"Rulemaking Procedures","type":"Proposed Rule","abstract":"The Federal Maritime Commission (FMC or the Commission) is proposing to revise its rulemaking procedures. The changes would: consolidate informal rulemaking and rulemaking petition requirements into subpart D, clarify ambiguities, remove unnecessary, overly restrictive requirements (such as ex parte requirements), and allow for the FMC to integrate its rulemaking procedures into the Executive Order 12866 centralized regulatory review process, as directed by Executive Order 14215. This proposal would also make conforming changes associated with the FMC's transition to eRulemaking. The FMC invites public comment on all aspects of this proposed rule.","document_number":"2026-09450","html_url":"https://www.federalregister.gov/documents/2026/05/13/2026-09450/rulemaking-procedures","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-05-13/pdf/2026-09450.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-09450.pdf?1778589908","publication_date":"2026-05-13","agencies":[{"raw_name":"FEDERAL MARITIME COMMISSION","name":"Federal Maritime Commission","id":178,"url":"https://www.federalregister.gov/agencies/federal-maritime-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/178","parent_id":null,"slug":"federal-maritime-commission"}],"excerpts":"its duties and powers. \n B. Formal Versus Informal <span class=\"match\">Rulemaking</span> \n \n The Administrative Procedure Act (APA) provides the general procedures for agency <span class=\"match\">rulemaking</span>. Most <span class=\"match\">rulemakings</span> are conducted under the “informal <span class=\"match\">rulemaking</span>” procedures of 5 U.S.C. 553. In limited circumstances, federal agencies must engage in “formal <span class=\"match\">rulemaking</span>,” which has heightened procedural requirements. The formal <span class=\"match\">rulemaking</span> requirements of 5 U.S.C. 556 and 557 are only triggered when Congress explicitly requires <span class=\"match\">rulemaking</span> “on the record after opportunity for an agency hearing"},{"title":"Electric Vertical Takeoff and Landing and Advanced Air Mobility Integration Pilot Program-Announcement of Establishment of Program and Request for Proposals","type":"Notice","abstract":"The Department of Transportation (DOT), through the Federal Aviation Administration (FAA), announces a new eVTOL and AAM Integration Pilot Program (eIPP) that will accelerate the deployment of safe and lawful eVTOL and other AAM aircraft operations in the United States. The eIPP requests that State, local, tribal, and territorial (SLTT) governments, in partnership with a private sector partner(s) with demonstrated experience in eVTOL or other AAM development, manufacturing, and operations, or new supporting technologies enabling AAM operations integration into the NAS, submit proposals. The eIPP continues the DOT's efforts to integrate eVTOL and other AAM aircraft developed or offered by a United States-based entity into the National Airspace System (NAS) by identifying the most effective partnerships to test and validate operational concepts that can be scaled to national and international applications. SLTT governments and their private sector partner(s) will propose and define these operational concepts under the safety oversight role of the FAA.","document_number":"2025-17844","html_url":"https://www.federalregister.gov/documents/2025/09/16/2025-17844/electric-vertical-takeoff-and-landing-and-advanced-air-mobility-integration-pilot","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-09-16/pdf/2025-17844.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-17844.pdf?1757690107","publication_date":"2025-09-16","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"}],"excerpts":"will adhere to the privacy policies and <span class=\"match\">data</span> collection requirements specified in the agreement. Each participant will bear its own costs. \n The agreement will not include the transfer of any authority for airspace management or access upon signing. Any approval of airspace use will be handled in accordance with existing FAA policies and procedures. \n The participant will share <span class=\"match\">data</span> with the FAA, as outlined in the agreement, resulting from its development and testing of the operations concepts. Such <span class=\"match\">data</span> will enable the FAA to study the effects"},{"title":"Financial Data Transparency Act Joint Data Standards","type":"Rule","abstract":"The OCC, Board, FDIC, NCUA, CFPB, FHFA, CFTC, SEC, and Treasury are publishing a final joint rule to establish data standards to promote interoperability of financial regulatory data across these agencies. The standards established pursuant to this joint rule will later be considered for potential incorporation (to the extent feasible) into data standards to be adopted for certain collections of information in separate rulemakings by the agencies or through other actions taken by the agencies. At the effective date, the joint rule will not change any reporting requirements without further action by the agencies. The agencies are publishing this joint rule as required by the Financial Data Transparency Act of 2022.","document_number":"2026-12787","html_url":"https://www.federalregister.gov/documents/2026/06/25/2026-12787/financial-data-transparency-act-joint-data-standards","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-25/pdf/2026-12787.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12787.pdf?1782305111","publication_date":"2026-06-25","agencies":[{"raw_name":"DEPARTMENT OF THE TREASURY","name":"Treasury Department","id":497,"url":"https://www.federalregister.gov/agencies/treasury-department","json_url":"https://www.federalregister.gov/api/v1/agencies/497","parent_id":null,"slug":"treasury-department"},{"raw_name":"Office of the Comptroller of the Currency","name":"Comptroller of the Currency","id":80,"url":"https://www.federalregister.gov/agencies/comptroller-of-the-currency","json_url":"https://www.federalregister.gov/api/v1/agencies/80","parent_id":497,"slug":"comptroller-of-the-currency"},{"raw_name":"FEDERAL RESERVE SYSTEM","name":"Federal Reserve System","id":188,"url":"https://www.federalregister.gov/agencies/federal-reserve-system","json_url":"https://www.federalregister.gov/api/v1/agencies/188","parent_id":null,"slug":"federal-reserve-system"},{"raw_name":"FEDERAL DEPOSIT INSURANCE CORPORATION","name":"Federal Deposit Insurance Corporation","id":164,"url":"https://www.federalregister.gov/agencies/federal-deposit-insurance-corporation","json_url":"https://www.federalregister.gov/api/v1/agencies/164","parent_id":null,"slug":"federal-deposit-insurance-corporation"},{"raw_name":"NATIONAL CREDIT UNION ADMINISTRATION","name":"National Credit Union Administration","id":335,"url":"https://www.federalregister.gov/agencies/national-credit-union-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/335","parent_id":null,"slug":"national-credit-union-administration"},{"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"},{"raw_name":"FEDERAL HOUSING FINANCE AGENCY","name":"Federal Housing Finance Agency","id":174,"url":"https://www.federalregister.gov/agencies/federal-housing-finance-agency","json_url":"https://www.federalregister.gov/api/v1/agencies/174","parent_id":null,"slug":"federal-housing-finance-agency"},{"raw_name":"COMMODITY FUTURES TRADING COMMISION","name":"Commodity Futures Trading Commission","id":77,"url":"https://www.federalregister.gov/agencies/commodity-futures-trading-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/77","parent_id":null,"slug":"commodity-futures-trading-commission"},{"raw_name":"SECURITIES AND EXCHANGE COMMISSION","name":"Securities and Exchange Commission","id":466,"url":"https://www.federalregister.gov/agencies/securities-and-exchange-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/466","parent_id":null,"slug":"securities-and-exchange-commission"}],"excerpts":"defined by ISO 4217—Currency Codes. \n \n \n <span class=\"match\">Data</span> transmission and schema and taxonomy format \n \n Formats that, to the extent practicable:\n • Render <span class=\"match\">data</span> fully searchable and machine-readable; \n • Enable high quality <span class=\"match\">data</span> through schemas, with accompanying metadata documented in machine-readable taxonomy or ontology models, which clearly define the semantic meaning of the <span class=\"match\">data</span>, as defined by the underlying regulatory information collection requirements, as appropriate; \n • Ensure that a <span class=\"match\">data</span> element or <span class=\"match\">data</span> asset that exists to satisfy an underlying"},{"title":"Technical Assistance on State Data Collection-IDEA Data Management Center","type":"Proposed Rule","abstract":"The Department of Education (Department) proposes a priority for an IDEA Data Management Center, under the Technical Assistance on State Data Collection program. The Department may use this priority for competitions in fiscal year (FY) 2025 and later years. We take this action to focus attention on an identified national need to provide technical assistance (TA) to improve the capacity of States to meet the data collection requirements under Part B and Part C of the Individuals with Disabilities Education Act (IDEA). The IDEA Data Management Center (Data Management Center) will assist States in collecting, reporting, and determining how to best analyze and use their Part B and Part C data to establish and meet high expectations for each child with a disability by enhancing, streamlining, and integrating IDEA Part B data into their State longitudinal data systems (SLDS), and IDEA Part C data and IDEA Part B preschool special education data into their early childhood integrated data system (ECIDS). A brief summary of the proposed rule is available at www.regulations.gov/docket/ED-2024-OSERS- 0114.","document_number":"2024-25862","html_url":"https://www.federalregister.gov/documents/2024/11/07/2024-25862/technical-assistance-on-state-data-collection-idea-data-management-center","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-11-07/pdf/2024-25862.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-25862.pdf?1730900733","publication_date":"2024-11-07","agencies":[{"raw_name":"DEPARTMENT OF EDUCATION","name":"Education Department","id":126,"url":"https://www.federalregister.gov/agencies/education-department","json_url":"https://www.federalregister.gov/api/v1/agencies/126","parent_id":null,"slug":"education-department"}],"excerpts":"processes to gather <span class=\"match\">data</span> for their required <span class=\"match\">data</span> submissions, resulting in different degrees of reliability in the <span class=\"match\">data</span> collected.\n \n \n \n 3 \n  See \n https://data.ed.gov/dataset/idea-section-618-<span class=\"match\">data</span>-products-state-level-<span class=\"match\">data</span>-files. \n \n \n States with fragmented <span class=\"match\">data</span> systems are more likely to have missing or duplicate <span class=\"match\">data</span>. For example, if a State collects and maintains <span class=\"match\">data</span> on disciplinary removals of children with disabilities in a special education <span class=\"match\">data</span> system but maintains <span class=\"match\">data</span> on the demographics of all children in another <span class=\"match\">data</span> system, the State"},{"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":"necessarily a matter to address in the course of <span class=\"match\">rulemaking</span> nor would taking this action necessarily involve amendments to part 585 or part 563. \n \n On the issue of privacy, NHTSA emphasizes that part 563 does not require EDRs to record personally identifiable <span class=\"match\">data</span>, and captured <span class=\"match\">data</span> in EDRs are continuously overwritten in a temporary buffer, except for specified crash events meeting the trigger threshold to retain <span class=\"match\">data</span>. The Driver Privacy Act of 2015,\n 21 \n \n enacted as part of \n \n the FAST Act, states that <span class=\"match\">data</span> retained by an EDR are the “property of the"},{"title":"ADS-Equipped Vehicle Safety, Transparency, and Evaluation Program; Withdrawal","type":"Proposed Rule","abstract":"This action withdraws the notice of proposed rulemaking (NPRM) published in the Federal Register on January 15, 2025, which proposed to establish the Automated Driving System-Equipped Vehicle Safety, Transparency, and Evaluation Program (AV STEP). The proposal would have created a voluntary program for vehicle manufacturers, developers of Automated Driving Systems (ADS), and fleet operators or system integrators of such vehicles. Based on its reevaluation of the proposal, consideration of the comments received, and subsequent progress on other ADS initiatives, NHTSA is withdrawing the rulemaking.","document_number":"2026-12980","html_url":"https://www.federalregister.gov/documents/2026/06/26/2026-12980/ads-equipped-vehicle-safety-transparency-and-evaluation-program-withdrawal","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-26/pdf/2026-12980.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12980.pdf?1782391522","publication_date":"2026-06-26","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":"ACTION: \n Notice of proposed <span class=\"match\">rulemaking</span>; withdrawal. \n \n \n SUMMARY: \n \n This action withdraws the notice of proposed <span class=\"match\">rulemaking</span> (NPRM) published in the \n Federal Register \n on January 15, 2025, which proposed to establish the Automated Driving System-Equipped Vehicle Safety, Transparency, and Evaluation Program (AV STEP). The proposal would have created a voluntary program for vehicle manufacturers, developers of Automated Driving Systems (ADS), and fleet operators or system <span class=\"match\">integrators</span> of such vehicles. Based on its reevaluation of the proposal"},{"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":"general, “covered <span class=\"match\">data</span>” includes information about transactions, costs, charges, and usage. This coverage is intended to prioritize some of the most beneficial use cases for consumers and leverage <span class=\"match\">data</span> providers' existing capabilities. Clarifying the scope of the <span class=\"match\">data</span> access right will also promote consistency in the <span class=\"match\">data</span> made available to consumers, reduce costs of arranging for access to such <span class=\"match\">data</span>, and focus the development of technical standards around such <span class=\"match\">data</span>. \n Access Requirements \n \n The final rule generally requires a <span class=\"match\">data</span> provider to make"},{"title":"Technical Assistance on State Data Collection-IDEA Data Management Center","type":"Rule","abstract":"The Department of Education (Department) announces a priority for the IDEA Data Management Center (Center) under the Technical Assistance on State Data Collection program. The Department may use this priority in fiscal year (FY) 2025 and later years. This priority replaces the priority published in the Federal Register on August 5, 2014, and the priority published on July 10, 2020. We will use the priority to award a cooperative agreement for a Center to provide technical assistance (TA) to improve the capacity of States to meet the data collection and reporting requirements under Part B and Part C of the Individuals with Disabilities Education Act (IDEA).","document_number":"2025-11608","html_url":"https://www.federalregister.gov/documents/2025/06/25/2025-11608/technical-assistance-on-state-data-collection-idea-data-management-center","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-25/pdf/2025-11608.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-11608.pdf?1750769111","publication_date":"2025-06-25","agencies":[{"raw_name":"DEPARTMENT OF EDUCATION","name":"Education Department","id":126,"url":"https://www.federalregister.gov/agencies/education-department","json_url":"https://www.federalregister.gov/api/v1/agencies/126","parent_id":null,"slug":"education-department"}],"excerpts":"PTAC.\n \n \n Changes: \n None.\n \n Final Priority \n \n IDEA <span class=\"match\">Data</span> Management Center. \n \n Priority \n The purpose of this priority is to fund a cooperative agreement to establish and operate an IDEA <span class=\"match\">Data</span> Management Center (<span class=\"match\">Data</span> Management Center). The <span class=\"match\">Data</span> Management Center will respond to State needs as States determine whether and how to coordinate and <span class=\"match\">integrate</span> their IDEA Part B and Part C <span class=\"match\">data</span> required to meet the <span class=\"match\">data</span> collection requirements in sections 616 and 618 of IDEA into their longitudinal <span class=\"match\">data</span> systems (including SLDS and ECIDS) while ensuring applicable"},{"title":"Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program; Delete, Delete, Delete","type":"Proposed Rule","abstract":"In this document, the Federal Communications Commission (Commission) adopted a Further Notice of Proposed Rulemaking (FNPRM) that seeks comment on eliminating outdated requirements and ways to enhance the efficiency of the Broadband Data Collection (BDC) while ensuring that the Commission continues to receive accurate, granular data. Building off the infrastructure data-based coverage restoration process established by the Commission in 2024, the FNPRM seeks comment on several approaches suggested by commenters to simplify, streamline, or otherwise reduce burdens on this coverage restoration process. The FNPRM seeks comment on several ways to simplify the collection of fixed and fixed wireless biannual submissions, specifically on: (1) either allowing providers to indicate certain fixed broadband availability data have been \"grandfathered\" or else simply eliminating the collection of these data; (2) eliminating the requirement that a provider report fixed broadband availability data at speeds below 25/3 Mbps as part of its biannual submission; (3) revising the Commission's rules to eliminate the requirement for providers to use and disclose maximum buffer size data in their BDC biannual submissions; and (4) revising the Commission's rules to relax the 7 meter antenna height requirement that fixed wireless providers must use when modeling their coverage. In addition, the FNPRM seeks comment on ending legacy data collections for mobile service, specifically the collection of 3G mobile broadband availability data and mobile voice data as part of a provider's biannual submission, including potential impacts on reporting for Alaska and on relevant USF programs, respectively. Furthermore, the FNPRM seeks comment on current data retention practices to develop a set of best practices instead of adopting any substantive rule. The FNPRM seeks comment on several potential challenge process improvements, specifically on: (1) allowing service providers to presumptively rebut certain types of fixed challenges with infrastructure data and on requiring infrastructure data in response to certain types of fixed challenges; (2) various options for simplifying and reducing the provider response periods for the fixed challenge process; (3) streamlining the mobile challenge process by automatically removing from the National Broadband Map (NBM) all challenged areas that are conceded or upheld; and (4) relaxing or removing some current mobile crowdsourced data requirements to encourage the submission of additional data. The FNPRM seeks comment on mobile verification and audit process improvements. The FNPRM also seeks comment on improvements to the collection of mobile crowdsourced data and the use of drone data. Lastly, the FNPRM seeks comment on revising the Commission's rules to expressly provide that subscription data, the geographic coordinates of mobile or fixed wireless base stations, mobile or fixed wireless link budget parameter rationales, and any infrastructure data submitted in response to a verification request or audit will be always treated as confidential.","document_number":"2026-12767","html_url":"https://www.federalregister.gov/documents/2026/06/24/2026-12767/establishing-the-digital-opportunity-data-collection-modernizing-the-fcc-form-477-data-program","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12767.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12767.pdf?1782218725","publication_date":"2026-06-24","agencies":[{"raw_name":"FEDERAL COMMUNICATIONS COMMISSION","name":"Federal Communications Commission","id":161,"url":"https://www.federalregister.gov/agencies/federal-communications-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/161","parent_id":null,"slug":"federal-communications-commission"}],"excerpts":"either on-the-ground test <span class=\"match\">data</span> or infrastructure <span class=\"match\">data</span> to verify its improved coverage. In the \n Fourth Report and Order \n the Commission outlined a requirement for mobile providers that improve coverage following a lost challenge to submit either on-the-ground test <span class=\"match\">data</span> or infrastructure <span class=\"match\">data</span>, but it nevertheless adopted <span class=\"match\">data</span> requirements for restoring Removed \n \n Locations or Areas (\n i.e., \n locations removed from the NBM due to the outcome of challenges, verifications, or audits), that did not include on-the-ground <span class=\"match\">data</span>. The Commission sought comment"},{"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 to enhance Next Generation 911 (NG911) interoperability and improve NG911 accessibility. Specifically, the Further Notice of Proposed Rulemaking proposes requiring NG911 service providers to conduct multi-party interstate interoperability testing of 911 traffic. The Further Notice of Proposed Rulemaking also seeks comment about how 911 Authorities can integrate advanced technology such as Direct Video Calling into NG911 networks to improve accessibility.","document_number":"2026-13999","html_url":"https://www.federalregister.gov/documents/2026/07/10/2026-13999/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-13999.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-13999.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":"ex parte \n presentation was made, and (2) summarize all <span class=\"match\">data</span> presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of <span class=\"match\">data</span> or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such <span class=\"match\">data</span> or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such <span class=\"match\">data</span> or arguments can be found) in lieu of summarizing them"},{"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":"increased <span class=\"match\">data</span>. This revised cost analysis included incremental expenses for upgrading all hardware components necessary for buffering and writing the <span class=\"match\">data</span> to non-volatile memory. Feedback indicated many manufacturers use flash memory (standalone or in microcontrollers) with capacities up to 96 kB to capture EDR <span class=\"match\">data</span>. A few manufacturers are recording pre-crash <span class=\"match\">data</span> at 10 Hz (but not for 20 seconds) while many already capture pre-crash <span class=\"match\">data</span> elements not listed as required <span class=\"match\">data</span> elements to capture in Table I of Part 563. Based on the estimated <span class=\"match\">data</span> increase"},{"title":"Agency Information Collection Activities: Request for Comments; Clearance of a New Approval of Information Collection: Pilot Medical Disclosure Decision Making Model for Safety Risk Assessment Survey","type":"Notice","abstract":"In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the approval of the Office of Management and Budget (OMB) for a new information collection. The Federal Register Notice with a 60-day comment period soliciting comments on the following collection of information was published on June 10, 2025. The collection involves a short online survey gathering information on medical disclosure behaviors of working pilots. The information to be collected will be used to update the current safety risk assessments for integration into the Aviation Safety (AVS), Office of Aviation Medicine (AAM) Safety Risk Management process. The FAA received one comment during the 60-day comment period on the Federal Register. The FAA sincerely thank the Air Line Pilots Association, International (ALPA) for their letter of support and further recommendations for our data collection and study. In the letter, ALPA shared concerns regarding the anonymity of the source, voluntary informed participation, aggregate-only reporting, and response evaluations, which the FAA has recently addressed. We also appreciate ALPA for bringing their concerns of independent oversight and legal data protection to our attention. We will work closely with ALPA representatives to integrate these recommendations throughout our study design. Again, we sincerely thank ALPA for the letter of support and recommendations on the proposed collection of information.","document_number":"2026-00485","html_url":"https://www.federalregister.gov/documents/2026/01/13/2026-00485/agency-information-collection-activities-request-for-comments-clearance-of-a-new-approval-of","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-01-13/pdf/2026-00485.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-00485.pdf?1768225519","publication_date":"2026-01-13","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"}],"excerpts":"pilots. The information to be collected will be used to update the current safety risk assessments for <span class=\"match\">integration</span> into the Aviation Safety (AVS), Office of Aviation Medicine (AAM) Safety Risk Management process.\n \n \n The FAA received one comment during the 60-day comment period on the \n Federal Register \n . The FAA sincerely thank the Air Line Pilots Association, International (ALPA) for their letter of support and further recommendations for our <span class=\"match\">data</span> collection and study. In the letter, ALPA shared concerns regarding the anonymity of the source, voluntary"},{"title":"Pipeline Safety: Integration of Innovative Remote Sensing Technologies for Right-of-Way Patrols on Gas and Hazardous Liquid Pipelines","type":"Proposed Rule","abstract":"PHMSA proposes to clarify that right-of-way patrol requirements are technology neutral, and that operators can use remote sensing technologies, such as unmanned aerial systems and satellites, for complying with gas transmission, hazardous liquid, and carbon dioxide pipeline rights-of-way patrolling requirements.","document_number":"2026-08080","html_url":"https://www.federalregister.gov/documents/2026/04/24/2026-08080/pipeline-safety-integration-of-innovative-remote-sensing-technologies-for-right-of-way-patrols-on","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-04-24/pdf/2026-08080.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-08080.pdf?1776948324","publication_date":"2026-04-24","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":"Pipeline and Hazardous Materials Safety Administration","name":"Pipeline and Hazardous Materials Safety Administration","id":408,"url":"https://www.federalregister.gov/agencies/pipeline-and-hazardous-materials-safety-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/408","parent_id":492,"slug":"pipeline-and-hazardous-materials-safety-administration"}],"excerpts":"5 U.S.C. 601 \n et seq. \n ) requires Federal agencies to conduct an Initial Regulatory Flexibility Analysis (IRFA) for a proposed rule subject to notice-and-comment <span class=\"match\">rulemaking</span> unless the agency head certifies that the <span class=\"match\">rulemaking</span> will not have a significant economic impact on a substantial number of small entities. E.O. 13272, \n Proper Consideration of Small Entities in Agency <span class=\"match\">Rulemaking</span>, \n obliges agencies to establish procedures promoting compliance with the RFA. DOT posts its implementing guidance on a dedicated web page.\n 7 \n \n PHMSA developed"},{"title":"Integration of Powered-Lift: Pilot Certification and Operations; Miscellaneous Amendments Related to Rotorcraft and Airplanes; Correction","type":"Rule","abstract":"On November 21, 2024, the Federal Aviation Administration (FAA) published a final rule titled \"Integration of Powered-Lift: Pilot Certification and Operations; Miscellaneous Amendments Related to Rotorcraft and Airplanes\" (RIN 2120-AL72). That final rule inadvertently duplicated two tables in the regulatory text of the Special Federal Aviation Regulation for powered-lift. This correction removes the duplicates. Additionally, the FAA inadvertently cited an incorrect paragraph in the Training center instructor eligibility requirements section of the Code of Federal Regulations. This correction corrects the paragraph reference.","document_number":"2024-30331","html_url":"https://www.federalregister.gov/documents/2025/01/03/2024-30331/integration-of-powered-lift-pilot-certification-and-operations-miscellaneous-amendments-related-to","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-01-03/pdf/2024-30331.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-30331.pdf?1735825509","publication_date":"2025-01-03","agencies":[{"raw_name":"DEPARTMENT OF TRANSPORTATION","name":"Transportation Department","id":492,"url":"https://www.federalregister.gov/agencies/transportation-department","json_url":"https://www.federalregister.gov/api/v1/agencies/492","parent_id":null,"slug":"transportation-department"},{"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"}],"excerpts":"configuration of six or more seats and for which two pilots are required by type certification or operating rule; § 91.609(d) of this chapter applies to powered-lift required by that section to have a flight <span class=\"match\">data</span> recorder; and § 91.609(i) and (j) of this chapter apply to powered-lift required by that section to have a cockpit voice recorder and a flight <span class=\"match\">data</span> recorder \n \n (1) Operators of powered-lift having a passenger seating configuration, excluding any pilot seat, of 10 or more must comply with § 194.310 or § 194.311 in lieu of the appendices referenced"},{"title":"Order No. 917; Filing Process and Data Collection for the Electric Quarterly Report","type":"Rule","abstract":"The Federal Energy Regulatory Commission adopts eXtensible Business Reporting Language-Comma-Separated Values as the standard for filing the Electric Quarterly Report (EQR). In addition, the Commission amends its regulations to require Regional Transmission Organizations and Independent System Operators to produce reports containing market participant transaction data. The Commission also modifies and clarifies EQR reporting requirements. These changes are designed to update the data collection, improve data quality, increase market transparency, decrease the costs, over time, of preparing the necessary data for submission, and streamline compliance with any future changes to the filing requirements.","document_number":"2026-05709","html_url":"https://www.federalregister.gov/documents/2026/03/24/2026-05709/order-no-917-filing-process-and-data-collection-for-the-electric-quarterly-report","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-03-24/pdf/2026-05709.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-05709.pdf?1774269913","publication_date":"2026-03-24","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":"submission of <span class=\"match\">data</span> on a rolling basis during the filing window using a new append functionality. We clarify that the new system will allow Sellers to file <span class=\"match\">data</span> on a rolling basis within the four-month filing window, which will lead to increased flexibility for Sellers and facilitate the iterative editing functionality sought by ISO-NE. \n 68. Appending <span class=\"match\">data</span> involves adding new rows of <span class=\"match\">data</span> to an already accepted EQR filing, such as adding new rows of <span class=\"match\">data</span> without changing previously submitted and accepted rows of <span class=\"match\">data</span>. We clarify that appending <span class=\"match\">data</span> after"},{"title":"Financial Data Transparency Act Joint Data Standards","type":"Proposed Rule","abstract":"The Office of the Comptroller of the Currency, Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation, National Credit Union Administration, Consumer Financial Protection Bureau, Federal Housing Finance Agency, Commodity Futures Trading Commission, Securities and Exchange Commission, and Department of the Treasury invite public comment on a proposed rule to establish data standards to promote interoperability of financial regulatory data across these agencies. Final standards established pursuant to this rulemaking will later be adopted for certain collections of information in separate rulemakings by the agencies or through other actions taken by the agencies. The agencies are proposing this rule as required by the Financial Data Transparency Act of 2022.","document_number":"2024-18415","html_url":"https://www.federalregister.gov/documents/2024/08/22/2024-18415/financial-data-transparency-act-joint-data-standards","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2024-08-22/pdf/2024-18415.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2024-18415.pdf?1724244317","publication_date":"2024-08-22","agencies":[{"raw_name":"DEPARTMENT OF THE TREASURY","name":"Treasury Department","id":497,"url":"https://www.federalregister.gov/agencies/treasury-department","json_url":"https://www.federalregister.gov/api/v1/agencies/497","parent_id":null,"slug":"treasury-department"},{"raw_name":"Office of the Comptroller of the Currency","name":"Comptroller of the Currency","id":80,"url":"https://www.federalregister.gov/agencies/comptroller-of-the-currency","json_url":"https://www.federalregister.gov/api/v1/agencies/80","parent_id":497,"slug":"comptroller-of-the-currency"},{"raw_name":"FEDERAL RESERVE SYSTEM","name":"Federal Reserve System","id":188,"url":"https://www.federalregister.gov/agencies/federal-reserve-system","json_url":"https://www.federalregister.gov/api/v1/agencies/188","parent_id":null,"slug":"federal-reserve-system"},{"raw_name":"FEDERAL DEPOSIT INSURANCE CORPORATION","name":"Federal Deposit Insurance Corporation","id":164,"url":"https://www.federalregister.gov/agencies/federal-deposit-insurance-corporation","json_url":"https://www.federalregister.gov/api/v1/agencies/164","parent_id":null,"slug":"federal-deposit-insurance-corporation"},{"raw_name":"NATIONAL CREDIT UNION ADMINISTRATION","name":"National Credit Union Administration","id":335,"url":"https://www.federalregister.gov/agencies/national-credit-union-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/335","parent_id":null,"slug":"national-credit-union-administration"},{"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"},{"raw_name":"FEDERAL HOUSING FINANCE AGENCY","name":"Federal Housing Finance Agency","id":174,"url":"https://www.federalregister.gov/agencies/federal-housing-finance-agency","json_url":"https://www.federalregister.gov/api/v1/agencies/174","parent_id":null,"slug":"federal-housing-finance-agency"},{"raw_name":"COMMODITY FUTURES TRADING COMMISSION","name":"Commodity Futures Trading Commission","id":77,"url":"https://www.federalregister.gov/agencies/commodity-futures-trading-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/77","parent_id":null,"slug":"commodity-futures-trading-commission"},{"raw_name":"SECURITIES AND EXCHANGE COMMISSION","name":"Securities and Exchange Commission","id":466,"url":"https://www.federalregister.gov/agencies/securities-and-exchange-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/466","parent_id":null,"slug":"securities-and-exchange-commission"}],"excerpts":"collections of information, submitted <span class=\"match\">data</span> may refer to one or more schemas, taxonomies, or ontology models that describe the syntax, structure, or semantic meaning of the <span class=\"match\">data</span>.\n 50 \n \n These can be used to validate and explain the <span class=\"match\">data</span>. A high-quality machine-readable description of the syntax and structure of a <span class=\"match\">data</span> asset allows for automated verification of the associated <span class=\"match\">data</span> asset. A high-quality machine-readable description of semantic meaning of a <span class=\"match\">data</span> asset ensures that the specific meaning remains clear as the <span class=\"match\">data</span> asset is transmitted to multiple"},{"title":"Technical Assistance on State Data Collection-National Technical Assistance Center To Improve State Capacity To Collect, Report, Analyze, and Use Accurate IDEA Part B and Part C Fiscal Data","type":"Rule","abstract":"The Department of Education (Department) announces the priority for the National Technical Assistance Center to Improve State Capacity to Collect, Report, Analyze, and Use Accurate IDEA Part B and Part C Fiscal Data Center (Fiscal Data Center) under the Technical Assistance on State Data Collection program. The Department may use this priority for competitions in fiscal year (FY) 2025 and later years. This priority replaces the priority published in the Federal Register on August 11, 2014, and the priority published on June 16, 2020. We will use the priority to award a cooperative agreement for a Center to provide technical assistance (TA) to improve the capacity of States to meet the fiscal data collection requirements under Part B and Part C of the Individuals with Disabilities Education Act (IDEA). This Fiscal Data Center will support States in collecting, reporting, and determining how to best analyze and use their IDEA Part B and Part C fiscal data to establish and meet high expectations for each child with a disability and will customize its TA to meet each State's specific needs.","document_number":"2025-11599","html_url":"https://www.federalregister.gov/documents/2025/06/25/2025-11599/technical-assistance-on-state-data-collection-national-technical-assistance-center-to-improve-state","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2025-06-25/pdf/2025-11599.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2025-11599.pdf?1750769110","publication_date":"2025-06-25","agencies":[{"raw_name":"DEPARTMENT OF EDUCATION","name":"Education Department","id":126,"url":"https://www.federalregister.gov/agencies/education-department","json_url":"https://www.federalregister.gov/api/v1/agencies/126","parent_id":null,"slug":"education-department"}],"excerpts":"high-quality IDEA fiscal <span class=\"match\">data</span> to the Department and the public, which should, at a minimum, include providing virtual and on-site consultation to the SEA or LA to— \n \n (\n 1 \n ) Implement model practices for the management of IDEA <span class=\"match\">data</span> and <span class=\"match\">data</span> system <span class=\"match\">integration</span> policies, procedures, processes, and activities within the State;\n \n \n (\n 2 \n ) Develop, use, or adapt tools to meet State-specific IDEA <span class=\"match\">data</span> needs;\n \n \n (\n 3 \n ) Develop a sustainability plan for the State to continue the management of IDEA <span class=\"match\">data</span> and <span class=\"match\">data</span> system <span class=\"match\">integration</span> work in the future;"},{"title":"Request for Information (RFI): Pharmacy Benefit Manager Compensation and Data Collection","type":"Proposed Rule","abstract":"This request for information (RFI) solicits technical input on the services and business practices of pharmacy benefit managers (\"PBMs\") and their affiliates to inform implementation of recent legislation. It specifically focuses on gathering information to inform two specific legislative requirements that are effective beginning calendar year 2028: restrictions on the remuneration that PBMs and their affiliates may receive for services in connection with the utilization of covered Part D drugs; and data reporting requirements.","document_number":"2026-12344","html_url":"https://www.federalregister.gov/documents/2026/06/18/2026-12344/request-for-information-rfi-pharmacy-benefit-manager-compensation-and-data-collection","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-18/pdf/2026-12344.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12344.pdf?1781640907","publication_date":"2026-06-18","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":"relevant input, we are soliciting information from interested parties regarding the topics described in this section for the purpose of informing <span class=\"match\">rulemaking</span> on section 6224 of the CAA, 2026. In preparing submissions, respondents should clearly identify which section(s) of this RFI they are responding to and the circumstances to which their responses relate. We encourage commenters to provide specific examples, <span class=\"match\">data</span>, or documentation where possible. \n A. Definition of “Pharmacy Benefit Manager” \n Section 1860D-12(h)(7)(C) of the Act defines “pharmacy benefit"},{"title":"Joint Request for Comment on Swap and Security-Based Swap Data Reporting","type":"Proposed Rule","abstract":"The Commodity Futures Trading Commission (\"CFTC\") and the Securities and Exchange Commission (\"SEC\") (together, the \"Commissions\") request public comment on potential changes to the design, scope, and structure of swap and security-based swap data reporting requirements.","document_number":"2026-12742","html_url":"https://www.federalregister.gov/documents/2026/06/24/2026-12742/joint-request-for-comment-on-swap-and-security-based-swap-data-reporting","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-24/pdf/2026-12742.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12742.pdf?1782218724","publication_date":"2026-06-24","agencies":[{"raw_name":"COMMODITY FUTURES TRADING COMMISSION","name":"Commodity Futures Trading Commission","id":77,"url":"https://www.federalregister.gov/agencies/commodity-futures-trading-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/77","parent_id":null,"slug":"commodity-futures-trading-commission"},{"raw_name":"SECURITIES AND EXCHANGE COMMISSION","name":"Securities and Exchange Commission","id":466,"url":"https://www.federalregister.gov/agencies/securities-and-exchange-commission","json_url":"https://www.federalregister.gov/api/v1/agencies/466","parent_id":null,"slug":"securities-and-exchange-commission"}],"excerpts":"reference <span class=\"match\">data</span>? If so, please explain the benefits and drawbacks of using such reference <span class=\"match\">data</span>, including: (1) benefits or impacts to public transparency, usability, and accessibility of swap and SBS transaction and pricing <span class=\"match\">data</span>; (2) impediments to accessing reference <span class=\"match\">data</span>; (3) management of changes to the reference <span class=\"match\">data</span> that may occur over time; and (4) costs of maintaining and validating the reference <span class=\"match\">data</span>. In addition to these items, please describe any other risks, benefits, and costs associated with using standardized and static reference <span class=\"match\">data</span>. \n E"},{"title":"General Services Acquisition Regulation; Acquisition of Information and Communication Technology; Notice of Listening Sessions and Request for Comments","type":"Proposed Rule","abstract":"The General Services Administration (GSA) is seeking public comment on the draft of a new General Services Administration Acquisition Regulation (GSAR) clause regarding basic safeguarding of data within Large Language Model Artificial Intelligence Systems (LLMs). Due to the complexity of the issue, GSA is publishing this notification and draft clause to gather feedback from stakeholders before taking future action (e.g., deviation and/or formal rulemaking).","document_number":"2026-12205","html_url":"https://www.federalregister.gov/documents/2026/06/17/2026-12205/general-services-acquisition-regulation-acquisition-of-information-and-communication-technology","pdf_url":"https://www.govinfo.gov/content/pkg/FR-2026-06-17/pdf/2026-12205.pdf","public_inspection_pdf_url":"https://public-inspection.federalregister.gov/2026-12205.pdf?1781613917","publication_date":"2026-06-17","agencies":[{"raw_name":"GENERAL SERVICES ADMINISTRATION","name":"General Services Administration","id":210,"url":"https://www.federalregister.gov/agencies/general-services-administration","json_url":"https://www.federalregister.gov/api/v1/agencies/210","parent_id":null,"slug":"general-services-administration"}],"excerpts":"independently by such Contractor.\n \n \n <span class=\"match\">Data</span> Outputs \n means all <span class=\"match\">data</span>, information, PII, any improvements, enhancements, corrections, annotations, or other modifications made to <span class=\"match\">Data</span> Inputs, or content generated by the LLM in the performance of this contract, including but not limited to responses, results, analyses, anonymized <span class=\"match\">data</span>, derivative <span class=\"match\">data</span>, metadata, logs, synthetic <span class=\"match\">data</span>, and any other output or action produced by the LLM, regardless of whether such output incorporates or is derived from Background <span class=\"match\">Data</span>. This definition specifically excludes"}]}