A multi-site FQHC came to us with a problem they could not solve internally. Their 340B program was generating savings, but leadership suspected they were leaving significant money on the table. They were right.
The Starting Point
When we walked in, the organization had six clinic sites, two in-house pharmacies, and three contract pharmacy arrangements. Their annual 340B savings were approximately $2.1 million. Not bad on paper. But their patient volume, payer mix, and formulary composition suggested the number should be closer to $3.2 million. That gap of $1.1 million was not theoretical. It was sitting in missed captures, misclassified encounters, and contract pharmacy arrangements that were underperforming.
What We Found
The first issue was eligibility determination. Their EHR was not consistently flagging 340B-eligible patients at the point of prescribing. Providers would write a prescription during a qualifying visit, but the prescription would get filled at the in-house pharmacy without the 340B flag because the interface between the EHR and the pharmacy system dropped the eligibility indicator on referral prescriptions. That single integration gap was responsible for roughly $380,000 in missed annual savings.
The second issue was their contract pharmacy network. Two of the three contract pharmacies were capturing 340B-eligible prescriptions at rates well below benchmark. One was at 12 percent capture when similar arrangements in their market were running at 28 to 35 percent. The root cause was not the pharmacy. It was the covered entity not providing timely eligibility files to the TPA managing those arrangements.
The third issue was specialty medications. The organization had a growing HIV and Hepatitis C patient population but was not routing those prescriptions through a 340B-eligible channel. These are high-cost medications where the spread between 340B ceiling price and reimbursement can exceed $15,000 per patient per year. They were filling these scripts at retail, paying wholesale acquisition cost, and missing the 340B discount entirely.
What We Did
We rebuilt their 340B capture workflow from the prescriber forward. We worked with their IT team to fix the EHR-to-pharmacy interface so eligibility flags carried through on all prescription types, including referrals. We restructured the contract pharmacy data exchange so eligibility files were transmitted daily instead of weekly. And we stood up a specialty pharmacy referral pathway that routed high-cost prescriptions to a 340B-eligible dispensing channel.
None of this required new software. It required understanding where the data flow broke down and fixing the handoffs.
The Results
Within eight months, their annual 340B savings increased from $2.1 million to $2.84 million, a 35 percent improvement. The in-house capture rate went from 71 percent to 89 percent. Contract pharmacy captures doubled at the underperforming locations. And the specialty pharmacy pathway generated $420,000 in new savings that did not exist before.
The organization reinvested the incremental savings into two additional clinical pharmacist positions and expanded their chronic disease management program. That is the point of 340B. The savings are not revenue. They are capacity to serve more patients better.
The Lesson
Most 340B programs are not broken. They are just leaking. The leaks are in data handoffs, eligibility logic, and routing decisions that nobody has examined since the program was set up. A systematic review of your capture workflow, done once a year, will almost always find money you did not know you were missing.