akshay bhat

Unregistered less info
18 reputation
2
bio website
location
age
visits member for 1 year, 7 months
seen Dec 19 '12 at 9:57

Dec
18
comment A question regarding relevance of vulnerability of MD5 when linking multiple records together
Thanks for your answer, This data is actually publicly distributed and available for purchase. Hence the use case here is only to link multiple prescriptions together consistently without actually revealing patient identity/identifier. Most likely the personal identifier would be something more complicated than a simple SSN, most likely a synthetic identifier which would be virtually untraceable. (unless of course you rely on other approaches such as re-identification.) Thanks again.
Dec
17
comment A question regarding relevance of vulnerability of MD5 when linking multiple records together
Something like Patient name or SSN or some unique personal identifier. The hash would ensure that a multiple prescriptions of the same patient (as identified by the personal identifier) are linked to each other, without revealing the identifier itself. E.g. For each prescriptions you calculate a hash using MD5 for the patient identifier, and then all the prescriptions which have the same hash are linked to each other. A collision would result in two different patients getting their prescriptions mixed up which in turn would actually make re-identification harder.