The Short Answer
Clinical AI is arriving faster than hospitals can govern it: 950 agents found a novel enzyme system in 21 hours, and the FDA approved the first AI margin-assessment device in March. Ban or license, both assume you can observe the model. On ibl.ai you own all the code and the data.
The debate about clinical AI has been about whether the models are good enough. That question is closing. The one underneath it — whether a hospital can see what the model is doing — has barely been asked.
How fast is clinical capability actually moving?
Fast enough that the recent examples are qualitatively different from the last decade's.
On 23 September 2026 Anthropic released a preprint reporting that roughly 950 Claude agent sessions, running for 21 hours and consuming 210 million tokens, surveyed 1.9 billion protein clusters, recovered about 200,000 reverse transcriptases, and surfaced a previously unknown enzyme system it calls ART — array-associated reverse transcriptases, found mostly in bacteriophages.
Anthropic presents it as early results from one of its first research programs, and says the work would have taken an expert scientist weeks or months.
Worth stating the limits as clearly as the result. The function of the system itself is not yet known — not merely the accessory protein's — and whether it is useful for gene editing is undetermined.
Dario Amodei has acknowledged that a Stanford team previously described a system similar in some ways to this one, so "previously unknown" is doing careful work.
It is not purely computational, though: the preprint reports that ART arrays are highly expressed and appear as discrete units during Staphylococcus phage infection.
Expression was confirmed at the bench; function was not. A strong demonstration of search at scale, not a validated therapy.
On 3 March 2026 the FDA granted premarket approval to Claire, from Perimeter Medical Imaging AI — the first AI-enabled imaging device approved in the United States for intraoperative breast cancer margin assessment.
It images the excised lumpectomy specimen during surgery, not tissue in the patient.
Its pivotal trial reported 88.1% margin accuracy and a statistically significant reduction in patients with residual cancer against standard of care.
Repeat surgery occurs in about 20% of breast-conserving surgeries in the US, against roughly 300,000 breast cancer surgeries a year.
In August 2026 Intermountain Health became the first US health system to deploy it commercially, at LDS and American Fork hospitals. Five months from approval to an operating room is fast for a class III device.
So what is the bottleneck now?
Deployment, and then something harder than deployment.
The deployment part is documented. In a February 2026 survey of 120 US health systems, 75% were using or planning to use at least one AI application.
The share implementing or planning three or more AI solutions rose from 30% to 59% — a 67% year-on-year increase. Respondents named slow implementation timelines among their challenges.
That is a real drag, and it is the one most people name. But a slow procurement cycle is a solvable problem — budget, staffing, integration work. The constraint underneath it is not.
What is the constraint underneath it?
You cannot govern a model you cannot observe.
When clinical AI runs on a vendor's cloud, four things are outside the hospital's control at once:
| Question a quality committee must answer | Vendor cloud | Self-hosted |
|---|---|---|
| Which model version produced this recommendation, on this date? | Knowable if you pinned it — several platforms let you | A version you pinned |
| When did the weights last change? | On the vendor's schedule, with notice — until the version retires | When you decided |
| Has behaviour drifted since validation? | Measurable only from outputs | Measurable against a fixed artefact |
| Can you reproduce the decision a year later? | Only if the vendor retained it | Yes |
Be fair to the managed platforms first, because the absolute version of this claim is wrong.
Azure lets a deployment opt out of automatic model upgrades, exposes the current version through the portal and API, gives at least two weeks' notice before a default moves, and keeps the previous major version until its retirement date.
ONC's HTI-1 rule goes further, requiring certified health IT to disclose the update and validation schedule for predictive decision support.
So versions can be pinned and changes can be announced. What ends is the pinning: a retired version is gone, and with it the ability to re-run a case as it ran.
And the regulated case is not the clean exception either. Claire's own PMA authorises a predetermined change control plan covering "planned AI enhancements that can be implemented without additional FDA interaction." That is good regulation — the changes were reviewed in advance and are bounded — but it means an approved class III AI device also updates without a fresh submission, on a schedule the hospital does not set.
That is the sense in which "ban it" and "license it" answer a narrower question than they appear to. Both assume you can see what the model is doing well enough to decide whether it is acceptable.
Prohibition does not need observability because nothing is deployed. Licensure absolutely does — and licensing a service whose behaviour changes on a schedule you do not hold licenses a moving target.
Isn't this an argument against clinical AI generally?
No, and it would be a bad one. Repeat surgery after one in five breast-conserving operations is a real harm, and Claire's trial showed a statistically significant reduction in patients left with residual cancer.
The company puts the re-operation benefit as potential rather than measured. Either way, a hospital that refuses AI on principle is choosing the status quo.
The argument is about where the model runs, not whether it runs. An institution can adopt aggressively and still insist on three things: a version it controls, logs it holds, and the ability to reproduce a decision for a morbidity and mortality review or a malpractice claim.
Those are ordinary clinical governance expectations. They are only difficult when the model is somebody else's service.
What does a hospital need in place before it scales?
Four things, and none of them is a model choice:
- A pinned version — the artefact you validated is the artefact in production, and changing it is a decision with a date and a signature.
- Logs you hold — inputs, outputs, model version and the clinician who reviewed it, in your systems.
- Drift measurement against a fixed baseline — not vibes, and not the vendor's dashboard.
- Reproducibility — the ability to re-run a case as it ran then, years later, because that is the window in which claims arrive.
Why does ownership decide all four?
Because every one of them is a property of where the model lives.
On ibl.ai you own all the code and the data. The platform runs under a perpetual licence inside the hospital's own perimeter, so the model version, the inference logs and the audit trail are institutional records rather than a vendor's telemetry.
It is model-agnostic, which is what makes the pinning real: a health system can run an open-weight model entirely inside its own network, upgrade on its own schedule, and keep the prior version available for reproduction.
Pricing is usage-based with no per-seat pricing, and you can deploy anywhere: your cloud, your VPC, on-premise, or fully air-gapped.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
A stethoscope does not get a firmware update. Clinical models will, including the approved ones — so the governance question was never really about the model. It is about who holds the version, the logs, and the ability to reconstruct the day.
Sources: the enzyme discovery from Anthropic's announcement, its preprint and TechCrunch; Claire's approval, PCCP, indications and the re-excision figure from Perimeter's approval release, and the first deployment from its Intermountain release; the change-control pathway from FDA's PCCP guidance; version pinning from Azure's model-version documentation; adoption figures from Eliciting Insights' 2026 AI Adoption Survey.
Related: AI Agents Do Licensed Work. Liability Law Doesn't Fit. — the ban-versus-license split in detail, and why three liability doctrines all miss.