2 ms·
What happens in that case is they all do it anyway, except in a haphazard and careless way where you might get mixed up with someone else. Besides that, someti
by emodendroket 9y ago
What happens in that case is they all do it anyway, except in a haphazard and careless way where you might get mixed up with someone else.
Besides that, sometimes multiple entities do need to know who you are; how is it supposed to work if your insurer and your healthcare providers don't aren't able to match you up to one person?
- AnthonyMouse 9y ago> What happens in that case is they all do it anyway, except in a haphazard and careless way where you might get mixed up with someone else. It is possible to make things sufficiently mixed up that the entire consent-absent aggregation system falls apart. Prohibiting them from using social security numbers and otherwise not providing any alternative unique primary key would go a long way toward that end. > Besides that, sometimes multiple entities do need to know who you are; how is it supposed to work if your insurer and your healthcare providers don't aren't able to match you up to one person? You don't need a single global identifier for that. You can give your healthcare provider your insurance policy number.
- emodendroket 9y ago> It is possible to make things sufficiently mixed up that the entire consent-absent aggregation system falls apart. Prohibiting them from using social security numbers and otherwise not providing any alternative unique primary key would go a long way toward that end. Not really. Log onto Spokeo, look yourself up, and see how many errors there are -- but at the same time, how the data is "close enough" to be useful. All compiled without a single identifier like SSNs.