By Stephen Dean, COO, Keona Health
LinkedIn: Stephen Dean
LinkedIn: Keona Health
Every week, I talk to health system leaders who have spent the last three years investing heavily in patient access technology. Scheduling tools. AI chatbots. Digital front doors. Nurse triage platforms. Intake apps. And nearly every one of them says some version of the same thing: “We’ve bought all this, and patients are still calling us frustrated.” They’re right to be frustrated. And the reason usually isn’t the tools. It’s the architecture.
The Stack Illusion
Most health systems define their patient access stack as a collection of point solutions, a scheduling tool here, a triage platform there, maybe an AI layer on the website. Each product was evaluated on its own merits and solved a specific problem in isolation. What nobody evaluated was how they work together.
The result is what I’d call the stack illusion: a collection of technically functional tools that, in combination, creates more friction than it removes. The patient starts online, hits a wall, calls in, gets asked to repeat their information, gets transferred, gets put on hold, and eventually either gives up or succeeds despite the technology rather than because of it. That’s not a vendor quality problem. It’s a systems design problem. And it costs more than most organizations realize.
The Hidden Cost of Handoff Failures
The most expensive moment in patient access isn’t the phone call. It’s the handoff. The moment a patient moves from one channel to another and the context doesn’t follow. When context breaks, two things happen. The patient repeats themselves, which kills satisfaction. The staff member reconstructs the situation from scratch, which kills efficiency. Multiply that across thousands of interactions a day and you have a structural drag on operations that no single tool can fix.
Most health systems are measuring within channels, not across them. The scheduling tool shows its completion rate. The triage platform shows its volume. Nobody is measuring what happens in the gap between them.
What Integration Actually Means
When health IT folks talk about integration, they usually mean data interoperability: can system A read data from system B? That’s a baseline, not a solution. Real integration in patient access means the phone agent who takes a call at 8am knows the patient tried to schedule online at 11pm and where they dropped off. It means a triage encounter that escalates to an urgent callback comes with clinical context attached. It means AI isn’t a layer on top of the access workflow but built into how decisions get made inside it.
Most health systems don’t have that. They have data connections that still require staff to manually bridge the gaps. That’s not integrated access; it’s just connected data pushing friction around.
The Question You Should Actually Be Asking
Most organizations ask: does this tool do what we need? The better question is: how does this tool change what happens when things don’t go as planned?
Because, in patient access, things regularly don’t go as planned. Digital fails. Calls escalate. Patients are complicated. The question isn’t whether your tools work under ideal conditions. It’s whether they’re designed to route around failure. The organizations getting patient access right have stopped thinking in terms of individual tools and started thinking about what the patient experiences across every touchpoint. They’ve defined success at the handoff, not just within a single channel. What happens when digital fails? What does the phone agent see? What does triage know going in?
If the answers are “nothing” and “whatever the patient tells us,” you have an architecture problem. And no number of new tools solves that without addressing it first.