Skip to main content

Weekly Brief

New this week

September 28 – October 4, 2026

Published Tuesday, October 6

The governance gap is now an ownership gap: AI agents are running in production that no named human is accountable for, while the cheapest attack on health systems is still a phone call to the help desk.

What health system leaders said this week, drawn from conversations with Sarah Richardson, John McDaniel, Drex DeFord and Christopher Tyne.

Dominating the week

  • Agentic AI ownership
  • Help desk identity verification
  • Epic Orchard for rural systems
  • Proving AI value

What they’re talking about

Agentic AI is already in production without IT's knowledge, so the governance question has shifted from policy to named ownership.

A survey of 250 leaders found 28% already run agentic AI in production and 44% are piloting, while 72% admit tools or agents were deployed without formal IT approval — and a separate figure showing 86% confident they can govern AI looks hollow against the fact that most organizations lack a current AI inventory. The proposed fix is to treat every agent like an employee: an identifiable human owner accountable for its access and actions, with authentication (who it is) separated from authority (what it may do). At Trinity Health, that accountability is concentrated in an AI council spanning CIO, CEO, COO, CSO, CMIO and physicians, where the CIO holds personal veto power over any deployment.

Scattered Spider's hospital breaches required no exploit — just a help desk employee who skipped verification under pressure.

The group's core method was vishing: calling help desks impersonating locked-out employees to get passwords reset or MFA prompts approved, and it was used against hospitals including some of the largest U.S. health systems as far back as 2024. Prosecutors tie at least a dozen companies and 29 victims to the crew, with single incidents netting $6.3M and $1.7M. The test for leaders is not whether the verification policy exists but whether staff actually follow it when a caller claims to be a clinician in urgent need.

AI value claims should be judged on whether the fix was measured, not whether the demo worked — and workflows resist generalization more than vendors admit.

The useful vendor test is a three-stage demand: flag the problem, recommend the specific fix, then measure whether the fix actually resolved it. Generic tooling breaks on clinical specificity — off-the-shelf ambient scribing misreads medication names and can't separate patient from physician speech, and a single Coumadin refill-check workflow needed 100–200 distinct checks against 30–40 for typical medications, forcing a separate product line. Trinity's counterpoint is that administrative AI pays reliably: pre-implementation revenue cycle analysis found roughly $36 million a year in undercoding, and ambient documentation is projected to add $5–$10 per encounter in captured reimbursement.

Epic's new Orchard model puts a rural system on Foundation with Epic managing third-party contracts and upgrades — and the hard prerequisite is data, not software.

Trinity Health in Minot, North Dakota is the first acute care system on Orchard, a SaaS-driven Foundation variant built for smaller systems without implementation bench strength. Getting there required 13 rounds of data cleanup during the Workday implementation to resolve fragmented and duplicate legacy records, plus a data lake and named data owners who must approve any change in their domain; duplicate medical record rates are now under 2% ahead of go-live. Selection skipped the traditional RFP: vendors spent weeks embedded in departments before proposing anything, and 300-plus staff — about 10% of the organization — produced a 97.9% preference for Epic.

Every point above comes from something a named leader said on one of our shows or wrote for us during the week of September 28 – October 4, 2026. It is a record of those conversations, not a survey of the industry.

229 Signal

Clear the noise

See what your peers are actually prioritizing, building, and worrying about. No vendors. No analyst spin.

Join 229 Signal
Example 229 Signal report: "Not enough capacity. To build what they want." Competing priorities lead friction points at 54%.