Epic Lawsuit Reignites the Fight Over Patient Record Portability

Accessible to whom, in what format, and across how many logins?

A disability advocacy group and two plaintiffs have filed a class action against Epic alleging the company uses its dominant EHR position to make it harder for patients and third-party services to assemble complete medical records across providers. The complaint says MyChart effectively splinters a person’s history into separate provider-bound portals, which can become a major barrier for people trying to prove disability eligibility.

That is the part of this story that matters most.

This is not simply another health IT antitrust case. It highlights a broader issue in healthcare: the difference between having data available and having it in a form that is actually useful.

If a patient sees multiple specialists, visits different hospital systems, gets lab work in one place, imaging in another, and prescriptions managed elsewhere, they may technically have access to their records. In practice, though, that often means managing multiple portals, separate logins, and incomplete pieces of the full picture.

That gap is exactly what the plaintiffs are attacking. Becker’s says the suit alleges Epic’s system architecture creates barriers to building a complete longitudinal record and that those barriers can delay Social Security disability claims that depend on comprehensive documentation. One plaintiff allegedly spent more than two years assembling records while pursuing benefits. Another case described in the complaint involved records that were difficult to retrieve after the claimant died.

That turns this from an abstract interoperability debate into something more critical:

Fragmentation is not just an annoying user experience. It can become life-changing administrative friction.

Epic, of course, rejects the premise. In its statement to Becker’s, the company said it is fully interoperable with the Social Security Administration and has been for almost 15 years. Epic also says more than 2.7 million records were exchanged electronically between SSA and Epic-using organizations last year, and that over 85% of SSA’s interoperable health IT partners are providers using Epic. Epic’s own interoperability materials make similar claims and also point to very large cross-network exchange volumes more broadly.

Because both things can be true at once is what makes this story so interesting.

Epic can be highly interoperable in the aggregate and still leave important patient experiences broken at the edges.

Healthcare IT people love quoting standards, APIs, TEFCA, FHIR, exchange volumes, and compliance checkboxes. Regulators love talking about the 21st Century Cures Act and information blocking rules, which were explicitly designed to improve patient access, exchange, and use of electronic health information while encouraging more apps and competition.

But patients do not experience interoperability as a policy framework, they experience it as a task.

“Can I get the full record I need, right now, in one place, without becoming my own medical records department?”

That is the product test and it is one that electronic medical record systems keep failing.

The lawsuit also matters because Epic is not a niche vendor. Industry reporting and market-share research show Epic still holds the leading position in the U.S. hospital EHR market, with recent estimates around 41% to 42.3% depending on source and methodology. When the market leader makes a design choice, it does not stay a design choice. It becomes infrastructure.

The big picture is that healthcare records are now digital.

Patients must be able to actually assemble, move, authorize, and reuse those records without getting trapped inside institution-by-institution portal logic.

Because “your data is online” is not the same as “your data works for you.”

And if this lawsuit gains traction, it could pressure the industry to answer a question it has managed to dodge for years:

Is the patient portal a window into your record, or a cage around part of it?