More enrollment revocations would go retroactive — for every Medicare provider type
Update (6 Oct 2026): We corrected this article. CMS-1844-P proposes adding grounds on which a revocation takes effect retroactively; it does not make every revocation retroactive. Some proposed grounds take effect on the date CMS or its contractor makes the determination.
Under current rules, only certain revocation grounds let CMS claw back payments retroactive to when noncompliance began; most revocations take effect prospectively. CMS-1844-P proposes adding more grounds with a retroactive effective date — for example, back to the date of a False Claims Act judgment, or to the effective date of an enrollment obtained under a new name after an earlier revocation — so for many more revocations, payments made in between would become recoverable.
The rule also expands the reasons CMS can act: enrollment presenting a high program risk, and suspensions or revocations of the provider's owners or managing employees in other state or federal programs, among others. The cross-jurisdiction provision matters for multi-state operators and for anyone whose ownership group has history anywhere in the system — a Medicaid suspension in one state becomes potential grounds against Medicare enrollment everywhere.
The quiet consequence is financial-risk timing. A prospective revocation ends future revenue; a retroactive one converts months of already-spent revenue into a debt. For small agencies, that difference is existential, which is precisely the deterrent CMS intends.
What to do now
- Treat your enrollment file as a living compliance document: PECOS data, ownership disclosures, and managing-employee lists accurate at all times, not at revalidation.
- Diligence your own ownership group — know about any adverse action in any program before CMS connects it for you.
- If you acquire, this raises the price of inherited enrollment problems; adjust diligence accordingly.