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

Similar documents
Material covered in the Dec 2014 FDA Binding Guidances

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

Revision of Technical Conformance Guide on Electronic Study Data Submissions

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

Sandra Minjoe, Accenture Life Sciences John Brega, PharmaStat. PharmaSUG Single Day Event San Francisco Bay Area

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

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

Study Data Reviewer s Guide. FDA/PhUSE Project Summary

CBER STUDY DATA STANDARDS UPDATE

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

Introduction to ADaM and What s new in ADaM

STUDY DATA TECHNICAL CONFORMANCE GUIDE

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

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

Considerations on creation of SDTM datasets for extended studies

Standards Metadata Management (System)

Study Data Reviewer s Guide Completion Guideline

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

ectd TECHNICAL CONFORMANCE GUIDE

PharmaSUG Paper AD03

OpenCDISC Validator 1.4 What s New?

Experience of electronic data submission via Gateway to PMDA

esubmission - Are you really Compliant?

Preparing for FDA Mandated ectd Submissions

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

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

An Alternate Way to Create the Standard SDTM Domains

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

Lex Jansen Octagon Research Solutions, Inc.

Leveraging Study Data Reviewer s Guide (SDRG) in Building FDA s Confidence in Sponsor s Submitted Datasets

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

How to write ADaM specifications like a ninja.

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

Paper DS07 PhUSE 2017 CDISC Transport Standards - A Glance. Giri Balasubramanian, PRA Health Sciences Edwin Ponraj Thangarajan, PRA Health Sciences

ectd Next Major Version / Regulated Product Submission

Biotechnology Industry Organization 1225 Eye Street NW, Suite 400 Washington, DC 20006

Study Data Reviewer s Guide

The ectd Backbone Files Specification for Module 1. The ectd BACKBONE FILES SPECIFICATION FOR MODULE 1

Optimizing the Use of Data Standards CSS Summary

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

A CMC Reviewer s Perspective on the Quality Overall Summary. Arthur B. Shaw, Ph.D. FDA/CDER/ONDQA FDA DMF Expert June 15, 2010.

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

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

DIA 11234: CDER Data Standards Common Issues Document webinar questions

What is high quality study metadata?

Common Programming Errors in CDISC Data

Dataset-XML - A New CDISC Standard

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

FDA Study Data Technical Conformance Guide v4.2

Lex Jansen Octagon Research Solutions, Inc.

PharmaSUG Paper PO22

Step Up Your ADaM Compliance Game Ramesh Ayyappath & Graham Oakley

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

ectd Next Major Version Business Requirements (11-JUN-09)

Introduction to Define.xml

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

Optimization of the traceability when applying an ADaM Parallel Conversion Method

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

Legacy to SDTM Conversion Workshop: Tools and Techniques

Traceability Look for the source of your analysis results

A SDTM Legacy Data Conversion

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

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

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

CDISC SDTM and ADaM Real World Issues

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

CDASH MODEL 1.0 AND CDASHIG 2.0. Kathleen Mellars Special Thanks to the CDASH Model and CDASHIG Teams

From ODM to SDTM: An End-to-End Approach Applied to Phase I Clinical Trials

Generating Define.xml from Pinnacle 21 Community

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

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

ADaM Compliance Starts with ADaM Specifications

An Efficient Solution to Efficacy ADaM Design and Implementation

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

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

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

PharmaSUG Paper CD16

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

Examining Rescue Studies

PharmaSUG Paper DS16

US Food and Drug Administration. Revision History

About Domestic Implementation of the Electronic File Specifications to Be Included in the ICH Electronic Common Technical Document (ectd) v1.1.

CDISC Journal. Generating a cabig Patient Study Calendar from a Study Design in ODM with Study Design Model Extension. By Jozef Aerts.

Bay Area CDISC Network: PhUSE Working Group for Inspection Site Selection Data Standards

Steps to RPS Adoption

Business & Decision Life Sciences

Why organizations need MDR system to manage clinical metadata?

Data Science Services Dirk Engfer Page 1 of 5

Study Data Technical Conformance Guide (TCG)

Clinical Data Model and FDA Submissions

Aquila's Lunch And Learn CDISC The FDA Data Standard. Disclosure Note 1/17/2014. Host: Josh Boutwell, MBA, RAC CEO Aquila Solutions, LLC

Out-of-the-box %definexml

Standards Driven Innovation

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

CDISC Standards and the Semantic Web

The «CDISC Stupidario» (the CDISC Nonsense)

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

SAS Clinical Data Integration 2.6

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

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

Transcription:

Comparison of FDA and PMDA Requirements for Electronic Submission of Study Data Monika Kawohl Statistical Programming Accovion CDISC GSUG Meeting 15-Sep-2015 1

References FDA Website: Study Data Standards Resources Guidance for Industry: Providing Regulatory Submissions in Electronic Format Submissions Under Section 745A(a) of the FD&C Act. estudy Data Guidance PMDA Website: Advanced Review with Electronic Data Promotion Group Basic Principles on Electronic Submission of Study Data for New Drug Applications Notification on Practical Operations of Electronic Study Data Submissions Technical Conformance Guide Technical Conformance Guide Data Standards Catalog Data Standards Catalog CDISC GSUG Meeting 15-Sep-2015 2

Requirement Timelines FDA PMDA NDAs/ANDAs/ certain BLAs: Studies starting at/after 17-Dec-2016 Certain INDs: Studies starting at/after 17-Dec-2017 NDAs: Specific Studies submitted at/after 01-Apr-2020 Transition period: 01-Oct-2016 to 31-Mar-2020 CDISC GSUG Meeting 15-Sep-2015 3

PMDA: study types and submission formats of documents subject to electronic submission Source: Question and Answer Guide Regarding Notification on Practical Operations of Electronic Study Data Submissions CDISC GSUG Meeting 15-Sep-2015 4

Required CDISC Standards FDA PMDA SEND SDTM SDTM ADaM ADaM Define-XML Define-XML Analysis Results Metadata (ARM for Define-XML) CDISC GSUG Meeting 15-Sep-2015 5

Supplemental Data Submission Documents FDA PMDA Study Data Standardization Plan SDRG SDRG ADRG ADRG Programs Programs CDISC GSUG Meeting 15-Sep-2015 6

Other Selected Differences of Interest Topic FDA PMDA Dataset file size limit Standardized Units 1 GB 5 GB (no rules for splitting datasets) CDER and CBER recognize that SI units are the worldwide standard and international trials regularly measure and report lab tests using SI units. In the absence of a holistic transition within the U.S. healthcare community to SI units, conversion of certain lab test results to U.S. conventional units may be a necessary interim step toward a transition to full SI unit reporting. The use of SI units is recommended. If data were collected in units that are commonly used in guidelines where conversion of the data to those in SI units is possible, separately store the converted data in SI units in the SDTM dataset as data in the standard units and submit them. The conventional units may be used in application documents. The ADaM dataset must include the units used in application documents. Valid special characters in file names Non-supported Standard Versions Historically: - Per ectd validation criteria V3.1: -, _ Waiver possible _ exclusively Conversion necessary CDISC GSUG Meeting 15-Sep-2015 7

PMDA Data Standards Catalog In general, less entries than in FDA s catalog No Date Requirement Begins/Ends CDISC GSUG Meeting 15-Sep-2015 8

PMDA Option: Verbatim Terms in Japanese Language Primary reference for review: English datasets When data collected as free text should not/cannot be translated to English without loss of information, proceed as illustrated below: AE in folder sdtm AE in folder sdtm_j CDISC GSUG Meeting 15-Sep-2015 9

Topics Specific to PMDA Technical Conformance Guide Submission process technical details System requirements necessary for submission of electronic study data Method and basic flow of the submission of electronic study data Relationship between electronic study data and ectd Electronic study data on phase I and clinical pharmacology study results and clinical pharmacology analyses Specific deliverables to be stored in folder cp Respective guidance from FDA is stored in a set of different other documents CDISC GSUG Meeting 15-Sep-2015 10

Summary Overall, FDA and PMDA requirements are quite similar Still, differences exist Know where to find the smallprint Watch out for updates Keep in mind the common theme in FDA/PMDA docs: Consult with the regulatory agency prior to submission BTW, have you seen the following PharmaSUG 2015 paper? Japanese submission/approval processes from programming perspective (Ryan Hara) CDISC GSUG Meeting 15-Sep-2015 11