Transgender Care, Healthcare Fraud and the UPMC Settlement: What Compliance Officers Should Be Asking

The federal government has made ending gender-affirming medical care for transgender minors an enforcement priority. Now, one of Pittsburgh's largest healthcare systems has agreed to stop providing that care and to pay the federal government $950,000. For healthcare compliance professionals, how the government got here and what it means deserves attention.

On September 18, 2026, the Department of Justice announced that UPMC and NYU Langone had reached agreements with the federal government arising from their provision of gender-affirming care to minors. Both health systems agreed to stop providing specified treatments, including puberty blockers, cross-sex hormones and certain surgical procedures. UPMC also agreed to pay $950,000; NYU agreed to pay $8.5 million.

What caught my attention wasn't simply that UPMC was involved. It was that, after reading DOJ's announcement—and then several of the local news reports about it—I still couldn't figure out exactly what UPMC had allegedly done wrong. That is unusual for a healthcare enforcement case.  And I was curious because UPMC is close to home—literally. I live and work in Pittsburgh, where UPMC is a major part of our healthcare landscape.

Typically, when DOJ or OIG announces a significant healthcare settlement, the compliance issue is relatively easy to identify. Perhaps the provider allegedly billed for services that were not provided, submitted unsupported diagnosis codes, paid kickbacks, billed for medically unnecessary services or otherwise caused a federal healthcare program to pay claims it should not have paid.

The allegations may ultimately be disputed, but we can usually identify the alleged misconduct. Here, I couldn't.

DOJ says its nationwide investigation is examining potential violations of the False Claims Act, the Food, Drug, and Cosmetic Act and other federal healthcare laws. It also refers generally to potentially fraudulent billing practices, including the use of false diagnosis codes to obtain payment from federal healthcare programs and private insurers.

But DOJ's announcement does not identify a false diagnosis code used by UPMC. It does not identify a particular false claim submitted by UPMC. It does not tell us what UPMC allegedly misrepresented to a payor, which claims were improperly paid, or what coverage requirement supposedly made those claims improper.

What the announcement does explain, in considerable detail, is that UPMC has agreed to stop providing gender-affirming care to minors.

I was puzzled.  And that led me to a significant regulatory development that occurred just over a month before the UPMC settlement. On August 11, 2026, CMS finalized a rule ending the use of federal Medicaid and CHIP funds for specified gender-affirming treatments furnished to minors. The rule covers puberty blockers, cross-sex hormones and specified surgical procedures and is scheduled to take effect October 13, 2026.

At first glance, that appeared to provide the missing reimbursement connection. But then I looked at the dates. The rule wasn't in effect when DOJ announced the UPMC settlement.

And that made the case more interesting, not less. The new CMS rule establishes the federal Medicaid and CHIP funding requirements going forward. But it does not, simply by being adopted in 2026, establish that claims UPMC submitted before the rule existed were false when they were submitted.

So I was back to my original question:

What, exactly, was the compliance violation? Does the New CMS Rule Explain the Violation?

Not entirely.

On August 11, 2026, CMS finalized a rule prohibiting the use of federal Medicaid and CHIP funding for specified gender-affirming treatments for minors. The rule covers puberty blockers, cross-sex hormones and specified surgical procedures. It is scheduled to take effect October 13, 2026.

That certainly changes the reimbursement landscape going forward. But it doesn't explain why UPMC's earlier claims were allegedly fraudulent.

The timing is important. The CMS rule was finalized only about five weeks before DOJ announced the UPMC settlement, and it had not yet taken effect. A new reimbursement prohibition does not, simply because it exists today, establish that a claim submitted under different rules several years ago was false when it was submitted.

So if the government believed UPMC had previously submitted false claims, there still had to be some basis for that allegation under the requirements applicable at the time.

What was it?

A Closer Look at DOJ's Fraud Theory

Looking beyond UPMC provides some clues.

UPMC is not the first health system caught up in this nationwide investigation. DOJ has reached agreements with several other providers, including Texas Children's Hospital, Cleveland Clinic, Connecticut Children's and Mount Sinai.

And the Texas Children's settlement is particularly helpful because the actual settlement agreement tells us considerably more about the government's theory.The agreement defines what DOJ calls "Masking Conduct" as the use of false diagnosis codes for services provided to treat gender dysphoria, including allegedly using inaccurate ICD-10 codes instead of the appropriate primary diagnosis code to obscure the reason the services were provided.

That begins to look much more like a conventional healthcare fraud theory. If a provider knowingly submits an inaccurate diagnosis because the accurate diagnosis would result in a service not being covered, that presents a legitimate claims-compliance concern. Depending on the facts, it could potentially support False Claims Act liability.

The Texas Children's agreement also describes other alleged conduct involving commercial insurance reimbursement and federal drug requirements.

But that brings me back to UPMC.

Did UPMC engage in this "masking conduct"?

Perhaps. But DOJ's public announcement doesn't tell us. We aren't given the allegedly false diagnosis code. We aren't told what the accurate diagnosis should have been. We aren't told which UPMC claims were affected, which payors paid them, whether those payors would have denied the claims if coded differently, or what UPMC allegedly knew when the claims were submitted.

And those facts matter.

The False Claims Act does not simply prohibit conduct the federal government later determines it does not approve of. An FCA case requires, among other things, a false or fraudulent claim, the requisite knowledge and materiality to the government's payment decision.

So although the other settlements help us understand what DOJ may be investigating, they still don't tell us precisely what UPMC allegedly did.

Then There Is the UPMC Court Fight

The story becomes even more interesting when you look at what happened before the settlement.As part of its investigation, DOJ sought records concerning minors who had received gender-affirming care through UPMC Children's Hospital of Pittsburgh. Patients and their families challenged the government's efforts to obtain portions of those records.

The federal district court in Pittsburgh ultimately rejected significant portions of DOJ's subpoena effort. DOJ appealed. And then, on August 10, 2026, DOJ withdrew that appeal. Five weeks later, DOJ announced its agreement with UPMC.

That chronology should be approached carefully. It does not establish why UPMC settled, nor does it prove that DOJ's underlying allegations lacked merit. Organizations resolve government investigations for many reasons, including cost, uncertainty, disruption and litigation risk. But from a compliance perspective, it leaves us without something that would have been extremely useful: a judicial decision on the underlying legal theory.

UPMC did not admit that it committed fraud. DOJ did not obtain a judgment that UPMC committed fraud. And the settlement means a court will not decide whether the particular claims DOJ was investigating actually violated the False Claims Act.

There is therefore an important distinction between an enforcement outcome and a judicial determination of wrongdoing. Compliance professionals need to remember that distinction when reading settlement announcements.

What About Pennsylvania?

There is another piece of this that I find interesting. If the alleged misconduct involved claims paid through Pennsylvania Medicaid, where was Pennsylvania?

Pennsylvania's Department of Human Services administers the Commonwealth's Medicaid program and has its own program-integrity functions. It can identify improper payments, investigate questionable billing and refer suspected fraud for enforcement.

Yet DOJ's announcement does not tell us whether Pennsylvania DHS believed UPMC's claims were improper, whether Pennsylvania participated in the investigation, or whether the Commonwealth considered these services covered when they were provided.

That doesn't mean Pennsylvania disagreed with DOJ. There may be information that isn't public. But it is a fair question because Medicaid is a federal-state partnership.

And the new CMS rule makes that distinction especially important. CMS says the rule ends federal Medicaid and CHIP funding for the specified services. It does not describe the rule as a general federal prohibition on the practice of medicine.

That difference matters.

Compliance officers have to distinguish among several questions that can easily become conflated:

·      Was the treatment lawful?

·      Was it covered under the applicable insurance policy or Medicaid program?

·      Was federal financial participation available?

·      Was the claim coded accurately?

·      Was the service medically necessary under the applicable coverage standard?

·      And did the provider knowingly make a false statement material to payment?

Those are related questions. They are not the same question.

Why This Case Matters Beyond Transgender Care

This is where I think the UPMC case becomes particularly relevant to compliance professionals. You don't have to work for a health system providing gender-affirming care to encounter this problem. Healthcare operates at the intersection of clinical practice, federal regulation, state law, reimbursement rules and enforcement discretion. And those things do not always move together.

A service may be lawful but not reimbursable. A drug may be prescribed off-label without that fact alone making the prescription unlawful. A state may permit a particular practice while federal funding rules restrict payment for it. A new administration may also interpret or prioritize enforcement of existing authorities differently from its predecessor.

Compliance's job is to understand those distinctions.

And when an organization operates in an area where the regulatory environment is changing rapidly, the documentation supporting its decisions becomes particularly important.

The Practical Compliance Lesson: Preserve the "Why"

One lesson I take from this case is that it isn't enough to know that a claim is being submitted correctly today. An organization may need to defend that claim years from now.

By then, the coverage policy may have changed. The regulation may have changed. Government guidance may have changed. The people who made the decision may have left. And the government's enforcement priorities may be very different.

That means organizations operating in areas of heightened or evolving regulatory risk should be able to reconstruct:

• what coverage rule applied on the date of service;

• why a particular diagnosis code was selected;

• whether the medical record supported that diagnosis;

• whether the documented clinical indication matched the treatment provided;

• what information was submitted during prior authorization;

• whether a payor provided guidance or confirmation regarding coverage;

• whether Compliance or Legal identified uncertainty and how that uncertainty was resolved; and

• whether subsequent regulatory changes triggered a reassessment of existing practices.

The objective isn't to create a defensive memo for every claim. It is to make sure that, where the rules are uncertain or changing, the organization preserves enough contemporaneous evidence to explain why it reasonably believed its conduct was compliant at the time.

The Question This Case Leaves Me With

There may be considerably more behind the UPMC settlement than the public currently knows. DOJ may have evidence that has not been disclosed. UPMC may have made a pragmatic decision that resolving the investigation was preferable to continuing to litigate. And the settlement expressly does not constitute a determination of liability.

After looking more closely at the UPMC settlement, I am still left with the question that first caught my attention: what, exactly, was the alleged fraud?

DOJ is clear about the outcome it sought: the end of specified gender-affirming care for minors; but much less clear about the specific conduct that made UPMC's claims fraudulent.

For compliance professionals, that uncertainty is itself instructive. Enforcement priorities can change quickly, making it increasingly important to understand, and document, the legal and reimbursement basis for decisions when they are made.

That lesson extends well beyond transgender care.

DOJ Announcement: HERE