FDA CDER Common Data Standards Issues

Slides:



Advertisements
Similar presentations
Monika Kawohl Principal Statistical Programmer Accovion
Advertisements

Dimitri Kutsenko (Entimo AG)
CDISC based eSubmission Key Points of the CDISC SDTM/ADaM Pilot
Principal Statistical Programmer Accovion GmbH, Marburg, Germany
ADaM Implementation Guide: It’s Almost Here. Are You Ready?
FDA/Industry Statistics Workshop - 29 September 2006
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Agenda CDISC and Regulatory Submission Landscape
OpenCDISC Rules for Discussion
UC5:Assigning of Epoch after treatment discontinuation (NS)
Update on CDISC Terminology Activities RCRIM Vocab Session (Q4) 14 January 2009, Orlando Bron Kisler (CDISC)
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
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.
CDISC (CDASH/SDTM) integration into OC/RDC
CONFIDENTIAL Integration of SDTM File Creation into Study Analysis: A Practical Approach Anna Kunina, Edzel Cabanero, Efim Dynin, Lindley Frahm 04Apr2008.
Finalized FDA Requirements for Standardized Data
Life Sciences Accelerated R&D Services The Science of Getting Products to Patients Faster Study Data Standardization Plan Use Case Experience Dave Izard.
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
Requirements for Standardized Study Data: Update on Guidance Ron Fitzmartin, PhD, MBA Data Standards Program Office of Strategic Programs Center for Drug.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Monika Kawohl Statistical Programming Accovion GmbH Tutorial: define.xml.
CDISC and how Stata can help us implement it
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
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,
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,
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.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
15th Informal US MedDRA User Group Meeting, October 28, 2011 Slide 1 Double the Impact with Half the Work: Linking MedDRA and WHO Drug Indication coding.
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.
Optimizing Data Standards Working Group Meeting Summary
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
Penny Pang, Novartis. 2 About OpenCDISC 3  An open source community focused on building extensible frameworks and tools for the implementation and advancement.
CDISC – 17/12/2012 Carine Javierre Nathalie SABIN.
German Speaking CDISC UG, 22-Sep CDER Common Data Standards Issues Document Motivation CDISC submissions received varied more than expected Contents.
Why eCTD & CDISC? GSG-US, Inc. Chaeyong Chang March, 2012.
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
Dave Iberson-Hurst CDISC VP Technical Strategy
Monika Kawohl Statistical Programming Accovion GmbH
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
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.
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.
Traceability between SDTM and ADaM converted analysis datasets
Patterns emerging from chaos
CDISC UK Network Jun-16 – Welwyn
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
SDTMs in Medical Devices A First Attempt
SDTM and ADaM Implementation FAQ
PhilaSUG Spring Meeting June 05, 2019
Presentation transcript:

FDA CDER Common Data Standards Issues Evolution of SDTM Submission Standards Tina Apers CRO Manager Business & Decision Life Sciences Tel +32 2 774 11 00 Fax +32 2 774 11 99 Mobile +32 476 54 59 17 peter.vanreusel@businessdecision.com Sint-Lambertusstraat 141 Rue Saint-Lambert 1200 Brussels www.businessdecision-lifesciences.com 1

CDER Common Data Standards Issues 1 Introduction 2 CDER Common Data Standards Issues 3 Amendment 1 to the SDTMIG 4 Impact

CDER Common Data Standards Issues 1 Introduction 2 CDER Common Data Standards Issues 3 Amendment 1 to the SDTMIG 4 Impact

Introduction 06-May-2011: CDER published Common Data Standards Issues Document on the FDA website Document will be updated periodically Source: http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements/ElectronicSubmissions/ucm248635.htm

Source: http://www.cdisc.org/sdtm Introduction Amendment 1 to the SDTM V1.2 and SDTMIG V3.1.2 has been posted on the CDISC website Public review period ended on 06-June-2011 Source: http://www.cdisc.org/sdtm

CDER Common Data Standards Issues 1 Introduction 2 CDER Common Data Standards Issues 3 Amendment 1 to the SDTMIG 4 Impact

General Considerations Sponsors should refer to the latest version of SDTMIG Sponsors should refer to Amendment 1 to SDTM V1.2 Sponsors should ensure that every data variable’s codelist, origin and derivation is clearly and easily accessible in define file Include variables EPOCH, ELEMENT, and ETCD for every subject-level observation SDTM should be consistent with submitted analysis datasets

Traceability SDTM and ADaM Understanding relationship between the analysis results, the analysis datasets and the SDTM domains Establishing the path between an element and its immediate predecessor Two levels: Metadata traceability Relationship between an analysis result and analysis dataset(s) Relationship of the analysis variable to its source dataset(s) and variable(s) Data point traceability Predecessor record(s)

Traceability SDTM and ADaM

Traceability SDTM and ADaM Analysis Results

Traceability SDTM and ADaM Analysis Dataset

Traceability SDTM and ADaM ADaM define.xml

Traceability SDTM and ADaM and aCRF SDTM define.xml

Controlled Terminology Use existing CDISC terminology If available CDISC terminology is insufficient, sponsors may propose their own terminology Documentation on sponsor-specific terminology should be included in define.xml Source: http://www.cancer.gov/cancertopics/cancerlibrary/terminologyresources/cdisc

MedDRA and Common Dictionaries Sponsors should exactly follow spelling and case MedDRA version should be consistent across trials within the submission Dictionary name and version should be documented in define.xml

SDTM Datasets SUPPQUAL DM DS Should not be used as a waste basket Strongly preferred to use additional variables in Amendment 1 Section 2.1, Pages 6-7 DS EPOCH should be used to distinguish between multiple disposition events If DEATH occurs, it should be documented in the last record with the associated EPOCH

SDTM Datasets AE Custom Domains LB Provide variables for MedDRA hierarchy (Amendment 1 Section 2.2, Pages 8-9) Sponsors should include all AEs, not only the one caused by the study treatment AESOC = MedDRA-defined, primary mapped SOC AEBODSYS = SOC used for analysis Custom Domains Only to be used for data that does not fit in a published domain LB Ideal filesize < 400 megabytes Larger files should be split according to LBCAT, LBSCAT; Non-split dataset should also be included Discuss with your review division

SDTM Variables Permissible variables that CDER expects to see --BLFL (LB, VS, EG, Pharmacokinetics, Microbiology) EPOCH --DY and --STDY in SE and Findings Dates in ISO 8601 Missing dates are missing dates USUBJID No leading or trailing spaces allowed should match across all datasets (SDTM, ADaM) on a character basis No imputations allowed

CDER Common Data Standards Issues 1 Introduction 2 CDER Common Data Standards Issues 3 Amendment 1 to the SDTMIG 4 Impact

Additions to SDTM V1.2/SDTMIG V3.1.2 New variables in Demographics New variables in Events General Observation Class Additional accomodation for MedDRA codings Part of these previously used in SUPPQUAL

Additions to DM Variable Label ACTARMCD Actual Arm Code ACTARM Description of Actual Arm RFXSTDTC Date/Time of First Study Drug Exposure RFXENDTC Date/Time of Last Study Drug Exposure RFPSTDTC Date/Time of First Subject Contact RFPENDTC Date/Time of End of Subject Participation DTHDTC Date of Death DTHFL Subject Died Flag

Additions to DM ACTARMCD, ACTARM RFXSTDTC, RFXENDTC RFPSTDTC Actual arm a subject participated in during the trial Randomized subjects that are not treated ACTARMCD/ACTARM= ’NOTTRT ’/ ’Not Treated’ RFXSTDTC, RFXENDTC Date/Time of first/last study treatment exposure RFXSTDTC should match SESTDTC for first treatment element RFXENDTC should match SEENDTC for last treatment element RFPSTDTC Date/Time of informed consent Should match entry in DS if this is documented as a protocol milestone

Additions to DM RFPENDTC DTHDTC, DTHFL Date/Time of end of participation Last known date of participation FOR DATA NOT the last date of participation in study DTHDTC, DTHFL Date of death, Subject death flag

Additions to AE Variable Label AETRTEM Treatment Emergent Flag AELLT Lowest Level Term AELLTCD Lowest Level Term Code AEPTCD Preferred Term Code AEHLT High Level Term AEHLTCD High Level Term Code AEHLGT High Level Group Term AEHLGTCD High Level Group Term Code AESOC Primary System Organ Class AESOCCD System Organ Class Code AEBDSYCD

Additions to AE AETRTEM Treatment emergent flag: ‘Y’ or null Derivation must be clearly documented in define.xml AELLT, AELLTCD, AEPTCD, AEHLT, AEHLTCD, AEHLGT, AEHLGTCD, AESOCCD Promoted from SUPPQUAL (SDTMIG Appendix C5) into the parent domain AESOC Primary system organ class AEBODSYS should contain the SOC used in analysis AEBDSYCD Body system code

CDER Common Data Standards Issues 1 Introduction 2 CDER Common Data Standards Issues 3 Amendment 1 to the SDTMIG 4 Impact

Impact Amendment 1 deals with new FDA expectations CDER goes further than Amendment 1 ETCD, ELEMENT, EPOCH are rarely captured on the CRF SDTM derivation could be complex An updated data model together with new/updated check definitions is needed to enable electronic QC

Thank you for your attention Tina Apers CRO Manager Business & Decision Life Sciences Tel +32 2 774 11 00 Fax +32 2 774 11 99 Mobile +32 476 54 59 17 peter.vanreusel@businessdecision.com Sint-Lambertusstraat 141 Rue Saint-Lambert 1200 Brussels www.businessdecision-lifesciences.com 29