The Ops Stack — Newsletter Archive
A weekly newsletter on workflow and data orchestration, specialty pharmacy and infusion operations, and what actually moves operational work. Written by Jose Cruz, Wiles Ridge Automations. Subscribe on LinkedIn →
Many editions draw on specialty pharmacy and infusion operations. For how WRA works in that space, see Specialty Pharmacy + Infusion Operations →
What the Workaround Costs
A new system arrives with a price. The workaround it would replace never does. A worksheet for pricing one with your own numbers.
It Looks Like a Capacity Problem
When work backs up, the first request is usually more people. Often the backlog is telling you something else.
Where Work Actually Stalls
The expensive operational problems rarely look like outages. They live in the seams between systems, teams and data.
The Rule Changed the Rails. It Didn't Change the Drug.
CMS-0057-F's prior authorization API requirements arrive January 2027, but drug prior authorizations are excluded. What that means for infusion and specialty pharmacy operations.
"Pending" Is Not an Operating Strategy
Waiting is unavoidable. Losing track of why you're waiting, who owns the next action, and when something should happen next is not.
The Integration Gap Nobody Budgets For
In infusion operations, every system can record the right status while the case still loses time between intake, authorization, pharmacy, scheduling and billing.
Three Questions to Ask Before You Automate Anything
Most automation projects don't fail on execution — they fail because nobody answered these three questions about the process, its readiness, and its ROI before the project started.
The Layer Nobody Builds
Most businesses automate tasks. The ones that scale automate the operating model underneath — the shared data layer, the runtime, the observability that makes automation trustworthy.
The Prior Auth Status Gap: What Your Systems Aren't Telling Each Other
Eligibility and prior auth status live in the payer's system, not yours. Why the manual status call exists, the three failure patterns it produces, and how an integration layer closes the gap automatically.
Why Your Five Systems Disagree: The Single-Source-of-Truth Problem in Healthcare Operations
When the same fact lives in five systems, the copies drift and disagree. Why standardizing on one system doesn't work — and what a real single source of truth looks like.
The Re-Key Tax: Why One Patient Runs Through Five Systems in Healthcare Operations
Whether it's a specialty pharmacy, an infusion center, or a multi-site clinic, the same patient gets re-entered into five disconnected systems. Why it's getting more expensive, and the three handoffs worth fixing first.
Why the 5 Systems in Your Specialty Pharmacy Don't Talk to Each Other
A specialty pharmacy referral touches five disconnected systems before it's done. Why that happens, what it costs, and what CMS-0057-F's drug carve-out means for pharmacies still bridging by hand.
How to Document a Process That Lives in Someone's Head
Documenting what should happen is nearly useless. Here's how to actually extract a process from the person who runs it — and why documentation alone still isn't enough.
Why SMB Dashboards Fail — and What to Build Instead
Most SMB dashboards track lagging indicators nobody can act on. Why that happens, what it costs, and what actually makes a dashboard useful.
The $200K Operator Problem: When Your Best Person Is the Bottleneck
Every growing business eventually builds its operational reliability around one person's memory. Why it happens, what it looks like, and how to fix it without losing them.
Why AI Tools Aren't Fixing Your Ops — And What Actually Does
Individual productivity isn't operational leverage. Why most AI tool adoption makes people faster inside a system that stays slow — and what actually changes it.