Data Management and Integrity

  1. All educational and research projects conducted with the Clinical Simulation Center’s resources must identify a lead faculty member. If more than one faculty member is involved in the conduct of the project, the lead faculty member on the project should provide to the Clinical Simulation Center a comprehensive list of those faculty members. Student projects must identify a faculty member responsible for the supervision of the project.
  2. Each educational project and research project will be assigned a unique numerical identifier. For educational projects, the identifier will be assigned at the time of the lead faculty member’s submission of an instructional plan for the project. For research projects, the Clinical Simulation Research Committee will assign the identifier at the time of the completion of the project’s review.
  3. Lead faculty members must provide to the Clinical Simulation Center a copy of the description of each project; the Clinical Simulation Center will keep a copy of the project descriptions in a secure setting in its archives. Lead faculty responsible for the project should provide a paper or electronic copy of assessment instruments associated with the project. This policy is intended to protect the integrity of data gathered. Access to the assessment instruments for other projects must be explicitly negotiated by the interested faculty member with the faculty member leading the project. Access to the data gathered must be explicitly negotiated by the interested faculty member with the faculty member leading the project.
  4. Data security measures are intended to keep information gathered safe from corruption or unauthorized access. These measures apply to written and electronic data. Practices followed to protect data integrity in the physical environment include: making servers accessible only to network administrators, keeping transmission media (such as cables and connectors) covered and protected, and protecting hardware and storage media from power surges, electrostatic discharges, and magnetism. Information stored on the Clinical Simulation Center server will be backed up electronically at least weekly. The Clinical Simulation Center will maintain current authorization levels for all users, documenting system administration procedures, parameters, and maintenance activities, and creating disaster recovery plans for occurrences such as power outages, server failure, and virus attacks.
  5. Copies of data stored on the Clinical Simulation Center server will be provided on request to the lead faculty member on educational projects and the Principal Investigator of research projects. The associated core data on the Clinical Simulation Center server will be maintained, not destroyed.
  6. Lead faculty on educational and research projects can request preliminary reports on electronic data gathered or stored at the Clinical Simulation Center in order to assure the validity of the data gathered.