SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.

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?
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Participation Requirements for a Patient Representative.
OpenCDISC Rules for Discussion
Data Access Framework (DAF) Technical Work Group March 5 th 2014.
What’s New with CDISC Wayne R. Kubick CDISC CTO.
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
Quick tour of CDISC’s ADaM standard
Draft Operational procedures for registry systems 09 November 2004 Bonn, Germany Technical Breakout Group.
Participation Requirements for a Guideline Panel PGIN Representative.
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.
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
Monika Kawohl Statistical Programming Accovion GmbH Tutorial: define.xml.
Updates on CDISC Standards Validation
CDISC and how Stata can help us implement it
SDTM Validation Rules Sub-team Kickoff Meeting January 24 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.
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.
© 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:
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.
LCC -Proposal for Next Steps August 28, Discussion Points Recap of Whitepaper Recommendations Critical milestones and activities driving LCC activities.
© 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.
Implementation of CDISC Standards at Nycomed PhUSE, Basel (19-21 October 2009) Nycomed GmbH, Dr. B Traub CDISC Implementation at Nycomed.
1  Bob Hager Director of Publishing Standards Metadata Specification.
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
1 SDS&ADaM sub-team 28 January 2004 Mineko FUJIMOTO Rieko ICHIHARA Kazue TOMITA Hiroaki MATSUDA.
CDISC©2009 February CDISC INTRAchange Carey Smoak Device Team Leader Li Zheng Submission Data Standards Team Member Thurday, April 2, 2009.
From PDF to RDF – Representing the CDISC Foundational Standards
WG4: Standards Implementation Issues with CDISC Data Models Team Update: June 18, 2012.
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.
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
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.
© 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
Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism CDISC (CDASH/SDTM) integration into OC/RDC Peter Van Reusel.
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.
Data Standards for Pharmacometric Analysis Data Sets
Monika Kawohl Statistical Programming Accovion GmbH
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Updates on CDISC Standards Validation
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
In-Depth Report from Optimizing Data Standards Working Group
SDTM and ADaM Implementation FAQ
A SAS macro to check SDTM domains against controlled terminology
WG4: Data Guide/Data Description Work Group Meeting
SDTM and ADaM Implementation FAQ
WG4: Standards Implementation Issues with CDISC Data Models
WG5 P02 Proposal 2014 Qualification of Standard Scripts
SDTM and ADaM Implementation FAQ
WG5 P02 Proposal 2014 Qualification of Standard Scripts
Presentation transcript:

SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014

© CDISC 2014 SDTM Rules Sub-Team Introducing the Team Proposed 2014 Deliverables Progress so far… INTRAChange Topics  Rules Sub-Team SOW – ‘Focus and Simplify’  Issues/ Questions 2

© CDISC 2014 Sub-Team Membership (so far) Stetson Line – Amgen Tom Guinter – Independent Janet Reich – Amgen Max Kanevsky – Pinnacle21 Sergiy Sirichenko – Pinnacle21 Scott Bahlavooni – Biogen IDEC Anne Russotto – Celgene Carlos Radovsky – etera solutions Bess LeRoy – Cpath.org Gary Walker – Quintiles Dan DiPremio – BioMarin Sue Sullivan – d-Wise Technologies 3

© CDISC 2014 Proposed Sub-Team Goals Comprehensive SDTM IG v3.2 Validation Rules SDTM Validation Rule Implementation Guide (Documents rule metadata and usage to enable SDS sub- teams to publish standard validation rules as part of future IGs). 4

© CDISC 2014 Draft 2014 Sub-Team Milestones Q  Sub-team Kickoff /Member orientation/ assignments  SDTM IG v3.2 – DM Validation Rules Draft Q  SDTM IG v3.2 – Events/ Interventions Domains Validation Rules Draft  SDTM Validation Rules IG Draft  Check-in with SDS LT/ Share Team Q  SDTM IG v3.2 – Findings Domains Validation Rules Draft  SDTM IG v3.2 – Findings About Domains Validation Rules Draft  SDTM IG v3.2 – Other Special Purpose Domains Validation Rules Draft Q  SDTM IG v3.2 Validation Rules (submitted for public comment)  SDTM Validation Rule Implementation Guide (submitted for public comment) 5

© CDISC 2014 Progress to Date Charter Approved Rules Sub-team Wiki set-up Extraction DM Pilot  Rules template developed  SDTM 1.4/SDTMIG 3.2 DM Rules extracted Analysis ongoing 6

© CDISC 2014 SDTM Validation Rules Wiki Space 7

© CDISC 2014 Rules Template – ‘Metadata Model’ 8

© CDISC 2014 Working Model Pilot – DM Rules Objective: to get many different perspectives and experiences in order to refine the approach for the remaining domains/ observation classes.  Pilot Exercise – DM Domain Using draft rules template extract all text that may indicate DM rules from SDTM 1.4/SDTMIG 3.2 Record all potential interpretations Reconciliation team to harmonize and consolidate Full team review of rule metadata and potential interpretations 9

© CDISC 2014 Rules Team Scope Extract all business logic and data conformance rules? What about data quality?  Is the output expected to be comprehensive or only what is not captured e.g. DDT attributes, structural SDTM compliance? Inferred data quality? Rules metadata model:  English-like, not concerned with rigorous application of CT or rule syntax? More principle than law. VS.  Consistent syntax and CT, but perhaps too granular, lacking readability. More law than principle. Implementable in Share? Do we know? 10

© CDISC 2014 Rules Questions Screen failures - expected to be included or excluded?  Data for screen failure subjects, if submitted, should be included in the Demographics dataset, with ARMCD = “SCRNFAIL" and ARM = “Screen Failure”  Conditional rule? Add parameter to TS? ACTARM, ACTARMCD – implementation in complex trials are problematic, and are values expected to match TRTxxA (ADaM)? Population flags – expected?  Conditional rule? Add parameter to TS? 11

© CDISC 2014 Rules Questions Professional patients, patients shopping sites/arms – multiple DM records? What is the rule? Additional guidance needed.  Multiple records / different SUBJIDs  VS.  One record per patient/USUBJID Map secondary to SUPPDM Where can a variable be used? Class level rules? 12

© CDISC 2014 Rules Questions Managing Duplicate Rules Rules class heirarchies – e.g.  If Core Variable Status = Req then Variable must exist  Vs.  USUBJID must exist, ARM must exist, etc. Overall Guidance Heirarchy  SHARE (Future) SDTM –Class »Domain Can children refine / restrict parent rules? 13