3 ms·
If anyone does do this, please don't enforce uniqueness. My dad is a doctor and he complains about medical software that assumes previously input data is correc
by Joeri 11y ago
If anyone does do this, please don't enforce uniqueness. My dad is a doctor and he complains about medical software that assumes previously input data is correct and does things like preventing inputting a new patient just because their ss id is supposedly already registered to someone else. Then there are the classic data validation mistakes like assuming everyone has a first name and last name (some foreign nationals don't), assuming everyone has a birth date (some people don't know this), assuming addresses have streets, etc... Doctors see patients from all over the world, and the world is a pretty diverse place.
- logfromblammo 11y agoIf anyone links the social security number to this, I will kill them myself, not only with just my bare hands and ten gallons of boiling rage, but using only the ring fingers. Ever try doing something with just your ring fingers? It's gonna be slow and clumsy. I was thinking more along the lines of just keeping a list of hundreds of millions of unique integers, and linking as many identifiers to them as are necessary. If you have a keyed database, it is essential to have unique keys for indexing. Identity records all over have all kinds of problems, mostly due to stupid assumptions--like assuming that a SSN always uniquely identifies one individual.