The empty layer

A ward manager walks into Tuesday feeling its weight before she's taken off her coat. The same handover notes that didn't get updated overnight. The same lab results sitting unacknowledged in a system that doesn't nudge anyone. The scheduling gap from last week, still unresolved, because the patient's GP, the specialist's secretary, and the hospital's booking team all use different tools and nobody owns the handoff.
She is not delivering care. She's compensating for a system that was never designed to coordinate itself.
She is excellent at her job. That's what makes the next ten years uncomfortable.
Healthcare has accumulated more administrative overhead per patient than almost any other industry, and most of it wasn't designed: it grew. Each new regulation, each new specialisation, each new system created new handoffs. And each new handoff required someone to manage it. The result is a management structure where a large middle tier spends its days on tasks that are, at their core, routing problems.
A large fraction of modern healthcare management exists not to lead, but to compensate for the limits of human coordination. When those limits disappear, some roles will be exposed as structurally empty: not because the people in them were poor performers, but because the problem those roles were solving no longer exists.
The coordination layer is being automated
These are not small tasks. Routing, summarising, chasing, scheduling, verifying, coding: they are genuinely difficult, chronically under-resourced, and endlessly stressful. They're also precisely the category of work that AI agents handle well.
Salesforce Agentforce for Health saves up to 10 hours per week per worker in clinical admin alone: eligibility checks, scheduling, prior authorisations, care gap coordination. Oracle Health's Clinical AI Agent, announced this month, uses ambient listening to draft clinical orders without clinician input. BCG's 2026 analysis frames the shift as moving from task automation to agentic orchestration: not faster clerks, but autonomous systems that close the loop without a human in the middle.
A thread on r/AI_Agents, active this week, makes the distinction cleanly: "AI agents aren't replacing jobs, they're replacing task layers inside jobs." The coordination task layer sits inside many management jobs. When it leaves, what's left?
According to new research from Microsoft and The Health Management Academy published this month, only 3% of healthcare organisations have deployed agentic AI in live workflows, while 43% are already piloting. The gap between those numbers is where the structural question lives.
What survives and what doesn't
Let's name the stakeholders plainly.
For clinicians, the honest read is good news. As one healthcare AI practitioner put it this week: "the agent handles the 80% of admin that's purely mechanical, the clinician focuses on the patient." That's the outcome most people in the sector actually want.
For coordination-heavy managers, the question is harder. When prior authorisations get filed autonomously, when follow-up calls go out without prompting, when referral routing happens inside the EHR without anyone chasing it: what does the role look like? The honest answer depends on whether there was something else in the job all along.
For hospital CEOs and boards, the instinct will be to frame this as efficiency. Ten hours saved per worker. Forty percent reduction in manual effort. That framing is easier to approve and easier to communicate. But it stops short of the structural question underneath.
For patients, there's quiet upside: less that falls through the gaps, faster access, fewer things lost in the handoff.
Becker's Hospital Review makes the harder point: without orchestration embedded into the organisation's infrastructure, AI optimises around structural inefficiency instead of eliminating it. The organisations that will struggle aren't the ones that move fast. They're the ones that run enough pilots to feel like progress, but never force the question underneath.
What survives? Clinical judgement. Emotional presence. The 3am moment when a patient's family needs someone to hold the weight of a decision no protocol can fully specify. These aren't task layers. They are what the job was always supposed to be about.
The question worth asking your leadership team isn't "how much admin can AI save?" It's "if coordination became free tomorrow, which of our management roles would still exist, and why?"
That answer, wherever it leads, is the agenda.
💥 May this inspire you to ask the harder question before the answer imposes itself.