These are the starting point for Alex Jackl's recommendation for PII data elements for CCC based on the National Institute of Standards and Technology (NIST) recommended PII data elements.
...
These elements were selected using the guidelines laid out by the National Center for Education Statistics and the the NIST guidelines for protecting sensitive information. Information on this can be found in the Data Management section of Confluence on this page:
above.
The core criterion for inclusion was not the sensitivity of the data but rather whether inclusion of the data in the report would allow a person to be uniquely identified and thus have their privacy compromised with only minimal effort on the part of the observer.
...
By obfuscation we mean that the report MAY contain the column but it would have a set of symbols ( for example XXXXX) to indicate that there was data but it was intentionally obfuscated. This minimizes the number of followup requests from people who might think the data was "accidently" left out.
The Obfuscated element list, with much more metadata (which tables and and specific applications the data elements came from, can be found on the "Obfuscated Element" tab in the Enterprise Data Dictionary for CCCApply which can be found below. That list has duplicated because the same elements often hsow up in multiple tables and in multiple applications. To generate the unique list below filter on "X" in the "Unique" column.
This enterprise data dictionary for CCCApply also has six other tabs - a domain summary list for each of the three CCCApply applications and a detailed field list of each of the three applications. The Obfuscation information can also be found in the detailed field tabs in the "Obfuscate" column.
...