IRP Data Security Training
IRP requires training for individuals whose work on an IRP project requires that they have access to Wisconsin State administrative data through IRP. Wisconsin state agencies approve research projects’ use of the data, and share this data on the condition that anyone who has access to the data complete the necessary training and adhere to IRP’s policies and procedures to protect research data. Because there are a number of UW research projects using this data, it is important that we comply with requirements from the state to maintain access for all of these projects. Training starts with the Data Security Manual:
Have I Completed All Of The Requirements For Access To IRP Confidential Data?
Reference this list to determine which steps you have already completed and which still remain (some requirements are completed annually). This checklist is also included in the packet of IRP data access forms.
Keep in mind that some of the items may not apply to you (for example: some projects do not require IRB approval, and some individuals will not need silo access)
I'm renewing access. What do I need to do?
Data access is renewed each year. For continued access to data, individuals must review the IRP data security manual and complete the IRP data access forms. If you access data on Silo, you must also complete UW HIPAA training every year.
I'm a PI/Co-PI who will not have data access. Do I need to take this training?
Yes. Investigators are responsible for a project's compliance with data security policies.
PI's read the IRP data security manual and complete the forms as they relate to their research role (the technical silo access-related requirements will not need to be completed).
Publishing and Presenting Research
Publications and presentations using WADC data should not include cell sizes with observations <10.
State agency data owners must be given an opportunity to review research before it is publicly released. Copies of publicly released research should be provided to the IRP data sharing coordinator per the following schedule:
- Public presentations of results – 30 days before presentation delivery
- Reports to project funders – at the time of delivery
- Submissions to journals/others for publication – at the time of submission
Use the following disclaimer language for research disseminated publicly:
The authors of this article are solely responsible for the content therein. The authors would like to thank the *Wisconsin Department of Children and Families, Department of Health Services, Department of Public Instruction, Department of Workforce Development, and Department of Corrections* for the use of data for this analysis, but these agencies do not certify the accuracy of the analyses presented.
*Wisconsin state agencies to be listed will vary by project.
Silo Troubleshooting
You can only log in to Silo from a web browser silo.ssc.wisc.edu
Silo is like WinStat: if you “disconnect” it will keep your session running. A hard “Sign Out” from Silo can often help prevent problems associated with an open session.
If you try to silosync a file with the same name as an existing file in your receiving silosync directory, it will not work. It will not overwrite a file with a newer version of the same name.
Silo has regularly scheduled downtime during the morning on the first Wednesday of each month.
Policies To Remember
Data use is authorized by project only.
Individual-level data files remain on Silo servers.
Work with IRP data on Silo should be limited to non-public locations.
About the IRP Data Core
Contact Information
IRP Data Security Officer
Maggie Townsend
maggie.townsend@wisc.edu
(608) 262-5370
3444 William H. Sewell Social Sciences Building
IRP Data Sharing Coordinator
Steve Cook
steven.cook@wisc.edu
(608) 262-4517
3448 William H. Sewell Social Sciences Building
SSCC Helpdesk
For help with Silo technical issues
helpdesk@ssc.wisc.edu
(608) 262-9917
4226 William H. Sewell Social Sciences Building