My kid needed medication. Everything else stopped. That’s the deal when you’re a parent. Work, meetings, deadlines — all of it takes a back seat until your child is safe and cared for. So when our pediatrician called in a prescription, I figured I’d pick it up within the hour and get back to my desk. Instead, I experienced firsthand how healthcare automation failures can turn a simple errand into a multi-hour, multi-location nightmare — one that wasted the time of 3 pharmacy employees and left a parent standing helpless at a counter. What followed was a 6-hour journey through broken systems, disconnected pharmacies, and automation that seemed designed to keep humans out of the loop — even when humans were the only ones who could fix the problem. This isn’t a rant. It’s a case study in how healthcare automation fails when teams build it without guardrails, and a blueprint for what pharmacy CX redesign should actually look like.
The Journey: One Prescription, Three Locations, No Clarity
It started at the first pharmacy. Their core systems were mid-reboot — in the middle of the afternoon — so the staff couldn’t process any prescriptions. Fair enough. Technology fails. I asked my pediatrician’s office to transfer the prescription to another branch and headed there. A technician at the second location confirmed the transfer. “Give us a couple hours,” she said. “We’ll text you when it’s ready.” Three hours later: no text, no update, no clarity. I called. That’s when I met the IVR system — a maze of menu options that understood nothing about my situation. No “I’m checking on a transfer.” No “This is urgent, connect me to a human.” Just loops. Research from Forrester consistently shows that poor IVR design ranks among the top drivers of customer frustration — and I was living proof. I eventually figured out how to break through, but it took longer than it should have. When I finally reached a person, she told me the first location never actually transferred the prescription. They said they sent it; the second location never received it. She’d have to call them manually and call me back. At this point, I’m not thinking about work. I’m not thinking about productivity. I’m thinking: my kid needs this medication, and I have no idea when — or if — anyone will make it happen.
The Final Blow: A Phantom Pickup and an Insurance Reversal
The callback came, but not with good news. The original pharmacy — the one whose system reboot started this whole mess — now showed the prescription as picked up. But I never picked it up. I was standing in a different pharmacy, empty-handed. That single bad status flag triggered a cascade of manual work:
- The original pharmacy had to reverse the insurance claim before anything else could happen
- A technician had to release the prescription back into the system
- The second pharmacy had to re-process it from scratch
- A pharmacist — not a technician, a pharmacist — had to step in and untangle what automation had broken
Three different humans. One pediatric prescription. Hours of collective effort. And a parent standing at a counter, watching highly trained professionals do error correction instead of patient care.
The Resolution: A Pharmacist Saves the Day
Finally, the pharmacist at the third location got it done. She reversed the insurance claim, reprocessed the prescription, and handed me the medication at no out-of-pocket cost. Originally, the system wanted to charge me $19 because of the claim confusion. I would have paid it gladly — not because $19 is nothing, but because at that point, I’d already lost far more than $19 worth of time, energy, and trust. But here’s what stuck with me: this pharmacist spent 20+ minutes fixing a problem that better system design would have prevented entirely. According to McKinsey’s research on healthcare operations, frontline healthcare workers spend up to 70% of their time on administrative tasks rather than patient care. Multiply cases like mine by hundreds per week across thousands of locations, and you start to see the real cost of broken pharmacy CX — not just to patients, but to the employees trying to hold it together.
Why Healthcare Automation Failures Like This Keep Happening
From the outside, this looks like a frustrating afternoon. From a product and operations lens, it’s a textbook case of healthcare automation failure — and it’s not an edge case. It’s a predictable failure mode in any large pharmacy network running on fragmented systems and rigid automation. The Journal of the American Medical Informatics Association has documented how disconnected health IT systems create downstream errors that require costly human intervention. My experience was a live demonstration of exactly that pattern.
The Specific Breakdowns That Caused This Failure
No unified system of record. Each pharmacy location operated like an island. “Transferred” at one location didn’t mean “received” at another. The system allowed a prescription to show “picked up” when no one had picked it up — and nothing caught the error. Automation without guardrails. The IVR kept routing me through menus even though my situation clearly required a human. The system let staff mark a prescription as picked up without validating that the physical handoff actually happened. Invisible work pushed to humans. Every failure in the automated workflow became manual cleanup for staff — phone calls between locations, insurance reversals, re-entry of data that should have flowed automatically. This is the hidden tax of healthcare automation failures: they don’t eliminate work, they just shift it to your most expensive employees. No transparency for patients. At no point could I see where my prescription actually was. No SMS, no dashboard. Just silence, followed by bad news, and more waiting.
What Effective Pharmacy CX Redesign Looks Like
The same technologies that caused this mess — automation, IVR, digital workflows — can fix it when teams design them with the right principles. If I were leading this pharmacy CX redesign, here’s what I’d make non-negotiable: A true system of record. Every location reads and writes to the same prescription state. “Transferred,” “in progress,” “ready,” and “picked up” mean the same thing everywhere, updated in real time. Gartner’s research on master data management shows this is foundational to any cross-location operation. State validation before status changes. Before anyone can mark a prescription as “picked up,” the system confirms that the insurance claim, dispensing, and physical handoff all align. No more phantom pickups. Transparent patient-facing status. Parents like me should see — via text or app — exactly where the prescription sits, which location owns it, and whether anything blocks it. Human-aware automation. IVR and digital channels should recognize patterns that signal urgency or confusion — like repeated calls about the same prescription — and fast-track those cases to a human instead of looping through menus. Exception logging for root cause. Every time a pharmacist has to manually reverse an insurance claim or rescue a transfer, the system should log that event for analysis — not treat it as one-off noise.
The Bigger Picture
These aren’t moonshot ideas. This is orchestration of existing systems around the actual customer journey, with safeguards for known failure modes. The pharmacy chains that figure this out first will see it in their numbers: lower call volumes, higher NPS, reduced employee burnout, and fewer parents pacing in front of counters wondering if their kid will get the medication they need.
A Moment of Honesty
I was genuinely considering applying to this pharmacy chain. After this experience, I paused and asked myself: if this is what the customer-facing journey looks like, what does the internal workflow design look like? Where’s the ownership? The guardrails? The empathy for human time — both customer and employee? These problems are fixable. They should be fixed. And they represent exactly the kind of end-to-end system redesign that I find genuinely interesting.
If Your Organization Struggles with Healthcare Automation Failures, I Can Help
I’ve spent 15+ years leading product and platform teams through complex system redesigns — the kind where automation, operations, and customer experience all have to work together or nothing works at all. This isn’t about adding more technology. It’s about designing systems that know when to automate, when to escalate, and when to get out of the way. If you’re a product, CX, or operations leader at a healthcare or retail pharmacy company wrestling with these challenges, let’s talk. This is exactly the kind of problem I help teams solve.