Step Up Your ADaM Compliance Game Ramesh Ayyappath & Graham Oakley

Similar documents
Out-of-the-box %definexml

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

From SDTM to displays, through ADaM & Analyses Results Metadata, a flight on board METADATA Airlines

PhUSE US Connect 2019

Streamline SDTM Development and QC

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

Improving CDISC SDTM Data Quality & Compliance Right from the Beginning

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

Optimization of the traceability when applying an ADaM Parallel Conversion Method

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

ADaM Compliance Starts with ADaM Specifications

Lex Jansen Octagon Research Solutions, Inc.

esubmission - Are you really Compliant?

An Alternate Way to Create the Standard SDTM Domains

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

Experience of electronic data submission via Gateway to PMDA

Legacy to SDTM Conversion Workshop: Tools and Techniques

Why organizations need MDR system to manage clinical metadata?

PharmaSUG Paper AD03

PhUSE EU Connect 2018 SI05. Define ing the Future. Nicola Perry and Johan Schoeman

Dataset-XML - A New CDISC Standard

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

SDTM-ETL TM. New features in version 1.6. Author: Jozef Aerts XML4Pharma July SDTM-ETL TM : New features in v.1.6

How to write ADaM specifications like a ninja.

TS04. Running OpenCDISC from SAS. Mark Crangle

Introduction to ADaM and What s new in ADaM

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

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

PharmaSUG Paper PO22

Data Science Services Dirk Engfer Page 1 of 5

Introduction to Define.xml

PharmaSUG Paper DS16

CDISC SDTM and ADaM Real World Issues

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

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

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

Common Programming Errors in CDISC Data

A SDTM Legacy Data Conversion

Best Practices for E2E DB build process and Efficiency on CDASH to SDTM data Tao Yang, FMD K&L, Nanjing, China

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

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

How to Automate Validation with Pinnacle 21 Command Line Interface and SAS

Automation of SDTM Programming in Oncology Disease Response Domain Yiwen Wang, Yu Cheng, Ju Chen Eli Lilly and Company, China

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

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

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

An Efficient Solution to Efficacy ADaM Design and Implementation

CBER STUDY DATA STANDARDS UPDATE

Revision of Technical Conformance Guide on Electronic Study Data Submissions

PharmaSUG Paper CC02

Advantages of a real end-to-end approach with CDISC standards

Adding, editing and managing links to external documents in define.xml

Submission-Ready Define.xml Files Using SAS Clinical Data Integration Melissa R. Martinez, SAS Institute, Cary, NC USA

Material covered in the Dec 2014 FDA Binding Guidances

PMDA Valida+on Rules. Preparing for your next submission to Japanese Pharmaceu6cals and Medical Devices Agency. Max Kanevsky December 10, 2015

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

How a Metadata Repository enables dynamism and automation in SDTM-like dataset generation

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

SAS offers technology to facilitate working with CDISC standards : the metadata perspective.

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

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

How to validate clinical data more efficiently with SAS Clinical Standards Toolkit

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

Study Data Reviewer s Guide. FDA/PhUSE Project Summary

SAS Clinical Data Integration 2.4

PhUSE Paper SD09. "Overnight" Conversion to SDTM Datasets Ready for SDTM Submission Niels Mathiesen, mathiesen & mathiesen, Basel, Switzerland

Lex Jansen Octagon Research Solutions, Inc.

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

SDTM Attribute Checking Tool Ellen Xiao, Merck & Co., Inc., Rahway, NJ

Examining Rescue Studies

Clinical Metadata A complete metadata and project management solu6on. October 2017 Andrew Ndikom and Liang Wang

CDISC Migra+on. PhUSE 2010 Berlin. 47 of the top 50 biopharmaceu+cal firms use Cytel sofware to design, simulate and analyze their clinical studies.

Customizing SAS Data Integration Studio to Generate CDISC Compliant SDTM 3.1 Domains

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

ADaM and traceability: Chiesi experience

Considerations on creation of SDTM datasets for extended studies

Taming the SHREW. SDTM Heuristic Research and Evaluation Workshop

Metadata and ADaM.

SDTM-ETL 4.0 Preview of New Features

Managing CDISC version changes: how & when to implement? Presented by Lauren Shinaberry, Project Manager Business & Decision Life Sciences

Conversion of Company Standard Trial Data to SDTM

SAS Clinical Data Integration 2.6

One Project, Two Teams: The Unblind Leading the Blind

Standards Driven Innovation

CDISC Standards End-to-End: Enabling QbD in Data Management Sam Hume

SAS Online Training: Course contents: Agenda:

SAS Training BASE SAS CONCEPTS BASE SAS:

Traceability Look for the source of your analysis results

CDISC Variable Mapping and Control Terminology Implementation Made Easy

SAS Clinical Data Integration Server 2.1

OpenCDISC Validator 1.4 What s New?

Harnessing the Web to Streamline Statistical Programming Processes

PhUSE Protocol Representation: The Forgotten CDISC Model

Data Standardisation, Clinical Data Warehouse and SAS Standard Programs

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

PharmaSUG. companies. This paper. will cover how. processes, a fairly linear. before moving. be carried out. Lifecycle. established.

Patricia Guldin, Merck & Co., Inc., Kenilworth, NJ USA

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

Standards Metadata Management (System)

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

Transcription:

Step Up Your ADaM Compliance Game Ramesh Ayyappath & Graham Oakley Accountability & Delivery Collaboration Partnership Integrity

Agenda v Regulatory Requirement v Current Situation v iace-toolbox v 3 Step Process v Macros v Types of Issues v Assumptions & Limitations v Benefits

Introduction Regulatory Requirement: q Required standards for data submissions to FDA (US) and PMDA (Japan). q Timely and efficient review as the reviewers could utilize standardized tools. q Fewer questions and faster approval.

Current Situation q Compliance check tools require datasets as an input and therefore checked at later stage. q Rework resulting in timeline and cost implication. q Certain validation checks not covered by P21C (V2.2.0).

iace (ICON ADaM Capabilities and Expertise) Toolbox

3 Step Process In-house macro (specs2xpt) converts ADaM dataset specifications to empty SAS datasets and xpt files The xpt files are subjected to Pinnacle 21 Validator (Community V2.2.0) checks. In-house ADaM compliance check macro (based on ADaM Validation Checks v1.3) is run on the empty SAS datasets generated by specs2xpt.

Process ADaM Compliance Checks (Start) Populated ADaM Datasets (Input) Populated ADaM XPT Files (Input) - Produced from ADaM Datasets No Run ADaM Other Checks Macro (Assumes Macro SDTM (Assumes datasets SDTM datasets available) available) Run P21 Checks (Assumes SDTM xpt files available) Report Clean? No Explain in ADRG/report if issues/ warnings cannot be fixed. ADaM Other ADaM Other Checks Report Checks Report Created Created (Output) (Output) P21 Report Created (Output) Report Clean? No Yes ADaM Compliance Checks Complete (End)

SPECS2XPT and ADaM Compliance Checks (Start) ADaM Specifications (input) Run specs2xpt macro No Yes Successful run? SAS Dataset Shells Created (Output) SAS XPT files Created (Output) Yes Run ADaM Other Checks macro (Assumes SDTM datasets available) Run P21 Checks (Assumes SDTM xpt files available) ADaM Other Checks Report Created (output) P21 Report Created (output) Reports Clean? No Fix Issues? No SPECS2XPT and ADaM Compliance Checks Complete (end) Explain in ADRG/report if issues/warnings cannot be fixed.

Macros SPECS2XPT q Work with ICON ADaM Specs template. q Structural checks before creating output files. Input q ADaM Specs XL file, including metadata sheet. Output q Empty datasets and XPT files. Errors and Warnings printed in log if q Metadata sheet and ADaM specs not in sync wrt to dataset name. q Variable attributes not as expected or missing. 8

Macros ADaM Compliance Check Macro q Used with empty or populated datasets. Input q Analysis datasets following ADaM standards. Output q Temporary work dataset and a report showing status. 9

Types of Issues q Many of these findings are not easily identifiable by manual checks. q ICON s in-house macros identify potential structural issues in specs early on. Missing metadata Incorrect variable data type/format Inconsistency in attributes Variable name and label mismatches Variables labels or names over allowed lengths Missing required variables

Assumptions & Limitations SPECS2XPT q Assumes ICON ADaM Specs template as input. ADaM Compliance Check Macro q Programmed utilizing the SASHELP tables VTABLE and VCOLUMN in conjunction with ADaM datasets. q Checks are based on ADaM Validation Checks v1.3, as released by CDISC. q Will need to be updated when CDISC releases a new version of Validation Checks depending on whether or not all checks in that version will be covered by Pinnacle 21 Validator (Community).

Benefits q Reduced reliance on manual compliance checks. q Ability to check metadata compliance prior to sending ADaM specification for internal or external review. q Reduction in time in the reporting process by capturing metadata issues as early as possible instead of later in the study. q Collection of metrics to identify common findings across studies.

Thank You iconplc.com 2017 ICON. All rights reserved. Internal use only.