recommended reading

HHS Bought More Cloud Storage in the Days Before HealthCare.gov Launched

phloxii/Shutterstock.com

The agency in charge of HealthCare.gov bought an emergency cache of computing power from Verizon’s cloud division just days before the online insurance marketplace’s troubled launch on Oct. 1, 2013, contracting documents show.

The Centers for Medicare and Medicaid Services bought an additional $8.8 million in cloud computing power on Sept. 26 after stress tests revealed the site as it had been constructed could only handle about 10,000 concurrent users, far shy of its expected peak of 50,000 concurrent users, CMS said.

Verizon added that cloud space on Sept. 30, the day before HealthCare.gov went live, according to the notice posted on Friday to the Federal Business Opportunities contracting website. The move could add fuel to arguments the government was ill-prepared for the HealthCare.gov launch.

By late September, the cost of computer cloud space needed to share plan and price information with insurance seekers on HealthCare.gov and state-run Obamacare exchanges had already tripled to $37 million from roughly $11 million when Verizon’s cloud division Terremark first won the contract in 2011. The September modification brought that price tag to $46 million, more than four times CMS’ original estimate.

There was no requirement in Verizon’s contract that its cloud support a target number of concurrent users, so CMS was forced to purchase additional computing power, the agency said.

The document posted on Friday is a limited source justification. That means CMS bought cloud storage directly from Verizon because there wasn’t enough time to competitively bid for the service before HealthCare.gov’s planned launch four days later.

Federal contracting rules require agencies to post a justification for such non-competitive contracts within 30 days of implementing them. CMS did not immediately respond to a Nextgov query asking why this justification wasn’t posted until roughly four months later.  

HealthCare.gov performed disastrously upon launch, shutting most insurance seekers out of the site for several weeks. It has performed generally well since December, following a round-the-clock repair process.

House Republicans claim the site may still contain security gaps that could endanger insurance seekers’ personal information. CMS officials say the site meets all government security requirements and has never been successfully hacked. 

(Image via phloxii/Shutterstock.com)

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats

JOIN THE DISCUSSION

Close [ x ] More from Nextgov
 
 

Thank you for subscribing to newsletters from Nextgov.com.
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

    Download
  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

    Download
  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

    Download
  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download

When you download a report, your information may be shared with the underwriters of that document.