A Chaos-Driven Path to Single Payer?
Those who have resisted the idea that the HealthCare.gov web site and Obamacare in general may have been intentionally designed to create confusion and chaos as a means for imposing a single-payer healthcare system on a currently unwilling populace are going to have a tough time explaining away yet another recently discovered “quirk."
To be clear, I’m not claiming, as some have inferred from previous columns, that there is a widely orchestrated chaos-creation plan, or that any attempt to capitalize on the current bedlam to impose single-payer is destined to succeed. What I am saying is that the evidence supporting the idea that certain of Obamacare's key players are determined to try continues to mount.
The latest "nobody's this stupid and incompetent" revelation is that Obamacare's enrollment system "lacks a way for consumers to quickly and easily update their coverage for the birth of a baby and other common life changes."
Press reports indicate that it's literally impossible to add a new child to an existing health plan once a person or household has enrolled. That's not all. HealthCare.gov also cannot handle "marriage and divorce, a death in the family, a new job or a change in income, (or) even moving to a different community."
No one should try to verify the existence of these problems on their own. That's because the web site is such a security nightmare that outside IT experts have publicly stated that it’s too dangerous for a user concerned about the privacy of their personal data (i.e., anyone with a brain) to use. As if that's not enough, in late September, the chief information security officer for the Centers for Medicare and Medicaid Services "told congressional interviewers that she explicitly recommended denial of the website’s Authority to Operate." She "was overruled by her superiors."
As red flags for true intentions go, Obamacare's inability to accommodate common life changes is an even stronger indicator than the failures previously identified.
As to security, I suppose it’s possible for designers to be so ignorant that they believe it’s something they can layer in later instead of following currently accepted protocols which call for baking it in from the outset. As to the lack of progress in building a system to process billions of dollars in subsidy payments to insurers, it’s theoretically but barely conceivable that the administration is telling the truth when it insists, in essence, that “we just haven’t been able to get to that."
But HealthCare.gov's life changes bust takes things to a whole new level. Has anyone, anywhere, ever built an interactive database which is unable to interact, i.e., to handle fundamental changes in key information once it has been entered? Who would even think of doing this? It's overwhelmingly likely that a programming team would have to deliberately decide to exclude the ability to carry out such basic functions during the initial design process.