A Taste of ADaM Presented by: Peng/Zik Liu MSD (Shanghai) Pharma Co.

Slides:



Advertisements
Similar presentations
CDISC News: ADaM Basel, September 2, 2008.
Advertisements

Principal Statistical Programmer Accovion GmbH, Marburg, Germany
ADaM Implementation Guide: It’s Almost Here. Are You Ready?
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Analysis Data Model (ADaM)
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
Copyright © 2013, SAS Institute Inc. All rights reserved. LEVERAGE THE CDISC DATA MODEL TO STREAMLINE ANALYTICAL WORKFLOWS KELCI J. MICLAUS, PH.D. RESEARCH.
ADaM Standards Wouter van Wyk. Why ADaM –SDTM purpose is to provide collected data Not designed for ease of analysis –ADaM purpose is to provide data.
Common Problems in Writing Statistical Plan of Clinical Trial Protocol Liying XU CCTER CUHK.
Finalized FDA Requirements for Standardized Data
It’s about Time! (to Event)
Model X-Ray Image Data into ADaM BDS Structure
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
CDISC and how Stata can help us implement it
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
Principles and Practicalities in Building ADaM Datasets Cathy Barrows CDISC Users’ Group – May 25, 2012 Previously presented at: PhUSE Single Day Event.
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,
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
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.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
15th Informal US MedDRA User Group Meeting, October 28, 2011 Slide 1 Double the Impact with Half the Work: Linking MedDRA and WHO Drug Indication coding.
© Copyright 2008 ADaM Validation and Integrity Checks Wednesday 12 th October 2011 Louise Cross ICON Clinical Research, Marlow, UK.
How to go from an SDTM Finding Domain to an ADaM-Compliant Basic Data Structure Analysis Dataset: An Example Qian Wang, MSD, Brussels, Belgium Carl Herremans,
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
CONFIDENTIAL The Ultimate Integration Challenge Jennifer Chin, Covance Hester Schoeman, Covance PhUSE Conference Berlin 2010 Paper DH06.
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
Optimizing Data Standards Working Group Meeting Summary
Preventing Wide and Heavy ADs Dirk Van Krunckelsven Phuse 2011, Brighton ADaM on a Diet.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
Biostatistics Case Studies Peter D. Christenson Biostatistician Session 3: Missing Data in Longitudinal Studies.
UC3: Complications Related to Unscheduled performed instead scheduled (TK) Raw visit numberVISITNUMLBDYLBDTC 2missing VISITVISITNUMSVDYSVDTCSVUPDES.
1. © CDISC 2014 Presented by Angelo Tinazzi, Cytel Inc, Geneva, Switzerland Presented at 2014 CDISC Europe Interchange, Paris Adapted for CDISC UK Network.
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.
Efficacy and safety of the proprotein convertase subtilisin/kexin type 9 inhibitor alirocumab among high cardiovascular risk patients on maximally tolerated.
Clinical database management: From raw data through study tabulations to analysis datasets Thank you for your kind introduction, and the opportunity to.
Data Standards for Pharmacometric Analysis Data Sets
Principles and Practicalities in Building ADaM Datasets
« Lost » in Traceability, from SDTM to ADaM …
De-Identification Standards for CDISC Data Models
A Systematic Review of ADaM IG Interpretation
Traceability Look for the source of your analysis results
Challenges and Strategies in Pharmacometric Programming
Flowchart of participant screening, enrollment, withdrawal, and protocol completion Asterisk indicates those with partial or missing data included in analyses.
Some Considerations When Designing ADaM Datasets Italian CDISC UN Day - Milan 27th October 2017 Antonio Valenti Principal Statistical Programmer CROS.
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.
Why use CDISC for trials not submitted to regulators?
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
Quality Control of SDTM Domain Mappings from Electronic Case Report Forms Noga Meiry Lewin, MS Senior SAS Programmer The Emmes Corporation Target: 38th.
It’s about Time! (to Event)
Common Problems in Writing Statistical Plan of Clinical Trial Protocol
Fabienne NOEL CDISC – 2013, December 18th
Bring the Vampire out of the Shadows: Understanding the RETAIN and COUNT functions in SAS® Steve Black.
Visualizing Subject Level Data in Clinical Trial Data
Creating BDS DERIVED Parameters for a Subject-level Frequency Summary Table? Then this macro can be useful.
An FDA Statistician’s Perspective on Standardized Data Sets
What Do We Know About Estimators for the Treatment Policy Estimand
Handling Missing Not at Random Data for Safety Endpoint in the Multiple Dose Titration Clinical Pharmacology Trial Li Fan*, Tian Zhao, Patrick Larson Merck.
Record your QUESTIONS as your read.
Analysis Data Model (ADaM)
PhilaSUG Spring Meeting June 05, 2019
ADME Study PK SDTM/ADAM And Graph
Presentation transcript:

A Taste of ADaM Presented by: Peng/Zik Liu MSD (Shanghai) Pharma Co. Beilei Xu Accenture Changhong Shi Merck Sharp & Dohme Corp. Presented by: Peng/Zik Liu MSD (Shanghai) Pharma Co.

Outline Background ADaM Setup Steps for Lipid ADaM data Summary

Background CDISC - Clinical Data Interchange Standards Consortium SDTM - Study Data Tabulation Model Standard for interchange of collected data ADaM - Analysis Data Model Standard for analysis data http://www.cdisc.org/adam

ADaM Standard Data Structure ADSL: Subject level analysis data one record per subject subject-level population flags, planned and actual treatment variables, demographic information, randomization factors, sub-grouping variables, and important dates BDS: Basic Data Structure Long and skinny structure: contains one or more records per subject, per analysis parameter, and per analysis time point “One-proc” away readiness for analysis Traceability

BDS Variables A central set of variables: Other variables: The analysis parameter: e.g., PARAM The value being analyzed: e.g., AVAL and AVALC Other variables: Provide more information about the value being analyzed (e.g., the subject identification) Describe and trace the derivation of the variable (e.g., DTYPE) Enable the analyses (e.g., treatment variables, covariates)

Implementation Consideration Number of ADaM datasets needed Derivation of analysis endpoints, analysis windows, analysis values, and imputation of missing values Setup of analysis flags and population flags

Lipid Analysis Data - ADLP Lipid endpoints: LDL - C HDL - C LDL/HDL ratio Analysis time points: SCREENING BASELINE WEEK 2 WEEK 4 Analysis population- Full Analysis Set

Lipid Analysis Data - ADLP Subject identifiers: STUDYID, USUBJID, SUBJID, and SITEID Treatment variables: TRTP, TRPA, TRTPN, and TRTAN Analysis parameter variables: PARAM, PARAMCD, PARAMN, and PARAMTYP Analysis timing variables: ADT and ADY The analysis value variables: AVAL, BASE, and CHG The analysis flag variable - ANL01FL The parameter population flag - FASPFL The traceability variables: SRCDOM, SRCVAR, and SRCSEQ

ADLP Setup Steps Obtain Variables from Source SDTM LB Domain Derive New Analysis Endpoints (PARAMTYP) Handle Negatives (or under detection) and Multiple Records on the Same Date (DTYPE) Set Analysis Flag Variables (ANLzzFL) Compute Change, Percent Change from Baseline (BASE, CHG, PCHG) Set Population Flag Variables

Obtain Data from SDTM LB Domain USUBJID LBSEQ LBTESTCD LBTEST LBSTRESN LBSTRESU VISIT VISITNUM LBDTC LBDY 1A-4_02 1001 LDL LDL Cholesterol 2.36 mmol/L SCRNING 1 2008-09-15 -16 1002 2.8 DAY 1 2 2008-10-01 1003 2.73 DAY 15 3 2008-10-15 15 1004 2.68 1005 2.74 DAY 28 4 2008-10-28 28 ADLP: USUBJID PARAM AWRANGE AVISIT AVISITN ADT ADY AVAL SRCDOM SRCVAR SRCSEQ 1A-4_02 LDL-C (mmol/L) < Day 1 SCREENING -99 9/15/2008 -16 2.36 LB LBSTRESN 1001 Day 1 Baseline 10/1/2008 1 2.8 1002 2-21 Days Week 2 2 10/15/2008 15 2.73 1003 2.68 1004 >= 22 Days Week 4 4 10/28/2008 28 2.74 1005 10

Derive New Analysis Endpoint LDL/HDL Ratio ADLP: USUBJID PARAM AWRANGE AVISIT AVISITN ADT ADY AVAL PARAMTYP 1A-4_02 LDL/HDL ratio < Day 1 SCREENING -99 9/15/2008 -16 2.226 DERIVED Day 1 Baseline 10/1/2008 1 2.593 2-21 Days Week 2 2 10/15/2008 15 2.438 2.459 >= 22 Days Week 4 4 10/28/2008 28 2.383 11

Handle Multiple Records on the Same Date USUBJID PARAM AWRANGE AVISIT AVISITN ADT AVAL SRCDOM SRCVAR SRCSEQ DTYPE 1A-4_02 LDL-C (mmol/L) < Day 1 SCREENING -99 9/15/2008 2.36 LB LBSTRESN 1001   Day 1 Baseline 10/1/2008 2.8 1002 2-21 Days Week 2 2 10/15/2008 2.73 1003 2.68 1004 2.71 AVERAGE >= 22 Days Week 4 4 10/28/2008 2.74 1005 12

Set Analysis Flag Variables (ANLzzFL) USUBJID PARAM AWRANGE AVISIT AVISITN ADT ADY AVAL DTYPE ANL01FL 1A-4_02 LDL-C (mmol/L) < Day 1 SCREENING -99 9/15/2008 -16 2.36   Y Day 1 Baseline 10/1/2008 1 2.8 2-21 Days Week 2 2 10/15/2008 15 2.73 2.68 2.71 AVERAGE >= 22 Days Week 4 4 10/28/2008 28 2.74

Set Population Flag Variables USUBJID PARAM AWRANGE AVISIT AVISITN AVAL BASE CHG DTYPE ANL01FL FASPFL 1A-4_02 LDL-C (mmol/L) < Day 1 SCREENING -99 2.36 2.8   Y Day 1 Baseline 2-21 Days Week 2 2 2.73 -0.07 2.68 -0.12 2.71 -0.09 AVERAGE >= 22 Days Week 4 4 2.74 -0.06

One-Proc Away proc mixed data=adlp; where paramcd=‘LDL’ and anl01fl=‘Y’ and faspfl=‘Y’ and avisitn in (0,2,4); class subjid avisit trta; model chg=avisit trta trta*avisit; repeated avisit/subject=subjid type=un; run;

Summary The setup steps shown above enable: the creation of the ADaM Basic Data Structure (BDS) traceability between analysis data and source data "one-proc" away readiness for analysis Further development can be made to standardize the programs for analysis data setup