Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Adverse Event Reporting Catherine Dillon.

Slides:



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

Adverse Events and Serious Adverse Events
Safety Reporting IN Clinical Trials
AEs, SAEs, and EAEs – An Overview
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.
THE ACTION TO CONTROL CARDIOVASCULAR RISK IN DIABETES STUDY (ACCORD)
Reporting Unanticipated Problems Involving Risk to Subjects or Others and Adverse Events WFUHS Policy/Procedure Effective Date 6/1/07 Wendy Murray Monitoring.
Elements of a clinical trial research protocol
Update: 21 CFR PART 312 FDA Safety Reporting Requirements for INDs
Capturing and Reporting Adverse Events in Clinical Research
Director, Investigator Support & Integration Services, OCTRI
Fulfilling the Promise of Medicine Together New FDA Safety Reporting Requirements 2010 John McLane, Ph.D. COO & Vice President Clinical and Regulatory.
Human Research Protection Program Training: Post-Approval Event Reporting March 26, 2008 Lisa Voss, MPH, CIP Assistant Director, QIU Human Research Protection.
Investigator Meeting January 2010 Protocol Review and Refresher.
Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Investigator Meeting for New NETT Hubs November 12, 2012 NIH-NINDS U01 NSO69498.
AE/SAE/EAE Identification and Reporting AE/SAE/EAE Identification and Reporting.
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.
Clinical causality assessment I. Ralph Edwards R.H.B Meyboom.
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.
Expedited Reporting of Adverse Events to the DAIDS
New Adverse Event Reporting Policy Effective September 1, 2007.
Adverse Event Reporting.
Development and Approval of Drugs and Devices EPI260 Lecture 9 May 23, 2012 Richard Chin, M.D.
Office of Research Oversight ORO Reporting Adverse Events in Research to ORO Paula Squire Waterman, MS, CIP Department of Veterans Affairs Office of Research.
H. Lundbeck A/S21-Sep-151 Pharmacovigilance during clinical development SAE reporting, ASUR and PSUR IFF Seminar, 21. February 2007.
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 EFFECTS OF DRUGS Phase II May Adverse Drug Reaction An adverse reaction to a drug is a harmful or unintended response. ADRs are claimed.
The Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Brief Protocol Training NIH-NINDS U01 NS NETT CCC U01 NS NETT SDMC U01 NS
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.
Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Site Monitoring Shirley Frederiksen Donna Harsh.
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.
European Patients’ Academy on Therapeutic Innovation Introduction to pharmacovigilance Monitoring the safety of medicines.
Role of Site Investigator Ensure subject safety is protected & well-managed Full compliance with requirements of Good Clinical Practice (GCP) Conduct the.
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.
1 SAE Centralized Report and Review Process April 2012.
REPORTING ADVERSE EVENTS AND COMPLETING THE REPORT FORM
Safety of the Subject Cena Jones-Bitterman, MPP, CIP, CCRP
FHIR Adverse Event Resource
Assessing expectedness of an adverse event
8. Causality assessment:
Safety Reporting Nichol McBee, MPH, CCRP.
Expedited Adverse Event Reporting Requirements
Remote Monitoring of Adverse Events
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
Remote Monitoring of Adverse Events
SERIOUS ADVERSE EVENTS REPORTING
Model Enhanced Classification of Serious Adverse Events
Adverse Event Reporting _____________________________
Dr Tim England TICH-2 SAE adjudicator
Serious Adverse Event Reconciliation
Presentation transcript:

Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Adverse Event Reporting Catherine Dillon

Reporting 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 that are considered to be clinical significant by the site investigator are adverse events

Reporting Adverse Events Adverse Events are reported on Form 06: Adverse Event Report the diagnosis, not the symptoms: Fever, cough, chest pain, crackles = pneumonia Death, surgery, intubation, etc. are not adverse events. They are outcomes of adverse events

Reporting Adverse Events All AEs will be centrally coded verbatim using MedDRA 1 AE per CRF Avoid abbreviations/colloquialisms AEs that can’t be coded will be queried

Reporting Adverse Events All AEs must be reported through completion of study treatment All SAEs must be reported through End of Study

Serious Adverse Events fatal life-threatening result in hospitalization/prolongation of hospitalization result in disability/congenital anomaly OR require intervention to prevent permanent impairment or damage

Severity Refer to NCI Common Terminology Criteria for Adverse Events CTCAE Categories include: o Mild o Moderate o Severe o Life-threatening o Disabling Severity is different from serious: o Severe headache can be non-serious o Mild stroke can be serious

Relatedness to treatment Unrelated · The temporal relationship between treatment exposure and the adverse event is unreasonable or incompatible and/or adverse event is clearly due to extraneous causes (e.g., underlying disease, environment) Unlikely (must have 2) · May have reasonable or only tenuous temporal relationship to intervention. · Could readily have been produced by the subject’s clinical state, or environmental or other interventions. · Does not follow known pattern of response to intervention. · Does not reappear or worsen with reintroduction of intervention.

Relatedness to treatment Possible (must have 2) · Has a reasonable temporal relationship to intervention. · Could not readily have been produced by the subject’s clinical state or environmental or other interventions. · Follows a known pattern of response to intervention. Probable (must have 3) · Has a reasonable temporal relationship to intervention. · Could not readily have been produced by the subject’s clinical state or have been due to environmental or other interventions. · Follows a known pattern of response to intervention. · Disappears or decreases with reduction in dose or cessation of intervention.

Relatedness to treatment Definite (must have all 4) · Has a reasonable temporal relationship to intervention. · Could not readily have been produced by the subject’s clinical state or have been due to environmental or other interventions. · Follows a known pattern of response to intervention. · Disappears or decreases with reduction in dose or cessation of intervention and recurs with re-exposure.

Data Entry Time Lines for AEs Non-serious AEs must be submitted into WebDCU TM within 5 days of data collection SAEs must be submitted into WebDCU TM within 24 hours of discovery

Reporting SAEs SAEs require additional information: Detailed description of the event Relevant tests/laboratory data Relevant history and pre-existing conditions Concomitant meds

Reporting SAEs These narratives assist the Independent Medical Safety Monitor in reviewing the event Do not identify any subject, physician, or institution by name

Reporting SAEs Site data enters and submits AE CRF into WebDCU TM Automatic notification to Site Manager (Ms. Arthi RAMAKRISHNAN) SM reviews narrative - If CRF is sufficient, an automatic notification will be sent to the Internal Quality and Safety Reviewer (Dr. Cemal SOZENER)

Reporting SAEs IQSR reviews narrative - If AE data is sufficient, an automatic notification will be sent to the Independent Medical Safety Monitor (Dr. Tom Bleck) IMSM reviews the event and indicates whether the event is serious and unexpected Site Manager closes review process

SAE Reporting DSMB requires expedited reporting of all SAEs Site PIs are responsible for reporting the SAE to their IRB according to local requirements Site PIs responsible for submitting follow-up information into WebDCU TM, as it becomes available.

Additional Reporting for Neurological Worsening Neurological worsening associated with glucose concentrations of <=55 mg/dL and lasting longer than 24 hours must be coded as serious. Events of sudden neurological worsening ( ≥ 4 point NIHSS score increase) require the completion of Form 22: Neurological Worsening.

Additional Reporting for Hypoglycemia Blood glucose <40 mg/dL – Must be coded as severe, life threatening/disabling, or fatal. – Must be coded as serious Hypoglycemic events defined as blood glucose <70 mg/dl require the completion of Form 17: Hypoglycemic Event Form. Contact Dr. Bleck (SHINE Hotline) if a subject has 3 or more episodes of hypoglycemia within a 24 hour period. IMSM will determine if the level of sliding scale insulin should be adjusted or if insulin drip protocol should discontinued

Questions?