Innovaccer bets $250M on outcome pricing 💰, Abridge goes beyond the scribe 📚, AI gets its first cardiac billing code 🫀

Innovaccer Commits $250M to Agentic AI — and Bets the Pricing Model on Actually Delivering

Innovaccer announced a $250 million, three-year investment to expand its agentic AI platform across five healthcare workflow categories: patient access, value-based care, revenue cycle, risk and quality assessment, and utilization management. The platform runs on Innovaccer’s “Gravity” data layer — a unified integration of EHRs, claims, CRM, and finance systems — which enables end-to-end agent workflows that can touch multiple data sources in a single task. Major customers include Kaiser Permanente, Ascension, Trinity Health, and Banner Health.

The money is interesting. The pricing model is the story. Innovaccer is adopting outcome-based pricing: the system charges per successful task completion, not per software license or per seat. CEO Abhinav Shashank put a number on it: “If something is costing you $100 to do from a manual process perspective, we will price it at $20.”

This lands the same week PHTI published a report warning that AI-driven automation is creating “bot wars” — provider AI upcoding documentation while payer AI downcodes and denies, with no net cost reduction for the system. And a Qventus survey of 60+ health system executives found that 70% want a single comprehensive AI partner managing multiple use cases, but only 11% currently have one. Only 4% have achieved scaled AI with measurable outcomes.

😤 Haters

“250M over three years is a marketing number. It’s the R&D budget they were going to spend anyway, repackaged as a commitment.” Probably. Most “X investment in AI” announcements are relabeled operating budgets. But the outcome-based pricing is not a relabeled budget — it’s a structural change to the revenue model. If Innovaccer’s agents don’t complete the prior auth, you don’t pay. That’s a bet, not a press release. Whether the agents are good enough to make that bet profitable is the thing to watch.

“Outcome-based pricing sounds great until you realize ‘successful task completion’ is defined by the vendor, not the customer.” This is the exact right skepticism. If “successful” means “the agent ran to completion” rather than “the prior auth was approved” or “the patient got the referral,” the pricing model is cosmetic. The question for any health system evaluating this: what’s the definition of success, and who adjudicates disputes?

“One platform to rule them all is how Epic became Epic. Innovaccer is trying to build the next lock-in.” Fair. And the Qventus data suggests health systems will walk into that lock-in willingly — 70% actively want a single AI partner. The lesson from the EHR era is that integration convenience creates switching costs. The question is whether this generation of CIOs remembers that lesson or learns it again.

💡 80/20: The PHTI bot-wars critique is the backdrop. Innovaccer’s outcome-based pricing is the response. For clinician-builders, the signal is that “per-seat” AI pricing is going to come under pressure from vendors willing to bet on outcomes. If you’re building an AI tool for a health system, think about what outcome you’d be willing to guarantee — and what that guarantee would cost you if the agent fails. Try: pick one workflow your tool automates. Define “successful completion” from the customer’s perspective, not yours. If you can’t price against that definition, you don’t understand the workflow well enough yet.

→ Full write-up

---

📡 Builder’s Radar

Abridge Partners with NEJM and JAMA — The Scribe Company Is Now a Clinical Intelligence Platform

Abridge announced multi-year partnerships with NEJM Group and JAMA Network to embed peer-reviewed clinical evidence directly into EHR workflows. The integration lets clinicians ask clinical questions and receive answers grounded in both the medical literature and the patient’s own chart context — without leaving the EHR. This builds on Abridge’s existing clinical decision support partnership with Wolters Kluwer’s UpToDate, which is already live. Abridge now projects supporting over 100 million patient-clinician conversations this year across 250 of the largest US health systems.

😤 Haters

“This is a content licensing deal dressed up as a product launch. UpToDate has been doing CDS for decades.” The product isn’t the content — it’s the context. UpToDate answers generic clinical questions. Abridge answers clinical questions in the context of the specific patient conversation that just happened. That’s the gap between a search engine and a clinical copilot. Whether the context-awareness actually improves clinical decisions is an empirical question nobody has published on yet — but the architecture is different from what existed before.

“Ambient scribing is commoditizing. Abridge is pivoting because the core product is getting squeezed.” Partially true, and that’s exactly the right read. The scribe is becoming table stakes. The valuable layer is what sits on top of the transcript — coding, CDS, quality measures, referral suggestions. Abridge is building that layer. Whether they win it depends on execution, not on the NEJM logo.

💡 80/20: The scribe wars are over. The CDS-on-top-of-the-transcript war is starting. If you’re building anything that consumes clinical conversation data — coding audits, quality reporting, care gap detection — the integration surface is about to get much richer. Try: look at one clinical question you answered today by opening UpToDate in a separate tab. Ask: what if the answer had shown up inside the note, grounded in this patient’s context? That’s what Abridge is building toward.

→ Full write-up

---

CMS Creates a National Billing Code for AI Cardiac Calcium Detection — The Reimbursement Proof Point Is Here

Bunkerhill Health secured both FDA clearance and a new CMS national billing code for AI algorithms that detect coronary artery and aortic valve calcium on routine contrast-enhanced chest CT scans. Effective April 1, 2026, the billing code creates a reimbursement pathway under the Hospital Outpatient Prospective Payment System (OPPS). The algorithms — developed through a research consortium including UCSF, Emory, and MedStar Health — are the first cleared to analyze calcium on contrast-enhanced CTs, which are already being performed for other reasons. A paired STAT piece frames the scale: 19 million chest CTs are performed annually in the US, and 20-40% of incidental calcium findings currently go unreported.

😤 Haters

“One billing code for one company doesn’t change the FDA-to-reimbursement pipeline for everyone else.” True as a general statement. But the existence proof matters. Every cardiac AI startup pitching investors has been asked, ‘But will CMS pay for it?’ Now there’s a specific answer: this company, this algorithm, this code. The pathway exists. That changes the risk calculus for every subsequent entrant.

“Opportunistic screening on existing CTs sounds efficient until the follow-up costs hit — who pays for the cardiology referral the AI triggered?” The payment question is real and unanswered at scale. The algorithm detects calcium. The health system then has to decide what to do with that information — and the downstream cardiology workup isn’t free. But 20-40% of incidental findings going unreported means patients are walking around with undetected cardiovascular risk right now. The cost question is legitimate. The clinical question already has an answer.

💡 80/20: This is the clearest example yet of an AI algorithm getting both regulatory approval AND a payment mechanism. If you’re building clinical AI, study the Bunkerhill pathway: FDA clearance + CMS billing code + opportunistic screening on existing imaging. The formula is “find the scan that’s already happening, add an analysis layer that catches what humans miss, and get paid for the analysis.” Try: think about what data your patients are already generating — lab panels, imaging, vitals — where a second-pass AI analysis could catch something that’s currently being missed. That’s the Bunkerhill pattern.

→ Full write-up

---

What are you building this week? Reply and tell me — I read every one.

— Kevin