Analysis Data Model (ADaM)

Slides:



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

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)
UC5:Assigning of Epoch after treatment discontinuation (NS)
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
The Importance of CDASH
Quick tour of CDISC’s ADaM standard
Gregory Steffens Associate Director, Programming Novartis Row – Level Metadata.
1 To Hypothesize or not Hypothesize Hypothesis: An expectation about the nature of things, derived from a theory.
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.
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.
Copyright © 2010, SAS Institute Inc. All rights reserved. Define.xml - Tips and Techniques for Creating CRT - DDS Julie Maddox Mark Lambrecht SAS Institute.
CDISC and how Stata can help us implement it
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
Principles and Practicalities in Building ADaM Datasets Cathy Barrows CDISC Users’ Group – May 25, 2012 Previously presented at: PhUSE Single Day Event.
A Taste of ADaM Presented by: Peng/Zik Liu MSD (Shanghai) Pharma Co.
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,
Qian Zhao, J&J Consumer Companies, Inc. Jun (John) Wang, J&J Consumer China Ltd Ruofei Hao, J&J Consumer Companies, Inc. PharmaSUG 2015 Paper #BB11.
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.
ODM-SDTM mapping Nicolas de Saint Jorre, XClinical June 20, 2008 French CDISC User Group Bagneux/Paris © CDISC & XClinical, 2008.
Overview and feed-back from CDISC European Interchange 2008 (From April 21 st to 25 th, COPENHAGEN) Groupe des Utilisateurs Francophones de CDISC Bagneux.
© 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,
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
CDASH – SDTM Mapping Kurt Hellstern
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.
 6. Use matrices to represent and manipulate data, e.g., to represent payoffs or incidence relationships related in a network.  7. Multiply matrices.
Practical Uses of the DOW Loop Richard Allen Peak Stat April 8, 2009.
Copyright © 2008 Pearson Prentice Hall. All rights reserved. 1 Create a one-variable data table What-if analysis enables you to see how changes in variables.
GRAPH Definition: A PICTORIAL REPRESENTATION OF INFORMATION RECORDED IN A DATA TABLE. USED TO SHOW A RELATIONSHIP BETWEEN TWO OR MORE FACTORS.
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
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 SEND data? Timothy Kropp FDA/CDER/OCS 1.
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.
CDISC SDS Oncology Domains: An Orientation to Aid Review & Feedback Barrie Nelson CDISC SDS Oncology Sub Team Lead
Mark Wheeldon, Formedix CDISC UK Network June 7, 2016 PRACTICAL IMPLEMENTATION OF DEFINE.XML.
GRAPHING RULES.
Principles and Practicalities in Building ADaM Datasets
A Systematic Review of ADaM IG Interpretation
Traceability Look for the source of your analysis results
Practical Implementation of Define.xml
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
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.
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
It’s about Time! (to Event)
A SAS macro to check SDTM domains against controlled terminology
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
Bring the Vampire out of the Shadows: Understanding the RETAIN and COUNT functions in SAS® Steve Black.
define.xml.v2 row-level metadata
Visualizing Subject Level Data in Clinical Trial Data
Automating and Validating Edits
Tutorial: Writing a Lab Report CHEM 1154
Creating BDS DERIVED Parameters for a Subject-level Frequency Summary Table? Then this macro can be useful.
ADDITIVE VS. MULTIPLICATIVE RELATIONSHIPS
An FDA Statistician’s Perspective on Standardized Data Sets
ESRM 250/CFR 520 Autumn 2009 Phil Hurvitz
PhilaSUG Spring Meeting June 05, 2019
Clinical responses to therapy from baseline to week 24 and end point with last observation carried forward (LOCF). Clinical responses to therapy from baseline.
Presentation transcript:

Analysis Data Model (ADaM) To change this title, go to Notes Master 7/29/2019 Analysis Data Model (ADaM) Case Studies Wouter van Wyk, 27 Sep 2012

Case Studies Specific to Basic Data Structure (BDS) With the increased adoption of the Analysis Data Model (ADaM) we are facing a shift in our approach to creating Analysis datasets, as we are encouraged to create records rather than adding additional variables as we might have in the past.  With these Case Studies I hope to address some of the questions around: Mapping multiple SDTM Variables to the same ADaM variable Creating derived records Multiple baseline definitions in the same ADaM domain

Mapping multiple SDTM Variables to the same ADaM variable Finding domains Eg. LB, VS, EG **ORRES, **STRESN Map to BDS AVAL, AVALC Multiple variables mapping to a single ADaM BDS Result variable Traceability SRCDOM, SRCSEQ, SRCVAR

Mapping multiple SDTM Variables to the same ADaM variable SDTM VS Dataset DOMAIN VSSEQ VISIT VSTEST VSORRES VSORRESU VSSTRESN VSSTRESU VS 1 SCR WEIGHT 158.7 LB 72 kg 2 V1 162 73.5 3 V2 161.8 73.4 4 V3 161.6 73.3 5 V4 162.3 73.6 6 V5 163 74

Mapping multiple SDTM Variables to the same ADaM variable SRCDOM SRCSEQ SRCVAR VISIT PARAM AVAL VS 1 VSORRES SCR WEIGHT (LB) 158.7 VSSTRESN WEIGHT (kg) 72 2 V1 162 73.5 3 V2 161.8 73.4 4 V3 161.6 73.3 5 V4 162.3 73.6 6 V5 163 74

Mapping multiple SDTM Variables to the same ADaM variable Traceability The property that enables the understanding of the data’s lineage and/or the relationship between an element and its predecessor(s). Where did the data come from? SRCDOM: Identifies the SDTM domain SRCSEQ: Identifies the record in the SDTM domain SCRVAR: Identifies the SDTM variable used to create AVAL/AVALC

Creating derived records Derived Parameters Test is not present in SDTM BMI, BSA, Calculated Creatinine Clearance QTcF, QTcB Derived Value Test is in SDTM, but the record is not Baseline, Endpoint Last Observation Carried Forward Traceability PARAMTYP vs. DTYPE

Creating derived records DTYPE LOCF Row USUBJID VISIT AVISIT ADY PARAM AVAL 1 1001 BASELINE -4 SUPINE SYSBP (mm Hg) 145 2 WEEK 1 3 130 WEEK 2 9 133 4 WEEK 3 20 125 5 1002 -1 6 7 22 135 8 1003 150 140

Creating derived records Row USUBJID VISIT AVISIT ADY PARAM AVAL DTYPE 1 1001 BASELINE -4 SUPINE SYSBP (mm Hg) 145 2 WEEK 1 3 130 WEEK 2 9 133 4 WEEK 3 20 125 5 1002 -1 6 7 LOCF 8 22 135 1003 150 10 140 11 12

Creating derived records Duplicate the needed record Populate DTYPE to indicate new record Use something descriptive like, LOCF, BASELINE, ENDPOINT, WCCF SCRDOM, SRCVAR, SRCSEQ populated as with original record Do not modify SDTM variables

Creating derived records PARAMTYP Row PARAM PARAMCD AVISIT AVISITN AVAL PARAMTYP 1 Weight (kg) WEIGHT SCR -4 99 2 RUN-IN -2 101 3 BASELINE 100 4 WEEK 24 24 94 5 WEEK 48 48 92 6 WEEK 52 52 95 7 Log10(Weight (kg)) L10WT 1.9956 DERIVED 8 2.0043 9 10 1.9731 11 1.9638 12 1.9777

Creating derived records Add records needed New value for PARAM and AVAL SRCSEQ, SRCDOM, SRCVAR will be NULL AVAL did not have SDTM as source SDTM variables can be populated as appropriate Do not modify SDTM variables

Multiple baseline definitions in the same ADaM domain Multiple definitions of Baseline Last value prior to very first dose of active Last value prior to Run-in Last value prior to Double-Blind Last value prior to Open Label In case there is more than one definition of baseline, new rows must be created for each additional alternative definition of baseline Some data redundancy is expected BASETYPE

Multiple baseline definitions in the same ADaM domain CDISC ADaM IG v1.0 Table 4.2.1.11 Row BASETYPE EPOCH AVISIT AVAL ABLFL BASE CHG 1 RUN-IN BASELINE 34.5 Y 2 DAY 10 11.6 -22.9 4 STABILIZATION DAY 15 13.1 -21.4 6 DOUBLE BLIND DAY 20 13.7 -20.8 7 DAY 25 19.7 -14.8 8 DAY 30 28.1 -6.4 10 OPEN LABEL DAY 35 28.4 -6.1 11 DAY 40 30.5 -4

Multiple baseline definitions in the same ADaM domain Row BASETYPE EPOCH AVISIT AVAL ABLFL BASE CHG 1 RUN-IN BASELINE 34.5 Y 2 DAY 10 11.6 -22.9 4 STABILIZATION DAY 15 13.1 -21.4 6 DOUBLE BLIND DAY 20 13.7 -20.8 7 DAY 25 19.7 -14.8 8 DAY 30 28.1 -6.4 10 OPEN LABEL DAY 35 28.4 -6.1 11 DAY 40 30.5 -4 12 13 14 14.4 15 14.7 16 16.8

Multiple baseline definitions in the same ADaM domain Duplicate all records affected Populate BASETYPE with something descriptive SRCVAR, SRCDOM, SRCSEQ will be populated as records can be traced back to SDTM Some data redundancy is expected

Summary SRCVAR, SRCDOM, SRCSEQ used when multiple SDTM variables map to AVAL E.g. **ORRES and **STRESN DTYPE used when new record is created but AVAL is not modified. E.g. LOCF PARAMTYP used when new parameter is created and value of AVAL can not be traced back to SDTM BASETYPE used when there are multiple baseline definitions that require additional records to be added

Questions?