M. Rickard, Research Governance and GCP Manager R. Fay Research Governance and GCP Manager Elizabeth Clough, Governance Operations Manager

Similar documents
Marie-Claire Rickard, RG and GCP Manager Jimena Lovos, Quality Assurance Manager Elizabeth Clough, R&D Governance Operations Manager

Details: Approval: Distribution & Storage: Pharmacovigilance for Researchers for UoL / LTHT Sponsored CTIMPs. Standard Operating Procedure

Sponsor Responsibilities. Roles and Responsibilities. EU Directives. UK Law

M Rickard, Research Governance and GCP Manager Elizabeth Clough, R&D Governance Operations Manager Rachel Fay, Research Governance and GCP Manager

Keele Clinical Trials Unit

Marie-Claire Rickard, Governance and GCP Manager Jimena Lovos, Quality Assurance Manager Elizabeth Clough, R&D Governance Operations Manager

Standard Operating Procedure

Version Number: 003. On: September 2017 Review Date: September 2020 Distribution: Essential Reading for: Information for: Page 1 of 13

STANDARD OPERATING PROCEDURE

NEWCASTLE CLINICAL TRIALS UNIT STANDARD OPERATING PROCEDURES

Safety Reporting in Clinical Research Policy Final Version 4.0

STANDARD OPERATING PROCEDURE SOP 205

NEWCASTLE CLINICAL TRIALS UNIT STANDARD OPERATING PROCEDURES

Research Adverse Event and Safety Reporting Procedures Outcome Statement: Title:

Informed Consent SOP Number: 25 Version Number: 6.0 Effective Date: 1 st September 2017 Review Date: 1 st September 2019

Reference Number: UHB 253 Version Number: 1 Date of Next Review: 22/01/2018 Previous Trust/LHB Reference Number: SR-RG-015

POLICY ON RESEARCH RELATED ADVERSE EVENT REPORTING

STANDARD OPERATING PROCEDURE

IDENTIFYING, RECORDING AND REPORTING ADVERSE EVENTS FOR CLINICAL INVESTIGATIONS OF MEDICAL DEVICES

Standard Operating Procedure (SOP) for Reporting Serious Breaches in Clinical Research

R. Fay, Research Governance & GCP Manager K. Mahiouz, Clinical Trials Facilitator E. Clough, R&D Governance Operations Manager

TITLE: Reporting Adverse Events SOP #: RCO-204 Page: 1 of 5 Effective Date: 01/31/18

Adverse Event Reporting

SOP-QA-28 V2. Approver: Prof Maggie Cruickshank, R&D Director Approver: Prof Steve Heys, Head of School

Standard Operating Procedure (SOP) Research and Development Office

SOP19a & 19b: Standard Operating Procedure for (a) Safety Monitoring (especially Pharmacovigilance) & (b) Urgent Safety Measures

Standard Operating Procedure (SOP) for Reporting Urgent Safety Measures in Clinical Research

STANDARD OPERATING PROCEDURE SOP 325

MHRA Findings Dissemination Joint Office Launch Jan Presented by: Carolyn Maloney UHL R&D Manager

This Agreement dated DD/MM/YYYY (the Effective Date ) is between

Trial Management: Trial Master Files and Investigator Site Files

Standard Operating Procedure (SOP) Research and Development Office

Standard Operating Procedure INVESTIGATOR OVERSIGHT OF RESEARCH. Chief and Principal Investigators of research sponsored and/or hosted by UHBristol

Standard Operating Procedure (SOP) Research and Development Office

MANAGEMENT OF PROTOCOL AND GCP DEVIATIONS AND VIOLATIONS

Standard Operating Procedure:

Version Number: 004 Controlled Document Sponsor: Controlled Document Lead:

Document Number: 006. Version: 1. Date ratified: Name of originator/author: Heidi Saunders, Senior Portfolio Coordinator

STANDARD OPERATING PROCEDURE

Research Staff Training

Standard Operating Procedure (SOP)

I2S2 TRAINING Good Clinical Practice tips. Deirdre Thom Neonatal Nurse Coordinator

STANDARD OPERATING PROCEDURE

RITAZAREM CRF Completion Guidelines

SOP MONITORING & OVERSIGHT OF RESEARCH ACTIVITY. Contact Jess Bisset, Research Operations Manager x20227

STANDARD OPERATING PROCEDURE

Study Management SM STANDARD OPERATING PROCEDURE FOR Adverse Event Reporting

Adverse Event Reporting

Trial set-up, conduct and Trial Master File for HEY-sponsored CTIMPs

Research & Development Quality Manual

Study Monitoring Plan Template

Keele Clinical Trials Unit

Quality Assurance in Clinical Research at RM/ICR. GCP Compliance Team, Clinical R&D

Document Title: Site Selection and Initiation for RFL Sponsored Studies Document Number: 026

Standard Operating Procedure. Essential Documents: Setting Up a Trial Master File. SOP effective: 19 February 2016 Review date: 19 February 2018

NEWCASTLE CLINICAL TRIALS UNIT STANDARD OPERATING PROCEDURES

Standard Operating Procedure (SOP) Research and Development Office

STANDARD OPERATING PROCEDURE SOP 710. Good Clinical Practice AUDIT AND INSPECTION. NNUH UEA Joint Research Office. Acting Research Services Manager

Document Title: Document Number:

NEWCASTLE CLINICAL TRIALS UNIT STANDARD OPERATING PROCEDURES

Research Governance Framework 2 nd Edition, Medicine for Human Use (Clinical Trial) Regulations 2004

Document Title: Investigator Site File. Document Number: 019

DCP Safety Committee. Update and Review. January 19, 2017

Corporate. Research Governance Policy. Document Control Summary

PROMPTLY REPORTABLE EVENTS

STANDARD OPERATING PROCEDURE

SOP16: Standard Operating Procedure for Establishing Sites and Centres - Site Setup

Document Title: Research Database Application (ReDA) Document Number: 043

MEDICINES FOR HUMAN USE (CLINICAL TRIALS) REGULATIONS Memorandum of understanding between MHRA, COREC and GTAC

Preparation for an MHRA GCP Inspection including Training on New and Up-dated SOPs

Risk Assessment and Monitoring

Study Guide for Emergency Care Clinicians. (Version /09/2014)

Joint R&D Support Office SOP S-2011 UHL

FERCI MODEL SOPs. [The IEC members (author/s, reviewer/s) and Chairperson will sign and date the SOP on this first page]

Governance %%.4- r2&% Queen s University Belfast. Standard Operating Procedure Research Governance. r2.aoc7. Research and Enterprise

Gaining NHS Trust R&D Approvals

Site Closedown Checklist for UoL Sponsored CTIMP Studies

MEDICINES CONTROL COUNCIL

Biomedical IRB MS #

ABMU R&D Operational Framework

STH Researcher. Recording of research information in patient case notes

STANDARD OPERATING PROCEDURE

ACTIONS/PSOP/001 Version 1.0 Page 2 of 6

New European Union Clinical Trial Regulations

Document Title: Research Database Application (ReDA) Document Number: 043

Document Title: Study Data SOP (CRFs and Source Data)

SOP18b: Standard Operating Procedure for Preparing for External Audit and Inspection

Hertfordshire Hospitals R&D Consortium Incorporating West Herts Hospitals NHS Trust and East & North Herts NHS Trust

Once the feasibility assessment has been conducted the study team will be notified via (Appendix 3) of the outcome and whether the study is;

Risk Assessment. Version Number 1.0 Effective Date: 21 st March Sponsored Research

University of South Carolina. Unanticipated Problems and Adverse Events Guidelines

Document Title: File Notes. Document Number: 024

ACRIN ADVERSE EVENT REPORTING MANUAL. 1 March 2006 v.3

Overview of Draft Pharmacovigilance Protocol

STANDARD OPERATING PROCEDURE SOP 715. Principles of Clinical Research Laboratory Practice

Standard Operating Procedure Research Governance

Investigator Site File Standard Operating Procedure (SOP)

Drugs and Cosmetics (First Amendment) Rules, 2013

Storage and Archiving of Research Documents SOP 6

3 HEALTH, SAFETY AND ENVIRONMENTAL PROTECTION

Transcription:

Standard Operating Procedures (SOP) for: Pharmacovigilance and Safety Reporting for Sponsored non-ctimps SOP Number: 26b Version 2.0 Number: Effective Date: 29th November 2015 Review Date: 3 rd December 2017 Author: Reviewer: Reviewer: Authorisation: Name / Position Signature M. Rickard, Research Governance and GCP Manager R. Fay Research Governance and GCP Manager Elizabeth Clough, Governance Operations Manager Dr Sally Burtles, Director of Research Services & Business Development Date 11 th November 2015 Purpose and Objective: To identify and standardise the process for reporting Adverse Events (AEs), Serious Adverse Events, Serious Adverse Reactions (SARs - in this case reactions to the Medical Device or study procedure being investigated), and Urgent Safety Measures (USM). To ensure that systems are in place for the management of AEs for all studies, not just clinical trials of medicinal products (CTIMPs) to ensure that during the course of a study the participants involvement in the research is recorded and reported to ensure their continued safety. To be compliant with Good Clinical Practice (GCP), Research Governance Framework (RGF), Medical Devices Regulations 2002, Sponsors of Non-CTIMP clinical studies have a responsibility to record and report SAEs. Scope: This SOP covers procedures primarily for Barts Health NHS Trust [BH] and Queen Mary University of London [QMUL] sponsored Non - CTIMPs. (See SOP 26a for Pharmacovigilance for CTIMPs) Reporting mechanisms for SAEs in Non-CTIMPs are determined by the sponsor. The PI informs the sponsor of SAEs that occur in all study participants according to the sponsor Pharmacovigilance SOP and/ or the process outlined in the protocol. For all studies sponsored by an external sponsor, the sponsor procedure should be followed. Abbreviations: AE Adverse Event APR Annual Progress Report BH Barts Health NHS Trust CI Chief Investigator CRF Case Report Form CTIMP Clinical Trial of an Investigational Medicinal Product(s) SOP 26b Safety reporting for non CTIMPs v2.0 Page 1 of 7

DSUR Development Safety Update Report EOT End of Trial GCP Good Clinical Practice IMP Investigational Medicinal Product IRAS Integrated Research Application System JRMO Joint Research Management Office MHRA Medicines and Healthcare Regulatory Agency PI Principal Investigator QMUL Queen Mary University of London REC Research Ethics Committee ReDA JRMO Research Database SAE Serious Adverse Event SOP Standard Operating Procedures SUSAR Suspected Unexpected Serious Adverse Reaction Definitions (if needed): Non-CTIMP: Non- Clinical Trial of an Investigational Medicinal Product(s) [non-drug trial] Delegation of Responsibilities For multi-site studies, the Chief Investigator (CI) has overall responsibility for Pharmacovigilance and Safety Reporting for Sponsored non-ctimps at all the sites. Each Principal Investigator is delegated responsibilities for Pharmacovigilance and Safety Reporting for Sponsored non-ctimps at their site. Assessment of An Adverse event is a medical decision and as such MUST be performed by a Medically qualified team. This may not be the PI if they are not medically qualified. If there is only one site in the study, the CI usually is also the PI. Relevant SOPs SOP 26a - Phamacovigilance reporting for CTIMPs Associated document 1; AE flow chart Associated document 2: SAE form Associated document 3: NRES report Associated document 4: DSUR template SOP Text Responsibility Activity 1. All Identify adverse events within studies An adverse event [AE] is commonly defined as an untoward medical occurrence in a patient or clinical investigation subject who has been administered any research procedure. An adverse reaction [AR] can further be described as an untoward medical occurrence in a patient or clinical SOP 26b Safety reporting for non CTIMPs v2.0 Page 2 of 7

investigation subject who has been administered any research procedure, that can have a causal relationship with this treatment or procedure. An adverse reaction [AR] can, therefore, be any unfavourable and unintended sign (including an abnormal laboratory finding), symptom or disease temporarily associated with the use of a medical device product or taking part in research procedures, whether or not related to the clinical study. 2. Principal 3. Principal 4. Principal The PI assesses if the AE is serious The Principal Investigator (PI) / for the study assesses the AE or AR to establish if it should be classified as a Serious Adverse Event (SAE). An Adverse Event is classed as SERIOUS (SAE) if it : results in death, is life threatening, requires hospitalisation or prolongation of hospitalisation, Results in persistent or significant disability or incapacity Is a congenital anomaly or birth defect. Or the event is deemed by the PI to be medically significant. If the AE is NOT serious the PI should record, document and follow-up If the AE is not defined as serious as per the list above the PI must: Record the AE in the case report form (CRF) Document it in the participant s source data/ medical notes (e.g. electronic medical notes/hardcopy medical notes, as appropriate). This recording should include a description of the event, the date/time that it started and stopped, the severity of the event and details of any actions taken in response to the event. Follow-up the AE with the participant until resolution. This should be also recorded in the participant s medical notes (where appropriate) and the participant followed up until the event abates. For BH and QMUL sponsored studies do not report AEs that are NOT serious to the JRMO. If the AE is serious the PI should, record, document, and follow-up The PI is responsible for recording, assessing and reporting events to the sponsor. If the AE is deemed to be serious the PI must: Record (as above) SOP 26b Safety reporting for non CTIMPs v2.0 Page 3 of 7

Document (as above) Follow-up (as above) Report the SAE to the CI and sponsor using their SOP and following the protocol. Before reporting check against the protocol to identify whether there are any SAEs that do not need to be reported to the sponsor (proceed to point 5). 5. Chief Investigator/ Principal Investigator For BH and QMUL sponsored studies only serious, related and unexpected events should be reported to the JRMO. The PI is responsible for assessing adverse events. Prior to reporting the SAE to the CI or sponsor the PI must make an assessment of: Relatedness and Expectedness. To make this assessment the PI should review the protocol where all expected reactions should be listed. The PI makes the assessment of related and expectedness on the SAE form and sends the form to the CI. PLEASE NOTE: upon receipt of the SAE form the CI can upgrade the SAE s expectedness and relatedness, i.e. changing the event the PI s has reported to become related or unexpected. However, the CI cannot downgrade the reported event to become unrelated or expected. Should a difference of opinion arise the CI and PI should discuss the event but the PI at site will make the final decision. 6. If the SAE is NOT related to the study, the PI should record, document and follow-up. If the SAE report is assessed by the PI and CI as not being related to any study procedures, the SAE must be recorded in the case report form (CRF) and the participant followedup by the research team. The SAE must be documented in the participant s medical notes (where appropriate). If the SAE is classified as being likely to be related to a study procedure and expected, proceed to 7. If the SAE is not related proceed to section 8. 7. Principal For BH and QMUL sponsored studies do not report unrelated SAEs to the JRMO. The PI is responsible for reporting related and/or unexpected SAEs to the sponsor. The PI must report to the JRMO within 1-working day of the PI/Research team becoming aware of the SAE A safety reporting form must be completed for each SAR that requires reporting. Once completed the SAE form should be signed by the PI or appropriate delegated person. A scanned signed copy should be emailed to: research.safety@bartshealth.nhs.uk SOP 26b Safety reporting for non CTIMPs v2.0 Page 4 of 7

If the research team does not have a scanner the SAE form should be faxed to: 0207 882 7276 and an email research.safety@bartshealth.nhs.uk to alert the GCP team. If the study is NOT SPONSORED by BH/QM, the PI/CI should use the sponsor s SAE form and the sponsor s SOP. Do not send SAEs / AEs for studies not sponsored by BH or QMUL to the JRMO. 8. Chief Investigator If an SAE is related and/or unexpected the CI must report it to the JRMO and Research Ethics Committee (REC) who approved the study. See the HRA website for details of submitting non-ctimp SAE forms. http://www.hra.nhs.uk/researchcommunity/during-your-research-project/safety-reporting/ If the SAE relates to any of the following it should also be submitted to REC: it is a new event, related to the conduct of the study or the development of the investigational medical device, that is likely to affect the safety of subjects an SAE associated with the study procedures and which could modify the conduct of the study 9. JRMO Study Monitor 10. Chief Investigator Upon submission to REC assess whether the SAE impacts of trial design i.e. whether there are new risks to be included in Patient information sheet or whether the protocol needs to be amendment. When an SAE form is received by the JRMO, the form is checked for completeness. Upon receipt of an SAE the JRMO will send an acknowledgement of receipt email to the PI/research team. The JRMO may request further information from the CI/PI or research team. The JRMO will update their database as per the ReDa manual. File the SAE in the sponsor s study file( as per SOP 10 JRMO Filning). Any follow-up information about the SAE received from the study will be saved in the study file.. CI must submit Annual Progress Reports (APRs) to REC As sponsor, BH/QMUL delegates to the CI the responsibility of creating and submitting all annual reports to the regulators. Annual progress reports should be submitted to the approving REC twelve months after the date of the favourable ethical opinion letter was granted and annually thereafter. Details of how to submit an APR can be found on the HRA website. http://www.hra.nhs.uk/researchcommunity/during-your-research-project/progress-reporting/ SOP 26b Safety reporting for non CTIMPs v2.0 Page 5 of 7

The CI should create the report and submit to the REC when completed. A copy must also be sent to the sponsor via research.safety@bartshealth.nhs.uk for sponsor file. Evidence of submission should be retained in the Study Master File (and site files). PLEASE NOTE: Non-CTIMP annual progress reports to do not to be approved by the JRMO before they are submitted to REC. 11. Chief Investigator/ Principal Investigator/ Sponsor Urgent Safety Measures The sponsor and investigator may take appropriate urgent safety measures to protect clinical study subjects from any immediate hazard to their health and safety. On becoming aware of a potential hazard the CI or delegate should contact the sponsor immediately. If the CI is unable to contact the sponsor or REC, an Urgent Safety Measure (USM) can be implemented to protect the subject. The CI must then notify (in the form of a substantial amendment) the sponsor within one working day. The CI must then ensure the REC is notified within three days, in writing, of the measures taken and the reason for the measures using the Non- CTIMP safety report to REC form (see HRA website to download the form). This notification should include a covering letter detailing the measures taken, the reason for them, and any supporting documentation. 12. Site Principal Investigator The REC will acknowledge receipt within 30 days. Details of reporting Urgent Safety Measures can be found on the HRA website: http://www.hra.nhs.uk/researchcommunity/during-your-research-project/safety-reporting/ Ensure any incident that falls within the Barts Health NHS trust incident policy is appropriately reported. Please see the BH NHS trust intranet for the adverse incident policy for details of events to be reported. 13. External Sponsor Where possible, provide the annual progress reports to the JRMO on an annual basis. JRMO does not require SAE reports from external sponsors to be submitted. List of Associated Documents Document Document Name 1. Safety Reporting (Research other than CTIMPs) 2. JRMO Non CTIMP reporting form SOP 26b Safety reporting for non CTIMPs v2.0 Page 6 of 7

NON-CTIMP SAFETY FLOW CHART Research team identifies an Adverse Event (AE) A assesses if the AE is serious NOT SERIOUS (AE) Record in CRF Document in medical notes Follow-up the participant SERIOUS (SAE) Record in CRF Document in medical Follow-up the participant Report How to report an SAE PI assess the Relatedness (to the study) and Expectedness of the SAE (check protocol) SAE that is unrelated to the study and expected PI reports to CI only SAE that are related and/or Unexpected SAE Principal Investigator PI must complete JRMO Safety reporting form (SAE form) Send SAE to JRMO Send SAE to Chief Investigator Files in Investigator Site File (ISF) Chief Investigator sends SAE to REC Files correspondence with REC in Trial Master file (TMF) Assess whether protocol / PIS amendment is required, following SAE Includes SAE in Annual report to REC SOP 26b Safety reporting for non CTIMPs v2.0 Page 7 of 7