SAE data entry: Clinical versus Pharmacovigilance standards Daniel Becker Solvay Pharmaceuticals Hannover, Germany T: +49 511.

Slides:



Advertisements
Similar presentations
Adverse Events and Serious Adverse Events
Advertisements

Safety Reporting IN Clinical Trials
ADVERSE EVENT REPORTING
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
Focused on Pulmonology and Hepatology
Expedited Reporting/DAERS May 13, 2011 Oluwadamilola Ogunyankin, M.D. Chinedum Abanobi, M.D. DAIDS Regulatory Support Center (RSC) Oluwadamilola Ogunyankin,
Adverse Event Reporting. Reporting Adverse Events Adverse Events (AEs) are “... any untoward medical occurrence in a subject that was not previously identified.
SAE Reconciliation How to handle ‘a waterfall’ of SAEs?
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
Update: 21 CFR PART 312 FDA Safety Reporting Requirements for INDs
Life Sciences Accelerated R&D Services The Science of Getting Products to Patients Faster Study Data Standardization Plan Use Case Experience Dave Izard.
Brookhaven Science Associates U.S. Department of Energy 1 Brookhaven National Laboratory Protocol Compliance Monitoring Darcy Mallon May 7, 2009.
INTRODUCTION TO ICD-9-CM PART TWO ICD-9-CM Official Guidelines (Sections II and III): Selection of Principal Diagnosis/Additional Diagnoses for Inpatient.
Using EDC-Rave to Conduct Clinical Trials at Genentech
Basic Pharmacovigilance Training
Clinical Data Management is involved in all aspects of processing the clinical data, working with a range of computer applications, database systems.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Stroke Hyperglycemia Insulin Network Effort (SHINE) Trial Adverse Event Reporting Catherine Dillon.
Requirements of EU pharmacovigilance legislation for distributors Julia Sipos Quality Management Director Pharmacovigilance coordinator Version 03.
M ODULE H I NTERIM M ONITORING V ISIT Denise Thwing 21 Apr Version: Final 21-Apr-2010.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
Performing the Study Data Collection
How to process data from clinical trials and their open label extensions PhUSE, Berlin, October 2010 Thomas Grupe and Stephanie Bartsch, Clinical Data.
Adverse Event Reporting.
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.
Electronic Transfer of Serious Adverse Events to Global Pharmacovigilance PhUSE, Berlin, October 2010 Eva Bervar Bayer Vital GmbH, Leverkusen.
Joint Research & Enterprise Office Training The team, the procedures, the monitor and the Sponsor Lucy H H Parker Clinical Research Governance Manager.
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.
ICH V2 An FDA Update Susan Lu Office of Drug Safety Center for Drug Evaluation and Research FDA January 21, 2003.
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
Survey of Medical Informatics CS 493 – Fall 2004 October 11, 2004 V. “Juggy” Jagannathan.
AE/SAE/EAE Identification and Reporting AE/SAE/EAE Identification and Reporting.
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
Using EDC-Rave to Conduct Clinical Trials at Genentech Susanne Prokscha Principal CDM PTM Process Analyst February 2012.
FDA Regulatory and Compliance Symposium
Serious Adverse Event Reporting Start-up Meeting March 25, 2010 Kingston, ON.
PRIMA Investigator Meeting Friday, June 16, 2006 Grand Sofitel Demeure, Amsterdam Stéphanie Baulu, Delphine Germain & Gilles Salles.
Public Libraries Survey Data File Overview. What We’ll Talk About PLS: Public Libraries Survey State level data Public library data (Administrative Entities)
© 2015 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Comments on FDA Concept Paper Sidney N. Kahn, MD, PhD President Pharmacovigilance & Risk Management, Inc. Risk Assessment of Observational.
CONDUCTING COMPLIANCE ASSESSMENTS Allen Ditch Director Corporate Quality Bristol Myers Squibb Medical Research Summit March 6, 2003.
1 Data Quality Report Quality Assurance Report Live Data Download Site Datasets (SAS) Research Datasets Customized Cohort Reports Outcome Analytics Patient.
How Good is Your SDTM Data? Perspectives from JumpStart Mary Doi, M.D., M.S. Office of Computational Science Office of Translational Sciences Center for.
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.
1 SAE Centralized Report and Review Process April 2012.
11 iv. Create standard data collection materials
Software Project Configuration Management
8. Causality assessment:
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
Expedited Adverse Event Reporting Requirements
*Continue on SAE supplemental page CTT21 A if more space is required
Remote Monitoring of Adverse Events
Combination products The paradigm shift
In-Depth Report from Optimizing Data Standards Working Group
E-CRF Overview Oracle® Clinical Remote Data Capture Training (Version 4.6 HTML) e-CRF Completion John McDonach Manager CDM, PPD.
This presentation has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational purposes.
11 iii. Define management and supervision roles and responsibilities
Adverse Event Reporting _____________________________
Discrepancy Management
Dr Tim England TICH-2 SAE adjudicator
Adverse Event Analysis
Good clinical practice
Serious Adverse Event Reconciliation
Presentation transcript:

SAE data entry: Clinical versus Pharmacovigilance standards Daniel Becker Solvay Pharmaceuticals Hannover, Germany T: © Daniel Becker PSDM, Weesp, 22 May 2008

2 Who am I?  Global Safety Physician in Solvay Global Clinical Safety (part of Global Clinical Development)  Chair of Solvay-Quintiles Joint Clinical Safety and Coding Team  Solvay SAE reporting coordinator

3 Disclaimer These are my current views and not necessarily those of every concerned Solvay colleague

4 SAE data discrepancies between Pharmacovigilance and Clinical databases: Origins I.Different philosophies II.Different industry standards III.Multiple datasets IV.Technical aspects

5 I. Philosophies Pharmacovigilance Safety first! Clinical CRF data authenticity first!

6 Consequences (1) Pharmacovigilance data entry 1.interpretation of supplied data is entered 2.if inconsistent data is supplied (e.g. SAE report vs. discharge summary) the medically worse data is entered 3.selected non-serious AEs are updated to medically serious Clinical data entry 1.data is entered/accepted (in case of eCRF) as is 2.only data reported in the CRF/as query response is accepted 3.no change in seriousness

7 Consequences (2) Pharmacovigilance data entry  potential AEs mentioned e.g. in the narrative which are not reported as AEs are extracted and entered  worst-case assumption is entered, and confirmation is requested thereafter  Pharmacovigilance controls entries Clinical data entry  no data transfer to other variable  questionable entry is kept and query is issued  Reporter controls entries

8 II. Industry Standards Pharmacovigilance ICH-E2B Clinical SDTM, HL7,...

9 Consequences  different variables and formats  not all related variables may match in definition, formats and/or rules  particularly, if non-current versions of the industry standards are used or when not defined in them

10 III. Multiple datasets Pharmacovigilance 1.SAE form entry, as well as formless submissions (e.g., hospital discharge summary, query replies) 2.Pharmacovigilance database Clinical 3.CRF entries in several modules (demographics, concomitant medication, adverse event) 4.Clinical database

11 Consequences  investigators regularly report inconsistently to the clinical versus the pharmacovigilance databases or provide corrections / relevant follow-up information like a final hospital discharge diagnosis only to one database  unless the same person codes for both databases, codes will not always match  if a standard or its guide is modified the other three may have to be updated, too

12 IV. Technical aspects (1) Pharmacovigilance  database never locks  medical history occurs before the SAE  SAE start date is date of first sign / symptom / diagnosis. Clinical  database locks at study end  medical history occurs before the study. Medical events between study start and SAE are AEs.  SAE start date is date AE became serious.

13 IV. Technical aspects (2) Pharmacovigilance  If an SAE started during core study but extended into extension study it is recorded under the core study only.  Concomitant medication is only that administed at the time of the SAE and which is non- suspect to have caused the SAE. Clinical  If an SAE started during core study but extended into extension study it is recorded under both studies.  Concomitant medication is any medication administered during the study, whether suspect to have caused the SAE or not.

14 IV. Technical aspects (3)  unless data entry in both databases is done by the same person, discrepancies are inevitable, e.g. inconsistent ➤ splitting of verbatims (e.g., „pneumonia, malaise“ in „pneumonia“ and „malaise“) ➤ combination of related, concomitant events to code to inclusive term (e.g., „shortness of breath“ and „asthma“ to „asthma“) ➤ duplication of verbatims to code to two terms (e.g., „toxic psychosis“ duplicated and coded to „toxic reaction“ respectively „psychosis“)

15 My thoughts  I don‘t see how you can get around two databases  reconcile only medically most relevant items, e.g.: 1. Study Number 2. Subject Number 3. Randomization Number (if available) 4. Gender 5. Date of Birth 6. SAE verbatim 7. Stop Date 8. Ongoing 9. Outcome 10. Study Drug-Event relationship as judged by the investigator 11. Action taken with study drug

16 Questions? Comments?