SECURE DATA OFFICE: AN INDEPENDENT TEAM THAT CAN COME TO THE RESCUE IN BLINDED TRIALS

Similar documents
AUTOMATED SDTM CREATION AND DISCREPANCY DETECTION JOBS: THE NUMBERS TELL THE TALE. Joris De Bondt PhUSE Conference Oct 2014

EDC integrations. Rob Jongen Integration Technology & Data Standards

How to write ADaM specifications like a ninja.

Examining Rescue Studies

From ODM to SDTM: An End-to-End Approach Applied to Phase I Clinical Trials


One Project, Two Teams: The Unblind Leading the Blind

esource Initiative ISSUES RELATED TO NON-CRF DATA PRACTICES

BioInformatics A Roadmap To Success. Data Management Plans. Wes Rountree Associate Director of Data Management Family Health International

Purpose: To describe the requirements for managing IP at the clinical site

CDASH Standards and EDC CRF Library. Guang-liang Wang September 18, Q3 DCDISC Meeting

Best Practices for E2E DB build process and Efficiency on CDASH to SDTM data Tao Yang, FMD K&L, Nanjing, China

How to review a CRF - A statistical programmer perspective

UNIVERSITY OF LEICESTER, UNIVERSITY OF LOUGHBOROUGH & UNIVERSITY HOSPITALS OF LEICESTER NHS TRUST JOINT RESEARCH & DEVELOPMENT SUPPORT OFFICE

PharmaSUG Paper PO03

Automate Clinical Trial Data Issue Checking and Tracking

PharmaSUG Paper PO22

PharmaSUG 2014 PO16. Category CDASH SDTM ADaM. Submission in standardized tabular form. Structure Flexible Rigid Flexible * No Yes Yes

An Introduction to Analysis (and Repository) Databases (ARDs)

IRT & ecoa: The Good, The Bad & The Ugly YPrime, inc. All Rights Reserved

Leveraging Study Data Reviewer s Guide (SDRG) in Building FDA s Confidence in Sponsor s Submitted Datasets

Discrepancy Statuses In OC RDC PDF Discrepancy Management Window:

Pooling Clinical Data: Key points and Pitfalls. October 16, 2012 Phuse 2012 conference, Budapest Florence Buchheit

Standard Operating Procedure Clinical Data Management

OC RDC 4.6. User Guide

Standard Operating Procedure. SOP effective: 06 February 2017 Review date: 06 February 2019

Michael Duvenhage / Tarun Bhatnagar. 08 Aug 2018

Discrepancy Management

OC RDC HTML User Guide

Clinical trial data management technology Guide

Tips on Creating a Strategy for a CDISC Submission Rajkumar Sharma, Nektar Therapeutics, San Francisco, CA

User Guide 16-Mar-2018

Paper FC02. SDTM, Plus or Minus. Barry R. Cohen, Octagon Research Solutions, Wayne, PA

A Simple Interface for defining, programming and managing SAS edit checks

Discrepancy Management

D4.2 Data Management System

Implementing targeted Source Data Verification (SDV) Strategy in idatafax

Taming the SHREW. SDTM Heuristic Research and Evaluation Workshop

Using EDC System: Benefits, Considerations, and Challenges. March 20, 2012

PharmaSUG Paper SP09

General Guidance for Maintaining a Regulatory Binder

Trial Cost Analysis Trial: Knee Surgery Study Sponsor: Principal Investigator: Hillary Resendes Total Enrollment: 8

How a Metadata Repository enables dynamism and automation in SDTM-like dataset generation

CDASH MODEL 1.0 AND CDASHIG 2.0. Kathleen Mellars Special Thanks to the CDASH Model and CDASHIG Teams

SDTM Implementation Guide Clear as Mud: Strategies for Developing Consistent Company Standards

Implementation of Data Cut Off in Analysis of Clinical Trials

Lex Jansen Octagon Research Solutions, Inc.

Standardising The Standards The Benefits of Consistency

Standard Operating Procedure. Data Management. Adapted with the kind permission of University Hospitals Bristol NHS Foundation Trust

The Wonderful World of Define.xml.. Practical Uses Today. Mark Wheeldon, CEO, Formedix DC User Group, Washington, 9 th December 2008

Reducing SAS Dataset Merges with Data Driven Formats

Demystifying Laboratory Data Reconciliation. The issues at hand

Why organizations need MDR system to manage clinical metadata?

Standard Operating Procedure. SOP full title: Sponsor processes for reporting Suspected Unexpected Serious Adverse Reactions

Preparing the Office of Scientific Investigations (OSI) Requests for Submissions to FDA

Data Collection & Management

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

Document Version: 1.0. Purpose: This document provides an overview of IBM Clinical Development v released by the IBM Corporation.

Automation of SDTM Programming in Oncology Disease Response Domain Yiwen Wang, Yu Cheng, Ju Chen Eli Lilly and Company, China

Chapter 10: Regulatory Documentation

SAS Training BASE SAS CONCEPTS BASE SAS:

Standard Operating Procedure (SOP) OPTIMISE II Database User Guide SOP 007

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

Advanced Data Visualization using TIBCO Spotfire and SAS using SDTM. Ajay Gupta, PPD

Johannes Ulander. Standardisation and Harmonisation Specialist S-Cubed. PhUSE SDE Beerse,

Bay Area CDISC Network: PhUSE Working Group for Inspection Site Selection Data Standards

InForm Functionality Reference Manual for Sites. Version 1.0

PhUSE Paper SD09. "Overnight" Conversion to SDTM Datasets Ready for SDTM Submission Niels Mathiesen, mathiesen & mathiesen, Basel, Switzerland

SAS CLINICAL SYLLABUS. DURATION: - 60 Hours

ALEA instructions for Local Investigators

Standards Metadata Management (System)

Key. General. Host Account Functionality. Included, no-cost Not Included Add-on/Low cost $ Add-on/High cost $$$

Data Edit-checks Integration using ODS Tagset Niraj J. Pandya, Element Technologies Inc., NJ Vinodh Paida, Impressive Systems Inc.

Legacy to SDTM Conversion Workshop: Tools and Techniques

Release Notes IBM Clinical Development v (formerly eclinicalos) Release Date: 03 February 2017

CRA OC RDC Classic User Guide

Topics Raised by EFPIA. Webinar on Policy Jun 2017, FINAL. Presentation

Advanced Visualization using TIBCO Spotfire and SAS

Annual Report 2017 (Jan. Dec.) April 3, 2018 Japan CRO Association

CDISC SDTM and ADaM Real World Issues

Study Data Reviewer s Guide Completion Guideline

Traceability Look for the source of your analysis results

InForm for Primary Investigators Performing esignature Only (v4.6) Narration

Reporting & Visualisation : D un Dun standard maison au format CDISC 02/02/2016 CDISC GUF 1

October p. 01. GCP Update Data Integrity

Comprehensive Capabilities Comparison

How to clean up dirty data in Patient reported outcomes

Pooling strategy of clinical data

Integrated Safety Reporting Anemone Thalmann elba - GEIGY Ltd (PH3.25), Basel

Version 11, JAN2017. Regulatory Document Approval Parameters for WebDCU TM POINT. People Document Collection REGULATORY REQUIREMENTS

This is a controlled document. The master document is posted on the JRCO website and any print-off of this document will be classed as uncontrolled.

Standardizing FDA Data to Improve Success in Pediatric Drug Development

Argus to Oracle Clinical SAE Reconciliation. Dipti Kadam. DBMS Consulting 12 October 2010 Argus Focus Group Session 14

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

Introduction to CDASH

NEWCASTLE CLINICAL TRIALS UNIT STANDARD OPERATING PROCEDURES

CRF Design for Data Standards. David A. Scocca

ODM The Operational Efficiency Model: Using ODM to Deliver Proven Cost and Time Savings in Study Set-up

SAS (Statistical Analysis Software/System)

Now let s take a look

Transcription:

SECURE DATA OFFICE: AN INDEPENDENT TEAM THAT CAN COME TO THE RESCUE IN BLINDED TRIALS Annelies Van Zeveren, PhD Project Manager Biometrics and Medical Affairs SGS Life Science Clinical Research PhUSE US Connect 2018

OVERVIEW n Introduction n Secure Data Office tasks Randomisation Data The Pharmacokinetic (PK) Data flow Other unblinding data streams Cleaning of unblinding data Deliver blinded result transfers Deliver data to unblinded teams n Conclusion 2

OVERVIEW n Introduction n Secure Data Office tasks Randomisation Data The Pharmacokinetic (PK) Data flow Other unblinding data streams Cleaning of unblinding data Deliver blinded result transfers Deliver data to unblinded teams n Conclusion 3

INTRODUCTION n Double blind study: Subject and investigator are unaware of treatment status Parties without access to unblinding data: subjects, investigators, Data Management, Statistics, PK analysts, sponsor Parties with access to unblinding data: pharmacists, bio-analytical lab, unblinded CRA n Unblinding data: Any data that can unblind the study n Downside: Treatment information, Pharmacokinetic & Immunogenicity data Biomarkers.. Unblinding data is not cleaned Delay in clinical database lock or unblinding data are not included in lock Crunched timelines for some parts of the analysis 4

Who should handle randomisation data and other unblinding data (e.g. PK, biomarker, immunogenicity data)?

SD OFFICE n Dedicated team, physically separated from other study team members n Separate databases and secure server locations n Clearly defined processes in SOPs and WIs 6

OVERVIEW n Introduction n Secure Data Office tasks Randomisation Data The Pharmacokinetic (PK) Data flow Other unblinding data streams Cleaning of unblinding data Deliver blinded result transfers Deliver data to unblinded teams n Conclusion 7

RANDOMISATION DATA n Generation of randomisation lists Documented randomisation list specifications By SAS programmers with statistical background Distribution to required recipients n Support and handle of unblinding data in IWRS system n Creation of SDTM dataset containing randomisation information based on following input Subject information: from data management Receive randomisation information: from external vendor or internally created 8

PK DATA FLOW n PK data (Identifiers and results): Bio-analytical lab SDO n Blinded transfers: SDO DM n Cleaning is performed by DM n DM delivers clean PC file to SDO Contains CRF and sample tracking data Without results n SDO delivers clean PC file with results to include at time of database lock 9

1 Central lab 3 Ship sample and shipping list BAN lab Ship sample, req. Form and shipping list 2 4 8 Investigational site Transfer ST file for reconciliation Transfer SAMPID file Transfer Results file ZOOM 1 Capture ecrf data into clinical database 5 Data management 7 Send identifier file Send clean PC without concentrati ons 6 SD Office Create merged PC 9 Complete PK flow Send locked Clinical database Create PP dataset 10 13 12 NCA output file NCA input file Clinical Pharmacology, Pharmacometrics 10

1 Central lab 3 Ship sample and shipping list BAN lab Ship sample, req. Form and shipping list 2 4 8 Investigational site Transfer ST file for reconciliation Transfer SAMPID file Transfer Results file Capture ecrf data into clinical database 5 Data management 7 Send identifier file Send clean PC without concentrati ons 6 SD Office Creation of PC dataset Create merged PC 9 11

1 Central lab 3 Ship sample and shipping list BAN lab Ship sample, req. Form and shipping list 2 4 8 Investigational site Transfer ST file for reconciliation Transfer SAMPID file Transfer Results file Capture ecrf data into clinical database 5 Data management 7 Send identifier file Send clean PC without concentrati ons 6 SD Office Create merged PC 9 Complete PK flow Send locked Clinical database Create PP dataset 10 13 ZOOM 2 12 NCA output file NCA input file Clinical Pharmacology, Pharmacometrics 11 12

CREATION OF PK INPUT FILES AND PP DATASET Create merged PC 9 Data management Send locked Clinical database 10 SD Office Create PP dataset 13 NCA output file 12 NCA input file Creation of PP dataset Clinical Pharmacology, Pharmacometrics 11 13

Without SD Office CREATION OF PK/PD INPUT FILES BY SDO Database lock Start programming input file Final PK/PD input (NCA/ NONMEM) file ready PK/PD modeling Results Issues in DB? DB re-opening With SD Office Start programming input file Issues in DB? Solved before DB lock Database lock PK/PD modeling Results Time Gain Final PK/PD input (NCA/ NONMEM) file ready 14

OTHER UNBLINDING DATA STREAMS: LAB DATA n Similar to PK data stream n Only unblinding analytes via SDO n SDTM domains: LB, PD, IS n DM unblinded at release Yes: combine LB parts by DM No: combine LB parts and release by SDO 15

OTHER UNBLINDING DATA STREAMS: PROTOCOL DEVIATIONS n Identification of unblinding protocol deviations (usually medication kit errors) Protocol deviation defined as Any medication kit misallocation Only treatment misallocations Medication kit number unblinding? Y SD Office involved SD Office involved N Detection of medication kit misallocations by data management SD Office involved 16

OTHER UNBLINDING DATA STREAMS: PROTOCOL DEVIATIONS n Assigned medkit = planned data n Dispensed medkit = actual data n Reconciliation of planned and actual data by SDO n SDO creates part of the DV domain: Deviations related to medkit or treatment misallocations 17

CLEANING OF UNBLINDING DATA n Only if cleaning of the unblinding content is required n Cleaning requirements: in secure data handling plan n Cleaning Checks are: Defined Documented Programmed Validated Ran n Review output of checks n Write and follow up queries: blinded/unblinded 18

DELIVER BLINDED RESULT TRANSFERS TO BLINDED TEAMS n PK data (Identifiers and results), other unblinding data: external vendor SDO n Blinded transfers: SDO Data Management (DM) n Cleaning is performed by DM n Results transfer with dummy identifiers/scrambled: SDO Statistics, PK analysts: dry runs 19

DELIVER DATA TO UNBLINDED TEAMS n PK data (Identifiers and results), other unblinding data: external vendor SDO n Blinded transfers: SDO Data Management (DM) n Cleaning is performed by DM n Results transfer with real production data: SDO Safety commitee, DRC, Statistical Support Group (SSG) 20

OVERVIEW n Introduction n Secure Data Office tasks Randomisation Data The Pharmacokinetic (PK) Data flow Other unblinding data streams Cleaning of unblinding data Deliver blinded result transfers Deliver data to unblinded teams n Conclusion 21

CONCLUSION n Role of SD Office Create randomisation lists and datasets Clean data before database lock PK data Medication kit misallocations Other unblinding data Prepare input files for PK/PD analysis upfront -> analysis can start earlier n Results Time gain after database lock Higher quality Unblinded data available before database lock for DRC, SSG, dry runs Off the critical path and key results can be met 22

THANK YOU FOR YOUR ATTENTION Questions? Meet us at the SGS booth 5 clinicalresearch@sgs.com EUROPE: +32 15 27 32 45 AMERICAS: + 877 677 2667 WWW.SGS.COM/CRO JOIN THE SCIENTIFIC COMMUNITY CONNECT ON LINKEDIN www.sgs.com/linkedin-life 23

Agriculture, Food and Life Clinical Research Annelies Van Zeveren Project Director Biometrics and Medical Affairs SGS Belgium NV Phone: + 32 15 40 49 89 Life Science Fax: +32 15 29 93 02 Generaal De Wittelaan 19a bus 5 E-mail : annelies.vanzeveren@sgs.com 2800 Mechelen Web : www.sgs.com/lcro Belgium Meet us at the SGS booth 5 clinicalresearch@sgs.com EUROPE: +32 15 27 32 45 AMERICAS: + 877 677 2667 WWW.SGS.COM/CRO JOIN THE SCIENTIFIC COMMUNITY CONNECT ON LINKEDIN www.sgs.com/linkedin-life 24