OT: front and back end problems of ACA solved by open source zero cost programs

While not metal working related, there has been considerable discussion of the ACA/Obamacare act and implementation on the NGs.

It should be noted that nearly one billion dollars has been expended by HHS on software developmental costs for just the enrollment phase, with marginal results.

A small group of free lance web designers, over a long week-end and with the help of a case of Jolt cola [slogan: all the sugar and twice the caffeine] created an operational front end [the web page].

formatting link

Now another group of >>>student

Reply to
F. George McDuffee
Loading thread data ...

I think a lot of the issues are self inflicted,gov't bureaucracy,rules and regulations about contractors,put in place over the years by both parties for:

1) to make it easier for supporters of one party to get the contracts 2) to make it harder for supporters of the "other" party to get contracts 3) to make it look like the favoritism that is obviously happening in not really happening.

Add to this that all the insurance companies involved,each of which has business secrets it want to keep that way,but has to publish a lot of stuff that normally,while public,is generally not put out on a list right next to a competitor. It's probably not because the programmers are incompetent,it's probably because the job was broken up into segments,done by different contractors with out any communication between them - secrets to keep you know - and then assembled without testing. The fact that a bunch of programmers can throw a working facsimile in a few days proves little. That's not excusing the destructive bureaucracy the ACA programmers had to deal with,it's just that I get annoyed with all these useless idiots using problems like this just to prove a pointless political point.

Reply to
Just Me

formatting link

Reply to
PrecisionmachinisT

It's nonsense. Somehow, I seriously doubt that the students implemented the whole 3,000-page law, plus all the subsequent rules. Or interface to all the required legacy databases that cover the entire population. And so on. Probably built just the front end, the part people see. The back end is far larger.

As is designing it so 100,000 people can use it simultaneously. Think XMAS shopping for an idea of the scale.

Joe Gwinn

Reply to
Joe Gwinn

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.