Episode Summary
Thomasyna Sweed started in hospital pharmacy as a high school intern, moved through retail into PBM management and contract negotiations, entered 340B in 2012 with a consulting firm, spent time as an audit analyst on the TPA side, and is now Program Manager at LifeSpring Health Systems, an FQHC based in Jeffersonville, Indiana. That combination matters here, because she has sat on both sides of the vendor relationship she now has to police. LifeSpring has no entity-owned pharmacy, which makes contract pharmacy, in her words, "the lifeblood of our 340B program" and makes every manufacturer restriction an access problem rather than a paperwork problem. She runs it as a team of one, across four TPAs. Her sharpest line in the episode is her answer on whether a covered entity can lean on its vendor to submit claims data: because HRSA holds the covered entity 100 percent responsible for compliance, "I say trust no one." Delegate, yes. Have faith in your vendor, absolutely. Blindly trust, absolutely not.
The conversation is about what manufacturer restrictions actually cost an organization operationally, rather than what they mean legally. Her clearest framing of the scale problem: one or two restricted manufacturers is manageable, but as that list grows to ten, then twenty, then fifty, each with its own platform and its own submission rules, "I'm still just the same one person that I was six years ago when this all started." She walks through how she decides which pharmacies to designate and which to submit claims for, what data she trends weekly and monthly, why the highest-volume pharmacy is often not the highest-savings pharmacy, and where AI could genuinely reduce the load pulling four TPAs into one report instead of merging four while being direct that AI is "very much in the infancy stage" and needs human oversight before a compliance team can rely on it.
Show Notes
- Contract Pharmacy Under Pressure: Manufacturer Restrictions, Claims Data, and Patient Access in 340B
- Thomasyna Sweed, Program Manager, LifeSpring Health Systems
- Why contract pharmacy becomes the entire 340B program when a covered entity has no in-house pharmacy.
- The true gap between how simple claims submission looks on paper and what execution actually demands.
- Why most operators falsely assume their highest-volume contract pharmacy is also their highest-savings pharmacy.
- The critical difference between delegating work to a TPA and transferring responsibility for compliance.
- What the AbbVie example reveals about where manufacturer restrictions are heading next.
- Why restriction planning has to run manufacturer by manufacturer instead of across the program as a whole.
- How state-level Medicaid billing rules, PBM provisions, and pharmacy distance requirements quietly reshape a contract pharmacy network.
- Where AI could genuinely reduce the reporting burden, and the trust problem that has to be solved first.
- HRSA holds the covered entity 100 percent responsible for program compliance, which is why Thomasyna's answer on vendor reliance is trust no one.
- Delegate the work, have faith in your vendor, but never blindly trust the output.
- One or two restricted manufacturers is manageable, but the list grows while headcount does not.
- You should be able to name your highest-volume contract pharmacy from memory on any given day.
- You should separately know which pharmacy produces the largest share of your 340B savings, because it is often a different pharmacy.
- Know your top 15 to 30 drugs and the manufacturers behind them, so you can see a restriction coming before it lands.
- Know which TPA is tied to which contract pharmacies, including exclusive and gateway relationships.
- Trend pharmacy performance week over week and month over month, and look for variances rather than absolute numbers.
- Ask your TPA account manager for manufacturer-specific reporting instead of merging it yourself.
- Read every new policy fully before changing anything, then determine which parts actually apply to your covered entity type.
- Build the new requirement into the system you already have rather than standing up a parallel process.
- Solve the largest manufacturer first, then apply that same framework to the rest.
- Make sure all 12 HRSA-listed items are in your Pharmacy Services Agreement.
- Ask your TPA to walk you through how a claim is qualified, from prescription to qualification.
- Compliance and patient access do not have to compete with each other.
- Before adding a process, ask whether it genuinely improves compliance or accountability, and whether it still lets the organization serve patients.
- Thomasyna's six rules for 340B leaders: understand the policy, understand your data, define ownership, communicate early, monitor implementation, and keep the focus on patient access.
- Her advice on responding to restrictions: try not to be angry, because this is business and burnout is real.