.png)
In 2025, Tennessee enacted new 340B protections designed to prevent pharmaceutical manufacturers from restricting access to 340B pricing when drugs are dispensed through contract pharmacies. The law took effect July 1, 2025, and it is already facing legal challenges from drug manufacturers.
For covered entities operating in Tennessee, this legislation could significantly impact contract pharmacy strategy, manufacturer restrictions, and compliance planning.
Here’s what’s happening, and what it means.
Tennessee passed SB 1414 / HB 1242 in 2025. The law is designed to protect 340B-covered entities from manufacturer-imposed restrictions that limit access to 340B pricing through contract pharmacies.
In simple terms, the law:
The intent is to preserve access to 340B discounts for hospitals, FQHCs, and other covered entities that rely on contract pharmacy arrangements to serve patients.
One important nuance sets Tennessee apart from several other states that have passed similar 340B contract pharmacy protection laws.
Tennessee’s statute prohibits manufacturers from imposing new contract pharmacy restrictions after the law’s effective date of July 1, 2025. However, it does not require manufacturers to reverse restrictions that were already in place prior to that date.
In practical terms:
• Restrictions implemented after July 1, 2025 are prohibited
• Restrictions that existed before July 1, 2025 may remain in place
This distinction matters.
Some states have adopted broader language that challenges both new and existing restrictions. Tennessee’s more limited framework has led certain manufacturers to respond differently than they have in other jurisdictions.
For covered entities, this means the impact of the law may vary depending on when manufacturer policies were first implemented and how those policies are structured today.
The presence of state-level protections does not automatically reset contract pharmacy access. Entities should review manufacturer timelines, designation history, and current policy posture to understand how the law applies to their specific program.
Over the past several years, many manufacturers began restricting 340B pricing for drugs dispensed through contract pharmacies. Some required data submission through platforms like ESP. Others limited the number of pharmacies allowed. Some imposed additional administrative conditions.
States like Tennessee responded by passing legislation to ensure manufacturers could not block access to 340B pricing through contract pharmacy models.
Tennessee’s law reflects a broader national trend: states are stepping in where federal guidance has remained unsettled.
Shortly after the law was enacted, at least one major pharmaceutical manufacturer filed a lawsuit challenging the statute. Manufacturers argue that state laws regulating 340B contract pharmacy access may conflict with federal authority.
However, a federal court declined to block the Tennessee law while litigation proceeds. That means the law remains in effect for now.
Litigation is ongoing, and final outcomes could influence how similar state laws are interpreted nationwide.
For covered entities in Tennessee, this law potentially:
However, it does not eliminate operational complexity.
Manufacturer policies are still evolving. ESP participation, designation management, and claim submission processes still require careful oversight. State protection does not replace structured compliance management.
Covered entities should view this law as a layer of support, not a substitute for active 340B program optimization.
Tennessee is not alone. Multiple states have passed similar 340B contract pharmacy protection laws in response to manufacturer restrictions.
At the same time:
The 340B landscape is increasingly shaped by a combination of state law, federal litigation, and manufacturer policy.
If you operate a 340B program in Tennessee, now is a good time to:
State-level protection is meaningful, but structure and oversight still drive performance.
Frequently Asked Questions About Tennessee 340B Legislation
The law took effect July 1, 2025.
Not necessarily. It prohibits certain discriminatory practices related to contract pharmacy access, but manufacturers continue to evolve policies and legal challenges remain active.
Yes. Litigation is ongoing, and courts will ultimately determine the long-term scope and enforceability.
No. ESP participation and manufacturer data submission requirements may still apply depending on manufacturer policy.
Tennessee’s 340B legislation signals that state governments are increasingly willing to intervene in the contract pharmacy debate.
For covered entities, this reinforces an important truth:
340B is no longer just a federal compliance program, it is now shaped by state legislation, manufacturer policies, litigation, and evolving rebate models.
Navigating that complexity requires more than passive oversight.
It requires active management.
