United States: Medicaid Managed Care Proposed Rule Expands Program Integrity Obligations

On June 1, 2015, the US Centers for Medicare & Medicaid Services ("CMS") published its proposed rule on Medicaid managed care (CMS-2390-P).  As noted in our two earlier advisories, Massive CMS rule seeks to align Medicaid managed care with Medicare Advantage and marketplace plans and Medicaid managed care proposed rule expands federal role in rate setting at both the managed care organization and provider level, the proposed rule represents the first update to Medicaid managed care regulations since 2002, and offers revisions that are intended to better align the Medicaid program and the Children's Health Insurance Program ("CHIP") with other health care coverage sources, including Qualified Health Plans ("QHPs") under the Health Insurance Exchange marketplace and the Medicare Advantage program ("MA").

This third advisory examines the proposed rule's provisions related to program integrity, which range from expanded elements for an effective compliance program to a series of new integrity requirements.  According to CMS, these changes were necessary because the rapid growth of Medicaid managed care notwithstanding, the existing regulation's program integrity provisions are "fairly limited in scope."  The proposed regulations reflect CMS's focus on two types of program integrity risks: (1) fraud committed by Medicaid managed care health plans, and (2) fraud by network providers. The most notable changes relate to:

  1. Subcontractual Relationships and Delegation;
  2. Provider Screening and Enrollment;
  3. New Program Integrity Responsibility for States;
  4. Data Submission and Certification;
  5. Compliance Program Content and Procedures;
  6. Overpayments; and
  7. Payment Suspension.

If finalized, the cumulative impact of the proposed changes could have a profound effect not only on participating plans and providers, but also on the various states.  We discuss these changes and their implications in greater detail below.

Compliance Plan (42 C.F.R. § 438.608(a))

The current Medicaid managed care regulation states that a Medicaid managed care organization ("MCO") or Prepaid Inpatient Health Plan ("PIHP") "must have administrative and management arrangements or procedures, including a mandatory compliance plan, that are designed to guard against fraud and abuse."  42 C.F.R. § 438.608(a).  The detail provided is somewhat basic, focusing on the seven standard elements of a baseline compliance program:

  1. Written policies, procedures, and standards of conduct that articulate the organization's commitment to comply with all applicable Federal and State standards.
  2. The designation of a compliance officer and a compliance committee that are accountable to senior management.
  3. Effective training and education for the compliance officer and the organization's employees.
  4. Effective lines of communication between the compliance officer and the organization's employees.
  5. Enforcement of standards through well publicized disciplinary guidelines.
  6. Provision for internal monitoring and auditing.
  7. Provision for prompt response to detected offenses, and for development of corrective action initiatives related to the MCO's or PIHP's contract.

As noted, the current regulations offer little detail as to how plans can or should implement the seven standards.  The proposed rule, by contrast, fleshes out the purpose and function of the existing elements; in addition, it adds new substantive requirements for participating plans' compliance programs in the interest of making them more robust and effective.  Finally, CMS proposes to apply the program integrity requirements to Prepaid Ambulatory Health Plans ("PAHPs") and to subcontractors.

CMS asserts in several places that the proposed revisions and additions are intended to align Medicare Advantage and Medicaid by making the Medicaid managed care compliance program requirements  "consistent" with those of MA, as set forth at 42 C.F.R. § 422.503(b)(4)(vi).  CMS's statements notwithstanding, the proposed changes below differ from MA requirements in several fundamental respects (with the italicized language highlighting areas of difference from the MA requirements):

  • The establishment and implementation of procedures and a system with dedicated staff for routine internal monitoring and auditing of compliance risks, prompt response to compliance issues as they are raised, investigation of potential compliance problems as identifies in the course of self-evaluation and audits, correction of such problems promptly and thoroughly (or coordination of suspected criminal acts with law enforcement agencies) to reduce the potential for recurrence, and ongoing compliance with the requirements under the contract.
  • A system for training and education for the Compliance Officer, the organization's senior management, and employees for the Federal and State standards and requirements under the contract.
  • The establishment of a Regulatory Compliance Committee on the Board of Directors and at the senior management level charged with oversight of the compliance program.

Other noteworthy additional requirements on MCOs, PIHPs, and PAHPs include obligations relating to:

  • Notifying the State when a plan receives information about changes in an enrollee's circumstances that may affect the enrollee's eligibility;
  • Notifying the State when a plan receives information about a change in a provider's circumstances that may affect the provider's eligibility to participate in the managed care program;
  • Developing a method to verify, by sampling or other methods, whether services were in fact delivered to and received by enrollees;
  • Referring to the State Medicaid program integrity unit or fraud control unit any potential fraud, waste, or abuse that the MCO, PIHP, or PAHP identifies; and
  • Suspending payments to a network provider for which the State determines there is a credible allegation of fraud.

Data Submission (Proposed 42 C.F.R. § 438.604) and Certification (Proposed 42 C.F.R. § 438. 606)

Current managed care regulations identify required data elements for submission and certification, including, but not limited to, "enrollment information, encounter data, and other information required by the State and contained in contracts, proposals, and related documents." 42 C.F.R. § 438.604(a).  CMS is proposing to expand the types of data submitted as well as the standards regarding such submission by each MCO, PIHP, PAHP, Primary Care Case Manager ("PCCM") or entity performing primary case management and other services ("PCCM entity") to the State.  The new data submission categories would include encounter data and other data generated by the health plan for purposes of rate-setting; data on which the State determined compliance with MLR standards; data supporting compliance with solvency standards; data to ensure availability and accessibility of services; ownership and control disclosure information; the annual report on recoveries of overpayments; and, any other data related to the performance of the entity's obligations as specified by the State or Secretary.

The proposed rule also makes numerous and significant changes to the data certification process. In this regard, CMS proposes to eliminate the option available under the current regulations (similar to that available in the MA context) for a health plan's executive leadership to delegate the certification.  Under the proposed rule, the data attestation must be made by either the CEO or CFO of the health plan.  According to CMS, the CEO or CFO must be "personally responsible for the accuracy, completeness, and truthfulness of the reported data, documentation, or information."  Notably, CMS proposes that, "consistent with" recently revised MA regulations,  the certification be expressly based on a "reasonably diligent review of the data, documentation, and information specified."  Although the recently amended MA regulations do refer to the exercise of "reasonable diligence," it is exclusively in the context of identifying MA overpayments (42 C.F.R. § 422.326), and does not feature in any of the various MA certification regulations.  Therefore, it appears that CMS is proposing to apply the "reasonably diligent" standard, which is currently limited to MA overpayments, far more broadly in the context of Medicaid managed care certification requirements. This proposed change represents a major modification in the standards required for certification, meriting a strong public response to CMS's invitation for comments on using the reasonably diligent standard.

Overpayments (Proposed 42 C.F.R. § 438.608(d))

Section 1128J(d)(1) of the Social Security Act, as added by the Affordable Care Act, requires a person who has received an overpayment to report and return the overpayment to the Secretary, the State, an intermediary, or contractor, and to notify the party in writing of the reason for the overpayment within 60 days after the overpayment was identified.  The proposed rule would implement the statutory requirement by expressly mandating that MCOs, PIHPs, and PAHPs report overpayments to the State within 60 calendar days of their identification.  To assist in the reporting process, CMS is proposing that each MCO, PIHP, or PAHP have a standard mechanism in place for network providers to report the receipt of overpayments and return such overpayments within 60 calendar days.  Presumably, this mechanism would be supported by express contract provisions.

However, rather than the MCO, PIHP, or PAHP returning the overpayments to the State, CMS proposes that plan contracts specify that the MCO, PIHP, or PAHP should retain overpayments recovered from providers.  States would then be expected to take such recoveries into account in  developing future actuarially sound capitation rates based on information provided by the plans. States would be required to collect reports from MCOs, PIHPs, or PAHPs about their recovery of overpayments.

CMS is seeking comment on its proposal to allow MCOs, PIHPs, and PAHPs to retain overpayment recoveries.  This proposal, if implemented, could prove problematic for health plans and raise questions regarding the impact of such recoveries on plan capitation rates, particularly given the proposed rule's attention to actuarial soundness and rate setting.

Suspension of Payments (Proposed 42 C.F.R. § 438.608(a)(8))

As stated above, the proposed rule adds a new provision that would enable MCOs, PIHPs, and PAHPs to suspend payments to a network provider that is the subject of a credible allegation of fraud in accordance with 42 C.F.R. § 455.23.  CMS had previously discussed the applicability of suspension of payment requirements to Medicaid managed care plans,1 and believes the same rationale would apply with respect to investigations finding credible allegations of fraud regarding individual network providers, provided the State determines there is good cause for suspension of payments.  The responsibility of plans would be limited to promptly suspending payments at the direction of the State.

Some plans may appreciate the fact that the State would determine the existence of "good cause," since that could relieve the managed care entity of the burden of making a decision that is likely to be vigorously opposed by a suspended provider.

Provider Screening and Enrollment (Proposed 42 C.F.R. §§ 438.602(b), 608(b))

The Affordable Care Act added sections 1902(a)(77) and 1902(kk)(7) to the Social Security Act, requiring States to (1) comply with the process for screening providers, and (2) enroll all ordering and referring physicians or other professionals as participating providers.  Prior regulations specifically excluded Medicaid providers that only order or refer services as part of a risk-based managed care plan network from the screening and enrollment requirements.  76 Fed. Reg. 5862, 5904 (Feb. 2, 2011).

CMS's proposed revisions require the State, through its contracts with a MCO, PIHP, PAHP, PCCM, or PCCM entity, to ensure that all network providers are enrolled with the State as Medicaid providers, consistent with the Medicaid provider disclosure, screening, and enrollment requirements set forth in 42 C.F.R. Part 455, subparts B and E.  However, the proposed revisions make clear that they would not require network providers to render services to Medicaid fee-for-service ("FFS") beneficiaries.  Even though the State (and not the plans) would be responsible for screening and enrolling all network providers not otherwise enrolled with the State to provide services to FFS beneficiaries, the new screening and enrollment requirements could nevertheless prove problematic for plans who have managed care providers who do not participate in FFS.  Thus, requiring providers to enroll in Medicaid could present new challenges to building a provider network, such as logistical and administrative impediments if many providers need to be certified at the same time and if provider's are resistant or disinterested in going through the process. 

Subcontractual Relationships and Delegation (Proposed 42 C.F.R. § 438.230)

CMS proposes to replace the current standards set forth at § 438.230 with clearer expectations for MCOs, PIHPs, or PAHPs that enter into subcontractual arrangements and delegate responsibilities directly or indirectly related to the plan's performance of its contract with the State.  CMS notes that the new expectations are modeled on the MA standards set forth at 42 C.F.R. § 422.504(i) governing MA organization arrangements with first tier, downstream, and related entities (commonly referred to as "FDRs"), but they appear to go further.  For instance, under the proposed rule, CMS, HHS, or the OIG would have the right to audit, evaluate, and inspect at any time if the Agency or Comptroller determines a reasonable possibility of fraud exists.  The MA corollary regulation does not refer to the "OIG," or use the phrase "at any time."  Similarly, the proposed regulation would require a FDR to make available, for purposes of the audit, evaluation or inspection, "its premises, physical facilities, and equipment," but the MA regulation does not directly require FDRs to do so.

State Responsibilities (Proposed 42 C.F.R. § 438.602)

Current regulations set forth the basic rule that "as a condition of receiving payment under the Medicaid Managed Care program, an MCO, PCCM, PIHP, or PAHP must comply with the applicable certification, program integrity, and prohibited affiliation requirements" set forth in the Subpart H of the managed care regulations.  42 C.F.R. § 438.602.  CMS proposes revisions to replace the basic rule in its entirety and create a new section that contains all State responsibilities associated with program integrity, including monitoring of contractor compliance, screening, enrollment and revalidation of providers, review of ownership and control information, conducting federal database checks and periodic audits, receiving and investigating information provided by whistleblowers, posting certain information on the State website or making it available, upon request, implementing contractor safeguards, and implementing restrictions with regard to entities located outside the United States. 

Summary

While the expanded compliance program requirements, provider screening and enrollment procedures, overpayment provisions, enhanced data certification requirements, and new rules governing suspension of payments to providers may better address program integrity risks, the significant revisions to the existing program integrity requirements could have far reaching impacts on health plans, providers, service vendors, and State budgets.  In many respects, the additional detail and specificity in the regulations would create a new minimum, yet far more robust, compliance standard with which health plans, providers, contractors, and States would have to comply.

Health plans, providers, service vendors, the States, and other interested parties will have the opportunity to comment on CMS's comprehensive proposal.  To be assured consideration, comments are due to CMS no later than 5 p.m. EST on July 27, 2015.

Footnote

1. In the 2011 Payment Suspensions and Compliance Plans for Providers and Suppliers Final Rule, CMS stated that "if there is a pending investigation of a credible allegation of fraud against a Medicaid MCO, PIHP, or PAHP, the state should address the issue either through imposing a payment suspension or through other authorities that may be available to them under state law ...." 76 Fed. Reg. 5862, 5938 (Feb. 2, 2011).

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.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Events from this Firm
6 Dec 2017, Webinar, New York, United States

Join Dentons for a complimentary webinar focused on the ongoing challenge of integrating new technologies into existing information governance policies and risk management frameworks.

24 Jan 2018, Seminar, San Francisco, United States

Dentons will host our Fourth Annual Courageous Counsel Leadership Institute in January, centered on the theme "Cultivating Innovation."

 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Emails

From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.