Breaking down the exact workflow of a specialty medication denial, and where the system is designed to create friction.

Most people in healthcare treat a prior authorization denial as the end of the story. The claim comes back. The code is there. Everyone moves on. But a denial is not the end of anything. It is a moment inside a much longer sequence of decisions, handoffs, and system failures that were baked in long before the physician ever picked up the pen.

To understand why specialty patients do not get their medications, you have to understand what actually happens when a PA goes wrong. Not the summary. Not the code. The anatomy.

A denied authorization is not a paperwork failure. It is a treatment delay. The back office is where the clinical outcome gets decided.

The workflow, step by step

Every specialty PA follows roughly the same path from prescription to first dose. Here is where that path breaks.

Step 01 — The prescription is written

The physician makes the clinical decision. A biologic for a rheumatoid arthritis patient. A specialty infusion for MS. From a clinical standpoint, the decision is made. From a systems standpoint, the real work is just beginning.

Where friction starts: The prescribing system and the PA intake system often do not talk to each other. The clinical decision lives in the EHR. The PA request has to be initiated separately, by a different person, in a different workflow. That gap is where information first gets lost.

Step 02 — Benefit verification

Before a PA can even be submitted, the practice needs to verify whether the patient's plan covers this drug, at what tier, through which specialty pharmacy, and under what conditions. This is not one call. For a complex specialty patient, this can mean checking medical benefits, pharmacy benefits, and any applicable copay programs.

Where friction starts: Medicare Advantage plans vary by region, product, and plan year. A generalist who does not know the difference between a Part B biologic and a Part D oral specialty drug will file the wrong benefit request, get the wrong information, and either delay or incorrectly submit the PA.

Step 03 — Prior authorization submission

The PA is submitted to the payer with clinical documentation: diagnosis codes, treatment history, step therapy records, lab values, physician notes. This is where specialty expertise matters most. Payer criteria are not generic. They are drug-specific, diagnosis-specific, and plan-specific. A biologic PA for a Medicare Advantage patient looks nothing like the same drug under a commercial PPO.

Where friction starts: Most denials are not clinical denials. They are process denials. Missing documentation. Wrong diagnosis code. Step therapy requirement not addressed. A PA submitted by someone who does not know the payer's criteria will get denied on administrative grounds even when the clinical case is airtight.

Step 04 — The denial lands

The payer issues a denial. The denial reason matters enormously. "Not medically necessary" requires a peer-to-peer. "Incomplete documentation" requires resubmission. "Step therapy not met" requires either a new submission with different documentation or an appeal. Each path has its own timeline and its own process. The clock starts over.

Where friction starts: Practices that receive a denial and do nothing are more common than anyone admits. There is no automated escalation. No mandatory follow-up. If the denial lands and nobody is watching the queue, the patient simply does not get the medication.

Step 05 — Appeal or peer-to-peer

The appeal process is intentionally difficult. Deadlines vary by payer and plan type. Documentation requirements differ. The physician may need to schedule a peer-to-peer with the payer's medical director, often within a 72-hour window that nobody communicated clearly. Miss the window, and the denial is final.

Where friction starts: The peer-to-peer process is a friction point designed to consume physician time. Most physicians do not have a structured system for tracking open appeals. Most practices do not have someone who owns this workflow. The result is approvals that never happen because nobody followed up in time.

Step 06 — Patient assistance program screening (if appeal fails)

If the appeal fails, or if cost is a barrier independent of the authorization, the patient may qualify for a manufacturer PAP or commercial copay card. This is a separate workflow with its own income eligibility criteria, insurance restrictions, and enrollment portals. A PAP application that is never filed is revenue that never comes in and a patient who never starts treatment.

Where friction starts: Practices routinely miss PAP eligibility because the screening never happens. The physician writes the prescription. The PA gets denied. Nobody asks whether the patient qualifies for manufacturer assistance. The patient is told they cannot afford the drug. The case is closed. This is one of the most avoidable failures in specialty access.

The design question nobody is asking

Every friction point in this workflow exists because of a choice someone made, somewhere, to build the system that way. Payer portals are hard to use. Documentation requirements are not standardized. Appeal windows are narrow. Step therapy requirements are not published clearly. None of this is accidental.

The prior authorization system was not designed to be navigated. It was designed to be a barrier. That is its function. The question is not whether the friction is real. It is whether the practice has built the infrastructure to absorb it on behalf of the patient.

Most practices have not. They have someone in the back office doing their best with a generalist workflow that was never built for specialty PA criteria. They lose denials they should win. They miss appeals they had time to file. They skip PAP screenings that would have paid for the drug. The gap between a prescription and a patient's first treatment is not inevitable. It is a product of infrastructure failure at the practice level.

The system does not lose patients at the clinical decision. It loses them in the handoffs, the queues, and the workflows nobody is watching.

What closes the gap

The answer is not a new appeals software platform. It is not an AI tool that reads denial codes. It is operational expertise applied to a specialty-specific workflow, by someone who knows that a P1 denial code on a Medicare Advantage biologic means something different than the same code on a commercial plan.

The practices that consistently get their patients to first dose are the ones that have built three things: a BV workflow that catches eligibility issues before submission, a PA process that is specific to the payer and the drug class, and a denial management system that treats every denied authorization as an open case until it is resolved or exhausted.

Everything else is noise. The specialty access gap closes one workflow at a time, in back offices that most people in healthcare never think about.

Taylor McKinney · The Access Gap · @theaccessgap