3 ms·
Of course it's sloppy to not have any date in the DB. The thing is -- we don't know why exactly it happened and what kind of procedure they follow or don't. May
by Muromec 2y ago
Of course it's sloppy to not have any date in the DB. The thing is -- we don't know why exactly it happened and what kind of procedure they follow or don't. Maybe there is a scan of the certificate somewhere and it's illegible and nobody cares, because it's not a problem really. Benefits are mostly being paid to people eligible and any effort to achieve better quality will waster more money than is lost to fraud. That's of course triggering every autistas mind, but so what?
It could also be that entries in the DB that are complete are not exactly correct or even belong to real people and of course there is fraud and corruption going on at least somewhere.
- fallingknife 2y agoThe cost benefit calculation is, of course, reasonable. But there are 2 things that need to happen here. 1. Run a complex process requiring human intervention to determine age where it is hard to determine 2. Enter the result of step 1 in the DB And it's pretty obvious that 99.99% of the cost of this is coming from step 1. So I find it completely implausible that just tracking the results here, when a single error could potentially result in a loss of hundreds of thousands of dollars, is not cost effective.