The Five-Hour Myth: What 340B Rebate Readiness Really Takes | Celeste Fowler

Episode Summary

Celeste Fowler is Executive Director of Pharmacy 340B at Piedmont Healthcare, where she leads the 340B program at the health-system level across multiple hospitals. She backed into the space almost by accident: as a newly installed pharmacy director at a community hospital, her executive told her to "get that 340B going," a term she initially didn't recognize before educating herself through formal 340B training and building the program from scratch as what she calls a "one-woman show." On this episode of 340B Pulse, host Muhammad Atif presses her on what a rebate-based 340B model would actually demand operationally, and Fowler's clearest concrete claim is that the widely repeated "five-hour myth," the idea that rebate readiness costs a covered entity only a few extra hours a month, describes at most the mechanical act of uploading a file. Done correctly, she argues, the real work of gathering fragmented data, validating it, and then "checking the checker" to confirm a rebate paid back is accurate could run closer to five hours a day, not five hours total.

The conversation moves through data integrity and security as the operational blind spot most leaders are missing, the practical mechanics of reconciling scattered pharmacy, revenue-cycle, and EMR data into one submittable file, why standardization has to be the fixed "recipe" underneath every covered entity's unique program, where AI genuinely earns a role in 340B operations versus where clinical judgment cannot be automated away, and the financial exposure created when a covered entity must front the higher WAC price and then wait, unindemnified, for a manufacturer rebate to come back accurate and on time. Fowler closes by describing her role as an "ambassador of 340B," building cross-departmental alignment across pharmacy, finance, compliance, and IT so the program does not live or fail in a silo.

Show Notes

• The true definition of rebate readiness, and why it is closer to five hours a day of disciplined work than five extra hours a month.
• Why most operators falsely assume that adding another vendor or data field automatically increases transparency.
• The critical difference between a covered entity's own secure internal systems and rebate-model vendors who will not offer standard indemnification protections.
• Why most 340B data does not live in one place, and what it actually takes to pull pharmacy, revenue-cycle, and EMR data into a single accurate file.
• The true reason medical claims data behaves differently than retail claims data, with a constant ebb and flow of payer approvals, denials, and reversals.
• Why standardization has to function as the fixed compliance recipe underneath every program, even while each covered entity's version looks different.
• Where AI and automation genuinely earn their place in a 340B program, and where clinical judgment about an individual patient cannot be handed off to a machine.
• The operational meaning of checking the checker, and what it takes to confirm that a rebate a covered entity is owed is the rebate it actually receives.
• Key Insights and Takeaways
• Celeste Fowler backed into 340B almost by accident, after a hospital executive told her to get the program going and she had to learn what it was from scratch.
• She built her first 340B program as what she calls a one-woman show, with a single strong buyer supporting her, before later scaling to a health-system role overseeing multiple hospitals.
• Data integrity and security, not the addition of more data fields, is the operational blind spot most healthcare leaders are missing as rebate models expand.
• Data already submitted to a TPA is used internally for eligibility and qualification, not shared externally, which is why more fields do not automatically create more transparency.
• Covered entities should disclose only the minimum information necessary to meet a stated requirement and stay wary of requests for data that is not truly needed for 340B eligibility.
• Fowler calls her organization's internal information security setup Fort Knox, but flags that current rebate-model vendors have taken a take-it-or-leave-it stance on data protection language.
• The five-hour myth likely describes only the act of uploading a file, not the work of gathering, cleaning, validating, and reconciling the data underneath it.
• Doing rebate readiness the right way is not the same as doing it the fastest way, and organizations that treat it as a light lift are underestimating the effort.
• Reconciling a single claim can mean chasing data across separate pharmacy software, revenue-cycle software, and EMR systems that were never built to speak the same language.
• Small inconsistencies in units of measure, milliliters versus milligrams, packages versus implied quantities, or mismatched billing codes, can create a complete mismatch between what was meant to be sent and what actually arrives.
• Medical claims are never truly finished the way a retail prescription pickup is, since payer requirements can trigger updates, reversals, and status changes long after the original claim.
• Standardization is what makes it possible to identify and root-cause an abnormality, because without a consistent baseline, it is harder to tell what changed.
• Fowler describes every 340B program as its own snowflake, unique to the community it serves, while the core compliance fundamentals stay constant system-wide.
• AI's clearest value in 340B is volume, enabling a 100 percent audit instead of a random sample, which is not realistically achievable by adding more human auditors alone.
• AI needs a human in the loop at the point of exception, reviewing the claims that fall out as apparently ineligible before any compliance decision is finalized.
• Clinical judgment about whether a specific patient was actually treated for the diagnosis a medication addresses is a task Fowler believes should always stay with a human reviewer.
• Any AI or data vendor should be vetted carefully, since even redacted data raises the real question of whether a manufacturer could reverse-engineer it back to an individual patient.
• A rebate-based model creates a real cash flow strain, since covered entities must pay the higher WAC price up front on expensive, high-utilization medications and then wait for the rebate to come back.
• Checking the checker means verifying that a rebate received actually matches what was expected, which takes dedicated time and staff most lean 340B teams do not have to spare.
• Fowler's practical fix is opening a separate financial sub-account solely for 340B rebate funds, which makes them possible to isolate, track, and reconcile against expectations.
• Leveraging an existing TPA relationship to avoid duplicate uploads is a concrete way to reduce the number of channels where data, and communication, can break down.
• Fowler describes her cross-departmental role as being an ambassador of 340B, educating care management, finance, revenue cycle, and IT on how their own workflows affect program compliance.
• She learned early that a 340B program cannot be run in a silo, and that executive leadership support is what allows a program to scale past a single person's capacity.
• Her closing advice to healthcare leaders is that just because a workflow has not been built before does not mean it cannot be built, and that keeping eyes on every part of the program while keeping the patient first is what leads to success.