<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>BakerHostetler - Alert</title>
        <link>https://www.bakerlaw.com</link>
        <description>BakerHostetler, a national law firm, counseling clients in five core practice groups: Business, Employment, Intellectual Property, Litigation and Tax. Contact us to learn more.</description>
        <lastBuildDate>Thu, 19 Nov 2026 19:01:04 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>Next.js using Feed for Node.js</generator>
        <language>en-US</language>
        <image>
            <title>BakerHostetler - Alert</title>
            <url>https://www.bakerlaw.com/images/logo-32x32.png</url>
            <link>https://www.bakerlaw.com</link>
        </image>
        <atom:link href="https://www.bakerlaw.com/feed/alert/" rel="self" type="application/rss+xml"/>
        <item>
            <title><![CDATA[DOJ Announces Whistleblower Rewards Program with Fast-Track Payments]]></title>
            <link>https://www.bakerlaw.com/insights/doj-announces-whistleblower-rewards-program-with-fast-track-payments/</link>
            <guid>https://www.bakerlaw.com/?p=81843</guid>
            <pubDate>Thu, 19 Nov 2026 16:13:20 GMT</pubDate>
            <description><![CDATA[<p>Key Takeaways</p>
<p><!-- wp:list --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list"><!-- wp:list-item --></p>
<li>On Oct. 20, Attorney General (AG) Todd Blanche and Assistant Attorney General (AAG) Colin M. McDonald, National Fraud Enforcement Division (Fraud Division or Division), announced the creation of the Fraud Whistleblower Incentive Program (WHIP), “the first ever whistleblower rewards program that pays an up-front award for tips leading to criminal charges.”</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Under WHIP, whistleblowers will be eligible for an award of between $10,000 and $30,000 for information leading to criminal charges in particular subject areas, including federal healthcare and government-program-fraud offenses. The payment is tied to the Department of Justice (DOJ), bringing charges as opposed to final resolution of a criminal matter, which can take years.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Whistleblowers remain eligible for larger rewards, after litigation is concluded, if their tips lead to large financial penalties or forfeiture.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>An increase in the volume of fraud investigations and prosecutions based on whistleblower tips is expected. Companies should anticipate that these whistleblower incentives will spur employees to report misconduct if it occurs and that misconduct could be reported to the government before the company learns of it or while it is investigating, complicating the company’s reporting decision and time frame. The combination of WHIP and other recently announced Department policies and programs strongly suggests that prudent companies undertake a dual course of action: (1) Review their compliance policies and procedures and consider conducting risk assessments in an effort to prevent misconduct from occurring; and (2) when potential misconduct is uncovered, quickly engage outside counsel to develop and carry out an investigation strategy that maximizes the potential benefits from and avoids the potential pitfalls of these multiple new DOJ policies and programs.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --></p>
<p><!-- /wp:list --></p>
]]></description>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li>On Oct. 20, Attorney General (AG) Todd Blanche and Assistant Attorney General (AAG) Colin M. McDonald, National Fraud Enforcement Division (Fraud Division or Division), announced the creation of the Fraud Whistleblower Incentive Program (WHIP), “the first ever whistleblower rewards program that pays an up-front award for tips leading to criminal charges.”<a href="#_ftn1" id="_ftnref1">[1]</a></li>



<li>Under WHIP, whistleblowers will be eligible for an award of between $10,000 and $30,000 for information leading to criminal charges in particular subject areas, including federal healthcare and government-program-fraud offenses. The payment is tied to the Department of Justice (DOJ), bringing charges as opposed to final resolution of a criminal matter, which can take years.</li>



<li>Whistleblowers remain eligible for larger rewards, after litigation is concluded, if their tips lead to large financial penalties or forfeiture.</li>



<li>An increase in the volume of fraud investigations and prosecutions based on whistleblower tips is expected. Companies should anticipate that these whistleblower incentives will spur employees to report misconduct if it occurs and that misconduct could be reported to the government before the company learns of it or while it is investigating, complicating the company’s reporting decision and time frame. The combination of WHIP and other recently announced Department policies and programs strongly suggests that prudent companies undertake a dual course of action: (1) Review their compliance policies and procedures and consider conducting risk assessments in an effort to prevent misconduct from occurring; and (2) when potential misconduct is uncovered, quickly engage outside counsel to develop and carry out an investigation strategy that maximizes the potential benefits from and avoids the potential pitfalls of these multiple new DOJ policies and programs.</li>
</ul>



<h2 class="wp-block-heading" id="h-key-details">Key Details</h2>



<p>Earlier this year, DOJ announced a new Corporate Enforcement and Voluntary Self-Disclosure Policy (CEP), detailed in this prior BakerHostetler <a href="https://www.bakerlaw.com/insights/doj-announces-corporate-fraud-enforcement-priorities-companies-take-note/" target="_blank" rel="noreferrer noopener"><em>Insight</em></a>.<a href="#_ftn2" id="_ftnref2">[2]</a> Under the CEP, the Department sought “to incentivize responsible corporate behavior, encouraging companies to invest in effective compliance programs, voluntarily self-report potential misconduct, meaningfully cooperate with law enforcement, and make good-faith efforts to rectify wrongdoing.”<a href="#_ftn3" id="_ftnref3">[3]</a> It offered companies the opportunity to earn multiple self-disclosure benefits in return, including prosecution declinations.<a href="#_ftn4" id="_ftnref4">[4]</a> Shortly thereafter, DOJ created the Fraud Division and tasked it to “zealously investigate and prosecute those who steal or fraudulently misuse taxpayer dollars.”<a href="#_ftn5" id="_ftnref5">[5]</a> On Oct. 1, AAG McDonald issued a memorandum to the Fraud Division that provided additional guidance on the <a href="https://www.bakerlaw.com/insights/doj-announces-corporate-fraud-enforcement-priorities-companies-take-note/#_ftn1" target="_blank" rel="noreferrer noopener">investigation and prosecution of corporate entities</a>, including a directive to Division leadership to design policies and programs that incentivize whistleblowers to report credible information about fraudulent conduct.<a href="#_ftn6" id="_ftnref6">[6]</a></p>



<p>On Oct. 20, AG Blanche and AAG McDonald announced the creation of WHIP, a program offering early payouts to whistleblowers who meet certain criteria.<a href="#_ftn7" id="_ftnref7">[7]</a> AG Blanche said that WHIP “offers everyone the opportunity to be a part of the solution, help expose fraud, and be rewarded quickly for their efforts.”<a href="#_ftn8" id="_ftnref8">[8]</a> AAG McDonald added, “This groundbreaking program will enlist the public as part of the fraud-fighting apparatus and reward them quickly for helping the country in the war on fraud.”<a href="#_ftn9" id="_ftnref9">[9]</a> WHIP was created to “solve a critical gap in existing whistleblower programs.”<a href="#_ftn10" id="_ftnref10">[10]</a></p>



<p>Specifically, WHIP<a href="#_ftn11" id="_ftnref11">[11]</a> will pay whistleblowers an award of $10,000 to $30,000 for information leading to criminal charges in certain subject areas.<a href="#_ftn12" id="_ftnref12">[12]</a> The program will provide rewards for information relating to federal healthcare offenses and related crimes, emphasizing submissions involving hospice, home healthcare, day care and special services fraud.<a href="#_ftn13" id="_ftnref13">[13]</a> The program also offers rewards for fraud perpetrated on government programs and benefits administered by various government agencies.<a href="#_ftn14" id="_ftnref14">[14]</a></p>



<p>WHIP is different from other whistleblower incentive programs because reward payments are tied to DOJ bringing criminal charges in a prosecution  other programs condition the payment of rewards on the final resolution of a criminal matter, including the forfeiture and appeal process.<a href="#_ftn15" id="_ftnref15">[15]</a> “[E]arly-stage rewards encourage prompt disclosure of information by giving whistleblowers more certainty about the amount and timing of a possible reward payment.”<a href="#_ftn16" id="_ftnref16">[16]</a> Moreover, the prosecution need not “result in large fines or forfeiture” for a whistleblower to receive an award.<a href="#_ftn17" id="_ftnref17">[17]</a> Further, these early-stage payments do not preclude whistleblowers from recovering additional amounts if their information ultimately leads to large financial penalties or forfeiture.<a href="#_ftn18" id="_ftnref18">[18]</a> DOJ touts WHIP’s “certainty and speed” as the incentives for citizens to report fraud.<a href="#_ftn19" id="_ftnref19">[19]</a> Awards will be made at DOJ’s sole discretion after criminal charges are filed.<a href="#_ftn20" id="_ftnref20">[20]</a></p>



<h2 class="wp-block-heading" id="h-practical-considerations-for-companies-and-executives">Practical Considerations for Companies and Executives</h2>



<p>WHIP is the latest tool that DOJ is employing to combat fraud. Consistent with prior guidance, WHIP prioritizes certain types of cases by offering rewards in prosecutions involving healthcare fraud, other healthcare-related offenses and fraud on government programs. DOJ further notes that it may expand WHIP to other categories of fraud in the future.<a href="#_ftn21" id="_ftnref21">[21]</a> WHIP’s up-front, fast-track payments provide whistleblowers with more certainty about when they will receive rewards because the payments are tied to the initiation of prosecution rather than to its final resolution. Because these fast-track payments will provide whistleblowers with greater incentives to report, we anticipate a significant uptick in the volume of fraud investigations and prosecutions stemming from whistleblower tips. Companies should understand and anticipate the possibility that a whistleblower employee may report misconduct to DOJ under WHIP before the company uncovers potential fraud or during the company’s investigation of it, complicating the company’s decision about whether to report and the time frame for doing so.</p>



<p>The combination of WHIP and other recently announced DOJ policies and programs strongly recommends that prudent companies undertake a dual course of action: (1) Review their compliance policies and procedures and consider conducting risk assessments in an effort to prevent misconduct from occurring; and (2) when potential misconduct is uncovered, quickly engage outside counsel to develop and carry out an investigation strategy that maximizes the potential benefits from and avoids the potential pitfalls of these multiple new DOJ policies and programs.<a href="#_ftn22" id="_ftnref22">[22]</a></p>



<p>The BakerHostetler White Collar, Investigations and Securities Enforcement and Litigation team and the Criminal Tax Defense team are composed of dozens of experienced individuals, including numerous attorneys who have served in DOJ and at the Securities and Exchange Commission (SEC). Our attorneys include four former U.S. attorneys, several former assistant U.S. attorneys and unit chiefs, attorneys who served in DOJ’s Tax Division, and attorneys who served in the SEC’s Division of Enforcement. Our teams have extensive experience in defending regulatory investigations and litigation, conducting enterprise-wide and business-line and regulatory area-specific risk assessments, and providing compliance counseling.</p>



<p>Please feel free to contact any of our experienced professionals if you have questions about this alert.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p><a href="#_ftnref1" id="_ftn1">[1]</a> Press Release, Dep’t of Justice, <em>Justice Dep’t Announces Innovative Whistleblower Rewards Program to Combat Fraud</em> (Oct. 20, 2026), <em>available at </em><a href="https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud</a>.</p>



<p><a href="#_ftnref2" id="_ftn2">[2]</a> <em>See </em>Memorandum from Assistant Att’y Gen. Colin M. McDonald, <em>Directive 26-12 – Corporate Enforcement in the Fight Against Fraud</em> (Oct. 1, 2026), <em>available at </em><a href="https://www.justice.gov/opa/pr/assistant-attorney-general-colin-m-mcdonald-issues-memorandum-national-fraud-enforcement-0" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/pr/assistant-attorney-general-colin-m-mcdonald-issues-memorandum-national-fraud-enforcement-0</a>; <em>see also </em>U.S. Dep’t of Justice, Justice Manual § 9.28-000 <em>et seq.</em> (2026).</p>



<p><a href="#_ftnref3" id="_ftn3">[3]</a> <em>Id.</em></p>



<p><a href="#_ftnref4" id="_ftn4">[4]</a> <em>Id.</em></p>



<p><a href="#_ftnref5" id="_ftn5">[5]</a> Memorandum from Acting Att’y Gen. Todd Blanche, <em>Creation of the National Fraud Enforcement Division </em>(April 7, 2026), <em>available at</em> <a href="https://www.justice.gov/ag/media/1435311/dl?inline" target="_blank" rel="noreferrer noopener">https://www.justice.gov/ag/media/1435311/dl?inline</a>.</p>



<p><a href="#_ftnref6" id="_ftn6">[6]</a> Memorandum from Assistant Att’y Gen. Colin M. McDonald, <em>Directive 26-12 – Corporate Enforcement in the Fight Against Fraud </em>(Oct. 1, 2026), <em>available at</em> <a href="https://www.justice.gov/opa/media/1463571/dl?inline" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/media/1463571/dl?inline</a>. The directives in this and AAG McDonald’s other memoranda apply only to matters supervised by the Fraud Division, although the Division will continue to work closely with U.S. attorney’s offices and other Main Justice components.</p>



<p><a href="#_ftnref7" id="_ftn7">[7]</a> Press Release, Dep’t of Justice, <em>Justice Dep’t Announces Innovative Whistleblower Rewards Program to Combat Fraud</em> (Oct. 20, 2026), <em>available at </em><a href="https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud</a>.</p>



<p><a href="#_ftnref8" id="_ftn8">[8]</a> <em>Id.</em></p>



<p><a href="#_ftnref9" id="_ftn9">[9]</a> <em>Id.</em></p>



<p><a href="#_ftnref10" id="_ftn10">[10]</a> <em>Id.</em></p>



<p><a href="#_ftnref11" id="_ftn11">[11]</a> For unclear reasons, in its explanatory documents, the Fraud Division instead refers to the WHIP as the Division’s “Criminal Tip Rewards Pilot Program” and as the “Fraud Rewards Program.” <em>National Fraud Enforcement Division Criminal Tip Rewards Pilot Program</em> (Oct. 20, 2026), <em>available at</em> <a href="https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program" target="_blank" rel="noreferrer noopener">https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program</a>, <em>linked to and cited in</em> <em>Fraud Whistleblower Incentive Program (WHIP) </em>(Oct. 28, 2026), <em>available at</em> <a href="https://www.justice.gov/fraud/whistleblower" target="_blank" rel="noreferrer noopener">https://www.justice.gov/fraud/whistleblower</a>, at “External Guidance Terms and Conditions.” Based on the Department-provided links and content, however, these programs are one and the same.</p>



<p><a href="#_ftnref12" id="_ftn12">[12]</a> <em>National Fraud Enforcement Division Criminal Tip Rewards Pilot Program</em> (Oct. 20, 2026), <em>available at</em> <a href="https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program" target="_blank" rel="noreferrer noopener">https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program</a>.</p>



<p><a href="#_ftnref13" id="_ftn13">[13]</a> <em>Id.</em></p>



<p><a href="#_ftnref14" id="_ftn14">[14]</a> <em>Id. </em>Specifically, WHIP is also available to whistleblowers who provide information pertaining to fraud perpetrated on programs or benefits administered by the following federal departments: Agriculture, Labor, Health and Human Services, Housing and Urban Development, Education, and War (Defense), as well as the Small Business Administration. <em>Id.</em></p>



<p><a href="#_ftnref15" id="_ftn15">[15]</a> <em>Id.; see also </em>BakerHostetler<em> Insights:</em> DOJ Announces First-Ever Whistleblower Reward Just Six Months After Launching Rewards Program(<a href="https://www.bakerlaw.com/insights/doj-antitrust-division-announces-first-ever-whistleblower-reward-just-six-months-after-launching-rewards-program/">https://www.bakerlaw.com/insights/doj-antitrust-division-announces-first-ever-whistleblower-reward-just-six-months-after-launching-rewards-program/</a>) (paying reward to whistleblower who reported corporate misconduct to the Antitrust Division after reaching a deferred prosecution agreement with the corporate entity). </p>



<p><a href="#_ftnref16" id="_ftn16">[16]</a> <em>Fraud Whistleblower Incentive Program (WHIP) </em>(Oct. 28, 2026), <em>available at</em> <a href="https://www.justice.gov/fraud/whistleblower" target="_blank" rel="noreferrer noopener">https://www.justice.gov/fraud/whistleblower</a>.</p>



<p><a href="#_ftnref17" id="_ftn17">[17]</a> <em>Id.</em></p>



<p><a href="#_ftnref18" id="_ftn18">[18]</a> <em>Id.</em></p>



<p><a href="#_ftnref19" id="_ftn19">[19]</a> Press Release, Dep’t of Justice, <em>Justice Dep’t Announces Innovative Whistleblower Rewards Program to Combat Fraud</em> (Oct. 20, 2026), <em>available at </em><a href="https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/pr/justice-department-announces-innovative-whistleblower-rewards-program-combat-fraud</a>.</p>



<p><a href="#_ftnref20" id="_ftn20">[20]</a> <em>National Fraud Enforcement Division Criminal Tip Rewards Pilot Program</em> (Oct. 20, 2026), <em>available at</em> <a href="https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program" target="_blank" rel="noreferrer noopener">https://www.justice.gov/fraud/national-fraud-enforcement-division-criminal-tip-rewards-pilot-program</a>.</p>



<p><a href="#_ftnref21" id="_ftn21">[21]</a> <em>Id.</em></p>



<p><a href="#_ftnref22" id="_ftn22">[22]</a> Importantly, notwithstanding DOJ’s current priorities, statutes of limitations for employee misconduct frequently extend beyond a single administration’s term. Companies should continue to be diligent about co</p>
]]></content:encoded>
            <dc:creator><![CDATA[Robb C. Adkins, Jonathan R. Barr, Patrick T. Campbell, John J. Carney, C. Shawn Cleveland, Jimmy Fokas, Cornelia Brandfield-Harvey, Ryan S. Hedges, Kristen L. Jackson, Rebecca Chattin Lutzko, Artie McConnell, Brian F. McEvoy, Kimberly S. Morris, Justin P. Murphy, Jonathan B. New, Carlos F. Ortiz, Christos G. Papapetrou, Jacqueline Romero, Jennifer G. Solari, George A. Stamboulidis, Michelle N. Tanney]]></dc:creator>
            <category>Alert</category>
            <category>Litigation</category>
            <category>White Collar, Investigations and Securities Enforcement and Litigation</category>
            <category>Antitrust and Competition</category>
        </item>
        <item>
            <title><![CDATA[Workplace AI Tools May Expose California Employers to Wage-and-Hour Liability]]></title>
            <link>https://www.bakerlaw.com/insights/workplace-ai-tools-may-expose-california-employers-to-wage-and-hour-liability/</link>
            <guid>https://www.bakerlaw.com/?p=81761</guid>
            <pubDate>Thu, 19 Nov 2026 14:01:18 GMT</pubDate>
            <description><![CDATA[<p><!-- wp:heading --></p>
<h2 id="h-key-takeaways" class="wp-block-heading">Key Takeaways</h2>
<p><!-- /wp:heading --> <!-- wp:list --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list"><!-- wp:list-item --></p>
<li>AI tools can create wage-and-hour risks when used to track productivity, schedule shifts or automate timekeeping decisions.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>AI-generated data may become evidence in claims involving missed breaks, off-the-clock work or employee misclassification.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Employers should audit AI systems and maintain human oversight to help ensure wage-and-hour compliance.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --></p>
<p><!-- /wp:list --></p>
]]></description>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li>AI tools can create wage-and-hour risks when used to track productivity, schedule shifts or automate timekeeping decisions.</li>



<li>AI-generated data may become evidence in claims involving missed breaks, off-the-clock work or employee misclassification.</li>



<li>Employers should audit AI systems and maintain human oversight to help ensure wage-and-hour compliance.</li>
</ul>



<p>Recent discussions surrounding employers’ use of AI and algorithmic tools in the workplace have largely centered on the risk of prohibited discrimination against applicants and employees. However, as these tools become increasingly integrated into companies’ daily operations, employers in California and beyond should also evaluate whether such tools expose them to wage-and-hour risk.</p>



<h2 class="wp-block-heading" id="h-california-laws-increase-scrutiny-of-workplace-ai">California Laws Increase Scrutiny of Workplace AI</h2>



<p>Legislators have already begun scrutinizing employers’ use of AI tools in the workplace. In California, the “No Robo Bosses Act” (SB 947), effective July 1, 2027, will prohibit employers from relying solely on automated decision systems (ADSs) to decide whether to discipline or terminate an employee. For instance, one might imagine a scenario in which a productivity-tracking system flags an employee for extended inactivity and automatically recommends discipline, but it could be that such inactivity occurred during the employee’s legally required meal break. Thus, where an ADS’s output is a primary basis for the decision to discipline or terminate, a human must independently review the decision. Similarly, AB 1883, effective January 1, 2027, is a California law that will restrict employers’ use of AI surveillance tools that scan and infer employees’ emotional states or track neural data. Legislative action will only increase as employers use AI in new ways to track and manage employees, not just recruit them.</p>



<h2 class="wp-block-heading" id="h-ai-tools-can-create-wage-and-hour-compliance-risks">AI Tools Can Create Wage-and-Hour Compliance Risks</h2>



<p>Automated or AI-enabled tools may also expose employers to significant litigation risk. In California, employers are generally required to provide 30-minute, duty-free meal periods to non-exempt employees working over five hours, as well as paid, duty-free rest periods for every four hours worked or major fraction thereof. Many algorithmic tools create a detailed record of employee activity, which plaintiffs may cite as evidence that their employer knew about wage-and-hour violations, regardless of whether the employer actually had such knowledge. Additionally, automated or AI-enabled tools themselves may inadvertently operate in a way that violates employees’ rights, and because they are typically introduced across an entire workforce, their errors can be systemic in a way that poses significant class or representative action liability.</p>



<p>For example, some employers are introducing automated productivity-tracking software that monitors and records employees’ keystrokes, chat volume, and other metrics of productivity. While the data generated may be helpful to assess an employee’s productivity level, it may also be used as evidence that employees worked through their required meal breaks or worked off the clock. Moreover, if employees are aware that their productivity is tracked and that periods of inactivity may lead to discipline, they may be discouraged from taking their legally required meal or rest breaks. The system itself can also create unpaid wage and payroll issues if it equates inactivity with non-compensable time, since employees could simply be performing compensable tasks that do not require a computer. Additionally, some employers use AI tools to automate and optimize employee scheduling by predicting staffing needs and allocating shifts accordingly. However, if AI-generated schedules are not reviewed for wage-and-hour compliance, they may create issues such as delayed or shortened meal or rest breaks or unapproved overtime.</p>



<p>AI tools may also present challenges relevant to employee classification as exempt or non-exempt. If AI or automated systems are used in a way that dictates or replaces much of exempt employees’ judgment or decision-making, plaintiffs classified by employers as exempt may argue that they exercised less discretion than an exempt classification would require.</p>



<h2 class="wp-block-heading" id="h-how-employers-can-mitigate-ai-related-wage-and-hour-risk">How Employers Can Mitigate AI-Related Wage-and-Hour Risk</h2>



<p>To mitigate these risks, employers should identify any automated or AI-enabled systems involved in scheduling, payroll, timekeeping, or employee monitoring and audit them for compliance with California wage-and-hour laws. These systems should also incorporate a certain degree of human review and provide employees with a way to dispute any inaccurate outputs.</p>



<p>While automating processes and implementing AI tools can help employers decrease costs and increase efficiency, the data generated also makes wage-and-hour claims easier than ever to argue and prove. That said, AI can act as a powerful tool to track and confirm wage-and-hour compliance. AI tools can flag issues such as off-the-clock work, missed or late meal and rest breaks, and payroll anomalies well before a manager might notice any discrepancies, allowing these issues to be investigated and remedied before becoming widespread. As AI tools grow in sophistication and prevalence, employers will have to balance the advantages and risks of their implementation.</p>



<p>Please contact the authors of this alert or your BakerHostetler attorney contact if you have any questions.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Shareef Farag, Michelle S. Solarczyk]]></dc:creator>
            <category>Alert</category>
            <category>Labor and Employment</category>
            <category>California Labor and Employment</category>
            <category>Wage and Hour Compliance</category>
        </item>
        <item>
            <title><![CDATA[CBP Tightens Requirements for Foreign Importers of Record and Customs Brokers]]></title>
            <link>https://www.bakerlaw.com/insights/cbp-tightens-requirements-for-foreign-importers-of-record-and-customs-brokers/</link>
            <guid>https://www.bakerlaw.com/?p=81785</guid>
            <pubDate>Tue, 17 Nov 2026 21:41:18 GMT</pubDate>
            <description><![CDATA[<p><!-- wp:heading --></p>
<h2 id="h-key-takeaways" class="wp-block-heading">Key Takeaways</h2>
<p><!-- /wp:heading --> <!-- wp:list --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list"><!-- wp:list-item --></p>
<li><strong>U.S. formation is no longer dispositive.</strong> A U.S.-organized entity must also be located in the United States and continuously meet an ownership and control or real property test.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li><strong>The rule looks through corporate ownership.</strong> Beneficial owners are natural persons identified through at least 25 percent ownership or substantial control.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li><strong>Many foreign-owned U.S. subsidiaries require review.</strong> Some entities that historically entered merchandise as U.S. IORs may be foreign IORs under the new definition.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li><strong>A non-Customs Trade Partnership Against Terrorism (CTPAT) foreign IOR needs a CTPAT-validated broker.</strong> A customs broker license by itself is insufficient.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li><strong>Brokers must verify and document U.S. IOR status.</strong> The obligation includes record retention and continuing diligence as client circumstances change.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --></p>
<p><!-- /wp:list --></p>
]]></description>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li><strong>U.S. formation is no longer dispositive.</strong> A U.S.-organized entity must also be located in the United States and continuously meet an ownership and control or real property test.</li>



<li><strong>The rule looks through corporate ownership.</strong> Beneficial owners are natural persons identified through at least 25 percent ownership or substantial control.</li>



<li><strong>Many foreign-owned U.S. subsidiaries require review.</strong> Some entities that historically entered merchandise as U.S. IORs may be foreign IORs under the new definition.</li>



<li><strong>A non-Customs Trade Partnership Against Terrorism (CTPAT) foreign IOR needs a CTPAT-validated broker.</strong> A customs broker license by itself is insufficient.</li>



<li><strong>Brokers must verify and document U.S. IOR status.</strong> The obligation includes record retention and continuing diligence as client circumstances change.</li>
</ul>



<p>Beginning Jan. 5, 2027, a U.S.-organized company will not qualify as a U.S. Importer of Record (IOR) based solely on its incorporation, address or employer identification number (EIN).</p>



<p>U.S. Customs and Border Protection (CBP) has issued an interim final rule establishing new standards for determining whether an individual or entity qualifies as a U.S. IOR. The rule also restricts how foreign IORs may enter merchandise and requires customs brokers to verify clients that claim U.S. IOR status. The rule takes effect Jan. 5, 2027 – the same date comments are due.</p>



<p>The rule may have its greatest practical effect on foreign-owned U.S. subsidiaries. A company organized in the United States must also be located here and continuously satisfy either a U.S. beneficial ownership and control test or a U.S. real property test. An entity that does not meet one of those requirements will be treated as a foreign IOR, even if it is incorporated in the United States and has historically entered merchandise under a U.S. address and EIN.</p>



<p>Importers should evaluate each entity that serves as an IOR before Jan. 5. Customs brokers should identify clients claiming U.S. IOR status, establish procedures for reviewing supporting records and determine which foreign IOR relationships depend on the broker’s CTPAT validation.</p>



<h2 class="wp-block-heading">The Rule Is Part of a Broader Importer Identity Initiative</h2>



<p>The interim final rule implements part of Executive Order 14411, “Strengthening Customs Enforcement,” signed on June 3. The executive order directed the Department of Homeland Security and CBP to revise importer eligibility requirements, obtain additional ownership and asset information, and impose additional restrictions on foreign IORs.</p>



<p>CBP took an initial implementation step in August 2026, when it announced enhanced enforcement to verify information submitted on CBP Form 5106. That initiative began Sept. 18 and permits CBP to void IOR numbers immediately when the agency determines that Form 5106 information is inaccurate.</p>



<p>The new rule goes further by creating formal regulatory definitions of U.S. and foreign IORs, requiring declarations of U.S. IOR status at entry and entry summary, restricting entry by foreign IORs, and imposing new verification duties on licensed customs brokers. CBP adopted the rule to improve its ability to identify the parties behind import transactions, collect unpaid duties, and enforce customs laws against importers whose operations and assets may be outside the United States.</p>



<h2 class="wp-block-heading">Who Qualifies as a US IOR?</h2>



<p>New Part 110 of CBP’s regulations establishes separate requirements for individuals and entities.</p>



<p>An individual qualifies as a U.S. IOR if the individual is a U.S. citizen or lawful permanent resident.</p>



<p>An entity must satisfy three requirements:</p>



<ol class="wp-block-list">
<li>It must be organized under U.S. law.</li>



<li>It must be located in the United States.</li>



<li>It must, at all times, satisfy either the U.S. beneficial ownership and control test or the qualifying U.S. real property test.</li>
</ol>



<p>An IOR that does not meet these requirements is a foreign IOR.</p>



<h2 class="wp-block-heading">Being organized in the United States is not sufficient</h2>



<p>Whether an entity is “located” in the United States is a separate, fact-specific requirement. CBP may consider the entity’s principal place of business, U.S. physical presence and business activities, domestic assets, real property ownership, profitability and capitalization. CBP may also consider the size and scale of the entity’s overall operations and whether it functions as an instrumentality of a foreign manufacturer without a substantial U.S. presence.</p>



<p>The rule also defines “physical domestic assets” as cash deposited in a U.S. bank account, U.S. Treasury bonds, and U.S.-located real property, inventory, machinery and equipment. CBP deliberately excluded accounts receivable from the definition. These assets may be relevant to CBP’s evaluation of whether an entity is genuinely located in the United States and has assets available to satisfy customs liabilities.</p>



<p>U.S. formation, an EIN or a U.S. mailing address will not, standing alone, establish U.S. IOR status.</p>



<h2 class="wp-block-heading">The beneficial ownership test scours entity ownership</h2>



<p>Under the first alternative, at least 51 percent of the entity’s beneficial owners must be U.S. citizens or lawful permanent residents and have control of the entity.</p>



<p>For purposes of this rule, a “beneficial owner” is a natural person who, directly or indirectly, exercises substantial control over the entity or owns or controls at least 25 percent of its ownership interests.</p>



<p>Substantial control may arise from serving as a senior officer, having authority to appoint or remove certain officers or exercising important decision-making authority over the company’s business, finances or structure. The rule pierces multiple tiers of entity ownership to the underlying natural persons. It also provides that every entity should have at least one beneficial owner and may have multiple beneficial owners.</p>



<p>This definition creates a potentially significant issue for multinational corporate groups. A U.S.-organized subsidiary ultimately owned or controlled by foreign natural persons may fail the beneficial ownership alternative even if it has substantial U.S. operations.</p>



<h2 class="wp-block-heading">US real property may provide an alternative</h2>



<p>An entity that does not meet the beneficial ownership and control test may still qualify as a U.S. IOR if it directly owns a significant amount of unencumbered real property in the United States at all times. The property may be subject to some encumbrance, but its net unencumbered value must remain significant.</p>



<p>The rule does not establish a dollar amount, percentage or valuation test for determining what constitutes a “significant amount.” Entities relying on this alternative will therefore need to assess both direct ownership and net unencumbered value and should be prepared to substantiate that position.</p>



<h2 class="wp-block-heading">What Changes for Foreign IORs?</h2>



<p>A foreign IOR that is CTPAT-validated and otherwise has the right to make entry may enter merchandise itself or use a licensed customs broker.</p>



<p>A foreign IOR that is not CTPAT-validated may not make entry on its own behalf. It must designate a licensed customs broker that is CTPAT-validated to make entry on its behalf. A broker license alone does not satisfy this requirement.</p>



<p>Only Canadian foreign IORs are currently eligible for CTPAT validation in the applicable foreign manufacturer or foreign importer category. Many other foreign IORs will therefore depend on a CTPAT-validated customs broker to continue entering merchandise.</p>



<p>The rule applies to formal consumption entries and covered informal consumption entries. CBP’s entry systems may reject an entry summary involving a foreign IOR if the applicable CTPAT requirement is not met.</p>



<h2 class="wp-block-heading">The rule does not yet prohibit informal entry by foreign IORs</h2>



<p>Executive Order 14411 directed CBP toward prohibiting foreign IORs from filing informal entries. CBP did not adopt that prohibition in the interim final rule. Instead, a CTPAT-validated foreign IOR may continue making qualifying informal entries and a non-CTPAT foreign IOR may make qualifying informal entries through a licensed, CTPAT-validated broker.</p>



<p>CBP intends to monitor those transactions and has requested comments on whether foreign IORs should ultimately be prohibited from using informal entry. This remains an important open issue for businesses that rely on entry type 11 or other informal entry procedures.</p>



<h2 class="wp-block-heading">US IORs Must Declare and Support Their Status</h2>



<p>Beginning Jan. 5, 2027, filers must complete the new “U.S. Importer of Record” field on CBP Forms 3461 and 7501 and their electronic equivalents at entry and entry summary. CBP’s Cargo Systems Messaging Service (CSMS) #70381183 instructs filers to select “Y” when the IOR meets the U.S. IOR criteria or, when a broker acts as the IOR, the principal listed on the power of attorney (POA) meets those criteria. Filers must select “N” when the IOR or applicable principal does not meet the criteria; they should not leave the field blank to indicate foreign IOR status.</p>



<p>The forms also include an “Acting on behalf of” field. A customs broker must select “Y” when it lists itself as both filer and IOR to file an entry on behalf of a principal; otherwise, the field must be marked “N.” When a broker acts as the IOR, the U.S. IOR declaration therefore turns on the applicable principal’s qualifications, not simply the broker’s own U.S. status.</p>



<p>The “Principal on Power of Attorney” field is required when a broker that is not CTPAT-validated acts as the IOR on behalf of a principal. The broker must report the principal’s IOR number – such as a Social Security number, an EIN or a CBP-assigned number – linked to the principal’s CBP Form 5106. CBP states that, beginning Jan. 5, 2027, it may reject entries and entry summaries if a non-CTPAT-validated broker acting as an IOR fails to identify the principal when required or a foreign IOR attempts to file without either its own CTPAT validation or a CTPAT-validated customs broker.</p>



<p>These filing instructions are set out in <a href="https://content.govdelivery.com/accounts/USDHSCBP/bulletins/431ee7f" target="_blank" rel="noreferrer noopener">CBP’s CSMS #70381183, issued Nov. 6</a>.</p>



<p>Importers claiming U.S. IOR status should be prepared to substantiate the determination before the first affected entry is filed. Relevant records may include formation and governance documents, citizenship or residency records, ownership information, financial statements, purchase records, bank records, and documents establishing ownership and value of U.S. property.</p>



<p>An inaccurate U.S. IOR declaration gives CBP additional grounds to impose live entry or discontinue immediate-delivery privileges. Live entry requires the importer to file the entry summary and deposit estimated duties, taxes and fees before CBP releases the merchandise. The amended regulations permit CBP to impose these consequences on both formal and informal entries.</p>



<p>Inaccurate declarations may also implicate CBP’s existing civil and administrative enforcement authorities, depending on the facts.</p>



<h2 class="wp-block-heading">Customs Brokers Face New Verification and Recordkeeping Duties</h2>



<p>Before filing a U.S. IOR declaration for a client, a customs broker must exercise due diligence by requesting and reviewing records establishing that the client meets the requirements of new Section 110.2. If the broker determines that the client is not a U.S. IOR, a broker that is not CTPAT-validated must cease filing entries for that client.</p>



<p>The broker must retain records supporting its verification for five years from the verification date. This obligation is separate from the general rule requiring most broker records to be retained for at least five years after the date of entry.</p>



<p>Verification should not be treated solely as an onboarding exercise. CBP’s implementation materials instruct brokers to exercise continuing due diligence because a client’s status can change through changes in ownership, control, operations or property holdings. Brokers should therefore establish triggers for reassessing U.S. IOR status during an active client relationship.</p>



<h2 class="wp-block-heading">A POA is required when the broker acts as the IOR</h2>



<p>The rule amends 19 C.F.R. § 141.46 to require an executed POA whenever a broker conducts customs business on behalf of a principal, including when the broker makes entry in its own name as the IOR.</p>



<p>This amendment changes the treatment reflected in prior CBP rulings, including Headquarters Ruling Letter 223772, which concluded that a POA was not required when a broker made entry in its own name as the IOR. CBP states that the amendment supersedes prior rulings to the extent they are inconsistent with the new requirement.</p>



<p>Brokers that use broker-as-IOR arrangements should review those arrangements and confirm that they have an executed, current POA and an identifiable principal supported by Form 5106.</p>



<h2 class="wp-block-heading">The rule increases broker enforcement exposure</h2>



<p>The rule also amends CBP’s penalty guidelines in Appendix B to Part 171. CBP indicates that customs brokers may face liability under 19 U.S.C. § 1592 for violations connected to the new requirements, in addition to CBP’s administrative remedies under 19 U.S.C. § 1641.</p>



<p>That change makes the verification process more than a documentation exercise. Brokers should establish a consistent decision process, preserve the basis for each determination, and escalate cases involving complex ownership or uncertain U.S. presence before filing a U.S. IOR declaration.</p>



<h2 class="wp-block-heading">What Importers and Brokers Should Do Before Jan. 5</h2>



<h3 class="wp-block-heading">Importers</h3>



<ul class="wp-block-list">
<li>Map each U.S. import flow to the legal entity currently serving as the IOR.</li>



<li>Evaluate each entity separately under the location, beneficial ownership and control and real property requirements.</li>



<li>Identify all natural persons who may qualify as beneficial owners through either ownership or substantial control.</li>



<li>Inventory relevant U.S. operations and physical domestic assets, including cash in U.S. bank accounts, Treasury bonds, inventory, machinery, equipment and real property.</li>



<li>Assemble records supporting the U.S. IOR determination before asking a broker to make the declaration.</li>



<li>Verify whether an entity being treated as a foreign IOR is CTPAT-validated or its broker is both licensed and CTPAT-validated.</li>



<li>Reconcile Forms 5106, 3461 and 7501, POAs, bonds, Automated Commercial Environment (ACE) data, and written broker instructions with the intended structure.</li>



<li>Consider submitting comments by Jan. 5 if the company’s ownership structure, U.S. presence, real property holdings or use of informal entry exposes an unresolved issue under the rule.</li>
</ul>



<h3 class="wp-block-heading">Customs brokers</h3>



<ul class="wp-block-list">
<li>Divide current clients into those claiming U.S. IOR status and those treated as foreign IORs.</li>



<li>Develop a documented verification process tied to the requirements of Section 110.2.</li>



<li>Determine which foreign IOR relationships require the broker’s CTPAT validation.</li>



<li>Confirm that client identification, POA and Form 5106 records identify the actual principal and support the entry structure.</li>



<li>Retain U.S. IOR verification records for five years from the verification date.</li>



<li>Establish reassessment triggers for changes in ownership, control, senior management, U.S. operations, capitalization or qualifying real property.</li>



<li>Update ACE filing systems and procedures for the new Form 3461 and Form 7501 fields.</li>



<li>Train personnel not to select the U.S. IOR declaration based only on a U.S. address, EIN or place of formation.</li>
</ul>



<p>Brokers that need additional time to implement the new verification process may request delayed compliance before Jan. 5, 2027, if they satisfy the rule’s conditions. Brokers receiving approval must be in full compliance no later than May 6, 2027. The extension applies to the broker verification requirement and does not postpone the remainder of the rule.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Matthew W. Caligur, Michael S. Snarr]]></dc:creator>
            <category>Alert</category>
            <category>Litigation</category>
            <category>International Trade and National Security</category>
            <category>Trump Administration Resource Center</category>
            <category>Tariffs and Customs Duties</category>
        </item>
        <item>
            <title><![CDATA[Federal AI Policy in 2027: What Companies Should Expect from the Next Congress]]></title>
            <link>https://www.bakerlaw.com/insights/federal-ai-policy-in-2027-what-companies-should-expect-from-the-next-congress/</link>
            <guid>https://www.bakerlaw.com/?p=81605</guid>
            <pubDate>Tue, 17 Nov 2026 13:00:00 GMT</pubDate>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li><strong>Federal artificial intelligence (AI) policy is likely to divide along institutional lines in 2027.</strong> The Trump administration will continue to emphasize American technological leadership, infrastructure development and regulatory restraint, while the Democratic-controlled Congress is expected to focus more heavily on safety, accountability, consumer protection and the costs associated with AI. When the 120th Congress convenes in January 2027, AI policy is likely to look markedly different from the federal approach of the past two years.</li>



<li><strong>Congressional oversight may move faster than legislation.</strong> New congressional leadership will control committee agendas, hearing calendars and subpoena authority, giving Congress the ability to compel testimony and documents from AI developers and other companies concerning model safety, cybersecurity incidents, testing, data practices and other AI risks.</li>



<li><strong>Pending legislation identifies the controls Congress may expect, even if the bills do not become law. </strong>Legislative proposals from the current Congress provide a preview of what may come next: independent testing of frontier models, incident reporting, government oversight and human-controlled shutdown capabilities. These measures provide a useful indication of the governance practices likely to receive congressional attention in the next session. The bipartisan FRONTIER Act,<a href="#_ftn1" id="_ftnref1">[1]</a> for example, would create a federal oversight regime for frontier AI and independent assessment of certain developers’ safety practices.</li>



<li><strong>Regulatory fragmentation may persist.</strong> Presidential veto authority, Senate procedural requirements and continuing disagreements over the appropriate scope of AI regulation make enactment of a comprehensive federal statute uncertain. Companies should therefore prepare for overlapping federal oversight, executive action, state regulation, agency enforcement and private litigation rather than presume that a single national framework will emerge.</li>
</ul>



<h2 class="wp-block-heading" id="h-a-two-federal-ai-agendas">A. Two Federal AI Agendas</h2>



<p>For much of the past two years, federal AI policy has largely been developed through executive action rather than comprehensive legislation. The Trump administration has emphasized innovation, American technological competitiveness, infrastructure development and reducing regulatory barriers to AI deployment. <a href="https://www.bakerlaw.com/insights/navigating-the-emerging-federal-state-ai-showdown-doj-establishes-ai-litigation-task-force/">As we previously discussed</a>, that approach culminated in a federal effort to challenge state AI laws viewed as inconsistent with a uniform, minimally burdensome national framework.</p>



<p>The 120th Congress may alter, but not displace, that approach. Although the executive branch will continue to direct federal agencies and enforce existing law, Democratic control of the House and Senate will give the party significant authority over the congressional agenda beginning Jan. 3, 2027. Perhaps most important, it will put congressional committees, investigative agendas, hearing calendars and <a href="https://www.bakerlaw.com/insights/lawyer-up-congressional-investigations-are-coming-and-they-require-a-different-playbook/">subpoena authority</a> under new leadership. Current reporting indicates that Democratic lawmakers are preparing proposals addressing advanced-model testing, AI-related harms and the costs associated with AI deployment and development.</p>



<p>Companies should therefore prepare for <strong>two federal AI agendas operating simultaneously</strong>: an executive branch continuing to emphasize innovation, technological leadership and regulatory restraint and a Congress placing focus on the risks associated with AI development and deployment. The resulting tension may shape federal AI policy even if Congress does not enact comprehensive legislation.</p>



<p>The distinction should not, however, be understood as a simple choice between regulation and deregulation. The executive branch itself continues to develop new mechanisms for addressing risks associated with increasingly capable AI systems, principally through enforcement against harms or unlawful conduct. In November, <a href="https://www.justice.gov/opa/media/1470291/dl?inline">the Department of Justice (DOJ) announced a Super Intelligence Task Force</a> focused on misuse of advanced technology by foreign and state-sponsored actors, transnational criminal organizations, and individuals or companies engaged in fraud or other unlawful conduct. The DOJ specifically identified regular reporting of risks and incidents and “vigorous internal controls” over advanced AI systems as areas of focus.</p>



<p>The emerging divide therefore may be less about whether AI should be governed than about how. Congress is more likely to explore prospective obligations concerning safety, testing, transparency and accountability, while the administration will continue to pair its support for innovation with enforcement against harmful or unlawful uses of advanced AI.</p>



<h2 class="wp-block-heading" id="h-b-congressional-scrutiny-will-carry-different-consequences">B. Congressional Scrutiny Will Carry Different Consequences</h2>



<p>The change in congressional control will not necessarily produce entirely new areas of scrutiny. Democratic lawmakers have already used letters, information requests and other minority-party tools to examine AI companies and their practices. What will change in 2027 is the authority behind those inquiries. Committee chairs will have greater control over investigative agendas, hearings, witness testimony and compulsory process. <a href="https://www.bakerlaw.com/insights/lawyer-up-congressional-investigations-are-coming-and-they-require-a-different-playbook/">As we previously discussed</a>, this investigative authority is very broad and presents very different challenges than executive branch investigations and traditional litigation. A congressional investigation is not traditional litigation. Congress does not file a complaint. There are no Rules of Civil or Criminal Procedure or Rules of Evidence, and congressional investigative requests are not subject to the familiar discovery rules and proportionality requirements that govern litigation. Nor must a committee satisfy the same thresholds that constrain other forms of government investigations. For example, a congressional committee need not establish probable cause before issuing a subpoena, unlike federal law enforcement seeking a search warrant.</p>



<p>That distinction matters for companies that develop or deploy AI. An inquiry that begins with a voluntary request for information can develop into a broader investigation involving document production, executive testimony or subpoenas. And congressional investigations differ from traditional executive branch enforcement proceedings: They can develop rapidly, encompass conduct that is not itself unlawful and unfold publicly alongside legislative and political debate.</p>



<p>AI also presents an unusually broad range of potential subjects for congressional inquiry. Depending on the company and technology involved, committees could examine model testing and safety practices, reported incidents, cybersecurity controls, training and data practices, consumer harms, representations concerning AI capabilities or the adequacy of governance and escalation procedures. Congressional interest may also extend beyond model developers to companies that deploy AI in products, services, employment, financial, healthcare or other consequential settings.</p>



<p>Companies should therefore not wait for a subpoena to assess their readiness. Organizations facing potential congressional scrutiny should identify the internal personnel responsible for responding to congressional inquiries, understand where relevant records reside, review escalation and document preservation procedures, and consider whether public statements concerning AI safety and governance are consistent with internal policies and practices.</p>



<h2 class="wp-block-heading" id="h-c-frontier-ai-proposals-are-beginning-to-define-expected-controls">C. Frontier AI Proposals Are Beginning To Define Expected Controls</h2>



<p>Recent bipartisan proposals concerning advanced, or frontier, AI systems provide an early indication of the safeguards Congress may expect from developers of the most capable models. Although the proposals differ in scope and approach, they increasingly focus on concrete operational controls, including independent testing, incident reporting, cybersecurity protections, risk monitoring and mechanisms for human intervention.</p>



<p>H.R. 9925, the “Frontier Risk Oversight, National Transparency, Independent Evaluation, and Reporting Act,” or <strong>FRONTIER Act</strong>, introduced in July by Reps. Jay Obernolte, R-Calif., and Lori Trahan, D-Mass., with bipartisan cosponsors, would establish federal oversight of the development and deployment of frontier AI. Among other provisions, the legislation contemplates independent evaluation organizations assessing certain large developers’ governance, risk monitoring and mitigation practices.</p>



<p>Other proposals go further. For instance, H.R. 9917, the “<strong>AI Kill Switch Act</strong>,” introduced by Reps. Ted Lieu, D-Calif., and Nathaniel Moran, R-Texas,<a href="#_ftn2" id="_ftnref2">[2]</a> would require covered entities to maintain technical capabilities to shut down certain covered technologies. Sen. John N. Kennedy, R-La., subsequently introduced S. 5417, the “<strong>AI Emergency Button Act</strong>,”<a href="#_ftn3" id="_ftnref3">[3]</a> which likewise would require developers or operators of advanced AI systems to incorporate a human-controlled shutdown capability.</p>



<p>The incoming Congress may also broaden the range of frontier AI proposals under consideration. The incoming Senate will include members who campaigned on substantially more aggressive restrictions in the development of advanced AI. Democratic Sen.-elect Abdul El-Sayed of Michigan, for example, proposed pausing the training and release of the most powerful AI models until federal safeguards are established, prohibiting the development of superintelligent systems and recursive self-improvement, and creating a Cabinet-level agency empowered to inspect AI laboratories, block dangerous model releases and order shutdowns.</p>



<p>These proposals vary in scope and political viability but, when viewed together, reflect growing congressional attention to the independent evaluation of advanced models, the reporting of significant risks and incidents, safeguards against misuse or loss of control, and the circumstances in which the government might regulate the development and deployment of advanced AI systems. Even where Congress does not reach consensus on specific requirements, these issues are likely to shape the legislative debate in 2027.</p>



<h2 class="wp-block-heading" id="h-d-existing-laws-may-matter-as-much-as-new-legislation">D. Existing Laws May Matter as Much as New Legislation</h2>



<p>Another significant question will be whether Congress seeks to create new liability rules for injuries attributed to AI. Current reporting indicates that Democratic lawmakers are considering proposals addressing when AI developers may be held liable for harms caused by their products. But companies should not assume that liability depends on enactment of an AI-specific federal statute. Existing consumer protection, antidiscrimination, privacy, intellectual property, product liability and other laws may already apply to conduct involving AI, depending on the technology, use and resulting harm.</p>



<p>Of course, that does not mean Congress will leave the liability framework untouched. Proposals such as the “Clear Liability for Artificial Intelligence Misconduct (CLAIM) Act”<a href="#_ftn4" id="_ftnref4">[4]</a> from Rep. Trahan would create new federal remedies specifically addressing harms caused by AI systems. But the legislative debate over whether to create AI-specific causes of action will occur against an existing legal framework that regulators and private litigants are already using to address AI-related conduct.</p>



<p>The practical consequence is that companies may face liability risk even if broader federal AI legislation stalls. Organizations should therefore remain responsible for the accuracy, reliability, confidentiality and integrity of work produced with AI assistance. That principle is unlikely to change regardless of which AI bills ultimately become law.</p>



<h2 class="wp-block-heading" id="h-e-the-future-of-a-uniform-federal-ai-framework">E. The Future of a Uniform Federal AI Framework</h2>



<p>Perhaps the most immediate consequence of the election for businesses operating nationally is what Congress may <strong>not</strong> do.</p>



<p>The Trump administration has pressed for a uniform federal approach that would limit or displace state AI requirements. The administration’s December 2025 Executive Order (EO) 14365, “Ensuring a National Policy Framework for Artificial Intelligence,”<a href="#_ftn5" id="_ftnref5">[5]</a> expressly advanced a national AI framework, and the DOJ subsequently established an AI Litigation Task Force directed at challenging state laws considered inconsistent with federal policy.</p>



<p>On Sept. 29, the president issued EO 14434, “Inaugurating the Era of Super Intelligence.”<a href="#_ftn6" id="_ftnref6">[6]</a> This EO directs executive branch departments and agencies to use “Super Intelligence” and “SI” in place of “Artificial Intelligence” and “AI” in all official correspondence, public communications, websites, reports, policy documents and other non-statutory documents. Notably, the EO started a 60-day review period by the assistant to the president for science and technology to draft proposed legislation to establish a federal definition of SI.</p>



<p>With control of Congress changing hands in January 2027, broad federal preemption of state AI laws faces a substantially more difficult legislative path. That does not necessarily mean the federal-state conflict will subside. Instead, the forum in which that conflict plays out may shift. The executive branch can continue to challenge selected state laws while Congress considers federal standards that may not displace state requirements.</p>



<p>For businesses, this may be one of the most consequential developments of all. State AI requirements may continue to develop while Congress debates federal standards and the executive branch challenges selected state restrictions. Instead of quickly resolving the existing regulatory patchwork, the next two years could make the relationship between federal and state AI regulation even more complex. Companies operating across jurisdictions should therefore be cautious about dismantling state-specific compliance programs in anticipation of federal preemption. Until Congress acts or courts invalidate particular state provisions, existing state obligations remain relevant.</p>



<h2 class="wp-block-heading" id="h-f-ai-infrastructure-and-data-centers-enter-the-regulatory-conversation">F. AI Infrastructure and Data Centers Enter the Regulatory Conversation</h2>



<p>The congressional AI debate also is broadening beyond models, algorithms and data. Attempts were made to pass legislation before the Nov. 3 midterm election but were ultimately unsuccessful. On Sept. 16, the House of Representatives passed H.R. 9340, the “Ratepayer Protection Act,” by a vote of 417-3. On Sept. 30, a Senate effort to advance the bill fell short of the 60 votes required to invoke cloture on the motion to proceed by a vote of 57-43. The enormous computing demands associated with AI have placed data centers, electricity costs, grid capacity, permitting and infrastructure squarely within the policy debate. Democratic lawmakers are reportedly developing proposals intended to prevent residential customers from bearing increased utility costs attributable to data center construction and operation. And data center regulation emerged as a recurring campaign issue among members of the incoming Senate, frequently framed around affordability rather than technology policy alone.</p>



<p>Several senators-elect called for data center operators to bear their own electricity and grid upgrade costs, while others proposed restrictions on tax incentives, water use or new construction. Democratic Sen.-elect James Talarico of Texas, for example, proposed federal minimum requirements governing grid protection, environmental effects, jobs and transparency, together with requirements that large energy users pay their own costs. El-Sayed went further, calling for a pause on new data center development as part of a broader plan to restrict advanced AI development.</p>



<p>These campaign positions suggest that congressional scrutiny of AI infrastructure will focus increasingly on who bears the costs of deployment. Indeed, Congress is already considering broader permitting legislation with significant implications for data center construction and the infrastructure needed to support it. Accordingly, organizations making substantial investments in AI infrastructure should monitor congressional activity not simply for legislation expressly labeled as an “AI” bill. Some of the most consequential federal developments for AI deployment may emerge from energy, tax, cybersecurity, national security or infrastructure legislation.</p>



<h2 class="wp-block-heading" id="h-g-what-organizations-should-do-now">G. What Organizations Should Do Now</h2>



<p>The regulatory direction remains fluid, but companies need not wait for Congress to act before preparing.</p>



<p>Organizations developing or deploying AI should consider:</p>



<ul class="wp-block-list">
<li><strong>Reviewing AI governance and escalation procedures.</strong> Companies should be able to identify who is responsible for approving AI systems, monitoring material risks, escalating incidents and documenting significant decisions. Those procedures may matter not only for compliance with emerging legislation but also for enforcement risk. The DOJ’s Super Intelligence Task Force specifically identified risk reporting and “vigorous internal controls” as areas of focus.</li>



<li><strong>Preparing for congressional scrutiny.</strong> Companies with significant AI operations should assess whether their internal documentation, safety testing, incident-reporting procedures and public representations are consistent and capable of withstanding scrutiny in a congressional investigation or hearing.</li>



<li><strong>Mapping federal and state obligations separately.</strong> Organizations should resist assuming that a future federal framework will eliminate state requirements. Compliance programs should identify which obligations originate at the federal, state, contractual and sector-specific levels.</li>



<li><strong>Reviewing AI vendor agreements.</strong> Contracts should address responsibility for testing, security incidents, data use, legal compliance, audit rights, indemnification and allocation of liability as regulatory requirements evolve.</li>



<li><strong>Monitoring legislation beyond bills expressly regulating AI.</strong> Cybersecurity, energy, infrastructure, tax, procurement, national security, investor protection and consumer protection legislation all may materially affect companies developing or deploying AI.</li>



<li><strong>Preserving flexibility.</strong> Perhaps most importantly, companies should avoid designing compliance programs around the assumption that today’s regulatory approach will remain static. The principal challenge over the next two years may not be any single AI rule but the interaction among congressional oversight, executive action, agency enforcement, state regulation and private litigation.</li>
</ul>



<h2 class="wp-block-heading">Conclusion</h2>



<p>The 120th Congress is unlikely to settle the debate over how the United States should regulate AI. It may intensify it.</p>



<p>The Trump administration remains committed to a federal policy emphasizing AI innovation and American competitiveness, while incoming congressional leadership appears poised to place substantially greater emphasis on safety, accountability, liability and consumer protection. At the same time, state governments will continue developing their own approaches, and existing laws will continue to apply to AI even where Congress has not enacted technology-specific rules.</p>



<p>For companies, the practical lesson is straightforward: <strong>Do not wait for a comprehensive federal AI statute.</strong> The more immediate risks may come from congressional investigations, executive branch enforcement, evolving state requirements, existing regulatory authority, litigation and the rapidly changing expectations surrounding responsible AI governance. Organizations that can explain <strong>what AI they use, why they use it, how they assess its risks, who supervises it and what happens when something goes wrong</strong> will be better positioned for whatever framework ultimately emerges.</p>



<p>BakerHostetler’s White Collar, Investigations and Securities Enforcement and Litigation team, Artificial Intelligence group, Federal Policy team and Congressional Investigations team draw on experience across Congress, federal agencies, emerging technology and complex investigations to advise clients on government investigations, regulatory compliance, AI governance and emerging technology risks. Our teams include former members of Congress from both sides of the aisle, former congressional and senior committee staff, and experienced white collar defense lawyers who counsel clients responding to congressional inquiries, preparing for interviews and testimony, and assessing investigation and litigation risks. Please feel free to contact any of our experienced professionals with questions regarding these developments or their implications for your organization.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p><a href="#_ftnref1" id="_ftn1">[1]</a> <a href="https://www.congress.gov/bill/119th-congress/house-bill/9925/text" target="_blank" rel="noreferrer noopener">https://www.congress.gov/bill/119th-congress/house-bill/9925/text</a></p>



<p><a href="#_ftnref2" id="_ftn2">[2]</a> <a href="https://www.congress.gov/bill/119th-congress/house-bill/9917?s=2&r=3" target="_blank" rel="noreferrer noopener">https://www.congress.gov/bill/119th-congress/house-bill/9917?s=2&r=3</a></p>



<p><a href="#_ftnref3" id="_ftn3">[3]</a> <a href="https://www.congress.gov/bill/119th-congress/senate-bill/5417?s=3&r=5" target="_blank" rel="noreferrer noopener">https://www.congress.gov/bill/119th-congress/senate-bill/5417?s=3&r=5</a></p>



<p><a href="#_ftnref4" id="_ftn4">[4]</a> <a href="https://trahan.house.gov/news/documentsingle.aspx?DocumentID=3861" target="_blank" rel="noreferrer noopener">https://trahan.house.gov/news/documentsingle.aspx?DocumentID=3861</a></p>



<p><a href="#_ftnref5" id="_ftn5">[5]</a> <a href="https://www.whitehouse.gov/presidential-actions/2025/12/eliminating-state-law-obstruction-of-national-artificial-intelligence-policy/" target="_blank" rel="noreferrer noopener">https://www.whitehouse.gov/presidential-actions/2025/12/eliminating-state-law-obstruction-of-national-artificial-intelligence-policy/</a></p>



<p><a href="#_ftnref6" id="_ftn6">[6]</a> <a href="https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/" target="_blank" rel="noreferrer noopener">https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/</a></p>
]]></content:encoded>
            <dc:creator><![CDATA[Michelle N. Tanney, Kevin R. Edgar]]></dc:creator>
            <category>Alert</category>
            <category>Litigation</category>
            <category>Tax</category>
            <category>Commercial Litigation</category>
            <category>Federal Policy</category>
            <category>Preparing for Congressional Oversight and Investigations</category>
        </item>
        <item>
            <title><![CDATA[DOJ and HHS Announce Streamlined Avenues for Criminal and Civil Self-Disclosure of Healthcare Fraud]]></title>
            <link>https://www.bakerlaw.com/insights/doj-and-hhs-announce-streamlined-avenues-for-criminal-and-civil-self-disclosure-of-healthcare-fraud/</link>
            <guid>https://www.bakerlaw.com/?p=81612</guid>
            <pubDate>Mon, 16 Nov 2026 20:47:41 GMT</pubDate>
            <description><![CDATA[<p><!-- wp:heading --></p>
<h2 id="h-key-takeaways" class="wp-block-heading">Key Takeaways</h2>
<p><!-- /wp:heading --> <!-- wp:list --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list"><!-- wp:list-item --></p>
<li>The Department of Justice (DOJ or Department) and the Department of Health and Human Services Office of Inspector General (HHS-OIG) have announced a new policy and new program, both designed to incentivize companies to self-disclose potential violations of federal healthcare laws.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>As the Department recognized, in the healthcare context, a single course of conduct frequently gives rise to overlapping criminal, civil and administrative matters, complicating the decision of <em>whether</em> and <em>where</em> to self-report. On Oct. 15, Assistant Attorney General (AAG) Colin M. McDonald, DOJ National Fraud Enforcement Division (Fraud Division or Division), announced a new policy that streamlines the process for companies to voluntarily self-report potential healthcare-related criminal conduct and secure distinct disclosure benefits from both DOJ and HHS-OIG (the Policy). Now, companies that voluntarily disclose such conduct to the Fraud Division will not only receive the benefit of DOJ’s criminal Corporate Enforcement Policy (CEP), but “shall” also qualify for HHS-OIG’s Self-Disclosure Protocol (SDP) covering civil monetary penalties so long as the disclosure satisfies the CEP’s requirements.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>The SDP will now apply without a separate report to HHS-OIG. But to benefit from both policies, companies must self-disclose potentially criminal conduct to the Fraud Division – corporate self-disclosures made only to HHS-OIG will not generally qualify as “voluntary disclosure” under the CEP.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Further, on Oct. 22, DOJ’s Civil Division, HHS-OIG and the Centers for Medicare & Medicaid Services (CMS) announced a six-month Healthcare False Claims Act (FCA) Self-Disclosure Pilot Program (Pilot Program). They did so shortly after DOJ announced a separate, broader fast-track whistleblower rewards program in the criminal context. Under the civil Pilot Program, companies that disclose FCA violations will receive multiple benefits, including a coordinated civil liability release, no factual admissions, no Corporate Integrity Agreement and a favorable financial resolution with a set range for the repayment multiplier.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>The Policy and the Pilot Program reflect enhanced benefits to companies that self-disclose potential criminally fraudulent conduct and FCA violations involving healthcare, and they provide clear paths to make such reports. But in practice, the onus remains on companies to investigate internal misconduct thoroughly and determine whether conduct is potentially criminal, civil or both. Prudent companies will consider engaging outside counsel quickly to conduct prompt and thorough investigations into potential misconduct and to analyze whether and to whom they should disclose misconduct to ensure they can reap the benefits of DOJ’s criminal CEP, HHS-OIG’s civil SDP and the new Pilot Program.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --></p>
<p><!-- /wp:list --></p>
]]></description>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li>The Department of Justice (DOJ or Department) and the Department of Health and Human Services Office of Inspector General (HHS-OIG) have announced a new policy and new program, both designed to incentivize companies to self-disclose potential violations of federal healthcare laws.</li>



<li>As the Department recognized, in the healthcare context, a single course of conduct frequently gives rise to overlapping criminal, civil and administrative matters, complicating the decision of <em>whether</em> and <em>where</em> to self-report. On Oct. 15, Assistant Attorney General (AAG) Colin M. McDonald, DOJ National Fraud Enforcement Division (Fraud Division or Division), announced a new policy that streamlines the process for companies to voluntarily self-report potential healthcare-related criminal conduct and secure distinct disclosure benefits from both DOJ and HHS-OIG (the Policy). Now, companies that voluntarily disclose such conduct to the Fraud Division will not only receive the benefit of DOJ’s criminal Corporate Enforcement Policy (CEP), but “shall” also qualify for HHS-OIG’s Self-Disclosure Protocol (SDP) covering civil monetary penalties so long as the disclosure satisfies the CEP’s requirements.</li>



<li>The SDP will now apply without a separate report to HHS-OIG. But to benefit from both policies, companies must self-disclose potentially criminal conduct to the Fraud Division – corporate self-disclosures made only to HHS-OIG will not generally qualify as “voluntary disclosure” under the CEP.</li>



<li>Further, on Oct. 22, DOJ’s Civil Division, HHS-OIG and the Centers for Medicare & Medicaid Services (CMS) announced a six-month Healthcare False Claims Act (FCA) Self-Disclosure Pilot Program (Pilot Program). They did so shortly after DOJ announced a separate, broader fast-track whistleblower rewards program in the criminal context. Under the civil Pilot Program, companies that disclose FCA violations will receive multiple benefits, including a coordinated civil liability release, no factual admissions, no Corporate Integrity Agreement and a favorable financial resolution with a set range for the repayment multiplier.</li>



<li>The Policy and the Pilot Program reflect enhanced benefits to companies that self-disclose potential criminally fraudulent conduct and FCA violations involving healthcare, and they provide clear paths to make such reports. But in practice, the onus remains on companies to investigate internal misconduct thoroughly and determine whether conduct is potentially criminal, civil or both. Prudent companies will consider engaging outside counsel quickly to conduct prompt and thorough investigations into potential misconduct and to analyze whether and to whom they should disclose misconduct to ensure they can reap the benefits of DOJ’s criminal CEP, HHS-OIG’s civil SDP and the new Pilot Program.</li>
</ul>



<h2 class="wp-block-heading" id="h-key-details">Key Details</h2>



<p>Earlier this year, DOJ created a new Fraud Division and tasked it to “zealously investigate and prosecute those who steal or fraudulently misuse taxpayer dollars.”<a href="#_ftn1" id="_ftnref1">[1]</a> On Oct. 1, <a href="https://www.bakerlaw.com/insights/doj-announces-corporate-fraud-enforcement-priorities-companies-take-note/" target="_blank" rel="noreferrer noopener">AAG McDonald issued a memorandum to the Fraud Division that provided additional guidance on the Division’s investigation and prosecution of corporate entities</a>.<a href="#_ftn2" id="_ftnref2">[2]</a> On Oct. 7, <a href="https://www.bakerlaw.com/insights/dojs-new-comprehensive-approach-will-fight-fraud-from-all-angles/" target="_blank" rel="noreferrer noopener">AAG McDonald released another memorandum that directed the Fraud Division to prioritize prosecuting healthcare fraud schemes</a>, among others.<a href="#_ftn3" id="_ftnref3">[3]</a> The Policy and the Pilot Program build on these prior directives, and both use self-disclosure as a means of combating healthcare fraud and other violations of law.</p>



<h3 class="wp-block-heading" id="h-fraud-division-and-hhs-oig-policy"><em>Fraud Division and HHS-OIG Policy</em></h3>



<p>The Policy recognizes that in “the health care fraud context, a single course of conduct – e.g., an illegal remuneration arrangement, a scheme to bill for medically unnecessary services, or a scheme involving an excluded person – frequently gives rise to overlapping criminal, civil, and administrative matters involving the Health Care Fraud Section” and HHS-OIG.<a href="#_ftn4" id="_ftnref4">[4]</a> Accordingly, a single course of conduct may result in multiple, different consequences, complicating the decisions of a company that uncovers potentially criminal conduct about not only whether to self-report it, but also to whom.<a href="#_ftn5" id="_ftnref5">[5]</a> Emphasizing a desire to avoid delay and the potential that evidence could become stale, the Policy clarifies that companies should disclose to the Fraud Division potentially criminal conduct involving “federal health care program funds, patients, consumers, and investors.”<a href="#_ftn6" id="_ftnref6">[6]</a></p>



<p>Under the Policy, a company need only make one disclosure – to the Health Care Fraud Section (or another DOJ component) – to obtain the benefits of voluntary self-disclosure under both DOJ’s CEP, which applies to criminal matters, and HHS-OIG’s SDP, which applies to civil matters.<a href="#_ftn7" id="_ftnref7">[7]</a> The disclosure must satisfy the CEP’s requirements.<a href="#_ftn8" id="_ftnref8">[8]</a> Accordingly, “[a] party in the health care industry that seeks to benefit from both” the CEP and the SDP “should make its initial disclosure of potentially criminal conduct to the Fraud Division,”<a href="#_ftn9" id="_ftnref9">[9]</a> because a disclosure to HHS-OIG “generally does not qualify as a voluntary self-disclosure to the Fraud Division” under the CEP.<a href="#_ftn10" id="_ftnref10">[10]</a> The Policy qualifies this directive, however, by noting that prosecutors retain the discretion to recommend a declination based on the severity of the circumstances and other factors, and that prosecutors may consider disclosures to either government entity as part of a company’s cooperation and remediation.<a href="#_ftn11" id="_ftnref11">[11]</a></p>



<h3 class="wp-block-heading" id="h-doj-s-civil-division-and-hss-oig-pilot-program"><em>DOJ’s Civil Division and HSS-OIG Pilot Program</em></h3>



<p>The Pilot Program notes that DOJ and HHS have “long encouraged the healthcare industry to proactively invest in compliance and transparently engage with the government.”<a href="#_ftn12" id="_ftnref12">[12]</a> Accordingly, the Pilot Program seeks to build on these “long-standing efforts to incentivize disclosure”<a href="#_ftn13" id="_ftnref13">[13]</a> in the healthcare space by “offer[ing] a clear and predictable pathway for companies seeking to obtain a coordinated resolution of civil liability” under the FCA and several HHS administrative authorities.<a href="#_ftn14" id="_ftnref14">[14]</a> The Pilot Program is designed to “support[] legitimate American healthcare businesses endeavoring to quickly and cooperatively resolve prior misconduct and move forward with a clean slate.”<a href="#_ftn15" id="_ftnref15">[15]</a> The announcement distinguishes those entities from “illegitimate businesses that knowingly exploit the generosity of the American people through various fraudulent schemes.”<a href="#_ftn16" id="_ftnref16">[16]</a></p>



<p>The following entities are eligible to participate in the Pilot Program: “[h]ealthcare providers, suppliers, manufacturers, payors, and related entities that furnish, arrange for, manufacture, distribute, insure, administer, or bill for items or services reimbursed, subsidized or otherwise paid for, directly or indirectly, by HHS Federal health care programs.”<a href="#_ftn17" id="_ftnref17">[17]</a> To be eligible for a resolution under the Pilot Program, the self-disclosure must identify a potential violation of the FCA of which the government was not previously aware.<a href="#_ftn18" id="_ftnref18">[18]</a> Disclosures must be received on or before April 22, 2027.<a href="#_ftn19" id="_ftnref19">[19]</a></p>



<p>The announcement outlines several components required for a disclosure to be considered. It must:</p>



<p>(1) “Describe all relevant details relating to the disclosing company’s conduct that, in the disclosing company’s reasonable assessment, potentially violate the FCA … including the specific laws, regulations, or other binding requirements that were violated and the time period of the violations.”</p>



<p>(2) “Append as exhibits all documents sufficient to fully reflect the nature, terms, and operation of the disclosed FCA violations.”</p>



<p>(3) “Specify the remedial measures or other corrective action the disclosing company has taken to terminate the disclosed potential FCA violations and prevent them from reoccurring.”</p>



<p>(4) “Provide financial information sufficient to facilitate the DOJ Civil Division calculating the Base Self-Disclosure Repayment.”</p>



<p>(5) “Include a certification from the disclosing company’s authorized representative stating that to the best of the individual’s knowledge, the submission contains truthful and complete information about the disclosed potential FCA violations.”</p>



<p>(6) Include contact information for the company’s designated point of contact for any follow-up questions.<a href="#_ftn20" id="_ftnref20">[20]</a></p>



<p>Self-disclosing companies receive numerous benefits under the Pilot Program. Specifically, companies will “receive favorable treatment from DOJ Civil Division and HHS in a coordinated civil release, with no factual admissions.”<a href="#_ftn21" id="_ftnref21">[21]</a> Further, DOJ will provide self-disclosing companies with a release under the FCA, and HHS-OIG will not require a Corporate Integrity Agreement as part of a Pilot Program resolution. Further, CMS will not impose civil monetary penalties or seek revocation. Companies will also receive “favorable financial resolutions,” with repayments calculated using a fixed multiplier of 1.25 to 1.60 times the Base Self-Disclosure Repayment.<a href="#_ftn22" id="_ftnref22">[22]</a> The exact multiplier will be determined by evaluating the timeliness of the company’s disclosure, the duration and scope of misconduct, the involvement of senior leadership, the financial benefit to the disclosing company, and whether the disclosing company has successor liability for conduct that it promptly remediated.<a href="#_ftn23" id="_ftnref23">[23]</a></p>



<h2 class="wp-block-heading" id="h-practical-considerations-for-companies-and-executives">Practical Considerations for Companies and Executives</h2>



<p>The Policy and the Pilot Program build on DOJ’s prior guidance that emphasizes the Department’s interest in voluntary self-disclosure as an important component of combating fraud.<a href="#_ftn24" id="_ftnref24">[24]</a> Both the Policy and the Pilot Program incentivize companies to disclose potential healthcare fraud or other violations of law in the healthcare space by providing them with significant benefits for self-reporting. The Department has telegraphed a significant future uptick in fraud investigations and prosecutions, particularly in the healthcare context. Companies in the healthcare industry should consider the Policy, the Pilot Program and DOJ’s prior guidance in their risk assessments and should review their policies and procedures to ensure current compliance with the law.<a href="#_ftn25" id="_ftnref25">[25]</a> Companies should also ensure that they are able to react quickly upon learning of potential misconduct because credit for self-disclosure under the CEP and the Pilot Program hinges in part on the government not previously being aware of the potential violations of law. It is prudent for companies to engage outside counsel, conduct a thorough investigation and work with counsel to determine whether and to whom self-disclosure is appropriate, and to evaluate whether the misconduct might be criminal, civil or both.</p>



<p>The BakerHostetler White Collar, Investigations and Securities Enforcement and Litigation and the Criminal Tax Defense teams are composed of dozens of experienced individuals, including numerous attorneys who have served in DOJ and at the SEC. Our attorneys include four former U.S. attorneys, several former assistant U.S. attorneys and unit chiefs, attorneys who served in DOJ’s Tax Division, and attorneys who served in the SEC’s Division of Enforcement. Our teams have extensive experience in defending regulatory investigations and litigation, conducting enterprise-wide, business-line and regulatory area-specific risk assessments, providing compliance counseling, and assisting companies with navigating successful self-reports to the government.</p>



<p>Please feel free to contact any of our experienced professionals if you have questions about this alert.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p><a href="#_ftnref1" id="_ftn1">[1]</a> Memorandum from Acting Att’y Gen. Todd Blanche, <em>Creation of the National Fraud Enforcement</em> Division (Apr. 7, 2026), <em>available at</em> <a href="https://www.justice.gov/ag/media/1435311/dl?inline" target="_blank" rel="noreferrer noopener">https://www.justice.gov/ag/media/1435311/dl?inline</a>.</p>



<p><a href="#_ftnref2" id="_ftn2">[2]</a> Memorandum from Assistant Att’y Gen. Colin M. McDonald, <em>Directive 26-12: Corporate Enforcement in the Fight Against Fraud </em>(Oct. 1, 2026), <em>available at</em> <a href="https://www.justice.gov/opa/media/1463571/dl?inline" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/media/1463571/dl?inline</a>; <em>see also </em>U.S. Dep’t of Justice, Justice Manual §§ 9.28-000 <em>et seq.</em> (2026).</p>



<p><a href="#_ftnref3" id="_ftn3">[3]</a> Memorandum from Assistant Att’y Gen. Colin M. McDonald, <em>Directive 26-13: A Comprehensive Approach in the Fight Against Fraud</em> (Oct. 7, 2026), <em>available at </em><a href="https://www.justice.gov/opa/media/1465036/dl?inline=&utm_medium=email&utm_source=govdelivery" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/media/1465036/dl?inline</a>.</p>



<p><a href="#_ftnref4" id="_ftn4">[4]</a> Policy announcement from Assistant Att’y Gen. Colin M. McDonald, “National Fraud Enforcement Division & HHS-OIG Policy on Coordination of Voluntary Self-Disclosure in Health Care Fraud Matters”(Oct. 15, 2026), <em>available at </em><a href="https://www.justice.gov/opa/media/1466291/dl?inline" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/media/1466291/dl?inline</a>.</p>



<p><a href="#_ftnref5" id="_ftn5">[5]</a> <em>See id.</em></p>



<p><a href="#_ftnref6" id="_ftn6">[6]</a> <em>Id.</em></p>



<p><a href="#_ftnref7" id="_ftn7">[7]</a> <em>Id.</em></p>



<p><a href="#_ftnref8" id="_ftn8">[8]</a> <em>Id.</em></p>



<p><a href="#_ftnref9" id="_ftn9">[9]</a> <em>Id.</em></p>



<p><a href="#_ftnref10" id="_ftn10">[10]</a> <em>Id.</em></p>



<p><a href="#_ftnref11" id="_ftn11">[11]</a> <em>Id.</em></p>



<p><a href="#_ftnref12" id="_ftn12">[12]</a> Dep’t of Justice and Dep’t of Health & Human Services Healthcare Self-Disclosure Pilot Program(Oct. 22, 2026), <em>available at </em><a href="https://www.justice.gov/opa/media/1467546/dl" target="_blank" rel="noreferrer noopener">https://www.justice.gov/opa/media/1467546/dl</a>.</p>



<p><a href="#_ftnref13" id="_ftn13">[13]</a> <em>Id.</em></p>



<p><a href="#_ftnref14" id="_ftn14">[14]</a> <em>Id.</em></p>



<p><a href="#_ftnref15" id="_ftn15">[15]</a> <em>Id.</em></p>



<p><a href="#_ftnref16" id="_ftn16">[16]</a> <em>Id.</em></p>



<p><a href="#_ftnref17" id="_ftn17">[17]</a> <em>Id.</em></p>



<p><a href="#_ftnref18" id="_ftn18">[18]</a> <em>See id.</em></p>



<p><a href="#_ftnref19" id="_ftn19">[19]</a> <em>See id.</em></p>



<p><a href="#_ftnref20" id="_ftn20">[20]</a> <em>Id.</em></p>



<p><a href="#_ftnref21" id="_ftn21">[21]</a> <em>Id.</em></p>



<p><a href="#_ftnref22" id="_ftn22">[22]</a> <em>See id.</em></p>



<p><a href="#_ftnref23" id="_ftn23">[23]</a> <em>See id.</em></p>



<p><a href="#_ftnref24" id="_ftn24">[24]</a> <em>Id.</em></p>



<p><a href="#_ftnref25" id="_ftn25">[25]</a> Importantly, notwithstanding DOJ’s current priorities, statutes of limitations for employee misconduct frequently extend beyond a single administration’s term. Companies should continue to be diligent about compliance in all areas and forms.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Robb C. Adkins, Jonathan R. Barr, Patrick T. Campbell, John J. Carney, C. Shawn Cleveland, Jimmy Fokas, Ryan S. Hedges, Kristen L. Jackson, Rebecca Chattin Lutzko, Artie McConnell, Brian F. McEvoy, Kimberly S. Morris, Justin P. Murphy, Jonathan B. New, Carlos F. Ortiz, Christos G. Papapetrou, Jacqueline Romero, Jennifer G. Solari, George A. Stamboulidis, Michelle N. Tanney]]></dc:creator>
            <category>Alert</category>
            <category>Litigation</category>
            <category>White Collar, Investigations and Securities Enforcement and Litigation</category>
            <category>Healthcare</category>
        </item>
        <item>
            <title><![CDATA[EEOC Rescinds Background Check Guidance: What Employers Need to Know]]></title>
            <link>https://www.bakerlaw.com/insights/eeoc-rescinds-background-check-guidance-what-employers-need-to-know/</link>
            <guid>https://www.bakerlaw.com/?p=81554</guid>
            <pubDate>Wed, 11 Nov 2026 19:21:45 GMT</pubDate>
            <description><![CDATA[<p><!-- wp:heading --></p>
<h2 id="h-key-takeaways" class="wp-block-heading">Key Takeaways</h2>
<p><!-- /wp:heading --> <!-- wp:list --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list"><!-- wp:list-item --></p>
<li>The EEOC’s rescission of its background check guidance does not eliminate employers’ potential legal risk.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Employers should continue conducting individualized assessments when considering an applicant’s criminal history.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --> <!-- wp:list-item --></p>
<ul class="wp-block-list">
<li style="list-style-type: none;">
<ul class="wp-block-list">
<li>Employers must still comply with federal, state and local laws governing background checks and hiring decisions.</li>
</ul>
</li>
</ul>
<p><!-- /wp:list-item --></p>
<p><!-- /wp:list --></p>
]]></description>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways</h2>



<ul class="wp-block-list">
<li>The EEOC’s rescission of its background check guidance does not materially change employers’ obligations.</li>



<li>Employers should continue conducting individualized assessments when considering an applicant’s criminal history.</li>



<li>Employers must still comply with federal, state and local laws governing background checks and hiring decisions.</li>
</ul>



<p>The Equal Employment Opportunity Commission (EEOC) has rescinded its long-standing guidance on criminal background checks. But does this action change how employers should conduct background checks? Not at all.</p>



<h2 class="wp-block-heading" id="h-what-was-in-the-guidance">What was in the guidance?</h2>



<p>The rescinded guidance focused mainly on compliance with Title VII’s antidiscrimination provisions. Criminal history, of course, is not a protected class under Title VII. But the guidance largely conflated criminal history with race and national origin.</p>



<p>Relying on a disparate impact theory, the guidance argued that racial minorities had a higher rate of criminal convictions and arrests than whites. Therefore, the argument went, excluding applicants based on criminal history has a disparate impact against Title VII-protected minorities and is unlawful – unless the exclusion is job-related and based on business necessity. The guidance opined that a policy of automatically excluding applicants with criminal histories would violate Title VII, based on the policy’s disparate impact against minorities. (There are limited exceptions, such as where a federal or state law prohibits people with certain types of convictions from holding certain jobs.)</p>



<p>The guidance directed employers to conduct an individualized inquiry to assess whether the decision to disqualify someone would be job-related and consistent with business necessity. The individualized inquiry would require consideration of three factors:</p>



<ol class="wp-block-list">
<li>The nature and gravity of the offense or conduct</li>



<li>The time that has passed since the offense or conduct and/or completion of the sentence</li>



<li>The nature of the job held or sought</li>
</ol>



<p>The guidance also recognized the possibility of disparate treatment between two applicants of different races with similar criminal history. But that scenario is the kind of basic, textbook discrimination that needed no special guidance. The real focus of the guidance was disparate impact theory.</p>



<h2 class="wp-block-heading" id="h-how-does-the-rescission-affect-disparate-impact-claims">How does the rescission affect disparate impact claims?</h2>



<p>The most direct impact of the rescission is that the EEOC will no longer pursue disparate impact claims based on criminal history. That isn’t news. The Trump administration and the EEOC had already announced they would not be pursuing disparate impact claims. So in that sense, the rescission is just a formal reiteration of what we already knew.</p>



<p>But disparate impact claims are still recognized by the courts. Title VII prohibits neutral-sounding policies that have a disparate impact against members of a protected class.</p>



<p>Aggrieved employees may still pursue civil claims alleging disparate impact under Title VII. In other words, private litigants can still pursue the same claims under the same theories, even if the EEOC has lost interest.</p>



<p>Employers that automatically exclude candidates with criminal histories, without conducting individualized analyses, therefore remain at risk of facing a disparate impact claim.</p>



<p>Even after the rescission, employers should continue to conduct individualized analyses when reviewing criminal histories.</p>



<p>But disparate impact claims are not the only risk employers would face if they were to adopt a policy of excluding all applicants with criminal histories.</p>



<p>At least 24 states and localities have their own laws that require individualized inquiries. In many instances, these laws require employers to consider a specific list of factors or to reach a specific conclusion about an individual before disqualifying that person based on criminal history.</p>



<p>State and local laws impose a variety of other requirements too. These include, for example, filling out a specific form to document the individualized analysis, notifying applicants which convictions might be disqualifying and providing additional information along with pre- and post-adverse action notices. Failing to follow these requirements is, by itself, a violation of state or local law, even if there is no disparate impact. These laws impose <em>procedural</em> requirements.</p>



<p>Employers must also keep in mind the Fair Credit Reporting Act, a federal law that imposes procedural requirements for conducting employment-related background checks. Despite the name, the law covers much more than credit reporting. Its requirements extend to background checks that contain criminal history, employment or education information, civil lawsuits, motor vehicle records, bankruptcies, social media history and even personal references, if the information is gathered by a third-party consumer reporting agency (a background check company).</p>



<p>As a practical matter, employers should view the rescission of this guidance as nothing more than the EEOC saying that it, as an agency, will no longer bring disparate impact claims based on background check results. (It didn’t bring many of these claims anyway.) The recission should not be viewed by employers as an invitation to soften background check policies or to impose blanket criminal history bans.</p>



<p>Rather, employers should remain vigilant about complying with the many technical and procedural requirements that are mandated by federal, state and local laws, even after recission of the EEOC guidance.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Todd H. Lebowitz]]></dc:creator>
            <category>Alert</category>
            <category>Labor and Employment</category>
        </item>
        <item>
            <title><![CDATA[CMS Releases the 2027 Hospital Outpatient Prospective Payment System and Ambulatory Surgical Center Final Rule]]></title>
            <link>https://www.bakerlaw.com/insights/cms-releases-the-2027-hospital-outpatient-prospective-payment-system-and-ambulatory-surgical-center-final-rule/</link>
            <guid>https://www.bakerlaw.com/?p=81574</guid>
            <pubDate>Wed, 11 Nov 2026 18:03:54 GMT</pubDate>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways"><strong>Key Takeaways:</strong></h2>



<ul class="wp-block-list">
<li><strong>Major 340B changes:</strong> CMS reduces Medicare reimbursement for 340B drugs and accelerates recoupment of prior remedy payments.</li>



<li><strong>Continued shift to outpatient care:</strong> CMS removes 637 additional services from the Inpatient-Only list and adds 618 procedures to the ASC Covered Procedures List.</li>



<li><strong>New off-campus requirements:</strong> Expanded site-neutral payments and upcoming NPI and attestation requirements create new financial and operational considerations for hospitals.</li>
</ul>



<p>On Nov. 6, the Centers for Medicare & Medicaid Services (CMS) published in the <em>Federal Register</em> the Calendar Year 2027 Hospital Outpatient Prospective Payment System (OPPS) and Ambulatory Surgical Center (ASC) final rule. This rule will generally take effect on Jan. 1, 2027, and will include multiple policy changes affecting payments under Medicare Part B.</p>



<p>Taken as a whole, the CY 2027 OPPS final rule reflects CMS’s continued effort to reshape where Medicare services are delivered, how much Medicare pays for them and how closely CMS oversees hospital outpatient operations. Although hospitals and ASCs will receive a 2.3 percent headline payment increase, that increase tells only part of the story. CMS is simultaneously pursuing substantial reductions in 340B drug reimbursement, accelerating recoupment of the prior 340B remedy, expanding site-neutral payment for certain services furnished by off-campus hospital departments, and continuing to move hundreds of procedures out of the inpatient setting and into outpatient hospitals and ASCs. At the same time, CMS is adding new enrollment and attestation obligations for off-campus departments, expanding prior authorization and experimenting with new payment approaches for software-based services. The result is a rule that CMS may characterize as promoting efficiency, site neutrality and patient choice but that also raises a more fundamental question: whether Medicare is truly modernizing outpatient payment or simply using an expanding collection of payment reductions and administrative requirements to push care toward the settings CMS prefers. For hospitals, the practical impact therefore will depend less on the nominal 2.3 percent update than on their particular mix of 340B drugs, off-campus services, procedures affected by the Inpatient-Only (IPO) list and ASC changes, and ability to absorb the rule’s growing operational requirements.</p>



<p>Highlights under the CY 2027 OPPS/ASC final rule include the following:</p>



<ul class="wp-block-list">
<li><strong>OPPS Payment Update. </strong>CMS finalized a 2.3 percent outpatient department fee schedule increase for CY 2027 for hospitals that meet Hospital Outpatient Quality Reporting (OQR) Program requirements. The update reflects a 3.2 percent hospital inpatient market basket increase for inpatient services paid under the hospital inpatient prospective payment system, reduced by a 0.9-percentage-point productivity adjustment. Further, after incorporating the annual update and other conversion-factor adjustments, CMS established a CY 2027 OPPS conversion factor of $99.970 for hospitals that meet OQR Program requirements.</li>
</ul>



<ul class="wp-block-list">
<li><strong>ASC Payment Update. </strong>CMS finalized a 2.3 percent annual payment update for CY 2027 for ASCs that satisfy the Ambulatory Surgical Center Quality Reporting Program requirements. The increase reflects a 3.2 percent hospital inpatient market basket increase, reduced by a 0.9-percentage-point productivity adjustment. CMS also extended its use of the productivity-adjusted hospital market basket as the ASC update methodology for one additional year, through CY 2027, rather than reverting to the Consumer Price Index for All Urban Consumers. Applying the annual update and a 1.0018 wage-index budget-neutrality adjustment to the CY 2026 conversion factor of $56.322 produces a CY 2027 conversion factor of $57.721 for ASCs meeting quality reporting requirements.</li>
</ul>



<ul class="wp-block-list">
<li><strong>340B Updates:</strong></li>
</ul>



<ul class="wp-block-list">
<li>Reimbursement Reductions. Medicare Part B will no longer pay Average Sales Price (ASP) plus 6 percent for 340B drugs and will instead pay Covered Entities ASP minus 28 percent for 340B drugs. CMS states that because of budget neutrality, these rate cuts will result in increasing aggregate OPPS payments for nondrug services by an equivalent amount. These rate reductions go further than what CMS previously did in 2018-2022. As with the 2018 rate cuts that were ultimately overturned by a unanimous U.S. Supreme Court, litigation could be coming to challenge these reimbursement changes.</li>
</ul>



<ul class="wp-block-list">
<li>Accelerated 340B Remedy Recoupment. In 2023, to repay 340B Covered Entities for the previous attempt to cut rates, CMS finalized a remedy plan that included retroactively budget neutralizing the remedy payments by offsetting OPPS rates for nondrug payments. The original remedy plan was to use a 0.5 percent annual reduction for nondrug payments beginning in 2026, projected to recover the offset over approximately 16 years. However, the updated 2027 OPPS final rule increases that annual reduction to 2 percent, accelerating recovery of the same historical offset to recoup $7.8 billion by 2031.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Off-Campus Provider-Based Departments: Attestation and NPI Requirements. </strong>Beginning Jan. 1, 2028, off-campus hospital provider-based outpatient departments (PBDs) must have a separate NPI and satisfy new attestation requirements to receive applicable Medicare payment. For PBDs furnishing services on or before Jan. 1, 2028 – including departments that previously received a provider-based determination from CMS – hospitals must submit an initial attestation demonstrating compliance with Medicare’s provider-based requirements by Dec. 31, 2027. For departments beginning services after Jan. 1, 2028, an initial attestation must be submitted within two years prior to delivery of services. Subsequent attestations will be required at intervals established by CMS, not to exceed five years. Hospitals should begin evaluating affected locations and preparing for related enrollment, billing and operational changes in advance of the 2028 effective date.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Site-Neutral Payment for Off-Campus Imaging. </strong>CMS expanded its site-neutral payment policy for services furnished by excepted off-campus PBDs. Under the new policy, certain imaging services, including X-rays, ultrasounds, CT scans, MRIs and bone-density scans furnished without contrast, will be paid at a PFS-equivalent rate, approximately 40 percent of the full OPPS payment rate. Rural sole community hospitals are exempt from this expanded site-neutral policy. CMS estimates that the change will cut OPPS spending by approximately $260 million in CY 2027.</li>
</ul>



<ul class="wp-block-list">
<li><strong>IPO List. </strong>Under the policy adopted in the CY 2026 OPPS/ASC final rule, CMS continues to eliminate procedures from the IPO list as part of a planned three-year phaseout of the IPO list. The IPO list was originally created to require that certain services be provided in inpatient hospital settings under Medicare Part A, making them ineligible for reimbursement under OPPS. For CY 2027, CMS is eliminating an additional 637 services from the IPO list, including services from the following clinical families: auditory, digestive, endocrine, female genital, hemic and lymphatic systems, integumentary, male genital, maternity care and delivery, mediastinum and diaphragm, respiratory, and urinary. CMS has stated it expects that the remaining IPO services will be eliminated in 2028 but agreed with commenters that it “should wait to remove these more clinically complex and unique procedures, including neurological and cardiovascular procedures.”</li>
</ul>



<ul class="wp-block-list">
<li><strong>ASC Covered Procedures List. </strong>CMS continues its expansion of the ASC setting by adding to the ASC Covered Procedures List 618 procedures that the agency also finalized for removal from the IPO list. Although inclusion on the ASC Covered Procedures List permits Medicare payment when a procedure is performed in an ASC, it does not establish that every listed procedure is clinically appropriate for every patient or must be furnished in that setting, leaving that determination to the physician’s clinical judgment.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Intensive Outpatient Programs. </strong>For the intensive outpatient program (IOP), CMS largely maintains the existing payment methodology. CMS will continue the current rate structure, with two IOP ambulatory payment classifications (APCs) for each provider type, covering days with three services and days with four or more services. For hospital-based IOPs, CMS will continue calculating the per diem payment rates using specified OPPS data that include both identified IOP days and other hospital outpatient days that contain the service codes and level of intensity necessary to qualify as an IOP day. Lastly, CMS will continue calculating IOP costs at 40 percent of the corresponding hospital-based costs for community mental health centers.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Partial Hospitalization Program. </strong>For CY 2027, CMS finalized updated payment rates for the Partial Hospitalization Program (PHP). CMS will continue to use APC 5864, the payment rate for four or more hospital-based PHP services, as the maximum daily payment for certain outpatient mental health services. When the aggregate payment for specified outpatient mental health services furnished to a beneficiary on the same day would exceed the APC 5864 rate, Medicare will instead pay for those services through composite APC 8010 at the APC 5864 payment rate.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Botulinum Toxin Prior Authorization. </strong>CMS is expanding Medicare’s prior authorization requirements for certain services furnished in hospital outpatient departments by adding eight additional botulinum toxin injection codes to the existing prior authorization program for dates of service on or after July 1, 2027. The relevant codes include CPT codes 64611, 64616, 64617, 64642, 64644, 64646 and 64647 as well as HCPCS code J0589. The expansion builds on CMS’s existing prior authorization requirements for botulinum toxin injections and reflects CMS’s concerns regarding increased utilization of these services.</li>
</ul>



<ul class="wp-block-list">
<li><strong>EMTALA Accreditation Surveys. </strong>CMS finalized a policy allowing hospital accrediting organizations (AOs) with deeming authority to evaluate hospitals’ compliance with specified Emergency Medical Treatment and Labor Act (EMTALA) administrative requirements during accreditation and reaccreditation surveys. AOs may assess administrative requirements under 42 C.F.R. § 489.20, including requirements related to EMTALA signage, maintenance of a central emergency department log, retention of transfer-related records for five years and maintenance of physician on-call lists. However, CMS and the Department of Health and Human Services Office of Inspector General retain their respective enforcement authorities.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Software as a Medical Service and Algorithmic Laboratory Analysis. </strong>As discussed in more detail in our recent client alert, <a href="https://www.bakerlaw.com/insights/digital-health-and-ai-key-regulatory-reimbursement-and-policy-developments/">Digital Health and AI: Key Regulatory, Reimbursement and Policy Developments</a>.CMS  established Software as a Medical Service (SaMS) as a new category for certain software-based clinical technologies and will generally use New Technology APCs as an interim OPPS payment pathway while it develops a longer-term methodology CMS has stated the 36 HCPCS codes designated as SaMS in CY 2027 that are currently paid separately under clinical APCs will be reassigned to New Technology APCs, which CMS has indicated will align closely with their current CY 2026 payment rates.  CMS also moved certain stand-alone software analyses of previously generated laboratory data, such as algorithmic analysis of genomic sequencing results, from the Clinical Laboratory Fee Schedule to OPPS, creating a separate hospital outpatient payment pathway for these emerging technologies.</li>
</ul>



<p>BakerHostetler’s Healthcare team provides counsel to healthcare organizations nationwide regarding Medicare reimbursement and regulatory compliance.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Gregory A. Tanner, Natalie R. Berkowitz Cromartie, Nicole D. Katapodis, Valerie A. Morrow, Scott P. Robertson, Kierra I. Ross]]></dc:creator>
            <category>Alert</category>
            <category>Healthcare</category>
        </item>
        <item>
            <title><![CDATA[CMS Releases the 2027 Medicare Physician Fee Schedule Final Rule]]></title>
            <link>https://www.bakerlaw.com/insights/cms-releases-the-2027-medicare-physician-fee-schedule-final-rule/</link>
            <guid>https://www.bakerlaw.com/?p=81576</guid>
            <pubDate>Wed, 11 Nov 2026 18:02:12 GMT</pubDate>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways">Key Takeaways:</h2>



<ul class="wp-block-list">
<li>CMS released its annual Medicare OPPS/ASC and Physician Fee Schedule final rules for 2027.</li>
</ul>



<ul class="wp-block-list">
<li>The 2027 rules include significant efforts to reshape Medicare operations and compliance, with new requirements affecting provider-based departments, prior authorization, remote monitoring, physician billing and coding, quality reporting, ACO participation, and emerging software-based services.</li>
</ul>



<ul class="wp-block-list">
<li>Providers will need to look beyond Medicare’s headline payment updates because the financial impact of the 2027 rules will vary substantially based on service mix, care setting, 340B participation and involvement in accountable-care arrangements.</li>
</ul>



<h2 class="wp-block-heading" id="h-overview">Overview:</h2>



<p>The Centers for Medicare & Medicaid Services’ (CMS) 2027 Medicare payment rules continue a broader shift in how and where the agency wants care delivered. Across these rules, CMS is using a combination of payment reductions, targeted incentives, site-of-service policies and new operational requirements. Taken together, the rules suggest that CMS is increasingly using both payment incentives and payment reductions to steer where and how Medicare beneficiaries receive care, making the practical impact much more dependent on a provider’s service mix and delivery model than the headline annual payment updates might suggest.</p>



<p>On Nov. 9, CMS published the Calendar Year (CY) 2027 Medicare Physician Fee Schedule (PFS) final rule in the <em>Federal Register</em>. Most provisions take effect Jan. 1, 2027, although certain policies have different implementation dates. The final rule includes numerous changes affecting Medicare Part B payment and coverage, the Medicare Shared Savings Program, the Quality Payment Program and the Medicare Prescription Drug Inflation Rebate Program.</p>



<p>CMS’s CY 2027 PFS final rule sends physicians something of a mixed message. On one hand, CMS is increasingly willing to pay more for the types of services it wants to encourage, including longitudinal relationships, preventive interventions and care delivered within accountable-care structures. On the other hand, the basic PFS conversion factors will decline in 2027, including a 2.31 percent reduction for clinicians who are not qualifying APM participants, as the temporary CY 2026 statutory payment increase expires. For physician practices confronting rising costs while being asked to invest more heavily in care coordination, technology, quality reporting and new delivery models, that request may ultimately prove more consequential than any individual payment policy in the final rule.</p>



<p>Highlights under the CY 2027 PFS final rule include the following:</p>



<ul class="wp-block-list">
<li><strong>PFS Conversion Factors. </strong>CMS finalized a CY 2027 conversion factor of approximately $32.95 for qualifying participants (QPs) in Advanced Alternative Payment Models, a 1.83 percent decrease from CY 2026, and approximately $32.63 for clinicians who are not QPs, a 2.31 percent decrease. The conversion factors reflect the expiration of the temporary 2.5 percent CY 2026 statutory increase, a negative 0.12 percent budget-neutrality adjustment, and statutory updates of 0.75 percent for QPs and 0.25 percent for non-QPs.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Practice Expense Updates</strong>
<ul class="wp-block-list">
<li>Indirect PE generally will be allocated using both work RVUs and clinical-labor PE RVUs. Ten- and 90-day global codes are excluded: CMS will allocate indirect practice expenses (PE) using the sum of physician work relative value units (RVUs) and clinical-labor PE RVUs, rather than using the greater of the two as it has done in the past. Previously, services with separately reportable professional, technical and global components (typically diagnostic and imaging services) already received this sum-based treatment, while most other services did not. The final rule extends sum-based treatment to other services, except codes with 10- and 90-day global periods. This change concerns the allocator used to distribute indirect PE; it does not establish a separate clinical-labor payment or guarantee an increase in a particular service’s reimbursement.</li>



<li>CMS phases out the Indirect Practice Cost Index over two years, reducing reliance on older specialty PE data. Over CYs 2027 and 2028, CMS will phase out its use of the Indirect Practice Cost Index (IPCI) in calculating PE RVUs. CMS concluded that the steps of the current methodology that rely on IPCI effectively favor outdated aggregate specialty data over more current service-specific inputs and limit the effect of improvements to the allocation methodology. In CY 2027, only half the measured variation in the IPCI will be applied to the indirect allocator. In CY 2028, the IPCI will no longer be part of the calculation.</li>



<li>CMS generally limits methodology-driven annual changes in PE RVUs to 5 percent, subject to exceptions. CMS finalized a stabilization adjustment that generally limits annual increases or decreases in a code’s PE RVUs attributable to the PE methodology to 5 percent. The adjustment is not a cap on the code’s total Medicare payment change and does not apply to new, revised, revalued or newly nationally priced codes.</li>
</ul>
</li>
</ul>



<ul class="wp-block-list">
<li><strong>SNF Site-of-Service Adjustment. </strong>CMS finalized a policy equalizing the facility and non-facility PE RVUs for specified nursing-facility E/M services. Under the prior methodology, a service furnished to a beneficiary during a covered Part A SNF stay was paid using the facility rate, while the same nursing-facility service furnished to a resident who was not in a covered Part A SNF stay could be paid using the higher non-facility rate. CMS concluded that the beneficiary’s Part A coverage status did not adequately reflect differences in the practitioner’s PE, because the services were furnished in the same type of care setting. Beginning in CY 2027, CMS will set the facility PE RVUs equal to the non-facility PE RVUs for CPT codes 99304-99310, 99315 and 99316. CMS did not adopt a broader elimination of PFS site-of-service differentials but indicated that it may consider related policies in future rulemaking.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Same-Day E/M + Minor Procedure. </strong>For CY 2027, CMS finalized a payment adjustment when a physician, or another physician in the same practice, furnishes a separately identifiable office/outpatient E/M service reported with modifier 25 on the same day as a procedure with a 0-day global period. Medicare will pay the highest-valued service at 100 percent of the otherwise applicable amount and reduce payment for the other affected same-day service or services by 20 percent. CMS narrowed the final policy from its proposal, which would have paid the lower-valued service or services at 50 percent and would have applied the adjustment to procedures with 0-, 10- and 90-day global periods.</li>
</ul>



<ul class="wp-block-list">
<li><strong>G2211/B1 Modifier. </strong>Beginning in 2027, CMS will transition the office/outpatient E/M visit-complexity payment currently reported using HCPCS code G2211 to a new B1 modifier appended to an eligible E/M base code. Modifier B1 applies when the practitioner serves as the continuing focal point for the patient’s healthcare needs or furnishes ongoing care related to a single serious or complex condition. When properly reported, modifier B1 will result in an additional payment equal to 16 percent of the payment amount for the underlying E/M service.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Global Surgery Data. </strong>CMS will pause the mandatory reporting of postoperative visits using CPT code 99024, which CMS has required for certain practitioners and procedures as part of its MACRA global-surgery data collection. CMS explained that it has taken several steps to improve payment accuracy for the global services and is continuing to explore further steps to improve accountability and enable more accurate payment.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Maternity Care Services Coding. </strong>CMS finalized changes to Medicare coding for maternity care services, adopting the revised CPT framework that moves away from the long-standing global maternity package toward more separately identifiable antepartum, labor and delivery, and postpartum services. The revised code set is intended to better reflect evolving clinical practice, including individualized prenatal care schedules. CMS also declined to finalize proposed HCPCS G-codes that would have preserved the prior global maternity coding structure, although the agency indicated that it may revisit bundled maternity coding in future rulemaking as it gains experience with the new code set.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Remote Monitoring. </strong>CMS extended the established-patient requirement to remote therapeutic monitoring (RTM) and will now require an initiating visit for both remote physiologic monitoring (RPM) and RTM. CMS explained that these requirements are intended to ensure that the billing practitioner has sufficient information about the patient’s current medical status and clinical needs before ordering and managing remote-monitoring services.</li>
</ul>



<ul class="wp-block-list">
<li><strong>RPM/RTM Staffing. </strong>CMS is adopting, but delaying until Jan. 1, 2029, a requirement that clinical staff furnishing RPM and RTM services be employed by the billing practitioner or practice, rather than being personnel supplied through third-party contractor. Through Dec. 31, 2028, practitioners may continue using otherwise permissible third-party clinical-staff arrangements, provided the services satisfy the applicable incident-to supervision, billing, and other RPM or RTM requirements.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Smoking Cessation/SBIRT. </strong>CMS will apply a 19.1 percent upward adjustment to the work RVUs for smoking and tobacco-use cessation counseling and for screening, brief intervention and referral to treatment (SBIRT) services. The finalized policy increases work RVUs for tobacco-cessation codes 99406 and 99407 and for SBIRT codes G2011, G0396 and G0397. CMS explains that the revisions better recognize the clinical intensity and work associated with these evidence-supported interventions.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Rural Health Clinic (RHC)/Federally Qualified Health Center (FQHC) Telehealth. </strong>RHCs and FQHCs may continue furnishing qualifying mental health visits via telecommunications technology through Dec. 31, 2027, without satisfying the otherwise applicable initial and recurring in-person requirements. The underlying requirements call for an in-person mental health service within six months before the telecommunications service and at least every 12 months thereafter. Importantly, this is a statutory delay, not a permanent repeal of the in-person requirements. Separately, the Consolidated Appropriations Act, 2026, extended through Dec. 31, 2027, CMS’s authority to pay RHCs and FQHCs for qualifying non-behavioral-health visits furnished through telecommunications technology.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Ambulatory Specialty Model. </strong>CMS established the mandatory Ambulatory Specialty Model in CY 2026 for selected specialists managing heart failure and low back pain. The CY 2027 final rule makes several technical and operational changes, including revisions to participant eligibility and exceptions, treatment of TIN changes and heart failure specialty redesignations, participant termination, data-submission requirements, the quality performance category, rural scoring adjustments, and collaborative care agreement requirements.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Shared Medical Appointments. </strong>CMS finalized separate Medicare payments for shared medical appointments, a care model in which multiple patients with common medical conditions receive care in a group setting. New HCPCS code G0686 describes a voluntary group-based medical session involving two to 10 patients and furnished by a physician or other qualified healthcare professional, with G0687 serving as the related add-on code. Both codes will be added to the Medicare Telehealth Services List beginning in 2027.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Advance Care Planning. </strong>CMS established new coding and payment for specified advance care planning services furnished by clinical staff under the direction of a treating physician or other qualified healthcare professional. The final rule identifies G0572 for the initial service and G0573 for additional 20-minute increments, with both services also added to the Medicare Telehealth Services List beginning in 2027.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Drug Inflation Rebates. </strong>The final rule makes several changes to implementation of the Medicare Prescription Drug Inflation Rebate Program, under which manufacturers may owe rebates when prices for certain Part B or Part D drugs increase faster than inflation. Of particular importance to 340B stakeholders, beginning Jan. 1, 2027, 340B covered-entity providers and suppliers must submit specified data elements for affected Medicare Part D claims to the Medicare Part D Claims Data 340B Repository.</li>
</ul>



<ul class="wp-block-list">
<li><strong>MSSP/ACOs. </strong>CMS finalizes many modifications to the Medicare Shared Savings Program (MSSP). Many changes are intended to provide accountable care organizations (ACOs) with additional financial incentives for participation, such as increasing the BASIC Track Level E shared savings rate from 50 percent to 60 percent. CMS recognizes that this change and other financial changes may impact ACOs’ decisions to participate in BASIC Track Level E or the ENHANCED Track. Accordingly, CMS is permitting eligible ACOs that have applied with a start date of Jan. 1, 2027, to change their final selection between the BASIC Track and the ENHANCED Track for a limited time. CMS also finalizes many other changes to the MSSP, including several changes regarding beneficiary assignment to an ACO and several changes to ACO reporting requirements. Notably, CMS also finalizes its proposal to allow eligible ACOs to reduce or eliminate Medicare Part B cost sharing for Part B services (excluding DME and drugs) for assigned beneficiaries subject to CMS approval beginning April 1, 2027. Participating ACOs finance the incentives and must apply for this flexibility in early 2027. CMS anticipates approving applications in the second quarter of 2027.</li>
</ul>



<ul class="wp-block-list">
<li><strong>ACO Longitudinal-Care B2 Modifier. </strong>CMS is establishing modifier B2 for eligible clinicians participating in specified qualifying Medicare ACO arrangements. When the applicable requirements are satisfied, modifier B2 will result in an additional payment equal to 32 percent of the payment amount for the underlying E/M service. The enhanced adjustment is intended to recognize the additional longitudinal care coordination and accountability associated with qualifying ACO participation.</li>



<li><strong>CLFS. </strong>CMS also addressed payment updates under the Clinical Laboratory Fee Schedule (CLFS). Annual payment reductions resulting from the private-payer data methodology are limited to 15 percent per year through CY 2029, continuing the statutory constraints on how rapidly CLFS rates may decline. The rule also revises the schedule for applicable laboratories to report private-payer rate and volume data to CMS, delaying the next reporting period and updating the associated regulatory requirements.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Quality Payment Program (QPP): Traditional MIPS Sunset and New Specialty Pathways.</strong>
<ul class="wp-block-list">
<li>Traditional MIPS reporting ends beginning with the CY 2031 performance period. CMS is continuing its transition away from traditional Merit-based Incentive Payment System (MIPS) reporting toward MIPS Value Pathways (MVPs). CMS believes MVPs allow for a more cohesive participation experience by connecting activities and measures from the four MIPS performance categories that are relevant to a specialty, medical condition or particular population. CMS is ending traditional MIPS reporting beginning with the CY 2031 performance period/2033 MIPS payment year, giving clinicians through CY 2030 to transition to either MVP reporting or, where applicable, participation in an Advanced Alternative Payment Model. CMS delayed the sunset by two years from the timeline contemplated in the proposed rule.</li>



<li>CMS adds Diabetic Disease, Hypertension and Hospitalist MVPs. CMS expands the MVP portfolio with three new pathways focused on diabetes, hypertension and hospitalist care, beginning with the CY 2027 performance period. The disease-focused pathways offer practices an opportunity to align reporting more closely with their patient populations before the traditional MIPS sunset. The Diabetic Disease MVP measures and addresses matters such as glycemic assessment, kidney health, foot care, patient self-management and diabetes-related costs. The Hypertension MVP addresses both treatment and prevention for high-risk patients, including measures concerning blood-pressure control, BMI screening, and tobacco screening and cessation. The Hospitalist MVP includes measures addressing heart failure therapy, advance care planning, high-risk medications in older adults, appropriate vancomycin use and avoidance of sliding-scale insulin monotherapy in hospitalized patients with diabetes.
<ul class="wp-block-list">
<li>For a separate discussion of QPP/MIPS changes relating to health information technology and privacy requirements, see our recent client alert, <a href="https://www.bakerlaw.com/insights/digital-health-and-ai-key-regulatory-reimbursement-and-policy-developments/">Digital Health and AI: Key Regulatory, Reimbursement and Policy Developments</a>.</li>
</ul>
</li>
</ul>
</li>
</ul>



<p>BakerHostetler’s Healthcare team provides counsel to healthcare organizations nationwide regarding Medicare reimbursement and regulatory compliance.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Gregory A. Tanner, Catherine (Kate) S. Stern, Natalie R. Berkowitz Cromartie, Nicole D. Katapodis, Valerie A. Morrow, Scott P. Robertson, Kierra I. Ross]]></dc:creator>
            <category>Alert</category>
            <category>Healthcare</category>
        </item>
        <item>
            <title><![CDATA[Digital Health and AI: Key Regulatory, Reimbursement and Policy Developments]]></title>
            <link>https://www.bakerlaw.com/insights/digital-health-and-ai-key-regulatory-reimbursement-and-policy-developments/</link>
            <guid>https://www.bakerlaw.com/?p=81276</guid>
            <pubDate>Mon, 09 Nov 2026 22:28:45 GMT</pubDate>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways"><strong>Key Takeaways</strong></h2>



<ul class="wp-block-list">
<li><strong>As AI becomes more entrenched in healthcare delivery, federal policy is beginning to evolve with it</strong>. CMS is considering how Medicare payments should account for AI-enabled care, has created an interim payment pathway for certain qualifying software-based diagnostic services and has expressly recognized potential uses of AI in Medicare Annual Wellness Visits and other clinical workflows. At the same time, pending legislation, including the PATIENT AI Act and Doctors Not AI Act, reflects growing congressional attention to AI reimbursement, regulatory oversight, privacy and security, and the appropriate role of human decision-making.</li>



<li><strong>Healthcare organizations should expect greater responsibility for AI governance and oversight</strong>. CMS’s new MIPS AI Improvement Activity provides MIPS credit to organizations for maintaining policies governing the evaluation, deployment and monitoring of AI, even as the ONC has scaled back certain standardized AI transparency and risk management requirements for certified health IT in the HTI-5 rule. Together, these developments reinforce the importance of organizations’ own AI governance, vendor diligence, contracting and post-deployment monitoring as AI use expands.</li>



<li><strong>Liability for patient harm involving AI is coming into sharper focus</strong>. The AMA’s new framework would allocate responsibility among clinicians, AI developers and deploying healthcare organizations based on each party’s authority, access to information and ability to control or mitigate the relevant risk. Notably, the framework rejects the assumption that simply keeping a physician “in the loop” necessarily shifts responsibility away from developers or health systems, which could influence AI contracting, governance and future malpractice and product liability arguments.</li>
</ul>



<p>Healthcare organizations continue to face a rapidly evolving landscape for the payment, deployment and governance of digital health and artificial intelligence (AI) technologies. In the past week alone, the Centers for Medicare & Medicaid Services (CMS) finalized both the 2027 Hospital Outpatient Prospective Payment System (OPPS) and Medicare Physician Fee Schedule (MPFS) rules. The Office of the National Coordinator for Health Information Technology (ONC) also recently streamlined portions of the federal health IT certification framework, and the Office for Civil Rights (OCR) issued a new Health Insurance Portability and Accountability Act (HIPAA) cybersecurity newsletter (Newsletter). The American Medical Association (AMA) entered the debate over AI use in healthcare by releasing a clinical AI liability framework, while recently introduced legislation and a Senate discussion draft signal increasing federal attention to the use of AI in healthcare.</p>



<h2 class="wp-block-heading"><strong>OPPS: CMS Recognizes Software as a Medical Service for Payment Purposes</strong></h2>



<p>In the Calendar Year 2027 OPPS final rule, CMS continued its recognition of the evolving role of software-based technologies in clinical diagnosis and decision-making. Specifically, CMS coined the term “Software as a Medical Service” (SaMS) to describe software-based technologies that support clinical decision-making through algorithmic analysis, including technologies that provide clinical diagnostic functionality. These technologies include clinical decision-support software, clinical risk modeling tools, and computer-aided detection technologies that analyze diagnostic images or use complex algorithms and predictive modeling to assist with diagnosis and treatment planning. CMS’s terminology change is intended to distinguish these medical-function technologies from general cloud-based Software as a Service products and other digital health tools, such as remote patient monitoring and prescription digital therapeutics.</p>



<p><strong>Interim OPPS Payment for SaMS.</strong> To address the challenges of reimbursing rapidly evolving SaMS technologies, CMS finalized an interim policy assigning qualifying SaMS services to New Technology Ambulatory Payment Classifications (APCs). New Technology APCs are temporary payment classifications used for new services for which CMS has insufficient claims and cost data to establish a permanent clinical APC assignment. CMS also established a new status indicator, O1, identifying SaMS services eligible for separate payment under the OPPS. The interim approach is intended to recognize the costs associated with these technologies while CMS develops a longer-term reimbursement framework. Importantly, the policy does not establish a general entitlement to separate payment for all AI-enabled or software-based clinical tools; payment remains dependent on the applicable service and coding requirements.</p>



<p><strong>Algorithmic Analyses of Laboratory Data.</strong> CMS also finalized a separate payment pathway for certain stand-alone algorithmic analyses performed on data from previously completed laboratory tests, including secondary analyses of genomic sequencing results. These services will be treated as “other diagnostic tests” payable under the OPPS rather than as clinical diagnostic laboratory tests under the Clinical Laboratory Fee Schedule (CLFS). CMS will assign qualifying services to New Technology APCs, with payment rates aligned with the corresponding CY 2026 CLFS rates. This change is particularly relevant to companies developing proprietary genomic and other laboratory data analytics, as well as to hospitals seeking to offer these services. It also recognizes that the clinical value of diagnostic information may arise from subsequent algorithmic analysis of existing laboratory data rather than only from the original laboratory test.</p>



<p>Taken together, these policies reflect CMS’s recognition that traditional Medicare payment categories may not adequately account for emerging software-based diagnostic services. Although the final rule does not establish a comprehensive reimbursement framework for SaMS, it creates distinct interim payment pathways for qualifying technologies and provides a basis for further development of Medicare payment policy in this area.</p>



<h2 class="wp-block-heading"><strong>MPFS: AI-Enabled Care, Remote Monitoring, Telehealth and Digital Quality</strong></h2>



<p>Technology also featured prominently in the MPFS. Although CMS did not establish a new AI-specific payment pathway, the final rule reflects increasing attention to how technology may affect physician work, practice resources, care delivery and quality measurement.</p>



<p><strong>AI and Technology-Enabled Care. </strong>CMS acknowledged that advances in technology, including generative and agentic AI, are poised to transform the patient experience and the role of clinicians but have not previously been taken into consideration when defining relative value units and the time and intensity of physician services. Accordingly, the MPFS includes a Request for Information (RFI) seeking industry input on the payment implications of technology-enabled primary care and how Medicare payment methodologies might be updated to account for the impact of technology and clinical AI on beneficiaries and clinicians.</p>



<p>The final rule also discusses responses to CMS’s earlier RFI on AI’s impact on healthcare delivery. CMS noted that AI adoption in primary care currently focuses largely on reducing administrative burdens and supporting clinical decision-making. AI documentation tools, such as ambient scribes, are among the most widely adopted, with an estimated 25 percent penetration among U.S. physicians according to CMS. CMS also identified OpenEvidence as likely the most widely used AI tool in primary care, noting that more than 40 percent of U.S. physicians had self-reported using the application, which allows clinicians to ask clinical questions and receive answers based on peer-reviewed journals and guidelines. Although AI-assisted care delivery agents have been deployed in some health systems, CMS does not believe they have yet achieved widespread use.</p>



<p>CMS also reported that many commenters expressed skepticism about AI in healthcare, citing concerns about current AI models and urging CMS to ensure that any AI-enabled care for which Medicare pays demonstrates proven clinical value. Nevertheless, commenters broadly supported AI tools that help clinicians synthesize longitudinal patient information, identify screening and vaccination gaps, flag risk factors, and generate clinically meaningful summaries from health assessments, prior visits, wearable data and test results. CMS also highlighted the value of automating repetitive, nonclinical tasks, such as questionnaire administration and documentation, to allow clinicians to focus more on patient interaction, care planning and shared decision-making. CMS indicated that it would consider this feedback in future rulemaking.</p>



<p><strong>AI and the Medicare Annual Wellness Visit (AWV). </strong>CMS also addressed how AI and other technology may support Medicare AWVs, while emphasizing that the AWV must continue to be performed by a physician or other health professional and that clinicians must retain responsibility for clinical decisions. CMS clarified that AI may support several components of the AWV, including administering the Health Risk Assessment, extracting medical history and provider information from the electronic medical record, reconciling medications for clinician verification, summarizing clinical information, administering clinician-selected depression screening instruments and asking functional ability screening questions for clinician review. CMS noted, however, that it was not aware of how AI could be used to conduct a cognitive assessment under the current regulatory standard.</p>



<p>CMS indicated that AI may also assist in drafting a personalized prevention plan, including individualized health advice and referrals, for clinician review and approval. AI could also be used to prompt discussions about advance directives, future care decisions and caregiver identification to support an advance care planning discussion as part of the AWV. CMS emphasized that software applications provided to beneficiaries to support implementation of a prevention plan must not constitute the practice of medicine or replace the beneficiary-clinician relationship and must comply with applicable fraud and abuse laws, including the federal Anti-Kickback Statute and beneficiary inducement prohibition. CMS may provide further guidance in future rulemaking.</p>



<p><strong>Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM).</strong> The MPFS finalizes several changes to Medicare coverage and payment requirements for RPM and RTM in response to findings by the Office of the Inspector General that additional oversight of RPM and RTM was needed given potential fraud, waste and abuse concerns. First, CMS extended the established-patient requirement to RTM, aligning it with RPM. Practitioners billing for either service must furnish a separately reportable initiating face-to-face visit, in person or via telehealth, before monitoring begins. Second, CMS finalized a requirement that clinical staff performing RPM and RTM services be directly employed by the billing practitioner or practice, subject to applicable incident to requirements. This requirement may materially affect digital health companies that provide outsourced monitoring services. CMS delayed its implementation until Jan. 1, 2029, giving providers and vendors additional time to evaluate and adjust their operating models.</p>



<p><strong>Telehealth: Platform Transparency and Extended Flexibilities. </strong>Congress extended several Medicare telehealth flexibilities through Dec. 31, 2027, including broader access to telehealth services from beneficiaries’ homes and audio-only telehealth. In implementing these extensions, CMS finalized the addition of several codes to the Medicare Telehealth Services List and confirmed that shared medical appointments (SMAs), or group visits for patients with a common condition, may be furnished via telehealth, subject to a limit of one SMA per beneficiary per week.</p>



<p>Separately, CMS finalized new telehealth modifiers, effective Jan. 1, 2027, for services furnished through certain virtual telehealth platform arrangements and for services furnished incident to. Although the modifiers do not currently affect payment, they will provide CMS with greater visibility into virtual-platform relationships and incident to telehealth arrangements. Virtual care companies and provider organizations should assess whether their contractual and operational arrangements fall within these categories and ensure that claims workflows capture the applicable modifiers.</p>



<p><strong>MIPS HIPAA Security Risk Analysis Requirement.</strong> Beginning with the CY 2027 performance period – the 2029 MIPS payment year – CMS will remove the separate Security Risk Analysis (SRA) attestation from the MIPS Promoting Interoperability category, recognizing that the HIPAA Security Rule independently requires covered entities and business associates to conduct an SRA. The attestation requirement was previously included to promote awareness of the HIPAA Security Rule requirements, but CMS concluded that established awareness of these requirements obviated the ongoing need to include the SRA measure. Importantly, removal of the MIPS attestation does not eliminate the underlying HIPAA obligation to conduct and document an SRA and implement appropriate risk management measures. It does, however, provide clinicians with greater flexibility in timing the SRA because they will no longer need to satisfy the MIPS-specific timing requirement that it be conducted or reviewed during the year in which the applicable performance period occurs.</p>



<p><strong>New MIPS Improvement Activity for AI Use. </strong>CMS finalized a new MIPS Improvement Activity, “Clinician Use of Artificial Intelligence (AI) to Improve Patient Care,” which requires participating clinicians and organizations to “establish and maintain organizational policies and procedures for AI use in healthcare settings that guide the evaluation, deployment, and monitoring of AI-enabled tools” to receive credit for the activity. The policies must address key AI model characteristics, including fairness, appropriateness, validity and effectiveness, as well as risk mitigation and escalation. CMS also identified examples of qualifying initiatives, including AI-supported clinical decision support, predictive analytics, risk stratification, clinical documentation, literature review, population health management and care-gap identification.While the new activity does not require MIPS-eligible clinicians to use AI or participate in the activity, it provides an opportunity for clinicians and organizations to receive MIPS credit for adopting policies and workflows that support responsible and transparent use of AI in clinical and operational settings.</p>



<p><strong>Electronic Prior Authorization. </strong>CMS established a voluntary electronic prior authorization measure for the CY 2027 performance period, which will become mandatory beginning with the CY 2028 performance period. The measure continues CMS’s broader effort to move prior authorization away from manual, fragmented processes and toward more automated, interoperable workflows.</p>



<h2 class="wp-block-heading"><strong>Removal of AI Transparency Requirements in the HTI-5 Rule</strong></h2>



<p>For years, ONC has revised the certification criteria that electronic health record systems must satisfy in order to participate in the ONC Health IT Certification Program. ONC’s latest regulation, the Health Data, Technology, and Interoperability: ONC Deregulatory Actions to Unleash Prosperity (HTI-5) final rule, streamlines several health IT certification requirements, although less extensively than initially proposed. Most significantly for AI-enabled health IT, the rule eliminates certain requirements under the Decision Support Intervention (DSI) certification criterion that required developers to provide standardized “model card” information about predictive algorithms, including their development, intended use, limitations, training data and performance. It also scales back requirements for risk analysis, mitigation and governance of predictive DSIs. These changes reduce AI-specific transparency and oversight through ONC’s certification program, potentially placing greater responsibility on healthcare organizations to address these issues through their own AI governance, vendor diligence and contracting.</p>



<p>ONC acknowledged that a large majority of commenters opposed removing these criteria, citing concerns about reduced transparency and risk management protections; potential shifts in evaluation, governance and liability burdens to providers; and risks to patient safety, clinician trust and organizations’ ability to assess bias and algorithmic performance. Commenters also questioned removing model card requirements less than two years after implementation, particularly as AI adoption accelerates. In response, ONC stated that certified health IT developers reported that most clinical users lack the time and technical capacity to engage with source-attribute information. ONC also noted that it had not identified peer-reviewed publications or trade press reports demonstrating that users of certified health IT relied on the transparency requirements. The resulting reduction in certification-based requirements underscores the importance of independent vendor diligence by healthcare organizations evaluating existing and contemplated AI uses.</p>



<p>Finally, although ONC has proposed several changes to the Information Blocking Rule through ongoing HTI rulemaking, as we previously <a href="https://www.bakerlaw.com/insights/whats-hot-in-healthcare-digital-health-regulatory-update/">analyzed</a>, it did not finalize those changes in the HTI-5 rule. ONC noted that they “remain under consideration as part of HHS’ ongoing efforts to address and eliminate information blocking.”</p>



<h2 class="wp-block-heading" id="h-hhs-ocr-reinforces-cybersecurity-expectations"><strong>HHS/OCR Reinforces Cybersecurity Expectations</strong></h2>



<p>OCR’s October <a href="https://www.hhs.gov/hipaa/for-professionals/security/guidance/cybersecurity-newsletter-october-2026/index.html">Newsletter</a> reminds the healthcare industry of essential cybersecurity steps drawn from the HIPAA Security Rule and prior OCR guidance. The Newsletter provides a useful checklist for healthcare organizations to assess their cybersecurity posture and identify potential gaps:</p>



<ul class="wp-block-list">
<li><strong>Phishing Awareness</strong> – Train employees to recognize and report phishing attempts. OCR notes that phishing simulations and periodic security updates can increase vigilance and help satisfy the Security Rule’s security reminders requirement.</li>



<li><strong>Strong Passwords</strong> – Require strong passwords for all users to help prevent unauthorized account access.</li>



<li><strong>Multifactor Authentication (MFA)</strong> – Use MFA to strengthen account security, with phishing-resistant MFA where available.</li>



<li><strong>Software Updates and Patching</strong> – Promptly install security updates and patches to address known vulnerabilities and protect systems.</li>



<li><strong>Logging</strong> – Record and regularly review user activity on business systems to identify suspicious behavior and potential security incidents.</li>



<li><strong>Data Backups</strong> – Maintain robust, retrievable backups of business data to facilitate recovery and support operational resiliency.</li>



<li><strong>Encryption</strong> – Encrypt electronic protected health information at rest and in transit wherever reasonable and appropriate. Where encryption is not reasonable and appropriate under specific circumstances, organizations must implement equivalent alternative safeguards, where reasonable and appropriate, and document the decision and its rationale.</li>



<li><strong>Incident Reporting</strong> – Although HIPAA does not require reporting cyber incidents to the Cybersecurity and Infrastructure Security Agency (CISA), OCR encourages organizations to consider doing so to help inform national threat assessments and responses. OCR notes, however, that reporting to CISA does not satisfy separate HIPAA breach reporting obligations to OCR.</li>



<li><strong>Incident Response Plans</strong> – Develop, maintain and regularly exercise incident response plans for common threats, including ransomware. OCR recommends realistic exercises involving leadership, legal counsel and technical personnel, with plans reviewed and tested at least annually.</li>



<li><strong>Preparing for Disruptions</strong> – Develop contingency plans to restore critical systems and maintain essential operations during disruptions, including backup, disaster recovery and emergency mode operation plans, as well as procedures for testing and revising those plans.</li>
</ul>



<p>Although the Newsletter largely reiterates existing OCR guidance and HIPAA Security Rule requirements, it provides a useful indication of the cybersecurity practices OCR expects regulated entities to prioritize.</p>



<h2 class="wp-block-heading"><strong>AMA AI Liability Framework</strong></h2>



<p>One of the more interesting health AI developments in recent weeks came not from a regulator but from the AMA. By advancing its own proposed framework for aligning responsibility for AI among physicians, healthcare organizations and AI developers, the AMA is beginning to put structure around the question of who should bear responsibility when AI contributes to patient harm. The AMA’s clinical AI liability framework focuses on who is best positioned to understand and control a particular risk. Its core principle is that responsibility should track each party’s authority, access to information and ability to prevent or mitigate harm. According to the AMA’s proposed framework:</p>



<ul class="wp-block-list">
<li><strong>Physicians</strong> are responsible for the clinical judgment they can meaningfully exercise, based on the information available to them and their ability to evaluate and challenge AI outputs.</li>



<li><strong>Developers</strong> remain responsible for the systems they build and the risks within their control, including designing safe and effective tools and providing users with information about intended use, performance and limitations.</li>



<li><strong>Deploying healthcare organizations</strong> bear responsibility for how AI is selected, implemented and governed, including pre-deployment evaluation, vendor contracting, interface configuration, clinician training and post-deployment monitoring.</li>



<li><strong>Patients</strong> must retain meaningful avenues for accountability and appropriate remedies when AI contributes to harm.</li>
</ul>



<p>The framework recognizes that responsibilities can overlap and that the presence of a clinician in the workflow does not necessarily eliminate the responsibility of the developer or deployer.</p>



<p>What makes the AMA’s framework particularly noteworthy is that it moves beyond generalized calls for “human oversight” and attempts to allocate responsibility according to who actually controls the relevant risk. The AMA expressly recognizes that physicians may be unable to detect AI errors when they did not select the technology, cannot inspect or validate the model or lack sufficient information or authority to meaningfully challenge its output. At the same time, developers must provide sufficient information for users to identify and respond to errors, while healthcare organizations must evaluate AI tools before deployment, provide appropriate training and monitor performance over time. The framework also emphasizes that generic warnings and disclaimers are not substitutes for meaningful transparency and safeguards. Although the framework is not law, it may inform evolving discussions regarding AI contracting, institutional governance and the allocation of responsibility when AI contributes to patient harm.</p>



<h2 class="wp-block-heading" id="h-legislative-outlook-congress-turns-its-attention-to-healthcare-ai"><strong>Legislative Outlook: Congress Turns Its Attention to Healthcare AI</strong></h2>



<p>Congress is also considering legislation that could shape the regulation and use of AI in healthcare. On Oct. 29, Senate HELP Committee Chairman Bill Cassidy released a discussion draft of the Protecting Americans Through Intelligent, Ethical, and Transparent Artificial Intelligence in Health Care Act, or PATIENT AI Act. The proposal addresses several key issues facing the industry, including U.S. Food and Drug Administration (FDA) and ONC oversight of AI-based health technologies, FDA review of software changes, HHS guidance on AI privacy and security, and a payment pathway for qualifying AI technologies. Although only a discussion draft, the proposal offers a broad potential framework for federal healthcare AI policy.</p>



<p>A separate bipartisan House proposal, the Doctors Not AI Act of 2026, focuses on AI use in health plan coverage decisions. The bill would prohibit AI systems from issuing or dictating adverse benefit determinations involving clinical judgment, requiring such decisions to be made by appropriately trained and licensed healthcare professionals. AI could still assist with administrative claims processing, but professionals could not simply defer to algorithmic recommendations. The proposal reflects growing congressional interest in requiring meaningful human involvement in AI-assisted coverage decisions, an issue also addressed in separate legislation concerning Medicare Advantage prior authorization.</p>



<p>Neither proposal has advanced beyond its current legislative stage, and their prospects will depend on congressional priorities and committee leadership in the next Congress. Together, however, they illustrate the expanding scope of federal attention to healthcare AI, from regulatory oversight and reimbursement to the limits of automated decision-making.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Vimala Devassy, Justin Chavez]]></dc:creator>
            <category>Alert</category>
            <category>Healthcare</category>
            <category>Telehealth</category>
        </item>
        <item>
            <title><![CDATA[Taking Leave Seriously: Allegheny County Significantly Expands Employers’ Paid Leave Obligations]]></title>
            <link>https://www.bakerlaw.com/insights/taking-leave-seriously-allegheny-county-significantly-expands-employers-paid-leave-obligations/</link>
            <guid>https://www.bakerlaw.com/?p=81289</guid>
            <pubDate>Mon, 09 Nov 2026 21:18:50 GMT</pubDate>
            <content:encoded><![CDATA[
<h2 class="wp-block-heading" id="h-key-takeaways"><strong>Key Takeaways</strong></h2>



<ul class="wp-block-list">
<li>Allegheny County adopted an ordinance requiring employers with 15 or more employees to provide eligible employees with up to 12 weeks of paid, job-protected parental leave at their base rate of pay, capped at $4,200 per week.</li>



<li>The ordinance also expands the county’s existing paid sick leave requirements, increasing annual leave to 72 hours for employers with 15 or more employees and 48 hours for smaller employers.</li>



<li>Employers must implement the new leave benefits by Oct. 17, 2027, and should use the implementation period to review and update their leave policies and practices.</li>
</ul>



<p>On Oct. 22, 2026, Allegheny County amended Article XXIV of the Allegheny County Health Department Rules and Regulations to require paid parental leave and expand the county’s existing paid sick leave requirements (the Ordinance).</p>



<h2 class="wp-block-heading" id="h-when-do-employers-need-to-comply"><strong>When Do Employers Need to Comply?</strong></h2>



<p>The Ordinance takes effect 180 days after enactment, or on April 20, 2027. Employers then have an additional 180 days, until Oct. 17, 2027, to implement the new requirements.</p>



<h2 class="wp-block-heading" id="h-covered-employers-and-employees"><strong>Covered Employers and Employees</strong></h2>



<p>The Ordinance applies to employers that employ 15 or more persons for a salary, wage, commission or other compensation. Employees generally must work at least 80 hours in Allegheny County during a 12-month period to be covered. Independent contractors, temporary and seasonal employees, federal and Pennsylvania state employees, and certain construction employees covered by collective bargaining agreements, however, are excluded from the Ordinance.</p>



<h2 class="wp-block-heading" id="h-paid-parental-leave"><strong>Paid Parental Leave</strong></h2>



<p>Eligible employees may receive up to 12 weeks of paid parental leave for a qualifying event. Full-time employees must have worked for the employer for at least 180 continuous days before leave begins, while part-time employees must have worked for the employer for at least 180 days and 625 hours during that period.</p>



<p>Qualifying events include:</p>



<ul class="wp-block-list">
<li>The birth of a child</li>



<li>A stillbirth or fetal death</li>



<li>The adoption of a child</li>



<li>The legal permanent placement, including a qualifying foster-care placement, of a child</li>
</ul>



<p>For a live birth, adoption or permanent placement, employees may use the leave during the 12 months following the qualifying event.</p>



<p>During leave, employees are entitled to their base rate of pay, up to $4,200 per week, as well as continuation of established employment benefits, including medical, dental and vision coverage. For part-time employees, the benefit is based on their average weekly hours during the six months preceding the leave request. Employers may provide the paid parental leave benefit through private insurance, but they remain responsible for any difference between the insurance benefit and the amount required by the Ordinance.</p>



<h2 class="wp-block-heading" id="h-interaction-with-other-leave"><strong>Interaction with Other Leave</strong></h2>



<p>Paid parental leave must run concurrently with leave under the federal Family and Medical Leave Act (FMLA) when an employee qualifies for both. Accordingly, employees will not receive an additional 12 weeks of paid parental leave for the same qualifying event after using FMLA leave. The eligibility requirements differ, however, and an employee may qualify for paid parental leave under the Ordinance after 180 days of employment before satisfying the FMLA’s 12-month service requirement.</p>



<p>If spouses or domestic partners work for the same employer, each eligible employee is entitled to the full paid parental leave benefit even if their leaves overlap.</p>



<h2 class="wp-block-heading" id="h-notice-and-job-protection"><strong>Notice and Job Protection</strong></h2>



<p>Employees must provide employers with 30 days’ written notice when the need for leave is foreseeable or as soon as practicable when advance notice is not possible. Employers may require reasonable documentation supporting the qualifying event and must provide a written eligibility determination within 10 business days after receiving the claim and required documentation.</p>



<p>Paid parental leave is job-protected leave, and employees generally must be restored to the same or a comparable position with equivalent seniority, status, benefits, pay, and other terms and conditions of employment upon returning from leave. The Ordinance also prohibits interference with or retaliation for an employee’s exercise of protected rights. Covered employers must provide employees with written notice of their rights upon hire and every year thereafter, and beginning one year after the Ordinance’s effective date, annually certify their compliance to the county.</p>



<h2 class="wp-block-heading" id="h-expanded-sick-leave-requirements"><strong>Expanded Sick Leave Requirements</strong></h2>



<p>The Ordinance also expands Allegheny County’s existing paid sick leave requirements.</p>



<ul class="wp-block-list">
<li>Employers with 15 or more employees: Eligible employees generally accrue at least one hour of paid sick leave for every 30 hours worked, up to 72 hours per year.</li>



<li>Employers with fewer than 15 employees: The amended paid sick leave provisions contemplate the same accrual rate, subject to a 48-hour annual limit. However, because the Ordinance’s amended definition of employer covers entities employing at least 15 people and therefore makes the mandate with respect to smaller employers inherently contradictory, it is unclear whether this requirement can be applied to smaller employers. Further county guidance may clarify the issue.</li>
</ul>



<p>The changes extend paid sick leave requirements to smaller employers and increase the amount of paid sick leave available to employees of larger employers.</p>



<h2 class="wp-block-heading" id="h-penalties-and-enforcement"><strong>Penalties and Enforcement</strong></h2>



<p>The Ordinance prohibits employers from interfering with or retaliating against employees for exercising protected rights. Employers that violate the Ordinance may be subject to a penalty of $100 per day per violation, as well as civil actions brought by employees. Prevailing employees may recover reasonable attorneys’ fees and costs.</p>



<h2 class="wp-block-heading" id="h-next-steps-for-employers"><strong>Next Steps for Employers</strong></h2>



<ul class="wp-block-list">
<li>Employers should use the Ordinance’s implementation period to review existing parental leave, paid sick leave, paid time off and FMLA policies, and to make any necessary changes.</li>



<li>Employers should pay particular attention to the Ordinance’s eligibility requirements and coordination with other available leaves, as well as the expanded paid sick leave requirements.</li>
</ul>



<p>Allegheny County’s expanded leave requirements are likely to have significant operational implications for employers, making a thorough understanding of their obligations essential. The BakerHostetler Labor and Employment Practice Group is available to help employers navigate these requirements.</p>
]]></content:encoded>
            <dc:creator><![CDATA[Christian R. White, Matthew C. Berger, Alexandra McCloy]]></dc:creator>
            <category>Alert</category>
            <category>Labor and Employment</category>
        </item>
    </channel>
</rss>