<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="billres.xsl"?>
<!DOCTYPE bill PUBLIC "-//US Congress//DTDs/bill.dtd//EN" "bill.dtd">
<bill bill-stage="Introduced-in-House" dms-id="H66E3BFE7331F478D95374C85AA01A329" public-private="public" key="H" bill-type="olc">
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/">
<dublinCore>
<dc:title>117 HR 2438 IH: Justice in Forensic Algorithms Act of 2021</dc:title>
<dc:publisher>U.S. House of Representatives</dc:publisher>
<dc:date>2021-04-08</dc:date>
<dc:format>text/xml</dc:format>
<dc:language>EN</dc:language>
<dc:rights>Pursuant to Title 17 Section 105 of the United States Code, this file is not subject to copyright protection and is in the public domain.</dc:rights>
</dublinCore>
</metadata>
<form>
<distribution-code display="yes">I</distribution-code>
<congress display="yes">117th CONGRESS</congress><session display="yes">1st Session</session>
<legis-num display="yes">H. R. 2438</legis-num>
<current-chamber>IN THE HOUSE OF REPRESENTATIVES</current-chamber>
<action display="yes">
<action-date date="20210408">April 8, 2021</action-date>
<action-desc><sponsor name-id="T000472">Mr. Takano</sponsor> (for himself and <cosponsor name-id="E000296">Mr. Evans</cosponsor>) introduced the following bill; which was referred to the <committee-name committee-id="HJU00">Committee on the Judiciary</committee-name>, and in addition to the Committee on <committee-name committee-id="HSY00">Science, Space, and Technology</committee-name>, for a period to be subsequently determined by the Speaker, in each case for consideration of such provisions as fall within the jurisdiction of the committee concerned</action-desc>
</action>
<legis-type>A BILL</legis-type>
<official-title display="yes">To prohibit the use of trade secrets privileges to prevent defense access to evidence in criminal proceedings, provide for the establishment of Computational Forensic Algorithm Testing Standards and a Computational Forensic Algorithm Testing Program, and for other purposes.</official-title>
</form>
<legis-body id="H520926E4868D4635948992F386E2BA97" style="OLC">
<section id="HA6E74AE7C80344D294C7E58F7A9D1E20" section-type="section-one"><enum>1.</enum><header>Short title</header><text display-inline="no-display-inline">This Act may be cited as the <quote><short-title>Justice in Forensic Algorithms Act of 2021</short-title></quote>.</text></section> <section id="H6DF3AA3A12644A66838DFCB4A83F7522"><enum>2.</enum><header>Computational forensic algorithm testing standards</header> <subsection id="HB6BACAF9355640D8966760DAAC86D708"><enum>(a)</enum><header>In general</header><text>Not later than 1 year after the date of enactment of this Act, the Director of the National Institute of Standards and Technology shall establish a program to provide for creation and maintenance of standards for testing computational forensic software, to be known as the Computational Forensic Algorithm Testing Standards, consistent with the following:</text>
<paragraph id="HABE0F7522B3A4D6AB0CAF7D1FD32DBAB"><enum>(1)</enum><text>Testing standards shall include an assessment for the potential for disparate impact, on the basis of race, ethnicity, socioeconomic status, gender, and other demographic features.</text></paragraph> <paragraph id="H33D8315E054C47DD8564A7CE7E525B42"><enum>(2)</enum><text>Testing standards shall address—</text>
<subparagraph id="H0869ADC5F3514D4B91CC538567D5AB76"><enum>(A)</enum><text display-inline="yes-display-inline">the underlying scientific principles and methods implemented in computational forensic software; and</text></subparagraph> <subparagraph id="H80BD91C04ED54489A595A7F9B52F09BE"><enum>(B)</enum><text>requirements for testing the software including the conditions under which it needs to be tested, types of testing data to be used, testing environments, testing methodologies, and system performance statistics required to be reported including—</text>
<clause id="H90DA6508DBBD4554A73EFBB2B8291CD5"><enum>(i)</enum><text>accuracy, including false positive and false negative error rates;</text></clause> <clause id="H2732186E52C54C17925029BDDF9CDE72"><enum>(ii)</enum><text>precision;</text></clause>
<clause id="H7C23FF5504684ACF9F95626375961C95"><enum>(iii)</enum><text>reproducibility;</text></clause> <clause id="HDEFF20BCCD064C99B8AA35B50406264B"><enum>(iv)</enum><text>robustness;</text></clause>
<clause id="H61452ACC07194F7CA75039FD406C8B17"><enum>(v)</enum><text>sensitivity; and</text></clause> <clause id="H430513BDF6954F3898B2F0726615CBAD"><enum>(vi)</enum><text>system failure rates;</text></clause></subparagraph>
<subparagraph id="HA0FAA7E4004F425CB27F90E02EB62AA0"><enum>(C)</enum><text>requirements for publicly available documentation by developers of computational forensic software of the purpose and function of the software, the development process, including source and description of data used to develop the tool, and internal testing methodology and results, including source and description of testing data;</text></subparagraph> <subparagraph id="H5F7F23DD38C84C55B5872866D4039758"><enum>(D)</enum><text>requirements for laboratories and any other entities using computational forensic software to validate it for use, including to specify the conditions under which the lab has validated it for their use, requirements for what information needs to be included in a public report on the lab or other entity’s validation, and requirements for internal validation updates when there are material changes to the software; and</text></subparagraph>
<subparagraph id="H4590ED61C07643C7B0EC3E2173E42C10"><enum>(E)</enum><text>requirements for reports provided to defendants by prosecution produced documenting the use and results of computational forensic software used in individual cases.</text></subparagraph></paragraph> <paragraph id="HE9F98F9B632D41D7AC16CBF9DE7BC0FF"><enum>(3)</enum><text>Testing standards shall be issued as a rulemaking under section 553 of title 5, United States Code.</text></paragraph>
<paragraph id="H612B1D5B00104C5E8F700AF3C3A1CFDA"><enum>(4)</enum><text>The Director shall consult with outside experts in forensic science, bioethics, algorithmic discrimination, data privacy, racial justice, criminal justice reform, exonerations, and other relevant areas of expertise identified through public input.</text></paragraph></subsection> <subsection id="H9B5B010F6A4C47D38188E0415D6938DA"><enum>(b)</enum><header>Protection of trade secrets</header> <paragraph id="H3D7FBF5F712C41EDBD34560F54504066"><enum>(1)</enum><text>There shall be no trade secret evidentiary privilege to withhold relevant evidence in criminal proceedings in the United States courts.</text></paragraph>
<paragraph id="HF9039EF1572A42D89E292F77E1522F8B"><enum>(2)</enum><text>Nothing in this section may be construed to alter the standard operation of the Federal Rules of Criminal Procedure, or the Federal Rules of Evidence, as such rules would function in the absence of an evidentiary privilege.</text></paragraph></subsection> <subsection id="H8CC1D754BFC5424F83BC1FFD91E5F4A7"><enum>(c)</enum><header>Requirements for federal use of forensic algorithms</header><text>Any Federal law enforcement agency or crime laboratory providing services to a Federal law enforcement agency using computational forensic software may use only software that has been tested under the National Institute of Standards and Technology’s Computational Forensic Algorithm Testing Program and shall conduct an internal validation according to the requirements outlined in the Computational Forensic Algorithm Testing Standards and make the results publicly available. The internal validation shall be updated when there is a material change in the software that triggers a retesting by the Computational Forensic Algorithm Testing Program.</text></subsection>
<subsection id="HA0422A0BBA754CE683E163C722002CE6"><enum>(d)</enum><header>Testing program</header><text>The Director of the National Institute of Standards and Technology shall establish a Computational Forensic Algorithm Testing Program, whose activities include the following:</text> <paragraph id="HBC4C434F09224FD285A0A8E3335FEB3A"><enum>(1)</enum><text>Testing individual software programs using the testing requirements established in the Computational Forensic Algorithm Testing Standards.</text></paragraph>
<paragraph id="H69793A2DAB594566904ABA4BBACA526F"><enum>(2)</enum><text>Using realistic sample testing data similar to what would be used by law enforcement in criminal investigations in performing such testing, including incomplete and contaminated samples.</text></paragraph> <paragraph id="HC01FFAC3D4F342DA8085C7A500B97089"><enum>(3)</enum><text>Using testing data that represents diversity of racial, ethnic, and gender identities and intersections of these identities in performing such testing.</text></paragraph>
<paragraph id="HF5583F4C756D43F8BD39F689B9B44846"><enum>(4)</enum><text>Using testing data that tests the limits of the software and demonstrates the boundaries of reliability described in the performance measures defined in the Computational Forensic Algorithm Testing Standards in performing such testing.</text></paragraph> <paragraph id="H23A0A145021440BF9DBD3138CA015058"><enum>(5)</enum><text>Publishing the results of testing the software online including results under conditions specified in the testing standards and across diversity of racial, ethnic, and gender identities and intersections of these identities in a publicly available format.</text></paragraph></subsection>
<subsection id="H9A50960AC9DD4374A04A39E2FF2B0929"><enum>(e)</enum><header>Testing frequency</header><text>Retesting shall be conducted when a material change is made to the software that impacts its performance and may affect its outputs. The Director shall establish requirements for determining whether changes are material or nonmaterial.</text></subsection> <subsection id="H74D17FBD43164980A9E0AB7BEAE184F5"><enum>(f)</enum><header>Use of Computational Forensic Software</header><text>Any results or reports resulting from analysis by computational forensic software shall be provided to the defendant, and the defendant shall be accorded access to both an executable copy of and the source code for the version of the computational forensic software—as well as earlier versions of the software, necessary instructions for use and interpretation of the results, and relevant files and data—used for analysis in the case and suitable for testing purposes. Such a report on the results shall include—</text>
<paragraph id="H32D957B46BD04B4281CFD32E67A7A8B5"><enum>(1)</enum><text>the name of the company that developed the software;</text></paragraph> <paragraph id="H361B41BA9B054481A206417DD5048A1F"><enum>(2)</enum><text>the name of the lab where test was run;</text></paragraph>
<paragraph id="H1B04743A10F14D03B9208C955590318E"><enum>(3)</enum><text>the version of the software that was used;</text></paragraph> <paragraph id="H65A390F778D641A481BFBCCBBA3CBB41"><enum>(4)</enum><text>the dates of the most recent changes to the software and record of changes made, including any bugs found in the software and what was done to address those bugs;</text></paragraph>
<paragraph id="H90247E9CBA6E48D09F5539429FBB22CB"><enum>(5)</enum><text>documentation of procedures followed based on procedures outlined in internal validation;</text></paragraph> <paragraph id="H0065FE4619A248F6BB193DD64C40ABAE"><enum>(6)</enum><text>documentation of conditions under which software was used relative to the conditions under which software was tested; and</text></paragraph>
<paragraph id="HC6429675A2594CE895CBC4144A12BC69"><enum>(7)</enum><text>any other information specified by the Director of the National Institute of Standards and Technology in the Computational Forensic Algorithm Testing Standards.</text></paragraph></subsection> <subsection id="HFCC08D92A1E149EB8B22F6CF737FCC59"><enum>(g)</enum><header>Inadmissibility of certain evidence</header><text>In any criminal case, evidence that is the result of analysis by computational forensic software is admissible only if—</text>
<paragraph id="H5C519CC1BC7C428DBE9092A18B276A98"><enum>(1)</enum><text>the computational forensic software used has been submitted to the Computational Forensic Algorithm Testing Program of the Director of the National Institute of Standards and Technology and there have been no material changes to that software since it was last tested; and</text></paragraph> <paragraph id="H61BA05CAFCEC486D9412BAC6F460EDA7"><enum>(2)</enum><text>the developers and users of the computational forensic software agree to waive any and all legal claims against the defense or any member of its team for the purposes of the defense analyzing or testing the computational forensic software.</text></paragraph></subsection>
<subsection id="H81EF05BBD301443F91A810117D2DEFE8"><enum>(h)</enum><header>Definitions</header><text>In this Act:</text> <paragraph id="H6B967A8FC4AF4DA4839B9686267FF5D3"><enum>(1)</enum><header>Computational forensic software</header><text>The term <quote>computational forensic software</quote> means software that relies on an automated or semiautomated computational process, including one derived from machine learning, statistics, or other data processing or artificial intelligence techniques, to process, analyze, or interpret evidence.</text></paragraph>
<paragraph id="H2500262970A847EC89078CA0D9EC46D9"><enum>(2)</enum><header>Material change</header><text>The term <quote>material change</quote> means an update to computational forensic software that may affect the performance measures defined in the Computational Forensic Algorithm Testing Standards or the use or output of the software.</text></paragraph> <paragraph id="H73FF09078FA3468B9D910B6A815F1A1B"><enum>(3)</enum><header>Nonmaterial change</header><text>The term <quote>nonmaterial change</quote> means an update to computational forensic software that does not affect the performance measures, use, or output of the software.</text></paragraph></subsection></section>
</legis-body>
</bill> 


