De-identified dataUniversity Intellectual PropertyEmployee InformationSensitive Faculty ActivitiesStudent InformationDonor InformationCurrent Litigation/Investigation MaterialsContractsPhytractsPhysical Building DesignsFinancial Information 1. Faculty and/or staff costs: (if UCSF faculties are involved), direct costs related to faculty and/or staff periods (percent of their UCE) are covered by the third party. 2. Faculty and/or staff Indirect costs: (if the faculty of the UCSF is involved) indirect costs related to faculty and/or staff time set as a percentage (all direct costs borne by the third party. 3. Data processing and processing costs: the cost of identifying and producing the data set must be borne by the third party. These costs must be separated and distinguished from the consideration guaranteed by the licence fee negotiated by UCSF IT Governance Enterprise Information and Analytics (EIA). Check the frequently asked questions about the data sharing project. If you have a question that is not answered, please email [email protected]. Who at UCSF has the right to sign a data-sharing contract? ii. Projects that share identifiable data for patients. [Do you clarify this, we saw that MC Procurement must share PHI routine – Search for the EIA campus delegation for TPO?] 1. The transmission or access of P3 and P4 data to third parties must comply with the UC`s contractual guidelines and include the following key criteria: `Festival control visualization software is available to all UC employees.
You may want to consider registering if you are considering a data sharing partnership. Below is a summary of documentation requirements for compliance with research rules for unidentified, limited and identified research data requirements. UCSF Health assumes that the use of its sensitive data by third parties gives a tangible result that directly or indirectly benefits the mission, patients and society of the UCSF in general. A. Responsibility and Mission – UC must have a strategy that protects data, uses data to exploit the public overall and ensures an equitable distribution of the benefits and burdens of data exchange. 1. Exclusive: The third party has no right to use the data set that prohibits or restricts the use by the University of California (UC) for research, patient or educational purposes for any period of time. 2. Protected health information: Only unidentified health data (according to UCSF health standards) 1 can be considered for sharing. 3.
High-risk datasets: Datasets focused on HIV, hepatitis, psychiatric diseases, laboratory abuse tests, sexual orientation and gender identity, and genetic testing must be verified by the Chancellor`s executive team and the Office of the President (UCOP) at the University of California. 4. Multi-campus data sets: Applications for registrations from more than one UC health campus must be reviewed by the Chancellor`s management team and by UCOP. 5. Data management: registration should not be aggregated into a larger third-party dataset and the dataset must be located in a secure and agreed-upon location. The third-party provider must manage strict access protocols, allow UCSF Health to monitor these protocols, and remove the dataset (and all associated backups) at the end of the project. 6. Use of the following data: Records cannot be resold, transferred or reused for purposes other than those described in the final agreement with the third party. 7. Publications: (if UCSF faculties are involved) resulting from the use of data sets, UCSF authors must be involved and contribute usefully to improving the health of our patients and society. The session “De-mystifying Data Sharing …
Your questions, to which UCSF experts will answer” from the Research Data Series 2020 provides an overview and practical and don`ts basis for data exchange at UCSF. You can see the session or check the slides.