ObamaCare Software Glitching as Launch Nears
It can't reliably tell people how much they have to pay
By Kevin Spak, Newser User
Posted Sep 20, 2013 9:01 AM CDT

(Newser) – The health-insurance exchanges that are at the heart of the Affordable Care Act reforms are supposed to go online in less than two weeks, but there's a pretty big problem: They don't work. The software the federal government is planning on using frequently miscalculates how much people need to pay for coverage, insurance executives and other sources tell the Wall Street Journal. For many insurers, tests that began this week had been scheduled to start months ago.

"There's a blanket acknowledgment that rates are being calculated incorrectly," one executive says. "Our tech and operations people are very concerned about the problems they're seeing and the potential of them to stick around." But the administration says the exchanges will open on Oct. 1 as planned, and Medicare says it's "confident" prices will show up correctly. If things go wrong, consumers will still have the option of enrolling the old-fashioned way with paper forms, but companies are worried about making a bad first impression on consumers.

More From Newser
My Take on This Story
To report an error on this story,
notify our editors.
ObamaCare Software Glitching as Launch Nears is...
Show results without voting
You Might Like
Showing 3 of 43 comments
Sep 22, 2013 11:49 AM CDT
I am sure they will fix it in two weeks, no problem. All they do is negative publicity to something that is real positive for millions of low income americans.
Sep 21, 2013 7:44 PM CDT
OMG...Just give the software a waiver and pile it with the rest of obama failures. Sorry, I forgot...he gave the order to kill bin laden, lol!
Sep 20, 2013 6:55 PM CDT
A clickbait non-story, written by people who have no experience with software roll-out. Don't panic over what's likely a misspelled function call, a bit of stray punctuation, bad escape sequences, or a little from column A, a little from column B, etc. At worst, perhaps someone misread a spec and built one component wrong. It happens, then it gets fixed.