DHHS Preparing 'Tech Surge' To Fix Remaining Healthcare.gov Issues
itwbennett writes "It's no secret that the healthcare.gov website has been plagued by problems since its launch 3 weeks ago. On Sunday, the Department of Health and Human Services said that it's now bringing in the big guns: 'Our team is bringing in some of the best and brightest from both inside and outside government to scrub in with the [HHS] team and help improve HealthCare.gov,' the blog post reads. 'We're also putting in place tools and processes to aggressively monitor and identify parts of HealthCare.gov where individuals are encountering errors or having difficulty using the site, so we can prioritize and fix them.' Other emergency measures being taken as part of what HHS calls a 'tech surge' include defining new test processes to prevent new problems and regularly patching bugs during off-peak hours. Still unclear is how long it will take to fix the site. As recently reported on Slashdot, that could be anywhere from 2 weeks to 2 months."
Single payer - have everyone buy into Medicare. Done.
Defund the NSA, and repurpose their data center for this. Two birds with one stone.
"National Security is the chief cause of national insecurity." - Celine's First Law
"Our team is bringing in some of the best and brightest from both inside and outside government"
It's not about helping the poor; it's about feeling good for helping the poor. Whether the poor are helped or not is irrelevant.
Do you even lift?
These aren't the 'roids you're looking for.
Personally, I'm not that bothered by teething problems. Plenty of sites have experienced them. Yes, there are many ways they could have been avoided, but they weren't, and they will undoubtedl be fixed.
Even assuming that to be true, fixed by when? The law has hard-coded dates in it, and insurers have vast sums at stake predicated on the numbers and types of people signing up, the premiums they'll get, and the subsidies they'll receive. If things slip, lawsuits will fly and it's logical to assume that taxpayers will be on the hook for damages. Not to mention the people who are losing their coverage at work who were expecting to be able to sign up via the exchanges. This disaster has knock-on effects that will resonate thru all sectors of the economy and society, and to call them 'teething problems' is far too dismissive.
Thirty Million out of 300+ million supposedly don't have health insurance.
So, lets write a plan that affects all 300+ million instead of one that addresses the 30 million.
Brilliant!
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
then it is truly screwed, he is out of his depth on this. Those dreamy eyed fools who made the ACA did not realize the implications of it needing an massive IT infrastructure that cannot be crapped out in 3 years and tested for all of ONE FREAKIN DAY when it was completed this month (!!!!). pop up the popcorn kids, this train wreck will be worthy of a Fugative sequel
I'm sure there's tons of people salivating at the chance to jump all over this topic and say things like "classic government inefficiency at work." But the reality is that these kinds of projects happen every day in private sector companies. You only hear about them when they make the news. I've seen many companies throw out millions in sunk costs because they couldn't get an ERP system massaged enough to fit their business processes. Often, the companies realize too late that they're getting bled dry by outsourcing "partners" and getting nothing in return, then make the hard decision to just dump everything and try again.
Some of it may be leadership incompetence (analogous to CIOs getting swindled by consulting salesmen over copious rounds of golf and strippers) but HHS doesn't have hundreds of web developers on staff, and there would be a monster backlash if they actually did go out and hire them as permanent employees. IN the real world, they're forced to outsource to be "good stewards of the taxpayer's dollar" and end up getting crap. I can't believe that no one over the last 30 years has come to the realization that outsourcing always costs more, and results are not guaranteed no matter how much money gets flushed. What probably happened is that the project got awarded to the lowest bidder of the big consultancy firms, who promptly replaced all the super-geniuses they promised with new grads, and just kept collecting money.
A lot of private firms get fed up and just insource the whole thing, but I don't think the government has that option right now. Given the political climate, I'm sure every paper clip purchased is tracked by certain right-wing groups, and hiring hundreds of Federal employees certainly won't go over well. So, we'll just see the same consultancies who screwed up get rewarded to "fix" the problem. Just like in the private sector...
I think this might be the first goverment case of a large organization trying to execute a publicly facing software project and failing. For decades the goverment didn't do public facing benefit projects. If this all happened in the 90s you would have to sign up using paper forms and although it may have been slow and inconvenient by today's standards that's what the goverment had experience in doing, it probably would have worked just fine.
I think software/web centric failures like this are going to keep happening. Few organizations, especially those whose primary business isn't software, are good at implementing huge software projects. Most management doesn't know how to run software projects, budget departments dont know how to account for software projects. If the Social Security administration has a huge backlog of applications they just add more people to the workforce until they work through it. Now everything is different, it doesn't matter how many people and how much money you throw at it, it's going to talk a while to fix. Very few people in goverment, and very few members of the electorate understand how a software project is run, hence a "surge" to fix the problem. People understand that concept, they imagine tons of nerdy looking guys flowing into some building and typing furiously at a keyboard until the problems go away. Good imagery, not really accurate.
I'm actually really amused by all this, it's my job playing out on a national stage. Terrible software estimates, contractors failing to live up to contracts, unrealistic timelines, poorly understood requirements, angry management demanding all hands on deck, and unhappy users. Maybe now software management will become an academic subject and mandatory study for MBAs and such.
The Articles of Confederation have not been in use since 1789... so I think we can safely discard them in any discussion about modern states. One of my professors pointed out an interested change in linguistics after the Civil War. Prior to the war, "United States" was almost always a plural ("The United States are...") but after the war, it became a singular noun ("The United States is..."). The Civil War was basically the end of the question of state sovereignty in the US. It's also one of the reasons the Confederate States were a confederation (and not a federation)... confederate states are independently sovereign and can freely secede from the confederation, but in a federal government, they have shared sovereignty with the federal government at best.