Standard specialty pharmacy PA workflows are designed around the assumption that there is a body of payer precedent for the drug being submitted. The payer has seen submissions for this drug before. Their PA criteria are established. Their reviewers are familiar with the disease state. The documentation requirements are predictable. A well-run workflow with the right documentation will produce a predictable result within a predictable timeline.
Rare disease medications break most of those assumptions. By definition, there are fewer patients receiving the drug — which means fewer submissions in the payer's review history, less established reviewer familiarity, and PA criteria that may be newly written or still being refined. For a specialty pharmacy that handles a mix of standard specialty medications and rare disease therapies, the rare disease PAs will disproportionately consume staff time and generate more back-and-forth with payers — not because the pharmacy is doing anything wrong, but because the payer infrastructure for these drugs hasn't matured the same way it has for high-volume specialty categories like biologics for rheumatology or oncology.
The Payer Precedent Problem
When a specialty pharmacy benefits coordinator submits a PA for a drug in a well-established category — a TNF inhibitor for rheumatoid arthritis, for example — the payer's reviewer has likely seen hundreds of submissions for that drug in that indication. The PA criteria are explicit, the required documentation is known, and the reviewer can evaluate the submission against a well-understood template. Turnaround is faster and additional documentation requests are less frequent because the criteria are well-documented on both sides.
For a newly approved rare disease therapy — an enzyme replacement therapy for a lysosomal storage disorder, or a gene therapy with a narrow indication — the payer reviewer may be encountering the drug for the first time in a PA context. Their PA criteria may have been established months ago based on the FDA label and clinical trial data, but those criteria may not yet reflect the real-world clinical presentation of patients who are appropriate candidates. Documentation requests come back asking for information that doesn't exist in the clinical trial framework. The PA process becomes an education exercise as well as an authorization exercise.
This is the rare disease PA paradox: the patients who have the fewest treatment options and are most dependent on timely access to specific medications are covered by PA processes that are least mature for those medications.
Step Therapy for Conditions with No Step
Step therapy requirements for rare diseases are a particular frustration for specialty pharmacists and prescribers, because many rare diseases have no viable first-line alternative to the prescribed therapy. The condition is treated by one drug, or a very small number of drugs, and the step therapy concept — try a lower-cost preferred agent first — simply doesn't apply.
Yet PA systems built around standard specialty workflows may apply generic step therapy logic to rare disease submissions, triggering a documentation requirement that the prescriber must respond to even when the requirement is clinically inapplicable. The response is typically a letter from the specialist documenting that there is no appropriate alternative therapy, that the patient's condition is responsive only to the prescribed agent, and requesting a step therapy exception — which is then reviewed by the payer, often by a reviewer without rare disease expertise.
Some states have enacted protections that limit step therapy requirements for patients with rare diseases or established diagnoses. For pharmacies in those states serving Medicaid or state-regulated commercial plans, knowing which protections apply to which plan types is operationally useful — a letter invoking the applicable state law can resolve a step therapy issue that would otherwise take weeks to work through the standard exception process.
We're not saying step therapy protections for rare disease are consistently enforced or universally applicable — the patchwork of state laws, plan types, and ERISA preemption creates real variation in what any given patient's rights are. We're saying that knowing the applicable rules for your state and your patient's plan type can meaningfully affect whether you get an exception in days or weeks.
Specialty Pharmacy Distribution Programs (SPP/SPD) and PA Complexity
Many rare disease therapies are dispensed under specialty pharmacy distribution programs — sometimes called Specialty Pharmacy Programs (SPP) or Specialty Distributor Programs (SPD) — where the manufacturer has contracted with a limited network of specialty pharmacies that are accredited and trained to dispense and support the specific medication. These programs add a layer of coordination to the PA process that's specific to rare disease.
When a pharmacy is part of a manufacturer's limited distribution network for a rare disease drug, they may have access to manufacturer hub services that assist with PA and patient support — programs that can provide clinical documentation templates, track PA status, and connect patients with copay assistance or foundation funding. The coordination between the pharmacy's own PA workflow and the manufacturer's hub services needs to be explicit to avoid duplicate submissions or conflicting status tracking.
For pharmacies that are not in the limited distribution network for a given rare disease drug, the hub service option may not be available, and the PA process falls entirely to the pharmacy's own team. This creates asymmetry within the rare disease landscape: the same drug may have more PA support infrastructure available to some pharmacies than others, based on distribution network membership.
Documentation Assembly for Rare Disease PAs
The documentation required for rare disease PA submissions is typically more extensive than for standard specialty medications, and it draws from a narrower pool of prescribers. Most rare diseases are managed by a small number of specialist physicians — metabolic disease specialists, neuromuscular disease specialists, hematologists with specific rare disease expertise — who may be at academic medical centers or specialty clinics rather than community practices.
Getting clinical documentation from a specialist at a major academic medical center has its own logistics: the documentation request needs to reach the right person in a large institution, be processed through that institution's administrative workflow, and be transmitted in a format the payer accepts. For a specialty pharmacy building a rare disease practice, establishing a direct working relationship with the specialist's practice administrator — the person who actually handles PA documentation requests — is as important as having the right submission workflow.
Documenting that relationship in a structured way — specialist contact name, preferred communication method, typical turnaround for documentation requests, which staff member to follow up with if no response within 48 hours — is operational infrastructure that pays dividends over multiple submissions. The first rare disease PA from a new prescriber relationship is always the hardest; the tenth is much smoother if the coordination pathway is documented and maintained.
Redesigning for Rare Disease: What the Workflow Needs to Look Like
Standard specialty pharmacy PA workflows are built for throughput — processing a high volume of submissions efficiently for well-understood drugs and payers. Rare disease PA workflows need to be built for complexity management: handling a lower volume of more intricate cases, each requiring more active coordination and documentation assembly.
The operational changes that make the most difference for rare disease PA are:
- Intake triage that flags rare disease scripts at receipt — so they're assigned to experienced coordinators rather than the general queue from the start
- Prescriber documentation request initiated at submission, not after the payer asks — for drugs where clinical documentation is always required, getting that documentation in parallel with the PA submission rather than waiting for the payer to ask for it
- Payer-specific rare disease criteria tracked as institutional knowledge — including which payers have explicit rare disease criteria, which apply generic specialty PA criteria, and which have known patterns of requesting specific documentation types
- Expedited review eligibility evaluated at intake — rare disease diagnoses frequently support urgent or expedited review requests based on clinical necessity, and that option should be evaluated before the standard review timeline starts running
The pharmacies that handle rare disease PA well aren't doing fundamentally different work from standard specialty PA — they're applying the same core skills to a more complex situation, with workflow infrastructure that reflects the complexity rather than fighting it.
