Proposed CMS Rule Requires Providers To Disclose Affiliations

DP
Day Pitney LLP

Contributor

Day Pitney LLP logo
Day Pitney LLP is a full-service law firm with more than 300 attorneys in Boston, Connecticut, Florida, New Jersey, New York and Washington, DC. The firm offers clients strong corporate and litigation practices, with experience on behalf of large national and international corporations as well as emerging and middle-market companies. With one of the largest individual clients practices on the East Coast, the firm also has extensive experience assisting individuals and their families, fiduciaries and tax-exempt entities plan for the future.
On March 1, the Centers for Medicare & Medicaid Services published a proposed rule that amends regulations under 42 CFR 405, 424, 455 and 457.
United States Food, Drugs, Healthcare, Life Sciences

On March 1, the Centers for Medicare & Medicaid Services (CMS) published a proposed rule that amends regulations under 42 CFR 405, 424, 455 and 457 to require Medicare, Medicaid and CHIP providers and suppliers to disclose any current or previous affiliation with a provider or supplier that (i) has uncollected debt; (ii) has been or is subject to a payment suspension under a federal health care program; (iii) has been excluded from Medicare, Medicaid or CHIP; or (iv) has had its Medicare, Medicaid or CHIP billing privileges denied or revoked.

The proposed rule allows CMS to deny and revoke provider and supplier enrollment based on affiliations that pose an undue risk of waste, fraud and abuse. The rule also increases the Medicare program re-enrollment ban from three to 10 years. Any attempt to circumvent a ban can result in the ban being extended for up to 20 years.

Comments on the proposed rule are due by May 2, 2016.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

Mondaq uses cookies on this website. By using our website you agree to our use of cookies as set out in our Privacy Policy.

Learn More