Yale New Haven Picked Rad AI Over PowerScribe One

Note: This post was written by Claude Opus 4.8. The following is a synthesis of company announcements and industry reporting.

When Microsoft began mailing end-of-life letters to PowerScribe 360 customers this spring, the conventional read was straightforward. Small and independent radiology practices might shop the market, but large multi-hospital systems would almost certainly migrate to Microsoft’s successor product, PowerScribe One — because at that scale the switching costs make staying the path of least resistance. Thousands of templates and macros, years of radiologist muscle memory, deep integration with the PACS and the EMR: that kind of institutional investment is hard to walk away from. This month, Yale New Haven Health — a major Connecticut health system anchored by a nationally ranked academic medical center — complicated that read.

What Yale actually did

On June 10, Yale New Haven Health announced it is deploying Rad AI’s reporting platform across its imaging network — five hospital campuses and more than sixteen outpatient imaging centers, a network that reads north of 700,000 radiology exams a year. Rather than upgrade to PowerScribe One, the system, in its executives’ words, “chose to look for a new radiology reporting partner.”

The reasoning is the part worth sitting with. “It’s a completely different product,” said Melissa Davis, MD, Yale’s vice chair for imaging informatics, of the forced move to PowerScribe One. “That allows us to actually have room to take a step back and say, ‘Is this the product that we want, or do we want to explore something different?’” Christopher Whitlow, MD, PhD, the system’s radiologist-in-chief, framed the choice as needing “a true co-development partner, capable of building alongside us” rather than an off-the-shelf vendor.

Concretely, Yale is rolling out Rad AI’s Impressions tool — which drafts a report impression from a radiologist’s dictated findings — alongside the company’s reporting product, in a phased deployment. The system reports a 12% efficiency gain in the first week. That figure is self-reported and early, the kind of number every pilot produces, so it is worth holding loosely. But the direction is unambiguous: a flagship academic system treated a forced migration not as an upgrade to schedule, but as a platform decision to reopen.

Why it counts as a surprise

The expectation that a system Yale’s size would stay put wasn’t unreasonable — it was the switching-cost argument, and it still holds for plenty of practices. What it underweighted is what a forced migration does to those costs. When the incumbent is retired out from under you, the question shifts from “how do we upgrade” to “is this even the platform we want” — and that second question is one many practices had stopped asking, because PowerScribe simply was the answer. Davis put it directly: “With PowerScribe 360 sunsetting, there’s a big opening for what reporting looks like in radiology at this point, and we wanted to be on the forefront of that conversation.”

Two qualifiers keep the story honest. Yale isn’t replacing its imaging stack — Rad AI is the reporting and impressions layer, not a PACS, and the viewer and worklist are a separate decision. And this wasn’t a cold switch: Davis noted Yale established its relationship with Rad AI “a couple of years ago,” so what landed this month is an expansion to enterprise scale, not a first contact. Even so, scaling that relationship across the whole system at the moment PowerScribe One was the default on the table is a deliberate choice, not a drift.

It isn’t just Yale

Yale doesn’t appear to be an outlier. Since Microsoft’s March announcement, Rad AI says it has seen a fourfold spike in inbound inquiries from health systems, a 72% year-over-year jump in new sales deals, and — the figure that stands out — a 233% increase in inbound forms from organizations explicitly saying they want out of the Microsoft ecosystem rather than upgrade to PowerScribe One.

Those are Rad AI’s own numbers, and Rad AI sells the alternative, so they are marketing as much as measurement. But they track with Yale’s move and with the competitive field that has grown up around radiology reporting — cloud-native, AI-first platforms like RADPAIR and NewVue that barely existed the last time most practices chose one, and that are now openly courting the base PowerScribe is about to displace. A forced migration is the rare moment the whole market gets shopped at once.

What it signals

None of this means PowerScribe One is in trouble. It is a genuinely improved product — cloud-based speech recognition without profile training, AI-assisted impressions, ambient dictation — and most large systems, with their template libraries and deep integrations, will still take it. The gravity is real. The correction is narrower: “large health system” is not a synonym for “stays on Microsoft,” and the assumption that a forced migration is a settled outcome rather than an open one just took a visible hit.

For the radiology practices and health-system IT teams now planning their own moves against the August 2026 renewal cutoff and 2027 end-of-support dates, Yale’s decision is not a template to copy. The efficiency numbers are self-reported. And “co-development partner” cuts both ways: Yale gets a vendor that will build custom functionality for it over time, and Rad AI gets a marquee academic system to co-develop with — the companies plan to pair the vendor’s documentation automation with Yale’s clinical research expertise. For an established product, a flagship academic deployment is a flywheel for the vendor as much as a tool for the buyer. That doesn’t make it the wrong call — it means the deal is doing more than one thing, and anyone weighing the same move should price that in.

The migration was always going to be forced. Whether “forced” also means “predetermined” is the question Yale just reopened.

What Yale actually did

Why it counts as a surprise

It isn’t just Yale

What it signals

Sources

Security Scorecard