HealthCare.gov has recovered from its rocky start. So why are state exchanges -- opened by enthusiastic supporters of the Affordable Care Act -- still suffering?
The federal HealthCare.gov website got off to an unhealthy start, but recovered after a tense, heroic effort. Meanwhile, several state-run health insurance exchanges remain chronically ill as the March 31 deadline for open enrollment looms. Citizens who are uninsured won't get another chance to sign up until the next open enrollment period begins in November.
Turns out the Tea Party wasn't the biggest threat to Obamacare, after all. An analysis by ProPublica, a nonprofit investigative news site, noted the "spectacular failure of health insurance exchanges in Minnesota, Massachusetts, Oregon, and Maryland -- all blue states that support the Affordable Care Act." They were among the 14 states that chose to implement their own insurance shopping sites, while others -- including those with administrations hostile to the law -- punted that responsibility to HealthCare.gov.
In most cases, the dysfunction of the state websites was a matter of poor performance, bugs, and missing features, some of which still haven't been addressed after six months. Oregon never managed to launch an online shopping experience for consumers at all.
Massachusetts had a working health insurance exchange before all this began, created to support health insurance reforms that date to Mitt Romney's time as governor. Yet the state stumbled when reworking the site to adopt the federal law enacted under President Obama. This week, Massachusetts decided to end its relationship with CGI, the same consulting firm responsible for the rocky initial implementation of the federal HealthCare.gov website and several problematic state efforts.
Oracle, IBM, and Xerox have all come under fire for their roles in these implementations. Meanwhile, Deloitte is the one IT consultancy that came out smelling like a rose, having worked on the best-performing exchanges in Connecticut, Kentucky, Rhode Island, and Washington. In every case where vendors are blamed, there's room for debate about whether state officials should be taking more responsibility for lack of oversight or for changing requirements while the project was underway.
In Oregon, former Oregon Health Authority CIO Carolyn Lawson has filed the initial paperwork for a lawsuit against the state, alleging that the blame for the project's failures was directed at her after she resisted cooperating with a "coverup" of the truth. Part of what she is disputing is the division of responsibility between her former agency and Cover Oregon, the organization set up to administer the health insurance exchange program. Cover Oregon officials have said they were kept in the dark about problems with the system during a period when OHA oversaw the IT project. Lawson said Cover Oregon officials were intimately involved and caused some of the problems by not setting clear and consistent requirements for the project.
A federal review of the project aimed more blame at Oracle for poor performance and Cover Oregon for poor contract administration. However, a review of the contract's history by The Oregonian found some of the problems began when OHA tacked the Cover Oregon implementation onto a previously planned project to revamp the state's health and welfare systems. Cover Oregon never took steps to tighten those controls, according to that report.
David F. Carr oversees InformationWeek's coverage of government and healthcare IT. He previously led coverage of social business and education technologies and continues to contribute in those areas. He is the editor of Social Collaboration for Dummies (Wiley, Oct. 2013) and ... View Full Bio
InformationWeek Tech Digest August 03, 2015The networking industry agrees that software-defined networking is the way of the future. So where are all the deployments? We take a look at where SDN is being deployed and what's getting in the way of deployments.