Emergency Preparedness and Response: Collaborative Approaches to Ensure Sustainability of Research Oversight

Explores considerations for a human research protection program (HRPP) emergency preparedness plan.

Questions? Contact Us
Scroll Down Arrow


About this Webinar

Organizations can face a myriad of emergencies, from natural and human-made disasters to cyberattacks and pandemics. Even in emergencies, the safety and well-being of research participants should be paramount. This webinar explores considerations for a human research protection program (HRPP) emergency preparedness plan, including how that plan differs from an organization’s more global approach to emergencies, and how organizations can ensure the sustainability of an HRPP.

Webinar Demo:

Release Date: October 2, 2024

Language Availability: English

Suggested Audiences: Compliance Professionals, HRPP Staff, Institutional/Signatory Officials, IRB Administrators, IRB Members, Research Personnel, Researchers

Organizational Subscription Price: Included as part of an annual subscription to our All Access Webinar Package
Independent Learner Price: $49 per person


Webinar Content

Emergency Preparedness and Response: Collaborative Approaches to Ensure Sustainability of Research Oversight

Nichelle Cobb, PhD, CIP –  Association for the Accreditation of Human Research Protection Programs; Robert Hood, PhD –  Association for the Accreditation of Human Research Protection Programs

Learning Objectives:

  • Discuss why an emergency preparedness plan for an HRPP is critical to the protection of research participants.
  • Identify the factors to consider when developing an emergency preparedness plan.
  • Consider who should be involved in the development of an emergency preparedness plan and its dissemination.
  • Understand the importance of evaluating and modifying the emergency preparedness plan as needed.

Recommended Use: Required
ID (Language): 21498 (English)


Learn More

Your Name(Required)
I'd Like To Receive Emails From CITI Program
This field is for validation purposes and should be left unchanged.