Riepilogo e Spazio Q&A

Similar documents
Introduction to ADaM and What s new in ADaM

Traceability: Some Thoughts and Examples for ADaM Needs

An Efficient Solution to Efficacy ADaM Design and Implementation

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

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

Introduction to ADaM standards

Creating an ADaM Data Set for Correlation Analyses

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

ADaM Compliance Starts with ADaM Specifications

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

Some Considerations When Designing ADaM Datasets

ADaM for Medical Devices: Extending the Current ADaM Structures

A Taste of SDTM in Real Time

ADaM and traceability: Chiesi experience

Deriving Rows in CDISC ADaM BDS Datasets

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

Clarifications About ADaM Implementation Provided in ADaMIG Version 1.1

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

How to write ADaM specifications like a ninja.

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

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

Interpreting CDISC ADaM IG through Users Interpretation

PharmaSUG2014 Paper DS09

DCDISC Users Group. Nate Freimark Omnicare Clinical Research Presented on

SDTM-ETL 3.2 User Manual and Tutorial

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

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

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

Avoiding Sinkholes: Common Mistakes During ADaM Data Set Implementation

ADaM Implementation Guide Status Update

PharmaSUG Paper DS24

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

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

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

Material covered in the Dec 2014 FDA Binding Guidances

ADaM Implementation Guide Prepared by the CDISC ADaM Team

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

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

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

PharmaSUG Paper PO22

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

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

ADaM Reviewer s Guide Interpretation and Implementation

PharmaSUG DS05

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

Applying ADaM Principles in Developing a Response Analysis Dataset

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

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

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

Traceability Look for the source of your analysis results

Standardizing FDA Data to Improve Success in Pediatric Drug Development

AZ CDISC Implementation

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

Optimization of the traceability when applying an ADaM Parallel Conversion Method

Metadata and ADaM.

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

Customer oriented CDISC implementation

NCI/CDISC or User Specified CT

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

Study Data Reviewer s Guide Completion Guideline

Legacy to SDTM Conversion Workshop: Tools and Techniques

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

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

Detecting Treatment Emergent Adverse Events (TEAEs)

Mapping and Terminology. English Speaking CDISC User Group Meeting on 13-Mar-08

Application of SDTM Trial Design at GSK. 9 th of December 2010

PharmaSUG Paper PO21

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

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

Conversion of CDISC specifications to CDISC data specifications driven SAS programming for CDISC data mapping

Considerations on creation of SDTM datasets for extended studies

Updates on CDISC Standards Validation

Optimization of the traceability when applying an ADaM Parallel Conversion Method

TS04. Running OpenCDISC from SAS. Mark Crangle

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

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

Experience of electronic data submission via Gateway to PMDA

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

Validating Analysis Data Set without Double Programming - An Alternative Way to Validate the Analysis Data Set

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

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

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

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

Challenges with the interpreta/on of CDISC - Who can we trust?

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

The «CDISC Stupidario» (the CDISC Nonsense)

SDTM domains by query - is it possible?

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

Why organizations need MDR system to manage clinical metadata?

SDTM Automation with Standard CRF Pages Taylor Markway, SCRI Development Innovations, Carrboro, NC

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

DIA 11234: CDER Data Standards Common Issues Document webinar questions

Out-of-the-box %definexml

Johannes Ulander. Standardisation and Harmonisation Specialist S-Cubed. PhUSE SDE Beerse,

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

CDISC Standards and the Semantic Web

esubmission - Are you really Compliant?

SDTM-ETL. New features in version 3.2. SDTM-ETLTM: New features in v.3.2

What is high quality study metadata?

Transcription:

Riepilogo e Spazio Q&A CDISC Italian User Network Day 27 Ottobre 2017 Angelo Tinazzi (Cytel) - Silvia Faini (CROS NT) E3C members 2

Agenda ADaM key list Bad & Good ADaM...More... Spazio Q&A

ADaM Key List 4

ADaM Key List ADaM Key Principles Traceability Be analysis-ready Have metadata Be usable with common available tool

ADaM Key List ADaM is not ADaM without define.xml ADSL is the only mandatory ADaM datasets, all the rest is analysis driven i.e. no need to create ADIE (inclusion/exclusion criteria), no need to create ADMH if there is no specific MH analysis Create a second by-subject ADaM if ADSL is not enough i.e. do not try to squeeze all baseline variables in ADSL. For example create something called ADBASE ADxxx if it s ADaM compliant ADxxx otherwise

ADaM Key List Respect naming conventions for standards variables or use ADaM fragments when deriving new variables Fragment CHG BL FU OT Meaning Change Baseline Follow-up On treatment Format: Sponsor defined content fragment + Period (i.e., xx) + ADaM timing fragment + Date/Time Suffix or Grouping Suffix RU SC TA TI WA Run-in Screening Taper Titer Washout Examples: SBP01BL WEIGHTSC WT01SC RUSDT WA01SDT BMIBLGR1

ADaM Key List ADaM can be derived from the following source one SDTM dataset multiple SDTM datasets one ADaM dataset multiple ADaM datasets a combination of SDTM and ADaM datasets The only allowed non-sdtm/non-adam datasets are look-up datasets i.e. a dataset containing SMQ mapping

ADaM Key List Traceability (cont) Hypertension event (HYPEREVT) is defined as the earliest occurrence of hospital admission, DBP > 90 or SBP >140 DATA AS FOUND IN SDTM VS DATASET USUBJID VISITNUM VSSEQ VSDTC VSDY VSTESTCD VSSTRESN 2010 1 22 2004-08-05 1 SYSBP 115 2010 1 23 2004-08-05 1 DIABP 75 2010 2 101 2004-08-12 8 SYSBP 120 2010 2 102 2004-08-12 8 DIABP 90 2010 3 207 2004-08-19 15 SYSBP 135 2010 3 208 2004-08-19 15 DIABP 92 DATA AS FOUND IN SDTM DS DATASET USUBJID DSSEQ DSSTDTC DSSTDY DSDECOD DSTERM 2010 25 2004-08-05 1 RANDOM Subject Randomized 2010 99 2004-08-13 9 HOSPSTRT Subject Hospitalized 2010 140 2004-08-15 11 Subject Discharged from HOSPEND Hospital 2010 301 2004-08-26 22 COMPLETED Subject Completed Analysis Dataset USUBJID PARAMCD AVAL SRCDOM SRCVAR SRCSEQ 2010 HOSPSTRT 9 DS DSSTDY 99 2010 DBP 15 VS VSDY 208 2010 HYPEREVT 9 DS DSSTDY 99

ADaM Key List Traceability ADaM is always derived from SDTM No need to copy over all source datasets records from (but for ADAE/OCCDS...) i.e. not all laboratory parameters needs to be mapped to ADLB if they are not all analyzed i.e. if Urinalysis are only described in listings However make sure you copy all relevant variables to make the ADaM analysis-ready i.e. study population flags and subgroups/covariates from ADSL It has to be traceable back to source make use of --SEQ i.e. AESEQ when deriving ADAE make use of SRCDOM/SRCVAR/SRCSEQ when an ADaM dataset make use of several datasets as source

ADaM Key List Traceability (cont) Make use of flags to specify which records are not used for which analysis i.e. ANLxxFL Use of Intermediate ADaM Datasets Validate against SDTM in the P21 validation include DM, EX and AE

ADaM Key List Derivations/Imputations If an SDTM variable appears in an ADaM dataset, then ALL attributes must remain the same same name, same meaning, same values with few exceptions i.e. DS.DSDECOD Variable name, label, format, content With the exception that lengths can be shortened to the maximum length needed for the variable Imputations for missing information not in SDTM but in ADaM. Be transparent do not override original variables and make use of date DTFL new record i.e. when a missing time-point is derived from other time-points, for example LOCF or WOCF methods

ADaM Key List BDS The six «good» rules All rules except one require the creation of new records Rule 1: A parameter-invariant function of AVAL and BASE on the same row that does not involve a transform of BASE should be added as a new column. Rule 2: A transformation of AVAL that does not meet the conditions of Rule 1 should be added as a new parameter, and AVAL should contain the transformed value. Rule 3: A function of one or more rows within the same parameter for the purpose of creating an analysis timepoint should be added as a new row for the same parameter. Rule 4: A function of multiple rows within a parameter should be added as a new parameter. Rule 5: A function of more than one parameter should be added as a new parameter. Rule 6: When there is more than one definition of baseline, each additional definition of baseline requires the creation of its own set of rows.

Bad & Good ADaM 14

Bad and Good Microsoft Excel Worksheet PARCATy can be not used as PARAM Qualifier Misuse of flag and criteria variables BDS Deriving Rows or adding columns

Bad & Good ADaM PARCATy can be not used as PARAM Qualifier Provisional PARQUAL

Bad & Good ADaM BDS Deriving Rows or adding columns Section 4.2 of IG illustrates the 6 rules for the creation of rows vs columns All rules except one require the creation of new records «A parameter invariant function of AVAL and BASE on the same row that does not involve a transformation of BASE should be added as a new column» Adding a new column is restricted to available BDS variables e.g. CHG=AVAL-BASE Designing and Tuning ADaM Datasets; PharmaSUG 2013 Common Misunderstanding about ADaM Implementation; PharmaSUG 2012 Adding new Rows in the ADaM Basic Data Structure. When and How; SAS Global Forum 2013 Derived observations and associated variables in ADaM datasets; PharmaSUG 2013

Bad & Good ADaM BDS Deriving Rows or adding column (Cont)

.More. 19

Analysis Datasets vs ADaM Date Imputation Data Imputation AVAL vs AVALC Analysis Ready Use of Analysis Flags

.More. Analysis Datasets vs ADaM Analysis Datasets ADaM Datasets ADSL BDS OCCDS OTHER Non-ADaM Analysis Datasets ADSL ADLB* ADAE* ADMV* PATP** ADEFF* AXEVT** ADTTE* Datasets not in one of the defined ADaM structures can still be ADaM datasets They must follow the ADaM Fundamental Principles and naming conventions * Example name of ADaM dataset ** Example name of dataset developed without following ADaM fundamental principles

.More. Date Imputation A subject can t remember the day of a knee injury SDTM MH.MHSTDTC = 2013-05 ADaM Imputation, per SAP specifications: ADMH.ASTDT = May 1, 2013 (numeric date) and ASTDTF = D A subject can t remember the month of a knee injury SDTM MH. MHSTDTC = 2013---15 ADaM Imputation, per SAP specifications: ADMH. ASTDT = January 1, 2013 and ASTDTF = M A subject can t remember the month or day SDTM MH. MHSTDTC = 2013 ADaM Imputation, per SAP specifications: ADMH. ASTDT = January 1, 2013 and ASTDTF = M

.More. Data Imputation AEREL NOT RELATED NOT RELATED NOT RELATED POSSIBLY RELATED PROBABLY RELATED PROBABLY RELATED DEFINITELY RELATED DEFINITELY RELATED DEFINITELY RELATED RELGR1 Not Related Not Related Not Related Related Related Related Related Related Related Related Original value of AEREL copied from SDTM New variable RELGR1 created to group into Related Not Related Follows the ADaM general naming conventions, like BDS Mixed case content makes table production easier

.More. Data Imputation (cont) Derivation of study endpoint when early drop-out Primary endpoint was «Weekly Mean Daily Pain Intensity Score at 12 weeks» For early drop-out prior to week-12 the Last Observation Carry forward imputation method was used

.More. AVAL vs AVALC When both AVAL and AVALC are non-missing on any record of a parameter, then AVALC must be 1:1 with AVAL on all records for that parameter

.More. Analysis Ready As per ADaM IG Analysis datasets have a structure and content that allows statistical analysis to be performed with minimal programming Analysis ready" - Considerations, Implementations, and Real World Applications; PharmaSUG 2012 Laboratory Analysis Dataset (ADLB): a real-life experience; CDISC Europe Interchange 2013 Linkedin ADaM Group Discussion http://www.linkedin.com/groupitem?view=&gid=3092582&type=member&item=245409684&qid=379c7b1b-df19-4772-acf1-3d279ef5b245&trk=group_most_popular-0-b-ttl&goback=%2egmp_3092582&_msplash=1 One-proc-away Output programs should only focus on selecting (and extracting) the statistical models and «eventually» improving the standard statistical outputs template It is preferable to have complex derivation in the derived (and fully validated) analysis datasets

.More. Analysis Ready (cont) Complex derivations for exposure ADEXSUM derived from ADEX

.More. Use of Analysis Flag Derivation of Weekly Mean Daily Pain Intensity Score by excluding observations occurred during the washout period

Spazio Q&A 29