The FCA Insider

The FCA Insider

Insights and updates on False Claims Act Litigation

DOJ

DOJ’s New West Coast Strike Force Puts Health Care Providers on Notice

The DOJ’s National Fraud Enforcement Division announced on April 30, 2026, the formation of the West Coast Health Care Fraud Strike Force, a multi-district enforcement initiative spanning Arizona, Nevada and the Northern District of California. Announced by Assistant Attorney General Colin McDonald, the new Strike Force signals a significant escalation of federal healthcare fraud enforcement in the broader West Coast region and warrants close attention from healthcare providers, technology companies and other industry participants operating in the area.

Read on to learn more about the Strike Force and what industry participants should do to prepare.

OIG, Regulatory

HHS Inspector General Reminder: Kickback Liability Turns on Intent, Not Market Value or Stark Law Compliance

OIG FAQ

The U.S. Department of Health and Human Services Office of Inspector General (OIG) updated its FAQs on Fraud and Abuse Authorities to add a new answer on fair market value (FMV) in FAQ 17 and revise the answer on how the physician self-referral law (Stark Law) overlaps with the federal Anti-Kickback Statute (AKS) in FAQ 4. The takeaway from FAQ 4 and FAQ 17 is clear: An arrangement can violate the AKS even if the compensation is FMV or the arrangement fits within a Stark Law exception.

This update is not new law, but it is a strong reminder that AKS liability turns on intent, not on FMV or Stark Law compliance alone.

What the New FAQs Say, At a Glance

FAQ 17 is new. It asks whether arrangements with FMV remuneration can violate the AKS. OIG’s answer is that FMV is good practice (and often a required element of a safe harbor), but FMV alone is not a defense. AKS liability depends on the facts of the arrangement and the parties’ intent. The text of the AKS prohibition does not even use the term “fair market value,” and no safe harbor protects remuneration just because it is at FMV. Some safe harbors include FMV as one condition among several, but parties that focus only on FMV miss the other safe harbor conditions. OIG calls its position here “unwavering,” pointing to its compliance program guidance, a 2014 Special Fraud Alert (see page 4), and recent advisory opinions.

Revised FAQ 4 (see our generated comparison redline) now begins with an explicit “Yes”: A financial arrangement that satisfies a Stark Law exception can still violate the AKS. OIG explains that the Stark Law and AKS are separate statutes; the Stark Law is a civil strict liability statute, while intent is a critical element of the criminal AKS. Compliance with a Stark Law exception therefore does not by itself show the party lacks the intent that violates the AKS. Consider OIG’s example. Giving sporting event tickets to a physician who refers patients may fit the Stark Law’s nonmonetary compensation exception (42 C.F.R. § 411.357(k)), but it is unlikely to fit any AKS safe harbor, and the government would look at the full picture, including what the parties intended. Giving anything of value to induce or reward referrals may violate the AKS if the requisite intent is there, regardless of whether a Stark Law exception is also satisfied.

Practically, Why FMV and Stark Law Compliance Do Not Solve AKS Risk

The way AKS safe harbors work helps explain why FMV and Stark Law compliance matter but do not end the analysis. A safe harbor protects an arrangement from being treated as an AKS offense only when every element of that safe harbor is met in full. The space rental, equipment rental, and personal services and management contracts safe harbors are good examples. Each requires that compensation be consistent with FMV and not be set in a way that takes into account the volume or value of referrals or other business between the parties. Each also imposes a commercial reasonableness condition (i.e., the deal must make business sense): The space, equipment, or services may not exceed what is reasonably necessary for the commercially reasonable business purpose of the arrangement. That commercial reasonableness piece ties these safe harbors back to OIG’s prior guidance, including the sources cited in FAQ 17, which has long cautioned that even where contracts look fine on paper, sham arrangements will not be protected. Practically, the government will look behind the agreement to see whether payments are really tied to referrals.

There is no “FMV‑alone” safe harbor under the AKS. FAQ 17 reinforces that each stream of remuneration must squarely satisfy each condition of an applicable safe harbor to receive protection. When an arrangement does not fit a safe harbor, AKS exposure depends on the facts and circumstances, including the parties’ intent and whether the arrangement would make business sense even without the referrals. As OIG puts it, “while adhering to the practice of ensuring the fair market value of remuneration is a highly useful general practice, it is not a guarantee of legality.” The same is true for Stark Law exceptions: meeting one is required for Stark Law compliance, but it does not, on its own, shield the arrangement from AKS scrutiny.

The practical takeaway is to treat FMV and Stark Law exceptions as an initial foundation, not a cure for AKS risk. Either meet every element of an applicable AKS safe harbor or be ready to show, with contemporaneous documentation, that there was no knowing and willful inducement or reward for referrals (in plain terms, that the arrangement was not set up to encourage referrals). That documentation should include the legitimate business need for the arrangement and the deliverables that hold up regardless of any referrals. As the entertainment example above illustrates, nonmonetary benefits still warrant particular care under the AKS even when a Stark Law exception applies. For novel or close-to-the-line arrangements, the OIG Advisory Opinion process remains available for binding, arrangement‑specific analysis. The FAQs are a different tool, offering useful informal feedback for day‑to‑day compliance choices, but they are not binding and do not protect any specific arrangement from enforcement.

Where This Fits in OIG’s Informal Guidance Effort Since 2023

The April 23, 2026, updates are part of OIG’s ongoing use of informal FAQs as a compliance resource. OIG opened this channel in 2023 to take general questions about the AKS, the Beneficiary Inducements civil monetary penalty (CMP) and related enforcement topics, while keeping the formal Advisory Opinion process for binding, fact‑specific determinations. As we discussed in our April 2023 overview, OIG launched the FAQs to answer general industry questions faster and more efficiently. Recently, OIG also added an Advisory Opinion FAQ addressing what happens if the facts or law change after issuance of a favorable opinion. The April 2026 updates show that OIG is in fact maintaining and refreshing the FAQs over time.

Conclusion

The underlying law has not changed with these FAQs, but OIG’s message is worth hearing again: Documenting FMV or fitting within a Stark Law exception does not on its own eliminate AKS risk. As discussed above, AKS risk turns on intent, and the better practice for arrangements outside a safe harbor is to pair FMV with documentation of a legitimate business purpose that would hold up even without any referrals. For day-to-day compliance, the refreshed FAQs are a useful reminder. OIG looks at the circumstances and intent behind an arrangement.

McGuireWoods’ Healthcare Compliance, Regulatory & Policy attorneys continuously monitor OIG developments and guidance affecting the healthcare industry. For more information, contact one of the authors of this article.

Regulatory

GSA AI Procurement Rules Would Introduce New Disclosure and Use-Rights Requirements for Federal Contractors

The General Services Administration Federal Acquisition Service has released draft contract terms and conditions related to AI-related procurements through a new proposed GSAR clause 552.239-7001, “Basic Safeguarding of Artificial Intelligence Systems” (February 2026), that would impose material new requirements on contractors and service providers supplying AI capabilities to the federal government. If adopted, the clause would be inserted into all solicitations and contracts for AI capabilities and would govern data rights, disclosure obligations, security protocols and performance standards for AI systems used in federal operations. Federal contractors, technology vendors, and their in-house operations and counsel teams should closely review the proposed terms, as they represent one of the most comprehensive efforts to date to regulate the procurement and use of AI systems across the federal enterprise.

The proposed clause would significantly alter the landscape for companies providing AI capabilities to the federal government. Read on to learn more about the proposed rule and its implications.

CMS Guidance, OIG, Regulatory

Long Anticipated Medicare Advantage Compliance Guidance Heightens Investor and Provider Scrutiny

In February 2026, the Department of Health and Human Services, Office of Inspector General (HHS-OIG) issued its highly anticipated Industry Compliance Program Guidance for Medicare Advantage (MA ICPG), the first such compliance guidance for the MA industry in over 25 years. The MA ICPG is the second industry segment-specific compliance guidance published in a series for providers, suppliers, and other participants in the health care industry. The first was a 2024 nursing facility ICPG.

The guidance comes as MA now covers more than half of all Medicare enrollees. The program’s capitated payment structure generally pays Medicare Advantage Organizations a fixed monthly amount per enrollee. This model creates financial incentives that run throughout the entire MA ecosystem, touching plans, providers, investors and vendors alike, but in a manner different from traditional fee-for-service. While the MA ICPG is voluntary, nonbinding guidance, it carries significant practical weight.

Read on to learn more about the guidance and why investors, owners and operators of MA-related businesses as well as providers contracting with MA plans should treat the MA ICPG as a signal of HHS-OIG’s current enforcement priorities and a benchmark against which their compliance programs will be measured.

CMS Guidance, Stark Law

CMS Reaches $100 Million in Stark Self-Disclosure Settlements

The Centers for Medicare & Medicaid Services (CMS) recently released data on its 2025 settlements of voluntary self-disclosures related to past violations or potential violations of the physician self-referral law (the Stark Law). Generally, two notable items arise from our annual review of CMS’ settlement data.  First, CMS has now reported aggregate settlements reaching $105,090,031. Second, CMS reported the largest Stark Law settlement: $2,683,066 more than doubling the previous record high of a single settlement from 2018.  Read on for more with respect to the CMS settlement data and potential lessons.  

In 2025, CMS settled 244 self-disclosures, with settlement amounts totaling over $20,396,958 in the aggregate. This represents a decrease from the record-breaking 314 settlements in 2024 that had an aggregate total of $24,737,356, but the 2025 totals remain among the highest in the program’s history and reflect CMS’ continued commitment to processing self-referral disclosure protocol (SRDP) submissions. Notably, 2025 produced the highest individual settlement amount on record, with settlement amounts in 2025 ranging from $2 to $2,683,066. This new record individual settlement represents a significant outlier and demonstrates the potential magnitude of liability that can arise from Stark Law violations.

 

As of December 31, 2025, CMS settled a total of 1,234 SRDP submissions since the SRDP’s inception in 2011. Additionally, 373 disclosures have been withdrawn, closed without settlement, or settled by CMS’s law enforcement partners.

This represents a total of aggregate settlements reaching $105,090,031, since 2011, with amounts in the last four reported years exceeding every year prior under the SRDP process.

 

Background

SRDP submissions stem from the highly technical Stark Law, which generally prohibits a physician from making a referral for designated health services (which include clinical laboratory services, radiology and certain other imaging services, and durable medical equipment and supplies) payable by Medicare to an entity with which the physician (or an immediate family member of the physician) has a financial relationship, unless an exception is satisfied. The Stark Law has strict liability consequences and violations are often inadvertent. Therefore, at the direction of Congress, CMS created the voluntary SRDP for healthcare providers and suppliers to self-disclose actual or potential violations of the Stark Law to resolve overpayment liability for the disclosed conduct.

As CMS does not report on individual settlements, we closely monitor the annual information related to SRDP settlements to determine if there are trends or other information that can be helpful when advising on how best to address technical Stark Law concerns. Because disclosures of actual or potential violations of the physician self-referral law include proprietary, confidential, or otherwise nondisclosable information, CMS presents settlement information on an aggregate basis.

Continued Processing Efficiency

The sustained high volume of settlements in 2024 and 2025 demonstrates CMS’s continued focus and efforts to work through SRDP submissions more expeditiously than in the past. Our anecdotal experience reinforces this trend, as we have seen responses to submissions and settlements occurring on a more rapid basis than in prior years. In fact, some settlements are offered to clients the same calendar year as the SRDP submission. This is a material change from earlier in the decade when a historic backlog led many providers to experience significant waiting periods.

 

The Disclosures settled by year further demonstrates the pace CMS has maintained in processing disclosures post-Covid.  In the last two years, CMS has settled nearly half of all disclosures since 2011.  The last four years represent 67.8% of all settlements, and 63.7% of the settlement dollars.  On the other hand, the slight decrease compared to 2024 ends a three-year trend where CMS settled more disclosures year-over-year.

Average Settlements

This year, in addition to the records described above, we note that the average settlement number $83,594.09 in 2025 is well within the range that we have seen in recent years, as reflected in the chart below. Indeed, this is very close to the 2021 and 2024 averages, suggesting that the range of settlements appear to continue to converge (though we recognize that a settlement number is fact-dependent, and these averages may just be coincidental based on specific submissions).

 

Key Takeaways

The 2025 settlement data provides several important observations for providers considering or engaged in the SRDP process. First, while the number of settlements decreased from the record 314 in 2024 to 244 in 2025, this still represents the second-highest annual settlement total in program history and suggests CMS continues to prioritize clearing its SRDP backlog.

Second, the record-high individual settlement of $2,683,066 in 2025 is a notable development. This eclipses the prior record of $1,196,188 from 2018 by more than double and serves as a reminder that settlement amounts remain highly fact-dependent. A number of factors may contribute to the exact numeric value of a specific settlement, and one or two outliers with very high or low settlement values can skew the average settlement amount. Indeed, the lowest settlement last year was $2.

Third, the aggregate settlements exceeding $100 million since 2011 underscore the significant financial implications of Stark Law compliance and the importance of proper arrangement structuring. The sustained high settlement numbers in 2024 and 2025 give those considering the SRDP process further context that settlement may come quicker than a decade ago. It also shows the SRDP process continues to be a viable path for providers and suppliers, commonly used by the industry.

We will continue monitoring CMS statements on SRDP settlements in future years to examine what other trends the provider community may be able to glean from these announcements.

Defense Arguments, FCA Litigation

Ninth Circuit Ruling in FCA Case Predicated on 340B Pricing Violations Has Significant Implications for Pharma Manufacturers 

On March 17, 2026, the United States Court of Appeals for the Ninth Circuit issued a significant opinion in United States ex rel. Adventist Health System of West v. AbbVie Inc., [1] reversing the district court’s dismissal of a qui tam complaint brought under the False Claims Act (“FCA”) against four major drug manufacturers. The Ninth Circuit held that the FCA provides an independent mechanism for relators to bring claims alleging fraudulent drug pricing in violation of the Public Health Service Act’s Section 340B Program (“the 340B Program”), [2] even though Section 340B does not provide a private right of action. The ruling has important implications for pharmaceutical manufacturers participating in the Section 340B Program.

Background

The 340B Program requires participating drug manufacturers to sign a pharmaceutical pricing agreement (“PPA”) with the Secretary of Health and Human Services and sell drugs to qualified health-care facilities (“covered entities”) at or below statutory ceiling prices in order for their products to be reimbursed by Medicare and Medicaid. The formula for setting the ceiling price of the drug is defined in the statute; the ceiling price is determined by taking the Average Manufacturer Price (AMP) and subtracting the Unit Rebate Amount (“URA”). Under this formula, though rare, drug prices could fall to zero or below zero when the drug price had increased far beyond the rate of inflation. Health Resources and Services Administration (“HRSA”), the agency which operates 340B, finalized a rule effective January 1, 2019, that these drugs would be priced at $0.01, hence the term “penny pricing. Even outside of “penny pricing”, 340B prices generally are roughly 55% of the list price for drugs in the aggregate. [3]

A critical aspect of the 340B Program that is fundamental to the current decision is that there is no private right of action under the 340B Program for covered entities to pursue claims of overcharging of drugs by manufacturers; as the Supreme Court held in Astra USA, Inc. v. Santa Clara County, 563 U.S. 110 (2011), covered entities alleging pricing violations must instead pursue relief through Section 340B’s Administrative Dispute Resolution (“ADR”) process.

The Alleged Fraudulent Scheme in Adventist

Adventist Health System of West (“Adventist”), a provider whose medical clinics and facilities are eligible for 340B pricing as a “Covered Entity” under the statute, brought a qui tam action alleging that the defendant drug manufacturers knowingly charged “materially false, unlawfully inflated prices” for their drugs, which had “no relation to the statutory formula” for years preceding the issuance of a HRSA final rule in 2019 that promised “hefty civil penalties for non-compliance with the 340B Ceiling Price formula”.

Adventist alleged that the manufacturers’ fraudulent 340B pricing therefore caused the government to overpay through Medicaid reimbursements, Medicare cost-based payments to critical access hospitals, and direct purchases by government-funded prisons and clinics. Importantly, Adventist did not seek to recover its own losses as a covered entity but instead sought to recover on behalf of the government, claiming the fraud “caused the federal and state governments to wrongly pay hundreds of millions of dollars.”

The District Court Dismissal

The manufacturers moved to dismiss on several grounds including arguments that the complaint failed to adequately allege falsity and scienter, that the qui tam action was inappropriate because Adventist was not “an original source” as the allegations had been publicly disclosed prior to the action, and finally that Astra barred the action because it was an attempt by a private party to enforce the requirements of the 340B Program.

The district court did not address the first two grounds, instead focusing its grant of dismissal on the third prong, that the FCA action brought by Adventist was “in essence claims to enforce Section 340B” and that allowing Adventist to proceed would disrupt Congress’s chosen enforcement scheme. Citing the language in Astra, the district court reasoned that even when faced with reports of insufficient enforcement of the 340B Program, Congress created the ADR rather than a private right of action. Further, the alleged falsity that is critical to the FCA action is directly a result of a failure to comply with the statutory requirements of the 340B Program, and the current action was just an attempt to enforce those requirements. The district court dismissed the complaint with prejudice, essentially finding that the FCA claims were an inappropriate attempt at an “end-run” around the Supreme Court’s clear holding in Astra.

The Ninth Circuit’s Decision

The Ninth Circuit reversed, holding that Adventist stated cognizable claims under the FCA and satisfied the necessary pleading requirements. The court’s analysis rested on the following principal grounds:

The FCA Provides an Independent Right of Action Not Barred by the 340B Program

The court held that the FCA provides an independent mechanism through which Adventist, as a relator standing in the shoes of the government, can assert its claims, regardless of the absence of a private right of action under Section 340B. Relying on its prior decision in United States ex rel. Sutton v. Double Day Office Services, Inc., 121 F.3d 531 (9th Cir. 1997), the court explained that FCA plaintiffs bring their actions “in the name of the United States,” making it “irrelevant” that the relator happens to also be a covered entity that lacks a private right of action arising from its own alleged damages under the underlying statute. The government is the real party in interest, and Adventist seeks redress on the government’s behalf, and does not seek to personally recover from the alleged overcharging.

Adventist is Not Suing to Enforce the 340B Drug Program, it is Bringing a False Claims Action

The court made a clear distinction between Adventist’s FCA claims and the breach-of-contract claims at issue in Astra. In Astra, the Supreme Court held that a plaintiff’s suit to enforce PPAs was “in essence a suit to enforce [Section 340B] itself” and was therefore barred. In contrast, the Ninth Circuit held that Adventist brings a “prototypical FCA action” that does not allege defendants are liable only because they violated Section 340B, it alleges the defendant’s actions caused the submission of false claims which resulted in distinct financial losses to the government through the overpayment of millions of dollars through Medicaid, Medicare, and government-funded clinics.

Notably, the court emphasized the difference in relief sought. In a 340B Program ADR proceeding, a covered entity may obtain reimbursement of overcharges or termination of a manufacturer’s pricing agreement, similar to the breach of contract damages that were the subject of the Astra case the district court relied on for its holding. By contrast, Adventist sought FCA damages for the government, including civil penalties of $5,000 to $10,000 per false claim plus treble damages. However, even though Adventist could receive compensation as relator in a non-intervened case (25 to 30 percent of any recovery), the court held that this difference in relief is yet another example of how the Adventist action differed from a repackaged private claim to directly enforce the requirements of the 340B Program.

Barring Adventist’s Claims Would Undermine the FCA

The court observed, citing the Government’s amicus brief, that the FCA is “the federal government’s primary tool to combat fraud and recover losses due to fraud in federal programs,” and that Congress intended it “to reach all types of fraud, without qualification, that might result in financial loss to the government.” The court noted that Congress uses specific statutory exceptions to preclude FCA actions, such as it has when barring claims under the Internal Revenue Code, claims by armed forces members against fellow service members, and claims against members of Congress or the judiciary. There is no similar exception for 340B and the court lacks authority to create such an exception. Finally, the court held that reading such an exception into the FCA would require a disfavored finding of implied preemption.

Falsity Was Plausibly Pled

The court also rejected the defendants’ alternative argument that Adventist failed to plausibly plead the falsity element of its FCA claims. The defendants argued that pre-January 1, 2019 claims should not be permitted because there were no civil penalties for such actions prior to the effective date. The court found this argument unpersuasive, noting that Adventist “plausibly alleges that the plain text of the statutory formula did not ‘authorize any pricing over $0.01 regardless of the existence of a regulation,’” and that the government had “formally adopted a written guidance in 2011 which expressly directed manufacturers to charge $0.01 if the statutory formula resulted in a negative Ceiling Price.” 

What it All Means: Potential New Exposures for Pharmaceutical Manufacturers, and an Affirmation of the Expanse of the FCA

This case has broad implications, for both health care systems and pharmaceutical manufacturers. It is important to note that this case is at an early stage. The court reversed the dismissal and remanded for further proceedings; it did not reach the merits of Adventist’s claims. The case will now return to the district court, where discovery and additional motion practice will determine whether Adventist can substantiate its allegations. Further, the Adventist decision is currently limited to the Ninth Circuit, and there is little insight into how a similar case would play out in another Circuit Court. 

A clear takeaway from this case is the potentially expanded FCA exposure for pharmaceutical manufacturers. The decision confirms that drug manufacturers participating in the 340B Program face potential FCA liability for allegedly overcharging covered entities, even though Section 340B itself does not provide a private right of action. The FCA’s qui tam mechanism affords putative relators an independent avenue to bring claims on behalf of the government, with the prospect of civil penalties and treble damages. Indeed, one whistleblower law firm commenting on Adventist has claimed that the case “Opens Up [a] Whole New World of Potential Qui Tam Cases.” Of note, though, where the hospital bills the government a flat rate (such as DRG code) for an inpatient stay or a provider bills for a bundled payment for a procedure and that flat global reimbursement includes any drugs administered to the beneficiary, the alleged violation of 340B will not have caused the submission of a false claim or inflated reimbursement and, so, in that case the alleged violation of 340B cannot serve as predicate for an FCA violation.

The Adventist decision is another confirmation that the courts may continue to assert an expansive reading of the FCA and that may have significant implications for pharmaceutical manufacturers who participate in the 340B program. We will continue to monitor developments in this case and related litigation. Companies participating in the 340B Program should carefully evaluate their compliance with statutory pricing requirements in light of the potential FCA risk and exposure.


[1] United States ex rel. Adventist Health System of West v. AbbVie Inc., No. 24-2180 (9th Cir. Mar. 17, 2026)

[2] 42 U.S.C. § 256b

[3] Drug Channels reports that using 2024 data the wholesale acquisition cost (WAC), also known as the “list price” of 340B purchases was $147.8 Billion, while the actual 340B price was $81.4 Billion, implying a 55% discount. Fein, Adam, Drug Channels: 340B Hit $81 Billion in 2024 (+23%): Why CMS and the IRA Are Poised to Cool the Program’s Runaway Growth, December 15, 2025.

DOJ, FCA Litigation, Uncategorized

New Executive Order Targets DEI Practices by Federal Contractors, Imposes Mandatory Contract Clause and FCA Liability

Continuing his administration’s efforts to eliminate diversity, equity and inclusion (DEI) activities, President Donald Trump signed an executive order, “Addressing DEI Discrimination by Federal Contractors,” on March 26, 2026, that directs all executive departments and agencies to include a new clause in all federal contracts and subcontracts prohibiting what the order defines as “racially discriminatory DEI activities.” The order represents another escalation of the administration’s efforts to restrict DEI programs in the federal contracting space — building on Executive Order 14173 and the Department of Justice’s May 2025 Civil Rights Fraud Initiative — and carries substantial enforcement implications, including potential liability under the False Claims Act (FCA).

Read on for key provisions of the new executive order, analysis of practical implications for federal contractors and subcontractors, and recommended steps for compliance.

Regulatory

New GSA Proposal Could Expose Federally Funded Institutions With Programs Perceived as DEI-Related

The General Services Administration has proposed requiring all federal funding recipients to certify that they do not maintain diversity, equity, inclusion and accessibility programs. Recipients also would also need to certify they are not knowingly hiring or recruiting undocumented staff.

The GSA estimates the proposal would impact approximately 222,760 entities — including colleges and universities. If enacted, the certification requirements would expose grant recipients to potential liability under the False Claims Act. The deadline for public comments is March 30, 2026.

Read on to learn more about the GSA proposal and its potential impacts on federally funded institutions.

DOJ

DAAG Provides Views on FCA Enforcement Focus: Targeting Discrimination, Not DEI Programs Per Se

At the Federal Bar Association’s 2026 Qui Tam Conference on Feb. 19, 2026, Deputy Assistant Attorney General Brenna Jenny delivered a keynote speech that provided insight into the DOJ’s enforcement priorities and viewpoints on FCA enforcement. From her perspective, the DOJ is not investigating federal contractors and grant recipients for having DEI programs, but for potentially engaging in discrimination through their implementation of those programs. She emphasized that companies could be found to engage in discrimination with or without DEI programs and can also operate DEI programs without engaging in discrimination.

Read on to learn more about the specific programs and practices that, according to Jenny, the DOJ has been reviewing for potential violations of federal antidiscrimination laws.

OIG, Regulatory

HHS OIG Issues Guidance on Anti-Kickback Statute Implications for Direct-to-Consumer Drug Sales Ahead of TrumpRx Launch

In advance of the anticipated rollout of the “TrumpRx” website, a platform promising lower-priced drugs sold directly to consumers, the Office of Inspector General of the Department of Health and Human Services released a special advisory bulletin on Jan. 27, 2026, outlining the Federal Anti-Kickback Statute implications for direct-to-consumer drug sales. The OIG concludes that the risk of AKS violations is minimal if certain guidelines are followed, adding that its bulletin “clears the path” for DTC programs including the TrumpRx program. However, a letter from Sens. Richard Durbin, Elizabeth Warren, and Peter Welch to the OIG suggests that not all stakeholders share this confidence in TrumpRx, citing to concerns arising from a recent investigation into other DTC platforms. Pharmaceutical companies and other stakeholders can submit public comments until March 30, 2026. Read on to learn more about the guidance and what the pharmaceutical industry should know.

We use cookies to enhance your experience of our website. By continuing to use this website, you agree to the use of these cookies. For more information and to learn how you can change your cookie settings, please see our policy.

Agree