Update on SDTMIG v. 3.1.2 and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.

Slides:



Advertisements
Similar presentations
FDA CDER Common Data Standards Issues
Advertisements

Monika Kawohl Principal Statistical Programmer Accovion
Principal Statistical Programmer Accovion GmbH, Marburg, Germany
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
What’s New with CDISC Wayne R. Kubick CDISC CTO.
The Importance of CDASH
SEND Standard for the Exchange of Nonclinical Data
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
CDISC (CDASH/SDTM) integration into OC/RDC
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.
WUSS 2009 CDISC for the Medical Device and Diagnostic Industry: An Update Carey Smoak Team Leader CDISC Device SDTM Sub-team.
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.
Updates on CDISC Standards Validation
SDTM Validation Rules Sub-team Kickoff Meeting January 24 th, 2014.
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
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.
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
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.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
HL7 RCRIM Meeting: 9 January 2007 CDISC-RCRIM Vocab Update: Related CDISC Terminology Projects Bron Kisler, CDISC Terminology Program Director
1 RCRIM Vocab-BRIDG Session Wednesday, Session Q2 19 September 2007.
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.
How to go from an SDTM Finding Domain to an ADaM-Compliant Basic Data Structure Analysis Dataset: An Example Qian Wang, MSD, Brussels, Belgium Carl Herremans,
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.
RCRIM Projects: Protocol Representation and CDISC Message(s) January 2007.
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
WG4: Data Guide/Data Description Work Group Meeting August 29, 2012.
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
CDISC©2009 February CDISC INTRAchange Carey Smoak Device Team Leader Li Zheng Submission Data Standards Team Member Thurday, April 2, 2009.
SDTM - Tips and Tricks Oncology Domains
Updates on CDISC Activities
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
1. © CDISC 2014 Stetson Line, Team Lead CDISC Intrachange SDTM Rules Sub-team Update.
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.
CDISC SDS Oncology Domains: An Orientation to Aid Review & Feedback Barrie Nelson CDISC SDS Oncology Sub Team Lead
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
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
CDISC submission standard
A need for prescriptive define.xml
Data Standards for Pharmacometric Analysis Data Sets
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
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
SDTM and ADaM Implementation FAQ
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
SDTMs in Medical Devices A First Attempt
To change this title, go to Notes Master
WG4: Data Guide/Data Description Work Group Meeting
PhUSE: Pooling WHODrug B3 Format
Presentation transcript:

Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions

SDTMIG Comment Statistics Total - >950 Fix Check Assign - 64 Defer - 22 Discuss No action required No action suggested - 13 ADaM - 22 (many duplicates) Duplicates - 57

Outline Comment Statistics Findings Issues/Actions “Findings About” SUPPQUAL Comments Other SDS Team Work SEND FDA Issues –Resolved –Proposals Ready –Not in Scope –Needing Clarification Other SDTM-Based Standards Work Harmonization Work The Future

SDTM Comment Statistics Total - 88 Fix 44 Check - 5 NA - 9 Discuss - 23 Duplicate - 7

Findings Team Actions (1) 1.Standardization of character values in --ORRES to numeric in -- STRESC. QS examples retained. New LB examples inconsistent with data-flow diagram removed. 2.Population of --ORRES for derived records, wording to state that it generally should not be. 3.--BLFL for more than one record per test, dependent upon other keys (e.g., position), clarified. 4.Other sets of results and units for lab tests (standard or conventional), deferred 5.Compound test codes (test details). Decision to remove concatenation example to discourage “lumping.” Address via value-level metadata with CRT-DDS and Metadata Team. 6.Numeric variable for original results such as lab data, not implemented.

Findings Team Actions (2) 7.Length of time in a position for a Finding, under development. 8.Decreasing the emphasis on the use of RELREC for PC and PP, adding that relationship data, which is often part of the analysis metadata, does not need to be brought into the SDTM. 9.Algorithm for scoring questionnaire data

Clinical Findings (“Findings About”) Team 1.Discussion of Findings about and Event (FE) and Findings about an Intervention (FI) 2.More Examples of when to use FI and FE versus a custom Findings domain

SUPPQUAL-Related Comments 1.Value-level metadata (e.g., Origin) in SUPP--; add QTYPE to SUPPQUAL since other value-level metadata are there; numeric QVAL variable (value-level metadata), deferred. 2.Requirements for use of SUPPQUAL variables in Appendix C5, note to be added. 3.Use of domain prefixes for QNAM values, not required. 4.Examples for using SUPPQUAL variables in IDVAR for RELREC, deferred. 5.Proposal to allow relationships to be identified with multiple keys (multiple IDVAR and/or IDVARVAL) values, under discussion. 6.Deprecation of QORIG, deferred.

Other SDS Team Work 1.Revision of Appendix C2 (Domain Codes) and guidance of assigning codes for custom (sponsor-created) domains. 2.Specifying 20-character limit for ARMCD (no limit cited previously), and 200 for ARM. 3.Removal of SDTM general-observation-class tables from SDTMIG. 4.Dataset-naming and domain-code proposals to be reviewed within SDS Team 5.Change Log creation

SEND 1.“Rebaselining” - Alignment with SDTM and other CDISC standards 2.Adding new variables to SDTM for SEND (Exclusion Flag, Reason for Exclusion, Species, Strain, Substrain, AGETXT, POOLID. 3.Addition of new SEND Domains 4.Pilot Project 5.Reproductive Toxicology

Issues for Discussion with FDA: Resolved 4.Dictionary Version 6.Promotion of SUPPQUAL Variables 7.Test Details 8.Variable Order 12.Permissible vs. Required 14.No Imputed Data

Issues for Discussion with FDA: Proposals Ready (1) 1.Day in Period/Phase/Cycle 2.Baseline Flags Algorithm for selecting baseline observation Baselines for multiple treatment periods Baselines for multiple tests with the same TESTCD value 3.Population Flags 5.MedDRA Secondary Organ Class 9.Submission of Null Values for Y/N Questions

10.Exposure Records a. Placebo Dose b. Doses Not Given c. Creation and requiredness of EX 11.Multiple Qualifier Values 16.Discourage Custom Domains 18.No duplication of data (need clarification) 20.Difficulty associating findings with the most recent experimental intervention or a concomitant intervention (related to 24; TD requirements) Issues for Discussion with FDA: Proposals Ready (2)

24.ARM and ARMCD Not helpful in Crossover Studies (related to 20; TD requirements) 28.CT for AEREL (Y, N vs. Possible, Probable, etc.) 29.Expectations for use of CT in Submissions (lists of CT are not tied to SDTM versions). Versions of CT are different from versions of SDTMIG. Subset discussion included? Does FDA access published list? 30.Questionnaire Scores 32.CRF Annotation and Bookmarking Preferences Issues for Discussion with FDA: Proposals Ready (3)

33.Referencing ECG Waveforms 34.Size of Datasets 35.MedDRA and WHO Drug numeric codes in addition to text values -add defined variables? Issues for Discussion with FDA: Proposals Ready (4)

13.Relationships between Source Data 17.All verbatim terms need a corresponding coded value 19.Lack of Adherence 21.Lack of a clear and consistent method to capture concomitant interventions, 22.Lack of a clear and consistent method to capture device characteristics 25.Missing or Incomplete Values for Date and Time Records (similar precision for dates that might be subtracted) (from Intrachange) (Education issue) 26.Death Information (from Intrachange) 27.Not Measurable Versus Not Done (from Intrachange) Issues for Discussion with FDA: Not in Scope for 3.1.2

15.Include Derived Data 17.“Regional Requirements” for Variables Issues for Discussion with FDA: Needing Clarification

Other SDTM-Based Standards Work Oncology Subteam of the SDS Team –Oncology domains (Tumor Identification and Tumor Measurements) Devices Team –Device Properties domain Other Teams –Cardiology and TB standards

Harmonization Efforts BRIDG (Biomedical Research Integrated Domain Group) CDASH (Clinical Data and Acquisition Standards Harmonization) Controlled Terminology ADaM (Analysis Data Model) SEND (Standard for the Exchange of Nonclinical Data)

Beyond Change data type for STNRHI and STNRLO to character to allow for “ ”, since --STRNRC might not be used for a range, but for only for one of the limits Multiple Date for a single Event (e.g., start date, diagnosis date, most recent episode) More direction and harmonization on anatomical locations (right, left; dorsal, ventral; anterior, posterior; lateral, medial; proximal, distal; liver lobe, kidney region). Publishing in a better electronic format Addition of new Intervention variables for Concentration, Concentration Units, and Dose Form Amount. Addition of --SSCAT Deprecation of TI

New Domains in Deviations (DV) Drug Accountability (DA) Pharmacokinetics (PC & PP) Pharmacogenomics (PG) Microbiology (MB and MS) Clinical Findings (Findings About Events, Findings About Interventions) Clinical Events