OpenAI's Head of Health AI: Medical Intelligence Costs Are Collapsing, But Savings Come from Workflow Integration, Not the Model Itself
Karan Singhal, OpenAI’s head of health AI research, outlined the core logic of the company’s healthcare strategy in a podcast with Andreessen Horowitz (a16z): health intelligence should be embedded within general-purpose frontier models rather than standalone medical ones. The latest model costs are 34 times lower than the previous month’s flagship, but Singhal argues that compressing the United States’ $5.3 trillion healthcare expenditure will not come from intelligence itself, but from workflow integration. He explicitly draws a boundary—OpenAI acts as the “front door” and “quarterback,” not a care provider. For investors, this signals that the value source for healthcare AI is shifting from model capability to workflow ownership.
Karan Singhal, OpenAI’s head of health AI research, explained the underlying logic of the company’s healthcare strategy to partner Jay Rughani on the a16z podcast. This logic rests on an counterintuitive core judgment: the cost-saving mechanism of healthcare AI does not lie in models becoming smarter, but in workflows being redesigned.
Singhal provided specific cost evidence. He stated that GPT-6 Luna is OpenAI’s cheapest frontier model on its API, scoring higher on HealthBench Professional than GPT-5.6 Sol—the latter was the company’s best model just a month ago—while costing only one-thirty-fourth of the latter’s price. He expects the cost of a fixed level of health intelligence to continue plummeting, while the trust threshold continues to rise.
But Singhal immediately made an uncommonly honest cut in the industry. He said, 'I don’t think health intelligence has yet had a macro effect on the problem you’re describing.' US healthcare spending exceeds $5.3 trillion, and ChatGPT has over 300 million weekly users asking health questions, but Singhal clearly pointed out that abundant health intelligence is merely a prerequisite for compressing expenditures, not a sufficient condition; true compression comes from integration, workflows, deployment, and scaling.