A specialty pharmacy referral arrives, and within minutes it has touched five different systems — none of which share a record.
The referral comes in by fax or e-prescribe and lands in an intake queue. Benefits and prior authorization get worked in a payer portal or a separate PA tool. Dispensing happens in the pharmacy management system. Inventory and procurement — cold-chain drugs, limited-distribution products, REMS requirements — live in yet another platform. And patient outreach, refill coordination, and financial-assistance enrollment run somewhere else again.
Five systems. One patient. No connection between them.
So a single case gets re-entered five times, and the staff become the integration layer — the human glue moving data from one screen to the next, all day, every day. This is the operational reality of specialty pharmacy, and it’s the single biggest reason a growing pharmacy’s headcount climbs faster than its volume.
Why the systems don’t talk
This isn’t negligence. It’s the shape of the software category.
Specialty pharmacy is a young, fragmented market. The intake tool, the PA tool, the dispensing platform, the inventory system, and the patient-engagement layer were each built by a different vendor to solve a different problem — and each became the system of record for its slice. None was designed to be the single source of truth for the whole case, because no single vendor owns the whole case.
The result is five systems that each hold part of the patient’s story and none that holds all of it. Integrating them is possible, but it’s custom work, it’s expensive, and it never rises to the top of the priority list — because the pharmacy is already functioning. The staff are absorbing the gap. It works, right up until volume grows and the manual bridging stops scaling.
That’s the trap: the cost of disconnection is real but invisible. It shows up as headcount, as overtime, as turnaround time, as errors caught late — never as a line item anyone can point to.
What it looks like on the floor
Three patterns show up in almost every specialty pharmacy running disconnected systems.
The same patient, entered five times. Demographics, insurance, prescriber, drug — re-keyed into each system because none of them talk. Every re-entry is a chance to introduce an error, and every error surfaces downstream, where it’s most expensive to fix.
The denied PA that no one routed back. A prior authorization comes back denied or needs more information. That status lives in the PA tool. But the intake team — the people who could actually chase the missing document — don’t see it unless someone tells them. The case sits. The patient waits. The clock runs.
The clock no single system owns. Every specialty case is a race: the patient needs therapy, the payer needs information, and the pharmacy is in the middle. Because the case is spread across five systems, no one system knows how long the whole thing has been open. A case can read “in progress” in three tools and be stalled in reality, and nobody notices until the patient calls asking where their medication is.
None of these are people problems. They’re structural — the predictable output of running one patient across five disconnected systems.
The regulatory turn — and the carve-out nobody mentions
Here’s where it gets sharper.
Everyone in healthcare is talking about CMS-0057-F, the Interoperability and Prior Authorization Final Rule. Starting in 2026, impacted payers — Medicare Advantage, Medicaid and CHIP, and Qualified Health Plans on the federal exchange — must return prior authorization decisions within 72 hours for urgent requests and seven days for standard ones. By 2027, they must run prior authorization through a standardized electronic API. Prior auth for the rest of healthcare is about to get faster and, finally, digital.
Except for one thing. The rule explicitly excludes drugs.
In CMS’s own words, this provision “does not apply to prior authorization decisions for drugs.” The 72-hour clock, the seven-day standard, the electronic PA exchange — all of it is scoped to medical items and services. Medication prior authorization is carved out.
Read that again if you run a specialty pharmacy, because it means the most-cited prior-authorization reform in a decade skips the exact work you do all day. Drug PA is your entire bottleneck, and it’s the one thing the rule leaves untouched.
That doesn’t make the pressure disappear — it redirects it. Electronic prior authorization for drugs already exists through established pharmacy standards and is spreading. Payers have publicly committed to streamlining prior authorization. States are passing their own reforms. The direction of travel is unmistakable: PA is going electronic and fast everywhere, drugs included — just not on CMS-0057-F’s mandate or timeline.
So the specialty pharmacy lands in the worst seat of the transition. The rest of healthcare digitizes its prior authorization on a federal deadline. Specialty pharmacy — carved out of that deadline, still bridging five systems by hand — doesn’t fall less behind. It falls further behind, because the gap between “manual” and “everyone else’s automated” widens every quarter.
What the fix actually requires
The instinct is to buy a sixth platform — an all-in-one that promises to replace the five. It rarely works. Rip-and-replace in a live pharmacy is a multi-year project with real patient-safety risk, and by the time it’s finished the market has moved.
The realistic fix is smaller and faster: stop trying to replace the five systems and start connecting the three handoffs that actually matter — intake → prior authorization → dispensing.
Connect those three and the record moves on its own instead of being re-keyed. A denied PA flags the intake team automatically. The clock — how long this specific case has been open, across every system it touches — becomes visible to everyone who owns a piece of it. The five systems stay exactly where they are; a thin integration and orchestration layer sits on top of them and carries the case from one to the next.
That’s the difference between compliance as a scramble and compliance as a default — and it’s achievable in weeks, not years, because it doesn’t touch the systems of record. It connects them.
Where WRA Fits
This is the work we do: not replacing the tools a pharmacy already runs, but building the connective layer between them. We map the intake-to-dispense path, find the two or three handoffs where the manual bridging costs the most, and automate those first — so the case moves itself, exceptions surface early, and the staff stop being the integration layer.
It’s software that runs in the background of your existing systems — no new platforms to manage, nothing to rip and replace.
Ready to Trace Your Slowest Case?
Take one recent case and trace it by hand across your five systems. At each step, ask a single question: if this case stalled right now, who would know, and how long before they knew?
If the answer at any handoff is “no one, until the patient calls” — that’s your first automation. Not the biggest system. The most fragile handoff.