Examining Rescue Studies

Similar documents
esource Initiative ISSUES RELATED TO NON-CRF DATA PRACTICES

Why organizations need MDR system to manage clinical metadata?

OC RDC HTML User Guide

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

Chapter 10: Regulatory Documentation

How to review a CRF - A statistical programmer perspective

CRA OC RDC Classic User Guide

!"# $ # # $ $ % $ &% $ '"# $ ()&*&)+(( )+(( )

EDC integrations. Rob Jongen Integration Technology & Data Standards

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

Investigator Site OC RDC PDF User Guide

Study Composer: a CRF design tool enabling the re-use of CDISC define.xml metadata

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

Smart Measurement System for Late Phase

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

Standard Operating Procedure Clinical Data Management

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

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

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

Comprehensive Capabilities Comparison

Chapter 8: SDLC Reviews and Audit Learning objectives Introduction Role of IS Auditor in SDLC

How to write ADaM specifications like a ninja.

Sparta Systems TrackWise Digital Solution

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

5 Data processing tables, worksheets, and checklists

InForm Functionality Reference Manual for Sites. Version 1.0

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

RealWorld Data solutions for PMS studies

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

Pharmaceuticals, Health Care, and Life Sciences. An Approach to CDISC SDTM Implementation for Clinical Trials Data

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

Sparta Systems TrackWise Solution

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

The Lilly Safety Mailing Process

OC RDC 4.6. User Guide

FDA XML Data Format Requirements Specification

Design Better. Reduce Risks. Ease Upgrades. Protect Your Software Investment

Recommendations for Implementing an Information Security Framework for Life Science Organizations

CDISC SDTM and ADaM Real World Issues

Magento Enterprise Edition Customer Support Guide

REDCap User Guide Version: September 30, 2010

Clinical trial data management technology Guide

Taming Rave: How to control data collection standards?

User Guide 16-Mar-2018

Converting Data to the SDTM Standard Using SAS Data Integration Studio

Discrepancy Management

ORACLE RDC ONSITE RESEARCH COORDINATOR TRAINING

Local Lab Normal Range Management Tool (LNMT) Site Job Aid for Late Stage Development

Federal Agency Firewall Management with SolarWinds Network Configuration Manager & Firewall Security Manager. Follow SolarWinds:

Information Technology Procedure IT 3.4 IT Configuration Management

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

October p. 01. GCP Update Data Integrity

Release Notes Viedoc 4.35

Creating a Patient Profile using CDISC SDTM Marc Desgrousilliers, Clinovo, Sunnyvale, CA Romain Miralles, Clinovo, Sunnyvale, CA

Advantages of a real end-to-end approach with CDISC standards

How to choose a website design firm

A company built on security

ehepqual- HCV Quality of Care Performance Measure Program

eclinical ecrf Guideline

The Project Charter. Date of Issue Author Description. Revision Number. Version 0.9 October 27 th, 2014 Moe Yousof Initial Draft

No conflict of interest to disclose

Sparta Systems Stratas Solution

Standardising The Standards The Benefits of Consistency

Release Highlights

Business Continuity Management Standards A Side-by-Side Comparison

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

Data Science Services Dirk Engfer Page 1 of 5

IBIS. Case Study: Image Data Management System. IBISimg at Novartis using Oracle Database 11g Multimedia DICOM

Data Integrity in Clinical Trials

Real Time Clinical Trial Oversight with SAS

Get your business Skype d up. Lessons learned from Skype for Business adoption

CRF Design for Data Standards. David A. Scocca

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

Solving Legacy EMR Data Access with Interoperability. Presenter: Tom Wilson Sentara Healthcare

ELECTRONIC SITE DELEGATION LOG (esdl) USER MANUAL

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

OE-PM Project Charter Document

Implementation of Data Cut Off in Analysis of Clinical Trials

Clinical trial databases are a crucial investment in clinical research. Part 3 Database Development Considerations and REDCap Demo

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

Discrepancy Statuses In OC RDC PDF Discrepancy Management Window:

Data Protection. Plugging the gap. Gary Comiskey 26 February 2010

ORACLE RDC ONSITE RESEARCH COORDINATOR TRAINING

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

Risk Priority Index - Introductory User Guide

IT Governance ISO/IEC 27001:2013 ISMS Implementation. Service description. Protect Comply Thrive

MOIS Release Notes Version

Information Security Controls Policy

Brooke Roecker, Kristen Ward, Chris Mickle, Sarah Wright & Shauna McKellar

SITE FILE MANAGEMENT

Validation of a CMS Software

ABSTRACT INTRODUCTION WHERE TO START? 1. DATA CHECK FOR CONSISTENCIES

OG0-091 Q&As TOGAF 9 Part 1

01.0 Policy Responsibilities and Oversight

Serious Adverse Events Reporting Form Completion Guidelines

CDISC Standards End-to-End: Enabling QbD in Data Management Sam Hume

Data for Accountability, Transparency and Impact Monitoring (DATIM) MER Data Import Reference Guide Version 2. December 2018

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

DISASTER RECOVERY PRIMER


Transcription:

White Paper Examining Rescue Studies Introduction The purpose of this White Paper is to define a Rescue Study, outline the basic assumptions, including risks, in setting up such a trial based on DATATRAK s prior experiences, and present the actions that can help avoid or mitigate these risks during a deployment. What is a Rescue Study? A Rescue Study is a clinical trial, previously conducted in paper, EDC, or both, that was run by one or more vendors over time, but is now contracted to continue with a different vendor. The new vendor will take over certain project duties and rescue the project. The study may have been in a Production Environment for several months or even years. Data may have been entered into a client database through double data entry, entered manually in another EDC system, or other data may have been imported into the EDC or database system, etc. Why Do Studies Need Rescuing? Conducting even one Clinical Trial is a monumental task. Many issues can arise during the course of a clinical trial and negatively affect a study timeline, which in turn delays reporting to the FDA, and can ultimately delay a chance at profitability. It may be that tasks assigned to study personnel (such as coordinators, monitors, medical coders, etc) are not being performed at the level expected of them. This can result in poor quality data or data that is missing altogether. Sometimes a vendor will have an unexpected problem with personnel turnover or an increased amount of work generated from another study, and the vendor will not be able to provide an adequate amount of qualified resources to the project. In instances of vendor consolidation, many software programs become legacy systems and resources to support these systems are at minimal or non existent levels. Sponsors might also encounter problems with data analysis and FDA reporting. In short, a study most often needs rescuing when it is in danger of not being completed within an appropriate timeline, its quality is suspect or it has lost access to resources. One other possibility is that unexpected results have caused a regulatory agency to halt the trial. Rescue Concerns Although rescue studies are usually intended to speed up study timelines, some time must be spent on the rescue process itself. Therefore, rescue study vendors are carefully chosen and must demonstrate the ability and experience necessary to perform an efficient rescue, enabling the study sites to perform data entry and Examining Rescue Studies datatrak.com marketing@datatrak.com Page 1 of 6

cleaning tasks with minimal interruption. The following are a list of requirements to help ensure a seamless migration or rescue: 1. New clinical database developed quickly more quickly than in a normal contract 2. New ecrfs designed to provide the easiest transition for existing study personnel 3. Import of existing study data performed quickly and accurately 4. Query handling and other data cleaning tasks made more efficient shortening study timeline 5. Problem areas specific to the study must be assessed and then improved Key Elements for Consideration There are several key items that must be addressed before beginning development on a Recue Study. First, the scope of the project must be identified, and the client s expectations set accordingly. Project timelines, costs and deliverables must be defined or estimated. Key stakeholders in the process must be identified, as well as any client personnel who will be primary contacts. Any risks that may affect the success of the project must be identified and planned for as well as measurements for quality. See Figure 1 on the following page. In order to complete these items, questions must be asked about project specifications. File Import of Existing Electronic Data 1. How will the existing data be entered into the ecrf? a. Will there be a file to import? Paper? 2. What are the specifications of the import file? a. Is there one file to import or several? b. If several, are all the files of the same type? (Text, ASCII, SAS) c. Is the format type(s) supported? d. Are all of the fields in the file consistent? i. In order to map the file to the ecrf, each of the fields mapped needs to be in the same location within the file. ii. The fields of the file need to be consistent in terms of format. For example, if you have a field that captures weight with the unit of measure as pounds but it periodically changes to kilograms, you will have inconsistencies when you export the data. The same problem may occur if the field is formatted to be an integer in one file but set as a date only in another file. e. Who will be responsible for reviewing and validating the file prior to design? f. How will file discrepancies be resolved? Who will be responsible for approving? In some cases, the file will need to be imported to create the existing patients and completed visits before the new data entry can begin. If the timelines set by the client are too short or do not take the import file review into account, the project Examining Rescue Studies datatrak.com marketing@datatrak.com Page 2 of 6

may be at risk of failure. This is a key expectation that needs to be set early in the project planning phase. Double Data Entry of Existing Paper Data 1. Will paper CRF s need to be entered through double data entry? 2. If yes, who will enter the data, the client or the vendor? 3. Does the client have an established DDE guideline or SOP that should be followed? 4. If DATATRAK or one of it s connect partners is asked to perform the data entry, the clinical trialprocesses and SOPs should be reviewed first. This step is always completed early in the planningphase to ensure client expectations are being met and any gaps that need to be addressed are identified before the ecrf design starts. 5. What are the timelines for entering the data? Can this be done concurrently with the live data entry or does it need to be completed prior? Once a plan for migrating the existing data into the system is established, the next step is to understand the design requirements. This part of the process is similar to any other EDC study. The same planning, design, testing, and approval process applies; however, there are historical issues that can have a large impact on the design. Examining Rescue Studies datatrak.com marketing@datatrak.com Page 3 of 6

ecrf Design 1. Does the client have an existing paper CRF? 2. If so, has this been used throughout the trial or has it changed over time (mid study changes or amendments)? If the CRF has changed, it can greatly affect the import and export of the data. For example, the client may want to eliminate certain questions or forms. What happens to the existing data that needs to be imported but the question or form no longer exists? 3. What happens if the question text on a form is changed? This may completely change the meaning of an answer previously recorded. 4. If the metadata in the file varies within a question, you may consider only importing the answer and having a second dropdown or other type field to associate it with. As in the example above, you could import the numeric value in one field and have another field to select either pounds or kilograms. However, this will have an impact on the auditable fields, which may have an impact on the overall budget. 5. The client may want to import all of the data but hide certain questions from the ecrf. This data would then appear on the export but not be collected going forward. Finally, we need to consider our points of contact and the associated expectations and risks. Because this is a rescue study, we are going to be taking the project over from one or more previous vendors. Often, the reason we are getting the trial is that the previous vendor either failed or was unable to manage the project. This will provide quite a challenge to both DATATRAK and the client, as the key personnel with knowledge of the trial are often unavailable or unwilling to help with the project. These are some of the key points to consider regarding expectation and risk. Stakeholders, Expectations, and Risk 1. Who with knowledge of the project is available for contact? This may include lab companies, the client data management or clinical team, executives or previous vendors. 2. Who will have the power to make the final decisions? Who is driving the timelines? Who can help coach or assist in obtaining information? 3. Is there adequate time to review the import file prior to ecrf design? 4. What flexibility in time and cost is allowed if the file does not meet the import mapping requirements? 5. What experience levels do these users have in EDC and in rescue studies in particular? 6. Are the timelines and budgets in line with the estimated level of work? Will the client approve certain deliverables, such as the export mapping, to be done after deployment? How can DATATRAK Help? The DATATRAK eclinical platform has several key underlying features that make it ideal for taking on a rescue study. Examining Rescue Studies datatrak.com marketing@datatrak.com Page 4 of 6

Single Database Patient CRFs, adverse events, lab data and other types of data can all be stored in the same database. This allows for fast, accurate reporting with no overhead cost of reloading data into a separate database. All trial revisions are tracked and retrievable online. Different revisions can be loaded to environments specifically for designing, testing and approving clinical studies. One Interface DATATRAK provides users with a consistent and intuitive interface across all modules from one username and password. This allows for seamless data integration and usability among data entry, coding, randomization, inventory and reporting tools. It is not necessary to switch between applications or spend countless hours providing backend data packaging. Import and Manage External Data DATATRAK eclinical features a highly flexible data import system as part of our integration capabilities. While normally used for items such as ECG and lab data, entire patient records can be imported with the push of a button. We support a large number of import formats (sas, excel, csv, text, xml, dat, and more) as well as industry standard formats such as HL7 ECG, ICH, CDISC, CDASH and SDTM. Advanced Data Monitoring Tools Because no two monitors approach data cleaning quite the same way, the Alert and Query Managers allow users to easily identify and manage unresolved edit checks and queries. Standard trial management reports allow users to quickly review the overall study progress, site metrics, visit schedules and more. Edit checks can be programmed into the eclinical application to alert coordinators and monitors to any potential problems as soon as the patients are imported into the system. Powerful scripting tools allow for complex edit checks to trigger onscreen alerts or even send emails directly to study personnel. Highly Flexible and Powerful System DATATRAK eclinical has a wide array of features designed to make conducting clinical trials easier. The following are just some of the many features available: The Form Manager identifies CRFs that need to be reviewed, source document verified or signed. Custom filters and labels group patients for efficiently managing data subsets and intermediate database locks. Real time data access provides up to the minute data review or exports. Adhoc reporting engine allows users to create data listings via an intuitive interface, including statistics, filters and multiple formats. Dynamically generated manager screens allow users to manage study progress. Users randomize patients and make drug assignments in a system that supports kits, open volume drug, drug lookup tables, permuted Examining Rescue Studies datatrak.com marketing@datatrak.com Page 5 of 6

block randomization, or dynamic randomization algorithms and more. Emails are sent to notify the team when randomization, un blinding or other key events occur. Drug Inventory provides control, management, and automation of drug supply fulfillment through a single interface. The advanced auto coding and smart synonym technology increases coding efficiency. In addition, DATATRAK s clinical and consulting services as well as those from our partners can provide relevant and needed resources surrounding the eclinical platform and trial processes. Summary The success of a rescue study depends on the quality of the data file being imported, developing realistic timelines to account for the pre design review work, setting client expectations, and above all communication. Inevitably, the biggest threat to the project s critical path will be the data import. If the fields being mapped are not consistent, if the data values or format of the fields change within the file, or if the question/form structure of the ecrf changes over time, the work effort to prepare the file for import will rise exponentially along with the costs. But, if the effort is made upfront to educate the stakeholders of the risks and to communicate the progress of the deliverables, the success of these projects can be greatly increased. Success in a rescue study also brings the added benefit of strong customer loyalty. Usually, these studies are a result of a project or vendor failure resulting in a negative customer experience. A successful deployment in a rescue situation can lead to a solid partnership going forward. Examining Rescue Studies datatrak.com marketing@datatrak.com Page 6 of 6