The Short Answer
A widely-shared DeepMind position paper argues LLMs cannot perform abduction — the leap that generates new scientific premises. It is one researcher's personal view, not an institutional position, and it does not explain why clinical AI errs today. Its real lesson for health systems is architectural: build so the model can be replaced. On ibl.ai you own all the code and the data and run it model-agnostic across any LLM.
The gap between what the paper claims and what it is being cited for is itself worth documenting.
What did the DeepMind position paper actually argue?
That LLMs cannot make an abductive leap. The paper is "LLMs can't jump" by Tom Zahavy of Google DeepMind, dated 27 January 2026.
Its argument runs through Peirce's three modes of inference. Modern models do induction — pattern recognition across data — and deduction — deriving conclusions from established premises — well.
Abduction, the intuitive jump that proposes a novel explanatory hypothesis, is the one it says they are structurally incapable of.
The case study is Einstein's seven-year path to General Relativity. The paper's contention is that a model could execute the deductive phase of proving theorems from given premises, but not formulate those premises when observational data is scarce.
Two qualifications matter and are usually dropped in the retelling. Zahavy has publicly clarified this is a personal position paper rather than DeepMind's institutional view. And the scope is scientific invention, not general task performance.
The honest summary is narrower than "DeepMind says move beyond LLMs," and considerably narrower than "reasoning architectures instead of next-token prediction."
Does that limitation matter for a hospital deploying AI today?
Not directly, and conflating the two produces bad procurement decisions.
A clinical decision-support tool that surfaces a wrong drug interaction is not failing because it cannot originate a new physical theory.
It is failing at retrieval, grounding, or evaluation — the answer was not checked against a current, authoritative source the health system controls.
Those failures are addressable with today's architecture: grounded retrieval against a formulary the institution maintains, guardrails that refuse rather than guess, human review at the point of action, and audit records that let a pharmacist reconstruct what the system saw.
That is why the 95% of enterprise AI pilots that MIT's Project NANDA found delivered no measurable P&L impact traced to data foundations and workflow gaps rather than model quality.
So the paper is not a reason to delay clinical AI. It is a reason to doubt anyone who tells you the current architecture is the final one.
Why does where a clinical model runs matter more than which model it is?
Because model choice has a shorter half-life than clinical workflow.
If credible researchers are arguing the dominant architecture has a ceiling, then whichever model a health system standardizes on this year is a temporary occupant.
Meanwhile the workflow it is embedded in — triage, documentation, prior authorization, care coordination — will outlive several model generations.
That asymmetry decides the architecture. A deployment coupled to one vendor's API converts every model change into a migration: re-integration, re-validation, re-negotiation.
There is a second reason specific to healthcare. PHI moving to a third party requires a BAA and a trust relationship for every processor in the chain.
A model swap on hosted infrastructure means re-running that review; a model swap inside your own perimeter does not move PHI anywhere new.
| When the better model ships | Hosted, single-vendor | Model-agnostic, self-hosted |
|---|---|---|
| Switching effort | Re-integration project | Configuration change |
| PHI review | New processor, new BAA | PHI never left the perimeter |
| Clinical revalidation | Required, on vendor's timing | Required, on your timing |
| Cost at 8,000 clinicians | Per seat, scales with headcount | Usage-based or flat license |
How should a health system choose an AI architecture that survives model change?
Optimize for replaceability rather than for this quarter's benchmark leader:
- Require model-agnostic routing. If swapping the underlying LLM is a code change rather than a configuration change, the platform has made a bet on your behalf.
- Keep PHI inside the perimeter. Inference where the data already lives removes the third-party custodian rather than papering over it with an agreement.
- Pin and record versions. Clinical validation means reproducing behaviour; a silently upgraded model makes that impossible.
- Log tool calls, not just conversations. The action creates the obligation, so the tool call is the record that matters at review.
- Price it at full clinician count. Per-seat licensing prices the org chart rather than the work.
Where ibl.ai fits
ibl.ai is the agentic AI platform where you own all the code and the data.
You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.
For a health system that means PHI never reaches a third-party processor, the audit trail belongs to the institution, and next year's better model is a configuration change rather than a migration.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
Related: Self-Hosted AI Agents for Healthcare · Healthcare AI Reference Architecture · Model-Agnostic AI: The Real Risk Is Vendor Lock-In