Quickly fixing Obamacare’s most visible problems could be a disaster for the health care law.
By now, pretty much everyone knows that HealthCare.gov, the main portal to access the law’s new insurance exchanges, doesn’t work. When the site first launched, hardly anyone could create an account to begin shopping for coverage. And though the registration problems have gotten better, enrollment is still an uphill climb.
The site’s disastrous front end has overshadowed another set of serious problems on the back end. Insurance companies say they’re seeing widespread errors in the trickle of applications they do receive through the exchanges.
And until those errors can be fixed, it might be best to leave enrollment at a trickle.
“Is CMS stupid enough to fix the front end of this thing before they fix the back end?” asked Bob Laszewski, a health care consultant who works closely with insurers.
In Laszewski’s view—and he’s hardly alone—the fact that users can’t easily log in to HealthCare.gov is a blessing in disguise. Sure, it’s a political and public-relations headache for the White House, but leaving the back-end problems unchecked could be a bigger one.
Insurance companies are seeing a range of errors in the applications they receive through HealthCare.gov. One anecdotal report said a man showed up as having three spouses, two of whom were actually his dependents.
Insurers also say they’ve gotten an enrollment, followed by a cancellation, followed by another enrollment. They don’t know why, and in some cases, the various documents don’t have time stamps—so the insurance company doesn’t know which is the most recent and, presumably, the accurate transaction to process.
CGI, the contractor that built most of HealthCare.gov, downplayed the back-end errors during a congressional hearing Thursday.
“We have uncovered a number of those scenarios—not significant—but a number of them. “¦ Most of them are isolated, not across the board for all insurers,” CGI’s Cheryl Campbell said.
But an insurance industry official said the problems are actually much more widespread than Campbell indicated. Insurers simply don’t have much confidence in the data they’re getting, even the applications that don’t contain obvious errors.
Laszewski questioned whether CMS is truly working overtime to fix the site’s front-end problems, in which case “they’re about to flood the insurance companies with crummy data,” or quietly letting the sign-up problems linger to help identify and fix back-end errors.
The latter would be the smarter move, he said, but it would also be an acknowledgement of serious problems in the enrollment process.
“They’re either really stupid or they’re smart. And if they’re smart, this is de facto shut down,” he said.
Right now, the flow of new enrollees from HealthCare.gov is so slow that insurance companies can monitor applications by hand, tracking down inconsistencies one by one. But if hundreds or thousands of people start to come through the system, insurers won’t be able to keep up—and they could end up getting the blame from angry customers for problems they didn’t cause.
Insurers also don’t yet know the extent of the exchanges’ bad-data problems.
HealthCare.gov batches and sends over all of its enrollments every night. But only two of the state-run exchanges (which total 14, plus the District of Columbia) are submitting enrollments to insurance companies; the rest are holding off until at least Nov. 1, while they continue to test their own systems.
States are giving each insurer a sense of how many people signed up for each plan, but the companies don’t know who their new customers are—whether they’re the young, healthy consumers insurers covet, or older, sicker enrollees who are more likely to file expensive claims.
Chris Clark, the technology program manager for Kentucky’s state-based exchange—widely considered one of the best in the country—said the state and insurance companies agreed early on to a delayed submission process. Kentucky is still testing the accuracy of the enrollment forms it will submit to insurers.
“We’re very confident that that process is going to work smoothly,” Clark said.
What We're Following See More »
The Supreme Court announced "that it would consider a challenge to President Trump’s latest effort to limit travel from countries said to pose a threat to the nation’s security." The case concerns Trump's most recent attempt to make good on a campaign promise "tainted by religious animus" and only questionably justified by national security concerns. The decision to take the case, called Trump v. Hawaii, comes almost exactly a year after Trump issued the first travel ban. The ban under consideration affects Iran, Libya, Syria, Yemen, Somalia, Chad and North Korea.
Trump wants to move the two grants, the High Intensity Drug Trafficking Areas grant and the Drug Free Communities Act, to the Justice and Health and Human Services departments, respectively. This would result in a $300 million plus reduction in funding, about 95 percent of the cost of the Office of National Drug Control Policy. "'I’m baffled at the idea of cutting the office or reducing it significantly and taking away its programs in the middle of an epidemic,'" said Regina LaBelle, who served as ONDCP chief of staff during the Obama administration. This is the second time the Trump Administration has proposed gutting the agency.
A new report assembled by the watchdog group Citizens for Responsibility and Ethics in Washington has identified more than 500 potential conflicts of interest in President Trump's first year. First, the report notes, Trump spent 122 days at his properties during his first year. He has been accompanied by 70 federal officials and 30 members of Congress. "Second, far from this signaled access to power being an empty promise, those who patronize President Trump’s businesses have, in fact, gained access to the president and his inner circle." Lastly, about 40 special interest groups and 11 foreign governments have held events at Trump properties.