The Affordable Care Act is technically too big

The Affordable Care Act shortfalls are not something software can solve Photo: Computer failure/ google.plus

MISSOURI, October 14, 2013 — According to John McAfee one of the main problems with the Affordable Act is its technical shortfalls. According to McAfee, “Here’s the problem: It’s not something software can solve,” McAfee continued. “I mean, what idiot put this system out there and did not create a central depository? There should be one website, run by the government, you go to that website, and then you can click on all of the agencies. This is insane. So, I will predict that the loss of income for the millions of Americans, who are going to lose their identities — I mean, you can imagine some retired lady in Utah, who has $75,000 dollars in the bank, saving her whole life, having it wiped out in one day because she signed up for Obamacare. And believe me, this is going to happen millions of times.”

To resolve the problems, personnel must first identify and document the issues. This would involve all the end users, policy, technical, in addition to systems that interface with the core applications such as insurance companies, state exchanges, doctors and all government agencies that are involved such as the IRS.


SEE RELATED: History for the young and memories for the seniors


They must then coordinate and obtain sign offs from the responsible persons to the completeness and accurate identification of the problems-document.

Finally, they need to identify the functions and supporting applications of the act that can be isolated to be re-done. To support this action, document the tangible or in intangible benefits for the end users and all others who are involved during the implementation and production of this segment of the Affordable Act. 

The end users will then resolve those technical, policy and operational problems that impact these applications. Technical personnel test the applications. When complete, the technical personnel will migrate the solutions to a test bed to involve potential production applications, hardware and networks.

Upon completion of this test and migration, system engineers will set up a test facility, employ users from a diverse cross section of the population to test the system. This will be a continuing process involving identifying, fixing and re-testing the system. This will be a live test of the technical systems involved in the Affordable Care Act.


SEE RELATED: The blame game


After that test phase, the system will be available to the general public. A pilot test will take place in a single state. If the system passes that test, the system will then go live to the rest of the nation.

IT personnel will continue this process with each application to ensure that it is functional.

Rather than risking choking by eating the whole cake at once, the government should distribute the Affordable Care Act in easily digestible pieces.

       However, that’s from a time and place I am from-


SEE RELATED: Behind the talking points on Obamacare



This article is the copyrighted property of the writer and Communities @ WashingtonTimes.com. Written permission must be obtained before reprint in online or print media. REPRINTING TWTC CONTENT WITHOUT PERMISSION AND/OR PAYMENT IS THEFT AND PUNISHABLE BY LAW.

More from Charles Vandegriffe Time and Place
 
blog comments powered by Disqus
Charles Vandegriff, Sr.

Charles is a fifty-four-year career in technology retiring at the directors level from three major corporations. Followed by three-plus years as a free-lance columnist, published three books, over three hundred speeches to senior organizations, radio interviews, one television commercial and finally married for sixty-five years, four children, seven grandchildren and thirteen great grand children. 

Charles is also a Navy veteran.

Contact Charles Vandegriff, Sr.

Error

Please enable pop-ups to use this feature, don't worry you can always turn them off later.

Question of the Day
Featured
Photo Galleries
Popular Threads
Powered by Disqus