SB 5981 prohibits drug manufacturers, distributors, and third‑party logistics providers from denying, restricting, or conditioning the acquisition or delivery of drugs sold at 340B prices to covered entities, their contract pharmacies, or authorized locations, except when federal law bars receipt. The bill also bars conditioning access on submission of utilization, purchasing, or other data unless federal law requires those disclosures.
The measure creates an enforcement regime allowing covered entities to sue and the Washington attorney general to bring actions under the state consumer protection act. Courts may enjoin violations and assess civil penalties up to $5,000 per day for each violation, with each package of 340B drugs constituting a separate violation.
The bill aims to preserve access and the financial resources safety‑net providers use to support underserved patients but raises practical questions about evidentiary burden, supply‑chain compliance, and interaction with federal distribution and safety requirements.
At a Glance
What It Does
SB 5981 makes it unlawful for manufacturers, distributors, or third‑party logistics providers to prevent covered entities or their contract pharmacies from acquiring or receiving 340B drugs, or to require data as a precondition to access, unless federal law compels otherwise. It treats each package of 340B drugs subject to a prohibited act as a separate violation and authorizes injunctions and civil penalties.
Who It Affects
The bill directly affects drug manufacturers and their distribution partners (including third‑party logistics providers), covered entities that participate in the federal 340B program (FQHCs, Ryan White clinics, tribal and urban Indian health centers, critical access and other qualifying hospitals), and the pharmacies that contract with those entities to dispense 340B medications.
Why It Matters
By codifying state limits on manufacturer restrictions, the law seeks to protect access to discounted drugs and the financial viability of safety‑net services that rely on 340B savings. For compliance teams and supply‑chain operators it recalibrates the legal risks of restricting shipments, requiring new operational policies, and exposes parties to per‑package penalties and consumer protection enforcement.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill adds a new chapter to Title 69 RCW built around two operative prohibitions and a civil enforcement scheme. First, it forbids manufacturers, distributors, and third‑party logistics providers from denying or otherwise restricting a covered entity’s ability to buy or receive drugs at 340B prices.
That ban explicitly covers pharmacies operating under contract with covered entities and any location a covered entity authorizes to receive 340B drugs. The statute carves out only those situations where federal law actually bars receipt of a drug at 340B pricing.
Second, the statute prevents manufacturers and their distribution partners from making access to 340B drugs conditional on submission of claims, utilization, purchasing, or other data, again unless federal law requires such disclosures. Those two prohibitions are written broadly: they reach direct acts and indirect ones, and they name manufacturers’ distributors and third‑party logistics providers to limit attempts to rely on intermediaries to impose restrictions.On enforcement, the bill gives covered entities a private right of action and empowers the state attorney general to sue under the consumer protection act, including parens patriae authority.
Remedies include injunctive relief, reasonable attorneys’ fees and costs, and civil penalties of up to $5,000 per day, with each physical package of 340B drugs subject to a prohibited act counted as a separate violation. The bill also contains a standard severability clause and a command to interpret the statute so it does not conflict with federal law and related regulations.Practically, compliance teams will need to reassess shipment‑denial policies, data‑request practices, and contractual terms with distributors and 3PLs.
Covered entities and contract pharmacies will likely demand clearer documentation channels to prove a denied or restricted delivery when enforcing rights in court. Manufacturers and logistics providers will have to weigh the statute’s penalties and state enforcement posture when designing oversight and fraud‑prevention measures, particularly where those measures rely on data exchange or controlled distribution programs under federal law.
The Five Things You Need to Know
The bill prohibits manufacturers, distributors, and third‑party logistics providers from denying or restricting acquisition or delivery of 340B drugs to covered entities, contract pharmacies, or authorized locations unless federal law prohibits receipt.
The statute bars conditioning access to 340B drugs on submission of claims, utilization, purchasing, or other data unless federal law requires that data sharing.
Covered entities may sue for violations; courts can issue injunctions, award attorneys' fees and costs, and impose civil penalties up to $5,000 per day for each violation.
The attorney general can enforce the law under the state consumer protection act (chapter 19.86 RCW), including bringing parens patriae actions on behalf of state residents.
Each physical package of 340B drugs subject to a prohibited act counts as a separate violation, and the law names distributors and 3PLs alongside manufacturers as potential defendants.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Legislative findings explaining purpose
This section sets out the legislature’s rationale: 340B savings sustain services for low‑income and uninsured patients and contract pharmacies expand access. The findings anchor the statute’s intent to protect both patient access and the financial resources that safety‑net providers reinvest, which matters for statutory interpretation and for courts evaluating the law’s purpose versus federal preemption arguments.
Definitions that limit scope and reference federal law
Section 2 defines key terms — '340B drug', 'covered entity', 'manufacturer', 'package', 'pharmacy', and 'third‑party logistics provider' — generally by cross‑referencing federal statutes and a Washington pharmacy definition. Those cross‑references fix the bill to the federal 340B eligibility framework as of the bill’s effective date and narrow ambiguity about who counts as a covered entity or 3PL.
Substantive prohibitions on denying delivery and conditioning access on data
This is the operative core: subsection (1) forbids denial, restriction, or prohibition of acquisition or delivery of 340B drugs to covered entities, their contract pharmacies, or authorized locations, unless federal law prohibits receipt. Subsection (2) forbids requiring submission of claims, utilization, purchasing, or other data as a condition of access, unless federal law mandates it. The language reaches direct and indirect action and explicitly names distributors and 3PLs to prevent circumvention through intermediaries.
Private and public enforcement; civil penalties and consumer protection framing
This section gives covered entities a private cause of action and allows the attorney general to sue in the state's name or as parens patriae. Courts may enjoin violations and impose civil penalties up to $5,000 per day; critically, each package of 340B drugs subject to a prohibited act counts as a separate violation, which multiplies potential exposure. By declaring violations inconsistent with business development and labeling them unfair or deceptive for CPA purposes, the bill imports the CPA’s remedies and standing rules into enforcement.
Severability
Standard severability language preserves the remainder of the statute if any provision is struck down. Given likely constitutional and preemption challenges in litigation, this clause aims to ensure other prohibitions remain enforceable even if courts invalidate a portion.
Placement in state code
Declares that Sections 1–4 constitute a new chapter in Title 69 RCW. The placement groups 340B protections with broader public health and safety chapters, signaling legislative intent that the provisions address health care access and safety‑net stability.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Federally qualified health centers and Ryan White (HIV) clinics: the bill protects their ability to obtain and dispense discounted outpatient drugs through contract pharmacies, preserving a revenue stream they use to fund patient services and support programs.
- Contract pharmacies (community and independent pharmacies that serve 340B patients): by barring manufacturer restrictions, the law aims to keep these pharmacies available as dispensing points for vulnerable patients who rely on local access.
- Tribal and urban Indian health centers and critical access hospitals: entities with thin margins that use 340B savings for care coordination and community health programs regain a statutory backstop against shipment or supply restrictions.
- Low‑income and uninsured patients served by 340B entities: the practical effect is intended to reduce interruptions in access to prescribed medications and preserve ancillary services funded by 340B savings.
- Washington state public health and safety‑net systems: preserving 340B flows helps maintain programs (transportation, case management, vaccines) that reduce downstream costs and access gaps.
Who Bears the Cost
- Pharmaceutical manufacturers: the bill curtails contractual and operational levers manufacturers use to control distribution and to prevent diversion, exposing them to larger litigation and penalty risk and potentially increasing compliance costs.
- Distributors and third‑party logistics providers (3PLs): named directly in the prohibitions, distributors and 3PLs must revisit procedures that deny or limit deliveries and may face litigation exposure and changed contractual obligations with manufacturers.
- Contract pharmacies and covered entities (administrative burdens): while beneficiaries, these stakeholders will likely incur administrative work to document denials, track 'package'‑level events, and bring enforcement actions when necessary.
- State resources and courts: expanded AG enforcement under the consumer protection act and increased private litigation may increase demands on public enforcement resources and court dockets, though prevailing plaintiffs can recover fees.
Key Issues
The Core Tension
The central dilemma is straightforward: the law prioritizes uninterrupted patient access and the financial viability of safety‑net providers by stripping manufacturers and logistics partners of certain distribution and data‑conditioning tools, but in doing so it limits the manufacturers’ ability to manage supply integrity, comply with federal safety programs, and use distribution controls to prevent diversion—creating a trade‑off between access protection and supply‑chain and regulatory safeguards.
The bill’s broad prohibitions and per‑package penalty scheme create several implementation and legal frictions. First, proving a 'denial' or 'restriction' will often hinge on transactional records and manufacturer communications; covered entities must capture contemporaneous delivery notices, refusals, or contractual language to win a claim.
The statutory rule that each package counts as a separate violation amplifies damages exposure and could produce outsized penalties for shipment disputes that may otherwise be resolved administratively.
Second, the prohibition on conditioning access to 340B drugs on data submission collides with legitimate manufacturer and regulatory interests—fraud prevention, risk‑sharing arrangements, and safety monitoring sometimes require data exchange. The bill tries to preserve federal exceptions ('unless federal law requires'), but it does not define how to reconcile conflicting obligations when federal programs or manufacturer safety programs rely on data that manufacturers argue they need to lawfully distribute certain products.
That ambiguity invites litigation and operational pressure: manufacturers or distributors may elect to halt shipments or redesign distribution strategies rather than risk state penalties.
Finally, federal preemption and related federal program rules will be central in litigation. The statute ties many definitions to the federal 340B framework as of the effective date, but substantive conflicts could arise with evolving federal interpretations, REMS controls, or Medicaid rebate interactions.
While the bill includes a non‑conflict clause, courts will decide the boundary between state authority to regulate commerce within the state and federal supremacy over drug pricing and distribution, which creates uncertainty for all parties during enforcement and compliance planning.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.