AcquiredAcquired

Epic Systems (MyChart)

Ben Gilbert on epic Systems built healthcare’s integrated software empire without VC money.

Ben GilberthostDavid Rosenthalhost
Apr 21, 20253h 57mWatch on YouTube ↗
Judith Faulkner origin story and early programmingChronicles single-database architecture; MUMPS lineageBilling (Resolute) as adoption inflection pointKaiser Permanente deal as market-defining proof pointVerona campus and Epic’s “software factory” cultureHITECH/Meaningful Use: digitization vs transformationInteroperability battles: Care Everywhere, Cures Act, TEFCACustomer model: technical specialists, BFFs, report cardsCompetitor consolidation: Cerner/Siemens; Oracle acquisitionDoD/VA EMR contract failures as industry contrastCosmos: anonymized, cross-system research datasetAI/ambient documentation and future “grid of care”

In this episode of Acquired, featuring Ben Gilbert and David Rosenthal, Epic Systems (MyChart) explores epic Systems built healthcare’s integrated software empire without VC money Acquired profiles Epic Systems, the private Wisconsin-based company behind MyChart and the dominant EHR “nervous system” for major U.S. health systems. The episode traces founder Judith Faulkner’s origins as a math/programming prodigy, Epic’s early technical differentiation (a single integrated database in Chronicles), and the company’s unusually disciplined, idiosyncratic operating culture.

At a glance

WHAT IT’S REALLY ABOUT

Epic Systems built healthcare’s integrated software empire without VC money

  1. Acquired profiles Epic Systems, the private Wisconsin-based company behind MyChart and the dominant EHR “nervous system” for major U.S. health systems. The episode traces founder Judith Faulkner’s origins as a math/programming prodigy, Epic’s early technical differentiation (a single integrated database in Chronicles), and the company’s unusually disciplined, idiosyncratic operating culture.
  2. Epic’s dominance is explained through integrated clinical + billing workflows, a reputation for implementations that work, extreme customer focus on hospital leadership, and massive switching costs—amplified by network effects like Care Everywhere and physician training pipelines.
  3. Policy shifts—especially Medicare/Medicaid’s documentation needs and the 2009 HITECH “Meaningful Use” incentives—pulled forward nationwide digitization, entrenching incumbents and rewarding low-risk vendors like Epic. The episode closes on current scale (607 customers, 5.7B revenue), emerging opportunities (payers/pharma, prior auth, AI scribes, Cosmos research data), and risks (antitrust, interoperability mandates).

IDEAS WORTH REMEMBERING

7 ideas

Epic won by tightly integrating clinical and billing workflows in one database.

Chronicles’ single-database design reduces data handoffs between modules, making revenue cycle, documentation, and clinical workflows more reliable—crucial when errors can mean lost reimbursement, compliance violations, or patient harm.

Reliability and implementation credibility became Epic’s primary sales engine.

Epic’s reputation for delivering “on time and working” (relative to industry norms) created a “nobody gets fired for buying Epic” brand, especially after marquee wins like Kaiser validated performance at extreme scale.

Policy created the billing-driven need for standardized records—then supercharged adoption.

Medicare/Medicaid and private payers required auditable documentation to pay claims, making EHRs foundational. The 2009 HITECH Act then moved adoption from ~9% to ~95% of hospitals by 2014 via incentives and penalties.

HITECH digitized healthcare, but did not truly transform it.

The episode argues “Meaningful Use” defined checkboxes that increased clicks and administrative burden, contributing to burnout and bloat; digitization enabled new capabilities, but workflows and incentives often remained misaligned.

Epic’s culture is engineered like a production system, not a typical software company.

Hiring young talent, standardizing processes (note-taking, emails, testing), requiring developers to fix their own bugs, and using immersion trips creates a high-trust, high-performance “software factory” optimized for low-defect enterprise delivery.

Switching costs and network effects now make Epic’s moat exceptionally hard to breach.

EHR replacement is multi-year, high-risk, and mission-critical; once installed, customers rarely leave. Network effects compound via Care Everywhere record exchange and the fact that most medical trainees learn on Epic.

Epic’s future upside is expanding from providers to the rest of healthcare’s value chain.

With broad provider penetration, Epic can sell tools to payers and pharma (e.g., prior auth automation) and leverage Cosmos’ anonymized data for research, clinical trials, and decision support—while AI scribes may reduce the EHR’s biggest pain point.

WORDS WORTH SAVING

5 quotes

Epic is a very unusual company… they do no marketing… don't negotiate, don't discount… never raised venture capital… never done any acquisitions.

Ben Gilbert

Of their over six hundred customers, they have never lost a single one.

Ben Gilbert

Rather than managing multiple vendors and systems, buyers get a comprehensive platform with a single database, unified workflows…

Ben Gilbert (quoting Health API Guy)

Do not go public. Do not acquire or be acquired… Software must work. Reality equals expectations.

David Rosenthal (Epic’s Ten Commandments)

Meaningful Use wildly succeeded at digitization… It did absolutely nothing on digital transformation.

David Rosenthal (quoting a health system CIO)

QUESTIONS ANSWERED IN THIS EPISODE

5 questions

How exactly does Chronicles’ single-database model differ from Cerner/others architecturally, and what tradeoffs does it impose?

Acquired profiles Epic Systems, the private Wisconsin-based company behind MyChart and the dominant EHR “nervous system” for major U.S. health systems. The episode traces founder Judith Faulkner’s origins as a math/programming prodigy, Epic’s early technical differentiation (a single integrated database in Chronicles), and the company’s unusually disciplined, idiosyncratic operating culture.

Why did Epic avoid billing software until 1987 (Resolute), and how did that change its growth trajectory?

Epic’s dominance is explained through integrated clinical + billing workflows, a reputation for implementations that work, extreme customer focus on hospital leadership, and massive switching costs—amplified by network effects like Care Everywhere and physician training pipelines.

What were the decisive technical and organizational factors that made Kaiser choose Epic over Cerner—and why did Epic refuse a split ambulatory/inpatient approach?

Policy shifts—especially Medicare/Medicaid’s documentation needs and the 2009 HITECH “Meaningful Use” incentives—pulled forward nationwide digitization, entrenching incumbents and rewarding low-risk vendors like Epic. The episode closes on current scale (607 customers, 5.7B revenue), emerging opportunities (payers/pharma, prior auth, AI scribes, Cosmos research data), and risks (antitrust, interoperability mandates).

To what extent did HITECH/Meaningful Use entrench Epic specifically versus simply expanding the overall EHR market?

Which parts of physician burnout are truly “Epic problems” versus hospital configuration choices, regulatory requirements, or payer-driven documentation?

EVERY SPOKEN WORD

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome