We have two goals when de-identifying the records within a database. Simultaneously, we intend to: remove the personally identifiable characteristics of individuals, and retain the integrity of the records for analysis and reporting. As soon as we set out to establish the business rules for de-identifying individual records, the paradox of these goals becomes apparent. The message in this paper about de-identification is: do it with full knowledge of the degradation of the research and analytic value of the database; do it at the least disturbed level allowable; or better yet, don’t do it. The twiminar discusses how to de-identify databases and mask small cells in reports. Polititech is introduced as the data governance process of managing the political and technology issues related to information systems, including de-identification.
Click here to read the complete white paper on De-Mystifying De-Identification.
De-Identification: Follow & respond to tweets about #deidentification of #databases. #ESPTwiminar5.1 #ESPTwiminars https://t.co/mYqgzHiu01
— ESP Solutions Group (@espsg) November 14, 2016
#ESPTwiminar5.2 #ESPTwiminars: #Deidentification of #databases has 2 paradoxical goals. Remove personal info & retain analytic integrity.
— ESP Solutions Group (@espsg) November 14, 2016
#ESPTwiminar5.3 #ESPTwiminars: #FERPA & #HIPAA compete with the requirements of researchers for #DeIdentification of #databases.
— ESP Solutions Group (@espsg) November 14, 2016
#ESPTwiminar5.4: #Newtonsthirdlaw “equal/opposite reaction” is exponential in a #database with #deidentification degrading research.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.5: Lesson is do #deidentification with full knowledge of the degradation of the research & analytic value of the #database.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.6:#DeIdentification: 4 steps to protect #database identities: Security, authorize users, authenticate users, mask reports.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.7: #DeIdentification: 1st step to protect identities is always secure the #database from unintended disclosure.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.8: #DeIdentification: 2nd step to protect identities is authorize #database users for acceptable purposes.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.9: #DeIdentification: 3rd step to protect identities is authenticate #database users to control access.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.10: #DeIdentification: 4th step to protect identities in a #database is #maskingsmallcells in published reports.
— ESP Solutions Group (@espsg) November 16, 2016
#ESPTwiminar5.11: #DeIdentification success in any #database depends upon an effective #DataGovernance policy with 3 processes.
— ESP Solutions Group (@espsg) November 17, 2016
#ESPTwiminar5.12: #Database #Deidentification #DataGovernance 1st process is official analysis & reporting from #SLDS.
— ESP Solutions Group (@espsg) November 17, 2016
#ESPTwiminar5.13: #DeIdentification #DataGovernance 2nd process is #RandE from a de-identified #database. #researchandevaluation
— ESP Solutions Group (@espsg) November 17, 2016
#ESPTwiminar5.14: #DeIdentification #DataGovernance 3rd process is #maskingsmallcells in public reports from the #database.
— ESP Solutions Group (@espsg) November 17, 2016
#ESPTwiminar5.15: #DeIdentification #DataGovernance is now known as #Polititech–the merging of political mandates with the #technology.
— ESP Solutions Group (@espsg) November 18, 2016
#ESPTwiminar5.16: Click here to access you #DeIdentification badge https://t.co/59p9ZEh01w. Thanks for participating in our #ESPTwiminars.
— ESP Solutions Group (@espsg) November 18, 2016
Click here to read the complete white paper on De-Mystifying De-Identification.