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,

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)
OpenCDISC Rules for Discussion
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
SUPPQUAL – Where’s My Mommy? Sandra VanPelt Nguyen Midwest CDISC Users Group May 2012.
Data Dictionary What does “Backordered item” mean? What does “New Customer info.” contain? How does the “account receivable report” look like?
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.
CDISC (CDASH/SDTM) integration into OC/RDC
Finalized FDA Requirements for Standardized Data
Model X-Ray Image Data into ADaM BDS Structure
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 1 PhUSE 2010 Berlin * Accessing the metadata from the define.xml using XSLT transformations.
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
Updates on CDISC Standards Validation
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.
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,
PhUSE SDE, 28-May A SAS based Solution for define.xml Monika Kawohl Statistical Programming Accovion.
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.
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 2 Octagon Research Solutions, Inc. Leading the Electronic Transformation of Clinical R&D ©
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.
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.
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.
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
1 SAS 1-liners SAS Coding Efficiencies. 2 Overview Less is more Always aim for robust, reusable and efficient code Coding efficiency versus processing.
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
1. © CDISC 2014 SDS ELT Rules Team Update Stetson Line 08 Dec
Preventing Wide and Heavy ADs Dirk Van Krunckelsven Phuse 2011, Brighton ADaM on a Diet.
The Use of Metadata in Creating, Transforming and Transporting Clinical Data Gregory Steffens Director, Data Management and SAS Programming ICON Development.
FORMAT statements can be used to change the look of your output –if FORMAT is in the DATA step, then the formats are permanent and stored with the dataset.
For a programming more efficient Claude Guyot PhUSE 2010 – Berlin Paper CS05.
Tracing Data Elements through a Standard Data Flow Alistair Dootson Dootsonic Ltd, Manchester, UK 16 February 2016Copyright Dootsonic Ltd 2011.
1 Much ADaM about Nothing – a PROC Away in a Day EndriPhUSE Conference Rowland HaleBrighton (UK), 9th - 12th October 2011.
A leading global CRO 1 Effective Use of the RETAIN Statement in Programming Clinical Trial Mingxia Chen Biostatistician Beijing, China.
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
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.
MindMajix SAS Clinical TrainingSAS Clinical Training.
Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism CDISC (CDASH/SDTM) integration into OC/RDC Peter Van Reusel.
Most Common Issues in Define.xml files
Principles and Practicalities in Building ADaM Datasets
A Systematic Review of ADaM IG Interpretation
Traceability Look for the source of your analysis results
Some Considerations When Designing ADaM Datasets Italian CDISC UN Day - Milan 27th October 2017 Antonio Valenti Principal Statistical Programmer CROS.
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Creating ADaM Friendly Analysis Data from SDTM Using Meta-data by Erik Brun & Rico Schiller (CD ) H. Lundbeck A/S 13-Oct
Some ways to encourage quality programming
Traceability between SDTM and ADaM converted analysis datasets
Patterns emerging from chaos
A SAS macro to check SDTM domains against controlled terminology
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
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.
Adding Like Terms Guided Notes
Record your QUESTIONS as your read.
Analysis Data Model (ADaM)
Presentation transcript:

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, MSD, Brussels, Belgium PhUSE 2010, Berlin

PhUSE Berlin 2 ADaM versus SDTM ADaM datasets do use redundancy for easy analysis – common variables may be found across all analysis datasets (e.g., population flags, subject identifiers, etc.); ADaM datasets have a greater number of numeric variables (e.g., SAS formatted dates, numeric representation of a character grouping variable from SDTM); ADaM datasets may combine variables from multiple SDTM domains; ADaM datasets are named AD.

PhUSE Berlin 3 ADaM-compliant Basic Data Structure (BDS) A BDS dataset contains one or more records per subject, per analysis parameter and per analysis time point. It describes the data being analyzed and also includes variables to support the analysis (e.g. covariates) as well as information to facilitate traceability.

PhUSE Berlin 4 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 5 STEP 1: Preparing for ADAM Precursor by Adding SUPPQUAL to SDTM LB SUPPQUAL LB + SUPPQUAL (where RDOMAIN=‘LB’)

PhUSE Berlin 6 STEP 1: Preparing for ADAM Precursor by adding SUPPQUAL to SDTM USUBJIDSEXLBSEQLBTESTCDLBORRES LBFAST 0002_0001M1NA0.1Y STUDYIDRDOMAINUSUBJIDIDVARIDVARVARLQNAMQVAL 0002LB 0002_0001 LBSEQ1 LBFASTY USUBJIDSEXLBSEQLBTESTCDLBORRES 0002_0001M1NA0.1 +

PhUSE Berlin 7 STEP 1: Preparing for ADAM Precursor by Adding SUPPQUAL to SDTM proc transpose data=supplb out=supplb2 (rename=(idvarval=lbseq)); by usubjid idvarval; var qval; id qnam; idlabel qlabel; run; %addsuppqual(input_libary =, input_dataset_suppqual =, input_dataset_define =, output_library = );

PhUSE Berlin 8 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 9 STEP 2: Converting ISO8601 Date/Time --DTC T13:14:17

PhUSE Berlin 10 STEP 2: Converting ISO8601 Date/Time If not missing ADT and ATM populate ADTM

PhUSE Berlin 11 STEP 2: Converting ISO8601 Date/Time --DTCADTADTFATMATMFADTM T13:14:1715Dec200313:14:1715Dec2003:13:14: T13:1415Dec200313:14:00S15Dec2003:13:14: T1315Dec200313:00:00M15Dec2003:13:00: Dec Dec2003D Jul2003M %convert2date(input_dataset=, output_dataset= );

PhUSE Berlin 12 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 13 STEP 3: Creating Analysis Relative Day ADY = LBDT - ADSL. TRTSDT + (LBDT > ADSL.TRTSDT)

PhUSE Berlin 14 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 15 SDTM LB LBTESTCDLBTESTLBSTRESNLBSTRESU NASodium139mmol/L KPotassium3.5mmol/L ADaM ADLB PARAMCDPARAMAVAL NASodium (mmol/L)139 KPotassium (mmol/L)3.5 STEP 4: Creating Key Analysis Parameter Variables PARAM(CD), AVAL

PhUSE Berlin 16 STEP 4: Creating Key Analysis Parameter Variables PARAM(CD), AVAL SDTM LB LBDYLBTESTCDLBTESTLBSTRESNLBSTRESU 1NASodium139mmol/L 1NASodium145mmol/L ADaM ADLB ADYPARAMCDPARAMAVALDTYPE ANL01FL 1 NASodium (mmol/L)139 1 NASodium (mmol/L)145 1 NASodium (mmol/L)142 AVERAGEY

PhUSE Berlin 17 STEP 4: Creating Key Analysis Parameter Variables PARAM(CD), AVAL %finding(input_dataset=, domain=, summaryfunction=AVERAGE, output_dataset= );

PhUSE Berlin 18 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 19 Time Point (Target Day) Time window in Days Baseline (1)-70 to 7 Treatment 1 (45)8 to 90 Treatment 2 (135)91to Time Baseline Treatment 1Treatment 2 STEP 5: ADDING TIME WINDOWS

PhUSE Berlin 20 STEP 5: ADDING TIME WINDOWS Start dayStop dayTargetAVISITAVISITNBaseline -7071Baseline0Y 89045Treatment Treatment 22 ADYPARAMCDAVALAVISITAVISITNAWTARGETAWRANGEABLFLANL02FL -18NA141Baseline01-70 to 7 1NA140Baseline01-70 to 7YY 14NA145Treatment to 90 46NA149Treatment to 90Y

PhUSE Berlin 21 6 Basic Steps Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline

PhUSE Berlin 22 Step 6: Deriving Change From Baseline ADYPARAMCDAVALAVISITAVISITNABLFLBASECHG -18NA141Baseline NA140Baseline0Y NA145Treatment NA149Treatment %change(input_dataset=, input_timewindow_dataset=, output_dataset= );

PhUSE Berlin 23 Conclusion Step 1 Prepare ADaM Precursor Step 2 Convert ISO8601 Dates Step 3 Create Analysis Relative Day Step 4 Create Key Analysis Variables Step 5 Add Time Windows Step 6 Derive Change from Baseline 6 Steps have been described to transform a SDTM finding dataset into an ADaM-compliant BDS analysis dataset.