CDISC (CDASH/SDTM) integration into OC/RDC

Slides:



Advertisements
Similar presentations
CLINTON W. BROWNLEY AMERICAN UNIVERSITY PH.D. CANDIDATE SEPTEMBER 2, 2009 BRIDGing CDASH to SAS: How Harmonizing Clinical Trial and Healthcare Standards.
Advertisements

Dimitri Kutsenko (Entimo AG)
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
What’s New with CDISC Wayne R. Kubick CDISC CTO.
CDISC ADaM 2.1 Implementation: A Challenging Next Step in the Process Presented by Tineke Callant
Quick tour of CDISC’s ADaM standard
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
Metadata Management – Our Journey Thus Far
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
7. German CDISC User Group Meeting Define.xml Generator ODM Validator (define.xml validation) 2010/03/11 Dimitri Kutsenko Marianne Neumann.
Harmonization of SHARPn Clinical Element Models with CDISC SHARE Clinical Study Data Standards Guoqian Jiang, MD, PhD Mayo Clinic On behalf of CDISC CEMs.
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
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
23 August 2015Michael Knoessl1 PhUSE 2008 Manchester / Michael Knoessl Implementing CDISC at Boehringer Ingelheim.
JumpStart the Regulatory Review: Applying the Right Tools at the Right Time to the Right Audience Lilliam Rosario, Ph.D. Director Office of Computational.
CBER CDISC Test Submission Dieter Boß CSL Behring, Marburg 20-Mar-2012.
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,
Contents Integrating clinical trial data Working with CROs
Implementation of a harmonized, report-friendly SDTM and ADaM Data Flow General by Marie-Rose Peltier Experience by Marie Fournier Groupe Utilisateurs.
Vertex and CDISC / MBC / 12March Vertex and CDISC Accomplishments and Strategy 12 March 2008 Lynn Anderson Associate Director Statistical Programming/Biometrics.
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 2 Octagon Research Solutions, Inc. Leading the Electronic Transformation of Clinical R&D ©
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
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.
Copyright © 2011, SAS Institute Inc. All rights reserved. Using the SAS ® Clinical Standards Toolkit 1.4 to work with the CDISC ODM model Lex Jansen SAS.
SDTM Validation Delaware Valley CDISC user network Ketan Durve Johnson and Johnson Pharmaceutical Reasearch and Development May 11 th 2009.
RCRIM Projects: Protocol Representation and CDISC Message(s) January 2007.
Implementation of CDISC Standards at Nycomed PhUSE, Basel (19-21 October 2009) Nycomed GmbH, Dr. B Traub CDISC Implementation at Nycomed.
Dave Iberson-Hurst CDISC VP Technical Strategy
CDASH – SDTM Mapping Kurt Hellstern
Overview of CDISC standards and use cases along the E2E data management process Dr. Philippe Verplancke ESUG Marlow, UK 27 May 2009.
How to improve quality control in a data conversion process? By extended usage of metadata! Dimitri Kutsenko Entimo AG - Berlin/Germany.
From PDF to RDF – Representing the CDISC Foundational Standards
The Use of Metadata in Creating, Transforming and Transporting Clinical Data Gregory Steffens Director, Data Management and SAS Programming ICON Development.
© 2011 Clinovo. All Rights Reserved. The contents of this document are confidential and proprietary to Clinovo 1 Clinovo 1208 E. Arques Avenue, Suite 114.
1 CDISC HL7 Project FDA Perspective Armando Oliva, M.D. Office of Critical Path Programs FDA.
Defining & Managing Data Elements and Permissible Values or CDISC Terminology - A Use Case BACUN Barrie Nelson.
April ADaM define.xml - Metadata Design Analysis Results Metadata List of key analyses (as defined in change order) Analysis Results Metadata per.
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.
MindMajix SAS Clinical TrainingSAS Clinical Training.
Metadata Driven Clinical Data Integration – Integral to Clinical Analytics April 11, 2016 Kalyan Gopalakrishnan, Priya Shetty Intelent Inc. Sudeep Pattnaik,
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.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
Clinical database management: From raw data through study tabulations to analysis datasets Thank you for your kind introduction, and the opportunity to.
Dave Iberson-Hurst CDISC VP Technical Strategy
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
Beyond regulatory submission - Standards Metadata Management Kevin Lee CDISC NJ Meeting at 06/17/2015 We help our Clients deliver better outcomes, so.
Accenture Accelerated R&D Standards Metadata Management – version control and its governance Kevin Lee CDISC NJ Meeting at 01/28/2015 We help our Clients.
Why use CDISC for trials not submitted to regulators?
MAKE SDTM EASIER START WITH CDASH !
Creating ADaM Friendly Analysis Data from SDTM Using Meta-data by Erik Brun & Rico Schiller (CD ) H. Lundbeck A/S 13-Oct
Traceability between SDTM and ADaM converted analysis datasets
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
Safety Analytics Workshop – Computational Science Symposium 2019
CDISC 360: Evolving our standards towards end to end automation
Presentation transcript:

CDISC (CDASH/SDTM) integration into OC/RDC Generation of real-time SDTM datasets and metadata through a generic SDTM converter mechanism Peter Van Reusel Business Unit Director CRO Services Business & Decision Life Sciences Tel +32 2 774 11 00 Fax +32 2 774 11 99 Mobile +32 476 54 59 17 peter.vanreusel@businessdecision.com Sint-Lambertusstraat 141 Rue Saint-Lambert 1200 Brussels www.businessdecision-lifesciences.com

Agenda Introduction CDASH/SDTM in OC/RDC SDTM Converter Mechanism 1 Introduction 2 CDASH/SDTM in OC/RDC 3 SDTM Converter Mechanism 4 Conclusion

Agenda Introduction CDASH/SDTM in OC/RDC SDTM Converter Mechanism 1 Introduction 2 CDASH/SDTM in OC/RDC 3 SDTM Converter Mechanism 4 Conclusion

CDISC organization Clinical Data Interchange Standards Consortium CDISC started in 1999 Is a non-profit organization Data models are created by industry volunteers Mission: to develop & support global, platform-independent data standards that enable information system interoperability to improve medical research & related areas of healthcare http://www.cdisc.org

CDISC models Acronym Title Use ODM LAB PRG Clinical Data Acquisition Standards Harmonization Data Collection Study Data Tabulation Model Content Analysis Dataset Model Case Report Tabulation Data Definition Specification Metadata ODM Operational Data Model Format LAB Clinical Laboratory Model PRG Protocol Representation Group CDASH B R I D G / HL7 SDTM ADaM Define.xml CRT-DDS

Near Term Approach: Legacy Data Conversion

Longer Term Approach: Global CDISC Integration

Agenda Introduction CDASH/SDTM in OC/RDC SDTM Converter Mechanism 1 Introduction 2 CDASH/SDTM in OC/RDC 3 SDTM Converter Mechanism 4 Conclusion

CDISC integration objectives To integrate global CDISC standards in OC/RDC Use CDISC nomenclature across the CDM system Ensure metadata consistency Use of CDISC controlled terminology Avoid additional data conversion steps Generate SDTM data as of study start Production of real-time SDTM deliverables Facilitate generation of ADaM datasets based on SDTM Allow CDISC consistency checking early in the process

CDISC data model SDTM domains Special purpose domains: General class domains: Findings: Events: Interventions: SUPPQUAL: External data upload: New domain: Trial Design RELREC e.g. CO, DM e.g. VS e.g. AE e.g. EX e.g. SUPPAE, -BA, -DM, -EX, -LB e.g. LB e.g. BA

OC/RDC system set-up Metadata definition: Create metadata specifications OC level: Define DCM, DCI and DCI books External data upload RDC level: Patient data entry OC extract creation and output

Additional CDISC integration set-up Metadata definition: Create metadata specifications OC level: Use CDASH/SDTM variables Define DCM, DCI and DCI books External data upload RDC level: Patient data entry OC extract creation and output SDTM converter level: CDISC (CDASH/SDTM) standards library and business rules SDTM converter mechanism Generation of SDTM datasets, metadata and reports/warnings

OC level: Use CDASH/SDTM variables Define in Global Library: DVGs (SDTM controlled terminology/SAS formats) Questions (CDASH/SDTM variables) Questions groups (SAS datasets)

OC level: Define DCM, DCI & DCI books Define at the study level: DCM (collection of QGs) DCI (collection of DCMs) DCI books Create default view definitions (O*C extracts)

OC level: set-up rules & naming conventions Kept to a minimum Use CDASH/SDTM variables ONLY except – Rename &DOMAIN.TESTCD  &DOMAIN.TSTC Rename &DOMAIN.ORRES  &DOMAIN.ORES Use of extended attribute DVG_LONG_VALUE in &DOMAIN.TSTC (Testcode) to populate TEST All Non CDASH/Non SDTM variables populate SUPP datasets Potential use of extended attributes for numeric values (to produce SDTM+)

Data flow for e.g. Demography

Data flow for e.g. Demography

Agenda Introduction CDASH/SDTM in OC/RDC SDTM Converter Mechanism 1 Introduction 2 CDASH/SDTM in OC/RDC 3 SDTM Converter Mechanism 4 Conclusion

SDTM Conversion – High Level Perspective

Data flow for Demography

Data flow for Adverse Experiences

SDTM converter input: CDISC standards library Used by SDTM converter to interpret standard source or system variables i.e., SDTM or CDASH or OC system Metadata SDTM variables Metadata CDASH variables Metadata OC system variables

SDTM converter input: CDISC standards library Used by SDTM converter to interpret standard source or system variables i.e., SDTM, CDASH or OC system

SDTM converter input: Short list of business rules Defines generic SDTM conversion choices:

SDTM converter input: Parameter database Define project paths in a Central Parameter Table

SDTM converter input: Short list of default values A default (and editable) value table is used by the SDTM converter DCM Name QG Domain Variable Default Value EX1EX1 EX1 EX EXTRT “DRUG A” EXDOSE 20 EX2EX2 EX2 “DRUG B” 40 ………..

SDTM conversion – high level perspective

SDTM converter mechanism What is it? A mechanism based on Base SAS code (DI Studio) Functionalities: ISO 8601 data transformation Automatic transpose for findings Global transformations Domain specific transformations Generate SEQ variable Extract TEST from DVG for TESTCD Create Supplementary Datasets Create Comment Dataset Create SDTM Dataset …

ISO 8601 date transformation Rule - Converts variables ending with DAT & TIM in ISO 8601 date format

Automatic transpose for findings Rule - Transposes finding variables TESTCD and corresponding results. Puts records of variables ending with the same number together

Global transformations Rule - Compute values based on rules in business rule sheet USUBJID   О STUDY||SUBJID STUDY||SITEID||SUBJID include custom macro

Domain specific transformations Rule - Populate variables with values specified in default value sheet EXDOSE EXTRT Variable 40 EX EX2 EX2EX2 “DRUG B” 20 EX1 EX1EX1 “DRUG A” Default Value Domain QG DCM Name

Generate SEQ variable Rule – Generate SEQ variable based on Keys specified in Table Level Metadata in the CDISC Standards Library Rule - For custom domains use the following: Event: --TERM, -- STDTC Intervention: --TRT, --STDTC Finding: --TESTCD, VISITNUM, TPTNUM, --DTC

Extract TEST from DVG for TESTCD Rule - Populates TEST by extracting DVG long value of TESTCD Vertical structure: Horizontal structure:

Create Supplementary Datasets Rule - Non-CDASH/Non-SDTM/Non-OC System variables to populate supplementary datasets

Create Comment Dataset Rule - Collect comments in OC in &DOMAIN._COVAL variable

Create SDTM Dataset Rule – Use variable level attributes from the CDISC standards library

SDTM conversion – high level perspective

SDTM converter output: Reports and Warnings Data profile reports of the SDTM generated datasets.

SDTM converter output: Reports and Warnings Warning reports: includes basic checks for conformance with the CDISC domain models: Including all required and expected variables as columns in a domain Using CDISC-specified standard variable names Using CDISC-specified data types for all variables Etc. These conformance checks are a subset of the complete set of CDISC SDTM compliance checks

SDTM converter output: Metadata Table Metadata Variable Metadata Dataset Name Dataset Label Class Structure Purpose Keys Location Variable Name Variable Label Type Height Controlled Terminology Origin Role Comments Controlled Terminology Value Level Metadata Code Value Code Text Source Variable Value Label Type Controlled Terminology Origin Role Comments Computational Algorithms Reference Name Computation Method

Agenda Introduction CDASH/SDTM in OC/RDC SDTM Converter Mechanism 1 Introduction 2 CDASH/SDTM in OC/RDC 3 SDTM Converter Mechanism 4 Conclusion

Conclusion Maximize use of CDASH and SDTM variables Use CDISC controlled terminology Through smart set-up in OC, automate SDTM generation through a generic SDTM converter mechanism No SDTM conversion required in OC/RDC; occurs outside OC/RDC No additional programming is required within OC Real-time SDTM datasets and metadata, ready for analysis

Thank you for your attention Peter Van Reusel Business Unit Director CRO Services Business & Decision Life Sciences Tel +32 2 774 11 00 Fax +32 2 774 11 99 Mobile +32 476 54 59 17 peter.vanreusel@businessdecision.com Sint-Lambertusstraat 141 Rue Saint-Lambert 1200 Brussels www.businessdecision-lifesciences.com