The document discusses standards for clinical trial data submission, including:
- Regulatory agencies are pushing for standardized data submission to improve review efficiency under PDUFA. CDISC standards including SDTM and ADaM are becoming required.
- CDISC regularly updates and expands clinical data standards to include new domains and enhancements.
- A properly constructed define.xml file documenting the metadata is important for reviewers to understand the data.
Presentation on CDISC- SDTM guidelines.Khushbu Shah
This document provides an overview of CDISC (Clinical Data Interchange Standards Consortium) and SDTM (Standard Data Tabulation Model). It defines these standards, their purpose in establishing common data formats for clinical research, and key concepts in SDTM like domains, variables, qualifiers and time standards. The document also provides examples of how SDTM organizes data from a clinical trial, including adverse events, trial design, and standards for related records.
According to FDA Draft Guidance for Industry in Electronic Submission and Study Data Technical Conformance Guide, the pharmaceutical companies will need to provide CDISC Electronic submission to FDA. The paper will explain Data Standard Catalog which will dictate FDA Standards. The paper will discuss how to prepare CDISC electronic submission and what to prepare in CDISC electronic submission.
The document describes CDISC's Study Data Tabulation Model (SDTM), which provides a fundamental model for organizing clinical trial data based on observations of discrete pieces of information (variables). SDTM defines general classes of observations (Events, Findings, Interventions) and variable roles including topic, identifier, timing, and qualifier variables. It discusses SDTM domains as SAS dataset implementations of the model with optimizations for data exchange and medical review. Controlled terminologies and the define.xml specification are also covered.
In this presentation, Principal Statistical Scientist Ben Vaughn explains how clinical trial data moves from collection in the case report form to its presentation to FDA.
A complex ADaM dataset - three different ways to create oneKevin Lee
This document discusses three different methods for creating a complex ADaM (Analysis Data Model) dataset from SDTM (Study Data Tabulation Model) datasets. The first method involves transforming SDTM datasets directly into ADaM datasets. The second method uses intermediate permanent datasets between the SDTM and final ADaM datasets. The third method uses intermediate ADaM datasets between the SDTM and final ADaM datasets. An example complex ADaM dataset measuring average daily drinking rate is provided to illustrate each of the three methods. Key components and algorithms for deriving parameters in the example are also described.
The document discusses the Combined Data Interchange Standard Consortium (CDISC) and its Standard Data Tabulation Model (SDTM). CDISC develops standards to support clinical research data exchange and submission. SDTM defines a standard structure for study data tabulations submitted to regulators. The document outlines key aspects of SDTM including its implementation guide, fundamentals, observation classes, special purpose domains, trial design model, relationship datasets, metadata, controlled terminology, and date/time variables.
The document discusses several Trial Design domains from CDISC, including Trial Arms (TA), Trial Elements (TE), and Trial Visits (TS). It describes the key variables in each domain like ARMCD, ETCD, ELEMENT, EPOCH, VISITNUM, and start/end rules for trial elements and visits. The domains are used to represent the overall study design and plan without subject-level data.
Presentation on CDISC- SDTM guidelines.Khushbu Shah
This document provides an overview of CDISC (Clinical Data Interchange Standards Consortium) and SDTM (Standard Data Tabulation Model). It defines these standards, their purpose in establishing common data formats for clinical research, and key concepts in SDTM like domains, variables, qualifiers and time standards. The document also provides examples of how SDTM organizes data from a clinical trial, including adverse events, trial design, and standards for related records.
According to FDA Draft Guidance for Industry in Electronic Submission and Study Data Technical Conformance Guide, the pharmaceutical companies will need to provide CDISC Electronic submission to FDA. The paper will explain Data Standard Catalog which will dictate FDA Standards. The paper will discuss how to prepare CDISC electronic submission and what to prepare in CDISC electronic submission.
The document describes CDISC's Study Data Tabulation Model (SDTM), which provides a fundamental model for organizing clinical trial data based on observations of discrete pieces of information (variables). SDTM defines general classes of observations (Events, Findings, Interventions) and variable roles including topic, identifier, timing, and qualifier variables. It discusses SDTM domains as SAS dataset implementations of the model with optimizations for data exchange and medical review. Controlled terminologies and the define.xml specification are also covered.
In this presentation, Principal Statistical Scientist Ben Vaughn explains how clinical trial data moves from collection in the case report form to its presentation to FDA.
A complex ADaM dataset - three different ways to create oneKevin Lee
This document discusses three different methods for creating a complex ADaM (Analysis Data Model) dataset from SDTM (Study Data Tabulation Model) datasets. The first method involves transforming SDTM datasets directly into ADaM datasets. The second method uses intermediate permanent datasets between the SDTM and final ADaM datasets. The third method uses intermediate ADaM datasets between the SDTM and final ADaM datasets. An example complex ADaM dataset measuring average daily drinking rate is provided to illustrate each of the three methods. Key components and algorithms for deriving parameters in the example are also described.
The document discusses the Combined Data Interchange Standard Consortium (CDISC) and its Standard Data Tabulation Model (SDTM). CDISC develops standards to support clinical research data exchange and submission. SDTM defines a standard structure for study data tabulations submitted to regulators. The document outlines key aspects of SDTM including its implementation guide, fundamentals, observation classes, special purpose domains, trial design model, relationship datasets, metadata, controlled terminology, and date/time variables.
The document discusses several Trial Design domains from CDISC, including Trial Arms (TA), Trial Elements (TE), and Trial Visits (TS). It describes the key variables in each domain like ARMCD, ETCD, ELEMENT, EPOCH, VISITNUM, and start/end rules for trial elements and visits. The domains are used to represent the overall study design and plan without subject-level data.
SDTM (Study Data Tabulation Model) defines a standard structure for human clinical trial (study) data tabulations and for nonclinical study data tabulations that are to be submitted as part of a product application to a regulatory authority such as the United States Food and Drug Administration (FDA).
This document discusses the implementation of CDISC SDTM. It notes that the FDA plans to require SDTM as a federal regulation, giving it legal force. Successful implementation requires mapping source data to SDTM domains and validating the results. The data manager plays a key role in mapping and quality control. New roles like mapping specialist and data integration specialist are needed to perform tasks like developing SDTM domains and executing conversion jobs. Widespread adoption of SDTM is expected to provide significant benefits through automation and standardization.
This document summarizes Angelo Tinazzi and Cedric Marchand's experience submitting clinical trial data to the FDA using CDISC standards. It describes their recent submission, including standards used, current status, and interaction with FDA reviewers. It also discusses requirements for electronic submissions and FDA feedback received from a test submission, including suggestions for SDTM content and define.xml. The presentation aims to help others in properly preparing FDA submissions using CDISC standards.
Finding everything about findings about (fa)Ram Gali
The document discusses the SDTM 3.1.2 Findings About (FA) domain. FA is used to store findings that do not fit in other domains or supplemental qualifiers. It provides examples of when to use FA, such as to store adverse event severity timings or details of a prerequisite condition not in the Medical History domain. The document also discusses how to relate unrelated FA data to the parent domain using multiple datasets linked with RELREC relationships. Important FA variables include FATEST/FATESTCD to describe measurements/events and FAOBJ to describe the event/intervention measured.
The document discusses CDISC standards and their implementation. It begins by asking what the CDISC standards are, when is the best time to implement them, and the timeline for requiring them in FDA submissions. It then explains that CDISC develops data standards for medical research through an open consensus process. Implementing standards early in a clinical program saves time and money compared to converting legacy data later. The FDA will require CDISC standards like SDTM and ADaM for submissions through binding guidance issued in 2012 as part of critical path initiatives and legislative acts. Resources are available to stay up to date on standards development.
SDTM (Study Data Tabulation Model) defines a standard for organizing and formatting data to streamline processes in collection, management, analysis and reporting of human clinical trial data tabulations and for non-clinical study data tabulations which are to be submitted as part of a product application(IND and NDA) to a regulatory authority such as the United States Food and Drug Administration (FDA) and PMDA (Japan)
CDISC is a non-profit organization that establishes clinical research data standards to support data acquisition, exchange, and submission. It has developed several standards including CDASH, which aims to standardize data collection fields across clinical trials to streamline data analysis and reduce errors. CDASH defines a set of common safety domains and variables that can be collected consistently across studies in a standardized way. This helps analyze data more efficiently, reduces training time for sites, and decreases potential errors from inconsistent data collection.
The document summarizes the Study Data Tabulation Model (SDTM), which defines a standard structure for submitting human clinical trial data to regulatory authorities. SDTM organizes data into domains based on three general classes: Interventions, Events, and Findings. Each observation within a domain contains identifier, topic, timing, and qualifier variables to describe essential details. Qualifier variables are further categorized, and the Submission Metadata Model specifies seven attributes for each variable to ensure consistent interpretation.
INTERPRETING CDISC ADaM IG THROUGH USERS INTERPRETATIONAngelo Tinazzi
The document appears to be a presentation about interpreting the CDISC ADaM Implementation Guide. It discusses conducting a systematic review of papers discussing ADaM implementation to understand areas of ambiguity and different interpretations. The review found over 100 papers focused on ADaM implementation, with the most discussions at PharmaSUG and PhUSE conferences. Common topics of interpretation included traceability, non-ADaM analysis datasets, validation, and issues with the basic data structure. The presentation aims to facilitate discussion on resolving areas of ambiguity in the guide.
This document discusses how to validate the SDTM SUPPQUAL dataset. It recommends creating separate SUPP datasets for each SDTM domain to make validation easier. It also recommends creating SDTM+SUPP datasets that combine each SDTM domain with its related supplemental variables for improved traceability. The document provides steps for validating SDTM+SUPP datasets and using a define document and macro to split them into separate SDTM and SUPP datasets during the validation process.
The document discusses the requirements and specifications for submitting applications to the FDA using the electronic common technical document (eCTD) format. It states that eCTD is the standard format for submissions to the Center for Biologics Evaluation and Research and the Center for Drug Evaluation and Research. The document outlines the five modules that make up an eCTD submission and provides details on submission types, required formats, pre-submission requirements like obtaining an application number, and how to transmit submissions through the Electronic Submissions Gateway.
CLINICAL STUDY REPORT - IN-TEXT TABLES, TABLES FIGURES AND GRAPHS, PATIENT AN...Angelo Tinazzi
This document discusses technical requirements and solutions for producing statistical outputs for clinical study reports according to ICH E3 guidelines. It provides an overview of key points in ICH E3 related to in-text tables, post-text tables and figures, narratives, and patient data listings. It also discusses considerations for formatting outputs, including paper size and style guidelines. Potential solutions for automating output generation using SAS are presented.
Explaining the importance of a database lock in clinical researchTrialJoin
One of the most crucial aspects of research is clinical data management or CDM. Proper CDM will generate results with excellent quality, integrity, and reliability. Quality data is essential in order to support the final conclusions of a certain study.
The person responsible for this area of research is called a clinical data manager. This job position can be filled by a PI, a study coordinator, or a CRA. No matter who fills this position at your site, data management has to be done promptly and correctly in order to generate the best results. Aside from all the other reasons why data management is so important, it’s also what determines the future IP (investigational product) development.
This document provides an overview of oncology and cancer clinical trials from a data standards and programming perspective. It begins with basic cancer definitions and epidemiology. Key aspects of clinical trials in oncology are then discussed, including complex efficacy endpoints, safety evaluations, and exposure assessments. Standardization efforts through CDISC are summarized, including SDTM and ADaM domains for oncology. Regulatory guidelines from the FDA and EMA are also covered. Throughout, challenges specific to oncology trials from a data and programming standpoint are highlighted. The aim of the PhUSE oncology wiki is also introduced as a resource for further information.
This document provides guidance on starting ADaM specification development and dataset programming. It recommends starting with ADaM subject matter experts and a well-defined specification template. It also recommends understanding the SDTM datasets, analysis keys, and Occurrence Data Structure requirements. The document outlines considerations like variable attributes and traceability when developing specifications and programming datasets. It emphasizes adhering to the ADaM Implementation Guide.
This document provides an overview of ADaM (Analysis Data Model) and recommendations for getting started with ADaM specification development, programming, and quality control (QC). It discusses:
1) Starting ADaM specification development by identifying analysis datasets needed based on the SAP and using a clear template to define required variables and attributes.
2) Beginning ADaM programming by understanding the source SDTM datasets and ADaM specifications, including how complex algorithms and derivations are defined.
3) Initiating ADaM QC by checking that analysis variables can be traced back to SDTM, comply with the ADaM IG, and support required analysis results. Simple programming and use of
Handling Third Party Vendor Data_Katalyst HLSKatalyst HLS
The document discusses handling third party vendor data in clinical trials. It covers four types of external data including safety laboratory data, PK/PD data, pharmacogenetics data, and device data. Centralized vendors provide standardized testing across sites and electronic transfer of data to minimize errors. Data reconciliation involves generating discrepancy reports using primary keys like sponsor ID, study ID, and subject ID, and secondary keys like date of birth. Queries are raised to sites or vendors to resolve inconsistencies between third party and clinical trial databases.
How to build ADaM BDS dataset from mock up tableKevin Lee
This document provides instructions for building ADaM basic data structures (BDS) from annotated mock up tables. It discusses how to design mock up tables based on the statistical analysis plan, annotate the tables, create metadata, and then build the ADaM BDS datasets according to the metadata. The process results in analysis-ready ADaM datasets where all numbers in the final report can be calculated with one SAS procedure. An example is provided demonstrating how to annotate a mock up table and extract the necessary variables and parameters to include in the ADaM datasets and metadata.
CDISC's CDASH and SDTM: Why You Need Both!Kit Howard
CDISC's clinical data standards are widely used for clinical research, but many people wonder why there seem to be two standards for collected data: the Clinical Data Acquisition Standards Harmonization (CDASH) standard and the Study Data Tabulation Model (SDTM) standard. This poster steps through four significant reasons that reflect the differences in philosophy, intermediate goals and broad-scale uses. Examples illustrate each reason and how they affect your studies.
This document describes a presentation by Angelo Tinazzi of Cytel Inc. looking for an SDTM specialist to work at the PhUSE conference in London from October 12-15, 2014. It provides examples of challenges faced in legacy data conversion, including a case study of performing a gap analysis for a small biotech company and discussing issues in modeling oncology study data to SDTM.
The presentation discusses the FDA's Electronic Submissions Gateway (ESG) and electronic submissions. It provides an overview of the ESG and what types of submissions it accepts from each FDA center. It emphasizes that requirements vary by center and preparing for electronic submissions takes time. The presentation encourages attendees to contact the speaker for assistance in navigating FDA's electronic submission processes.
SDTM (Study Data Tabulation Model) defines a standard structure for human clinical trial (study) data tabulations and for nonclinical study data tabulations that are to be submitted as part of a product application to a regulatory authority such as the United States Food and Drug Administration (FDA).
This document discusses the implementation of CDISC SDTM. It notes that the FDA plans to require SDTM as a federal regulation, giving it legal force. Successful implementation requires mapping source data to SDTM domains and validating the results. The data manager plays a key role in mapping and quality control. New roles like mapping specialist and data integration specialist are needed to perform tasks like developing SDTM domains and executing conversion jobs. Widespread adoption of SDTM is expected to provide significant benefits through automation and standardization.
This document summarizes Angelo Tinazzi and Cedric Marchand's experience submitting clinical trial data to the FDA using CDISC standards. It describes their recent submission, including standards used, current status, and interaction with FDA reviewers. It also discusses requirements for electronic submissions and FDA feedback received from a test submission, including suggestions for SDTM content and define.xml. The presentation aims to help others in properly preparing FDA submissions using CDISC standards.
Finding everything about findings about (fa)Ram Gali
The document discusses the SDTM 3.1.2 Findings About (FA) domain. FA is used to store findings that do not fit in other domains or supplemental qualifiers. It provides examples of when to use FA, such as to store adverse event severity timings or details of a prerequisite condition not in the Medical History domain. The document also discusses how to relate unrelated FA data to the parent domain using multiple datasets linked with RELREC relationships. Important FA variables include FATEST/FATESTCD to describe measurements/events and FAOBJ to describe the event/intervention measured.
The document discusses CDISC standards and their implementation. It begins by asking what the CDISC standards are, when is the best time to implement them, and the timeline for requiring them in FDA submissions. It then explains that CDISC develops data standards for medical research through an open consensus process. Implementing standards early in a clinical program saves time and money compared to converting legacy data later. The FDA will require CDISC standards like SDTM and ADaM for submissions through binding guidance issued in 2012 as part of critical path initiatives and legislative acts. Resources are available to stay up to date on standards development.
SDTM (Study Data Tabulation Model) defines a standard for organizing and formatting data to streamline processes in collection, management, analysis and reporting of human clinical trial data tabulations and for non-clinical study data tabulations which are to be submitted as part of a product application(IND and NDA) to a regulatory authority such as the United States Food and Drug Administration (FDA) and PMDA (Japan)
CDISC is a non-profit organization that establishes clinical research data standards to support data acquisition, exchange, and submission. It has developed several standards including CDASH, which aims to standardize data collection fields across clinical trials to streamline data analysis and reduce errors. CDASH defines a set of common safety domains and variables that can be collected consistently across studies in a standardized way. This helps analyze data more efficiently, reduces training time for sites, and decreases potential errors from inconsistent data collection.
The document summarizes the Study Data Tabulation Model (SDTM), which defines a standard structure for submitting human clinical trial data to regulatory authorities. SDTM organizes data into domains based on three general classes: Interventions, Events, and Findings. Each observation within a domain contains identifier, topic, timing, and qualifier variables to describe essential details. Qualifier variables are further categorized, and the Submission Metadata Model specifies seven attributes for each variable to ensure consistent interpretation.
INTERPRETING CDISC ADaM IG THROUGH USERS INTERPRETATIONAngelo Tinazzi
The document appears to be a presentation about interpreting the CDISC ADaM Implementation Guide. It discusses conducting a systematic review of papers discussing ADaM implementation to understand areas of ambiguity and different interpretations. The review found over 100 papers focused on ADaM implementation, with the most discussions at PharmaSUG and PhUSE conferences. Common topics of interpretation included traceability, non-ADaM analysis datasets, validation, and issues with the basic data structure. The presentation aims to facilitate discussion on resolving areas of ambiguity in the guide.
This document discusses how to validate the SDTM SUPPQUAL dataset. It recommends creating separate SUPP datasets for each SDTM domain to make validation easier. It also recommends creating SDTM+SUPP datasets that combine each SDTM domain with its related supplemental variables for improved traceability. The document provides steps for validating SDTM+SUPP datasets and using a define document and macro to split them into separate SDTM and SUPP datasets during the validation process.
The document discusses the requirements and specifications for submitting applications to the FDA using the electronic common technical document (eCTD) format. It states that eCTD is the standard format for submissions to the Center for Biologics Evaluation and Research and the Center for Drug Evaluation and Research. The document outlines the five modules that make up an eCTD submission and provides details on submission types, required formats, pre-submission requirements like obtaining an application number, and how to transmit submissions through the Electronic Submissions Gateway.
CLINICAL STUDY REPORT - IN-TEXT TABLES, TABLES FIGURES AND GRAPHS, PATIENT AN...Angelo Tinazzi
This document discusses technical requirements and solutions for producing statistical outputs for clinical study reports according to ICH E3 guidelines. It provides an overview of key points in ICH E3 related to in-text tables, post-text tables and figures, narratives, and patient data listings. It also discusses considerations for formatting outputs, including paper size and style guidelines. Potential solutions for automating output generation using SAS are presented.
Explaining the importance of a database lock in clinical researchTrialJoin
One of the most crucial aspects of research is clinical data management or CDM. Proper CDM will generate results with excellent quality, integrity, and reliability. Quality data is essential in order to support the final conclusions of a certain study.
The person responsible for this area of research is called a clinical data manager. This job position can be filled by a PI, a study coordinator, or a CRA. No matter who fills this position at your site, data management has to be done promptly and correctly in order to generate the best results. Aside from all the other reasons why data management is so important, it’s also what determines the future IP (investigational product) development.
This document provides an overview of oncology and cancer clinical trials from a data standards and programming perspective. It begins with basic cancer definitions and epidemiology. Key aspects of clinical trials in oncology are then discussed, including complex efficacy endpoints, safety evaluations, and exposure assessments. Standardization efforts through CDISC are summarized, including SDTM and ADaM domains for oncology. Regulatory guidelines from the FDA and EMA are also covered. Throughout, challenges specific to oncology trials from a data and programming standpoint are highlighted. The aim of the PhUSE oncology wiki is also introduced as a resource for further information.
This document provides guidance on starting ADaM specification development and dataset programming. It recommends starting with ADaM subject matter experts and a well-defined specification template. It also recommends understanding the SDTM datasets, analysis keys, and Occurrence Data Structure requirements. The document outlines considerations like variable attributes and traceability when developing specifications and programming datasets. It emphasizes adhering to the ADaM Implementation Guide.
This document provides an overview of ADaM (Analysis Data Model) and recommendations for getting started with ADaM specification development, programming, and quality control (QC). It discusses:
1) Starting ADaM specification development by identifying analysis datasets needed based on the SAP and using a clear template to define required variables and attributes.
2) Beginning ADaM programming by understanding the source SDTM datasets and ADaM specifications, including how complex algorithms and derivations are defined.
3) Initiating ADaM QC by checking that analysis variables can be traced back to SDTM, comply with the ADaM IG, and support required analysis results. Simple programming and use of
Handling Third Party Vendor Data_Katalyst HLSKatalyst HLS
The document discusses handling third party vendor data in clinical trials. It covers four types of external data including safety laboratory data, PK/PD data, pharmacogenetics data, and device data. Centralized vendors provide standardized testing across sites and electronic transfer of data to minimize errors. Data reconciliation involves generating discrepancy reports using primary keys like sponsor ID, study ID, and subject ID, and secondary keys like date of birth. Queries are raised to sites or vendors to resolve inconsistencies between third party and clinical trial databases.
How to build ADaM BDS dataset from mock up tableKevin Lee
This document provides instructions for building ADaM basic data structures (BDS) from annotated mock up tables. It discusses how to design mock up tables based on the statistical analysis plan, annotate the tables, create metadata, and then build the ADaM BDS datasets according to the metadata. The process results in analysis-ready ADaM datasets where all numbers in the final report can be calculated with one SAS procedure. An example is provided demonstrating how to annotate a mock up table and extract the necessary variables and parameters to include in the ADaM datasets and metadata.
CDISC's CDASH and SDTM: Why You Need Both!Kit Howard
CDISC's clinical data standards are widely used for clinical research, but many people wonder why there seem to be two standards for collected data: the Clinical Data Acquisition Standards Harmonization (CDASH) standard and the Study Data Tabulation Model (SDTM) standard. This poster steps through four significant reasons that reflect the differences in philosophy, intermediate goals and broad-scale uses. Examples illustrate each reason and how they affect your studies.
This document describes a presentation by Angelo Tinazzi of Cytel Inc. looking for an SDTM specialist to work at the PhUSE conference in London from October 12-15, 2014. It provides examples of challenges faced in legacy data conversion, including a case study of performing a gap analysis for a small biotech company and discussing issues in modeling oncology study data to SDTM.
The presentation discusses the FDA's Electronic Submissions Gateway (ESG) and electronic submissions. It provides an overview of the ESG and what types of submissions it accepts from each FDA center. It emphasizes that requirements vary by center and preparing for electronic submissions takes time. The presentation encourages attendees to contact the speaker for assistance in navigating FDA's electronic submission processes.
ICD-10 Transition Update: What Health Lawyers Need to KnowPYA, P.C.
This document provides an overview of ICD-10 and the transition from ICD-9 to ICD-10 for healthcare organizations. It discusses the regulatory timeline requiring compliance by October 1, 2014, the differences between ICD-10-CM for diagnoses and ICD-10-PCS for procedures, organizational and financial impacts, and risk mitigation strategies for the transition. The transition represents a significant change that will impact coding, clinical documentation, claims processing, billing systems, and vendor relationships. Proper planning is needed to assess readiness and minimize risks to operations and revenue during the transition period.
ICD-10 Transition: What Health Lawyers Need to KnowPYA, P.C.
PYA Principal Denise Hall, along with Senior Corporate Counsel Julie Chicoine of Ohio State University Wexner Medical Center, presented “ICD-10 Transition: What Health Lawyers Need to Know” at the AHLA 2015 Institute on Medicare and Medicaid Payment Issues.
understanding the validity and increased scrutiny of data used for compliance...All4 Inc.
This document discusses the validity and scrutiny of data used for environmental compliance purposes. It outlines the five components of next generation compliance according to the EPA: advanced monitoring, electronic reporting, regulation and permit design, innovative enforcement, and transparency. It then discusses increased regulatory scrutiny and the importance of understanding CMS data systems, management, and validation processes to ensure compliance.
Disaster Recovery and Business Continuity for Your Clinical and Safety SystemsPerficient, Inc.
Your systems are up and running. You have no issues. It’s business as usual and all is as it should be. Then, suddenly, it’s not. A flood, an earthquake, a tornado or a fire threatens your organization’s ability to continue operating. Systems are offline, critical business processes have stalled. What damage has been inflicted? How long until you can recover? What do you do in the meantime? These are questions that no organization can properly answer without proper planning and testing.
The implications of an unplanned and unprepared-for event can be devastating to a company, as well as to the patients it serves. The only way to mitigate such risks is through comprehensive planning and testing.
Sean Bernard, lead business consultant in Perficient's life sciences practice, discussed why business continuity and disaster planning are so critical to life sciences companies, and shares best practices for preparing your company for the unforeseen.
The document provides an overview of electronic Common Technical Document (eCTD) format for regulatory submissions globally. It defines key terms related to eCTD and describes the history and structure of the Common Technical Document (CTD) format adopted by the International Conference on Harmonization (ICH). The document compares paper, non-eCTD electronic and eCTD submission formats and highlights benefits of eCTD format. It also provides high-level information on eCTD fundamentals, folder structure and backbone XML view. Finally, it discusses key requirements and considerations for electronic submissions to major regulatory authorities in US, EU, Saudi Arabia, GCC countries and Health Canada.
2010 07 BSidesLV Mobilizing The PCI Resistance 1c Security B-Sides
This document discusses lessons learned from previous compliance initiatives that can be applied to improving the state of PCI DSS compliance. It draws parallels between problems with SOX-404 compliance and current issues with PCI DSS, noting frustration with both standards. The document proposes using concepts from the GAIT framework, which was created to address SOX-404 problems, as a model for how to better scope the PCI assessment and define relevant controls. It intends to get feedback on this plan to help refine the approach and potentially mobilize industry stakeholders to improve PCI DSS practices.
2010 07 BSidesLV Mobilizing The PCI Resistance 1cGene Kim
Properly Mobilizing the PCI Resistance: Lessons Learned From Fighting Prior Wars (SOX-404)"
I have noticed that there is a growing wave of discontent and disenchantment from information security and compliance practitioners around the PCI DSS. Josh Corman has been an effective voice for these concerns, providing an intellectually honest and earnest analysis in his talk “Is PCI The No Child Left Behind Act For Infosec?”
The problem are well-known and significant: too much ambiguity in the PCI DSS, Qualified Security Assessors (QSAs) and consultant using subjective interpretations, existing guidance either too prescriptive or too vague, scope missing critical systems that could risk cardholder data, overly broad scope and excessive testing costs, excessive subjectivity and inconsistency, poor use of scarce resources, no meaningful reduction in risk of data breaches, and so forth.
For years, I have been studying the PCI DSS compliance problem, as well. I have noticed many similarities to the PCI compliance challenges and the “SOX-404 Is The Biggest IT Time Waster” wars in 2005. I was part of the leadership team at the Institute of Internal Auditors (IIA) where we did something about the it. We identified inability to accurately scope the IT portions of SOX-404 as the root cause of the billions of dollars of wasted time and effort, while not reducing the risk of financial misstatements.
I propose to present the two-year success story of the IIA GAIT project and how we changed the state of the IT audit practice in support of SOX-404 financial reporting audits. We defined the four GAIT Principles, which could be used to correctly scope the IT portions of SOX-404. We mobilized over 100K internal auditors, the SEC and PCAOB regulatory and enforcement bodies, as well as the external auditors from the 8 big CPA firms (e.g, Big Four and other firms doing SOX advisory work). In short, we made a difference, in a highly political process that involved many constituencies.
I am attempting to do something similar with the PCI Security Standards Council, through my work as part one of the leaders of the PCI Scoping SIG (Special Interest Group). My personal goal is to find a “third way” to better enable correct scoping of the PCI Cardholder Data Environment, and create a risk-based approach of substantiating the effective controls to ensure that cardholder data breaches can be prevented, and quickly detected and corrected when they do occur.
My desired outcome is to find fellow travelers who also see the pile of dead bodies in PCI compliance efforts, and work with those practitioners to catalyze a similar movement to achieve the spirit and intent of PCI DSS.
This document summarizes a hospital's vendor selection process in 1993 to replace their existing hospital information system. It describes how Meditech was selected over 9 other vendors after a rigorous evaluation process involving an RFI, on-site demonstrations, reference calls, user manual reviews, and contract negotiations. Meditech scored highest based on functionality, support, costs, stability, and unanimous preference by the hospital's departments. The document highlights both Meditech's strengths as well as weaknesses presented to the selection committee.
How FDA will reject non compliant electronic submissionKevin Lee
Beginning Dec 18, 2016, all clinical trial and nonclinical trial studies must use standards (e.g., CDISC) for submission data and beginning May 5, 2017, NDA, ANDA, and BLA submissions must follow eCTD format for submission documents.
In order to enforce these standards mandates, the FDA also released "Technical Rejection Criteria for Study Data" in FDA eCTD website on October 3, 2016. FDA also implemented a rejection process for submissions that do not conform to the required study data standards.
The paper will discuss how these new FDA mandates impact the electronic submission and the required preparation for CDISC and eCTD complaint submission package such as SDTM, ADaM, Define.xml, SDTM annotated eCRF, SDRG, ADRG and SAS® programs. The paper will introduce the current FDA submission process, including the current FDA rejection processes – “Technical Rejection” and “Refuse-to-File” and discuss how FDA uses “Technical Rejection” and “Refuse-to-File” to reject submission. The paper will show how FDA rejection of CDISC non-compliant data will impact sponsor’s submission process, and how sponsors should respond to FDA rejections as well as questions throughout the whole submission process. Use cases will demonstrate the key technical rejection criteria that will have the greatest impact on a successful submission process
We feature experts Stanley Nachimsom of Nachimsom Associates and Michael Palatoni of Athena Health to review WEDI survey results and share small practice/physician update on ICD-10 implementation. Visit floridablue.com/icd-10, your complete ICD-10 resource.
Vendor Management for PCI DSS, HIPAA, and FFIECControlCase
ControlCase covers the following:
•Requirements for PCI DSS, HIPAA, Business Associates, FFIEC and Banking Service Providers
•What is Vendor Management
•Why is Continual Compliance a challenge in Vendor Management
•How to mix technology and manual processes for effective Vendor Management
QualiTest offers a holistic testing approach which provides an end-to-end test at a fraction of the cost compared to current market approaches.
QualiTest understands the challenges and risks involved in ICD-10 transformation across the healthcare spectrum: providers, payers, clearinghouses, and vendors. As the world’s second-largest independent pure play QA and testing solution partner, QualiTest provides comprehensive end-to-end services for ICD-10 testing to all entities in the healthcare industry.
http://www.qualitestgroup.com
This document provides an overview of a presentation by Brian Levy MD on using Health Language tools to help with the ICD-10 conversion. The presentation covers Health Language offerings including terminologies, software, and services. It then discusses using the LEAP I-10 tool to analyze potential financial impacts of ICD-10 through claims analytics and identify areas for clinical documentation improvement. The presentation concludes by discussing benefits of ICD-10 such as increased coding accuracy and support for value-based reimbursement models.
Eugm 2012 demets - clinical trials and the impact of regulationsCytel USA
This document summarizes key topics in clinical trials and the impact of regulations. It discusses the proliferation of multinational trials and varying interpretations of regulatory guidelines. Globalization has increased the number of countries and sites involved in trials. Regulations have increased costs without necessarily improving trials. The guidelines focus monitoring on critical events rather than exhaustive validation. New strategies aim to streamline processes while maintaining scientific rigor.
This document discusses the transition from ICD-9 to ICD-10 coding in the United States. ICD-9, implemented in 1979, is outdated and limited to around 15,000 codes. Most other countries adopted ICD-10 in the 1990s. The U.S. has faced delays in implementing ICD-10, most recently pushing the deadline to October 1, 2014. The transition requires upgrades to comply with HIPAA 5010 standards as well as extensive testing and revisions to systems and processes. The new system will include over 141,000 codes and impact billing, reimbursement and data reporting.
“Detection of Diseases using Machine Learning”IRJET Journal
This document describes a machine learning-based disease prediction system. The system was developed as a web application using the Flask framework. It uses logistic regression and random forest classifiers trained on disease-related health parameters to predict diseases. The system allows users to login and submit their health details, generates a prediction report, and stores all user data in a MySQL database for admin access and record keeping. The goal is to help doctors detect diseases earlier and improve healthcare system quality by leveraging machine learning models.
Beyond regulatory submission - standards metadata managementKevin Lee
After FDA published the final “Guidance for Industry on electronic submission” that will require submission data in CDISC standards, all the life sciences organizations focus on implementing CDISC standards on clinical data development. However, organizations also see other opportunities with CDISC standards. The presentation will introduce what could be possible through Standards such as Standards-driven automated process in clinical artefacts development and how the organization need to manage and govern standards in order to achieve the next steps.
Similar to THE DO’S AND DON’TS OF DATA SUBMISSION (20)
The use of Adaptive designs is becoming quite popular and well-perceived by the regulatory agencies such as the FDA in the US. “Adaptation” can occur in different fashion and potentially make studies more efficient (e.g. shorter duration, fewer patients) more likely to demonstrate an effect of the drug if one exists, or more informative (see “Adaptive Design Clinical Trials for Drugs and Biologics” FDA guidance).
The aim of this presentation is to illustrate a case where an adaptive design was used in a Phase III oncology pivotal study having Overall Survival as a primary end-point. The particular adaptation implemented was an un-blinded SSR that applied a promising zone approach.
The main focus will be how the adaptive design impacted the SDTM modelling, the design of some ADaM datasets (e.g. those containing the time-to-event endpoints and therefore using ADTTE ADaM model) and later on how some mapping and analysis decisions were described in both the study and analysis reviewer guide.
This document discusses an adaptive clinical trial design that was used in a phase III oncology study. The particular adaptation was an unblinded sample size re-estimation based on interim analysis results. This required changes to the SDTM and ADaM data models to account for the interim analysis cut-off dates. The reviewer guides were also updated to explain how to identify patients in the interim analysis and which analysis datasets to use for re-calculating results based on the interim and final cut-offs.
This document discusses CDISC standards for representing survival data from oncology clinical trials. It provides an overview of CDISC and describes the SDTM and ADaM domains that are useful for capturing efficacy endpoints involving survival, such as overall survival, progression-free survival and tumor response. Examples are given of how survival data from different patients would be represented in an ADTTE (Analysis Dataset for Time to Event) dataset according to CDISC ADaM standards.
This document summarizes a paper presented at the PhUSE 2014 conference about migrating clinical trial data from its original format to the CDISC SDTM format. It outlines the key steps in the SDTM migration process, including performing a gap analysis, understanding the source datasets, modeling the migration, performing the migration, and final validation. It emphasizes that SDTM migration can be challenging, especially for studies with complex designs, and requires careful planning by a specialized SDTM migration expert.
A Systematic Review of ADaM IG InterpretationAngelo Tinazzi
The document summarizes a systematic review of publications about the implementation of the ADaM model. Over 100 papers were identified that discussed ADaM implementation, with the majority coming from CRO authors. Several areas of interpretation in the ADaM guidelines were identified from the literature, including how to classify parameters in BDS, derive rows versus columns, and determine what constitutes an "analysis-ready" dataset. The review concluded that feedback from users would help the CDISC team further develop and clarify the ADaM guidelines.
Therapeutic Area Standards –Reflections on Oncology standards and what is ne...Angelo Tinazzi
This document discusses CDISC standards for oncology clinical trials and opportunities for improvement. It notes that CDISC has incorporated domains for tumor response assessment but questions remain around implementing RECIST criteria and capturing prior cancer therapies. The document suggests areas where CDISC oncology standards could provide more guidance, such as trial design elements like unlimited treatment cycles, capturing exposure modifications, and providing more support for non-solid tumor response assessments. Overall, it examines current CDISC oncology standards and identifies examples of additional clarity and domains that could better meet the needs of oncology clinical research.
While the evolution of information technology is bringing the data closer to customers for their own exploration, the need of a comprehensive understanding of the therapeutic area knowledge for programmers in clinical development is increasing. Starting with a basic understanding on the medical background, special assessment methods, ways of statistically analyzing and displaying the data, to name a few essential ones enables programmers to interact with partners (e.g. scientist, statisticians etc.) on equal par.
In this intent, activities to collect and provide comprehensive information around the Oncology and Rheumatoid Arthritis Therapeutic Areas (TA) via the PhUSE Wiki had started in February 2013 and continued throughout the year. Various PhUSE members have spent time and energy to provide and expand their knowledge and make it available to the entire community.
Today, although there is still much to do to complete and maintain the collected material, the two TA Wikis are a useful tool for Statistical Programmers approaching these TA for the first time or who want to improve their knowledge. Moreover the PhUSE Wiki can be seen as a basic tool for future developments to improve the way professionals in the different TA work. An established working relationship across organizations, pharmaceutical companies or external service providers, will help to support implementation of TA-specific standards from mapping raw data in SDTM, data analysis using ADaM and finally data presentation in standardized outputs. The PhUSE Wiki can be the central place to share important updates such as new CDISC TA standards or the availability of new TA regulatory guidance. On the other hand we see the Wiki as a place to discuss, to stimulate and inspire new initiatives among the “SAS-Programming Community”, be it Statisticians, Programmers, Data Managers or everyone else involved; this may include specific TA working related white papers and/or scripts being part of the FDA Working Groups WG5 “Development of Standard Scripts for Analysis and Programming” Project 08 “Create white papers providing recommended display and analysis including Table, List and Figure shells”.
Presented at PhUSE/FDA CSS 2014 in Silver Spring (US)
Interpreting CDISC ADaM IG through Users InterpretationAngelo Tinazzi
This document summarizes a presentation given at the PhUSE 2013 conference titled "Interpreting CDISC ADaM IG through Users Interpretation". The presentation aimed to systematically review publications on the CDISC Analysis Data Model (ADaM) standard in order to evaluate how different organizations have implemented and interpreted ADaM. Over 100 presentations focused on ADaM implementation were identified from conferences like PharmaSUG and PhUSE. Key topics of discussion included how to map non-standard clinical domains to ADaM, determining how "analysis-ready" datasets should be, and handling listings/derived values not supported in ADaM. The presentation provided qualitative summaries of user interpretations and applications of various ADaM guidelines and
This document summarizes key efficacy endpoints used in oncology clinical trials, including for solid tumors and non-solid tumors like acute myeloid leukemia. For solid tumors, the best overall response (BOR) is assessed using RECIST criteria to evaluate tumor shrinkage or progression based on target and non-target lesion measurements. Key time-to-event endpoints discussed include overall survival (OS), progression-free survival (PFS), and time to progression (TTP). For acute myeloid leukemia, response is assessed based on blood counts and bone marrow blast percentage according to International Working Group criteria, with endpoints like complete remission rate and event-free survival. Surrogate endpoints are also discussed.
A gentle introduction to survival analysisAngelo Tinazzi
This document provides an introduction to survival analysis techniques for statistical programmers. It discusses key concepts in survival analysis including censoring, the Kaplan-Meier method for estimating survival probabilities, and assumptions of survival models. Programming aspects like creating time-to-event datasets and using SAS procedures for survival analysis are also covered.
This document provides an overview of meta-analysis and summarizes its key aspects and statistical methods. It discusses how meta-analysis can combine results from multiple studies to obtain a single estimate of treatment effect. It also summarizes the steps involved in planning and conducting a meta-analysis, including defining the question, inclusion criteria, searching strategies, and statistical methods for analyzing different types of outcomes. Finally, it reviews several software options available for performing meta-analyses.
The Implementation of ICH Development Safety Update Report (DSUR) GuidanceAngelo Tinazzi
The document summarizes a presentation about implementing the ICH Development Safety Update Report (DSUR) guidance. It discusses:
- The background and overview of the new ICH DSUR guidance, including its history and key points.
- Implications for study sponsors, including streamlining multiple reports into a single DSUR and establishing standardized processes.
- Components of DSUR implementation, such as developing a clinical trials inventory, extracting and managing data, and mapping data for analysis outputs.
Presented at PhUSE 2013
The evaluation of efficacy in oncology studies, in particular for solid tumors, is pretty standard and well defined by several regulatory guidance (e.g. EMA and FDA), including some specific cancer type guidance (e.g. NSCLC from FDA).
Although some references will be also given for non-solid tumors, the paper will mainly focus on solid tumors efficacy
endpoints.
Overall Survival, Best Overall Response as per RECIST criteria, Progression Free Survival (PFS), Time to Progression (TTP), Best Overall Response Rate are some of the key efficacy indicators that will be discussed.
Web-Triage An Application for patient registration in phase I dose escalation...Angelo Tinazzi
This document describes an application called Web-Triage for patient registration in phase I dose escalation oncology studies. SENDO is a non-profit academic research organization that coordinates phase I-II oncology clinical trials across sites in Italy and Switzerland. Phase I studies test new drugs in cancer patients to determine safety and optimal dosing. Web-Triage streamlines patient screening and registration to accelerate trial enrollment. The application was designed to meet the specific needs of phase I oncology trials, including rapid sorting of eligible patients to optimize treatment.
From Local Laboratory to Standardisation and beyond Applying a common grading...Angelo Tinazzi
This document discusses applying a common grading system for laboratory data from local laboratories involved in clinical trials for early drug development in oncology. It notes the challenges of standardizing data from multiple local labs with different normal ranges and methods. It proposes capturing lab results and normal ranges directly on case report forms to facilitate data management and integration across sites.
The application of STDM in a no-profit and disease specific organisation - CD...Angelo Tinazzi
This document summarizes a presentation given by Angelo Tinazzi at the 2008 CDISC Italian-Speaking User Group Meeting in Milan. The presentation discusses the application of SDTM at SENDO Tech, a non-profit clinical research organization focused on oncology drug development. SENDO implements SDTM using a hybrid approach, applying some SDTM standards within their clinical database and performing additional transformations and mappings in SAS post-processing to fully comply with SDTM. The presentation outlines SENDO's SDTM implementation challenges due to the heterogeneity of oncology data and describes their methods for mapping clinical data to SDTM domains and variables. It also provides examples of new domains SENDO has
Part 2 Deep Dive: Navigating the 2024 Slowdownjeffkluth1
Introduction
The global retail industry has weathered numerous storms, with the financial crisis of 2008 serving as a poignant reminder of the sector's resilience and adaptability. However, as we navigate the complex landscape of 2024, retailers face a unique set of challenges that demand innovative strategies and a fundamental shift in mindset. This white paper contrasts the impact of the 2008 recession on the retail sector with the current headwinds retailers are grappling with, while offering a comprehensive roadmap for success in this new paradigm.
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
At Techbox Square, in Singapore, we're not just creative web designers and developers, we're the driving force behind your brand identity. Contact us today.
Company Valuation webinar series - Tuesday, 4 June 2024FelixPerez547899
This session provided an update as to the latest valuation data in the UK and then delved into a discussion on the upcoming election and the impacts on valuation. We finished, as always with a Q&A
Brian Fitzsimmons on the Business Strategy and Content Flywheel of Barstool S...Neil Horowitz
On episode 272 of the Digital and Social Media Sports Podcast, Neil chatted with Brian Fitzsimmons, Director of Licensing and Business Development for Barstool Sports.
What follows is a collection of snippets from the podcast. To hear the full interview and more, check out the podcast on all podcast platforms and at www.dsmsports.net
Digital Marketing with a Focus on Sustainabilitysssourabhsharma
Digital Marketing best practices including influencer marketing, content creators, and omnichannel marketing for Sustainable Brands at the Sustainable Cosmetics Summit 2024 in New York
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
How to Implement a Real Estate CRM SoftwareSalesTown
To implement a CRM for real estate, set clear goals, choose a CRM with key real estate features, and customize it to your needs. Migrate your data, train your team, and use automation to save time. Monitor performance, ensure data security, and use the CRM to enhance marketing. Regularly check its effectiveness to improve your business.
Best practices for project execution and deliveryCLIVE MINCHIN
A select set of project management best practices to keep your project on-track, on-cost and aligned to scope. Many firms have don't have the necessary skills, diligence, methods and oversight of their projects; this leads to slippage, higher costs and longer timeframes. Often firms have a history of projects that simply failed to move the needle. These best practices will help your firm avoid these pitfalls but they require fortitude to apply.
❼❷⓿❺❻❷❽❷❼❽ Dpboss Matka Result Satta Matka Guessing Satta Fix jodi Kalyan Final ank Satta Matka Dpbos Final ank Satta Matta Matka 143 Kalyan Matka Guessing Final Matka Final ank Today Matka 420 Satta Batta Satta 143 Kalyan Chart Main Bazar Chart vip Matka Guessing Dpboss 143 Guessing Kalyan night
Event Report - SAP Sapphire 2024 Orlando - lots of innovation and old challengesHolger Mueller
Holger Mueller of Constellation Research shares his key takeaways from SAP's Sapphire confernece, held in Orlando, June 3rd till 5th 2024, in the Orange Convention Center.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
Discover timeless style with the 2022 Vintage Roman Numerals Men's Ring. Crafted from premium stainless steel, this 6mm wide ring embodies elegance and durability. Perfect as a gift, it seamlessly blends classic Roman numeral detailing with modern sophistication, making it an ideal accessory for any occasion.
https://rb.gy/usj1a2
Taurus Zodiac Sign: Unveiling the Traits, Dates, and Horoscope Insights of th...my Pandit
Dive into the steadfast world of the Taurus Zodiac Sign. Discover the grounded, stable, and logical nature of Taurus individuals, and explore their key personality traits, important dates, and horoscope insights. Learn how the determination and patience of the Taurus sign make them the rock-steady achievers and anchors of the zodiac.
Taurus Zodiac Sign: Unveiling the Traits, Dates, and Horoscope Insights of th...
THE DO’S AND DON’TS OF DATA SUBMISSION
1. Geneva Branch
THE DO’S AND DON’TS OF DATA
SUBMISSION
- Biometristi Italiani Associati – V Annual Congress
Università Bicocca – Milano - 24-25/10/2013
Angelo Tinazzi
Cytel Inc., Wilmington Del. USA
Succursale de Meyrin – Geneva – Switzerland
angelo.tinazzi@cytel.com
2. Cytel Inc. - Confidential
2
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Disclaimer
The information contained in this
presentation is based on personal
research of the author and does not
necessarily represent Cytel Inc..
Geneva Branch
3. Cytel Inc. - Confidential
3
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
4. Cytel Inc. - Confidential
4
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
Missing Variables and Mislabeled Variables
Datasets are presented in a way that remains
confusing despite diligent and repeated efforts to understand
the presentation
The problems these issues cause prevent even an initial
cursory verification of the primary and
secondary endpoints of the XXXXX trial let alone
any more sophisticated analysis
What Next
Conclusions
5. Cytel Inc. - Confidential
5
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Datasets Deficiency
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
6. Cytel Inc. - Confidential
6
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Geneva Branch
A Failed Submission
Datasets Deficiency
Agencies
A world of Standards
Variable
Name
Variable
Label
Type Decode
/Format
Origin
OCS1DT
Date of first
recurrence
Num
Derived See derved datasets
specs page 125
Date9
Comment
No link provided
Variable
Name
Variable
Label
Type Decode
/Format
Origin
OCS1DT
Date of first
recurrence
Num
Derived Actual date associated
with QOC1CD = 1.
FRE1SDT =
minimum FRE1SDT,
where FRE1SDT ≥ RNDT.
Date9
Comment
Variable FRE1SDT and RNDT are not in the same dataset
eCTD Rules
Meet the reviewer
What Next
Conclusions
7. Cytel Inc. - Confidential
7
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Geneva Branch
A Failed Submission
Datasets Deficiency
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
illogical Order
Conclusions
8. Cytel Inc. - Confidential
8
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A Failied Submission
Geneva Branch
A Failed Submission
Meet the
PDUFA V, 21st Century Review, CDER Data Standards, PhUSE/FDA and
ADaM: Getting It All Right; Steve Wilson.
PhUSE SDE - Durham, North Carolina. Thursday, April 18th, 2013
reviewer and
always be
«honest»
Clear
Communication
Create robust
Analysis Dataset
Specifications
Claritiy
Use plain
english
Traceability
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
9. Cytel Inc. - Confidential
9
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
Geneva Branch
A Failed Submission
Prescription Drug User Fee Act (PDUFA)
Part of the law for Food and Drug Administration
Safety Innovation Act (FDASIA)
Passed in 1992 allows FDA to collect fees from
Sponsors (User Fee Programme)
In return for meeting review performance goals
—eally works
R
Review time decrease by half (priority) and 37%
—
(standard)
Since 1993 over 1000 drugs were approved
Over 50% of new drugs are launching in US
compare to 8% pre-‐PDUFA
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
10. Cytel Inc. - Confidential
10
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
Geneva Branch
A Failed Submission
Prescription Drug User Fee Act (PDUFA)
—eauthorized for 2013-‐1017
R
—erformance Goals
P
“Review and act on 90% ….. Submissions in 10/6 months of
the 60 day filing date”
—
Improve the efficiency of human drug review
through required electronic submissions
standardization of electronic drug
application data
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
11. Cytel Inc. - Confidential
11
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
Geneva Branch
A Failed Submission
Prescription Drug User Fee Act (PDUFA)
High Quality Standard of Data
CDISC data is foundational pre-‐requisite
— akes possible the
M
— se of standard‐based review tools
U
Development of reusable analysis scripts
Analysis across submissions
— February 2012, FDA requested congress to make
In
standard data required for submissions
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
12. Cytel Inc. - Confidential
12
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
Prescription Drug User Fee Act (PDUFA)
Timeline
—ec 2012 – Draft Guidance on standards and format
D
of eSub
+12 Months – Final Guidance released
+36 Months – All new NDAs/BLAs to use CDISC
End 2015 / 2016 no more an option
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
13. Cytel Inc. - Confidential
13
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
14. Cytel Inc. - Confidential
14
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Agencies pushing for Standards
What about the other Agencies?
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
CDISC Interchange 2013
15. Cytel Inc. - Confidential
15
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
16. Cytel Inc. - Confidential
16
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
17. Cytel Inc. - Confidential
17
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
SDTM Version 3.1.2 Dec-2011
Amendment 1 to the SDTM V1.2 and SDTMIG
V3.1.2
New variables in DM (e.g. DTHDTC/DTHFL and
ACTARM) and AE (e.g. additional coding variables)
SDTM Version 3.1.3
Oncology (efficacy) domains (TU,TR,RS)
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
18. Cytel Inc. - Confidential
18
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
SDTM Version 3.1.4 (upcoming)
SS (Survival Status)
EX/EC Exposure Domains
New domains: IS/SR (Immunogenicity/Skin React),
PR (Procedure), DD (Death)
TD (Trial Disease Assessment)
HO (Healthcare Encounters)
AP (Associated Persons)
What’s new in draft SDTM IG 3.1.4, Nicola Tambascia,
28th June 2013, PhUSE SDE Basel
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
19. Cytel Inc. - Confidential
19
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
SDTM Version 3.1.5 (planned)
More Oncology Domains
More enanchements
Lab Findings (e.g. biomarkers)
More TA domains
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
20. Cytel Inc. - Confidential
20
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
ADaM Latest Release (2012-2013)
ADTTE for Time-to-Event Endpoints
ADAE for Adverse Events
Validation Checks
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
ADaM To come
General Occurrences
IG v1.1
ADaM Integration IG 1.0
ADaM Metatadata Guide
21. Cytel Inc. - Confidential
21
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Define.xml v2.0
Case Report Tabulation Data Definition
Specification, (CRT-DDS)
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
“A critical component of data submission is the
define file. A properly functioning define.xml file is an
important part of the submission of standardized
electronic datasets and should not be considered
optional”
“Additionally, sponsors should make certain that every
data variables code list, origin, and derivation is
clearly and easily accessible from the define file.
An insufficiently documented define file is a common
deficiency that reviewers have noted.”
Conclusions
22. Cytel Inc. - Confidential
22
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Define.xml v2.0
Specification for
describing data
sets (metadata)
Does not
describe how this
metadata should
be displayed;
display is not part
of the
standard
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
23. Cytel Inc. - Confidential
23
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Validation Rules
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
24. Cytel Inc. - Confidential
24
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Accepted Standards at FDA
Agencies
SDTM IG 3.1.3
ADaM IG 1.0
SEND 3.0
Define.xml 2.0
Validation Rules
(OpenCDISC 1.4.1)
http://www.fda.gov/forindustry/datastandards/studydatastandards/default.htm
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
25. Cytel Inc. - Confidential
25
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
A World of Clinical Standards - CDISC
Geneva Branch
A Failed Submission
Agencies
CDISC submission
In 2010, CDER received an average of over 650
datasets/week, with 23% of active NDAs
containing CDISC/SDTM data
In 2011 this number has increased to an average
39% in SDTM and 32% in ADaM
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
26. Cytel Inc. - Confidential
26
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Geneva Branch
A Failed Submission
The Electronic Common Technical Document (eCTD) allows for
the electronic submission of the Common Technical Document
(CTD) from applicant to regulator
The CTD describes the organization of modules, sections and
documents.
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
27. Cytel Inc. - Confidential
27
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Module 5: Clinical Study Reports
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
ADaM datasets,
Define.xml
ADaM SAS programs
SDTM datasets,
Define.xml, SDTM
annotated blank eCRF
Conclusions
28. Cytel Inc. - Confidential
28
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Geneva Branch
A Failed Submission
eCTD File Format
Protocol – pdf (i.e., study001-protocol.pdf)
SAP – pdf (i.e., sutdy001-sap.pdf)
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
eCRF – pdf (i.e., sutdy001-blankecrf.pdf)
What Next
SDTM – xpt (i.e., dm.xpt, ae.xpt, ds.xpt, and etc)
Conclusions
ADaM – xpt (i.e., adsl.xpt, adae.xpt, adtteos.xpt,
and etc)
SEND – xpt (i.e., dm.xpt, se.xpt, bw.xpt, and etc)
CSR – pdf (i.e., sutdy001-csr.pdf)
Define.xml – xml or pdf (i.e., define.xml/define.pdf)
ADaM SAS programs – txt (i.e., c-adsl-sas.txt)
Output SAS programs – txt (i.e., t-14-01-001-ds-
sas.txt )
29. Cytel Inc. - Confidential
29
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Geneva Branch
A Failed Submission
Naming Conventions
Lower case of letter from “a” to “z”
Number from “0” to “9” “-” hypen
No special character ( #, %, $ and etc)
File name should be less than or equal to 64
characters including the appropriate file
extension
The length of entire path of the file should
not exceed 230 characters.
(m5/datasets/study001/sdtm/ae.xpt)
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
30. Cytel Inc. - Confidential
30
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Geneva Branch
A Failed Submission
File Guideline
Version – 1.4 thru 1.7 are acceptable
Fonts
Standard : Arial, Courier New, Times Roman
Sizes : range from 9 to 12 point ( Times New
Roman 12-point font is recommended for
narrative text )
Page
Print area : 8.5 inches by 11 inches
Margin : at least ¾ inch
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
31. Cytel Inc. - Confidential
31
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
eCTD Rules
Geneva Branch
A Failed Submission
SAS XPT File Guidance
Length
Agencies
A world of Standards
Variable length is less than or equal to 8
eCTD Rules
Variable label is less than or equal to 40
Meet the reviewer
Dataset length is less than or equal to 8
Dataset label is less than or equal to 40
Dataset Size – less than 1 GB (LB1, LB2, and so
on)
The length of character variables should be
minimized (i.e., if the maximum length of
USUBJID is 20 character long, keep the length as
20, not 200)
What Next
Conclusions
32. Cytel Inc. - Confidential
32
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
A Failed Submission
Pre-NDA Meeting
The objective of this meeting is to obtain guidance on
certain aspects of the Sponsor’s plans for NDA
submission. Specifically, the Sponsor seeks
agreement related to activities that must be
undertaken prior to the final submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
33. Cytel Inc. - Confidential
33
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Pre-NDA Meeting
Does the FDA concur with the Sponsor’s plan
regarding the composition and format of the clinical
data submission for the XXXXXXX eCTD NDA?
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
Do not use «Open Question», always propose
solutions and ask for confirmation
34. Cytel Inc. - Confidential
34
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Top 7 CDER/CBER CDISC Issues
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
More details in the backup slides
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
35. Cytel Inc. - Confidential
35
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
CDER Common Data Standards Issues
A Failed Submission
May-2011: CDER published Common Data
Agencies
Standards Issues
Dec-2011: v1.1 is published
Issued by CDER to convey
Common Issues
Requests for future submissions
Study Data Specifications v2.0, July 18, 2012
http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements/Electro
nicSubmissions/ucm248635.htm
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
36. Cytel Inc. - Confidential
36
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
CDER Common Data Standards Issues
A Failed Submission
Sponsors should refer to the latest version of
Agencies
SDTM IG
Sponsors should refer to Amendment 1 to SDTM
V1.2
Sponsors should ensure that every data variable’s
codelist, origin and derivation is clearly and easily
accessible in define file
SDTM should be consistent with submitted analysis
datasets
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
37. Cytel Inc. - Confidential
37
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
CDER Common Data Standards Issues
A Failed Submission
Traceability
Understanding relationship between the analysis
results the analysis datasets and the SDTM
domains
Establishing the path between an element and its
immediate predecessor
Two levels:
Metadata traceability
Agencies
Relationship between an analysis result and analysis dataset(s)
Relationship of the analysis variable to its source dataset(s)
and variable(s)
Data point traceability
Predecessor record(s)
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
38. Cytel Inc. - Confidential
38
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
CDER Common Data Standards Issues
A Failed Submission
Traceability
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
39. Cytel Inc. - Confidential
39
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
CDER Common Data Standards Issues
Controlled Terminology
Use existing CDISC terminology
If available CDISC terminology is insufficient,
sponsors should create their own terminology
Documentation on sponsor-specific terminology
should be included in define.xml
http://www.cancer.gov/cancertopics/cancerlibrary/terminologyresources/cdisc
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
40. Cytel Inc. - Confidential
40
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
A Failed Submission
CDER Common Data Standards Issues
MedDRA and Common Dictionary
Sponsors should exactly follow spelling and case
MedDRA version should be consistent across
trials within the submission
Dictionary name and version should be
documented in define.xml
More details in the backup slides
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
41. Cytel Inc. - Confidential
41
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
A Failed Submission
PhUSE SDE; ADaM Review from a CDER Statistical
Reviewer's Perspective; Behrang (Ben) Vali. FDA
‘Traceability’ is the key for reviewers
Less is NOT more
ADaM appropriately emphasizes this
Derived Variables SHOULD ONLY exist in
ADaM datasets
SDTM Datasets SHOULD ONLY present the
observed data from the CRF
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
42. Cytel Inc. - Confidential
42
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Meet the reviewer
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
43. Cytel Inc. - Confidential
43
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
More Metadata Oriented
e.g. Results Metadata
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
Also addressed in the FDA Guidance «Semantic Interoperability»
44. Cytel Inc. - Confidential
44
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
The FDA/PhUSE Collaboration
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
45. Cytel Inc. - Confidential
45
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
The FDA/PhUSE Collaboration
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
46. Cytel Inc. - Confidential
46
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
The FDA/PhUSE Collaboration – Optimizing the Use of Data Standards
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
47. Cytel Inc. - Confidential
47
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
The FDA/PhUSE Collaboration – Optimizing the Use of Data Standards
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
48. Cytel Inc. - Confidential
48
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
Other PhUSE Initiatives
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
49. Cytel Inc. - Confidential
49
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
More requirements to come
The agency uses it to facilitate use of a
risk-based approach for the timely
identification of clinical investigator sites for
on-site inspection by CDER during the
review of marketing applications
Experiences in Preparing Summary Level Clinical Site Data
within NDA’s Submission for FDA’s Inspection Planning.
Xiangchen (Bob) Cui, PharmaSUG 2013
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
50. Cytel Inc. - Confidential
50
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
What Next
Geneva Branch
A Failed Submission
Data Sharing
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
51. Cytel Inc. - Confidential
51
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Conclusions
Communication, clarity and honesty play a key role
in data submission
Traceability
Use of Standards
There are still Regional Differences
(e.g. Japanese HA looks more closely at details)
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
52. Cytel Inc. - Confidential
52
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Conclusions
Communication, clarity and honesty play a key role
in data submission
Traceability
Use of Standards
There are still Regional Differences
(e.g. Japanese HA looks more closely at details)
Data Submission
Geneva Branch
A Failed Submission
Agencies
A world of Standards
eCTD Rules
Meet the reviewer
What Next
Conclusions
53. Cytel Inc. - Confidential
53
[A. Tinazzi]
THE DO’S AND DON’TS OF DATA SUBMISSION
Questions
New Geneva offices – November 2012
Geneva Branch
54. Cytel Inc. - Confidential
[A. Tinazzi]
54
THE DO’S AND DON’TS OF DATA SUBMISSION
More details on the following topics
• Top 7 CDER/CBER CDISC Issues
• CDER Common Data Standards Issues
Geneva Branch
55. Cytel Inc. - Confidential
[A. Tinazzi]
55
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
1. Waste of Space
i.e. actual length = 8, allotted length = 200
Impact on dataset size compounded by large number of
rows
In the CDISC IG, an example references a column
length of 200. It appears this example was taken to
heart by industry
2. Extras (Domains, Variables, SUPPQUAL)
Use common sense and discuss with review team on
whether all information in supp- datasets are necessary
(e.g. Initials)
If “important” variables (support key analyses) are
placed in SUPPQUAL, discuss with the review team
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
56. Cytel Inc. - Confidential
[A. Tinazzi]
56
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
3. Validation Errors
Validation process results in error log -> read it!
Errors and warnings that CAN be fixed, SHOULD
be fixed
Some errors/warnings will inherently exist because
of your study design
i.e. no baseline result, no exposure record
Others won’t
Don’t simply address and dismiss these errors in a
“Reviewer’s Guide”
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
57. Cytel Inc. - Confidential
[A. Tinazzi]
57
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
3. Validation Errors – Common Errors
Codelist mis-match for extensible codelists
End date is prior to start date
Required and expected variables should be present
in the dataset
Variable labels in the dataset should match CDISC
naming conventions
AE set to serious but no qualifier exists that has
been set to “Y”
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
58. Cytel Inc. - Confidential
[A. Tinazzi]
58
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
4. Extended Codelist
Submissions include codelists where variable
values are not included in the codelist
Incorrect define.xml
5. ISO Dates (YYYY-MM-DDThh:mm:ss)
Clarification needs to occur in CDISC IGs
regarding when to input times and when to
omit
If time was captured in CRFs, include in
tabulations data
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
59. Cytel Inc. - Confidential
[A. Tinazzi]
59
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
6. Traceability
No traceability between source data and datasets
Need linkage: CRF -> SDTM -> ADaM -> CSR
SDTM datasets should be created from CRFs
If instead CRFs -> Raw -> SDTM, your analysis (and
hopefully ADaM) datasets should be created from those same
SDTM datasets, not the raw datasets
Features exist in the ADaM standard that allow for traceability
of analyses to ADaM to SDTM
Creating SDTM and Analysis data from the raw data is
incorrect (especially when submitting only SDTM and
analysis data)
Raw data should create SDTM, and SDTM should then create
Analysis
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
60. Cytel Inc. - Confidential
[A. Tinazzi]
60
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
7. Inadequate Documentation
Often times not all aspects of the standard apply to
your study/submission
Submit supporting documentation in the form of a
“Reviewer’s Guide” to explain how the data
standard was implemented:
What is in the custom domains?
What is in the suppqual’s?
Insufficient codelists?
Unfixable errors/warnings and why?
Derivation of key analysis variables
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
61. Cytel Inc. - Confidential
[A. Tinazzi]
61
THE DO’S AND DON’TS OF DATA SUBMISSION
Top 7 CDER/CBER CDISC Issues
Reccomendations
Start implementing CDISC as soon as possible
Pre-‐NDA/BLA is too late
—
Pre-‐IND is the best time for planning
Communicate with FDA
—ollow FDA guidelines and recommendations (e.g.
F
CDER Data Standards Common Issues Document)
—ata validation errors and warning that CAN be
D
fixed, SHOULD be fixed
CDER/CBER’s Top 7 CDISC Standards Issues
Dhananjay Chhatre, eData Management Solutions Team, Office of Business Informatics CDER, U.S. FDA
Amy Malla, Review Management, CBER, U.S. FDA
Geneva Branch
62. Cytel Inc. - Confidential
[A. Tinazzi]
62
THE DO’S AND DON’TS OF DATA SUBMISSION
CDER Common Data Standards Issues
SDTM Datasets
SUPPQUAL
Should not be used as a waste basket
DM
Strongly preferred to use additional variables in
Amendment 1
DS
EPOCH should be used to distinguish between multiple
disposition events
If DEATH occurs, it should be documented in the last record
with the associated EPOCH
Geneva Branch
63. Cytel Inc. - Confidential
[A. Tinazzi]
63
THE DO’S AND DON’TS OF DATA SUBMISSION
CDER Common Data Standards Issues
SDTM Datasets
AE
Provide variables for MedDRA hierarchy
Sponsors should include all AEs, not only the
one caused by the study treatment
AESOC = MedDRA-defined, primary mapped
SOC
AEBODSYS = SOC used for analysis
Geneva Branch
64. Cytel Inc. - Confidential
[A. Tinazzi]
64
THE DO’S AND DON’TS OF DATA SUBMISSION
CDER Common Data Standards Issues
SDTM Datasets
Custom Domains
Only to be used for data that does not fit in a
published domain
LB
Ideal filesize < 400 megabytes
Larger files should be split according to LBCAT,
LBSCAT; Nonsplit dataset should also be
included
Discuss with your review division
Geneva Branch
65. Cytel Inc. - Confidential
[A. Tinazzi]
65
THE DO’S AND DON’TS OF DATA SUBMISSION
CDER Common Data Standards Issues
SDTM Datasets
Permissible variables that CDER expects to see
--BLFL (LB, VS, EG, Pharmacokinetics, Microbiology)
EPOCH
--DY and --STDY in SE and Findings
No imputations allowed
Dates in ISO 8601
Missing dates are missing dates
USUBJID
No leading or trailing spaces allowed
Should match across all datasets (SDTM, ADaM) on a
character basis
Geneva Branch