Adverse Event Reporting _____________________________

Slides:



Advertisements
Similar presentations
Susan Burner Bankowski, M.S., J.D. Chair, OHSU IRB
Advertisements

Comparison GHTF/SG5/N5:2012 vs. MEDDEV 2.7/3:2010
Adverse Events and Serious Adverse Events
Safety Reporting IN Clinical Trials
ADVERSE EVENT REPORTING
Expedited Reporting/DAERS May 13, 2011 Oluwadamilola Ogunyankin, M.D. Chinedum Abanobi, M.D. DAIDS Regulatory Support Center (RSC) Oluwadamilola Ogunyankin,
Pharmacovigilance Dr. Muiris Dowling,
Adverse Event Reporting. Reporting Adverse Events Adverse Events (AEs) are “... any untoward medical occurrence in a subject that was not previously identified.
Reporting Unanticipated Problems Involving Risk to Subjects or Others and Adverse Events WFUHS Policy/Procedure Effective Date 6/1/07 Wendy Murray Monitoring.
SAE Reconciliation How to handle ‘a waterfall’ of SAEs?
Elements of a clinical trial research protocol
Capturing and Reporting Adverse Events in Clinical Research
Investigator Meeting January 2010 Protocol Review and Refresher.
Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Adverse Event Reporting Catherine Dillon.
Adverse Events, Unanticipated Problems, Protocol Deviations & other Safety Information Which Form 4 to Use?
SERIOUS ADVERSE EVENTS REPORTING Elizabeth Dayag IRB Administrator Naval Medical Center Portsmouth.
Adverse Events and Unanticipated Problems Presented by: Karen Jeans, PhD, CCRN, CIP COACH Program Analyst.
Paula Peyrani, MD Division of Infectious Diseases University of Louisville Performing the Study.
1 Nuts and Bolts of Safety Reporting The Role of the CRO Dr. Noa Lowenton Spier Pharma-Clinical S.A.G.
Adverse Event Reporting.
Office of Research Oversight ORO Reporting Adverse Events in Research to ORO Paula Squire Waterman, MS, CIP Department of Veterans Affairs Office of Research.
SAE Reporting Judy Breed, BA, RN June, 2011 CONFIDENTIAL.
Collecting data in clinic.  Aim of BADBIR  Definition of Adverse Events  Adverse events in BADBIR  Adverse event recording in hospital case notes.
Adverse Event/Unanticipated Problems Policy and Procedures November 2007.
Andrace DeYampert Bethany Lane Samkeliso Mawocha ProTECT III Investigator Meeting November 12-14, 2012.
AE/SAE/EAE Identification and Reporting AE/SAE/EAE Identification and Reporting.
SAE data entry: Clinical versus Pharmacovigilance standards Daniel Becker Solvay Pharmaceuticals Hannover, Germany T:
Adverse Event Reporting & SAE Reporting for Investigators Trial Number: (POLO-AML-2) Date of training:23 February 2013 Trainer: Deepa Sachdev Venue:Investigator.
EAE Training EAE Reporting and Assessment Overview DAIDS Regional Training Event, Regulatory Compliance Center Kampala, Uganda, September 2009 DAIDS Regional.
Investigator’s Meeting
EAE Training PROTOCOL ­ SPECIFIC Objectives  Definitions  Assessment of Adverse Events  EAE Reporting.
Michelle Groy Johnson Quality Improvement Officer Research Integrity Office Houston, We have a Problem: When and How to Report Problems to the IRB.
Serious Adverse Event Reporting Start-up Meeting March 25, 2010 Kingston, ON.
General Instructions for CRF 3 Rev H To be completed at each follow up visit Patient Identification and Group Date of Visit Assessment performed physician.
European Patients’ Academy on Therapeutic Innovation Introduction to pharmacovigilance Monitoring the safety of medicines.
Stress Ulcer Prophylaxis in the Intensive Care Unit (SUP-ICU) SAR/SUSAR Mette Krag Dept. of Intensive Care 4131 Copenhagen University Hospital Rigshospitalet,
Module 6 Monitoring Events Supposedly Attributable to Vaccination or Immunization (ESAVIs) Training for Inactivated Poliovirus Vaccine (IPV) introduction.
D3 ) Not Recovered d5) Fatal Was a post-mortem undertaken?YesNo Was the SAE ongoing at time of death from other cause? Yes No d d m m y y y y d1) Recovered.
Main Line Hospitals Institutional Review Board Unanticipated Problems Anne Marie Hobson, BSN, JD, ORA Director Theresa Greaves, ORA Manager.
Bussara Sukpanichnant, Human Subject Protection Office, USAMD-AFRIMS Unanticipated Problems 15 th FERCAP International Conference 24 Nov 15 Nagasaki, Japan.
1 SAE Centralized Report and Review Process April 2012.
CLINICAL TRIALS.
REPORTING ADVERSE EVENTS AND COMPLETING THE REPORT FORM
Safety of the Subject Cena Jones-Bitterman, MPP, CIP, CCRP

FHIR Adverse Event Resource
Safety Reporting V6.0 17/01/17.
Assessing expectedness of an adverse event
Safety Reporting Nichol McBee, MPH, CCRP.
Expedited Adverse Event Reporting Requirements
Reporting Unanticipated Events to the CIRB and in WebDCU™
Remote Monitoring of Adverse Events
Copenhagen University Hospital Rigshospitalet, Denmark
3. Key definitions Multi-partner training package on active TB drug safety monitoring and management (aDSM) July 2016.
Pharmacovigilance in clinical trials
Safety of the Subject Cena Jones-Bitterman, MPP, CIP, CCRP
Expedited Adverse Event Reporting Requirements
*Continue on SAE supplemental page CTT21 A if more space is required
9. Introduction to signal detection
Remote Monitoring of Adverse Events
ARCADIA Coordinator Webinar
To start the presentation, click on this button in the lower right corner of your screen. The presentation will begin after the screen changes and you.
SERIOUS ADVERSE EVENTS REPORTING
To start the presentation, click on this button in the lower right corner of your screen. The presentation will begin after the screen changes and you.
Model Enhanced Classification of Serious Adverse Events
Why should we disclose? Patients have the Right to Know
Adverse Event Is it Serious? Record as an Adverse Event No Yes
Dr Tim England TICH-2 SAE adjudicator
Policy on Prompt Reporting
Serious Adverse Event Reconciliation
Presentation transcript:

Adverse Event Reporting _____________________________ Catherine Dillon, MS February 2019 Investigators Meeting

Investigators Meeting Adverse Events Adverse Events (AEs) are “. . . any untoward medical occurrence in a subject that was not previously identified which does not necessarily have a causal relationship to the study drug…” Events existing prior to randomization should not be reported as AEs, unless there is a change in severity. Pre-existing conditions that are discovered after randomization are not adverse events. These should be documented as medical history. Abnormal lab values collected after randomization that are considered to be clinically significant by the site investigator are adverse events. February 2019 Investigators Meeting

Serious Adverse Events Serious Adverse Events (SAEs): Are Fatal Are Life-threatening Result in hospitalization/prolonging of hospitalization – excluding optional, pre-planned surgery Result in disability/congenital anomaly Require intervention to prevent permanent impairment or damage February 2019 Investigators Meeting

Investigators Meeting Reporting AEs Reported on Form 104 – Adverse Event Case Report Form (CRF) One AE per CRF Report diagnosis, not symptoms Fever, cough, chest pain, crackles = pneumonia Avoid abbreviations/colloquialisms February 2019 Investigators Meeting

Investigators Meeting Reporting AEs Death, surgery, intubation, etc. are NOT adverse events. They are outcomes of adverse events. All AEs will be coded using MedDRA. A new feature of WebDCUTM will auto-populate the Lowest Level Term when 3 or more letters are entered into the name field . February 2019 Investigators Meeting

Reporting Requirements for AEs AE reporting – must be submitted through the StrokeNet WebDCUTM as described and within the timeframes described in NIH StrokeNet Network Standard Operating Procedure ADM 12 Central Institutional Review Board (CIRB) Reporting. SAE reporting – reported in WebDCUTM within 24 hours of the study site being made aware of the occurrence of the SAE. February 2019 Investigators Meeting

Data Entry Timelines for AEs Non-serious AEs must be entered and submitted into WebDCUTM within 5 days of data collection. SAEs must be entered and submitted into WebDCUTM within 24 hours of discovery. February 2019 Investigators Meeting

Investigators Meeting Reporting SAEs SAEs require additional information to be submitted on the AE CRF: Detailed description of the event Relevant tests/laboratory data Relevant history and pre-existing conditions Concomitant medications February 2019 Investigators Meeting

Investigators Meeting SAE Narratives Narratives assist the Independent Medical Safety Monitor (IMSM) in reviewing the event. Remove any protected health information (PHI) from the narrative i.e., subject, physician or institution name February 2019 Investigators Meeting

Investigators Meeting IMSM Review Process Site enters data and submits AE CRF into WebDCUTM Automatic e-mail notifications to Site Manager (SM). If SAE and data is sufficient, automatic e-mail notification sent to the IMSM IMSM blindly reviews the event and indicates whether it is serious, unexpected and study intervention-related SM closes review process and reports to cIRB if required. February 2019 Investigators Meeting