Note: This article is a publication-ready legal and healthcare policy overview based on publicly available U.S. regulatory materials, court docket summaries, hospital association updates, state law materials, and healthcare industry reporting. It is informational only and is not legal advice.
The first week of December 2025 was not exactly a quiet holiday warm-up for the 340B Drug Pricing Program. While everyone else was pretending their inbox could survive until January, 340B litigants were busy filing responses, fighting preliminary injunctions, defending state contract pharmacy laws, and opening a fresh front in New Mexico. The week of December 2 to December 8, 2025, showed once again that 340B litigation is not a side issue in healthcare policy. It is now one of the main arenas where drug pricing, state authority, federal oversight, rural access, pharmacy operations, and hospital financing collide.
The central theme for the week was contract pharmacy. That phrase may sound like something only compliance officers discuss after their third coffee, but it sits at the heart of today’s 340B disputes. Covered entities such as safety-net hospitals and community health centers often rely on outside pharmacies to dispense 340B-priced drugs. Manufacturers argue that broad contract pharmacy networks can create risks of duplicate discounts, diversion, and insufficient claims transparency. Hospitals and health centers counter that contract pharmacies are often essential for patients who do not live next door to an in-house hospital pharmacy. In rural America, “just use the hospital pharmacy” can be about as practical as suggesting patients pick up prescriptions by carrier pigeon.
Why This 340B Litigation Week Matters
During December 2 to December 8, four major litigation developments stood out. First, in a case challenging South Dakota’s 340B contract pharmacy law, the state government filed its response to the manufacturers’ request for a preliminary injunction. Second, in Oklahoma, defendants opposed a preliminary injunction request in a case brought by a pharmaceutical trade association challenging Oklahoma’s contract pharmacy statute. Third, another Oklahoma case saw further motion practice over discovery, including a response supporting a protective order and stay. Fourth, a pharmaceutical trade association filed a new complaint against New Mexico’s attorney general, challenging that state’s 340B contract pharmacy law.
Put simply, this was not a week of final answers. It was a week of positioning. Parties were building records, testing arguments, and asking courts to decide whether state laws protecting contract pharmacy access can stand alongside the federal 340B statute. The difference matters because preliminary injunctions can determine what happens while litigation crawls forward. In healthcare, “temporary” can still mean months of operational disruption, cash-flow stress, patient confusion, and a compliance team quietly developing a twitch.
Quick Refresher: What Is the 340B Program?
The 340B Drug Pricing Program requires participating drug manufacturers to sell certain outpatient drugs at discounted prices to eligible safety-net providers. Eligible covered entities include many federally supported health centers, Ryan White HIV/AIDS clinics, children’s hospitals, disproportionate share hospitals, critical access hospitals, and other providers serving vulnerable populations. The purpose is to help these providers stretch limited resources, serve more patients, and offer more comprehensive services.
In the classic 340B model, the covered entity purchases drugs at the 340B ceiling price. The controversy grows when the covered entity uses outside pharmacies to dispense those drugs. Contract pharmacy arrangements have become more common since federal guidance in 2010 allowed covered entities to use multiple contract pharmacies. Manufacturers have increasingly pushed back, especially since 2020, by limiting contract pharmacy access or requiring claims data before honoring 340B pricing. That pushback triggered a wave of litigation and state legislation.
The Core Legal Fight: Federal Silence vs. State Action
The major legal question is deceptively simple: if the federal 340B statute does not clearly say how drugs must be delivered to patients through contract pharmacies, can states step in and regulate that delivery? Manufacturers say many state laws are preempted because they effectively expand the federal 340B program and impose new obligations on companies that participate in Medicaid and Medicare. States, hospitals, and health centers argue that these laws regulate pharmacy access and prevent discriminatory distribution practices that undercut patient care.
Federal courts have not spoken with one perfectly synchronized voice. The Eighth Circuit upheld Arkansas’ 340B contract pharmacy protection law, and the U.S. Supreme Court declined to review that result. Meanwhile, other courts have been more receptive to manufacturer arguments, especially where state laws appear to restrict manufacturers’ ability to obtain claims data or directly regulate obligations tied to federal 340B participation. This patchwork is why December 2025 litigation activity mattered: each state case has become another tile in a national mosaic that nobody has fully assembled yet.
South Dakota: The State Responds in the Preliminary Injunction Fight
South Dakota entered the spotlight because its 2025 contract pharmacy law was designed to stop manufacturers from interfering with arrangements between 340B covered entities and pharmacies. South Dakota Senate Bill 154 prohibited pharmaceutical manufacturers from blocking or restricting 340B-related contract pharmacy relationships and created penalties for violations. AbbVie and related entities challenged the law, arguing that federal law preempts South Dakota’s approach and that the state cannot impose contract pharmacy obligations beyond the federal 340B statute.
During the December 2 to December 8 update period, the government filed its response to the plaintiffs’ motion for a preliminary injunction. That filing mattered because the court was being asked to decide whether South Dakota’s law should be paused before the case reached a final judgment. For covered entities, the state’s position represented a defense of local access and continuity of care. For manufacturers, the injunction request represented a bid to prevent a new state-level compliance regime from taking effect while core constitutional and statutory questions remained unresolved.
The South Dakota dispute fits a familiar pattern. The state says its law protects patient access, especially for rural communities and safety-net providers. Manufacturers say the law interferes with a carefully balanced federal program, imposes additional requirements, and risks undermining federal mechanisms designed to prevent duplicate discounts and diversion. This is the 340B version of two people arguing over the thermostat: one says the room is freezing, the other says the furnace is being abused, and the judge has to decide who gets control of the dial.
Oklahoma: A Partial Injunction and More Motion Practice
Oklahoma’s 340B Nondiscrimination Act, House Bill 2048, was another major battleground. The law targeted manufacturer restrictions on 340B contract pharmacy arrangements and included provisions involving discriminatory actions, enforcement, reimbursement, and state oversight. Pharmaceutical manufacturers and industry challengers argued that the law went too far by requiring manufacturers to provide 340B pricing through contract pharmacies in ways not required by federal law.
By the time of the December 2 to December 8 update, the Oklahoma litigation already had an important preliminary injunction ruling in the background. A federal court had granted in part and denied in part preliminary injunction requests, blocking enforcement of key provisions while allowing other aspects of the litigation to proceed. During this update period, defendants filed opposition papers in one case brought by a pharmaceutical trade association, and in a related manufacturer case, the defendant supported a motion for a protective order and stay of discovery.
These procedural moves may sound dry, but they are not filler. Discovery disputes can shape the evidence available to the parties. A stay of discovery can slow expensive fact-gathering while legal issues are sorted out. A protective order can limit burdens or protect sensitive information. In 340B litigation, discovery may involve claims data, pharmacy network practices, manufacturer policies, covered entity operations, and internal communications about compliance. In other words, the parties are not arguing over paperclips. They are arguing over the engine room of the 340B business model.
New Mexico: A New Complaint Opens Another Front
The newest development for the week was the complaint filed against the New Mexico attorney general by a pharmaceutical trade association. New Mexico’s 340B law was designed to protect contract pharmacy access, with particular attention to health centers and other safety-net providers. The lawsuit challenged the statute as another example of state overreach into an area the manufacturers argue belongs to federal law.
New Mexico’s case is important because it shows that the industry’s litigation strategy remained active and expanding in late 2025. Rather than waiting for appellate courts to settle every issue in earlier cases, trade associations and manufacturers continued challenging new state laws as they appeared. For states, this means passing a 340B contract pharmacy protection bill is no longer the end of the policy process. It is often the beginning of litigation season.
For community health centers, the New Mexico dispute carries practical significance. Health centers often rely on contract pharmacies because their patients may face transportation barriers, work schedule constraints, limited pharmacy options, or chronic disease management needs that require reliable access to medications. Manufacturers, however, continue to argue that contract pharmacy arrangements can obscure whether discounts are being used properly and whether the same drug is generating both a 340B discount and a Medicaid rebate.
The Shadow of the 340B Rebate Model
Although the December 2 to December 8 weekly litigation update focused primarily on contract pharmacy cases, the broader 340B world was also watching the federal 340B Rebate Model Pilot Program. Around the same period, hospital groups challenged the pilot program in federal court. The pilot would have shifted certain 340B transactions from upfront discounts to a post-purchase rebate process, meaning covered entities would pay more upfront and later seek rebates.
Hospitals argued that this would create enormous administrative burdens and cash-flow strain. Manufacturers and supporters of rebate models argued that rebates could improve transparency and help prevent duplicate discounts. The rebate model controversy is connected to contract pharmacy litigation because both fights revolve around the same pressure points: who controls the data, who carries the financial burden, and how much discretion manufacturers have in fulfilling 340B obligations.
For safety-net providers, upfront discounts are not merely an accounting preference. They can affect whether money is available now for oncology drugs, HIV medications, diabetes treatments, charity care, transportation programs, and community outreach. A rebate may arrive later, but a patient may need medicine today. Healthcare finance is not a sitcom where cash-flow problems solve themselves before the credits roll.
What Manufacturers Are Arguing
Manufacturer arguments in these cases generally follow several themes. First, manufacturers contend that state contract pharmacy laws are preempted by federal law because they impose additional 340B obligations beyond what Congress enacted. Second, they argue that the federal statute requires them to offer discounted drugs to covered entities, not to an unlimited network of contract pharmacies. Third, they emphasize program integrity concerns, especially duplicate discounts, diversion, and the difficulty of auditing opaque replenishment models.
Manufacturers also object to laws that limit their ability to request claims data. From their perspective, claims data is the flashlight in the dark hallway. Without it, they argue, they cannot determine whether a 340B transaction is legitimate. Hospitals and covered entities respond that broad manufacturer data demands can be burdensome, intrusive, and sometimes inconsistent with the way the 340B program has historically operated.
What States, Hospitals, and Health Centers Are Arguing
States defending contract pharmacy laws generally argue that they are regulating conduct within their traditional police powers, including pharmacy access, healthcare delivery, and unfair or discriminatory trade practices. Hospitals and health centers argue that manufacturers’ restrictions threaten patient access, especially when covered entities lack in-house pharmacies or serve geographically dispersed communities.
Covered entities also argue that 340B savings support services that reimbursement alone does not cover. These may include medication management, uncompensated care, specialty clinics, rural access points, behavioral health support, and outreach programs. When contract pharmacy access shrinks, the concern is not only that an accounting spreadsheet changes. The concern is that a patient who once had a convenient pharmacy option now has to travel farther, wait longer, or abandon treatment altogether.
Key Takeaways From December 2 to December 8, 2025
1. Contract pharmacy remains the main courtroom battlefield
Every major item in the weekly update involved contract pharmacy arrangements. This confirms that contract pharmacy access remains the most active and consequential area of 340B litigation.
2. State laws are spreading, and lawsuits are following
South Dakota, Oklahoma, and New Mexico were all part of the same national pattern: states enact 340B protection laws, then manufacturers or trade associations challenge them.
3. Preliminary injunctions are doing heavy lifting
Because these cases can take months or years, preliminary injunction rulings often determine the real-world rules while litigation continues. A temporary ruling can have very permanent-feeling consequences.
4. Discovery fights are strategic, not procedural fluff
The Oklahoma protective order and discovery stay activity shows that parties are carefully managing how much evidence must be exchanged before courts resolve threshold legal issues.
5. The rebate model adds pressure to an already heated landscape
The 340B rebate model controversy overlaps with contract pharmacy fights because both raise questions about data, payment timing, manufacturer discretion, and covered entity reliance on the traditional discount structure.
Practical Experience: What This Week Felt Like for 340B Stakeholders
For compliance teams, the week of December 2 to December 8, 2025, felt less like a single legal update and more like watching several browser tabs freeze at once. A covered entity operating in multiple states could not simply ask, “What is the rule?” The better question was, “Which state, which court, which defendant, which injunction, and as of what hour?” That is not a joke; it is the daily reality of 340B operations in a fragmented litigation environment.
For hospital leaders, the experience was especially frustrating because the litigation did not live in a legal vacuum. Pharmacy directors still had to make sure patients received medications. Finance teams still had to forecast drug acquisition costs. Revenue cycle teams still had to track reimbursements. Compliance officers still had to document policies, maintain audit readiness, and explain to executives why a law passed in one state might be partially blocked while a similar law elsewhere remained enforceable. If 340B compliance had a soundtrack that week, it was probably a printer jamming during a thunderstorm.
For rural providers and community health centers, the stakes felt more personal. Contract pharmacy relationships can be the difference between a patient picking up medication near home and driving an unreasonable distance for care. In communities where transportation is limited, pharmacies are not just retail locations; they are access points. When manufacturers restrict contract pharmacy shipments, providers worry that patients with chronic conditions may miss refills, delay care, or disengage from treatment plans.
For manufacturers, the experience was different but no less intense. They faced a growing list of state laws that, in their view, created inconsistent obligations and undermined federal program integrity safeguards. A manufacturer operating nationally had to evaluate different state statutes, different enforcement risks, different court orders, and different data requirements. One state might allow enforcement, another might be blocked, and a third might be newly sued. That is not a compliance map; that is a legal escape room with prescription drugs.
Attorneys on both sides likely treated this week as a record-building moment. Preliminary injunction briefing is not just about winning a quick ruling. It is about framing the case: irreparable harm, likelihood of success, public interest, balance of equities, and statutory purpose. Every filing becomes part of the story a court may later tell in an order. In 340B cases, that story often turns on whether the court sees state laws as patient-access protections or as unauthorized expansions of a federal discount program.
Operationally, the best lesson from this week is that 340B stakeholders need a living litigation tracker, not a dusty memo. Covered entities should monitor state-specific developments, review contract pharmacy agreements, maintain documentation supporting patient access, and prepare contingency plans for sudden shifts in enforcement. Manufacturers should document the rationale for restrictions, data requests, and state-specific compliance positions. State officials should draft laws with existing court decisions in mind, because small wording differences can decide whether a statute survives an injunction.
The human lesson is simpler: 340B litigation is not only about statutes, filings, and acronyms. It is about how drug pricing rules translate into patient access, hospital margins, pharmacy workflows, and community care. The December 2 to December 8 update showed that the program’s future will be shaped not by one dramatic ruling, but by dozens of incremental fights. Each case adds a brick to the wall. Whether that wall becomes a stable framework or a maze depends on what courts, agencies, lawmakers, providers, and manufacturers do next.
Conclusion
The 340B litigation update for December 2 to December 8, 2025, shows a program under intense legal pressure from multiple directions. South Dakota defended its contract pharmacy law against a preliminary injunction request. Oklahoma continued to battle over enforcement, discovery, and the scope of its 340B Nondiscrimination Act. New Mexico became the latest state drawn into the litigation wave. Meanwhile, the federal rebate model controversy loomed in the background, raising broader questions about whether 340B discounts should remain upfront or shift toward post-sale rebates.
For healthcare providers, manufacturers, pharmacies, policymakers, and patients, the takeaway is clear: 340B litigation is now a national chessboard. Every state law, every injunction, every discovery order, and every new complaint can change the strategic position. The smartest stakeholders will not wait for a final Supreme Court answer before preparing. They will track the cases, document their operations, and plan for a future in which 340B compliance remains both essential and unpredictable.