United States: Medicaid Managed Care Transitions' Impact On Brain Injury Waiver Populations

As of June 2015, 24 states utilize a traumatic or acquired brain injury waiver, 1 as provided under section 1915(c) of the Social Security Act, which are designed to help individuals with traumatic brain injury (TBI) live in the community setting of their choice. The waiver services are intended to help an individual achieve maximum independence in the community, thus improving overall quality of life.

For the past decade, individual states have pursued unique and oftentimes novel approaches to managing their Medicaid population. However, as more states look to transition their Medicaid populations into managed care as a potential way to save money, several serious consequences have arisen, impacting the quality of care and the level of collaboration between providers and state officials. Through state-specific research, we found that as states look to incorporate waivers into their managed care models, rapid transitions have caused unnecessary disruptions for those with traumatic brain injury and negatively impacted the delivery of care. As a result, states that are interested in pursuing a managed care model should learn from the experience and lessons learned in other states. These lessons include easing vulnerable populations, such as TBI waiver populations, into managed care models in addition to conducting robust stakeholder outreach, which includes beneficiary, insurer, and provider education.

This article surveys how three states handled their TBI waiver population as the state transitioned into managed care and the lessons that can be drawn from the different approaches these states took. We also detail the role of advocacy on the state and federal level in ensuring a smooth transition for vulnerable populations.

Background

The Medicaid Home and Community Based Services (HCBS) waiver program was established by the Omnibus Budget Reconciliation Act (OBRA) of 1981 (P.L. 97-35). OBRA created section 1915(c) of the Social Security Act, which enabled states to provide home and community-based alternatives to institutionalized care upon federal approval. Initially, waivers were used to treat the elderly and disabled, as well as those with developmental disabilities. Over time, the waivers have broadened to include treating those with HIV/AIDS, mental illness, those with medically fragile and palliative care needs, and those with TBI (sometimes referred to as acquired brain injury for the purposes of the waiver), among other population groups. 2

Currently, 41 states contract with private insurers to run some or all of their health programs, with 70% of Medicaid enrollees being treated through private plans. 3 States consistently look to this model for a host of reasons, including as a way to save money, particularly as a greater number of individuals become eligible under expanded Medicaid due to the Affordable Care Act (P.L. 111-148). While some states have opted to continue under a fee-for-service model, more states are drifting towards managed care. For example, two current hold-outs—Oklahoma and North Carolina—are planning to initiate a managed care transition as early as next year. 4

States have increasingly touted the cost savings behind these proposals, but the results of the initiatives are often mixed. Some states saw modest savings due to reduced inpatient utilization, but peer-reviewed literature found little savings from managed care on the national level. 5 Still, states continually push the cost-saving argument, and the federal government appears willing to take, as New York's Medicaid director describes, "a leap of faith," to improve access and quality, with the potential for cost savings. 6

Given this trend, as well as the broad federal guidelines concerning Medicaid, it is imperative to address the impact of individual state plans to transition their waiver populations into managed care so states and providers can learn from past, often avoidable mistakes, and to identify a potential model for success when transitioning vulnerable populations.

Case Studies

Examining How Three States Chose Three Different Approaches with Different Outcomes

Kansas

Rapid Transition Caused Turbulent Roll Out

In November 2011, Kansas initiated its transition to Medicaid managed care, known as KanCare. Governor Sam Brownback touted the cost savings associated with the move, which brought the entirety of the state's Medicaid population into managed care by January 2013. The process was mired in controversy almost immediately following the initial announcement, receiving bipartisan criticism from the state legislature to remove certain waiver populations from the transition, or to postpone the transition plan altogether. 7 Despite these concerns, the state pressed forward, awarding three companies – Amerigroup Kansas, Sunflower Health Plan, and UnitedHealthcare Community Plan for Kansas – with contracts to operate statewide under KanCare in early 2012.

The rapid transition was especially problematic for the TBI community. In a memo dated August 2012, the state encouraged people currently employed as case managers for physically disabled and elderly Medicaid enrollees to apply for similar jobs with the three companies chosen to operate KanCare. 8 Case management specialists—a core, specialized service for the TBI population—are responsible for determining how many Medicaid services an individual needs. This is an especially important service for those individuals with complex needs who usually find themselves on 1915(c) waivers. This consolidation resulted in statewide downsizing, as the three companies were solely responsible for providing these services throughout the state.

In one instance, a local company that provides management and rehab services for about 500 people with brain injuries laid off 26 case managers. 9 This was not unique to this one company, as dozens of smaller programs also closed or decided to forego providing case management services. 10 In this new environment, the managed care organizations (MCOs) were taking on larger than normal caseloads, which led to them managing patients over the phone rather than in person. The new system was so poorly articulated that those with brain injury did not know how to find or request services they needed.

This also negatively impacted providers, who were forced to take on additional responsibilities to prevent service lapses. 11 By consolidating the service into three companies and aggregating care at a county level, it became increasingly difficult to get people connected with the services needed in their community.

Kentucky

Excluding Waiver Populations from Transition

Kentucky has been involved in managed care for nearly three decades. As of 2011, almost 90% of Medicaid beneficiaries in Kentucky were enrolled in managed care. 12 However, that same year, the state began to gradually redesign its Medicaid program, terminating its original managed care program, known as the Kentucky Patient Access and Care (KenPAC) Program, and incorporating those covered by KenPAC into its second managed care foray, known as the Kentucky Health Partnership (KHP). Furthering its goal to transition nearly its entire Medicaid program to a managed care model, in 2011 the state implemented a mandatory risk-based managed care program referred to as Medicaid Managed Care.

This program enrolled most Medicaid beneficiaries, including those newly eligible as a result of the Affordable Care Act Medicaid expansion. While Kentucky required its managed care organizations (MCOs) to expand their provider networks to ensure adequate access, the program still faced criticism regarding service delivery. Patients were being denied treatment and forced to travel long distances for care, a result of the aggressive timeline. 13 In fact, the MCOs that had applied to serve Kentucky only had four months to establish operations in the state. 14

Kentucky stakeholders, including those in the TBI provider community, raised concerns that the potential for disruptions were high given the lack of training for the MCOs. Ultimately, the state decided to exclude certain waiver populations from the managed care transition, 15 which advocates argued would have been too disruptive to current waiver members and possibly cause service disruptions as the new program was implemented. 16

New York

Stakeholder Engagement Leads to Delayed Transition

New York state officials have been engaged with stakeholders for nearly two years regarding the states intention to transition its Medicaid waivers into managed care. Stakeholders, who range from providers to consumer groups, identified a number of issues and concerns that need to be addressed.

For example, the Uniform Assessment System of New York is the current assessment tool being used in Medicaid managed care to determine ones level of care. Providers are especially concerned by this model as it has been shown in the early stages of development to not effectively capture the service needs of those on the TBI waiver. In fact, the New York State Department of Health increased its training of those who would assess individuals once the transition was implemented, and while there were improvements, over 25% of participants on the TBI waiver would still no longer receive the services they were receiving post-transition. This issue remained unresolved even as the state moved closer to the April 1, 2016, deadline for when the proposal would have been posted for its 30-day public comment period.

Another ongoing issue is defining a new scope of service coordination, a crucial stabilizing service under the waivers. State officials remain at odds with stakeholders over defining a new scope of service coordination as a service distinct and separate from care management, and the details of how this service will be available have not been worked out. The elimination of service coordination would be detrimental to those utilizing waivers, especially those with traumatic brain injury.

Stakeholders have been working collaboratively with the State and CMS to address these issues, in addition to working with legislators urging them to introduce legislation which would highlight their concerns. The bills introduced, which range from outlining requirements for the transition to excluding the waiver population from the transition, reflect the advocacy work of New York stakeholders who seek to develop a plan that ensures positive outcomes for beneficiaries.

As a result of these efforts, in late March, days before it was scheduled to post a transition plan for public comment, state officials came to an agreement via the state budget process to delay the transition for those utilizing waivers until January 2018. Securing this one-year delay will provide all parties involved additional time to work out remaining issues and to educate consumers on the evolving health care delivery model.

Role of Federal Government as Backstop

The federal government's role has varied as individual states submit proposals for their managed care models. In some cases, Centers for Medicare and Medicaid Services (CMS), which oversees state administered managed care, may require a state to delay its launch to ensure beneficiaries are not placed in undue risk.

While CMS may withhold approval until a state meets federal requirements, there are also a number of federal statutes CMS may use to ensure a smooth transition. In addition to a 30-day public comment period, states must demonstrate that there was a sufficient level of meaningful input from the public, with a report of the issues raised by the public and how the State considered those comments when developing the demonstration application. 17 CMS has the authority to request additional modifications, and at its discretion, an additional 30-day public comment period.

Recently, the state of Iowa intended to launch its managed care model on January 1, 2016, but in the weeks leading up to that launch, CMS informed the state that it would have to hold off on implementation:

"Based on our review last week of Iowa's progress, as well as the information you have provided, CMS expects that we will ultimately be able to approve Iowa's managed care waivers. However, we do not believe that Iowa is ready to make this transition Jan. 1," the letter says. "CMS previously outlined the requirements to provide high quality, accessible care to Medicaid beneficiaries, and Iowa has not yet met those requirements, meaning that a transition on January 1 would risk serious disruptions in care for Medicaid beneficiaries." 18

Critics of the Iowa transition pointed out that Iowa Medicaid beneficiaries had little information regarding the types of plans that were available, which would have caused issues on both ends of the delivery spectrum if the plan went forward as originally intended. Additionally, a tumultuous launch could have negatively impacted providers who were trying to understand the system, who could have decided to leave the system altogether. Iowa instead launched its managed care plan April 1, 2016, and early reports are that plans are operating relatively smoothly, an indication that more time was critical to ensuring the plan was operable.

The role of advocacy does not end at the state level, as the federal government maintains final authorization for a state transition plan.

Conclusion

As more states look at managed care models, it is important that stakeholders understand the options they have available to them when working with state officials. It is clear that as states look to address budget deficits, managed care is an intriguing model to pursue, but it is not without its challenges. Going forward, it has been shown that states who work with stakeholders are in the best position to ensure a smooth transition for beneficiaries.

Additionally, the role of advocacy cannot be understated for elevating important issues and ensuring the appropriate bodies are informed of ongoing matters. The New York case underscores this point, as members of the legislature introduced legislation on their behalf, and stakeholders were engaged with CMS and their federal delegation in Washington. These proactive engagement efforts ultimately lead to a one-year delay. As more states start to look at managed care models, ensuring providers and beneficiaries have the time to understand state plans, are engaged in development of that plan, and have the tools necessary to engage with state officials, are critical to a successful roll out.

Originally published in HFMA Advisor, Volume XLIII, Issue 5, reprinted with permission

Footnotes

1 https://www.nashia.org/pdf/state_services_2015_june.pdf

2 National Overview of 1915(c) HCBS waivers. https://www.cms.gov/Outreach-and-Education/American-Indian-Alaska-Native/AIAN/LTSS-Roadmap/Resources/State-Federal-Relationships/National-Overview-of-1915c-HCBS-Waivers.html

3 Connecticut Moves Away from Private Insurers to Administer Medicaid Program. Wall Street Journal. 2016.

4 Connecticut Moves Away from Private Insurers to Administer Medicaid Program. Wall Street Journal. 2016.

5 http://media.khi.org/news/documents/2013/01/14/managed-care-rwjf.pdf

6 http://media.khi.org/news/documents/2013/01/14/managed-care-rwjf.pdf

7 http://www.khi.org/news/article/hundreds-protest-inclusion-disability-services-kan

8 http://www.khi.org/news/article/kancare-mcos-take-case-management-role

9 http://www.khi.org/news/article/kancare-mcos-take-case-management-role

10 http://www.thegazette.com/subject/news/health/managed-care-companies-to-offer-own-case-management-20160313

11 http://www.thegazette.com/subject/news/health/managed-care-companies-to-offer-own-case-management-20160313

12 https://www.medicaid.gov/medicaid-chip-program-information/by-topics/delivery-systems/managed-care/downloads/kentucky-mcp.pdf

13 http://khn.org/news/kentucky-medicad-managed-care/

14 http://www.medicalnews.md/managed-care-in-kentucky-failure-or-success/

15 "Evaluation of Statewide Risk-Based Managed are in Kentucky." Urban Institute and University of Kentucky. 2012

16 Based on conversations with Kentucky advocate.

17 42 C.F.R. § 431.408.

18 http://www.desmoinesregister.com/story/news/politics/2015/12/17/feds-tell-iowa-delay-medicaid-privatization-60-days/77495488/

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
 
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.

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.