Episode 07 · The UpStream Life · Vishal Krishna in conversation with Sudhir Kesavan

US healthcare's structural rewrite — and why it took twenty years.

American healthcare is the largest, slowest, most regulated software market on earth. For two decades it has been quietly migrating from a system that bills for activity to one that pays for outcomes — and the IT stack underneath, the EHRs, the claims engines, the analytics, has had to be rebuilt from inside out. Sudhir Kesavan runs CitiusTech, an eight-thousand-person Indian firm that lives inside that rebuild for US payers, providers, and life-sciences companies. In this conversation he traces why the shift is now accelerating, what AI actually changes at the clinician's desk, and why "Indian healthcare engineering" has finally earned its own name.

Guest Sudhir Kesavan · President & CEO, CitiusTech· Host Vishal Krishna· Length ~46 min· Markets United States · United Kingdom · India (engineering)
Video thumbnail
Understanding US healthcare & why it's on the cusp of change — a view from CitiusTech's Sudhir Kesavan
Embedding off · opens YouTube

In sixty seconds.

US healthcare is the only trillion-dollar industry that still bills the way medieval guilds did — paid per act, not per outcome. That is changing, slowly, and now suddenly faster.

Sudhir's thesis is that the shift from fee-for-service to value-based care is rewriting every system underneath it: the EHRs, the claims platforms, the analytics stacks, the way a clinician spends their day. CitiusTech's bet is that the rewrite is too domain-heavy for generalist IT firms and too long for product start-ups — which is why a specialist services company, run mostly out of Mumbai and Bengaluru, is now sized like a small Cognizant.

The path here took twenty years of HIPAA audits, SOC2 reports, and integration projects that nobody else wanted. The pay-off is that the same teams now sit close enough to clinical workflow to ride the next curve — ambient scribing, FHIR pipelines, and a payer analytics surface that finally has the data to use.

Where to land in the conversation.

Each chapter opens the YouTube video at that timestamp in a new tab.

Five ideas to carry into your own work.

Mental models lifted from the conversation that travel beyond healthcare. Each one is the kind of thing you can quote in a strategy meeting on Tuesday.

01

The unit-of-payment shift

In fee-for-service, the billable atom is the procedure. In value-based care, the atom is the outcome over a window — a member-year, a hospital-readmission rate, a HEDIS measure. Change the atom and every system measuring it has to be rebuilt. EHRs, claims engines, analytics, even the org chart of a provider group.

Whenever a market changes what it is paying for, look two layers down — the rebuild is hiding in the plumbing.
02

Compliance as ramp, not ceiling

HIPAA, HITECH, SOC2, HITRUST — twenty years of audits look from outside like overhead. From inside they are the qualifier. A firm that has passed a hundred audits has built an engineering muscle that no Series B competitor can match. Compliance is the moat once you have already paid for it.

Regulation feels like cost when you are paying it and a moat once you are past it. The lag is the asset.
03

Clinical workflow is the product

An AI tool that saves three minutes is a feature. A tool that re-routes the order of a clinician's day is a product. Ambient scribing didn't win because the transcription was best in class; it won because the note appeared where the doctor was already looking. The product is the workflow, not the model.

When the user is high-status and time-starved, the unit of value is the workflow second, not the feature.
04

Population health as the new analytics surface

Once the unit of payment is the panel, the analytics surface flips from individual encounter to cohort. Who is rising-risk this quarter? Which seventy-five-year-olds are about to be re-admitted? Payers and ACOs need this. Providers need it. The same data, asked a different question.

A new payment model produces a new analytics surface. The first firms that build it own the next decade's dashboards.
05

The AI-augmented clinician

Ambient scribing, prior-authorisation drafting, retrospective coding — none of these replace the clinician. Each gives back time that the system had previously taxed out of them. The right framing is not "AI in healthcare" but "what does the clinician's hour look like a year from now, and what is now in it that was not before."

For high-skill labour, the AI question is always about hours returned, not about tasks automated.

Fifteen things to actually walk away with.

Each one carries the timestamps where the moment lives, and a transferable note for work that isn't healthcare.

01

US healthcare is the slowest software market because it is the most regulated one.

Sudhir's opening frame: there is no other industry where a payment model invented in 1965 still runs the cash flow, an interoperability standard set in 1996 still gates the data, and a coding system from the 1970s still determines whether a claim is paid. Healthcare moves slowly not because it is technically backward but because the regulation underneath every workflow is a thirty-year sediment that nobody can rip out at once.

That slowness is itself a competitive feature — most consumer-software companies cannot tolerate the cadence. The firms that can are the ones that started building inside the regulation rather than around it. CitiusTech is one of those.

Beyond healthcare. Any market whose pace is dictated by regulation has a different selection function on companies than a market whose pace is dictated by consumer demand. Read the speed before you read the size.
02

The fee-for-service to value-based care shift is the structural story.

Sudhir keeps returning to it. Fee-for-service pays a hospital for what it does: every imaging study, every consult, every admission. Value-based care pays it for what happens to a population over a period: the cost of care, the readmission rate, the HEDIS score. Change the unit of payment and you change every system that reports against it. The EHR has to capture outcomes, not just charges. The claims platform has to attribute members to providers. The analytics has to think in cohorts and member-years, not encounters.

The transition is twenty years old in policy and barely ten years old in production systems. Most of the rewrite is still in front of the industry. That is the order book.

Beyond healthcare. When you hear "we are changing the payment model," translate it as "we are rewriting all the software." The first headline is policy. The second is procurement.
03

Three customer pillars: payers, providers, life sciences.

CitiusTech's revenue map is a three-legged stool. Payers — the insurance companies, the Blues plans, the Medicare Advantage runners — need claims engines, member analytics, prior-authorisation automation, and the increasingly heavy machinery of HEDIS and STAR-ratings reporting. Providers — the IDNs, the academic medical centres, the ACOs — need EHR integration, revenue cycle management, clinical analytics, and increasingly the ambient-scribing rails. Life sciences — pharma, medical devices — need real-world evidence pipelines, clinical-trial data infrastructure, and compliance tooling that satisfies the FDA and EMA.

The three pillars do not buy the same software. They buy adjacent skill sets from the same firm. The diversification is the moat: a downturn in payer IT spend is rarely synchronous with life-sciences procurement.

Beyond healthcare. Service businesses that look horizontal are often three or four verticals with shared skills. The thing that travels is the engineering culture, not the product.
04

Epic's moat is workflow, not features.

Roughly two-thirds of US hospital beds run on Epic. Sudhir is precise about why: it is not that Epic's database design or UI is better. It is that an Epic install touches every workflow in the hospital — registration, scheduling, orders, results, billing — and the cost of switching is measured not in licence fees but in retraining tens of thousands of clinicians who learned medicine through that interface. The moat is the muscle memory of a generation of doctors.

That is also why the third-party-app layer above Epic is where the interesting product opportunity lives. Replacing Epic is a fool's errand. Building tools that sit on top of Epic — through its APIs, through FHIR — is a quarter-long integration rather than a year-long migration. CitiusTech lives in that adjacency.

Beyond healthcare. When a system of record has been the daily interface for a decade, its moat is no longer technical — it is muscle memory. The opportunity moves to the layer immediately above it.
05

Oracle Health (formerly Cerner) is the long-pole story nobody is watching.

Oracle's twenty-eight-billion-dollar acquisition of Cerner is one of the largest healthcare-IT deals in history and the press has mostly stopped covering it. Sudhir's read: Oracle is in the middle of replatforming Cerner onto its cloud, rebuilding the data model, and trying to win back the share that has drifted to Epic. Whether that bet pays off shapes the second-most-important EHR in the country for the next decade.

The under-discussed implication is the data architecture. Oracle is the only EHR vendor with a serious bet on cloud-native, FHIR-first design at the foundation rather than as a translation layer. If they pull it off, the analytics ceiling on the Cerner footprint rises sharply. If they don't, Epic keeps consolidating.

Beyond healthcare. The biggest infrastructure migrations are the ones the press loses interest in halfway through. The story is in years three through seven.
06

HIPAA, HITECH, SOC2 — the compliance ramp.

From outside, the alphabet soup looks like overhead. From inside, Sudhir argues, it is the qualifier and ultimately the protection. HIPAA gave the industry its data-handling rules in 1996. HITECH in 2009 forced electronic adoption with carrots and sticks. SOC2 became the audit grammar customers learned to ask for. The result is that any firm doing serious work in US healthcare has been writing the same kinds of attestations and runbooks for fifteen years.

The interesting structural fact is that this turns into a moat in the opposite direction from how it looks. The first audit is expensive. The hundredth is a process. Firms that paid the early cost now compound on it; new entrants discover that compliance-from-scratch costs more than the differentiated engineering work they came in to do.

Beyond healthcare. Compliance is not a moat. Passing audits repeatably is. Build the engineering muscle that makes the fortieth audit cheaper than the first.
07

FHIR is finally tipping, twenty years late.

Fast Healthcare Interoperability Resources — FHIR — is the API standard that lets one healthcare system talk to another. It was meant to fix the absurdity of an industry that could not move a patient's record across the street. For most of its existence FHIR was a slide in a keynote, not a wire-level reality. Sudhir's view is that the last three years have changed that: CMS mandates, the 21st Century Cures Act, and finally an EHR vendor base that ships usable FHIR endpoints have crossed a tipping point.

The downstream implication is large. Once data flows out of the EHR through a standard API, the analytics, the AI, the third-party tools all become unblocked. Twenty years of "data trapped in the EHR" complaints become a transition rather than a permanent state.

Beyond healthcare. When a long-deferred standard finally turns on at scale, the value accrues to the layer above it — not to the standard itself. Watch the toolmakers, not the spec authors.
08

Ambient scribing changed clinical AI from demo to product.

Sudhir is unsentimental about the AI hype cycle in healthcare. Most of what was announced in 2023 was a chatbot bolted onto a clinical workflow nobody redesigned. Ambient scribing — Abridge, Nuance/Microsoft DAX, a handful of others — was different. The model listens to the encounter, drafts the note, files it in the EHR. The clinician sees a finished document instead of typing through dinner.

It worked because it solved the right unit of value. Doctors do not need help reasoning; they need their evenings back. The win is two hours of pajama-time documentation removed from every weeknight. That number is so visible to a clinician's life that the buying decision moves out of IT and into the chief medical officer's office. CitiusTech's bet is that this pattern — AI that returns hours, not AI that replaces tasks — is the template for the next ten years of clinical software.

Beyond healthcare. For high-status, time-starved users — doctors, lawyers, senior engineers — the AI product is the one that returns the most evening hours. Measure in hours, not in features.
09

Population health analytics is the new dashboard war.

Once payment shifts to outcomes over a panel, the question changes. Instead of "did this patient get the right care during this admission," the question is "which of my forty thousand attributed members are rising-risk this quarter, and what is the cheapest intervention that keeps them out of the hospital." That is a different software product. It needs claims, EHR, social determinants, pharmacy fills, and increasingly device telemetry, all stitched and risk-stratified.

Sudhir notes that the analytics surface is unevenly developed. Payers are further along — they have always been data companies in disguise. Providers are catching up under ACO pressure. The interesting middle is the joint venture: payer-provider entities like Optum, Kaiser, the integrated delivery systems, where the data sits on one side of the firewall and the financial accountability on the other.

Beyond healthcare. A new payment model creates a new analytics surface within five years. The dashboard category that wins is built by the firm that has the data plumbing already.
10

Provider burnout is the real design constraint.

One in three US physicians reports burnout at any given moment, and a meaningful share are leaving practice or moving to part-time work. The proximate cause is documentation: hours of EHR clicks per hour of patient time. Sudhir frames this as the most under-appreciated design constraint in the industry. Every new product, every new analytics dashboard, every regulatory check-box adds to a workflow that is already at breaking point.

The reframe is that the best healthcare-IT products of the next decade will be measured by what they remove from the clinician's day, not what they add. Ambient scribing succeeds on this axis. So does prior-authorisation automation. So does retrospective coding. The market for "add another button to Epic" is functionally closed.

Beyond healthcare. When the bottleneck user is burned out, the design brief is subtractive. Each feature you ship has to remove more than it adds, in time, in attention, in cognitive load.
11

CMS rules are the silent product manager.

The Centers for Medicare and Medicaid Services — CMS — sets the cadence of half the industry. Pricing-transparency rules in 2021, the interoperability rule, the No Surprises Act, the prior-authorisation rule, Medicare Advantage payment-model updates each year. Every CMS rule is, downstream, a software project at every payer and every provider. Sudhir's working observation: CitiusTech's project pipeline lags CMS rule-making by about nine months.

This is a feature of US healthcare, not a bug. The biggest customer of US healthcare is the US government. The government's policies are the product roadmap for the industry that serves the government. A firm that reads CMS rules carefully has a leading indicator on its own demand curve that most consumer-software firms cannot dream of.

Beyond healthcare. In any heavily-regulated industry, the regulator is the silent product manager. Reading regulation as a roadmap is a strategy, not a chore.
12

Indian healthcare engineering, finally named.

Sudhir reaches for the analogy with measured confidence. India is the back office of US healthcare in the same way it became the back office of US banking in the 2000s — Cognizant TriZetto, Wipro, TCS, Sutherland, and CitiusTech itself are no longer doing low-end ticket work. They are running the clinical-trial analytics for top-five pharma. They are operating the claims systems for major Blues plans. They are writing the ambient-scribing pipelines.

The under-told fact is that this took twenty years to compound and is now its own category. There is a stack of skill — domain knowledge, compliance experience, HL7 and FHIR fluency, ICD-10 coding literacy — that simply does not exist outside India and a handful of US specialists. The GCC (global capability centre) model, which Indian engineers built in financial services, is replicating in healthcare in the late 2020s.

Beyond healthcare. A vertical's "back office in India" graduates into a primary engineering centre when domain depth crosses a threshold. Watch for the threshold; it always comes a decade after the press has stopped reporting on it.
13

Pricing transparency is a slow-acting solvent.

CMS now requires hospitals to publish negotiated rates and insurers to publish their pricing files. The data is messy, inconsistent, and not yet wired into the consumer experience the rule-makers imagined. Sudhir is patient about the implication: the second-order effects, not the first. The data exists. Aggregators are cleaning it. Employers are starting to use it in benefits design. Reference-based pricing is creeping back. The cost-opaque era of US healthcare is ending — not next year, but inside this decade.

The downstream IT consequence is large. Every payer has to support transparency-driven workflows. Every provider has to defend its rates in negotiation. The analytics tooling that lets you compare reimbursement across markets is a new category that did not exist five years ago.

Beyond healthcare. Mandated transparency works on a five-to-ten-year clock. The first headline says "nothing happened." The fifth says "the market is unrecognisable."
14

Medicare Advantage is the centre of gravity.

Half of US Medicare beneficiaries are now on Medicare Advantage plans rather than traditional Medicare. That single fact is reshaping the payer landscape. MA plans are paid a capitated rate per enrolled senior; their margin lives in care management, STAR ratings, and risk-adjustment accuracy. Sudhir treats this as the single biggest driver of payer IT spend over the next five years.

The downstream demand is for software that is good at exactly the things MA plans live and die by: HEDIS measure capture, STAR uplift programmes, risk-adjustment factor (RAF) coding, member engagement analytics, and care-management workflow. That stack is being rebuilt right now. Every regional Blues plan is buying it or building it.

Beyond healthcare. When a payment model crosses fifty per cent share, it stops being a segment and starts being the centre of gravity. Strategy follows the median customer.
15

The next ten years: AI returns hours, value-based care finishes its transition.

Sudhir's closing frame is restrained. He does not promise revolution. He promises that the changes already underway will finish — that the value-based-care share of payment will keep climbing, that ambient scribing will become table stakes, that FHIR will be the default API, that population-health analytics will be a budgeted line item at every provider above a certain size. None of these are predictions about the next product. They are predictions about completion.

The thing that ages well in this conversation is the discipline of incremental claims. Healthcare rewards firms that stay in the room for two decades and bet on completion. The exciting bets are the ones the keynote stage announced ten years ago and are quietly turning real now.

Beyond healthcare. Most of what is interesting in a slow market is the completion of changes the keynote stage announced a decade ago. Bet on completion before you bet on revolution.

Lines worth keeping near your desk.

The hardest part of US healthcare isn't the technology. It's the fact that you are changing the technology while the system is running, and the system happens to be paying for someone's mother's surgery this afternoon. Sudhir Kesavan · 03:45
Value-based care is not a policy. It is a software rewrite that takes twenty years and we are about twelve years in. Sudhir Kesavan · 06:52
Doctors don't need help thinking. They need their evenings back. The AI that wins in healthcare is the one that knows the difference. Sudhir Kesavan · 28:42
Indian healthcare engineering took twenty years to become its own category. It looks obvious now. It did not look obvious in 2005. Sudhir Kesavan · 37:45

The jargon, unpacked.

Some of these will be obvious; some won't. Skim, mark the unfamiliar, come back later.

EHR
electronic health record
The system of record for clinical data — orders, results, notes, medications. Two-thirds of US hospital beds run on Epic; Oracle Health (formerly Cerner) is the main alternative.
FHIR
Fast Healthcare Interoperability Resources
The modern API standard for moving clinical data between systems. Long promised, finally usable at scale after CMS mandates in the early 2020s.
HIPAA
1996 federal law
The Health Insurance Portability and Accountability Act. Sets the privacy and security rules for protected health information (PHI). The first law any US healthcare engineer learns.
HITECH
2009 federal law
The Health Information Technology for Economic and Clinical Health Act. Used carrots and sticks to push US hospitals onto electronic records — the reason Epic and Cerner are at their current scale.
SOC2
audit framework
An attestation report on how a service organisation handles data security, availability, confidentiality. The audit grammar that healthcare procurement learned to ask for.
RCM
revenue cycle management
The business of getting providers paid — eligibility, coding, claims, denials, appeals. Where a meaningful share of US healthcare IT spend lives.
Fee-for-service
payment model
The legacy model: each procedure is billed and paid. Volume drives revenue. Still the majority of US healthcare payment, but declining.
Value-based care
payment model
Pay for outcomes over a population and time window rather than per procedure. Risk-bearing arrangements, capitation, shared-savings contracts. The structural shift in this conversation.
ACO
Accountable Care Organisation
A provider group that takes financial accountability for a population of patients under Medicare. The vehicle through which value-based care spread on the provider side.
Medicare Advantage
payment programme
Private-plan alternative to traditional Medicare. Roughly half of US seniors are now enrolled. Capitated payment, risk adjustment, STAR ratings — the centre of gravity for payer IT.
HEDIS
quality measures
The Healthcare Effectiveness Data and Information Set. The standardised report card every health plan files. Drives a large share of payer analytics spend.
STAR ratings
CMS scoring
A five-star rating for Medicare Advantage plans. Determines bonus payments and member acquisition. A four-to-five-star plan can be worth hundreds of millions per year.
Clinical AI
umbrella
AI applied to clinical workflows — note drafting, decision support, imaging interpretation, prior-authorisation. The hype/reality ratio is closing fast on the ambient-scribing wedge.
Ambient scribing
product category
Software that listens to the doctor-patient encounter and drafts the clinical note. Abridge, Nuance/Microsoft DAX. Returns hours of pajama-time documentation per clinician per week.
Population health
analytics surface
Looking at a panel of patients as a cohort rather than per-encounter. Risk-stratification, rising-risk, care-gap closure. The dominant analytics question once value-based care is the payment model.
CMS
Centers for Medicare and Medicaid Services
The US government agency that pays for roughly forty per cent of US healthcare. Its rules are the silent product manager for the industry.
ICD-10 / ICD-11
diagnostic coding
The international classification of diseases. ICD-10 is the operational standard in the US (since 2015); ICD-11 is being adopted internationally and slowly seeping in.

Check what you actually retained.

Try to answer before you click. The point is to notice where the conversation is fuzzy in your memory, then return to the transcript.

Q1
What is the structural shift Sudhir keeps returning to, and why does it matter for IT?
The shift from fee-for-service to value-based care — paying for outcomes over a population rather than for each procedure. It matters because every system underneath is built to measure the old unit of payment. Changing the unit forces a rebuild of EHRs, claims engines, and analytics layers, and CitiusTech sits inside that rebuild.
Q2
Why does Sudhir argue Epic's moat is workflow, not features?
Because two-thirds of US hospital beds run on Epic and a generation of clinicians has learned medicine through that interface. The switching cost is measured not in licence fees but in retraining tens of thousands of doctors. Muscle memory is the moat. That is also why the opportunity has moved to the layer that sits on top of Epic via FHIR.
Q3
What are CitiusTech's three customer pillars?
Payers (insurance plans, Blues, Medicare Advantage), providers (hospitals, IDNs, ACOs), and life sciences (pharma, medical devices). The pillars buy different software but share the same underlying engineering culture — and their procurement cycles rarely move in sync, which makes the firm counter-cyclical inside healthcare.
Q4
How does Sudhir frame HIPAA, SOC2, and HITECH — overhead or moat?
A ramp that becomes a moat once paid. The first audit is expensive; the hundredth is a process. Firms that have written the same kinds of attestations and runbooks for fifteen years have an engineering muscle that new entrants cannot acquire quickly. Compliance is a moat in the opposite direction from how it looks.
Q5
Why did ambient scribing succeed where most clinical AI demos didn't?
Because it returned hours to a burned-out user rather than offering a new feature. The doctor sees a finished note instead of typing through dinner. Pajama-time documentation falls. That number is so visible to a clinician's life that the buying decision moves from IT to the chief medical officer — and the workflow change, not the model, is the product.
Q6
What is FHIR and what changed about it recently?
Fast Healthcare Interoperability Resources — the modern API standard for moving clinical data. It was a slide in keynotes for over a decade. CMS mandates, the 21st Century Cures Act, and finally usable endpoints from major EHR vendors have made it a wire-level reality in the last three years. The analytics and AI tools that sit above it are now unblocked.
Q7
What is Medicare Advantage and why does Sudhir treat it as the centre of gravity?
A private-plan alternative to traditional Medicare, paid on a capitated basis per enrolled senior. Roughly half of US seniors are now enrolled. MA plans live and die by HEDIS capture, STAR ratings, and risk-adjustment accuracy, which makes them the largest single driver of payer IT spend over the next five years.
Q8
What is population health analytics, and why does it require a different software product?
Once payment shifts to outcomes over a panel, the question changes from "did this patient get the right care during this admission" to "which forty thousand of my attributed members are rising-risk this quarter, and what is the cheapest intervention." That needs claims, EHR, social determinants, pharmacy fills, and device telemetry stitched together — a different stack from per-encounter analytics.
Q9
Why does Sudhir call provider burnout a design constraint?
Because one in three US physicians is burned out and the proximate cause is documentation load. Every new tool that adds clicks to the EHR makes the problem worse. The best healthcare-IT products of the next decade will be the ones that remove clicks — ambient scribing, prior-auth automation, retrospective coding. The market for "add another button to Epic" is functionally closed.
Q10
What does Sudhir mean when he calls CMS the silent product manager?
The Centers for Medicare and Medicaid Services pays for about forty per cent of US healthcare and writes the rules — pricing transparency, interoperability, prior-authorisation, MA payment models. Every CMS rule is, downstream, a software project at every payer and provider. Reading CMS rule-making is reading the demand curve nine months in advance.
Q11
How does Sudhir describe Indian healthcare engineering as a category?
A twenty-year compounding of domain knowledge, compliance experience, and HL7/FHIR/ICD-10 fluency that is now its own thing — not a back office, not low-end ticket work. Cognizant TriZetto, Wipro, TCS, Sutherland, and CitiusTech run clinical-trial analytics for top-five pharma and claims systems for major Blues plans. The GCC model is replicating in healthcare in the late 2020s.
Q12
What is the "completion" frame Sudhir closes on, and why does it age well?
Most of what is interesting in US healthcare over the next decade is not a new revolution but the completion of changes already underway — value-based care reaching majority share, ambient scribing becoming table stakes, FHIR as the default API, population-health analytics as a budgeted line item. Slow markets reward firms that stay in the room and bet on completion.

Five questions worth sitting with.

No correct answers. Type into the boxes — your responses are saved locally and exportable along with your notes.

Sudhir frames compliance as a ramp that becomes a moat. Where in your own industry is the audit grammar quietly turning into a competitive asset?

Ambient scribing won by returning hours, not by adding features. Where is the equivalent "give back evening time" wedge in the workflow you serve?

The Epic moat is muscle memory, not feature parity. Where is the system-of-record interface you cannot dislodge — and what is the right adjacency above it?

CMS rule-making is the silent product manager for US healthcare. Who is your industry's silent product manager — and are you reading them?

Sudhir bets on completion, not revolution. What three changes already underway in your sector are mostly going to finish over the next decade?

Where to push back.

The strongest version of each disagreement, written to be persuasive — not to win.

"US healthcare moves too slowly to matter."

A common dismissal from product-software founders: by the time anything ships in healthcare, the technology is two cycles out of date.

The steelman is real. Sales cycles run twelve to twenty-four months, integration projects another twelve, and the regulatory overhead taxes every feature. But the steelman misses the structural fact Sudhir builds his career on: the slowness is exactly why the market is large and durable. Firms that can tolerate the cadence compound; firms that cannot, churn. A pace that consumer-software founders find intolerable is itself a selection function. The matter, then, is not speed but the patient capital and engineering culture that survives the wait.

"AI will leapfrog the existing healthcare IT stack."

A claim heard at every AI conference: foundation models will obsolete the EHR, the claims engine, the analytics warehouse.

The counter: the regulated stack is the part that isn't being leapfrogged. HIPAA still requires that PHI be handled a specific way. ICD-10 still gates payment. The clinical workflow is still defined by the EHR. What AI is doing is colonising the layer above — note drafting, prior-auth, coding assistance — none of which replaces the underlying system of record. The pattern is augmentation inside the existing stack, not replacement of it. The firms that win are the ones embedded enough in the existing stack to ship the augmentation. CitiusTech is one. A pure AI start-up trying to "rebuild healthcare from scratch" usually discovers in year three that it is rebuilding HIPAA from scratch.

"Epic's moat is unassailable."

Two-thirds of US hospital beds, generational muscle memory, no serious challenger in twenty years. Game over.

The push: Epic's moat is unassailable as a system of record. It is not unassailable as a workflow surface. The layer that sits between the clinician and Epic — through SMART-on-FHIR apps, ambient scribing overlays, AI-driven order entry — is where new value is accruing, often without Epic's permission. Oracle Health is also a real second-order risk if its cloud-native rebuild lands. The healthier reading is that Epic's seat is secure but the interesting product surface has moved upward from it. The moat does not include the air above the moat.

"Indian healthcare engineering can't move beyond services."

The traditional dismissal: India is good at staffing, capable at delivery, but unable to produce a healthcare product that wins in US markets.

The serious counter is that the services frame is a sociology, not a destiny. CitiusTech, Innovaccer (Indian-founded, US-listed), and a growing cohort of healthcare-AI start-ups (some still GCC-incubated) are already shipping productised offerings — population-health platforms, FHIR pipelines, RCM SaaS. The threshold question is whether the next decade produces a healthcare-IT category leader founded out of Mumbai or Bengaluru. The conditions — domain depth, compliance fluency, US-market exposure — are now present in a way they were not in 2010. The services frame is correct for the firms that have not yet crossed; it is the wrong frame for the ones that are crossing now.

Three angles on Monday morning.

If you don't work in healthcare, here's what to take.

H

If you're a health-tech operator

  • Map your roadmap against CMS rule-making nine months ahead. The regulator is your silent product manager — read the rule-text, not the press release.
  • Score every new feature on hours-returned-to-the-clinician. Subtractive features beat additive ones in a burned-out user base.
  • Build above Epic, not against it. Integration depth via FHIR is a quarter-long project; replacement is a decade-long suicide note.
  • Treat your compliance posture as an engineering muscle. Make the fortieth audit cheaper than the first; that ratio is your moat.
  • Pick a side of the three pillars (payer / provider / life sciences) and stay there long enough to compound domain. Generalist healthcare services are a tougher sell every year.
I

If you're an investor

  • Discount founders who can't name three CMS rules and what they imply for procurement. Healthcare moves on policy clocks.
  • Read time-to-first-audit as a leading indicator of GTM realism. Companies that haven't shipped a SOC2 report by Series A are usually two years from where they think they are.
  • Track Medicare Advantage exposure across the portfolio. It is the centre of gravity for payer IT spend; under- or over-weight is a real allocation call.
  • Bet on completion before you bet on revolution. The most boring "value-based care infrastructure" deal can outperform the most exciting "AI doctor" deal over a ten-year hold.
E

If you're an engineering leader

  • Design every interface to a clinician for hours returned, not features added. Time is the only currency.
  • Treat FHIR as the default I/O. Bespoke HL7 integrations are still common; they are also a sign that the team has not yet skated where the puck is going.
  • Make audit evidence a first-class artefact of your build pipeline. Every PR should produce attestation-ready logs without manual scraping.
  • Hire for domain depth before you hire for AI fluency. A senior clinical informaticist who has shipped at Epic or Cerner is rarer than a transformer specialist and worth more in this market.
  • Build for hybrid deployment. Many large US payers and providers still require single-tenant or on-prem options; SaaS-only is a story enterprise health doesn't fully buy.

Thirty years of US healthcare IT, briefly.

The arc Sudhir sketches in the conversation, lined up.

1996HIPAA passed. The Health Insurance Portability and Accountability Act sets the privacy and security baseline for protected health information. Twenty-eight years later it still gates how every healthcare system handles data.
1999CitiusTech founded. Started in Mumbai as a healthcare-IT services firm. Spends the next two decades quietly compounding domain depth across payer, provider, and life-sciences work.
2009HITECH Act. Federal carrots and sticks push US hospitals onto electronic records. Epic and Cerner become national systems. The EHR era begins in earnest.
2010Affordable Care Act. Establishes ACOs, expands Medicaid, and sets the legal scaffolding for value-based care. The unit-of-payment shift starts in earnest in policy, slower in production.
2015ICD-10 adoption. US healthcare finally moves from ICD-9 (13,000 codes) to ICD-10 (68,000 codes). Every claims system, every EHR, every provider workflow is reworked. A trillion-dollar code migration.
~2019FHIR R4 standardisation. The interoperability standard reaches a stable, usable version. CMS interoperability rules in 2020 give it teeth. Twenty years of "data trapped in the EHR" begins to thaw.
2021CMS pricing transparency rules. Hospitals must publish negotiated rates; insurers must publish pricing files. Messy, inconsistent, slow-acting — but the cost-opaque era begins to end.
Nov 2022ChatGPT release. Large language models go mainstream. Within six months every healthcare vendor has an AI roadmap; within twelve, ambient scribing turns from demo to budgeted line item.
2022Oracle acquires Cerner. A twenty-eight-billion-dollar bet on rebuilding the second-largest US EHR on a cloud-native, FHIR-first foundation. The biggest healthcare-IT migration of the decade is underway and mostly off the front page.
2023–'25Ambient scribing emergence. Abridge, Nuance/Microsoft DAX, and a handful of others move clinical AI from keynote to clinic. Pajama-time documentation begins to fall. The template for AI in healthcare is established as workflow, not chatbot.
2026Sudhir's CitiusTech. Eight thousand employees. Serves US payers, providers, and life sciences. Indian healthcare engineering is finally a named category. The next ten years are about completing the rewrites already underway.

The whole conversation, searchable.

Click a timestamp to open YouTube at that moment. Click any line to highlight it (yellow). Highlights and notes save in this browser only.

Shortcuts: / focus search · j/k previous/next segment · h toggle highlight on active line · click any 00:00 in the page to seek.
About this transcript. The transcript scaffold is in place but segments have not yet been ingested for this episode. Once captions are pulled from YouTube's auto-generated subtitles and grouped into ~12-second blocks, they will appear here in searchable form. In the meantime, every timestamp elsewhere on this page still opens YouTube at the right moment. Treat the chapter map, takeaways, and pull-quote timestamps as the working table of contents until the transcript lands.

Built as a personal listening tool. Video stays on YouTube.
/listening-lab · ep-07