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

Similar documents
Introduction to ADaM and What s new in ADaM

Material covered in the Dec 2014 FDA Binding Guidances

Yes! The basic principles of ADaM are also best practice for our industry Yes! ADaM a standard with enforceable rules and recognized structures Yes!

ADaM Compliance Starts with ADaM Specifications

Clarifications About ADaM Implementation Provided in ADaMIG Version 1.1

Riepilogo e Spazio Q&A

How to write ADaM specifications like a ninja.

Creating an ADaM Data Set for Correlation Analyses

An Efficient Solution to Efficacy ADaM Design and Implementation

DCDISC Users Group. Nate Freimark Omnicare Clinical Research Presented on

ADaM Implementation Guide Status Update

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

PharmaSUG2014 Paper DS09

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

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

Traceability Look for the source of your analysis results

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

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

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

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

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

ADaM for Medical Devices: Extending the Current ADaM Structures

Deriving Rows in CDISC ADaM BDS Datasets

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

Introduction to ADaM standards

Analysis Data Model Implementation Guide Version 1.1 (Draft) Prepared by the CDISC Analysis Data Model Team

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

Applying ADaM Principles in Developing a Response Analysis Dataset

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

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

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

PharmaSUG Paper PO22

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

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

ADaM Reviewer s Guide Interpretation and Implementation

One-PROC-Away: The Essence of an Analysis Database Russell W. Helms, Ph.D. Rho, Inc.

PharmaSUG Paper PO21

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

ADaM and traceability: Chiesi experience

Sandra Minjoe, Accenture Life Sciences John Brega, PharmaStat. PharmaSUG Single Day Event San Francisco Bay Area

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

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

Customer oriented CDISC implementation

PharmaSUG Paper DS24

CDISC SDTM and ADaM Real World Issues

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

Edwin Ponraj Thangarajan, PRA Health Sciences, Chennai, India Giri Balasubramanian, PRA Health Sciences, Chennai, India

Doctor's Prescription to Re-engineer Process of Pinnacle 21 Community Version Friendly ADaM Development

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

How to handle different versions of SDTM & DEFINE generation in a Single Study?

A Taste of SDTM in Real Time

NCI/CDISC or User Specified CT

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

Clinical Metadata Metadata management with a CDISC mindset

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

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

Creating Define-XML v2 with the SAS Clinical Standards Toolkit 1.6 Lex Jansen, SAS

Lex Jansen Octagon Research Solutions, Inc.

AZ CDISC Implementation

SDTM Implementation Guide Clear as Mud: Strategies for Developing Consistent Company Standards

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

Some Considerations When Designing ADaM Datasets

Main challenges for a SAS programmer stepping in SAS developer s shoes

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

Interpreting CDISC ADaM IG through Users Interpretation

Optimization of the traceability when applying an ADaM Parallel Conversion Method

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

Study Data Reviewer s Guide Completion Guideline

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

Why organizations need MDR system to manage clinical metadata?

Introduction to Define.xml

Automated Creation of Submission-Ready Artifacts Silas McKee, Accenture, Pennsylvania, USA Lourdes Devenney, Accenture, Pennsylvania, USA

Codelists Here, Versions There, Controlled Terminology Everywhere Shelley Dunn, Regulus Therapeutics, San Diego, California

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

SAS Application to Automate a Comprehensive Review of DEFINE and All of its Components

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

Comparison of FDA and PMDA Requirements for Electronic Submission of Study Data

Metadata and ADaM.

Reporting & Visualisation : D un Dun standard maison au format CDISC 02/02/2016 CDISC GUF 1

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

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

Define.xml 2.0: More Functional, More Challenging

Legacy to SDTM Conversion Workshop: Tools and Techniques

TS04. Running OpenCDISC from SAS. Mark Crangle

How to review a CRF - A statistical programmer perspective

Creating Define-XML version 2 including Analysis Results Metadata with the SAS Clinical Standards Toolkit

SAS as a Tool to Manage Growing SDTM+ Repository for Medical Device Studies Julia Yang, Medtronic Inc. Mounds View, MN

Avoiding Sinkholes: Common Mistakes During ADaM Data Set Implementation

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

Considerations on creation of SDTM datasets for extended studies

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

The application of SDTM in a disease (oncology)-oriented organization

Lex Jansen Octagon Research Solutions, Inc.

Standardizing FDA Data to Improve Success in Pediatric Drug Development

ADaM Implementation Guide Prepared by the CDISC ADaM Team

Best Practice for Explaining Validation Results in the Study Data Reviewer s Guide

Detecting Treatment Emergent Adverse Events (TEAEs)

Updates on CDISC Standards Validation

The Submission Data File System Automating the Creation of CDISC SDTM and ADaM Datasets

Implementing CDISC at Boehringer Ingelheim

Transcription:

Accenture Accelerated R&D Services Rethink Reshape Restructure for better patient outcomes What is the ADAM OTHER Class of Datasets, and When Should it be Used? John Troxell, Data Standards Consulting

Outline ADaM fundamental principles ADaM dataset classes and standard dataset structures The OTHER Class of ADaM datasets ADaM OTHER in the universe of analysis datasets When the OTHER class should and should not be used Concluding thoughts 2015 Accenture All Rights Reserved. 2

CDISC ADaM Clinical Data Interchange Standards Consortium (CDISC) Analysis Data Model (ADaM) Model for observed and derived subject data enabling analysis and supporting review Influenced by needs of FDA statistical and medical reviewers Preferred by FDA Will be required by FDA for new studies no earlier than Dec. 18, 2016 Transparent: Materializes and exposes derivation Fundamental Principles Standard data and metadata structures standard variables dataset and variable naming conventions rules etc. 2015 Accenture All Rights Reserved. 3

The Evolution of ADaM First, there was a philosophy: Fundamental Principles 2015 Accenture All Rights Reserved. 4

ADaM Fundamental Principles Analysis datasets and their associated metadata must: facilitate clear and unambiguous communication provide traceability between the analysis data and its source data (ultimately SDTM) be readily useable by commonly available software tools Analysis datasets must: be accompanied by metadata be analysis-ready 2015 Accenture All Rights Reserved. 5

Fundamental Principles have Practical Effects - A Few Examples Analysis datasets and their associated metadata must: facilitate clear and unambiguous communication Flag imputed dates Keep all observed and derived records, not just those analyzed provide traceability between the analysis data and its source data (ultimately SDTM) Include traceability variables, e.g. --SEQ Metadata traceability always required Analysis datasets must: be analysis-ready Ideally, One PROC away from results Minimal or no data manipulation in analysis programs 2015 Accenture All Rights Reserved. 6

The Evolution of ADaM First, there was a philosophy: Fundamental Principles Then there were standard data structures: Classes of ADaM Datasets 2015 Accenture All Rights Reserved. 7

Four Classes of ADaM Datasets But only Three Standard Data Structures 1. Subject-Level Analysis Dataset (ADSL) only member of this class is ADSL 2. Basic Data Structure (BDS) the Swiss Army Knife vertical structure 3. Occurrence Data Structure (OCCDS) Generalization of ADAE, will be finalized in 2015 4. Other (ADAM OTHER) This class has no standard structure! Note: the OTHER Class is called ADAM OTHER in the CDISC Controlled Terminology for CLASS 2015 Accenture All Rights Reserved. 8

The OTHER Class Purpose is to support analyses that cannot be supported by the ADaM dataset structures that have been defined to date Datasets of the OTHER Class must: follow the ADaM Fundamental Principles follow all ADaM dataset and variable naming conventions, etc. as much as possible The OTHER Class shrinks as the CDISC ADaM Team defines new Classes and structures e.g., BDS (2009), ADTTE in BDS (2012), ADAE (2012), OCCDS (2015) But the OTHER Class is unlimited and grows each time someone needs something that is not yet addressed 2015 Accenture All Rights Reserved. 9

ADaM OTHER in the Universe of Analysis Datasets Analysis Datasets ADaM Datasets Non-ADaM Analysis Datasets ADSL Class Datasets BDS Class Datasets OCCDS Class Datasets OTHER Class Datasets No Class! J ADSL AD... AD... AD........ ADLB* ADAE* ADTTE* ADMH* 2015 Accenture All Rights Reserved. 10

So what have we seen so far? Not all analysis datasets are ADaM datasets ADaM datasets is not a synonym of analysis datasets Non-ADaM analysis dataset ADaM dataset of the OTHER Class There are standard ADaM data structures (ADSL, BDS, OCCDS) The ADaM OTHER Class doesn t have a standard structure 2015 Accenture All Rights Reserved. 11

The OTHER Class has no standard structure so can I use the OTHER Class to do whatever I like? I really don t like the BDS vertical dataset structure. I prefer a horizontal structure. Can I make a horizontal dataset like I am used to and call it an OTHER class dataset? Probably not! OTHER is not a loophole to drive a truck through ADaM is a data standard FDA wants sponsors to use the ADaM data standard Use an ADaM standard structure when a standard structure is capable of enabling the analysis 2015 Accenture All Rights Reserved. 12

Why choose an ADaM standard data structure when it is capable of enabling the analysis? Use standard structures when you can, because they help: Everyone: Facilitate advances in medicine Your peers: Improve communication (including at PharmaSUG!) Your company: Data integration, systems, people onboarding, partnering Regulatory agencies: Make FDA more effective reduce learning curve in new submissions support FDA review tools You benefit too: Fewer oddities to explain in metadata and reviewer s guide Enable portable skills (good for the resume!) Don t use OTHER unless the standard structures are not capable of supporting the analysis 2015 Accenture All Rights Reserved. 13

We all have a stake in the standard structures What would happen if most people decided to deviate a little bit from the standard structures? Is that harmless? Is there a slippery slope? Would we have a data standard? ADaM standard structures handle more situations than you might think at first glance Designing ADaM datasets, especially BDS, is a creative process Become familiar with all the tools in the BDS toolbox Please think twice! 2015 Accenture All Rights Reserved. 14

When can I use OTHER? We have just seen that you should use the standard data structures when you can Now we will look at 4 situations where it may make sense to use OTHER There may be others 2015 Accenture All Rights Reserved. 15

Reason #1 for an ADaM OTHER Class dataset: No standard structure can enable the analysis If ADSL, BDS and OCCDS cannot support the analysis, then the OTHER class can be used Must follow ADaM fundamental principles, naming conventions, etc. Example: Multivariate Analysis of Variance (MANOVA) More than one dependent variable is needed on the same row Example: Correlation Matrix The variables to be correlated must be on the same row Note: True statistical multivariate analysis is rare in Pharma Virtually all hypothesis testing in Pharma involves univariate analysis (one analysis variable on the left hand side of the model statement) BDS works great for univariate analyses (ANCOVA, CMH, TTE, ) Note: A horizontal OTHER Class dataset can often be created by transposing a BDS dataset, using BDS PARAMCD for the analysis variable names (but this is not always simple) 2015 Accenture All Rights Reserved. 16

Reason #2 for an ADaM OTHER Class dataset: Listing view Someone wants/needs to see analysis variables side-by-side This can be a legitimate need of statistician or reviewer An ADaM dataset of the OTHER Class, or even a non-adam dataset, can be created to support eyeball review of data If it follows ADaM fundamental principles etc., can be ADaM OTHER Class However, such a dataset should not be used as the input dataset to the statistical analysis if ADSL, BDS, or OCCDS would suffice 2015 Accenture All Rights Reserved. 17

Reason #3 for an ADaM OTHER Class dataset: Pre-ADSL dataset Example: a pre-adsl dataset that assembles facts to be used when deriving per-protocol population flag PPROTFL in ADSL, e.g. Was the subject compliant enough with the prescribed therapy? Did the subject take certain disqualifying concomitant medications? Did the subject violate dietary restrictions? This dataset could be like a BDS dataset, with a parameter PARAM for each of these facts; but it probably won t be BDS-compliant It won t have planned treatment It won t have variables copied from ADSL If it follows ADaM fundamental principles etc., can be ADaM OTHER Class This dataset won t be used for analysis If these facts are needed for analysis, create ADSL variables to contain them 2015 Accenture All Rights Reserved. 18

Reason #4 for an ADaM OTHER Class dataset: Intermediate dataset Example: an EX-plus (ADEX?) dataset is needed for statistician review SDTM EX Plus some SDTM EX supplemental qualifiers Plus some columns copied from ADSL Plus some derived variables If it follows ADaM fundamental principles etc., can be ADaM OTHER Class Note: Renaming EXTRT to PARAM and some other variable to AVAL does not make this a BDS dataset This dataset should not be used for the statistical analysis A compliant BDS dataset (ADEXSUMM?) may be derived from this intermediate dataset Parameters summarizing aspects of exposure for analysis 2015 Accenture All Rights Reserved. 19

Not Valid Reasons for OTHER It s going to cost us a lot to change to the standard ADaM structures I am used to a certain layout I don t want to learn something new I want to do it my way 2015 Accenture All Rights Reserved. 20

Concluding Thoughts CDISC ADaM has rules, but can still express the science There is plenty of room for expression within ADSL, BDS, OCCDS Designing ADaM datasets is a creative process The ADaM OTHER Class is available for use when there is a need that can t be met by the standard ADaM dataset structures Don t be afraid of it but use it only when necessary 2015 Accenture All Rights Reserved. 21

References www.cdisc.org/adam http://www.fda.gov/forindustry/datastandards/studydatastandard s/default.htm 2015 Accenture All Rights Reserved. 22

Questions? John Troxell Data Standards Consulting Accenture Accelerated R&D Services john.troxell@accenture.com 2015 Accenture All Rights Reserved. 23