Metadata Management – Our Journey Thus Far

Slides:



Advertisements
Similar presentations
Dimitri Kutsenko (Entimo AG)
Advertisements

Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Managing and Analyzing Clinical Data
Quick tour of CDISC’s ADaM standard
EDRN’s Validation Study Information Management System Developed for EDRN by the DMCC Cancer Biomarkers Group Division of Cancer Prevention Jet Propulsion.
Copyright © 2013, SAS Institute Inc. All rights reserved. LEVERAGE THE CDISC DATA MODEL TO STREAMLINE ANALYTICAL WORKFLOWS KELCI J. MICLAUS, PH.D. RESEARCH.
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
Standardisation of Trial Design Definitions in CDW at Novo Nordisk
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.
An Approach-Creating Trial Design Models
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
1 Data Strategy Overview Keith Wilson Session 15.
Copyright © 2010, SAS Institute Inc. All rights reserved. Define.xml - Tips and Techniques for Creating CRT - DDS Julie Maddox Mark Lambrecht SAS Institute.
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.
JumpStart the Regulatory Review: Applying the Right Tools at the Right Time to the Right Audience Lilliam Rosario, Ph.D. Director Office of Computational.
Ihr Logo Data Explorer - A data profiling tool. Your Logo Agenda  Introduction  Existing System  Limitations of Existing System  Proposed Solution.
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
Database Design - Lecture 1
Contents Integrating clinical trial data Working with CROs
CDISC Implementation Strategies: Lessons Learned & Future Directions MBC Biostats & Data Management Committee 12 March 2008 Kathleen Greene & A. Brooke.
Vertex and CDISC / MBC / 12March Vertex and CDISC Accomplishments and Strategy 12 March 2008 Lynn Anderson Associate Director Statistical Programming/Biometrics.
Eric Westfall – Indiana University Jeremy Hanson – Iowa State University Building Applications with the KNS.
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
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
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.
11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)
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.
Metadata driven application for data processing – from local toward global solution Rudi Seljak Statistical Office of the Republic of Slovenia.
INFORMATION MANAGEMENT Unit 2 SO 4 Explain the advantages of using a database approach compared to using traditional file processing; Advantages including.
Essential 3a - SSID Enrollment Capabilities and Key Concepts v3.0, August 07, 2012 SSID ENROLLMENT Capabilities and Key Concepts Essential 3a.
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
Practical Image Management for Pharma Experiences and Directions. Use of Open Source Stefan Baumann, Head of Imaging Infrastructure, Novartis.
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
Open GSBPM compliant data processing system in Statistics Estonia (VAIS) 2011 MSIS Conference Maia Ennok Head of Data Warehouse Service Data Processing.
CSS OCTraining 1 Oracle Clinical Overview/Hands-On.
Defining & Managing Data Elements and Permissible Values or CDISC Terminology - A Use Case BACUN Barrie Nelson.
1 Copyright © Oracle Corporation, All rights reserved. Business Intelligence and Data Warehousing.
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.
MindMajix SAS Clinical TrainingSAS Clinical Training.
CDISC SDS Oncology Domains: An Orientation to Aid Review & Feedback Barrie Nelson CDISC SDS Oncology Sub Team Lead
ADaM or SDTM? A Comparison of Pooling Strategies for Integrated Analyses in the Age of CDISC Joerg Guettner, Lead Statistical Analyst, Bayer Pharma, Wuppertal,
A need for prescriptive define.xml
Presented by Jenny Griffiths Data Standards Office, PD Biometrics,
The Development Process of Web Applications
Overview of MDM Site Hub
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Supplier Recovery Claim Automation
Data challenges in the pharmaceutical industry
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
EDRN’s Validation Study Information Management System
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.
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
Patterns emerging from chaos
CDISC UK Network Jun-16 – Welwyn
C.U.SHAH COLLEGE OF ENG. & TECH.
A SAS macro to check SDTM domains against controlled terminology
Fabienne NOEL CDISC – 2013, December 18th
Metadata The metadata contains
Reportnet 3.0 Database Feasibility Study – Approach
Presentation transcript:

Metadata Management – Our Journey Thus Far Archana Bhaskaran Oncology Database Development Operations 28-Jan-2015

Disclaimer The opinions expressed in this presentation and on the following slides are solely those of the presenter and not necessarily those of Novartis. Novartis does not guarantee the accuracy or reliability of the information provided herein.

Evolution of metadata management – Beginning, Current and Future Agenda Introduction Evolution of metadata management – Beginning, Current and Future Key Benefits Achieved and Current Challenges Governance process

Introduction Present a high level overview of Novartis roadmap on metadata management and associated processes from inception to present. What is Metadata? Metadata is information about the data. Metadata describes the domains and data elements used in clinical trials Example of metadata: variable names, type, derivation algorithm, codelists, etc.

MDR Roadmap Novartis has defined an end to end process that governs the framework to define, maintain and use of metadata within a single repository to support all upstream and downstream processes and tools. Beginning: iMDR - Interim MetaData Repository (Excel spreadsheets) Current: MDR - off-the-shelf Oracle based global metadata management tool customized for Novartis Future: MDR – off-the-shelf Oracle based ‘Single Repository’ that enables the management of Global standards and study level Metadata

Metadata Hub Data Warehouse MDR Like a center screw in a wheel Data Collection (CDMS) Data Warehouse MDR Standards Development / Modeling Submission (SDTM, ADaM) Like a center screw in a wheel the Metadata (Standards) in the MDR drives all Implementation programs and data flow (hence process)

Type of metadata maintained Clinical Data Elements (CDE) Controlled Terminology (CT) Derivations and Imputations (DI) Reference Tables (Lab/Non-Lab/Questionnaires) Master Data Domains (MDD) External Partners

Metadata Management – Our Beginning(2009).. iMDR – Interim MetaData Repository Contained only global level metadata with no version control. Metadata was defined and managed in excel spreadsheets for each type of metadata. E.g. CDE, CT, etc. All files were stored and maintained in a central sharepoint location Give a high level overview of maintenance within SP

Metadata Management – Our Beginning (contd) Domain Sheet - Clinical Data Elements Tab Data Elements were defined at Domain level. One spreadsheet for every domain referred as the domain sheet. E.g. AE, CM, etc. The domain sheets contained metadata from collection through submission (SDTM) ADaM metadata was maintained separately in Excel spreadsheets. Each domain sheet contained two main tabs: Clinical Data Elements and Derivations/Imputations. Clinical Data Elements – Contained data elements from collection and submission (SDTM). Each element had 53 attributes that were defined Derivation/imputations – Contained details on the derivations for elements that were derived or imputed. Each derivation had 19 attributes that were defined.

Metadata Management – Our Beginning (contd) Domain Sheet - Clinical Data Elements Tab The Clinical Data Elements Tab

Metadata Management – Our Beginning (contd Metadata Management – Our Beginning (contd.) Domain Sheet – Derivations/Imputations Tab This sheet provides information regarding the derivations and imputations used within the data domain. Derivation: a sequence of steps, logical or computational, from one result to another. The result is a new variable. Example of this method is AGE_DRV - If Date of Birth is present and non- missing then the derived variable will be calculated as Visit Date of Visit 1 minus the Date of Birth.

Metadata Management – Our Beginning (contd Metadata Management – Our Beginning (contd.) Domain Sheet – Derivations/Imputations Tab Imputation: Creating a value when all or part of the original variable is missing. Example of this method is commonly found within dates Data collected Mar1960 Data imputed 15Mar1960

Metadata Management – Our Beginning (contd.) Controlled Terminology Defines the codelist choices that are allowed in a domain for a given CDE. Master controlled terminology was maintained in Excel sheet. Subsets (groups) of codelist values were maintained within CDMS system. This sheet contained 24 attributes for each value defined in a codelist.

Metadata Management – Our Beginning (contd.) QC measures QC checks – SAS based programs to check for the completeness of the domain sheets based on pre- established rules. Manual Review

Metadata Management – Current (2013) Metadata defined and maintained in an off-the-shelf Oracle based tool customized for Novartis. A Central global metadata repository that holds all metadata that is easily accessible to all end users The same concept from iMDR was adapted into the MDR tool. The views were customized to match the iMDR sheets for ease of review and use by end users Following key enhancements were made to the tool: Enabled workflow process for adding and approving new objects User friendly screens for codelist and lab reference tables were added Introduced online validation checks and QC reports Updated interface views for use by downstream systems

Metadata Management – Current Clinical Data Element View Derivations/Imputation View

Key Benefits Achieved Controlled and Audit trailed environment Better quality gained by having on-line checks and built in QC reports Efficiency gained in defining and maintenance of metadata. E.g. Codelist, lab reference tables, etc. User friendly data entry screens for codelists and reference tables Efficiency gained by providing improved interface views to the downstream systems Reduced manual review steps Instant access to all end users to browse metadata

Current Challenges Data entry screens for CDE not user friendly Batch load functionality requires lot of pre-processing steps due to de-normalized structure of MDR Option to subset elements and codelists does not exist Dependent objects and attributes need to be manually created. This entails 40% of the objects within the CDE Unable to manage study level metadata Transformation challenges – horizontal to vertical, handling blank records, etc. Other challenges include Versioning, lack of interface with upstream/downstream systems, ADaM metadata housed outside of MDR, etc.

Metadata Management - Future Support both Global Data Standards and Study level metadata needs Support global & study level governance workflows Enable integration with CDMS and CDISC - SHARE Enable integration with upstream and downstream systems Create views to support Define.xml requirements Integrate ADaM Metadata and Structures

Metadata Management - Future Proposed process flow

Governance workflow model Request Decision Feedback * CSU encompasses: Clinical Science Unit Business Unit (i.e. Oncology) Translational Sciences (TS) Requestor (CTH/CTL) CSU Data Standards Governance Standards Extended Team Onc. Standards - approves (from a scientific & franchise specific standpoint) requests DSG - final approval DSG - Standards Experts who approve requests from CSUs, with input from Extended Team, as required (senior representatives with a background in Clinical Science, Biostatistics, Statistical Reporting, Data Management Ext. Team - Provides adhoc expertise in specific functional area (e.g. Imaging, lab data, biomarker development) Oncology - Integrated Disease Area strategy team (IDS) Requester - Identifies new needs for data element /codelist for safety / indication standards

Questions?