Episode Summary
This episode is a practical, first-person account of what it actually takes for a brand-new covered entity to enroll in 340B, survive go-live, and build a compliance foundation from scratch. Jordana speaks candidly about the ambiguity in HRSA guidance, the vendor decisions that make or break a rollout, and why a rebate-delay policy could have crippled a clinic that survives on a paper-thin margin.
Key Themes & Main Arguments
1. 340B Eligibility Has No Rulebook: Jordana was introduced to 340B through a Ryan White Part C Capacity Building Grant tied to her clinic's HIV-exposure and substance-use population. When she tried to get a clear definition of patient eligibility from HRSA, the state, and the Ryan White program, "nobody would" give her one. Her workaround: screen every patient for STDs, which creates the Ryan White eligibility paper trail an auditor can actually follow.
2. Hire the Consultant Before You Need One: The single decision Jordana credits most is hiring a 340B compliance consultant (340bauditors.com) before go-live, not after a problem surfaces. She recommends every new covered entity talk to other 340B entities, get referrals, and bring in a consultant or mentor who has already been through an audit and knows what triggers one.
3.Vendor Selection Is a Communication Test, Not a Feature Comparison: Before signing with a TPA, Jordana ran informal response-time tests: how fast they answered an email, whether they called back, whether someone gave her a direct cell number. For a small nonprofit with only a one-year 340B contract, a slow vendor isn't an inconvenience, it's an existential rollout risk.
4.The Covered Entity Owns Every Mistake, Even the Vendor's: Jordana is explicit that if a TPA, wholesaler, or pharmacy makes an eligibility or carve-in error, the covered entity is still the one on the hook in an audit. That reality forced her, as a non-pharmacist, to keep asking questions until she genuinely understood what her vendors were doing.
5.AI Is Middle-of-the-Road, and Over-Reliance Is a Compliance Risk: Jordana uses a small EMR (Clinic Tracker) without leaning on built-in AI. Her verdict on AI in 340B operations: it can help pull data together, but it "is only as good as the data that's being inputted," and over-reliance on an AI-driven TPA or pharmacy system doesn't shift liability away from the covered entity.
6.The Rebate Pilot Program Would Have Buried Small Entities: Jordana calls the now-halted rebate pilot a "delay tactic" that would have forced her nonprofit to front drug costs and wait months for reimbursement on a paper-thin margin. She also corrects a common misconception: 340B was never designed to lower drug prices for the patient directly, it exists to keep safety-net programs like hers operating.
7.Go-Live Takes Longer Than Anyone Promises: In the rapid-fire segment, Jordana confirms she was told go-live would take three months. It didn't. Her broader advice to any organization just starting out: find a mentor first, because reading the raw 340B requirements cold "I wouldn't have touched it with a 10-foot pole."
Show Notes
- The true definition of 340B patient eligibility, and why HRSA never actually hands you one.
- Why most new covered entities falsely assume the OPAIS registration process is the hard part.
- The critical difference between deploying a 340B program and building one that survives its first audit.
- How a Ryan White Part C grant became the doorway into 340B for a mobile addiction treatment clinic.
- Why hiring a compliance consultant before go-live was the single highest-leverage decision Jordana made.
- The real test for choosing a TPA or wholesaler, and it has nothing to do with their pitch deck.
- Why the covered entity is legally on the hook for every mistake its vendors make, no exceptions.
- The honest verdict on AI in 340B operations, and why over-reliance on it is still a compliance risk.
- Why the now-halted rebate pilot program was a delay tactic that could have buried a nonprofit like hers.
- The common misconception that 340B is supposed to lower drug prices directly for the patient.
- A founder built a mobile clinic in an RV after losing a 23-year-old patient who could not reach treatment.
- An eligibility gap forced her clinic to build its own paper trail by screening every patient for STDs.
- A vendor selection process where response time to an email mattered more than any sales pitch.
- A go-live timeline that was promised at three months and did not happen anywhere close to three months.
- A rebate policy that would have forced a paper-thin-margin nonprofit to front drug costs for months.
- A closing warning that reading the raw 340B requirements alone would scare any new entity away for good.