The Endgame, Part II: Why Entities Hit a Ceiling

Every organizational model in this series was designed to solve a coordination problem. Every one of them created a new boundary instead.

Last week I laid out three possible futures for healthcare organization. This week I want to explain why the first two can’t finish the job, and what I’ve seen happen when organizations try.

The Cycle

The history of healthcare organization follows a repeating pattern:

A coordination failure causes harm or waste. A new organizational model is created to fix it. The model succeeds. And in succeeding, it creates a new boundary that causes a different coordination failure. That failure generates the next model.

The IPA solved the problem of solo physicians having no negotiating power. It created a new problem: each practice kept its own EHR, its own workflows, its own culture. The IPA could negotiate collectively but couldn’t coordinate care across its members.

The IDN solved that by putting everything under one umbrella. But it created the fortress problem: patients inside the system get coordinated care. Patients who see one specialist inside and another outside fall into a gap the IDN wasn’t designed to bridge.

The ACO solved the problem of fee-for-service rewarding volume. But it created the attribution problem: patients are assigned based on where they saw their PCP, yet they can walk into any provider they want. The ACO is accountable for costs it can’t fully control.

Every model solves the last model’s problem and generates the next. Nobody designed it this way. Because the root cause isn’t any specific organizational failure. The root cause is that organizations have boundaries, and patients cross them.

Why Ownership Can’t Finish the Job

The vertical integrators represent the most aggressive attempt to break this cycle. Eliminate boundaries by making everything one company.

The math that breaks it: over one million practicing physicians in the U.S. Optum has roughly 90,000. Add every other vertically integrated system and you’re covering maybe 15-20% of the market. The solo doctor in rural Ohio, the three-physician group sharing a lease, the critical access hospital that’s the only facility for 50 miles — vertical integration doesn’t reach them.

Then there’s something you don’t see from the outside: integration on paper doesn’t mean integration in practice. I’ve watched a large system acquire a physician group and spend two years unable to get them onto the same EHR instance. Same corporate parent, same IT budget, same stated goals. Two years of interface meetings, data migration plans, and workflow redesign, and the acquired group was still faxing referrals to the hospital across the street that they technically now shared an org chart with. Ownership doesn’t automatically produce coordination. It produces the authority to coordinate. The execution is a different problem entirely.

Why Federated Networks Can’t Finish the Job

CINs, ACOs, and IPAs represent the collaborative alternative. Don’t merge. Align. Share data, follow protocols, split savings.

Three structural weaknesses that I haven’t seen anyone overcome permanently:

The governance problem. Every decision is a committee discussion among parties with different economics. A hospital system and an independent physician group don’t naturally agree on anything. I sat in a CIN governance meeting where the independent physicians voted against adopting a shared care management protocol because they believed (correctly) it would increase their administrative burden without proportionally increasing their share of the savings. The protocol was clinically sound. The incentive math wasn’t. The protocol died. That’s federated governance in a sentence.

The durability problem. Networks degrade. The physician champion retires. The health system anchor gets a new CEO who prioritizes employed growth over network maintenance. The shared savings pool has a bad year. I’ve seen a CIN go from 90% physician engagement to a contracting shell in 18 months after a leadership transition. Nobody quit. They just stopped showing up to meetings, stopped following protocols, and stopped believing the investment would pay off.

The depth problem. This is the most important one. Federated networks coordinate what their members agree to coordinate. Quality reporting. Care gap closure. Some utilization management. It almost never extends to behavioral health integration, post-acute coordination, or social determinant interventions, because those require capabilities and data that individual members don’t possess.

An ACO can tell you that a patient was readmitted within 30 days. It usually can’t tell you she was readmitted because she couldn’t afford her medications, was managing untreated depression, and had no one at home to help with wound care. The data exists, scattered across the PBM, the behavioral health carve-out, the hospital social worker’s notes, and the home health intake form. No federated network I’ve been part of synthesizes all of that in real time.

Why Previous Platforms Failed

The skepticism is earned. Let me engage with it directly.

Google Health launched in 2008 to let patients aggregate their own data. Shut down in 2012. Nobody used it because patients don’t want to manage health data. They want someone to manage their health.

Haven. Amazon, Berkshire Hathaway, and JPMorgan. Three of the most operationally capable companies in the world. Dissolved in 2021 with nothing to show for it.

The consistent pattern: technology overlaid on the existing system without changing incentives, relationships, or workflows. A portal nobody logs into. A dashboard glanced at weekly. An interoperability standard technically implemented and practically empty.

I’ll add one more failure mode that doesn’t get discussed enough: I watched a 14-site CIN deploy a care coordination platform designed to reduce readmissions. Six months in, readmissions hadn’t moved. Care manager burnout was worse. The platform was working exactly as designed — it surfaced thousands of care gaps nobody knew existed. Missed screenings, lapsed referrals, unfilled prescriptions, overdue follow-ups. The problem wasn’t the technology. The problem was that the organizational model couldn’t absorb the answers fast enough. Twelve care managers can’t act on 9,000 alerts. The platform found the problems. The humans were drowning in them.

That experience changed how I think about this. The technology layer isn’t just a detection system. It has to act, not just alert. And it has to act at a scale that human-only care management teams can never reach.

What Changed

Two things happened simultaneously.

AI can now engage patients directly in natural language, at scale, continuously. Not a portal. Not a decision tree. A conversational intelligence that can call a patient after discharge, understand they sound confused about medications, detect an unfilled prescription, notice a missed follow-up, and take action. Not just surface an alert for a care manager to handle on Tuesday. Act. This was not possible at a useful quality level before 2023.

Healthcare interoperability finally has plumbing that works. FHIR APIs are mandated. TEFCA is establishing national data exchange. CMS requires payers to share data programmatically. The data is still messy, still incomplete. But for the first time there are standard pipes instead of fax machines.

AI that can act on information, plus information that can be accessed programmatically. That combination creates the precondition for an intelligence layer that coordinates care across organizational boundaries without requiring those organizations to merge, affiliate, or even agree to coordinate.

The Honest Complication

I’d be dishonest if I framed this purely as an incentive problem, as if health systems and payers are strategically refusing to build the care layer because it threatens their boundaries. Some of that is real. An IDN that builds a layer coordinating care seamlessly across its own facilities and its competitors’ has made its organizational boundary less valuable.

But the more common reality is less dramatic and more frustrating: most health systems and payers are already trying to build this. They’re spending millions on care management platforms, population health tools, and patient engagement technology. They want coordination. They’re failing at it — not because they lack willingness, but because the technology until recently wasn’t capable enough, the interoperability wasn’t there, and the organizational complexity of deploying these tools across fragmented provider networks is genuinely, brutally hard.

The ceiling isn’t just strategic reluctance. It’s operational reality. And the platform that breaks through will have to be not just technologically superior, but operationally humble enough to work within the mess rather than pretending the mess doesn’t exist.

I’ve spent 42 posts describing how the healthcare system is organized. I haven’t yet described what needs to exist for the person the system was built to serve.