California County's Healthcare IT Chief Charts A Course To Reduce AI Technical Debt

For healthcare leaders, AI promises to solve many of the industry’s most persistent challenges: physician burnout, operational inefficiencies, and declining revenue. Yet in the rush to adopt it, many are discovering a troubling side effect. Each new AI layer adds fragility on top of legacy systems. Now, the resulting technical debt threatens to slow the very transformation this technology promises.

To understand the actual cost of AI in healthcare, we spoke with Khalid Turk, Chief Healthcare Information Technology Officer for the County of Santa Clara, one of the largest public health systems in America. Here, he leads a team of over 250 professionals, managing IT operations across four hospitals and more than 20 clinics serving 14,000 users. Before becoming a CHIO, Turk was a software engineer writing the very code that holds his hospitals together. His experience with large-scale EMR integrations and digital transformations enables Turk to see AI as both a strategist and an engineer.

• An inevitable debt: The very speed of AI's evolution is the source of this new debt, Turk explained. When technology advances at an unprecedented pace, today's cutting-edge solution becomes tomorrow's legacy problem, seemingly overnight. "With AI, we are introducing technical debt for ourselves for the future. Technical debt is the long-term cost of choosing an easy solution now instead of using a better approach that would take longer. Because AI is evolving so fast, many of the systems we're implementing today won't be able to scale or transform readily tomorrow."

The decision to incur this debt is not arbitrary, Turk continued. Instead, it's a direct response to one of three critical business pressures. "The drive to adopt AI isn't random. Is your goal to increase revenue? Is it to improve efficiency and reduce provider 'pajama time'? Or is it to create better patient engagement? Your AI strategy will be completely different depending on which of those one, two, or all three problems you're trying to solve."

• Wrappers on wrappers: Often, these solutions are just "wrapper" technologies layered on top of aging, inflexible systems, Turk cautioned. The result is a form of "institutional debt" that emerges through vendor lock-in. For example, he pointed to the market’s dominant EMRs. Because their foundational client-server designs are ill-suited for modern AI, vendors are forced to bolt on solutions rather than integrating them natively, he said. "Most AI in the EMR sphere today is just a wrapper on existing technology. The core systems are often built on older architectures, which do not lend themselves to AI. To compensate, they build a cloud service. An API call goes from the on-premise system to the cloud and back. It works, but it's not a native solution. It's a layer bolted onto a legacy foundation."

• The sunk-cost anchor: Institutional debt makes it especially challenging for large health systems to switch to newer, AI-native systems, Turk said. "Think of it like a $10 million house. Even if you don't like it, the cost to change it is enormous. Over the past 12 years, we've invested nearly $300 million in our system. To let go of that investment, plus all the customization, user training, and familiarity we've built, just to start over with a new product and go through another five-year cycle to make it mature? That is a monumental decision for any organization to make."