1. Lisa Neidert Population Studies Center May 26-28, 2010 Ann Arbor, MI Third Working Group on Data Access

2.  Overview of our services  Shortcomings & Fears  Strengths & Wish List

3.  Application Process  Administrative Records  Secure Computing Environment  Education/Compliance  Contracts Database

4.  Help with IRB process Including renewals, amendments, close-out  Contract Templates from previous applications Signatures/affidavits Material Transfer forms  Develop security plan What does contract require?

5.  License/Renewal Dates  Personnel on contracts/licenses  Annual Reports/Inspections  Hostage Projects  Media tracking and storage

6.  Environments Stand-alone Networked Enclaves [MiCDA/Michigan Research Data Center]  Conditions Bake-in conditions Notifications & Education

7.  What are the conditions of the contract? Most contracts have 25+ conditions Plus the security conditions  What conditions does the researcher control or are relevant to the researcher? Many fewer  Reminder of conditions  Monitor conditions

8.  Data for statistical use only  No re-distribution of data or informal sharing  Work from location described in contract  Office security Locked door; Media locked up (if relevant)  Comply with computer/printing conditions  Comply with disclosure conditions

9. Disclosure Conditions Add Health To avoid inadvertent disclosure of persons, families, or households by using the following guidelines in the release of statistics derived from the Data Files. 1. In no table should all cases in any row or column be found in a single cell. 2. 2. In no case should the total for a row or column of a cross ‑ tabulation be fewer than three (3). 3. 3. In no case should a cell frequency of a cross ‑ tabulation be fewer than three (3) cases. 4. 4. In no case should a quantity figure be based on fewer than three (3) cases. 5. 5. Data released should never permit disclosure when used in combination with other known data. HRS Magnitude Data: Ensure that no cells/strata with n < 3 are produced. Frequency Data: Apply a marginal threshold of n >= 5 and cell threshold of n >= 3 to all tabulations. Protecting against complementary disclosure: Additional cells may be suppressed, i.e., complementary disclosure, to make sure the primary suppressions cannot be derived by subtraction from published marginal totals. No geography below Census Division NCES Licensee shall provide IES a copy of each publication containing information based on subject data or other data product based on subject data before they are made available to individuals who have not executed an affidavit of nondisclosure. NSF The Licensees shall ensure that all printouts, tabulations, and reports are edited for any possible disclosures of Subject Data using generally accepted methods. Principal Researcher shall provide SRS a copy of all or sufficient portions of each paper, report, or other data product containing information based on Subject Data at least forty-five (45) days prior to its submission for publication review, publication or other dissemination to anyone not listed in this license.

10. Disclosure Conditions PSID Information regarding the specific neighborhoods (counties, census tracts, Block Numbering Areas, Enumeration Districts, Minor Civil Divisions/Census County Divisions, Census Places, or 5-digit ZIPCodes) in which individuals or families resided, including the identification codes for the neighborhoods or any exact counts (total or for any specific characteristic) of the number of persons, families, households, or housing units in the neighborhood. The “PSID-Geocode Match Files” are Sensitive Data Files. NIS F. Restricted Data will be used only to generate statistical summary information that does not permit the identification of any individual person, family, household, employer, or institution. To avoid inadvertent disclosure of persons, families, households, or institutions by using the following guidelines in the release of statistics derived from the dataset. a. In not table should all cases in any row or column be found in a single cell. b. In no case should the total for a row or column of a cross-tabulation be fewer than three. c. In no case should a cell frequency of a cross-tabulation be fewer than three cases. d. In no case should a quantity figure be based on fewer than three cases. e. Data released should never permit disclosure when used in combination with other data f. No geographic unit (state, county, metropolitan area, city, etc.) with fewer than 100 NIS respondents will be tabulated separately. CMS The User agrees that any use of CMS data in the creation of any document (manuscript, table, chart, study, report, etc.) concerning the purpose specified in section 4 (regardless of whether the report or other writing expressly refers to such purpose, to CMS, or to the files specified in section 5 or any data derived from such files) must adhere to CMS’ current cell size suppression policy. This policy stipulates that no cell (eg. admittances, discharges, patients) less than 11 may be displayed. Also, no use of percentages or other mathematical formulas may be used if they result in the display of a cell less than 11. By signing this Agreement you hereby agree to abide by these rules and, therefore, will not be required to submit any written documents for CMS review. If you are unsure if you meet the above criteria, you may submit your written products for CMS review. CMS agrees to make a determination about approval and to notify the user within 4 to 6 weeks after receipt of findings. CMS may withhold approval for publication only if it determines that the format in which data are presented may result in identification of

11. Contracts Database: Administrative

12. Contracts Database: Media

13. Contracts Database: Documents

14. Contracts Database: Closeout

15. Contracts Database: Conditions

16. Keeping track of conditions

17. LowCard$.com

19. Shortcomings & Fears

20. Strengths of Open AccessWish List Preferred venue and cost-effective although requires a great deal of staff time and expertise. Dislike oddities in contracts/data protection plans; over time DSDR may help solve this We know our research community and communicate with them; know their foibles Love to see more harmonization of contracts – less hope for data disclosure conditions We understand data and the issues associated with disclosure Trust our judgment We appreciate all the vulnerabilities in a non-enclave environment Dislike frequent password changes; Practical & Informed: Password strength Application materials, contract conditions, security requirements on-line.