Episode Summary
Vinson Tran's path into 340B started as a pharmacy intern at a community hospital, where he later watched a 340B program get misused and eventually shut down after roughly a year or two of drift. That experience shaped how he now runs programs: don't trust that a system is working just because it's set up build a workflow that actively catches when it isn't. Today he holds a core TPA role at a hospital and runs Pharmacy Operation Solutions, an LLC helping covered entities DSH hospitals and community health centers alike manage and defend their 340B programs. He's been through two HRSA audits, four years apart, with the same auditor both times.
On a recent episode of 340B Pulse, Vinson broke down what actually prevents duplicate discounts (a two-data-set minimum: pharmacy data plus 340B data, always), why mixed-use hospital operations are harder to police than retail pharmacy because charge files are the one common denominator across every downstream system, and why he treats his TPA's output as something to verify, not trust blindly. He also walked through a concrete reimbursement example a $1,300 wholesale drug reimbursed at $11 under 340B to make the case that programs need to watch revenue, not just compliance. On the newly reproposed HRSA rebate model, he's genuinely split: it could give manufacturers better data to distinguish 340B from MFP claims, but the cash-flow burden of paying full price upfront and waiting on a rebate could hit thin-staffed covered entities hard.
Show Notes
- The true definition of duplicate discount prevention, and why it requires a minimum of two data sets working together at all times.
- Why most operators falsely assume their TPA or 340B software is already preventing duplicate discounts on its own.
- The critical difference between preventing duplicate discounts in a retail pharmacy setting versus a hospital mixed-use environment.
- Why the charge file sent from a hospital EMR is the single common denominator every downstream 340B system depends on.
- How Vinson builds a temporary unique identifier to isolate duplicate hospital claims when transaction IDs don't match across systems.
- The real math behind a 340B reimbursement: a drug that costs 1,300 dollars at wholesale reimbursed at roughly 11 dollars.
- Why most flawed accumulations trace back to bad data sent to the splitter, not the splitter itself.
- Vinson's honest, 50/50 read on the reproposed HRSA rebate model and what it could mean for small covered entities.
- Key Insights and Takeaways
- Never trust that a system is working correctly just because it is set up.
- Trust the workflow you build to catch inconsistencies instead.
- At minimum, keep two data sets available at all times: pharmacy data and 340B data.
- California and Illinois are the only two mandatory carve-in states in the country.
- Medicaid Exclusion File accuracy affects both state rebate determinations and HRSA audit readiness.
- A 340B dashboard tracking purchases, revenue, and net profit is close to the bare minimum for real visibility.
- Ask every TPA or software vendor the same core question before adopting a new feature: how does this impact my covered entity.
- HRSA only audits the data a covered entity actually submits, which makes submission-time accuracy the highest-leverage moment in the entire process.
- Strong 340B oversight is a team effort across pharmacy, billing, IT, and finance, not a single department's responsibility.