Wednesday, December 4, 2013

Enrollment data for 1/3 of Obamacare enrollees filled with errors; Means they won't have insurance Jan 1

Even though the Obama Administration is claiming victory - that Healthcare.gov is fixed, there remains numerous problems including ID verification and errrors in the data of enrollees. The enrollment records for about 1/3 of the Americans who have chosen health plans contain errors generated by the computer system which means that they won't have coverage starting month. Someone is hurt, goes to the doctor and gets a nasty surprise finding out they don't have insurance. .
The errors have affected roughly one-third of the people who have signed up for health plans since Oct. 1, according to two government and health-care industry officials. The errors include failure to notify insurers about new customers, duplicate enrollments or cancellation notices for the same person, incorrect information about family members, and mistakes involving federal subsidies. The errors were the subject of a meeting Monday between administration officials and a new “Payer Exchange Performance Team” made up of insurance industry leaders.
The errors mean that tens of thousands of consumers may not have coverage Jan. 1, because the health plans do not yet have accurate information needed to send them a bill. Under the law, consumers don't have coverage unless they have paid at least the first monthly insurance premium. The WH says that they have a team of experts working to make sure that enrollement data is correct.
“We’ve got a team of experts already working closely with issuers to make sure that every past and future 834 is accurate. We’re confident they’ll succeed,” White House senior communications adviser Tara Mc­Guinness said. The 834s are nightly enrollment forms sent to insurers to tell them who their new customers are.
The White House blamed the errors on users saying that errors were generated by the way people were using the system. Another senior official on the project said, such as clicking twice on the confirmation button or moving backward and forward on the site.
Another error involved the social security numbers. In a call with reporters Monday, Julie Bataille said that about 80 percent of the errors with 834 forms — the enrollment data — came from “one bug that prevented a Social Security number from being included. That caused the system not to generate an 834.”
“That bug has now been fixed and [that part] is now working properly,” Bataille said. She said that CMS also has addressed smaller bugs, including one that caused family relationships to be coded inaccurately (a child, for example, might show up as a spouse).
With recently implemented application fixes, the team reduced the instances of when data was not generated on 834 forms from 3 percent last week to 0.5 percent now, according to senior officials.
Administration officials said that by 6 p.m. Monday, the Web site had had close to 800,000 unique visitors and was set to pass that mark by the end of the day. And the site processed 18,000 enrollments in the most recent 24-hour period, nearly double the previous record. But despite the fixes the site still malfunctioned. By late morning, when the number of people on the site was roughly 35,000 —15K short of the much touted 50,000 figure — the queueing system activated putting people in a waiting room of sorts. An internal report Monday showed that nearly 149,000 individuals have completed the enrollment process through the new online system.
A major error being generated by the system and a top priority for insurers to correct is the so called “orphan reports,” in which a new customer is excluded from reports sent to each health plan early every evening listing their new enrollees from that day.
“When plans have checked this, they realize there is a good number there is no record of,” said an insurance industry official. Last week, the official said, the online system sent one health plan a cancellation notice for a customer for whom the plan had never received an enrollment report.

No comments:

Post a Comment