Why eCTD & CDISC? GSG-US, Inc. Chaeyong Chang March, 2012.

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.
OpenCDISC Rules for Discussion
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
Quick tour of CDISC’s ADaM standard
Kendle Implementation of Clinical Data Acquisition Standards Harmonization Dr Elke Sennewald Kendle 9th German CDISC User Group Meeting Berlin, 28 September.
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.
Finalized FDA Requirements for Standardized Data
Study Data Standardization Plan Kick0ff Meeting 23 July 2014.
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 1 PhUSE 2010 Berlin * Accessing the metadata from the define.xml using XSLT transformations.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Copyright © 2010, SAS Institute Inc. All rights reserved. Define.xml - Tips and Techniques for Creating CRT - DDS Julie Maddox Mark Lambrecht SAS Institute.
Monika Kawohl Statistical Programming Accovion GmbH Tutorial: define.xml.
Updates on CDISC Standards Validation
CDISC and how Stata can help us implement it
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.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
Dominic, age 8, living with epilepsy SDTM Implementation Guide : Clear as Mud Strategies for Developing Consistent Company Standards PhUSE 2011 – CD02.
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,
Contents Integrating clinical trial data Working with CROs
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 2 Octagon Research Solutions, Inc. Leading the Electronic Transformation of Clinical R&D ©
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
1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion:
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.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
© Copyright 2008 ADaM Validation and Integrity Checks Wednesday 12 th October 2011 Louise Cross ICON Clinical Research, Marlow, UK.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
CONFIDENTIAL The Ultimate Integration Challenge Jennifer Chin, Covance Hester Schoeman, Covance PhUSE Conference Berlin 2010 Paper DH06.
RCRIM Projects: Protocol Representation and CDISC Message(s) January 2007.
SAS Programmer in Teva Pharmaceuticals Job Description The basic responsibilities are to provide SAS programming support in deriving analysis datasets,
Implementation of CDISC Standards at Nycomed PhUSE, Basel (19-21 October 2009) Nycomed GmbH, Dr. B Traub CDISC Implementation at Nycomed.
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.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
CDISC User Group in Deutschland/Japan Hajime Shimizu (nickname: Akiba) CDISC Japan User Group introduction to team activity.
Updates on CDISC Activities
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.
Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism CDISC (CDASH/SDTM) integration into OC/RDC Peter Van Reusel.
Most Common Issues in Define.xml files
CDISC submission standard
A need for prescriptive define.xml
Dave Iberson-Hurst CDISC VP Technical Strategy
Monika Kawohl Statistical Programming Accovion GmbH
Facilitating Data Integration For Regulatory Submissions
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Updates on CDISC Standards Validation
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
by M.Fournier Groupe Utilisateurs Francophones du CDISC – 08/02/05
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?
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
Quality Control of SDTM Domain Mappings from Electronic Case Report Forms Noga Meiry Lewin, MS Senior SAS Programmer The Emmes Corporation Target: 38th.
Freundschaft Konferenz
In-Depth Report from Optimizing Data Standards Working Group
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
SDTM and ADaM Implementation FAQ
Data Submissions Douglas Warfield, Ph.D. Technical Lead, eData Team
PhilaSUG Spring Meeting June 05, 2019
Presentation transcript:

Why eCTD & CDISC? GSG-US, Inc. Chaeyong Chang March, 2012

FDA approved Prilosec OTC on June 20, 2003.

eCTDHybrideNDA

SDTMADaM Clinical Reports

Datasets Analyses Programs Define.xml adsl.xpt adae.xpt … Tabulations Define.xml dm.xpt ae.xpt … ADaM data include the primary efficacy analyses SDTM data mirror the observed data Module 5 Study Name

Mapping SPEC

FDA can accept data in the SAS XPORT Transport Format (Open Format) that is processed by the XPORT engine in Version 6 of SAS software and later, and by PROC XCOPY in Version 5.

SAS XPT

An annotated case report form (CRF) is a blank CRF with annotations that document the location of the data with the corresponding names of the datasets and the names of those variables included in the submitted datasets.

Annotated CRF

Definition : The data definition file describes the format and content of the submitted datasets. (SDTM & ADaM) Specifications : The specification for the data definitions for datasets provided using the CDISC SDTM IG or SEND IG is included in the Case Report Tabulation Data Definition Specification (define.xml) developed by the CDISC define.xml Team. The latest release of the define.xml is available from the CDISC web site ( FDA can accept definition file in XML or PDF format.

define.xml

1. AEACN : Action Taken with Study Treatment (Expected variable) DOSE INCREASED DOSE NOT CHANGED DOSE REDUCED DRUG INTERRUPTED DRUG WITHDRAWN NOT APPLIABLE UNKNOWN 2. AEOUT: Outcome of Event (Permissible variable) FATAL NOT RECOVERED/NOT RESOLVED RECOVERED/RESOLVED RECOVERED/RESOLVED WITH SEQUELAE RECOVERING/RESOLVING UNKNOWN

3. LBTESTCD : Laboratory Test Code (Required variable) BILI : Bilirubin; Total Bilirubin AST : Aspartate Aminotransferase;SGOT ALT : Alanine Aminotransferase;SGPT GGT : Gamma Glutamyl Transferase HIV1AB : HIV-1 Antibody HIV12AB : HIV-1/2 Antibody HIV2AB : HIV-2 Antibody T3 : Triiodothyronine;Total T3 T4 : Thyroxine;Total T4 4. EGTESTCD : ECG Test Code (Required variable) QTCB : QTcB - Bazett's Correction Formula QTCF : QTcF- Fridericia's Correction Formula VRMEAN : Summary (Mean) Ventricular Rate QTMAX : Summary (Max) QT Duration

5. CMDOSFRQ : Dosing Frequency per Interval(Permissible variable) BID : BD,Twice per day BIS : Twice per week QM : Every Month PRN : As needed Q10H : Every 10 hours QID : 4 times per day QS : Every week QD : Daily

LBORRES : Result of Finding in Original Units (Expected Variable) LBORRESU : Original Units (Expected Variable) LBSTRESC : Character Results/Finding in Std. Format (Expected Variable) LBSTREN : Numeric Result/Findings in Std. Format (Expected Variable) LBSTRESU : Standard Units (Expected Variable) Units used for reporting Platelets count in 97 different local laboratories. (LBORRESU) /MM3 10E6/ML /UL 10E9/L 10E3/CL CELLS/MM3 10E3/MCL G/L 10E3/MM3 ( 아산 )GIGA/L 10E3/MMC MM3/10E3 10E3/UL ( 네오딘 )XMMC S.I. Unit : 10^9/L

FDA’s Enterprise Program to improve management of structured scientific data ­Clinical study data ­Nonclinical study data ­Pharmacogenomic (and other –omic) data ­Product quality and manufacturing data ­Post-market surveillance data What is Janus?

Severity Levels in Janus Validation Criteria Severity Levels in Janus Validation Criteria Severity Description High The error is serious and will prevent the study data from being loaded successfully into the Janus repository. The SDTM study will not be loaded into the Janus repository Medium The error may impact the reviewability of the submission, but will not have an impact on loading the study data into the Janus repository. The SDTM study will be loaded into the Janus repository Low The error may or may not impact the reviewability or the integrity of the submission but will not have an impact on loading the study data into the Janus repository. The SDTM study will be loaded into the Janus repository

Janus Validation Criteria Define.xml that fails the structural validation check or check for controlled vocabularies1 Missing mandatory domains—mandatory domains for Janus include DM (demographics), EX (exposures), and DS (disposition) Missing mandatory fields in either the mandatory domains or optional domains provided in the submission Date fields in the submission (all domains) are not compliant with the SDTM specification Domain-specific errors as described in the detailed specifications described below.

Detailed SDTM Validation Criteria

Example of Validation Results

Rule IDMessageDescription of RuleDomainCategoryTypeWebSDM ID CT0004 Value for AGEU not found in AGEU controlled terminology codelist Variable values should be populated with terms found in 'Age Unit' (C66781) CDISC controlled terminology codelistDMTerminologyErrorR5062 SD0083Duplicate USUBJID The value of Unique Subject Identifier (USUBJID) variable must be unique for each subject across all trials in the submission.DMConsistencyError SD0084Negative AGE value The value of Age (AGE) cannot be less than 0.DMLimitErrorR5006 SD1002 Start date must be before end date Subject Reference Start Date/Time (RFSTDTC) must be less than or equal to Subject Reference End Date/Time (RFENDTC).DMLimitError SD1020Missing DM dataset Demographics (DM) dataset should be included in every submission.DMPresenceError

Example of Validation Results Rule IDMessageDescription of RuleDomainCategoryTypeWebSDM ID SD0006 No baseline result in [Domain] for subject All subjects should have at least one baseline observation (--BLFL = 'Y') in EG, LB, QS, and VS domains, except for subjects who failed screening (ARMCD = 'SCRNFAIL') or were not fully assigned to an Arm (ARMCD = 'NOTASSGN'). EG, LB, QS, VSPresenceWarningIR5005 SD0007 Inconsistent value for Standard Unit Identifies Short Name of Measurement, Test or Examination values where standard units value (Standard Units) is not consistent across all records EG, LB, QS, VSConsistencyErrorIR5006 SD0080 AE start date must be less than or equal to latest disposition date Start Date/Time of Adverse Event (AESTDTC) must be less than or equal to the Start Date/Time of the latest Disposition Event (DSSTDTC)AEConsistencyWarningIR5517 SD0081 Observation date must be less than or equal to latest disposition date Date/Time of Collection (--DTC) must be less than or equal to the Start Date/Time of the latest Disposition Event (DSSTDTC)EG, LB, VSConsistencyWarningIR5517 SD0002 Null value in variable marked as Required Required variables (where Core attribute is 'Req') cannot be null for any record.AllPresenceErrorIR5001

FDA request eCTD (CDISC) as a Submission -We don’t have another option!!! It is desired that taking a charge of SDTM conversion process by DM team is better than SAS Programming team according to our experience. - Prevent chance of manipulating raw data - Require to prevent SAS programmer’s own idea It is desired that applying CDISC at early stage of project - Lower Cost / Time - Increase SDTM Data Quality Janus is under developing

Global STATISTICS Group, Inc. 미주 최초의 한국인 CRO Website: Contact: Phone: : ( 한국 ) (USA) 감사합니다