Posted on 10/18/2013 8:25:36 AM PDT by Kaslin
I can't believe I'm writing this sentence, but Obamacare's exchanges appear to somehow be more deeply corrupted and broken than previously known. If there were words more impactful than "meltdown" and "trainwreck," I'd use them. Instead, I'll simply present the facts as they continue to come to light. USA Today:
The federal health care exchange was built using 10-year-old technology that may require constant fixes and updates for the next six months and the eventual overhaul of the entire system, technology experts told USA TODAY....Recent changes have made the exchanges easier to use, but they still require clearing the computer's cache several times, stopping a pop-up blocker, talking to people via Web chat who suggest waiting until the server is not busy, opening links in new windows and clicking on every available possibility on a page in the hopes of not receiving an error message. With those changes, it took one hour to navigate the HealthCare.gov enrollment process Wednesday. Those steps shouldn't be necessary, experts said..."The application could be fundamentally flawed," said Jeff Kim, president of CDNetworks, a content-delivery network. "They may be using 1990s technology in 2.0 world." Outsiders acknowledged they can't see the whole system, but they said they feared HHS built a system that will need an expensive overhaul that would cause more headaches for people trying to buy insurance.
The problems are so deeply entrenched that the federal exchanges' week-two enrollments do not appear to have improved at all over the first week's feeble stats. Expert Bob Laszewski:
There was no progress for the new federal health insurance exchange's information technology and enrollment challenges in its second week. At the end of week two of the Obamacare launch, health plans were generally seeing no more enrollments per day then they saw in the first week. As troubling, the backroom issues plaguing the connection between health insurers and the federal government had not been resolved and there is no indication from the feds when they will have these things cleared up. My sense is that the feds, based upon the number of enrollments they have sent to the insurance companies, enrolled about 10,000 people in the first week (about 5,000 single and family contracts) and another 10,000 people in the second week in the 36 states using the federal exchange...Most states running their own exchanges aren't doing a whole lot better.
One of those states is Maryland. I noted at Hot Air this week that Maryland's strongly pro-Obamacare governor was forced to admit that his state's exchange likely won't be functioning for at least another 4-6 weeks. Mary Katharine Ham followed up on this point, explaining why Maryland's big whiff should be profoundly worrying to the Obama administration:
This is the state that’s a perennial leader in the number of health care mandates it places on businesses and consumers, and has the army of health regulatory bodies to match. Even when the administration delayed important rules to prevent them becoming election fodder, Maryland forged ahead without. Formed by state legislation in early 2011, the Maryland Health Benefit Exchange Board met at least once a month starting in June 2011 to plan the build. The board, ironically, has a thorough and functioning website of its own. A calendar of events lists more than 200 meetings of exchange officials, working, business, and community groups about the exchanges over the last two years...Jonathan Cohn, a health care reporter at The New Republic and an Obamacare supporter, declared in 2011, “none are moving as quickly, or effectively, to follow through on the law as Maryland Governor Martin O’Malley.” ... If there was ever a state that was, in good faith, trying hard to get an exchange operational, Maryland was it. And, yet, Maryland produced a disaster that may not be fixed in time to prevent the “death spiral.”
Be sure to read the entire piece for bonus comments from both Obama and O'Malley, prematurely congratulating themselves on Obamacare -- which they've argued is a testament to the virtues of expansive government. Oops. Meanwhile, the "death spiral" concept is really important to this entire discussion. Megan McArdle explains it well in her indispensable Bloomberg piece, but the idea is straightforward: Because the exchanges are so dysfunctional, only the most motivated consumers are likely to tough it out and work really hard to enroll. These people, for obvious reasons, tend to be sicker, older folks with pre-existing conditions. So if they flood into the market --while young and healthy people do not (thus off-setting the others) -- insurance companies will have no choice but to jack up rates on everyone to compensate for their new, unusually costly, enrollees. This, in turn, will drive younger, healthier consumers to exit the market, making the problem worse. Unless Obamacare gets its act together very soon, and manages to get millions of "young invincibles" to voluntarily overpay for coverage (rather than pay the cheap penalty tax), the entire insurance market breaks down. As Laszewski's analysis demonstrates, the sign-up rate is pathetically low -- so much so that HHS is now denying that they ever had monthly enrollment goals in the first place. Yuval Levin, a conservative healthcare wonk, has written a lengthy and important piece at National Review, based on numerous discussions with Obamacare and insurance officials. Behind the scenes, chaos and "restrained panic" reigns:
If the problems now plaguing the system are not resolved by mid-November and the flow of enrollments at that point looks like it does now, the prospects for the first year of the exchanges will be in very grave jeopardy. Some large advertising and outreach campaigns are also geared to that crucial six-week period around Thanksgiving and Christmas, so if the sites are not functional, all of that might not happen—or else might be wasted. If that’s what the late fall looks like, the administration might need to consider what one of the people I spoke with described as “unthinkable options” regarding the first year of the exchanges...The tone of the CMS officials who spoke with me was a kind of restrained panic. Among the insurance company officials (who, I should stress again, work in the Washington offices of some large insurers, and so are basically policy people and lobbyists), there was much less restraint. The insurers are very, very worried about the viability of the exchange system..And they believe, as the CMS officials I spoke with do, that all of these problems will not be addressed immediately. No one wants to say how long it might take, and no one would share with me what estimates they might be getting from their contractors (whom they no longer trust anyway), but there has so far been relatively little progress and it seems like everyone involved is preparing for a process that will take months, not weeks.
Levin's sources (all Obamacare supporters, by the way) say that, paradoxically, the tiny trickle of enrollees is actually something of a blessing in disguise. Why? The back-end connectivity issues are so terrible, that an avalanche of "successful" sign-ups could cripple that part of the system. "Trainwreck" doesn't even suffice. And all this, despite three-and-a-half years of lead time (most of which the administration frittered away for political reasons), and a mammoth tech budget -- which tripled, and still resulted in failure. How the hell is Kathleen Sebelius' job secure? Finally, on the subject of rank political concerns, a new Politico report is as jaw-dropping as anything else mentioned in this post:
Facing such intense opposition from congressional Republicans, the administration was in a bunker mentality as it built the enrollment system, one former administration official said. Officials feared that if they called on outsiders to help with the technical details of how to run a commerce website, those companies could be subpoenaed by Hill Republicans, the former aide said. So the task fell to trusted campaign tech experts.
Having already punted reams of key regulations past the election -- making the timeline for a relatively seamless launch all but impossible -- the administration decided against seeking certain outside expert assistance to develop Obamacare's exchanges because...they were afraid that Republicans might find out how badly things were going. So they kept it all in-house, hush-hush, beyond the reach of GOP investigators, and, you know, the public -- a large portion of which would be relying on these sites for their healthcare. Allahpundit encapsulates things well: "Between this and the fact that HHS deliberately hid the price of insurance behind a reg wall on Healthcare.gov to reduce 'rate shock,' the grand takeaway about the website’s failure is that O and his team made it much worse than it needed to be because they were terrified of transparency. And the reason they were terrified of transparency...is because they know they’ve delivered a bad product." This crosses the line from gross, mind-blowing incompetence to corrupt, myopic malpractice. I'll leave you with Alan Colmes (!) calling for a one-year delay of the whole enchillada. Bear in mind that this segment aired before any of the above information became public:
Alan Colmes: The Implementation of Obamacare has been Terrible ... Have a Delay on It
Sure, they've royally screwed up the entire website beyond all comprehension via a combination of ineptitude, arrogance and corruption -- but the program itself will be great! Good luck with that argument. Tick tock, Mr. President. Were Republicans right about delaying the big government mess you've created? Or are you going to forge ahead to save face, harming millions of people in the process?
"The federal health care exchange was built using 10-year-old technology ..."?
I don't think they are talking about hardware. This is a failed software development program.
So what is 10 year old software technology?
How is that possible?
What would you use to build a website like this— Dreamweaver or something comparable? And wouldn’t programs like this be updated to HTML 4 or 5 by now?
You don’t even really need to code HTML anymore, just know about it. The programs do it for you and most are on HTML 4, I think.
I heard on one of the FOXNEWS shows last night that the company is CANADIAN. We paid them close to 100 million dollars for this site. They chose to use open source software that is available for free, is old, and outdated. They hid this fact by removing the required for licensing name of the company on the bottom of each page.
Whether any of this is true, I do not know as I did not download the software and review it. If so, the Canadian company made a tidy profit on the deal. LOL
Obama's friends.
The Democrat Party.
Secretly funneled to unions.
Vote rigging operations in the various states.
Bribes to pay off MSM propagandists.
Various members of Congress to buy votes.
Etc. The usual places including Obama's pocket.
you are bad
That has to be the only explanation.
OMG! Campaign techs! They are so screwed, yup now I believe CGIs were used to build the Obamacare web site. FOOLS! Nothing wrong with CGIs, fine for a low volume, non complex data web site like a candidates campaign site.
YEP...what YOU said...the WEBSITE is NOT the problem....it’s the attempt to CONTROL everyone’s life...they are finding it is a little more difficult than they thought.
On inside information, this statement is so true. The reason for Obama Waivers was not only about political payback, but that there was NO way the government and contractors could handle the work. The government/contractors still haven't trained everyone. Offices are still under construction.
Reported that if an application happens to come through for a small business it goes to the bottom of the pile because there is nothing set up to process.
The government is so far behind on individuals that there is not way they are ready to process all the entities that must sign up next year when the waivers expire.
Visual basic, the old interpreted version. ;-)
At least it’s not written in Perl.
CGIs, Common Gateway Interface, popular back in the mid-late 90’s but the tec was replaced by servlets, and servlets were were replace by enterprise beans. I am retired now so I don’t know the latest server tec today. 4 years ago it was EJBs (EJB3) Enterprise Java Beans.
"What difference does it matter at this point in time, anyhow???"
Open source is usually good code as long as it is well vetted (used a lot by lots of folks), but it is a serious (criminal) no no to remove the open source header, if that was done then someone is in deep do do.
They probably think Linux is a character from Peanuts comic strip.....................
Thanks for posting
I should have added that there is nothing wrong imo with php and open source software for a website. The problem arose, i believe, when the 0 admin reviewed the site and wanted it all changed to force users to input their information prior to seeing the pricing structure. This would cause a rewrite of much of the software where the company would have to actually have some knowledge of php. The 0 admin also waited until the last minute which made it impossible to get the work done on time.
I don't blame the Canadian developer at all. The 0 admin shouldn't have waited until the last minute to review the site and should have given the development team their requirements from the start. Changing boats in midstream is never a good idea when there are written in stone due date on project completion.
Why should I laugh. I agree with you
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.