Qualification Process for Standard Scripts Hosted in the Open Source Repository ABSTRACT Dante Di Tommaso 1 and Hanming Tu 2 Tehran 1 F. Hoffmann-La Roche.

Slides:



Advertisements
Similar presentations
Quality Management Branch Cady Clark, MSN, RN Branch Manager Claudia Himes-Crayton, BSN, RN Patricia Palm, MS, RNC Nurse Consultants.
Advertisements

PhUSE Computational Science Symposium Working Groups An Experiment in Collaboration.
FDA scripts. Validation of script/programs. Heavy and light validation Check list FDA scripts Basis for discussion FDA: WG5 Project 02 18/8/2015 WG5 Project.
#PhUSE Standard Scripts Project Proposal for Qualification of Standard Scripts.
NOAA Metadata Update Ted Habermann. NOAA EDMC Documentation Directive This Procedural Directive establishes 1) a metadata content standard (International.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
JumpStart the Regulatory Review: Applying the Right Tools at the Right Time to the Right Audience Lilliam Rosario, Ph.D. Director Office of Computational.
Reporting and Using Evaluation Results Presented on 6/18/15.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
WG5 P02 Proposal2014 Qualification of Standard ScriptsStandard Scripts.
WG5 P02 Proposal2014 Qualification of Standard ScriptsStandard Scripts.
Standard Script All-Hands meeting September 29,
Standard Script All-Hands meeting September 29,
Contents Integrating clinical trial data Working with CROs
Development of Standard Scripts for Analysis and Programming Working Group – White Papers Project PhUSE Webinar January 2015 Mary Nilsson 1.
1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion:
ITEC224 Database Programming
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
Driving value through Standardization – Industry Challenges and Best Practices Henry Levy, partner-Life Sciences R&D European Lead.
United States Department of Agriculture Food Safety and Inspection Service 1 National Advisory Committee on Meat and Poultry Inspection August 8-9, 2007.
1 Click to edit Master title style Demographic Analysis Panel Current and Future State FDA/PhUSE CSS - Working Group 5 - Analysis Standards Script Examples.
CONFIDENTIAL The Ultimate Integration Challenge Jennifer Chin, Covance Hester Schoeman, Covance PhUSE Conference Berlin 2010 Paper DH06.
Current and Future Applications of the Generic Statistical Business Process Model at Statistics Canada Laurie Reedman and Claude Julien May 5, 2010.
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
Standard Script All-Hands meeting September 29,
Develop Project Charter
HIT Policy Committee METHODOLOGIC ISSUES Tiger Team Summary Helen Burstin National Quality Forum Jon White Agency for Healthcare Research and Quality October.
Standard Scripts - Project 2 Proposal for Qualification July 2014 Project 2 Update.
1 Noise & Nuisance Conference LOCAL AUTHORITY NOISE NUISANCE SERVICE EVALUATION 6 th October 2006 John Boyle Associate Director.
Using EDC-Rave to Conduct Clinical Trials at Genentech Susanne Prokscha Principal CDM PTM Process Analyst February 2012.
Development of Standard Scripts for Analysis and Programming PhUSE Annual Conference October 2014 Mike Carniello 1.
PhUSE Computational Science Working Group Update 24 November 2015 Development of Standard Scripts for Analysis and Programming.
Copyright © 2015, SAS Institute Inc. All rights reserved. Future Drug Applications with No Tables, Listings and Graphs? PhUSE Annual Conference 2015, Vienna.
White Papers to Fill the Gaps of Standardization of Tables, Figures, and Listings (Creating Standard Targets) Analyses and Displays for Vital Signs, ECG,
Emerging Technologies Semantic Web and Data Integration This meeting will start at 5 min past the hour As a reminder, please place your phone on mute unless.
Development of Standard Scripts for Analysis and Programming 17 March 2014 PhUSE Computational Science Symposium Conference Summary.
WG5 P02 Proposal2014 Qualification of Standard ScriptsStandard Scripts.
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.
The PhUSE Therapeutic Area Wiki Page Angelo Tinazzi 1, Oliver Wirtz 2, Christian Mueller 3, Sascha Ahrweiler 2 1 Cytel Inc, Geneva (Switzerland), 2 UCB.
Event-Level Narrative
Title of the Change Project
Chapter 10 Software Quality Assurance& Test Plan Software Testing
TechStambha PMP Certification Training
SEER Case Consolidation Study: Design & Objective
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
An Experiment in Collaboration
Standard Analyses and Code Sharing Summary for the Best Practices for Data Collection Instructions Project Team Mary Nilsson 20 March 2017.
Script Metadata for Sharing
Standard Analyses and Code Sharing Working Group
In-Depth Report from Optimizing Data Standards Working Group
Standard Scripts Project 2
Standard Analyses and Code Sharing
Job Analysis CHAPTER FOUR Screen graphics created by:
Bob Friedman, Xybion; Anthony Fata, SNBL
Overview of the Standard Analyses & Code Sharing Working Group
An Update on the CS Standard Analyses and Code Sharing Working Group Nancy Brucken, Principal Statistical Programmer, Syneos Health; Jared Slain, Associate.
Standard Analyses and Code Sharing
Development of Standard Scripts for Analysis and Programming
Standard Scripts Project 2
WG5 P02 Proposal 2014 Qualification of Standard Scripts
Standard Scripts Project 2
Standard Analyses and Displays for Common Clinical Trial Data:
Specific Safety Monitoring Tools & How This Will Benefit Drug Safety
Safety Analytics Workshop – Computational Science Symposium 2019
PhUSE Standard Analyses and Code Sharing Working Group
Standard Scripts Project 2
WG5 P02 Proposal 2014 Qualification of Standard Scripts
Version 1 Version 2 Review Published
Presentation transcript:

Qualification Process for Standard Scripts Hosted in the Open Source Repository ABSTRACT Dante Di Tommaso 1 and Hanming Tu 2 Tehran 1 F. Hoffmann-La Roche Ltd., Basel, Switzerland; 2 Accenture, Wayne, PA, USA Industry standards have evolved over time for data collection (CDASH), observed data (SDTM), and analysis datasets (ADaM). Using these standards as a foundation, a cross-industry working group within the PhUSE Computational Science Symposium (CSS) continues to establish standard analyses for data that are common across therapeutic areas, and a repository for SAS and R programs to analyze these data (laboratory measurements, vital signs, ECG, adverse events, demographics, medications, dispositions, hepatotoxicity, pharmacokinetics). Development of these standard tables and figures with associated scripts will lead to improved product life-cycle evaluation by ensuring reviewers receive the desired analyses for the evaluation of patient safety. More importantly, having an organized process for shared learning of improved methodologies can lead to earlier safety signal detection and better characterization of the safety profile of our products. The PhUSE CSS working group Development of Standard Scripts for Analysis and Reporting made substantial progress in 2014 to establish a code repository for standard analyses. The objective of this poster is to describe this cloud-based repository, and our process for qualifying these open source programs that support clinical trial research, reporting, and analysis. Computational Science Symposium, 2015 Annual Conference, March 15th – 17th, 2015, Maryland, USA Nine white papers at various stages –ECGs, Vitals, Labs – Central Tendency  Finalized October 2013 –ECGs, Vitals, Labs – Outlier/Shifts  Draft 3 Review ongoing – Target Q –Adverse Events  Draft 1 Review ongoing – Target Q –Demographics, Disposition, Medications  Finalized October 2014 –Hepatotoxicity  In progress – Call for volunteers –Pharmacokinetics  Finalized March 2014 –QT Studies  In progress – Volunteers needed –Questionnaire  In progress – Volunteers needed –Events of Special Interest  In progress – Volunteers needed Final White Papers: Draft White Papers: EXAMPLE DISPLAYS FROM THE WHITE PAPERS Visualize changes over time, and changes from baseline Assess the impact of outliers (out-of-range values in red) Easy to see treatment differences Summary table complements box plot Outliers/Shifts SCRIPT REPOSITORY – THE VISION Outliers/shifts analysis for safety measures Min. & Max. Baseline vs. Post-baseline comparisons Scatter plot of patient-level values Shift table summaries Treatment-emergent High/Low table SCRIPT REPOSITORY SUMMARY OF STANDARDIZATION CONCLUSIONS Industry standards have evolved over time for collected (CDASH), observed (SDTM), and analysis data (ADaM). Shared learning of improved methodologies can lead to earlier safety signal detection and better safety profiles. Our working group volunteers are delivering standard data displays based on industry input and review. We have established an open-source repository for sharing SAS and R scripts across the industry. We now aim to deliver standard scripts that can be used across the industry to deliver standard displays & analyses. We welcome new members! Contact information on PhUSE WHITE PAPER SUMMARY Mean Changes–Boxplots PhUSE Repository: – orhttp://code.phuse.com – Google Code to host the script repository –MIT open-source license –Process guidelines under development –24 SAS and 3 R scripts contributed by 2015 Established the basic structure and process Folder structure and naming conventions Required metadata and recommended programming style for scripts Roles and responsibilities Tasks and duties Process of tracking issues Test data and validation documentation Qualification of Scripts in our Repository Roles Contributor:Anyone with skill & interest Developer:A volunteer familiar with our objectives Tester:A volunteer familiar with our objectives Reviewer:Contributors to our white papers States Contributed:Script received from any source Develop:A volunteer is progressing the script Review:A volunteer is reviewing the script Qualified:Successful review, ready for public use ContributedDevelopReviewQualified o Initial state o Unknown are: Completeness Appropriateness & accuracy vis-à-vis specified target Quality & flexibility o Core components: Contact info Specifications White paper ID Target ID Script Header & YML GPP Tests & Test Data o Reviewer: Consult with Dev on appropriateness of target & script Decide whether to accept in repository Consult with Dev on test scope & defns o Developer: Review components Complete minimum components Implement tests Update test data as needed Consult contributor, as possible o Tester: Checks components Reviews Qualification Workbook Executes tests Confirms a good user experience Resolves findings with Developer Confirms success to Developer o Reviewer confirms Script functionality matches intentions Any changes to previously qualified test outputs o Developer updates: Script metadata, all YML information Script attributes State of script Link to Qual Wkbk etc. Central Qualification Workbook Central test data with new data required Central qualification outputs with new and updated outputs