Dr. Douglas Won: Vertical Integration Only Works When Designed for Flow

 By Dr. Douglas Sung Won, MD

Vertical integration has become one of the most frequently cited strategies in modern healthcare, yet it is also one of the most poorly understood. Too often, it is framed as a growth tactic - an exercise in acquisition, ownership, or consolidation. Clinics are added, imaging is internalized, surgical facilities are brought under one umbrella, and rehabilitation is folded into the enterprise. On the surface, this appears integrated. In reality, it often is not.

Ownership is not integration. Proximity is not continuity. And scale, without design, frequently amplifies the very fragmentation it is meant to solve.

True vertical integration succeeds or fails on one principle alone: flow.

When I speak about flow in healthcare, I am not referring to efficiency in a narrow operational sense. I am referring to the uninterrupted movement of patients, information, decision-making, accountability, and recovery across an entire care ecosystem. Flow is what determines whether a system behaves as a coherent organism or as a loose collection of parts.

Throughout my career, including my work building vertically integrated systems such as Lumin Health, I observed a consistent pattern. Integration efforts that began with assets struggled. Integration efforts that began with architecture endured.

Healthcare evolved historically as a series of discrete functions. Primary care developed independently of specialty care. Imaging evolved as a separate domain. Emergency services followed their own logic. Surgery became centralized in facilities optimized for episodic intervention. Rehabilitation was often externalized entirely. Each segment matured in isolation, optimizing its own metrics, incentives, and workflows.

The patient, however, never experienced care in pieces. The patient experienced the system as a whole.

When vertical integration is approached through acquisition alone, these silos remain intact beneath a common brand or balance sheet. Information still stalls at boundaries. Decisions still require translation. Accountability still dissolves during transitions. The system grows larger, but it does not become more intelligent.

Flow is what resolves this tension.

Designing for flow means beginning not with ownership, but with the patient journey as a continuous system. It requires asking how a clinical question moves from first presentation to resolution without unnecessary friction. It requires aligning diagnostic pathways, intervention planning, surgical execution, recovery, and follow-up into a single narrative rather than a sequence of handoffs.

This cannot be accomplished through coordination alone. Coordination attempts to manage fragmentation after it exists. Architecture prevents fragmentation from emerging in the first place.

At Lumin Health, vertical integration was treated as a design discipline rather than a business tactic. Before expanding footprint or adding capacity, we focused on how care would behave at scale. How would information propagate across facilities? Where would decision authority live? How would escalation occur when complexity increased? How would recovery be embedded rather than appended? How would incentives reinforce continuity rather than throughput?

These questions shaped structure. Structure shaped behavior.

When flow is designed intentionally, integration stops feeling like management and begins functioning like physics. Care moves naturally. Delays compress. Redundancies disappear. Clinicians gain clarity rather than administrative burden. Patients experience progression rather than navigation.

This is the difference between a vertically integrated system and a vertically owned one.

Flow also determines resilience. As healthcare systems face accelerating pressure—from workforce constraints to regulatory complexity to technological disruption—fragmented structures become brittle. Each interface becomes a potential failure point. Each handoff introduces risk. Each delay compounds cost.

A system designed for flow absorbs stress. It adapts without fracturing.

This is why vertical integration must be architectural before it is operational. It must be engineered before it is expanded. Without that foundation, integration becomes accumulation, and accumulation becomes entropy.

As Dr. Douglas Sung Won, MD, my work as a Healthcare Systems Architect consistently returns to this principle. Vertical integration is not successful because assets are owned. It succeeds because behavior is designed. When flow is treated as the primary objective, integration becomes a tool for continuity, quality, and sustainability.

Without flow, vertical integration is simply complexity under one roof.

With flow, it becomes a living system.

Get to know me a little more here:

https://www.instagram.com/drwonmd/

https://www.facebook.com/DrWonMD/

https://solo.to/drdouglassungwon

https://www.f6s.com/member/dr-douglas-sung-won

https://drdouglassungwon.stck.me/profile

https://drdouglassungwon.blogspot.com/

https://www.patreon.com/cw/drdouglassungwon