Twenty years of customer interviews, workshops, and journey maps. Then agentic AI arrived, and every framework I trusted turned out to share one assumption I had stopped noticing: that the human is always smarter than the tool. Here's what breaks when that stops being true.
The clinical reasoning pattern hasn't changed since Hippocrates. The vessels carrying it have, from paper charts to cloud EHRs. For fifty years, every vessel moved the data without understanding it. AI breaks that pattern for the first time. Not a better vessel. One that thinks.
I still read NEJM and BMJ cover to cover. Lately they are filled with elegant AI breakthroughs: models that promise to transform diagnosis, prediction, resource allocation. The deeper I build enterprise software, the more critical I get. A paper is a demo. A scaled deployment is a different problem.
This week I read three papers that made me happy. JAMA. NEJM. Nature Medicine. All randomized trials. All showing AI outperforming standard care. Then I read the methodology. None of them LLMs. The AI winning in top journals in 2026 was built before the hype cycle. The blueprint was always there.
A Nature study shows LLMs achieve 94.9% accuracy on benchmarks but only 34.5% when laypeople use LLMs on physician-created scenarios. The gap reveals something deeper: We measure the model in isolation. We deploy to a human in distress. The system fails at the intersection.
The physician's job has always been data synthesis. Fragments, approximations, family filters, descriptions of pill geometry. Consumer health AI was built for a different patient. One that has never walked through a clinic door.
For 20 years, I translated between customers and engineers. Now I architect decision systems with AI. But here's the catch: you're designing for two customers: humans and their AI agents. Design for one, forget the other, and it fails.
Everyone talks about governance. Nobody agrees on what it means. Data governance, AI governance, master data governance: they're not separate programs. They're one spectrum. And most enterprises already have 70% of what they need. They just can't see how the pieces connect.
MVP was meant to test ideas, not become architecture. Now, we’ve started stacking prototypes into production systems nobody designed as systems. When one layer fails, the whole structure drifts silently. In medicine, that’s not technical debt. It’s patient risk.
My first AI-assisted article was polished, accurate, and completely unrecognizable as mine. The problem wasn’t the model. It was that I never taught it how I think. If you want AI to sound like you, you have to externalize your reasoning first.
In healthcare AI, policy shifts now appear first in journals like JAMA and NEJM, then quietly become grant conditions and RFP requirements. Many tech teams miss this signal. The winners will be those who translate medical literature into architecture before it becomes mandatory.
Data products are the missing layer in healthcare AI. There is no harmonization at scale without them. Instead of fragmented, untrusted datasets, data products create governed, reusable, semantically clear assets with defined ownership and value. That’s how AI moves from pilots to production.