Metadata and ADaM.

Similar documents
From SAP to BDS: The Nuts and Bolts Nancy Brucken, i3 Statprobe, Ann Arbor, MI Paul Slagle, United BioSource Corp., Ann Arbor, MI

Creating an ADaM Data Set for Correlation Analyses

Applying ADaM Principles in Developing a Response Analysis Dataset

The Implementation of Display Auto-Generation with Analysis Results Metadata Driven Method

Working with Composite Endpoints: Constructing Analysis Data Pushpa Saranadasa, Merck & Co., Inc., Upper Gwynedd, PA

PharmaSUG2014 Paper DS09

Making a List, Checking it Twice (Part 1): Techniques for Specifying and Validating Analysis Datasets

ADaM for Medical Devices: Extending the Current ADaM Structures

PharmaSUG 2013 PO05. ADaM Datasets for Graphs Kevin Lee, Cytel, Inc., Chesterbrook, PA Chris Holland, Amgen, Rockville, MD

How to write ADaM specifications like a ninja.

PharmaSUG Paper DS24

Interactive Programming Using Task in SAS Studio

ADaM and traceability: Chiesi experience

Hands-On ADaM ADAE Development Sandra Minjoe, Accenture Life Sciences, Wayne, Pennsylvania

Dealing with changing versions of SDTM and Controlled Terminology (CT)

Hands-On ADaM ADAE Development Sandra Minjoe, Accenture Life Sciences, Wayne, Pennsylvania Kim Minkalis, Accenture Life Sciences, Wayne, Pennsylvania

Customer oriented CDISC implementation

PharmaSUG Paper DS06 Designing and Tuning ADaM Datasets. Songhui ZHU, K&L Consulting Services, Fort Washington, PA

PharmaSUG Paper DS-24. Family of PARAM***: PARAM, PARAMCD, PARAMN, PARCATy(N), PARAMTYP

Optimization of the traceability when applying an ADaM Parallel Conversion Method

Best Practices for E2E DB build process and Efficiency on CDASH to SDTM data Tao Yang, FMD K&L, Nanjing, China

It s All About Getting the Source and Codelist Implementation Right for ADaM Define.xml v2.0

Programming checks: Reviewing the overall quality of the deliverables without parallel programming

Traceability: Some Thoughts and Examples for ADaM Needs

A Taste of SDTM in Real Time

Use of Traceability Chains in Study Data and Metadata for Regulatory Electronic Submission

Optimization of the traceability when applying an ADaM Parallel Conversion Method

DCDISC Users Group. Nate Freimark Omnicare Clinical Research Presented on

ABSTRACT INTRODUCTION WHERE TO START? 1. DATA CHECK FOR CONSISTENCIES

Deriving Rows in CDISC ADaM BDS Datasets

PharmaSUG Paper PO22

From Just Shells to a Detailed Specification Document for Tables, Listings and Figures Supriya Dalvi, InVentiv Health Clinical, Mumbai, India

NCI/CDISC or User Specified CT

Out-of-the-box %definexml

PharmaSUG 2014 PO16. Category CDASH SDTM ADaM. Submission in standardized tabular form. Structure Flexible Rigid Flexible * No Yes Yes

Some Considerations When Designing ADaM Datasets

CDASH Standards and EDC CRF Library. Guang-liang Wang September 18, Q3 DCDISC Meeting

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

The Benefits of Traceability Beyond Just From SDTM to ADaM in CDISC Standards Maggie Ci Jiang, Teva Pharmaceuticals, Great Valley, PA

Standards Metadata Management (System)

An Efficient Solution to Efficacy ADaM Design and Implementation

ADaM Implementation Guide Prepared by the CDISC ADaM Team

Traceability in the ADaM Standard Ed Lombardi, SynteractHCR, Inc., Carlsbad, CA

Legacy to SDTM Conversion Workshop: Tools and Techniques

PharmaSUG DS05

Automate Analysis Results Metadata in the Define-XML v2.0. Hong Qi, Majdoub Haloui, Larry Wu, Gregory T Golm Merck & Co., Inc.

CDASH MODEL 1.0 AND CDASHIG 2.0. Kathleen Mellars Special Thanks to the CDASH Model and CDASHIG Teams

Introduction to ADaM standards

Experience of electronic data submission via Gateway to PMDA

THE DATA DETECTIVE HINTS AND TIPS FOR INDEPENDENT PROGRAMMING QC. PhUSE Bethan Thomas DATE PRESENTED BY

EDC integrations. Rob Jongen Integration Technology & Data Standards

ADaM Reviewer s Guide Interpretation and Implementation

PharmaSUG Paper PO21

Paper FC02. SDTM, Plus or Minus. Barry R. Cohen, Octagon Research Solutions, Wayne, PA

DIA 11234: CDER Data Standards Common Issues Document webinar questions

ADaM IG v1.1 & ADaM OCCDS v1.0. Dr. Silke Hochstaedter

Preparing the Office of Scientific Investigations (OSI) Requests for Submissions to FDA

Riepilogo e Spazio Q&A

SAS Training BASE SAS CONCEPTS BASE SAS:

Considerations on creation of SDTM datasets for extended studies

An Introduction to Visit Window Challenges and Solutions

Study Data Reviewer s Guide Completion Guideline

Introduction to ADaM and What s new in ADaM

Implementing CDISC Using SAS. Full book available for purchase here.

Analysis Data Model (ADaM) Data Structure for Adverse Event Analysis

How a Metadata Repository enables dynamism and automation in SDTM-like dataset generation

Planning to Pool SDTM by Creating and Maintaining a Sponsor-Specific Controlled Terminology Database

A SAS and Java Application for Reporting Clinical Trial Data. Kevin Kane MSc Infoworks (Data Handling) Limited

Robust approach to create Define.xml v2.0. Vineet Jain

Linking Metadata from CDASH to ADaM Author: João Gonçalves Business & Decision Life Sciences, Brussels, Belgium

Pharmaceuticals, Health Care, and Life Sciences. An Approach to CDISC SDTM Implementation for Clinical Trials Data

Leveraging Study Data Reviewer s Guide (SDRG) in Building FDA s Confidence in Sponsor s Submitted Datasets

Traceability Look for the source of your analysis results

Automated generation of program templates with metadata based specification documents for integrated analysis Thomas Wollseifen, Germany Vienna, Oct

Automation of SDTM Programming in Oncology Disease Response Domain Yiwen Wang, Yu Cheng, Ju Chen Eli Lilly and Company, China

How Macro Design and Program Structure Impacts GPP (Good Programming Practice) in TLF Coding

Beyond OpenCDISC: Using Define.xml Metadata to Ensure End-to-End Submission Integrity. John Brega Linda Collins PharmaStat LLC

Material covered in the Dec 2014 FDA Binding Guidances

Implementation of Data Cut Off in Analysis of Clinical Trials

Global Checklist to QC SDTM Lab Data Murali Marneni, PPD, LLC, Morrisville, NC Sekhar Badam, PPD, LLC, Morrisville, NC

Leveraging ADaM Principles to Make Analysis Database and Table Programming More Efficient Andrew L Hulme, PPD, Kansas City, MO

CDISC Variable Mapping and Control Terminology Implementation Made Easy

What is the ADAM OTHER Class of Datasets, and When Should it be Used? John Troxell, Data Standards Consulting

PhUSE Paper SD09. "Overnight" Conversion to SDTM Datasets Ready for SDTM Submission Niels Mathiesen, mathiesen & mathiesen, Basel, Switzerland

An Introduction to Analysis (and Repository) Databases (ARDs)

Harmonizing CDISC Data Standards across Companies: A Practical Overview with Examples

Knock Knock!!! Who s There??? Challenges faced while pooling data and studies for FDA submission Amit Baid, CLINPROBE LLC, Acworth, GA USA

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

SDTM-ETL 3.1 User Manual and Tutorial

ADaM Implementation Guide Status Update

SAS offers technology to facilitate working with CDISC standards : the metadata perspective.

Now let s take a look

From Implementing CDISC Using SAS. Full book available for purchase here. About This Book... xi About The Authors... xvii Acknowledgments...

How to review a CRF - A statistical programmer perspective

Paper DS07. Generating Define.xml and Analysis Result Metadata using Specifications, Datasets and TFL Annotation

Advanced Data Visualization using TIBCO Spotfire and SAS using SDTM. Ajay Gupta, PPD

esubmission - Are you really Compliant?

The Wonderful World of Define.xml.. Practical Uses Today. Mark Wheeldon, CEO, Formedix DC User Group, Washington, 9 th December 2008

Xiangchen (Bob) Cui, Tathabbai Pakalapati, Qunming Dong Vertex Pharmaceuticals, Cambridge, MA

Define.xml. Not Just for Submissions Anymore. Robbert P. van Manen, M.Sc. Senior Technical Solutions Consultant July 2010

Transcription:

Metadata and ADaM 1

Disclaimer Any views or opinions presented in this presentation are solely those of the author and do not necessarily represent those of the company. 2

Agenda Introduction of ADaM Metadata Clincial Trial Process Examples of how to create Metadata Goal of ADaM Metadata Pros and Cons Conclusion Questions & Answers 3

ADaM Metadata Definition Information of ADaM(Analysis Data Model) datasets Types Analysis Dataset Metadata Analysis Variable Metadata Analysis Parameter Value Level Metadata Analysis Results Metadata 4

Normal Clinical Trial Process Protocol SAP Mock Up Tables CRF DMDB Raw Derived TFL 5

CDISC Clinical Trial Process Protocol SAP Mock Up Tables ecrf ADaM Metadata EDC SDTM ADaM TFL ADaM Related Process 6

ADaM Related Process ADaM Metadata Analysis Dataset Metadata Analysis Variable Metadata Analysis Parameter value level Metadata Analysis Results Metadata ADaM TFL 7

Time to Event Example 1 Mock Up table Table 14.2.1 Time to Death by Treatment PARAM = Time to Death (Days), TRTP Analysis Population: Intent to Treat ITTFL= Y Drug 1 Drug 2 p-value N xxx xxx Censored Observation xxx xxx Median xx xx x.xx Q1, Q3 xx, xx xx, xx AVAL(Days to Event), CNSR(Censor information) PROC LIFETEST DATA=ADTTEOS; WHERE PARAM= Time to Death (Days) and ITTFL= Y ; TIME AVAL*CNSR(1); STRATA TRTP; RUN; 8

Time to Event Analysis Dataset Metadata Dataset Name Dataset Description Dataset Location Dataset Structure Key Variables of Dataset Class of Dataset Documentation ADTTEOS Overall Survival Time to Event Analysis Dataset adtteos.xpt One record per subject per parameter STUDYID, USUBJID, PARAM BDS adtteos.sas 9

[CB1]Note to ADaM team: We have elected to use this format for the program names. According to the Study Data Specifications, since the programs created by S Time to Event Analysis Variable Metadata including Analysis Parameter Value-Level Metadata (1) Dataset Name Parameter Identifier Variable Name Variable Label Variable Type Display Format Codelist / Controlled Terms Source / Derivation ADTTEOS *ALL* USUBJID Unique Subject Identifier Char $20 ADSL.USUBJID ADTTEOS *ALL* ITTFL Intent-To-Treat Population Flag ADTTEOS *ALL* TRTP Planned Treatment ADTTEOS *ALL* TRTPN Planned Treatment (N) Char $1 Y, null ADSL.ITTFL Char $40 Drug 1, Drug 2 ADSL.TRT01P Num 8 1 = Drug 1, 2 = Drug 2 ADTTEOS PARAMCD PARAM Parameter Char $50 Time to Death (Days) ADTTEOS PARAMCD PARAMCD Parameter Code Char $8 DEATH ADSL.TRT01PN 10

[CB1]Note to ADaM team: We have elected to use this format for the program names. According to the Study Data Specifications, since the programs created by S Time to Event Analysis Variable Metadata including Analysis Parameter Value-Level Metadata (2) Dataset Name Parameter Identifier Variable Name Variable Label Variable Type Display Format Codelist / Controlled Terms Source / Derivation ADTTEOS *ALL* AVAL Analysis Value Num 8 ADT STARTDT + 1 ADTTEOS *ALL* STARTDT Time to Event Origin Date for Subject Num YYYYMM DD10. ADTTEOS *ALL* ADT Analysis Date Num YYYYMM DD10. ADSL.RANDDT SAS Date of DS.DSDTC ADTTEOS *ALL* CNSR Censor Num 8 0, 1 0 for DEATH, 1 for any other study completion ADTTEOS *ALL* EVNTDESC Event or Censoring Description Char $40 DEATH, COMPLETED THE STUDY, LOST TO FOLLOW-UP, AE DS.DSDECOD 11

Time to Event Analysis Results Metadata Metadata Field DISPLAY IDENTIFIER DISPLAY NAME RESULT IDENTIFIER PARAM PARAMCD ANALYSIS VARIABLE REASON DATASET SELECTION CRITERIA DOCUMENTATION PROGRAMMING STATEMENTS Table 14.2.1 Metadata Time to Death by Treatment, Analysis Population: Intent to Treat Time to Death (Days) Time to Death (Days) DEATH AVAL Primary efficacy analysis ADTTEOS ITTFL= Y and PARAM = Time to Death (Days) See SAP Section XX for details. Program: t_14.2.1_death.sas PROC LIFETEST DATA= ADTTEOS; WHERE ITTFL= Y and PARAM = Time to Death (Days) ; TIME AVAL*CNSR(1); STRATA TRTP; RUN; 12

Time to Event Example 2 Mock Up table Table 14.2.2 Time to Progression Free Survival : Cox Proportional Hazard Model PARAM = Time to Progression Free Survival (Days), TRTP Analysis Population: Intent to Treat ITTFL= Y Drug 1 Drug 2 p-value N xxx xxx Censored Observation xxx xxx Median xx xx x.xx Q1, Q3 xx, xx xx, xx AVAL(Days to Event), CNSR(Censor information) PROC PHREG DATA=ADTTEOS; WHERE PARAM= Time to Progression Free Survival (Days) and ITTFL= Y ; MODEL AVAL*CNSR(1) = TRTP AGE SEX ; RUN; 13

[CB1]Note to ADaM team: We have elected to use this format for the program names. According to the Study Data Specifications, since the programs created by S Time to Event Analysis Variable Metadata including Analysis Parameter Value-Level Metadata (1) Dataset Name Parameter Identifier Variable Name Variable Label Variable Type ADTTEOS *ALL* USUBJID Unique Subject Identifier Display Format Codelist / Controlled Terms Source / Derivation Char $20 ADSL.USUBJID ADTTEOS *ALL* AGE Age Num 8 ADSL.AGE ADTTEOS *ALL* SEX Sex Char $1 ADSL.SEX ADTTEOS *ALL* ITTFL Intent-To-Treat Population Flag Char $1 Y, null ADSL.ITTFL ADTTEOS *ALL* TRTP Planned Treatment ADTTEOS *ALL* TRTPN Planned Treatment (N) Char $40 Drug 1, Drug 2 ADSL.TRT01P Num 8 1 = Drug 1, 2 = Drug 2 ADTTEOS PARAMCD PARAM Parameter Char $50 Time to Death (Days) Time to Progression Free Survival (Days) ADTTEOS PARAMCD PARAMCD Parameter Code Char $8 DEATH PFS ADSL.TRT01PN 14

[CB1]Note to ADaM team: We have elected to use this format for the program names. According to the Study Data Specifications, since the programs created by S Time to Event Analysis Variable Metadata including Analysis Parameter Value-Level Metadata (2) Dataset Name Parameter Identifier Variable Name Variable Label Variable Type Display Format Codelist / Controlled Terms Source / Derivation ADTTEOS *ALL* AVAL Analysis Value Num 8 ADT STARTDT + 1 ADTTEOS *ALL* STARTDT Time to Event Origin Date for Subject Num YYYYMM DD10. ADTTEOS *ALL* ADT Analysis Date Num YYYYMM DD10. ADSL.RANDDT SAS Date of DS.DSDTC ADTTEOS DEATH CNSR Censor Num 8 0, 1 0 for DEATH, 1 for any other study completion ADTTEOS PFS CNSR Censor Num 8 0, 1 0 for DEATH and PFS, 1 for any other study completion ADTTEOS *ALL* EVNTDESC Event or Censoring Description Char $40 DEATH, COMPLETED THE STUDY, LOST TO FOLLOW-UP, AE, PFS DS.DSDECOD 15

Time to Event Analysis Results Metadata Metadata Field DISPLAY IDENTIFIER DISPLAY NAME RESULT IDENTIFIER PARAM PARAMCD ANALYSIS VARIABLE REASON DATASET SELECTION CRITERIA DOCUMENTATION PROGRAMMING STATEMENTS Table 14.2.2 Metadata Time to Progression Free Survival : Cox Proportional Hazard Model Time to Progression Free Survival (Days) Time to Progression Free Survival (Days) PFS AVAL Secondary efficacy analysis ADTTEOS ITTFL= Y and PARAM= Time to Progression Free Survival (Days) See SAP Section XX for details. Program: t_14.2.2_pfs.sas PROC PHREG DATA= ADTTEOS; WHERE ITTFL= Y and PARAM = Time to Progression Free Survival (Days) ; MODEL AVAL*CNSR(1) = TRTP AGE SEX; RUN; 16

Summary of Examples Mock Up Tables 14.2.1 14.2.2 Metadata Dataset ADTTEOS Variables USUBJID ITTFL TRTP, TRTPN PARAM, PARAMCD AVAL STARTDT, ADT CNSR EVNTDESC AGE SEX Parameter DEATH PFS Results Time to Death Time to PFS 17

Goal of Metadata Serve as Spec and Define Spec : provide the programmers how ADaM and some TFL can be created Define : datasets information for sponsors Central document for all programmers and statisticians 18

Goal of Metadata (2) Minimize the communication traffic in virtual office setting Philadelphia Office Boston Office Pune Office Remote Programming Reconciliation between ADaM datasets and Metadata use macros to check wether ADaM datasets follow Metadata. 19

Cons Who will prepare and maintain the metadata CDISC expert(sdtm, ADaM and so on) Programmer Lead Statistician The initial investment on resource and time at the early stage of the study Two many metadata? 20

Pros (1) Consistency in ADaM datasets Label Name Format # of variables Help the inexperience personnel ADaMis new The central document between developers and validators especially for the virtual office setting Helps the programmers on efficacy analysis. 21

Pros (2) Better estimate on the number of ADaM datasets help the planning and resourcing. Review on Mock Up tables and SAP 22

Conclusion The concept of Metadata is Plan your work and work your plan ADaM Metadata is ongoing until all are done. 23

Questions? 24