Confidential - Property of Navitas - 2015 Accelerate define.xml using defineReady - Saravanan June 17, 2015.

Slides:



Advertisements
Similar presentations
Dimitri Kutsenko (Entimo AG)
Advertisements

CDISC Open Source and low-cost Solutions
Communicating with Standards Keeping it Simple Pamela Ryley Vertex Pharmaceuticals, Inc. September 29, 2006.
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
Quick tour of CDISC’s ADaM standard
Robust approach to create Define.xml v2.0
Kendle Implementation of Clinical Data Acquisition Standards Harmonization Dr Elke Sennewald Kendle 9th German CDISC User Group Meeting Berlin, 28 September.
Cross Check between Define.xml and blankcrf.pdf
Change/Insert Date & Location via >Insert >Header & Footer 1. Check in Date & Time 2. Type under >Fixed 3. Check in Footer 4. Fill in field 5. Click Apply.
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.
Metadata Management – Our Journey Thus Far
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 1 PhUSE 2010 Berlin * Accessing the metadata from the define.xml using XSLT transformations.
7. German CDISC User Group Meeting Define.xml Generator ODM Validator (define.xml validation) 2010/03/11 Dimitri Kutsenko Marianne Neumann.
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.
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.
WG5 P02 Proposal2014 Qualification of Standard ScriptsStandard Scripts.
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
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.
© Copyright 2008 ADaM Validation and Integrity Checks Wednesday 12 th October 2011 Louise Cross ICON Clinical Research, Marlow, UK.
Copyright © 2011, SAS Institute Inc. All rights reserved. Using the SAS ® Clinical Standards Toolkit 1.4 to work with the CDISC ODM model Lex Jansen SAS.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
MXI Confidential Copyright Material February 11, SAS Clinical Standards Toolkit 2.1 Tutorial Sy Truong, President of MXI.
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 Project on Metadata Extraction, Exploration and Pooling: Challenges and Achievements Ronald Steinhau (Entimo AG - Berlin/Germany)
Overview of CDISC standards and use cases along the E2E data management process Dr. Philippe Verplancke ESUG Marlow, UK 27 May 2009.
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
Copyright © 2015, SAS Institute Inc. All rights reserved. Future Drug Applications with No Tables, Listings and Graphs? PhUSE Annual Conference 2015, Vienna.
CDISC User Group in Deutschland/Japan Hajime Shimizu (nickname: Akiba) CDISC Japan User Group introduction to team activity.
Open GSBPM compliant data processing system in Statistics Estonia (VAIS) 2011 MSIS Conference Maia Ennok Head of Data Warehouse Service Data Processing.
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.
ICON CD04 - Ensuring Compliant and Consistent Data Mappings for SDTM-based Studies – an ICON Approach Jennie Mc Guirk 11 th October 2011.
German Speaking CDISC UG, 22-Sep CDER Common Data Standards Issues Document Motivation CDISC submissions received varied more than expected Contents.
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
With OpenCDISC Validator 1. What is 2 OpenCDISC Validator Open source project Freely Available Commercial-quality Facilitate compliance with CDISC standards.
© 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.
Metadata Driven Clinical Data Integration – Integral to Clinical Analytics April 11, 2016 Kalyan Gopalakrishnan, Priya Shetty Intelent Inc. Sudeep Pattnaik,
Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism CDISC (CDASH/SDTM) integration into OC/RDC Peter Van Reusel.
ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC Joerg Guettner, Lead Statistical Analyst, Bayer Pharma, Wuppertal,
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.
A need for prescriptive define.xml
Dave Iberson-Hurst CDISC VP Technical Strategy
Monika Kawohl Statistical Programming Accovion GmbH
Practical Implementation of Define.xml
7. German CDISC User Group Meeting Define
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.
Definition SpecIfIcatIons
Monika Kawohl Statistical Programming Accovion GmbH
MAKE SDTM EASIER START WITH CDASH !
Traceability between SDTM and ADaM converted analysis datasets
CDISC UK Network Jun-16 – Welwyn
Definition SpecIfIcatIons
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
Monika Kawohl Statistical Programming Accovion GmbH
Generating Define.xml at Kendle using DefinedocTM
WG5 P02 Proposal 2014 Qualification of Standard Scripts
Generating Define.xml at Kendle using DefinedocTM
WG5 P02 Proposal 2014 Qualification of Standard Scripts
PhilaSUG Spring Meeting June 05, 2019
Presentation transcript:

Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015

Confidential - Property of Navitas Agenda Introduction – define.xml Current situation Why defineReady? defineReady Stages Process Flow Key features defineReady - Reports defineReady – Mile stones Questions and Answers

Confidential - Property of Navitas Introduction - Define.XML The FDA reviewer requires a document which navigates through the study data presented in individual dataset. CDISC define.xml is the one such document which describes the structure and content of clinical data in a machine readable format for electronic submissions of CDISC datasets, such as SDTM and ADaM. The define.xml describes metadata in 5 Levels: Table Level Metadata Variable Level Metadata Value Level Metadata Controlled Terminology Computational Algorithm

Confidential - Property of Navitas Current situation Daunting and time consuming job in terms of collecting the CRF pages, handling the Origin, codelists, valuelists and study specific derivations. Requires multiple eyes on each area like metadata repository building, handling sponsor defined data along with standards Also it requires a lot more in-depth understanding in terms of other technologies like XML, Style Sheets, SAS®, interacting with PDF/RTF/XLS and also important to adhere standards of CDISC/FDA.

Confidential - Property of Navitas Current situation (contd…) Receive files from Sponsor Run OpenCDISC for xpt files Convert XPT to SAS datasets Split Dataset if XPT size > 1 GB Create destination in CRF Input sheet preparation Generate Define XML Review Define XML Run OpenCDISC for define XML package Sign-off

Confidential - Property of Navitas Why defineReady? – defineReady is an automated solution that will help generate the define.xml to meet the FDA requirement in a regulated environment with greater accuracy and integrity. – Predefined process with the minimal user interaction. – Ease of use. – No need of technology experts to generate a define.xml.

Confidential - Property of Navitas defineReady Stages The automated process involves three main stages – Setup and Configuration – Build and Generate – Reporting Setup and Configuration Reporting Verification / Review Step BuildGenerate

Confidential - Property of Navitas Process Flow

Confidential - Property of Navitas  Project and Study setup configurations Process Flow (contd..)  Study related files  Submission Configurations Submission Type(SDTM/ADaM) Metadata Version Define XML version External Dictionaries Datasets (XPTs/Dataset) Annotated Blank CRF * Data Guide & Supplemental document * Derivation Document * Codelist files* Study setup Setup and Configuration

Confidential - Property of Navitas Setup and Configuration System will execute the pre-loaded confirmation rules (Level 1 – Metadata Checks) to ensure the submission data meet the standards System will generate the exception report grouped by domain and severity Identifies a column that was described in the domain description but not included in the SAS dataset for that domain Identifies a column where the expected datatype inferred from the description file does not match the actual datatype in the dataset Identifies a column listed in the domain description as Required ('Req') but not included in the SAS dataset for that domain Identifies a column listed in the domain description as Expected ('Exp') but not included in the SAS dataset for that domain Identifies a column that appears in the SAS dataset but is not listed in the domain description Identifies a variable where datatype in (study specific) description is not consistent with datatype implicit in SAS dataset Identifies a variable present in SAS dataset but not present in (study specific) description file Identifies a domain that is referenced in a description file but for which there is no source data Identifies a variable whose description does not match the standard label Identifies a variable that has been deprecated according to the CDISC SDTM standard Identifies a domain for which metadata has not been provided Process Flow (contd..)

Confidential - Property of Navitas Build Study Metadata Domain Metadata Variable Level Metadata Configure Value Level Metadata Configure Codelists Configure Computation methods Configure External Dictionary -- TESTCD -- PARAMCD -- CAT QNAM > Pre-loaded Codelist Code List Name Coded Value Decoded Value Sponsor-Defined Code List Name Coded Value Decoded Value Extended Codelist Code List Name Coded Value Decoded Value Computation Dataset Variable Name Computation Name Computation Method External Codelist Variable Name External Codelist Name Dictionary Version Process Flow (contd..)

Confidential - Property of Navitas Study Specific Derivations Codelists Computation Origin Code list & Decoded values Role Origin Comments GMDCT DDCRF Build Process Flow (contd..)

Confidential - Property of Navitas Build  System will generate the combined metadata information, which user could be extracted in the form of Excel (Input sheet)  Input sheet includes Domain Level Metadata, Variable Level Metadata, Value Level Metadata, Control Terminology, Computational Algorithms and External Codelists Process Flow (contd..)

Confidential - Property of Navitas  The XML generation engine will read the information from Input sheet and generate the define.xml and exception report (Level 2 Report) Generate Process Flow (contd..)  The Level 2 exception report is reviewed by the Analyst and study specific documents are updated. The system will then generate a versioned Input sheet  Also it will generate the Validation report to ensure that the generated XML matches with the standards, in terms of structure and content.  System will generate the define.xml based on the updated/provided inputs

Confidential - Property of Navitas  Final submission package is ready along with the required supporting files  Generating Define.PDF to get a printable version of define.xml  Generate management reports Process Flow (contd..) Reporting

Confidential - Property of Navitas Pre-loaded Global Metadata repository to support all SDTM/ADaM versions. Able to handle the multiple versions of define.xml (various versions of style sheets for the respective submissions of ADaM and SDTM). System will support the sponsor defined code lists along with pre-loaded standard codelist provided by National Cancer Institute. System will auto import the derivation documents and annotated CRFs. System will support CUSTOM domains and SPLITTING of large datasets. Key features

Confidential - Property of Navitas Key features (contd..) System can read the CRF origin from the annotated CRFs and cross check against the origins provided. Provided standards to reference Data guide & Supplemental document Handling pre-loaded standard codelists, Sponsor defined codelists and Extended codelists System will automatically populate the Value level and codelist level information Able to support multiple versions of Input excel and also multiple versions of define xml. System will also help us to generate the printable version of define XML where known as printable PDF

Confidential - Property of Navitas System will generate the reports at each stages to ensure or give the flexibility to the user to make a decision Overview of the reports generated by each stage defineReady - Reports Configure Level 1 Reports Build User Friendly Reports (Domain Level, Variable Level, Value Level and Codelist ) Generate 1. Metadata INPUT EXCELS (Versioned) 2. Level 2 Reports Report Printable PDF

Confidential - Property of Navitas System will also generate the reports which will be used for audit trial purpose and help us to identify the project status Overview of the generated Reports by System Level defineReady – Reports (contd..) Project-wise Study-wise Stage-wise User-Wise

Confidential - Property of Navitas List of features will be added to the defineReady in a near feature, where it will help and support our submission package in an effective manner defineReady – Mile Stones CRF Auto Annotator Reviewer Guide Generator Validation Checks

Confidential - Property of Navitas

Confidential - Property of Navitas Thank You