After working on AI deployments across healthcare operations, command centres, and clinical workflows, I keep seeing the same pattern emerge. The technology itself usually performs reasonably well. The real challenge arrives when AI collides with the reality of hospitals.
It almost always comes down to the “4 Ds”.
Data
Healthcare data still lives across fragmented systems, disconnected workflows, and decades of operational workarounds. One department records timestamps differently from another. Clinical context gets buried in free text. Operational data changes every few minutes. AI models then inherit all of that chaos with remarkable enthusiasm.
Decisions
Healthcare is full of nuanced judgement calls where experience, context, and human trust matter enormously. Clinicians rarely want an algorithm making decisions for them. They want systems that support judgement, surface risk earlier, and reduce cognitive burden during busy operational periods.
Disruption
This is where projects become particularly entertaining. Organisations sometimes automate workflows that were already struggling before AI arrived. The result is usually faster movement towards the same bottlenecks… just with more dashboards and a slightly larger cloud bill.
We need to stop scaling inefficiency. AI should be an opportunity to redesign pathways, simplify operational friction, and rethink how decisions flow across the organisation.
Delegation
This is where organisations decide what AI agents are genuinely trusted to handle autonomously, and where humans still need oversight. Delegation is less about replacing people and more about carefully assigning operational responsibility.
Bed management, discharge coordination, documentation support, and patient communications all sit at different levels of acceptable autonomy.
The strongest deployments redesign workflows alongside the technology. They rethink escalation paths, operational ownership, and decision support from the ground up.
That is where AI starts creating measurable impact.
And occasionally, after enough workshops, architecture reviews, governance meetings, and coffee, everyone even agrees on what the workflow actually is.
