3 ms·
Slow, legacy backend systems are not an intractable problem. You can do things such as copy the data to a faster cache, or you use some kind of queuing system s
by ams6110 13y ago
Slow, legacy backend systems are not an intractable problem. You can do things such as copy the data to a faster cache, or you use some kind of queuing system so that queries are processed only as fast as the backend can handle (of course the frontend needs to be able to "check back later" for the results).
This does support the widely held disbelief that this system will be fixed anytime soon. Clearly the management of the project and the design of the architecture are/were fundamentally flawed, and its very unlikely that it can be fixed in 30 days or whatever at this point.
- hga 13y agoIndeed, as you note there are a bunch of fixes possible for slow back ends. A lot of the data is sufficiently static (e.g. from the IRS, what are the numbers for your 2012 taxes, what's your withholding to date for 2013?) that occasional exports to a database inside of "healthcare.gov" might do the trick. In many cases setting up a fake server mimicking the legacy one with such a static data store behind it could get around some of the "can't change the architecture in 7 weeks" issue. Maybe (that deadline is for those who are learning Obamacare outlawed their old policies, 16 million by one estimate for that subset). We've also read that Experian is doing both identification and income verification, so they're probably not as hopeless. The management was, as just about everyone is noting, fatally flawed. However it's been reported to have changed, to QSSI becoming the integrator, and the fix-it czar is saying the right reality recognizing things, like the top item on his punch list is to stop sending garbage to the insurers. Presumably the managers still in the chain of command at the White House on down have been convinced to stop making requirements changes.... We'll see.
- vinhboy 13y agoRegardless of how hard it was to make a functioning "data hub", they should have, at the very least, built a functioning registration system that is independent of all other fail points. This way, at the very least, they could have the names and contact information of everyone who wanted to fill out a form. Then they can go back and process the forms at a later date.
- hga 13y agoSupposedly the problem there was a very late change from somewhere in the White House to CMS, in August or September, to preclude the possibility of window shopping and require registration with a lot of verification up front. E.g. we know Experian is part of that process, said to be for identification and income verification. It's been reported that people who don't have credit records (e.g. those sufficiently ill they've stayed under the care of their families) get told by Healthcare.gov to contact Experian, who then upon discovering they don't have a record of them tells them they have to get the Healthcare.gov people to create a “Manual Process Identity Proof” ... which few if any of them know how to do, or whom to send someone to.
- lnanek2 13y agoThat's what I hated most about healthcare.gov. Other sites I could get a quote quite easily and decide to go with them or not. healthcare.gov had a bunch of forms that didn't work so I couldn't get a quote after hours of trying. Even if I let long loading pages sit there for long periods of time, some failed out and other times my data was lost.