Case Study 2 — The Hospitals That Sued Their Patients

This is a real, public story, told from the documented record: investigative reporting published in 2019 and after, court dockets that were public all along, congressional scrutiny, and the policy reversals that followed. Figures are characterized, not asserted precisely; the reporting itself is the source for specifics. It is told here for what it teaches, not for condemnation — every practice described was, in most respects, legal, and that is the point.

Background

Section 32.8 described what §501(r) of the Internal Revenue Code asks of a nonprofit hospital: a financial assistance policy, widely publicized; limited charges for eligible patients; reasonable efforts to determine eligibility before extraordinary collection actions. Roughly half of American community hospitals are nonprofit, holding tax exemptions justified by community benefit — of which charity care is the most visible kind.

In 2019, two investigations documented what the space between that framework and daily practice could hold.

What the reporting found

In Memphis, a nonprofit newsroom partnership examined the collection practices of a large faith-based nonprofit hospital system by reading five years of court records. The system had filed thousands of lawsuits against its own patients — more than any other institution in its county's general sessions court — pursuing balances through judgments and wage garnishment, frequently against low-income defendants, including some of the system's own employees, whose wages it garnished as both creditor and employer. The system operated its own collection agency. Its financial assistance policy existed throughout.

In Virginia, a separate investigation examined a university health system and found a collections operation of remarkable scale: over roughly six years, tens of thousands of lawsuits against patients, with the machinery to match — wage garnishments, bank account seizures, liens against homes — and charges to the uninsured computed from full charges. The reporting documented patients sued over balances that the system's own assistance criteria, applied differently, would have reduced or eliminated, and patients whose garnishments ran for years on balances that grew with interest.

Neither investigation alleged, in the main, that anything was illegal. Court dockets are public. The lawsuits were filed openly, in the institutions' own names, for years. What the reporting did was arithmetic and aggregation: nobody inside or outside either institution had ever put the number of suits, the profile of the defendants, and the words "nonprofit" and "charitable" on the same page.

The reversals

Both institutions changed course within weeks of publication. The Memphis system suspended its collection lawsuits, then announced it was erasing the debts of thousands of defendants, expanded its financial assistance policy, and raised its own minimum wage. The Virginia system suspended filings, expanded assistance eligibility, wrote off old judgments, and adopted a substantially more restrictive collections policy. Neither reversal followed a court loss, a regulatory action, or a change in the law. The practices ended when they became visible, and for no other documented reason.

The pattern was not confined to two systems. Follow-on reporting and academic work found hospital collection suits, garnishments, and liens in volume in multiple states; a senior member of the Senate Finance Committee sent oversight letters to nonprofit hospitals about §501(r) compliance; and several states subsequently tightened statutes governing hospital collections and financial assistance. Verify the current law in your state; this area has moved every year since.

What it shows

Everything §32.9 called the reputational math, run at institutional scale, with the answer printed. The suits were individually small and collectively enormous; the recoveries were modest against institutional revenue; and when the full cost — reputational, political, moral — was finally priced by the only mechanism that ever prices it, both institutions concluded within days that the program had never been worth running. The reversal is the arithmetic. What the organizations decided under scrutiny is what the numbers had said all along.

The FAP existed and did not function — which is §32.8's core warning made flesh. Both systems had policies. The reporting documented defendants who plausibly qualified and had never applied, never been screened, and in some cases never been told. A policy that depends on a completed application from the people least equipped to complete one will, with statistical certainty, pursue people it was written to protect. Presumptive eligibility is not a refinement; it is the difference between a policy and a paper.

"Preventable" here does not mean any individual was villainous — and that is what makes it teachable. Each step was ordinary: a balance aged, a policy escalated, a file went to legal, a court date arrived. Chapter 24's returned envelope, Chapter 29's "preventable: YES on a correct claim" — the same grammar. The failure was a process nobody owned end to end, measured by recoveries and never by outcomes, in which — echoing Chapter 26's unit clerk — the people processing the files could not see the aggregate they were creating, and the aggregate was the harm.

And it was detectable from outside before it was detected inside. The entire investigation was built from public dockets — no subpoena, no whistleblower, no PHI. Chapter 26's discharge-status distribution, Chapter 23's due-diligence finding, Case Study 1's claims-data researchers, and now this: the fourth time in this book that outsiders reading public or commercial documents saw an organization more clearly than its own reports did. An internal audit function that never asks "what would a journalist with our court docket conclude?" is missing a real audit procedure — Chapter 37 should say so.

The lesson

Legal is not the standard. Every tool in these programs — suit, garnishment, lien, interest — was lawful, mostly still is, and every one is also an extraordinary collection action that federal rules require a nonprofit to precede with reasonable efforts at assistance. The distance between "we complied" and "we would defend this on the front page" is where a revenue cycle leader actually works. This book has said it about coding since Chapter 5: the accurate claim and the defensible claim must be the same claim. This case extends it downstream: the collectible balance and the defensible collection must be the same event — and the test of defensibility is visibility, applied before the journalist applies it for you.

Discussion questions

1. Both institutions reversed within weeks of publication, without legal compulsion. What does the speed of the reversal tell you about what internal decision-makers already believed? Construct the internal report that, delivered two years earlier, might have produced the same decision — what is on it, and who receives it?

2. The FAPs existed throughout. Walk the failure through §32.8's requirements: at which specific points — publicity, application, screening before ECAs — did the paper policy and the real process diverge?

3. The employees whose wages were garnished by their own employer occupy a strange position in the story: insiders who experienced the process as outsiders. Why did their experience not function as an internal signal? Compare Chapter 19 CS2's finding that the absence of a place to say something is itself a control failure.

4. §32.9 argued that the most expensive collection event is often the one that works. Apply it here: list what each garnishment "recovered" and what it cost, including the costs that only became priceable after publication.

5. This case and Case Study 1 are the same story told from opposite directions — a pattern invisible from inside, priced by outsiders, ended by visibility. One produced a federal statute, the other produced voluntary reversals and scattered state laws. Which mechanism produced the more durable fix, and what does your answer imply about where §501(r) enforcement should go next?