Fabienne NOEL CDISC – 2013, December 18th

Slides:



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

ADaM Implementation Guide: It’s Almost Here. Are You Ready?
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
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
SEND Standard for the Exchange of Nonclinical Data
Change/Insert Date & Location via >Insert >Header & Footer 1. Check in Date & Time 2. Type under >Fixed 3. Check in Footer 4. Fill in field 5. Click Apply.
Standardisation of Trial Design Definitions in CDW at Novo Nordisk
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.
“Compliance” for Analysis Data Chris Decker, Vice-President, Life Sciences Practice, d-Wise Technologies Randall Austin, Manager, Data Standards, GlaxoSmithKline.
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.
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
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,
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
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.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
Dave Iberson-Hurst CDISC VP Technical Strategy
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.
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
Preventing Wide and Heavy ADs Dirk Van Krunckelsven Phuse 2011, Brighton ADaM on a Diet.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
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.
Tracing Data Elements through a Standard Data Flow Alistair Dootson Dootsonic Ltd, Manchester, UK 16 February 2016Copyright Dootsonic Ltd 2011.
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
German Speaking CDISC UG, 22-Sep CDER Common Data Standards Issues Document Motivation CDISC submissions received varied more than expected Contents.
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
© CDISC 2015 Paul Houston CDISC Europe Foundation Head of European Operations 1 CTR 2 Protocol Representation Implementation Model Clinical Trial Registration.
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.
CDISC SDS Oncology Domains: An Orientation to Aid Review & Feedback Barrie Nelson CDISC SDS Oncology Sub Team Lead
ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC Joerg Guettner, Lead Statistical Analyst, Bayer Pharma, Wuppertal,
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
Functions and relations
Paul Houston CDISC Europe Foundation Head of European Operations
A need for prescriptive define.xml
Dave Iberson-Hurst CDISC VP Technical Strategy
Data Standards for Pharmacometric Analysis Data Sets
A Systematic Review of ADaM IG Interpretation
Data and Information.
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
2.2 Defining Classes Part 2 academy.zariba.com.
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
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.
Why use CDISC for trials not submitted to regulators?
MAKE SDTM EASIER START WITH CDASH !
Traceability between SDTM and ADaM converted analysis datasets
Quality Control of SDTM Domain Mappings from Electronic Case Report Forms Noga Meiry Lewin, MS Senior SAS Programmer The Emmes Corporation Target: 38th.
Functions and relations
Patterns emerging from chaos
TRAINING OF FOCAL POINTS on the CountrySTAT SYSTEM based on FENIX
To change this title, go to Notes Master
WG4: Data Guide/Data Description Work Group Meeting
Functions.
Presenters Emily Woolley
TRAINING OF FOCAL POINTS ON THE CountrySTAT/FENIX SYSTEM
Generating Define.xml at Kendle using DefinedocTM
An FDA Statistician’s Perspective on Standardized Data Sets
WG5 P02 Proposal 2014 Qualification of Standard Scripts
Generating Define.xml at Kendle using DefinedocTM
Data Submissions Douglas Warfield, Ph.D. Technical Lead, eData Team
WG5 P02 Proposal 2014 Qualification of Standard Scripts
and Forecasting Resources
Presentation transcript:

Fabienne NOEL CDISC – 2013, December 18th How to CDISC in Sanofi… Fabienne NOEL CDISC – 2013, December 18th

Agenda Previous model Linear model overview Sanofi SDTM Sanofi ADS The futur …

Previous model: from 2009

Why to change ? FDA has stated "Analysis datasets should be derivable from the SDTM datasets, in order to enable traceability from analysis results presented in the study reports back to the original data elements collected in the case report form and represented in the SDTM datasets" The FDA does not receive the "raw" data. Therefore, any derivation documentation or programs/code used to derive ADS variables, or to include SDTM variables in the ADS, can not refer to raw variables. ADS/SDS creation and validation of SDTM after ADS caused problems When SDTM needed to change it was too late to change the ADS (already used for TLGs), so SDTM and ADS were out of sync.

From 2012 Linear Model SDTM domains are created and validated in a first step; and then, in a second step, the ADS domains are created using the SDTM domains. SDTM: variables are mapped using raw (e.g., OC) data when feasible, derived variables (e.g., --DY, --BLFL) use existing SDTM variables in their derivation (not raw data) ADS: may not use any raw data; the source for all variables must be the SDTM datasets (and other variables within the ADS submission). not all variables from the SDTM domains will be retained not all records from the SDTM may be retained and additional records may be added only ADS that are required to support an analysis should be created

From 2012 : Data flow in a Linear Model

A Look at Sanofi SDTM

Sanofi SDTM Standards Based on: SDTMIG version 3.1.2 Amendment 1 to SDTMIG CDER Common Data Standards Issues Document v1.1 CDISC Oncology domains Stricter adherence to CT FDA wishes stated at CDISC Interchange, at CDISC meetings, etc.

Validation of SDTM SDTM must be final and validated prior to use for listing or creation of ADS OpenCDISC Checks fix all avoidable errors document in a reviewers guide all that can’t be avoided Sanofi checks Double programming of key variables - derivations

A Look at Sanofi ADS

What ADS are created? Subject Level (ADSL) is mandatory Any other ADS is not created unless used for an analysis No one to one correspondence between SDTM and ADS

ADS must be "Analysis Ready" ADS should have a structure and content that allow statistical analyses to be performed with minimal programming FDA stopped using the term one-proc-away because it was misleading Analysis-ready does not mean that a formatted table can be generated in a single statistical procedure. Rather it means that each statistic (cell) in the table can be replicated without derivations or merging (with certain exceptions) However, it should not be necessary to have to transpose an ADS to produce a table, figure, or graph The exceptions: it is allowable to perform formatting in the reporting program because formats (e.g., rendering RACE to title case) are not used for calculating the "statistic" and are not considered derivations it is allowable to merge to ADSL in order to be able to determine denominators it is allowable to have the TLG program filter (select records) or sort the data ADS do not need to be analysis ready to produce a listing (i.e., if used to create a listing)

Sanofi ADS Standards Based on: Previous SDTM+ model with a move to linear Added variables/CT based on ADaMIG and review period requests Sanofi specific rules ADS domains defined Naming conventions Derivation definitions

Validation of ADS ADS must be final and validated prior to use for TLG Sanofi checks Check of data against Sanofi variable metadata and controlled terminology (chk_sads_meta.sas) Level of validation to be determined based on Validation matrix

And the planned futur… http://www.youtube.com/watch?v=gCyVdvgVpY8#t=13

Questions F2F Programming Management Meeting