3 ms·
California's exchange: 28k people signed up in the first week. Washington's exchange: 55k enrolled (mostly in Medicaid) in October, and another 40k applied for
by tzs 13y ago
California's exchange: 28k people signed up in the first week.
Washington's exchange: 55k enrolled (mostly in Medicaid) in October, and another 40k applied for coverage.
Colorado: 37k in October.
Kentucky: 32k.
New York: 47k.
There were some glitches here in Washington. They had stability and speed problems at launch. They took the site down for a few hours, and then overnight, for maintenance. Within 48 hours, it was fixed and has been stable ever since.
One of the keys to Washington's success was to treat the exchange as essentially a startup. They sought people to build the site who thought it was a great thing to do and found it exciting and interesting, not contractors who would see it as just more 9 to 5 work to do.
Article on the above: http://www.latimes.com/nation/la-na-washington-obamacare-20131113,0,4963580.story#axzz2kkXpE7MV http://www.latimes.com/nation/la-na-washington-obamacare-201...
- GVIrish 13y agoI don't know the specifics of the Washington healthcare exchange, but I can tell you right now, the healthcare.gov didn't fail because they chose contractors to do the job, they failed because of extremely incompetent management on the government side. Had a start up been chosen to do healthcare.gov, and none of the government management were changed, even the best start up would've failed too. The same contractors that did healthcare.gov (CGI Federal) also developed the Kentucky exchange, which has been lauded as one of the more successful state exchanges. If the contractor was the problem, you'd have expected them to fail in Kentucky too.
- rafaelsanp 13y agoNot calling you wrong, but it looks like there were concerns about the competence of the contractors[0]. It was certainly paired with bad management, though. http://www.npr.org/blogs/alltechconsidered/2013/11/15/245399200/internal-emails-reveal-warnings-healthcare-gov-wasnt-ready http://www.npr.org/blogs/alltechconsidered/2013/11/15/245399...