PharmaSUG Paper PO03

Similar documents
PharmaSUG Paper PO10

PharmaSUG Paper PO22

PharmaSUG Paper PO21

PharmaSUG Paper SP08

How to write ADaM specifications like a ninja.

The Benefits of Traceability Beyond Just From SDTM to ADaM in CDISC Standards Maggie Ci Jiang, Teva Pharmaceuticals, Great Valley, PA

Applying ADaM Principles in Developing a Response Analysis Dataset

An Efficient Solution to Efficacy ADaM Design and Implementation

Creating an ADaM Data Set for Correlation Analyses

START CONVERTING FROM TEXT DATE/TIME VALUES

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

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

PharmaSUG Paper SP09

Pharmaceuticals, Health Care, and Life Sciences. An Approach to CDISC SDTM Implementation for Clinical Trials Data

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

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

Deriving Rows in CDISC ADaM BDS Datasets

Creating output datasets using SQL (Structured Query Language) only Andrii Stakhniv, Experis Clinical, Ukraine

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

PharmaSUG Paper DS24

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

Traceability Look for the source of your analysis results

Revision of Technical Conformance Guide on Electronic Study Data Submissions

Tips on Creating a Strategy for a CDISC Submission Rajkumar Sharma, Nektar Therapeutics, San Francisco, CA

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

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

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

Introduction to ADaM and What s new in ADaM

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

How to review a CRF - A statistical programmer perspective

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

A Taste of SDTM in Real Time

PharmaSUG Paper AD03

Customer oriented CDISC implementation

Zambia Medicines Regulatory Authority APPLICATION FOR MARKETING AUTHORISATION OF A MEDICINE FOR HUMAN USE

One Project, Two Teams: The Unblind Leading the Blind

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

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

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

Paper FC02. SDTM, Plus or Minus. Barry R. Cohen, Octagon Research Solutions, Wayne, PA

esubmission - Are you really Compliant?

Why organizations need MDR system to manage clinical metadata?

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

PharmaSUG 2014 PO16. Category CDASH SDTM ADaM. Submission in standardized tabular form. Structure Flexible Rigid Flexible * No Yes Yes

An Alternate Way to Create the Standard SDTM Domains

PharmaSUG China Paper 70

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

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

Data Warehousing ABSTRACT

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

ADaM Compliance Starts with ADaM Specifications

CDISC ECG EXTENSION MODEL FINAL DRAFT RELEASE VERSION 1-0-0

SECURE DATA OFFICE: AN INDEPENDENT TEAM THAT CAN COME TO THE RESCUE IN BLINDED TRIALS

PharmaSUG Paper CD16

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

Interactive Programming Using Task in SAS Studio

Lex Jansen Octagon Research Solutions, Inc.

FDA XML Data Format Requirements Specification

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

Material covered in the Dec 2014 FDA Binding Guidances

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

Preparing the Office of Scientific Investigations (OSI) Requests for Submissions to FDA

An Efficient Tool for Clinical Data Check

A Picture is worth 3000 words!! 3D Visualization using SAS Suhas R. Sanjee, Novartis Institutes for Biomedical Research, INC.

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

PhUSE US Connect 2019

How to clean up dirty data in Patient reported outcomes

Codelists Here, Versions There, Controlled Terminology Everywhere Shelley Dunn, Regulus Therapeutics, San Diego, California

Standardizing FDA Data to Improve Success in Pediatric Drug Development

Reducing SAS Dataset Merges with Data Driven Formats

Clinical Metadata Metadata management with a CDISC mindset

SAS Clinical Data Integration 2.4

Study Data Reviewer s Guide

Once the data warehouse is assembled, its customers will likely

CDISC Variable Mapping and Control Terminology Implementation Made Easy

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

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

Clarifications About ADaM Implementation Provided in ADaMIG Version 1.1

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

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

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

Study Composer: a CRF design tool enabling the re-use of CDISC define.xml metadata

Reproducibly Random Values William Garner, Gilead Sciences, Inc., Foster City, CA Ting Bai, Gilead Sciences, Inc., Foster City, CA

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

PharmaSUG2014 Paper DS09

Data Annotations in Clinical Trial Graphs Sudhir Singh, i3 Statprobe, Cary, NC

Experience of electronic data submission via Gateway to PMDA

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

Creating Forest Plots Using SAS/GRAPH and the Annotate Facility

ADaM and traceability: Chiesi experience

PharmaSUG DS05

Pooling Clinical Data: Key points and Pitfalls. October 16, 2012 Phuse 2012 conference, Budapest Florence Buchheit

SAS Clinical Data Integration 2.6

Data Edit-checks Integration using ODS Tagset Niraj J. Pandya, Element Technologies Inc., NJ Vinodh Paida, Impressive Systems Inc.

Organizing Deliverables for Clinical Trials The Concept of Analyses and its Implementation in EXACT

Common Programming Errors in CDISC Data

ADaM Reviewer s Guide Interpretation and Implementation

Pharmaceuticals, Health Care, and Life Sciences

Creating a Patient Profile using CDISC SDTM Marc Desgrousilliers, Clinovo, Sunnyvale, CA Romain Miralles, Clinovo, Sunnyvale, CA

Managing your metadata efficiently - a structured way to organise and frontload your analysis and submission data

Transcription:

PharmaSUG 2012 - Paper PO03 Streamlining Regulatory Submission with CDISC/ADaM Standards for Nonstandard Pharmacokinetic/Pharmacodynamic Analysis Datasets Xiaopeng Li, Celerion Inc., Lincoln, NE (USA) Katrina Canonizado, Celerion Inc., Lincoln, NE (USA) Chun Feng, Celerion Inc., Lincoln, NE (USA) Nancy Wang, Celerion Inc., Lincoln, NE (USA) ABSTRACT Analysis Data Model (ADaM) which is encouraged by FDA in clinical trial data submission is designed to support analysis datasets. Non-Standard ADaM dataset for Pharmacokinetic (PK) and Pharmacodynamic (PD) analyses have not been clearly discussed. Based on Analysis Data Model v2.1, this paper shares the approaches of how to map non-standard PK/PD data to create ADaM datasets to support the analyses for Thorough QT studies, reproductive safety studies and studies with urine collections. The approaches make the ADaM datasets for these studies consistent with Analysis Data Model v2.1 and submission ready. Detailed mapping methods and examples of these ADaM datasets will be presented. INTRODUCTION Analysis Data Model (ADaM) from Clinical Data Interchange Standards Consortium (CDISC) is becoming more and more popular since FDA recommends ADaM as the analysis submission data sets in Study Data Specifications document. ADaM data sets are considered analysis ready, which means it includes all necessary variables needed to perform the statistical analysis of the data. Speeding turn-around time of Pharmacokinetic (PK) and Pharmacodynamic (PD) analyses is critical during the drug development process because it is always good to know a drug s availability as early as possible. STANDARD APPROACH TO ADAM PK/PD STUDY In CDISC Analysis Data Model v2.1, the information for PK/PD analysis data set is general. Based on the Basic Data Structure (BDS) specification in the ADaM guide, standard data structure for PK analysis can be generated. The Celerion standard process of creating an ADaM data set for PK analysis has been discussed 1. In this process, SDTM Pharmacokinetic Concentration (PC) data, SDTM Pharmacokinetic Parameter (PP) data, ADaM Pharmacokinetic Concentration (ADPC) data and ADaM Pharmacokinetic Parameters (ADPP) are created based on SDTM/ADaM structure data, clinical data, bioanalytical data and the analysis parameters calculated by scientists. Then, all the related listings, tables and figures can be generated based on ADPC and ADPP data sets. This process provides a consistent approach from clinical data sets to ADaM data sets for a Celerion standard plasma PK analysis, such as statistical analysis of PK parameters, statistical comparison of difference between treatments. However, some studies require more complex and more involved PK/PD analyses. This paper shares efficient approaches for building ADaM data sets for PK/PD analysis in the situations that go beyond the process discussed in the previous paper. ADAM DATA SET FOR THOROUGH QT STUDY BACKGROUND A thorough QT (TQT) study is expected in the early stages of clinical development for most drugs 2. Generally, the data for thorough QT analyses come from electrocardiogram (ECG) data set. In TQT studies, some tests are collected multiple times for a particular time point. To get an analysis data set, multiple observations at each time point should be properly mapped according to the analysis specified in the statistical analysis plan, thus the way to handle ADaM TQT data set for cardiac analysis (ADPD or customized ADaM parameter data set for TQT ADZP) are 1 Xie, Y., Chai, P., Kirby S., Wang N.. 2011. Pharmacokinetic Data Submission in the CDISC Environment. American Association of Pharmaceutical Scientists 2 International Conference on Harmonisation. Guidance for Industry E14 Clinical Evaluation of QT/QTc Interval Prolongation and Proarrhythmic Potential for Non-Antiarrhythmic Drugs. October 2005. Available at http://www.ich.org 1

different from the way to handle ADaM safety ECG data set (ADEG). Creating a separate ADaM data sets for TQT analysis from ECG data is suggested. An example of TQT data set for PD analysis is used to demonstrate the process. A SAMPLE LIST OF INFORMATION FOR ANALYSIS 1. Delta QT and delta QTc 2. Delta Summary (mean) Heart Rate 3. Delta Summary (mean) PR Rate 4. Delta Summary (mean) QRS Duration 5. Delta Summary (mean) RR Duration 6. Delta T-Wave Amplitude 7. Delta T-Wave Complexity HOW TO MAP To create an ADaM data set, there are two different approaches based on the aforementioned requirements. The first approach is used when parameters requested by analysis can be easily calculated, such as delta heart rate, delta pr rate and delta QT. In that case, all the analysis parameters needed can be generated while creating the ADaM data set. The process has two steps. First, create SDTM EG data set. Second, create ADaM ADPD data set based on SDTM EG data set. In this step, the relative information from SDTM EG data set should be selected first and then the calculations for analysis parameters will be performed. For example, to calculate the time-to-time matched change from baseline for QTcF values during ADPD creation. Another possible mapping approach suggested is similar to the Celerion standard process. In this case, some analysis parameters need to be calculated by a scientist. The process has five steps. First, all the ECG information from clinical collected in ECG data set is mapped to SDTM EG data set. Second, based on the information from SDTM EG data set, an ADaM data set (ADZC) is created for scientists to do the parameters calculation. The name ADZC is used to distinguish from the name ADPC used for ADaM pharmacokinetic concentration data set in the Celerion standard process. It is more appropriate to name the data set ADZC for TQT study since it is considered as a customized ADaM concentration data set. When preparing ADZC data set, different methods can be used for dealing with the multiple observations at the same time point. Depending on the protocol or Statistical Analysis Plan, mean, median, maximum and minimum could be calculated for the multiple observations to make the data analysis ready. Third, analysis parameters will be calculated by scientists based on ADZC data set. Fourth, based on the information of analysis parameters provided by scientists, create SDTM ZP data set. Fifth, ADZP, the customized ADaM parameter data set for TQT study, is created for further analysis usage. Display 1: ADPD for Thorough QT analysis Display (Only show part of data from dummy ADaM data set) 2

Special attention need to be paid to making sure ADEG and ADPD do not have overlapped information, because both analysis data sets ADEG and ADPD share information from SDTM EG data set. The overlapped information may cause confusion when end users review ADaM data sets and work on listings, tables and figures. Additionally, the overlapped information may cause queries during the submission review. ADAM DATA SET FOR REPRODUCTIVE SAFETY STUDY BACKGROUND Reproductive safety is a concern in certain drugs. It is usually collected through a different specimen such as semen. The analysis for this type of matrix is unique, thus the customized ADaM PK/PD data set should be created separately. A male reproductive safety study with semen samples is used as an example. A SAMPLE LIST OF INFORMATION FOR ANALYSIS 1. Gross Physical Characteristics 2. Neat Sample 3. Quantitative Microscopic Characteristics 4. Quantitative Morphology 5. Sample Collection Information HOW TO MAP Compared to the standard PK ADaM data sets, semen data do not quite fit into ADPC data set. Some parameters in semen data sets require averages or changes from baseline. Deriving parameters are not commonly done in a plasma concentration data sets. Additionally, semen analysis not only includes concentration information, but also includes other types of information, such as physical characteristics, thus it makes more sense to consider semen ADaM data set as a customized data. Accordingly, ADZS for semen data set name is suggested. To generate ADZS, there are two steps. First, starting from clinical semen data set, SDTM ZS data set is created. ZS data set is a customized SDTM data set which contains semen information in this study. Second, based on the protocol and statistical analysis plan, ADaM ADZS data set can be created. ADZS data set is similar to safety ADaM data set, such as ADEG data set, because some analysis of semen tests are required to calculate the change from baseline information which is often seen in safety ADaM data set, but not in ADPC and ADPP data sets. Furthermore, ADZS may include concentration information and volume information which is usually used in ADPC data set. All semen tests are implemented in the data set as parameters. All change from baseline information can be calculated as needed and the baselines need to be marked with baseline flags in ADaM ADZS data set. 3

Display 2: ADZS for Semen analysis (Only show part of data from dummy ADaM data set) Another possible mapping approach is when some parameters are needed to be calculated from semen concentration and volume information by scientists. In this case, ADSC (ADaM semen concentration data set) and ADSP (ADaM semen concentration parameter data set) will be created. First, create SDTM SC semen concentration data set which includes semen concentration bioanalysis data set information and the relevant clinical information. Second, create ADaM ADSC data set based on SDTM SC data set. SC stands for semen concentration. Similarly, ADSC is the name of analysis data set for semen concentration. ADSC contains information such as semen concentration, semen volume, total sperm count and total motile count. A scientist will use the ADSC data set to calculate the parameters needed. Generally, time intervals are used in semen clinical data set instead of individual time points. While programming ADSC, merging clinical data set with semen bioanalytical data is challenging. The reason is that clinical data usually has individual time point. Usually, using endpoint of an interval is one way for data merging. Third, when the semen parameters are calculated based on ADSC data set by a scientist, SDTM SP data set can be created. Finally, ADSP, analysis data set for semen parameters, can be created using the SDTM SP data set. SDTM Structure data set Clinical data sets ADaM Structure data set SDTM SC (Semen Concentration) data set ADSL ADaM ADSC data set Calculated by Pharmacokineticist ADaM Structure data set SDTM SP (Semen Parameters) data set ADaM ADSP data set Figure 1: Process to get ADaM ADSP data set for Semen analysis study ADAM DATA SET FOR URINE PHARMACOKINETIC ANALYSIS STUDY BACKGROUND Urine analysis includes Pharmacokinetics analysis and Pharmacodynamics analysis. The Urine Pharmacokinetic analysis is simple, but unique. A study with urine Pharmacokinetic analysis results is used as an example. A SAMPLE LIST OF INFORMATION FOR ANALYSIS 1. Urine volume 2. Urine sample collection interval (Start time and end time) 3. Rate of drug excretion 4. Cumulative amount of drug excreted in urine 5. Renal clearance (or other parameters to support main Pharmacokinetic analysis) 4

HOW TO MAP Different from Plasma Pharmacokinetics analysis, information needed for the ADaM urine Pharmacodynamics data set, such as volume, collection interval, derived rate of drug excretion, and cumulative drug excretion, is from the urine data set or can be calculated based on the urine data set. Based on the urine data set and urine concentration data set, SDTM UR data set can be created. According to analysis requirement, all the urine analysis parameters can be calculated. For example, rate of drug excretion is calculated by Cumulative amount of drug excreted in urine, which can be calculated by the concentration and the urine volume, during a certain time period divide by the duration of this time period. Then based on the SDTM UR data set and other PD information from other SDTM data set, the ADaM ADPD data set can be created. The urine analysis data set ADPD needs PD record level flags and population flags. Urine concentration, urine volume and the time interval could be included as a parameter in the ADPD data set for better understanding of the data set and for other analysis purpose. Adding flags for urine PD analysis is necessary, because urine analysis parameters may be handled separately from other PD parameters. Additionally, change from baseline information may be included as needed for the analysis. Display 3: ADPD for Urine PD analysis (Only show part of data from dummy ADaM data set) CONCLUSION In general, non-standard PK/PD analysis data can be prepared two ways. In the first situation when analysis parameters can be easily calculated by a programmer, then the programmer creates the analysis data set. In the second situation when the scientist is involved in calculating the parameters, two analysis data sets will be created. One is the analysis data set for concentration and the other is the analysis data set for parameters. Comparing with the Celerion standard ADaM PK approach, the approaches to ADaM data sets for Thorough QT study, reproductive safety study and Urine PD study are different and not detailed in the Analysis Data Model v2.1, but all of them can be successfully handled based on the similar definitions and the similar concepts. Additionally, based on these information and experience, other ADaM PK/PD approaches could be accomplished. REFERENCE Xie, Y., Chai, P., Kirby S., Wang N.. 2011. Pharmacokinetic Data Submission in the CDISC Environment. American Association of Pharmaceutical Scientists 5

Clinical Data Interchange Standards Consortium. Analysis Data Model v2.1. December 17th, 2009. Available at www.cdisc.org. Clinical Data Interchange Standards Consortium. CDISC SDTM Implementation Guide (Version 3.1.2). November 12th, 2008. Available at www.cdisc.org. Food and Drug Administration. Study Data Specifications. June 22 nd, 2011. Available at www.fda.gov. International Conference on Harmonisation. Guidance for Industry E14 Clinical Evaluation of QT/QTc Interval Prolongation and Proarrhythmic Potential for Non-Antiarrhythmic Drugs. October 2005. Available at http://www.ich.org. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the author at: Name: Xiaopeng Li Work Phone: 402-437-6260 E-mail: xiaopeng.li@celerion.com, xiaopeng.li@huskers.unl.edu Name: Katrina Canonizado Work Phone: 402-437-4160 E-mail: Katrina.Canonizado@celerion.com Name: Chun Feng Work Phone: E-mail: chun.feng@celerion.com Name: Nancy Wang Work Phone: E-mail: nancy.wang@celerion.com SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are trademarks of their respective companies. 6