.png)
Washington's new 340B law has been sued three times over in six months, and headlines have followed each filing. That noise can make it easy to miss the part that actually requires action from a covered entity right now: a new annual reporting obligation to the state, backed by real enforcement authority, that is running whether or not the litigation ever reaches a final answer.
The law is called E2SSB 5981. It took effect June 10, 2026. If you're a hospital or FQHC operating a 340B program in Washington, this is not a wait-and-see item.
SB 5981 does two distinct things, and covered entities need to treat them separately.
First, it protects contract pharmacy access. Manufacturers, distributors, and third-party logistics providers may not deny, restrict, or condition the delivery of 340B drugs to a covered entity or its contract pharmacies, unless federal law specifically allows the restriction. It also bars manufacturers from requiring covered entities to submit claims, utilization, or purchasing data as a condition of receiving 340B pricing, unless federal law requires that data sharing.
Second, and separately, it creates a new state reporting requirement that applies directly to covered entities, not manufacturers. This is the part that needs a project plan, not just awareness.
The reporting requirement applies to covered entities that are hospitals or federally qualified health centers under the federal 340B statute. It does not extend to every covered entity type. If that describes your organization, you must annually report to Washington's Health Care Authority (HCA):
That is not a summary memo. It is granular, multi-category financial and utilization data that has to come out of purchasing records, dispensing data, and internal accounting, most of which is not sitting in one place inside a typical program today.
The state backed this with real enforcement: the HCA can issue a civil fine against a covered entity or manufacturer that fails to provide the required information by the required date, though a covered entity must first be given the chance to correct the problem before a fine is imposed. Separately, the law gives covered entities their own civil enforcement right against manufacturers, with court-ordered penalties up to $5,000 per day per violation, and the Attorney General can enforce the law under the state's consumer protection act.
Novartis, AbbVie, and the Pharmaceutical Research and Manufacturers of America (PhRMA) sued to block the law before it took effect. On June 9, 2026, a federal district court denied their request, finding that federal law is silent on how 340B drugs are distributed and delivered, which leaves room for state regulation in that area. All three plaintiffs have since appealed. AstraZeneca was not part of the original request to block the law.
It is worth being precise about what that litigation covers and what it does not. The lawsuits challenge the contract pharmacy access and manufacturer data-restriction provisions. They are not challenging the covered entity reporting requirement, and even if they were, an appeal in progress does not suspend a law that is currently in effect. Entities that wait to see how the appeal resolves before building out reporting infrastructure risk not having that data ready when their first report comes due.
Even with a few specifics still to confirm directly with the state, the obligation itself is not in question. Start here:
Confirm whether your entity type is covered. The reporting mandate applies to hospitals and FQHCs specifically. If you operate under a different 340B entity type, confirm directly with the HCA whether the requirement reaches you before you build a reporting process you may not need, or before you assume you're exempt when you aren't.
Identify where each required data point currently lives. Acquisition cost and dispensing data usually sit in your 340B software or TPA platform. Payments to contract pharmacies and third parties often live in accounts payable, not your compliance system. Map each required category to its actual source before you assume you can pull one report and be done.
Confirm your savings-use tracking can produce the detail the state wants. Many programs track total 340B savings but not a breakdown of how those savings were applied. That breakdown is now a state reporting line, not just a board-level talking point.
Get the exact filing deadline and submission mechanics directly from the HCA. Public secondary sources give conflicting or incomplete information on the precise due date and format. Don't build your internal timeline around an assumed date. Confirm it with the agency.
Keep the reporting workstream separate from your litigation-watching. Assign someone to track the appeal for awareness. Assign someone else, on a fixed timeline, to own the report. They should not be the same task with the same urgency level.
We help covered entities confirm exactly what a new state law requires of their specific entity type, map each required data category to its actual source system, and build the internal process to pull and verify that data on a repeatable schedule. Our job is the infrastructure and the timeline. The entity's job is making the underlying program decisions the report reflects, like how savings are allocated and which populations are served.
No. It applies specifically to covered entities that are hospitals or federally qualified health centers under the federal 340B statute. Other entity types should confirm directly with the HCA whether any reporting obligation applies to them.
That would affect the contract pharmacy access and data-restriction provisions. It would not retroactively remove a reporting obligation that was in effect at the time you were required to report.
We have not been able to confirm an exact filing date from primary sources. Confirm the deadline and the applicable reporting period directly with the Health Care Authority before building your data pull.
That has not been confirmed through primary sources at the time of writing. Check directly with the Health Care Authority for current submission mechanics.
No. Given the number of data categories and the likelihood that the information is scattered across multiple systems, mapping your data sources is worth starting now. Confirming the exact deadline is a parallel task, not a prerequisite for starting.
