Access design is an operations decision, not a marketing one

Manufacturers plan for payer access well before launch: pricing strategy, HEOR dossiers, payer advisory boards. That part is standard practice. What gets less of that same early attention is the provider side: whether the site that will actually stock, prepare, and administer the product can do it without inventing a workaround on day one.

A limited-distribution example

Jelmyto is a useful illustration, not because it is unusual, but because it makes the design problem visible. It treats a rare, low-grade upper tract urothelial cancer, it is instilled directly into the renal pelvis, and it is reconstituted as a reverse-thermal gel: liquid when cold, set once it reaches body temperature. The preparation and administration window is tight, and the technique does not map onto anything else in a typical infusion pharmacy's routine.

For a program that might treat a handful of these patients in a given year, that is a real operational problem, and it has nothing to do with whether the drug works. Staying proficient at a rarely used compounding step that leaves no room for error is its own risk. The choice a lot of programs land on, and the one I would recommend, is to route procurement and preparation through a compounding pharmacy that handles this at volume, rather than build in-house competency for something used a handful of times a year. It is a better outcome for the patient and a smaller risk for the program.

That is the decision manufacturers should be making before launch. For a product with a narrow patient population or a handling process with no margin for error, the distribution and support model is not a marketing decision made after the fact. It belongs in the same room as the decisions about dosing and packaging, because a health system will make its own version of that decision with or without the manufacturer's input, and it would rather make it with.

What a well-built hub program actually does

I have never run a hub. What follows is a provider-side read on what the good ones deliver, not a technical review of any specific program.

• Benefits investigation done once, centrally. Instead of every site rebuilding the same payer research from scratch, one team does it and every site gets the answer.
• A single point of contact for the program. One name a clinic can call, instead of a different workaround at every site that happens to use the product.
• Case management for volume a site cannot staff for. A center that treats a handful of patients a year on a given product cannot justify a dedicated navigator. A hub can, because it is aggregating across every site that uses it.
• Assistance enrollment run by people who do it daily. Foundation and copay enrollment handled by a team that processes it constantly beats a clinic staff member who does it twice a year and forgets the form each time.

The honest caveat: this is uneven across programs. A good hub removes work from the provider side. A bad one adds a phone tree and a fax number. The difference is usually visible within the first two or three cases, and it is worth asking about specifically rather than assuming.

This is the specific read manufacturers bring me in for: a provider-side check on whether a hub or access program will actually hold up once it reaches a clinic, run before launch or while it is still fixable, not after providers have already built a workaround around it. It falls under voice-of-the-customer advisory, one piece of the medical affairs work I do for manufacturers.

The newer piece: AI in prior authorization

A growing set of tools are starting to sit on both sides of the prior authorization process, payer and provider, pulling structured chart data automatically instead of a staff member re-typing it into a portal by hand. It is early, and it is uneven across payers and specialties. None of it replaces the clinical judgment behind the actual request. But it is aimed directly at the part of this process that has always been hardest to instrument: the paperwork, not the medicine. It is worth asking about when you are evaluating a hub or access platform, because the answer is changing faster than most contracts get renegotiated.

The through-line

Health systems and manufacturers are usually having two different conversations about the same product. The health system is asking whether it can actually deliver the drug: acquisition, preparation, chair time, billing. The manufacturer is asking whether the field can get the drug adopted. Those turn out to be the same question, asked from opposite sides of the table, and the products designed with the provider side's constraints in mind are the ones that end up easier to actually use.

Robert Walters, PharmD, MBA is the founder of Walters Rx Strategy and is Apexus Advanced 340B Certified. He spent fifteen years leading health-system pharmacy operations across acute care, a cancer center, infusion, and emergency department pharmacy. Book a consult or read more insights.

This article is general and informational. Jelmyto is referenced here only as an operational example; this is not an endorsement and no claim is made about its clinical use. This article is not legal, regulatory, clinical, or medical advice, and it does not recommend or promote any specific product or therapy.