Data Domain Scope
Research Compliance data supports the university’s oversight of research activities, ensuring that research is conducted ethically, safely, and in accordance with federal, state, sponsor, and university requirements.
Examples include:
- Human subjects research approvals
- Animal research oversight
Out of scope
- Grant proposals and financial award management (Research Administration)
- Research datasets generated by investigators (Research data)
Data Trustee
Nadine Connor serves as the Data Trustee for the Research Compliance domain. Data Trustees are university officials with authority over institutional data within their assigned domain. They are accountable for managing, protecting, and ensuring the integrity and usefulness of institutional data and for upholding UW-Madison policies, UW System policies, state laws, and federal laws.
Data Governance Council
Lynn Haynes is the Research Compliance representative on the Data Governance Council. The Data Trustee may serve, or provide a delegate to serve, as a voting member of the Data Governance Council.
Data Steward
Heather McFadden serves as the Data Steward for the Research Compliance domain. Data stewards are assigned by and accountable to Data Trustees, to help define, implement, and enforce data management policies and procedures within their specific data domain. Institutional data stewards have delegated responsibility for all aspects of how data is acquired, used, stored, and protected throughout its entire lifecycle from acquisition through disposition.
Data Systems
Data Stewards identify and classify the systems where data from their data domain resides. Within the Research Administration domain these are:
| System | Classification |
| ARROW | Sensitive / Moderate Risk |
Data Classification Rationale
Data classification policy requires that data be classified according to its risk. Within the Research Administration domain, the classification rationale is:
| Classification | Classification Rationale | Example(s) | |
| High Risk | Research compliance data are classified as High Risk if they contain protected health information (PHI) that is subject to the federal Health Insurance Portability and Accountability Act (HIPAA). | Service dates, indirect identifiers such as initials. | |
| Moderate Risk Data | Research compliance data are classified as Moderate Risk if they contain proprietary data or if the loss of confidentiality, availability, or integrity could have adverse impact, such as impeding funding or research activities. | Research protocols. | |
| Low Risk Data | Research Compliance data are classified as Low Risk if the loss of confidentiality, availability, or integrity would have negligible impact to the University or to individuals. | Data related to the protocol review process, including reviewer notes, staff comments, and activity logs. System documentation, analytics and application logs. | |
| Public Data | Aggregate compliance protocol data with no identifiers of individual protocols, investigators or research activities are classified as Low Risk and may be released as public data as required by law or regulation. |
|