The Hub Paradox: Why Patient Access Is Breaking

The hub did everything right — and the patient still never started therapy. The paradox isn't the hub. It's the seams around it.

The short version: Hub programs are built for the visible 10% of the patient journey — enrollment, benefit verification, prior authorization, first fill — and most of them do that work well. Persistence is decided in the other 90%: the months between visits that no hub contract covers and no single function owns. The paradox is that a hub can succeed completely at its job while the patient fails anyway, because the patient's journey runs through handoffs between the hub, specialty pharmacy, market access, the field, and financial assistance — and those handoffs belong to no one.

The case that closed perfectly

A patient is enrolled within 48 hours. Benefits verified. Prior authorization approved on the first submission. Copay support in place. First fill shipped. The hub closes the case, and every metric on its dashboard is green.

Seven months later, the patient is off therapy — and nobody saw it happen, because the moment the case closed was the moment the 90% began.

That is the hub paradox: the part of the journey with the most infrastructure, the most staffing, and the best measurement is the part where patients were least likely to be lost. The part where persistence is actually decided has almost none of the three.

This is not a hub failure

The instinct is to blame the hub, renegotiate the contract, or switch vendors. That misreads the problem.

Hubs are a function, and they perform their function. They were scoped, priced, and measured around access events — enrollment, verification, authorization, fulfillment. Expecting a hub to own persistence is expecting it to do a job it was never contracted, staffed, or paid to do.

The failure lives in the structure around the hub. Patient support is run as a collection of functions: the hub owns enrollment, market access owns coverage, a vendor owns copay, specialty pharmacy owns dispensing, the field owns the provider relationship, marketing owns education. Each one does its piece reasonably well. But the patient doesn't experience functions — the patient experiences the journey across them, and the journey breaks in the handoffs:

• The hub completes a flawless enrollment and hands off to specialty pharmacy — which is waiting on information the hub didn't know it needed, while the patient hears nothing and assumes they've been forgotten.
• Financial assistance is approved at the start of therapy and quietly lapses at reauthorization — in a month when no function is scheduled to touch the patient.
• A coverage change hits in month six. Market access sees the payer policy. The hub's case has been closed for five months. No one connects the two until the refills stop.
• The hub flags a barrier it can see but can't fix — and there is no defined owner on the other side of the handoff to catch it.

In every one of these, each function's own metrics stay green. The loss is invisible precisely because it happens between the dashboards, in the space no single team owns or measures.

Why this is getting harder to ignore

For years, enrollment numbers were enough. That is ending. Value-based arrangements increasingly tie revenue to real-world outcomes, not access events. Finance teams are asking what patient support spend returns — and "enrollments" is not an answer to that question. And as therapeutic areas get more crowded, persistence data is becoming part of the conversation payers and providers actually have about a brand.

An organization that can only report the 10% — enrollment rates, turnaround times, call volumes — will keep posting strong numbers while its launch underperforms, and will not be able to explain why.

What to measure instead

The shift is from activity metrics to journey outcomes. Not "how many patients enrolled," but: where, specifically, patients discontinue, and what preceded it. How long access barriers take to resolve — across functions, not within one. What a persistent patient costs versus what an enrollment costs. Which handoffs lose the most patients.

None of those can be answered from inside any single function, including the hub — because each function can only see its own segment. Answering them requires a view across the whole journey at once: hub, specialty pharmacy, market access, field, and financial assistance reconciled into one picture of where persistence leaks and what each leak costs. Producing that view is what our patent-pending diagnostic, the Gap Finder, was built to do — not to replace the hub, but to show every function the same map of the seams between them, prioritized by what each one is costing.

Three questions before the next hub renewal

For any team reviewing its access investment, three questions are worth answering with evidence rather than assumption:

Where in the journey — not just the enrollment window — are our patients actually being lost?

Which of those losses happen in handoffs between functions, where no contract and no team currently owns the catch?

If we designed support around keeping patients on therapy, rather than around getting them started, what would we fund differently?

Teams that can't answer these aren't ready to renegotiate a hub contract — because they'd be renegotiating the 10% while the 90% keeps leaking.

The hub isn't the paradox. The paradox is a system that staffs, funds, and measures the beginning of the journey, then is surprised when patients are lost in the long middle nobody owns. The hub did its job. The question is who's doing the rest of it.

Linked Patient Learning helps pharma teams see where patient persistence leaks across the functions around the hub — and which handoff gaps to close first. If your access metrics are green but persistence isn't, let's talk.