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

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

What is high quality study metadata?

esubmission - Are you really Compliant?

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

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

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

OpenCDISC Validator 1.4 What s New?

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

Common Programming Errors in CDISC Data

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

Introduction to ADaM and What s new in ADaM

Challenges with the interpreta/on of CDISC - Who can we trust?

Updates on CDISC Standards Validation

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

Study Data Reviewer s Guide Completion Guideline

Considerations on creation of SDTM datasets for extended studies

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

Best Practice for Explaining Validation Results in the Study Data Reviewer s Guide

NCI/CDISC or User Specified CT

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

An Alternate Way to Create the Standard SDTM Domains

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

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

Experience of electronic data submission via Gateway to PMDA

Taming the SHREW. SDTM Heuristic Research and Evaluation Workshop

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

DIA 11234: CDER Data Standards Common Issues Document webinar questions

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

PharmaSUG Paper AD03

Out-of-the-box %definexml

STUDY DATA TECHNICAL CONFORMANCE GUIDE

Material covered in the Dec 2014 FDA Binding Guidances

CBER STUDY DATA STANDARDS UPDATE

PhUSE US Connect 2019

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

Study Data Reviewer s Guide

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

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

Revision of Technical Conformance Guide on Electronic Study Data Submissions

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

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

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

SDTM-ETL 3.1 User Manual and Tutorial

Introduction to SAS Clinical Standards Toolkit

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

Resolving OpenCDISC Error Messages Using SAS

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

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

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

Lex Jansen Octagon Research Solutions, Inc.

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

The «CDISC Stupidario» (the CDISC Nonsense)

Dataset-XML - A New CDISC Standard

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

Step Up Your ADaM Compliance Game Ramesh Ayyappath & Graham Oakley

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

Optimizing the Use of Data Standards CSS Summary

DCDISC Users Group. Nate Freimark Omnicare Clinical Research Presented on

Standards Driven Innovation

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

Customer oriented CDISC implementation

An Efficient Solution to Efficacy ADaM Design and Implementation

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

SDTM Validation Rules in XQuery

Generating Define.xml from Pinnacle 21 Community

PharmaSUG Paper PO22

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

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.

Introduction to Define.xml

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

Clinical Metadata Metadata management with a CDISC mindset

Streamline SDTM Development and QC

Traceability Look for the source of your analysis results

Advanced Data Visualization using TIBCO Spotfire and SAS using SDTM. Ajay Gupta, PPD

ADaM Reviewer s Guide Interpretation and Implementation

Study Data Tabulation Model Implementation Guide: Human Clinical Trials Prepared by the CDISC Submission Data Standards Team

%check_codelist: A SAS macro to check SDTM domains against controlled terminology

SDTM Implementation Guide Clear as Mud: Strategies for Developing Consistent Company Standards

PharmaSUG Paper DS16

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

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

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

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

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

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

Study Data Reviewer s Guide. FDA/PhUSE Project Summary

ADaM Compliance Starts with ADaM Specifications

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

Improving CDISC SDTM Data Quality & Compliance Right from the Beginning

SDTM-ETL 4.0 Preview of New Features

How to write ADaM specifications like a ninja.

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

Creating Define-XML v2 with the SAS Clinical Standards Toolkit

Standards Metadata Management (System)

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

Metadata and ADaM.

Johannes Ulander. Standardisation and Harmonisation Specialist S-Cubed. PhUSE SDE Beerse,

FDA XML Data Format Requirements Specification

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

CDISC SDTM and ADaM Real World Issues

Transcription:

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

Presenter Max Kanevsky Founder of OpenCDISC CEO of Pinnacle 21 Valida6on tool implementer at PMDA and FDA SME on FDA JumpStart Service

Disclaimer The views and opinions presented here represent those of the speaker and should not be considered to represent advice or guidance on behalf of the Pharmaceu6cals and Medical Devices Agency and Food and Drug Administra6on.

Topics Rebranding and new releases PMDA guidance and valida6on rules Rule structure and content Comparison between PMDA and FDA Using Pinnacle 21 tools to prepare for PMDA submission Recommenda6ons

ENTERPRISE COMMUNITY OpenCDISC has rebranded Why Requested by CDISC When Effec6ve November 9th What does it mean to you No changes in func6onality or business model The only thing that changes is the name OpenCDISC.org content will be migrated under Pinnacle21.net by spring 2016

Pinnacle 21 Releases with PMDA valida+on rules support Community 2.1.0 Released December 7th Open source desktop toolkit for programmers to QC their standardized deliverables Enterprise 3.0.0 Released November 2nd SaaS collabora6ve environment for regulatory submission prep, standards management, and con6nuous compliance Used by PMDA and FDA to validate incoming submissions

PMDA Guidance

Valida+on Requirement PMDA will perform the valida5on of all submi:ed electronic data. Valida5on of conformance to the CDISC standard will be performed using a tool known as the OpenCDISC Enterprise. The applicant should confirm in advance the conformity degree of the data to the CDISC standards prior to the applica5on by referring to the published rules and informa5on on the PMDA valida5on environment. In addi5on, the error must be explained in the data guide (SDRG and ADRG). *Source: No6fica6on on Prac6cal Opera6ons of Electronic Study Data Submissions

The first release of PMDA rules Published November 24th Based on the latest Pinnacle 21 rules Changes in Severity, Message and Descrip6on Introduces addi6onal PMDA specific valida6on rules

Covered Standards SDTM IG 3.2 SDTM IG 3.1.3 (3.1.2 Amendment 1) SDTM IG 3.1.2 ADaM IG 1.0 Define- XML 2.0 Define- XML 1.0

Rules document structure Excel format machine readable Most commonly used for metadata Easy to use Columns Rule ID (same as Pinnacle 21 Rule ID) Message, Descrip6on Domains, PMDA Severity Standards, PMDA Notes

Severity Reject rules which, if violated, will cause the review to be suspended un6l correc6ons have been made. Error rules which, if violated without any prior explana6on, will cause the review to be suspended un6l correc6ons have been made. Warning rules which, even when violated, will not necessarily require any explana6on.

Reject Rules Standard # of Reject Rules SDTM 9 ADaM 12 Define- XML 13

Reject Rules (SDTM)

Reject Rules (ADaM)

Reject Rules (Define- XML)

Reject Rules (Excep+ons) Viola6on of CT2001 for the following variable/ codelist pairs will be considered part of Rejec6on criteria. All others will be considered Errors. Variable Codelist Variable Codelist Variable Codelist AGEU AGEU - - OCCUR AECONTR COUNTRY COUNTRY - - PRESP AESCAN IECAT IECAT AESER AESMIE RELTYPE RELTYPE AESCONG AESOD SEX SEX AESDISAB IEORRES - - BLFL AESDTH IESTRESC - - DRVFL AESHOSP - - STAT ND - - FAST AESLIFE

Reject Rules (Excep+ons) Viola6on of CT2004 for the following variable/ codelist pairs will be considered part of Rejec6on criteria. All others will be considered Errors. Variable TSVAL when TSPARMCD value is SEXPOP TSVAL when TSPARMCD value is ADDON TSVAL when TSPARMCD value is RANDOM Codelist SEXPOP

Reject Rules (Excep+ons) Viola6on of SD0002 will be considered part of Rejec6on criteria, except for the following variables in DM domain that will be considered Variable ARMCD ARM ACTARMCD ACTARM

How do PMDA valida+on rules differ from rules published by FDA?

Difference 1: Covered standards PMDA FDA SDTM 3.2 SDTM 3.1.3 SDTM 3.1.2 SDTM 3.1.1 SEND 3.0 ADaM 1.0 Define.xml 2.0 Define.xml 1.0

Difference 2: SDTM rule severity 326 314 PMDA FDA

Difference 3: SDTM rule severity by dimension PMDA FDA PMDA FDA PMDA FDA PMDA FDA PMDA FDA

Difference 4: New rules 21 new rules Mostly to check data quality Examples Observa6ons aler End of Par6cipa6on Treatments before the First Study Treatment or aler Last Study Treatment Incorrectly set AE Serious Event flag Nega6ve Study Day in Exposure

Difference 5: Removed rules 9 rules removed All deal with Trial Summary parameters controlled by FDA Substance Registra6on System (SRS) PMDA doesn t use FDA SRS dic6onary

Difference 6: Redefined rules FDA Rule PMDA Rule Change SD1071: Dataset is greater than 1 GB in size SD1077: FDA Expected variable not found SD1097: No Treatment Emergent info for Adverse Event SD0008: Value for - - DECOD not found in MedDRA dic6onary SD0008C: Value for - - DECOD is in incorrect case SD1142: Dataset is greater than 5 GB in size SD1140: PMDA Expected variable not found SD1141: No Treatment Emergent info for Adverse Event Same Same PMDA can support larger datasets of 5 GB FDA expects ELEMENT and EPOCH, while PMDA expects - - BLFL and EPOCH Change in Descrip6on PMDA limits this check to AE domain only PMDA limits this check to AE domain only

Differences Conclusion Except for severity, rules are consistent across FDA and PMDA Even though PMDA has Reject criteria, FDA rules are s6ll far more strict FDA has more experience and more tools/analysis that depend on standard data It s PMDA s first version, requirements are expected to increase over 6me 77%* of all submission to FDA in 2014-15 failed to load to Clinical Trial Repository (CTR), so don t be surprise to see Reject criteria from FDA too * Common Errors in Loading SDTM Data to the Clinical Trial Repository, Crystal Allard, FDA OCS

How to use Pinnacle 21 tools to prepare for PMDA submission?

Recommenda+ons Always use the latest available valida6on rules and latest version of Pinnacle 21 tools Comply with highest severity across agencies You ll likely need to submit to both Requirements will only get more strict Fix all issues that are fixable and explain the rest Follow Con6nuous Compliance approach, catch and fix data issues as early as possible

Resources PMDA Guidance and informa6on webpage hqp://www.pmda.go.jp/english/review- services/reviews/advanced- efforts/0002.html Basic Principles on Electronic Submission of Study Data for New Drug Applica6ons hqp://www.pmda.go.jp/files/000153708.pdf No6fica6on on Prac6cal Opera6ons of Electronic Study Data Submissions hqp://www.pmda.go.jp/files/000206451.pdf Technical Conformance Guide on Electronic Study Data Submissions hqp://www.pmda.go.jp/files/000206449.pdf Data Standard Catalog hqp://www.pmda.go.jp/files/000206482.zip Study Data Valida6on Rules hqp://www.pmda.go.jp/files/000208341.zip

Get updates about our events linkedin.com/company/pinnacle- 21 twiqer.com/pinnacle_21 facebook.com/pinnacle21 pinnacle21.net/blog opencdisc.org

Ques+ons Max Kanevsky mkanevsky@pinnacle21.net