CDISC submission standard

Slides:



Advertisements
Similar presentations
Dimitri Kutsenko (Entimo AG)
Advertisements

Principal Statistical Programmer Accovion GmbH, Marburg, Germany
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
UC5:Assigning of Epoch after treatment discontinuation (NS)
Documentation and example Richard Senecal, Senior Principal Programmer NJ CDISC Users Group Merck/Summit, September 19, 2013 define.xml.v2 row-level metadata.
Quick tour of CDISC’s ADaM standard
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
ADaM Standards Wouter van Wyk. Why ADaM –SDTM purpose is to provide collected data Not designed for ease of analysis –ADaM purpose is to provide data.
CDISC (CDASH/SDTM) integration into OC/RDC
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Copyright © 2010, SAS Institute Inc. All rights reserved. Define.xml - Tips and Techniques for Creating CRT - DDS Julie Maddox Mark Lambrecht SAS Institute.
Monika Kawohl Statistical Programming Accovion GmbH Tutorial: define.xml.
CDISC and how Stata can help us implement it
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
CBER CDISC Test Submission Dieter Boß CSL Behring, Marburg 20-Mar-2012.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
PhUSE SDE, 28-May A SAS based Solution for define.xml Monika Kawohl Statistical Programming Accovion.
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
ODM-SDTM mapping Nicolas de Saint Jorre, XClinical June 20, 2008 French CDISC User Group Bagneux/Paris © CDISC & XClinical, 2008.
Antje Rossmanith, Roche 14th German CDISC User Group, 25-Sep-2012
CDASh : A Primer and Guide to Implementation
1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion:
Overview and feed-back from CDISC European Interchange 2008 (From April 21 st to 25 th, COPENHAGEN) Groupe des Utilisateurs Francophones de CDISC Bagneux.
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
HL7 RCRIM Meeting: 9 January 2007 CDISC-RCRIM Vocab Update: Related CDISC Terminology Projects Bron Kisler, CDISC Terminology Program Director
15th Informal US MedDRA User Group Meeting, October 28, 2011 Slide 1 Double the Impact with Half the Work: Linking MedDRA and WHO Drug Indication coding.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
Alun, living with Parkinson’s disease QS Domain: Challenges and Pitfalls Knut Müller UCB Biosciences Conference 2011 October 9th - 12th, Brighton UK.
RCRIM Projects: Protocol Representation and CDISC Message(s) January 2007.
Dave Iberson-Hurst CDISC VP Technical Strategy
Overview of CDISC standards and use cases along the E2E data management process Dr. Philippe Verplancke ESUG Marlow, UK 27 May 2009.
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
Eurostat 4. SDMX: Main objects for data exchange 1 Raynald Palmieri Eurostat Unit B5: “Central data and metadata services” SDMX Basics course, October.
Template provided by: “posters4research.com” Challenges and Solutions for Mapping Pathology Data to SEND Mike Wasko, Rich Buchanan, Fred Mura, and Laura.
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
1. © CDISC 2014 Stetson Line, Team Lead CDISC Intrachange SDTM Rules Sub-team Update.
Why eCTD & CDISC? GSG-US, Inc. Chaeyong Chang March, 2012.
How good is your SEND data? Timothy Kropp FDA/CDER/OCS 1.
How Good is Your SDTM Data? Perspectives from JumpStart Mary Doi, M.D., M.S. Office of Computational Science Office of Translational Sciences Center for.
Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism CDISC (CDASH/SDTM) integration into OC/RDC Peter Van Reusel.
Mark Wheeldon, Formedix CDISC UK Network June 7, 2016 PRACTICAL IMPLEMENTATION OF DEFINE.XML.
Most Common Issues in Define.xml files
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
A need for prescriptive define.xml
Dave Iberson-Hurst CDISC VP Technical Strategy
Monika Kawohl Statistical Programming Accovion GmbH
Practical Implementation of Define.xml
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
CPT and Disclosure: Connecting Critical Processes
Quality Control of SDTM Domain Mappings from Electronic Case Report Forms Noga Meiry Lewin, MS Senior SAS Programmer The Emmes Corporation Target: 38th.
Patterns emerging from chaos
CDISC UK Network Jun-16 – Welwyn
A SAS macro to check SDTM domains against controlled terminology
To change this title, go to Notes Master
Fabienne NOEL CDISC – 2013, December 18th
SDTMs in Medical Devices A First Attempt
define.xml.v2 row-level metadata
CPT and Disclosure: Connecting Critical Processes
Visualizing Subject Level Data in Clinical Trial Data
An FDA Statistician’s Perspective on Standardized Data Sets
PhUSE: Pooling WHODrug B3 Format
PhilaSUG Spring Meeting June 05, 2019
Presentation transcript:

CDISC submission standard CDISC SDTM unfolding the core model that is the basis both for the specialised dataset templates (SDTM domains) optimised for medical reviewers CDISC Define.xml metadata describing the data exchange structures (domains)

Background: CDISC SDTM’s fundamental model for organizing clinical data General classes Generic structure • Unique identifiers • Topic variable or parameter • Timing Variables • Qualifiers. Interventions Findings Observation Subject SDTM Domains Events (dataset structures) CM EX EG Subject Attributions Tables A place holder for additional subject data that does not “fit” within the other models ATSUBJ – designed to support subject level linking ATRECORD – designed to support record level linking (e.g. subject visit level, subject datetime event level, etc.) Submission Summary Information Model Model that contains information regarding the study type, title, phase, design, number of subjects, etc. RELATES A model that links/associates multiple observations within &/or across domains. EPOCH A model that contains the planned study interval of time points (e.g. “periods”, “cycles”, & “phase”) IE LB PE AE DS … The patient/subject focused information model of the clinical ‘reality’ (general classes of observations on subjects: interventions, findings, events). This model has been developed by CDISC/SDS team and exist today only as a text description.

CDISC SDTM’s Domains Interventions Events Findings Other Exposure AE Labs Incl Excl* Demog ConMeds Disposition Vitals Subj Char* RELATES* SUPPQUAL* Subject Attributions Tables A place holder for additional subject data that does not “fit” within the other models ATSUBJ – designed to support subject level linking ATRECORD – designed to support record level linking (e.g. subject visit level, subject datetime event level, etc.) Submission Summary Information Model Model that contains information regarding the study type, title, phase, design, number of subjects, etc. RELATES A model that links/associates multiple observations within &/or across domains. EPOCH A model that contains the planned study interval of time points (e.g. “periods”, “cycles”, & “phase”) Subst Use* MedHist PhysExam ECG Comments* Study Design* QS*, MB* CP*, DV* * New in Version 3 Study Sum* From CDISC SDTM Overview & Impact to AZ, 2004, by Dan Godoy, presented at the first CDISC/SDM meeting 20 October 2004

Basic Concepts in CDISC SDTM Observations and Variables The SDTM provides a general framework for describing the organization of information collected during human and animal studies. The model is built around the concept of observations, which consist of discrete pieces of information collected during a study. Observations normally correspond to rows in a dataset. Each observation can be described by a series of named variables. Each variable, which normally corresponds to a column in a dataset, can be classified according to its Role. Observations are reported in a series of domains, usually corresponding to data that were collected together. A domain is defined as a collection of observations with a topic-specific commonality about a subject. From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Variable Roles A Role determines the type of information conveyed by the variable about each distinct observation and how it can be used. A common set of Identifier variables, which identify the study, the subject (individual human or animal) involved in the study, the domain, and the sequence number of the record. Topic variables, which specify the focus of the observation (such as the name of a lab test), and vary according to the type of observation. A common set of Timing variables, which describe the timing of an observation (such as start date and end date). Qualifier variables, which include additional illustrative text, or numeric values that describe the results or additional traits of the observation (such as units or descriptive adjectives). The list of Qualifier variables included with a domain will vary considerably depending on the type of observation and the specific domain Rule variables, which express an algorithm or executable method to define start, end, or looping conditions in the Trial Design model. From the Study Data Tabulation Model document

Example: Mapping Vital Signs From CDISC End to End Tutorial - DIA Amsterdam 7 Nov 2004, Pierre-Yves Lastic, Sanofi-Aventis and Philippe Verplancke, CRO24

CDISC’s Submission standard Underlying Models: CDISC Study Data Tabulation Model Clinical Observations General Classes: Events, Findings, Interventions Trial Design Model Elements, Arms, Trial Summary Parameters etc. Domains, submission dataset templates: CDISC SDTM Implementation Guide

CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

Identifiers of records per dataset and study CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains Decoded format, that is, the textual interpretation of whichever code was selected from the code list. Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected Identifiers of records per dataset and study CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

Controlled Terminologies CT Packages for SDTM e. g Controlled Terminologies CT Packages for SDTM e.g. Codelist Patient Positiion and proposed terms for VSTESTCD CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

Controlled Terminologies CT Packages for SDTM e. g Controlled Terminologies CT Packages for SDTM e.g. Codelist Patient Positiion and proposed terms for VSTESTCD CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

Controlled Terminologies CT Packages for SDTM e. g Controlled Terminologies CT Packages for SDTM e.g. Codelist Patient Positiion and proposed terms for VSTESTCD CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards define.xml Case Report Tabulation Data Definition Specification to submit the Data Definition Document (submission dataset metadata) in a machine-readable format

called „define.xml“) will replace define.pdf in e-CTD Controlled Terminologies CT Packages for SDTM e.g. Codelist Patient Positiion and proposed terms for VSTESTCD CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains CRTDDS = Case Report Tabulation Data Description Specification (= an ODM extension, formerly called „define.xml“) will replace define.pdf in e-CTD ItemGroup Item ValueList (in an item) Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected <ItemDef OID="SU.SUTRT.SMKCLASS" Name="SMKCLASS" DataType="integer" Length="8“ Origin="CRF Page" Comment="Substance Use CRF Page 4" def:Label="Smoking classification"> <CodeListRef CodeListOID="SMKCLAS" /> </ItemDef> <CodeList OID="SMKCLAS" Name="SMKCLAS" DataType="integer"> <CodeListItem CodedValue="1"> <Decode> <TranslatedText xml:lang="en">NEVER SMOKED</TranslatedText> </Decode> </CodeListItem> <CodeListItem CodedValue=“2"> <Decode> <TranslatedText xml:lang="en">SMOKER</TranslatedText> </Decode> </CodeListItem> <CodeListItem CodedValue=“3"> <Decode> <TranslatedText xml:lang="en">EX SMOKER</TranslatedText> </Decode> </CodeListItem> define.XML as machine-readable replacement for define.pdf (= prevoius called Data Defintion Tables in item 11) > Needs complete syntax to reference external lists From Randy Levins presentation, see http://www.cdisc.org/publications/interchange2005/session8/JANUS2005.pdf > And to reference sponsor defined code lists cross studies CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards define.xml Case Report Tabulation Data Definition Specification to submit the Data Definition Document (submission dataset metadata) in a machine-readable format

SDTM fundemantal mode is also the basis for: CDISC SDTM Domains SAS Dataset implementations (dataset templates) e.g. Vital Signs domains SDTM fundemantal mode is also the basis for: SEND Domains for Nonclinical Data (generated from animal toxicity studies) Future domains of derived data, capturing metadata to describe derivations and analyses. Optimisations for Data Exchange per study and for Medical Reviewers to easier understand data Specific principles and standards such as ISO8601 for dates/timings, and both Original & Standard values expected CDISC SDTM fundamental model for organizing data collected in clinical trials Concept of Observations, which consist of discrete pieces of information collected during a study described by a series of named variables. General Classes of Observations: Events, Findings, Interventions Variable Roles: determines the type of information conveyed by the variable about each distinct observation: Topic variables, Identifier variables, Timing variables, Rule variables, and Qualifiers (Grouping, Result, Synonym, Record, Variable) General principles and standards

Basic Concepts in CDISC/SDTM Subclasses of Qualifiers Grouping Qualifiers are used to group together a collection of observations within the same domain. Examples include --CAT, --SCAT, --GRPID, --SPEC, --LOT, and --NAM. The latter three grouping qualifiers can be used to tie a set of observations to a common source (i.e., specimen, drug lot, or laboratory name, respectively). Synonym Qualifiers specify an alternative name for a particular variable in an observation. Examples include --MODIFY and --DECOD, which are equivalent terms for a --TRT or --TERM topic variable, and --LOINC which is an equivalent term for a --TEST and --TESTCD. Result Qualifiers describe the specific results associated with the topic variable for a finding. It is the answer to the question raised by the topic variable. Examples include --ORRES, --STRESC, and --STRESN. Variable Qualifiers are used to further modify or describe a specific variable within an observation and is only meaningful in the context of the variable they qualify. Examples include --ORRESU, --ORNHI, and --ORNLO, all of which are variable qualifiers of --ORRES: and --DOSU, --DOSFRM, and --DOSFRQ, all of which are variable qualifiers of --DOSE. observation and is Record Qualifiers define additional attributes of the observation record as a whole (rather than describing a particular variable within a record). Examples include --REASND, AESLIFE, and allother SAE flag variables in the AE domain; and --BLFL, --POS and --LOC. From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Variable Roles Topic variables which specify the focus of the observation (such as the name of a lab test), and vary according to the type of observation. Grouping qualifiers are used to group together a collection of observations within the same domain. Examples include --CAT, --SCAT, --GRPID, --SPEC, --LOT, and --NAM. The latter three grouping qualifiers can be used to tie a set of observations to a common source (i.e., specimen, drug lot, or laboratory name, respectively) Synonym Qualifiers specify an alternative name for a particular variable in an observation. Examples include --MODIFY and --DECOD, which are equivalent terms for a --TRT or --TERM topic variable, and --LOINC which is an equivalent term for a --TEST and --TESTCD. Qualifier variables Observation Record Topic Grouping Qual Synonym Qual From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Variable Roles Identifier variables which identify the study, the subject (individual human or animal) involved in the study, the domain, and the sequence number of the record. Timing variables which describe the timing of an observation (such as start date and end date). Result Qualifiers describe the specific results associated with the topic variable for a finding. It is the answer to the question raised by the topic variable. Depending on the type of result (numeric or character) different variables are being used. Includes variables for both original (as supplied values) and for standardised values (for uniformity). Examples include --ORRES, --STRESC, and --STRESN. Qualifier variables Observation Record Topic Identifier Timing Result Qual From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Variable Roles Variable Qualifiers are used to further modify or describe a specific variable within an observation and is only meaningful in the context of the variable they qualify. Examples include --ORRESU, --ORNHI, and --ORNLO, all of which are variable qualifiers of --ORRES: and --DOSU, --DOSFRM, and --DOSFRQ, all of which are variable qualifiers of --DOSE. Indictors where the results falls with respect to reference range Qualifier variables Observation Record Topic Identifier Timing Result Qual Variable Qual From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Variable Roles Record Qualifiers define additional attributes of the observation record as a whole (rather than describing a particular variable within a record). Examples include --REASND, AESLIFE, and allother SAE flag variables in the AE domain; and --BLFL, --POS and --LOC. Qualifier variables Observation Record Topic Identifier Timing Result Qual Variable Qual Record Qual From the Study Data Tabulation Model document

Basic Concepts in CDISC/SDTM Subclasses of Qualifiers Topic variables Identifier variables Timing variables Rule variables Qualifier variables Grouping Qualifiers Result Qualifiers Synonym Qualifiers Record Qualifiers Variable Qualifiers Observation Record Topic Identifier Timing Result Qual Variable Qual Record Qual Grouping Qual Synonym Qual From the Study Data Tabulation Model document