3 ms·
From the convoluted articles I've read, not only was the main bottleneck in the identification process, but the issue seemed to be that the authentication was n
by danso 13y ago
From the convoluted articles I've read, not only was the main bottleneck in the identification process, but the issue seemed to be that the authentication was necessary to just show the plans, because the gov wanted to make sure you were 25 before showing you a range of prices...was that the case? If so, whatever happened to letting people just browse the entire table of prices....remember when people had to look things up and scan tables once in awhile, instead of living in a Minority Report world where every piece of info is handcrafted to the user?
I wonder how much of Healthcare.gov's problems could have been eliminated if the sign up was more modular...users were allowed to browse before signing up for anything. Then they could sign up via email and tentatively pick a plan. Then in 3 days, they go through the full authentication process...this is similar to how Amazon does things...you can sign up without a credit card, you can browse without signing up, and you don't go through the processing bottleneck till the very end.
- hga 13y agoThe contractors were ordered in August to change the system to require up front registration and submission of "correct" information on penalty of perjury, no window shopping allowed, nor checking out "what if" scenarios (e.g. using the Kaiser Foundation's calculator, someone was unable to find any scenario where being married wasn't more expensive, and of course subsidies are based on income, and that can be very flexible for a lot of people). Since then window shopping has been allowed, but I don't know if the "under penalty of perjury" bit was dropped. As to "what happened", I'll just point you at this Washington Post article and let you come to your own conclusions: http://www.washingtonpost.com/politics/challenges-have-dogged-obamas-health-plan-since-2010/2013/11/02/453fba42-426b-11e3-a624-41d661b0bb78_print.html http://www.washingtonpost.com/politics/challenges-have-dogge... Note also the front end traffic jam has avoided sending the insurers more garbage 834 EDI enrollment and cancellation transactions than they can manually clean up by contacting enrollees. That's the #1 thing to correct according to the fix-it czar. And I do agree with you, an Amazon system, which I'm sure is based on the BASE eventual consistency back ends, e.g. you don't get your confirmation email until it decides who "won" the last copy of an item, would have been a lot better. But then again the contractors were doing a lot less of that sort of top level design that you'd think (see the Post article).