Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.

Slides:



Advertisements
Similar presentations
Principal Statistical Programmer Accovion GmbH, Marburg, Germany
Advertisements

ADaM Implementation Guide: It’s Almost Here. Are You Ready?
Labeling claims for patient- reported outcomes (A regulatory perspective) FDA/Industry Workshop Washington, DC September 16, 2005 Lisa A. Kammerman, Ph.D.
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Analysis Data Model (ADaM)
Managing and Analyzing Clinical Data
What’s New with CDISC Wayne R. Kubick CDISC CTO.
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
The Importance of CDASH
Quick tour of CDISC’s ADaM standard
ADaM Standards Wouter van Wyk. Why ADaM –SDTM purpose is to provide collected data Not designed for ease of analysis –ADaM purpose is to provide data.
Metadata Management – Our Journey Thus Far
It’s about Time! (to Event)
Model X-Ray Image Data into ADaM BDS Structure
…patient reported outcome (PRO) measure for your clinical study Dr Keith Meadows, DHP Research & Consultancy Ltd.
CDISC and how Stata can help us implement it
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
Dominic, age 8, living with epilepsy SDTM Implementation Guide : Clear as Mud Strategies for Developing Consistent Company Standards PhUSE 2011 – CD02.
A Taste of ADaM Presented by: Peng/Zik Liu MSD (Shanghai) Pharma Co.
CBER CDISC Test Submission Dieter Boß CSL Behring, Marburg 20-Mar-2012.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
PhUSE SDE, 28-May A SAS based Solution for define.xml Monika Kawohl Statistical Programming Accovion.
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
Renewable Energy Policy: A Local Government Perspective Alison Johnson for PEC624: Dissertation.
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
ODM-SDTM mapping Nicolas de Saint Jorre, XClinical June 20, 2008 French CDISC User Group Bagneux/Paris © CDISC & XClinical, 2008.
Antje Rossmanith, Roche 14th German CDISC User Group, 25-Sep-2012
Overview and feed-back from CDISC European Interchange 2008 (From April 21 st to 25 th, COPENHAGEN) Groupe des Utilisateurs Francophones de CDISC Bagneux.
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.
© Copyright 2008 ADaM Validation and Integrity Checks Wednesday 12 th October 2011 Louise Cross ICON Clinical Research, Marlow, UK.
King Fahd University of Petroleum & Minerals Department of Management and Marketing MKT 345 Marketing Research Dr. Alhassan G. Abdul-Muhmin Editing and.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
Dave Iberson-Hurst CDISC VP Technical Strategy
Research Project on Metadata Extraction, Exploration and Pooling: Challenges and Achievements Ronald Steinhau (Entimo AG - Berlin/Germany)
Overview of CDISC standards and use cases along the E2E data management process Dr. Philippe Verplancke ESUG Marlow, UK 27 May 2009.
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
WG4: Standards Implementation Issues with CDISC Data Models Data Guide Subteam Summary of Review of Proposed Templates and Next Steps July 23, 2012.
Preventing Wide and Heavy ADs Dirk Van Krunckelsven Phuse 2011, Brighton ADaM on a Diet.
The Question Bank Graham Hughes & Julie Gibbs Department of Sociology University of Surrey Research Methods Festival, July 2008
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
UC3: Complications Related to Unscheduled performed instead scheduled (TK) Raw visit numberVISITNUMLBDYLBDTC 2missing VISITVISITNUMSVDYSVDTCSVUPDES.
1. © CDISC 2014 Presented by Angelo Tinazzi, Cytel Inc, Geneva, Switzerland Presented at 2014 CDISC Europe Interchange, Paris Adapted for CDISC UK Network.
How good is your SEND data? Timothy Kropp FDA/CDER/OCS 1.
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.
ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC Joerg Guettner, Lead Statistical Analyst, Bayer Pharma, Wuppertal,
Analysis and Reporting Toolset (A&RT): Lessons on how to develop a system with an external partner David Smith AstraZeneca.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
Clinical database management: From raw data through study tabulations to analysis datasets Thank you for your kind introduction, and the opportunity to.
Dave Iberson-Hurst CDISC VP Technical Strategy
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
NJ CDISC Users Group April 17, 2014
+ THE DIABETES HEALTH PROFILE (DHP) DEVELOPMENT JOURNEY
Why use CDISC for trials not submitted to regulators?
Creating ADaM Friendly Analysis Data from SDTM Using Meta-data by Erik Brun & Rico Schiller (CD ) H. Lundbeck A/S 13-Oct
Traceability between SDTM and ADaM converted analysis datasets
It’s about Time! (to Event)
Patterns emerging from chaos
SDTM and ADaM Implementation FAQ
Fabienne NOEL CDISC – 2013, December 18th
SDTM and ADaM Implementation FAQ
WG4: Standards Implementation Issues with CDISC Data Models
Development Plans: Study Design and Dose Selection
An FDA Statistician’s Perspective on Standardized Data Sets
How to clean up dirty data in Patient reported outcomes?
Patient-reported outcomes: proportion of patients with clinically meaningful improvements in (A) SF-36 PCS and MCS at Week 52 and Week 104*†‡ and (B) HAQ-DI.
Analysis Data Model (ADaM)
PhUSE: Pooling WHODrug B3 Format
Presentation transcript:

Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK

2 Overview Introduction PRO data from source to analysis Data perspective Standards perspective Combining data and standards perspective Comprehensive Solution Summary

Introduction Patient Reported Outcomes Standardized questionnaire data Quality of Life, Mental Health, Disease Activity several levels of derivations are necessary CDISC standards: SDTM IG v3.1.2 ADaM IG v 1.0

Introduction Data Perspective vs. Standard Perspective Data Perspective: I have PRO data and I want to find a way to store it and to get the analysis done. Standards Perspective: I have a standard and how does the PRO data I collected fit into the standard structure without violating the rules. Combining both Perspectives: How do I adhere to the standards and still get my analysis done?

Data Perspective Patient Reported Outcomes: Example: SF-36 Health related quality of Life Standardized instrument - 36 items - 8 domains - 8 domains that could be adapted to population norms - 2 component scores

Source data PRO specific derivations Analysis specific derivations Original numeric response Domain scores Component scores Imputed visits Change from baseline Responder analysis … Rescaled Item Scores Data listings Tables, Figures Data Perspective: Levels of Derivation SF 36

Standards Perspective: CDISC SDTM and ADaM SDTM "defines a standard structure for study data tabulations that are to be submitted as part of a product application to a regulatory authority„ SDTM IG v3.1.2 ADaM "provides a framework that enables analysis of the data, while at the same time allowing reviewers and other recipients of the data to have a clear understanding of the data’s lineage from collection to analysis to results. „ ADaM IG v1.0 Comparison "Whereas ADaM is optimized to support data derivation and analysis, CDISC’s Study Data Tabulation Model (SDTM) is optimized to support data tabulation"

Standards Perspective: SDTM QS domain Result variables SDTM QSORRES  expected QSSTRESC  expected QSSTRESN  permissible

Standards Perspective: QSORRES SDTM IG section "The --ORRES variable contains the result of the measurement or finding as originally received or collected." SDTM IG section "Finding as originally received or collected (e.g. RARELY, SOMETIMES). When sponsors apply codelist to indicate the code values are statistically meaningful standardized scores, which are defined by sponsors or by valid methodologies such as SF36 questionnaires, QSORRES will contain the decode format, and QSSTRESC and QSSTRESN may contain the standardized code values or scores."

Standards Perspective: QSSTRESC / QSSTRESN SDTM IG section "Contains the finding for all questions or sub-scores, copied or derived from QSORRES in a standard format or standard units. QSSTRESC should store all findings in character format; if findings are numeric, they should also be stored in numeric format in QSSTRESN. If question scores are derived from the original finding, then the standard format is the score. Examples: 0, 1. When sponsors apply codelist to indicate the code values are statistically meaningful standardized scores, which are defined by sponsors or by valid methodologies such as SF36 questionnaires, QSORRES will contain the decode format, and QSSTRESC and QSSTRESN may contain the standardized code values or scores ".

Standards Perspective: QSSTRESC / QSSTRESN SDTM IG section "Contains the finding for all questions or sub-scores, copied or derived from QSORRES in a standard format or standard units. QSSTRESC should store all findings in character format; if findings are numeric, they should also be stored in numeric format in QSSTRESN. If question scores are derived from the original finding, then the standard format is the score. Examples: 0, 1. When sponsors apply codelist to indicate the code values are statistically meaningful standardized scores, which are defined by sponsors or by valid methodologies such as SF36 questionnaires, QSORRES will contain the decode format, and QSSTRESC and QSSTRESN may contain the standardized code values or scores".

Standards Perspective: QSSTRESC / QSSTRESN BP01 BP02 No 1 – 1 map !

Standards Perspective – Derived Scores SDTM IG provides examples where the SF36 domain scores are also part of the QS dataset BUT Domain scores may contain implicit or explicit imputations (missing item responses) Imputations are strongly discouraged by the CDER Guidance to Review Divisions regarding CDISC Data (FDA, 2011)  No derived scores in SDTM QS (?)

Standards Perspective - ADaM ADaM BDS structure is more flexible then SDTM Tailored to the need of the analysis "Analysis-ready" = one procedure away from the result

Combining both Perspectives Where to store what and how?

Combining both Perspectives Data perspective Standards perspective Source data PRO specific derivations Analysis specific derivations Original response (decode) Original numeric response Domain scores Component scores Imputed visits Change from baseline Responder analysis … QSORRES QSSTRESC/QSSTRESN Analysis ready ADaM datasets (AVAL AVALC) Basic ADaM dataset for Questionnaires (BADQ) SUPPQS SDTM ADaM QSORRES/QSSTRESC Rescaled Item Scores QSSTRESN

Combining both Perspectives SDTM "defines a standard structure for study data tabulations that are to be submitted as part of a product application to a regulatory authority„ SDTM IG v3.1.2 ADaM "provides a framework that enables analysis of the data, while at the same time allowing reviewers and other recipients of the data to have a clear understanding of the data’s lineage from collection to analysis to results. „ ADaM IG v1.0 Comparison "Whereas ADaM is optimized to support data derivation and analysis, CDISC’s Study Data Tabulation Model (SDTM) is optimized to support data tabulation"

Comprehensive Solution Questionnaire Clinical database SDTM QS dataset +SUPPQS BADQ datasets Tables and figures Data listings ADaM datasets Data entry / RDC SDTM mapping PRO specific derivations Analysis specific derivations Statistical analysis

Summary PRO data SDTM QS: Original responses in decode format SUPPQS may contain the original numeric responses  Source data (Data in, data out)  No complex derivations BADQ: Intermediate ADaM dataset BDS structure Provides complete PRO data for any further use ADaM: "Classic" analysis-ready datasets Use BADQ as source dataset

20 Questions?