Slashdot Mirror
Government Mistakenly Declares Deaths of Citizens
superbrose writes "According to MSNBC, thousands of U.S. citizens have wrongfully been declared dead, due to an average of 35 data input errors per day by the Social Security Administration (SSA). Many other agencies rely on the data provided by the SSA, such as the IRS. People who have been wrongfully declared dead face many problems, such as rejection of tax returns, cancellation of health insurance, and closure of bank accounts. The article states, 'Input of an erroneous death entry can lead to benefit termination and result in financial hardship for a beneficiary.' Apparently it is far easier to declare a person's death than it is to correct the mistake. It continues, 'Social Security says an erroneous death record can be removed only when it is presented with proof that the original record was entered in error. The original error must be documented, and the deletion must be approved by a supervisor after "pertinent facts supporting reinstatement" are available in the system.'"
http://alternatives.rzero.com/
on second thought, being dead hasn't stopped candidates from running for office before
Don't forget, being dead hasn't stopped candidates from winning, either!
~Philly
almost every time I come across a 'bug' in our ERP system, it's because a clerk did something wrong.
*That's* a bug in your ERP process. I've run projects that required large-scale, high-quality data entry. E.g., 600,000 French verb conjugations. Of the following factors:
- the extent to which the UI helps the clerk enter the data quickly and easily
- the extent to which intelligence can be and has been applied to detect errors in entered data via checks against other data sources and/or sanity checks, or to detect possible errors in entered data
- whether or not data was entered redundantly by multiple clerks and cross-checked
- how "wrong" the clerk was, that is, the overall error rate of the individual clerk
the latter was by far the least significant in every case.
That people type the wrong things sometimes is, for the most part, unavoidable. It's how you cope with that reality that makes the most difference.
In the case of the SSA, I'm surprised the false death rate is only 35 a year, I actually think that's an error rate to be proud of (out of 300,000,000 people in the US)
I'm a nature photographer.
Comment removed based on user account deletion
This is a bigger problem than the post alludes to. The Department of Homeland Security (DHS) put in to effect a new rule, called the "No-Match Rule" which requires an employer to terminate an employee when receiving a letter from the DHS or the Social Security Administration (SSA), that the new employee in question doesn't exist in the SSA database. There is a period of 90 days in which to contest the no-match rule but if you're not on top of things, your employer has to fire you.
Right now there is a stay on that rule ordered by a district court in California, but it goes to show you some small error can have big consequences. See AFL-CIO v. Chertoff, No. 07-4472 (N.D. Cal filed Aug. 29, 2007. Apparently the DHS is looking into revising the rule.
More here
But if you have an ID, it will be easier for you to prove you are alive - even if its canceled by mistake in a database.
How? If the database says you are dead, when someone scans the barcode it still says you are dead. Even if a government employee sees you appear to be alive and look like th eperson on the card, its going to take paper work and procedure to get that changed because often the people that you talk with (especially at the IRS) are not empowered to do anything of real value in this situation other than fill out a form.
Secondly, I know people who look like nothing like license card. They gained weight, dyed their, had surgery, are sick, etc etc and have grief going into a bar much less deal with the government.
"I am the king of the Romans, and am superior to rules of grammar!"
-Sigismund, Holy Roman Emperor (1368-1437)