340B: This Week In 08/12 – 08/18 for Contract Pharmacy

If the 340B contract pharmacy saga were a TV show, this week (August 12–18, 2025) would be the episode where everyone
says “We’ll see you in court” and then… actually means it.

In seven days, we saw fresh complaints, fresh preliminary-injunction moves, and fresh reminders that “contract pharmacy”
is no longer just an operational choiceit’s a legal battleground. Below is what happened, what it likely means for
covered entities and contract pharmacies, and what to watch nextwithout the filler, the fearmongering, or the
“synergy-driven stakeholder optimization” nonsense.

Quick refresher: what “contract pharmacy” means in 340B

The 340B Drug Pricing Program requires participating drug manufacturers to sell certain outpatient drugs at discounted
prices to eligible “covered entities” (think safety-net hospitals, community health centers, and other qualifying
providers). Many covered entities don’t dispense every prescription through an in-house pharmacy. So they contract
with outside pharmaciesretail, independent, or chainto dispense 340B drugs to eligible patients. Those partner
pharmacies are called contract pharmacies.

Modern contract-pharmacy use accelerated after federal guidance expanded the ability of covered entities to use more
than one contract pharmacy. That expansion helped covered entities extend pharmacy accessespecially for rural
communities and for patients who live nowhere near a hospital-owned outpatient pharmacy.

The operational core of contract pharmacy is tracking: ensuring the right patients receive the right drugs, purchased
at the right price, with safeguards against prohibited “diversion” (dispensing to non-eligible patients) and
“duplicate discounts” (stacking 340B discounts and Medicaid rebates on the same drug).

Why contract pharmacy is in court so often lately

The current wave of litigation is driven by a simple collision:
covered entities want broad pharmacy access, and many manufacturers want tighter control and more data
around contract-pharmacy dispensing.

Over the last few years, a number of manufacturers adopted policies that limit 340B pricing when drugs are dispensed
through contract pharmaciesoften conditioning discounts on data submissions, restricting which pharmacies qualify, or
limiting the number of contract pharmacies a covered entity can use.

In response, states began passing “contract pharmacy protection” laws designed to prevent manufacturers from denying
340B pricing based solely on the use of contract pharmacies. Those state laws are now being challenged in federal
courttypically on arguments like federal preemption, interference with federal enforcement schemes, and constitutional
claims. The result is a fast-growing patchwork of state statutes and lawsuits.

This Week In 08/12 – 08/18: the contract-pharmacy litigation snapshot

The developments below come from docket activity during the week and focus specifically on
contract pharmacy arrangements.

1) Oklahoma: the state fights back against a preliminary-injunction bid

In an Oklahoma case challenging a state law governing contract-pharmacy arrangements, the state filed a response
opposing a manufacturer’s motion for a preliminary injunction. In plain terms: the manufacturers asked the court to
pause enforcement; Oklahoma answered, “No, and here’s why.”

Oklahoma’s dispute fits the broader pattern: state officials argue their law protects access for rural and underserved
patients by preventing manufacturers from blocking 340B distribution through contract pharmacies. Manufacturers argue
the law forces them into discounting and distribution conduct that, in their view, goes beyond federal requirements
and undermines safeguards (especially around data visibility and audit mechanisms).

Why it matters for contract pharmacies: Oklahoma is a bellwether for how courts react when a state law
tries to regulate the “how” of 340B distributionespecially if the law restricts manufacturers’ ability to condition
discounts on data submission or audit-related controls. Even before any final decision, injunction fights can change
day-to-day operations: wholesalers ask questions, pharmacies get new contract addenda, and everyone suddenly rediscovers
the meaning of “urgent.”

2) Colorado: a preliminary-injunction motion hits the docket

In Colorado, the manufacturer-side litigation posture got more aggressive: the plaintiff filed a motion for a
preliminary injunction to block enforcement of Colorado’s contract-pharmacy protections.

Colorado’s law is part of the newer generation of state statutes that (generally) aim to stop manufacturers (and
sometimes their agents) from denying or interfering with a covered entity’s ability to acquire or receive 340B drugs
for dispensing through contract pharmacies. These statutes often also address whether manufacturers can require claims
data as a condition of honoring 340B pricing when a contract pharmacy is involved.

Why it matters for contract pharmacies: A preliminary injunction request is a “fast lane” attempt to
stop a law before it bites. If a court grants a preliminary injunction, contract pharmacies may see a return to more
restrictive manufacturer policiesat least temporarilywhile the case proceeds. If denied, states gain momentum and
covered entities gain near-term operational stability.

3) Maine: a preliminary-injunction motion challenges a new 340B contract pharmacy statute

In Maine, the plaintiff filed a motion for preliminary injunction in a case challenging a state law designed to
protect contract-pharmacy arrangements. Maine’s statute was framed around rural and underserved access and included
language aimed at prohibiting manufacturers from denying, restricting, or otherwise interfering with 340B drugs being
delivered to contract pharmacies on a covered entity’s behalf.

Maine’s model is notable because it also targets a pressure point that repeatedly shows up in litigation:
claims and utilization data. Many state laws in this area attempt to limit whether a manufacturer can
demand claims-level data as a condition of allowing 340B acquisition or delivery when contract pharmacies are involved.

Why it matters for contract pharmacies: Maine’s approach tees up the question courts keep revisiting:
can a state law tell manufacturers they must honor 340B pricing through contract pharmacies while also restricting
what data those manufacturers can require to monitor compliance? This is the “access vs. oversight” tension in its
purest form.

4) Maine: a new manufacturer complaint is filed (fresh suit, fresh paperwork, fresh headaches)

During the week, a drug manufacturer filed a complaint for declaratory and injunctive relief in Maine challenging the
state’s contract-pharmacy protections. New complaints matter because they can signal:
(1) a manufacturer deciding it can’t live with a state’s enforcement timeline, (2) a strategic choice of venue and
claims, or (3) a desire to accelerate toward an injunction before operations fully adjust.

What this suggests operationally: When new suits drop, contract pharmacies often see a short-term
spike in “policy churn”requests for attestations, new terms in dispensing agreements, and urgent questions like
“Are we still eligible to dispense this NDC under 340B next week?” (Translation: nobody sleeps, and everyone’s inbox
becomes a crime scene.)

5) South Dakota: AstraZeneca files a new complaint challenging a contract-pharmacy law

In South Dakota, AstraZeneca filed a complaint challenging the state’s contract-pharmacy-related law. This is a major
tell: manufacturers weren’t just litigating legacy laws anymorethey were actively expanding the map of challenges to
newly enacted state protections.

South Dakota’s statute (often discussed in the context of “SB 154”) has been part of the broader state-law trend:
restricting manufacturer interference with contract-pharmacy dispensing and, in many models, limiting the ability to
demand certain claims data as a condition of honoring 340B pricing.

Why it matters for contract pharmacies: When a manufacturer files a new challenge, it may attempt to
preserve (or reinstate) contract-pharmacy limits while the case proceeds. In practical terms, that can affect
pharmacies’ willingness to onboard new covered-entity relationships, pharmacies’ risk tolerance for 340B dispensing,
and covered entities’ decisions about how many pharmacies to contract withand which ones.

Reading between the lines: what everyone is actually fighting about

Access: “Let covered entities use the pharmacies patients actually go to.”

Covered entities and supportive states argue that contract pharmacies are a practical access toolespecially for rural
patients and for communities where the nearest hospital-owned pharmacy may be 45 minutes away (and closes at 5 p.m.).
From this viewpoint, restricting contract pharmacies restricts access, shrinks 340B savings, and threatens services
funded by those savings.

Oversight: “If discounts flow through third parties, we need data to prevent abuse.”

Manufacturers argue that widespread contract-pharmacy use can increase the risk of diversion and duplicate discounts,
and that they need claims-level visibility (or other controls) to confirm that discounted drugs are going only to
eligible patients and aren’t triggering duplicate rebate exposure.

This is where things get spicy: some state laws aim to protect contract-pharmacy access while limiting manufacturers’
ability to require claims or utilization data. Manufacturers often argue that data restrictions handcuff legitimate
compliance and audit efforts. States and covered entities often argue that the data demands are being used as
de facto barriers to contract-pharmacy participation.

Federal vs. state power: “Who gets to set the rules of the road?”

Many of these lawsuits boil down to whether states are supplementing the 340B program or stepping into a federally
occupied field. Plaintiffs typically argue that federal law and federal agency administration set the exclusive
framework, and that states can’t impose additional requirements or enforcement schemes on top.

States respond that they are regulating commercial conduct within their bordersespecially unfair or discriminatory
actionswhile staying consistent with the federal program’s goals.

So what should contract pharmacies and covered entities do right now?

You can’t litigate your way out of daily dispensing. But you can reduce risk while the legal weather changes.
Here are practical, non-dramatic steps that help in most environments:

1) Tighten documentation like a future you will be grateful for

If you use split-billing software or a third-party administrator, confirm that your audit trail is easy to export and
interpret. “It’s in the system” is not documentation; it’s a vibe. Ensure your records demonstrate patient
eligibility logic, purchasing records, dispensing records, and replenishment decisions.

2) Re-check diversion and duplicate discount controls

Even when lawsuits are about state statutes, the underlying compliance standards don’t disappear. Covered entities
remain responsible for preventing diversion and duplicate discounts. Contract pharmacies should understand the covered
entity’s policy and their own role in maintaining compliant dispensing and reporting workflows.

3) Expect more “policy updates” from manufacturersand plan for them

Contract pharmacies should anticipate frequent manufacturer policy announcements that change ordering channels,
require attestations, limit contract-pharmacy eligibility, or shift operational requirements. Build a process to track
updates by manufacturer and by drug class (especially for high-cost specialty drugs).

4) Align the covered entity–pharmacy relationship on the “data question”

Some manufacturers request claims data to validate 340B dispensing. Some state laws try to limit those demands.
Regardless of legal outcomes, covered entities and contract pharmacies should agreeup fronton who can share what,
how quickly, and under what safeguards. Misalignment here is how otherwise good relationships turn into “We should hop
on a quick call” calls that last 93 minutes.

5) Don’t ignore the dispute-resolution toolbox

The federal 340B Administrative Dispute Resolution (ADR) process exists to resolve certain disputes between covered
entities and manufacturers. While ADR won’t solve every contract-pharmacy conflict, it’s increasingly relevant in a
world where “enforcement pathways” are part of strategy, not just compliance.

What to watch next

• Preliminary injunction outcomes. Courts’ early decisions often influence how aggressively parties
  litigate and how quickly other states or manufacturers escalate.
• Data and audit arguments. The more a case focuses on claims-data restrictions and audit rights, the
  more it may shape how future state laws are drafted.
• Multi-state ripple effects. Manufacturers often apply national policies; states respond with
  state-specific laws. That push-pull can create operational fragmentation for contract pharmacies that serve multiple
  covered entities across state lines.
• Federal experimentation. Separate from contract-pharmacy access laws, the federal government has
  explored pilot approaches (like rebate-model pilots) that could change pricing mechanics for certain drugsan issue
  that can indirectly affect contract-pharmacy workflows and cash flow.

Experience Notes: from the contract-pharmacy trenches

If you’ve never worked around 340B contract pharmacy operations, it’s easy to assume the drama is purely legal.
But the real “experience” of this space is a mix of careful compliance, constant coordination, and the occasional
moment where someone realizes a spreadsheet can, in fact, be sentient.

Experience #1: The rural access reality check. A small rural hospital signs with two contract
pharmacies because patients don’t live near the hospitalsome are an hour away, and winter roads don’t care about
your pharmacy hours. The hospital views contract pharmacies as a direct access solution. Then a manufacturer policy
update lands, the pharmacy network eligibility changes, and suddenly the hospital is triaging which pharmacy
relationships matter most. The “experience” here isn’t abstract; it’s patients asking why their usual pharmacy
suddenly can’t dispense a medication at the expected price, and staff trying to explain a policy shift without
sounding like they’re narrating a courtroom drama.

Experience #2: The data request dilemma. A contract pharmacy receives a new request for claims-level
data tied to 340B dispensing. The pharmacy operations team thinks, “We can provide it,” because they want to keep
the pipeline smooth. The covered entity compliance team thinks, “Waitwhat does our agreement allow, and what does
state law say?” The legal team thinks, “Can we not do this via email?” The practical lesson: the best 340B contract
pharmacy programs have a pre-decided playbook for data sharingwhat’s allowed, what’s necessary, and how to protect
patient privacy and contractual obligations. When you don’t have a playbook, every request becomes an emergency.

Experience #3: The replenishment choreography. Contract-pharmacy replenishment is a choreography of
purchasing records, dispensing events, eligibility rules, and timing windows. When everything works, it feels almost
invisible. When it doesn’t, it becomes a hunt: “Why did this claim fall out?” “Why did this NDC not match?” “Why did
this dispense land in the wrong bucket?” The funny part is that the error is often tinya mismatched identifier, a
missing prescriber field, a timing mismatch. The not-funny part is that tiny errors can create big compliance
headaches, especially if someone later calls it diversion or duplicate discounting. The “experience” of teams who do
this well is obsessive clarity: who owns which data element, who validates it, and who signs off before replenishment
is finalized.

Experience #4: Relationship management is half the job. Contract pharmacy isn’t just a contract; it’s
a relationship between a covered entity, a pharmacy (or many), wholesalers, and sometimes a third-party administrator.
When litigation heats up, everyone’s risk tolerance changes. A pharmacy might hesitate to onboard a new covered entity
unless roles and indemnification are crystal clear. A covered entity might consolidate pharmacies to reduce complexity.
A wholesaler might tighten documentation requirements. The teams that survive these shifts aren’t the ones with the
fanciest dashboardsthey’re the ones with clear governance, regular communication, and enough humility to say,
“We should fix the process before we add another pharmacy.”

Experience #5: Humor is a compliance tool (kind of). When your week includes court filings, policy
updates, and a three-hour meeting about claim reversals, a little humor keeps teams human. The best leaders in this
space can say, “Yes, this is serious” and “Yes, we can still laugh” in the same sentence. Because if you can’t laugh
at the phrase “utilization data,” it will eventually laugh at you.

Bottom line

August 12–18, 2025 delivered a clear message: contract pharmacy is still the pressure point where 340B access, data,
and enforcement collide. New complaints and injunction moves mean the legal landscape can shift quicklybut the
operational fundamentals stay the same: document cleanly, prevent diversion and duplicate discounts, coordinate data
workflows, and prepare for policy churn.

If you’re running a contract-pharmacy program, your best strategy this week is boring in the best way:
stay compliant, stay organized, and keep a close eye on the states where laws (and lawsuits) are moving fastest.