1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec 2014 2.

Slides:



Advertisements
Similar presentations
Monika Kawohl Principal Statistical Programmer Accovion
Advertisements

Principal Statistical Programmer Accovion GmbH, Marburg, Germany
ADaM Implementation Guide: It’s Almost Here. Are You Ready?
United Nations Statistics Division
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
What’s New with CDISC Wayne R. Kubick CDISC CTO.
SEND Standard for the Exchange of Nonclinical Data
Metadata Management – Our Journey Thus Far
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.
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
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.
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.
Dominic, age 8, living with epilepsy SDTM Implementation Guide : Clear as Mud Strategies for Developing Consistent Company Standards PhUSE 2011 – CD02.
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:
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.
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.
How to improve quality control in a data conversion process? By extended usage of metadata! Dimitri Kutsenko Entimo AG - Berlin/Germany.
CDISC©2009 February CDISC INTRAchange Carey Smoak Device Team Leader Li Zheng Submission Data Standards Team Member Thurday, April 2, 2009.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
SDTM - Tips and Tricks Oncology Domains
© 2010 PAREXEL International | Confidential An Introduction to SDTM Laurent Marais Sorcery and other approaches An Introduction to SDTM.
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.
Copyright © 2014, SAS Institute Inc. All rights reserved. SAS® TOOLS FOR WORKING WITH DATASET-XML FILES Lex Jansen Principal Software SAS CDISC.
ICON CD04 - Ensuring Compliant and Consistent Data Mappings for SDTM-based Studies – an ICON Approach Jennie Mc Guirk 11 th October 2011.
Updates on CDISC Activities
Defining & Managing Data Elements and Permissible Values or CDISC Terminology - A Use Case BACUN Barrie Nelson.
1. © CDISC 2014 Stetson Line, Team Lead CDISC Intrachange SDTM Rules Sub-team Update.
DIA Electronic Submissions Meeting Olga Alfieri 26 April 2016
© 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
Mark Wheeldon, Formedix CDISC UK Network June 7, 2016 PRACTICAL IMPLEMENTATION OF DEFINE.XML.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
The use of LOINC in CDISC Standards German CDISC Users Meeting Stuttgart Jozef Aerts XML4Pharma.
Practical Considerations for Data Validation
Paul Houston CDISC Europe Foundation Head of European Operations
A need for prescriptive define.xml
Summary Report Project Name: Model-Driven Health Tools (MDHT)
Validation of CDISC data sets, current practice and future
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Updates on CDISC Standards Validation
The use of LOINC in CDISC Standards
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.
MAKE SDTM EASIER START WITH CDASH !
Traceability between SDTM and ADaM converted analysis datasets
WORKSHOP GROUP ON QUALITY IN STATISTICS
SDTM and ADaM Implementation FAQ
Practical Considerations for Data Validation
CDISC UK Network Jun-16 – Welwyn
A SAS macro to check SDTM domains against controlled terminology
Fabienne NOEL CDISC – 2013, December 18th
WG4: Data Guide/Data Description Work Group Meeting
SDTM and ADaM Implementation FAQ
Nonclinical SDRG Goals of the project Project status: Ambition:
PhUSE: Pooling WHODrug B3 Format
Presentation transcript:

1

© CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec

© CDISC 2014 SDS ELT Nov Discussion Decisions from last meeting SDTM 1.4 / SDTMIG 3.2 Rules Publication  Supplement (Excel)  Target Date by EOQ Rules Development Guide  Target Date for Internal Review by Jan 2015  Independent of rules publication SDTM 1.5 / SDTMIG 3.3 Rules  Target Date – Summer

© CDISC 2014 FDA SDTM Rules vs. SDS SDTM Rules FDA published 315 rules 11/18  Based on OpenCDISC Validator 1.x with updates New TS domain rules CT rules simplification Deprecated concept of ‘Notice’ type rules Versioned for SDTMIG  Approved and maintained by FDA Change Control Board (CCB) Pinnacle 21/OpenCDISC implement these in Validator 2.0  Publisher ID column used to reference FDA Rule ID FDA CCB to evaluate SDS SDTMIG v3.2 Rules (Q1 2015) 4

© CDISC 2014 FDA SDTM Rules vs. SDS SDTM Rules There are gaps/overlaps between FDA/SDS SDTM rules  Similar rules with differences in scope  Conflicts / differences in interpretation  FDA intends regular (semi-annual) updates asynchronous to SDS updates  FDA rules parameterized without benefit of parameter datasets Apparent ties to Pinnacle 21 OpenCDISC implementation 5

© CDISC 2014 Sample FDA CT Rules 6 FDA Rule ID MESSAGEDESCRIPTIONDOMAINSSEVERITY (3.1.2 A1) FDAC340Value for not found in ( ) CT codelist ( ) variable values should be populated with terms found in ' ' ( ) CDISC controlled terminology codelist. New values cannot be added into the CDISC CT non-extensible codelist. ALLErrorXX FDAC341Value for not found in ( ) CT codelist ( ) variable values should be populated with terms found in ' ' ( ) CDISC controlled terminology codelist. New terms can be added as long as they are not duplicates, synonyms or subsets of existing standard terms. ALLWarningXX FDAC343Value for not found in ( ) CT codelist ( ) variable values must be populated with terms found in ' ' ( ) CDISC controlled terminology codelist, when ( ) ' '. New values cannot be added into the CDISC CT non-extensible codelist. ALLErrorXX FDAC344Value for not found in ( ) CT codelist ( ) variable values must be populated with terms found in ' ' ( ) CDISC controlled terminology codelist, when ( ) ' '. New terms can be added as long as they are not duplicates, synonyms or subsets of existing standard terms. ALLWarningXX

© CDISC 2014 SDS Sub-Team Proposed CT Rules Rule IDRuleConditionItem #TextClassDomainVariable ALL_ALL_GEN_05Value in assigned controlled terms or 'MULTIPLE' Assigned non- extensible controlled terms 3.2Conformance with the SDTMIG Domain Models is minimally indicated by following SDTM-specified controlled terminology and format guidelines for variables, when provided ALL GENERAL ALL_ALL_GEN_06Value in assigned controlled terms or in ('MULTIPLE','OTHER') Assigned extensible controlled terms 3.2Conformance with the SDTMIG Domain Models is minimally indicated by following SDTM-specified controlled terminology and format guidelines for variables, when provided ALL GENERAL 7

© CDISC 2014 Questions for SDS ELT Should we be concerned about referencing or with harmonizing SDS rules with FDA rules sets?  Option – reference FDA Rule ID as additional metadata? What about rules not approved by FDA CCB or un-implementable? (How will they be viewed by industry?) What is our purview when compliance rules are wrong or misstated?  Feedback  Would it be advisable for CDISC to have representation on the FDA CCB? 8