In a lawsuit against the state, Oracle claims it is the victim of a smear campaign designed to obscure the state's project management failures.
Wearable Tech: 5 Healthcare Wins
(Click image for larger view and slideshow.)
Tired of being a punching bag, Oracle Corp. is hitting back at the State of Oregon over claims that the software company and the contractors it provided were responsible for the failure of the state's health insurance exchange to produce a functioning self-service website.
According to the lawsuit filed Friday, the state has been using a smear campaign to deflect attention from its own project management failures -- particularly constantly changing, never-finalized requirements that sabotaged the software development process. In addition to suing for unpaid consulting and licensing fees, Oracle used the filing to defend its reputation. "When the press reported that the exchange was not accessible for consumer self-service on October 1, 2013, public officials chose not to give a measured, fully informed response," the filing says. "Cover Oregon and public officials could have done two things in the face of those press reports: (a) own up to the management and technical challenges they had encountered and commit to a plan for resolving them; or (b) blame someone else. They chose the latter, and they fixed their sights on Oracle."
Independent investigations have cited the state's excessive reliance on Oracle as the turnkey provider of software and consulting services for the insurance exchange as one of the underlying causes of project failure. The software infrastructure for the project included Oracle Policy Automation, Siebel CRM, as customized and combined through the Oracle Enterprise Architecture. However, the project's auditors also put a large share of blame on the state for the way it managed the project. One of the main points Oracle hammers home is that it never had either the authority or the responsibility to act as the system integrator on the project. Though Oracle was a major player in the project, it was not the only contractor or technology provider, and the accepted best practice would have been for all of them to report to an integrator that could have acted as the general contractor.
The state elected not to hire a system integrator, instead choosing to assign that responsibility to its own personnel -- whom Oracle says were not up to the challenge. Project oversight responsibilities were actually split among several state organizations -- and shifted partway through the project from the Oregon Health Authority to the Cover Oregon organization created to run the exchange -- adding further confusion.
"Without a fixed scope for the project -- the equivalent of architectural blueprints -- no contractor could reasonably be expected to agree to work on a fixed-fee basis," Oracle states. Only the state organizations "could resolve the uncertainties regarding the overall scope and structure of the massive project, and because only Cover Oregon and the state agencies could demand changes in the project, those entities properly bore the inherent risks associated with failing to resolve them in a timely way."
Oregon Gov. John A. Kitzhaber, MD, has called for the state to sue Oracle, alleging that sloppy work by its contractors was a major cause of the insurance exchange's downfall. However, an analysis of the legal issues by The Oregonian newspaper concluded that Oregon would face an uphill battle to make the charges stick in court. Oracle also notes that the state has yet to file a lawsuit, suggesting that Kitzhaber's bluster is mostly about politics and public relations.
An enthusiastic backer of the expansion of access to health insurance under the Affordable Care Act, Kitzhaber made Oregon one of the first states to commit to creating its own online health insurance exchange and set ambitious goals for the project. Yet even though several other states that built their own insurance websites also failed to live up to expectations, Oregon alone failed to process a single self-service application online (instead funneling all applications through intermediaries). The federal HealthCare.gov exchange also failed to perform adequately for months after open enrollment began in October 2013, but it recovered in early 2014 after an intensive rescue by a SWAT team of developers.
Oregon now plans to abandon the online system created by Oracle and rely primarily on HealthCare.gov to provide the health insurance exchange services for its residents when open enrollment resumes in November.
Oracle claims that it didn't have to be that way. "By February 2014, a health insurance exchange website existed that included the citizen self-service functionality," Oracle's filing claims. "Cover Oregon did not disclose that information to the public and did not open the working self-service portal for individuals, for unexplained reasons of its own." State officials have said the software was still too buggy for public release and never rose to an acceptable level of quality.
The real bone of contention is over the cause of the bugs and the general dysfunction surrounding the project. Oracle leans heavily on reports filed while the project was under way by Maximus Inc., a contractor that the state retained specifically to monitor the project and the risks associated with it. Maximus kept reporting that the project faced a high risk of failure, and that state officials were not coordinating their oversight effectively.
In one section of its legal complaint, Oracle particularly points to infighting between the Oregon Health Authority (OHA) and Cover Oregon (CO):
For example, at one point, the OHA's chief information officer complained to Oracle personnel that Cover Oregon's efforts were "becoming highly disruptive to the Modernization effort," and that her team felt "they are being run over" by Cover Oregon. As a result, one organization would make decisions without taking account of implications of that decision for the work being performed for the other organization; the result was
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 Must Reads Oct. 21, 2014InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.