The CDISC Moonshot - Can we do it? Presented by FH-Prof. Dr. Jozef Aerts University of Applied Sciences FH Joanneum Graz, Austria

Similar documents
Less is more - A visionary View on the Future of CDISC Standards

SDTM Validation Rules in XQuery

CDISC Standards and the Semantic Web

SDTM-ETL. New features in version 3.2. SDTM-ETLTM: New features in v.3.2

SDTM-ETL 3.1 User Manual and Tutorial. Working with the WhereClause in define.xml 2.0. Author: Jozef Aerts, XML4Pharma. Last update:

SDTM-ETL 3.2 User Manual and Tutorial

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

Dataset-XML - A New CDISC Standard

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

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

SDTM-ETL 4.0 Preview of New Features

SDTM-ETL 3.1 User Manual and Tutorial

Define 2.0: What is new? How to switch from 1.0 to 2.0? Presented by FH-Prof.Dr. Jozef Aerts University of Applied Sciences FH Joanneum Graz, Austria

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

Lex Jansen Octagon Research Solutions, Inc.

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

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

SDTM-ETL 3.0 User Manual and Tutorial

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

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

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

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

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

PhUSE EU Connect Paper PP15. Stop Copying CDISC Standards. Craig Parry, SyneQuaNon, Diss, England

edify Requirements for Evidence-based Templates in Electronic Case Report Forms Marco Schweitzer, Stefan Oberbichler

Business & Decision Life Sciences

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

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

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

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

CDISC SDTM and ADaM Real World Issues

Introduction to Define.xml

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

R1 Test Case that tests this Requirement Comments Manage Users User Role Management

Now let s take a look

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

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

Standards Driven Innovation

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

Specification of a Cardiovascular Metadata Model: A Consensus Standard

AZ CDISC Implementation

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

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

Clinical Metadata Metadata management with a CDISC mindset

SDTM-ETL 3.0 User Manual and Tutorial

NCI/CDISC or User Specified CT

Towards a Fully Machine-Readable Protocol: The New ODM Extension for Trial Design / Protocol. Jozef Aerts XML4Pharma

esubmission - Are you really Compliant?

Lex Jansen Octagon Research Solutions, Inc.

Optimization of the traceability when applying an ADaM Parallel Conversion Method

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

Introduction to ADaM and What s new in ADaM

Creating Define-XML v2 with the SAS Clinical Standards Toolkit

Study Data Reviewer s Guide Completion Guideline

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

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

Traceability Look for the source of your analysis results

Multiple Graphical and Tabular Reports on One Page, Multiple Ways to Do It Niraj J Pandya, CT, USA

Towards a Fully Machine-Readable Protocol: The New ODM Extension for Trial Design / Protocol. Jozef Aerts XML4Pharma

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

A Taste of SDTM in Real Time

Xiangchen (Bob) Cui, Tathabbai Pakalapati, Qunming Dong Vertex Pharmaceuticals, Cambridge, MA

CDISC Public Webinar Standards Updates and Additions. 26 Feb 2015

What is high quality study metadata?

Material covered in the Dec 2014 FDA Binding Guidances

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

Legacy to SDTM Conversion Workshop: Tools and Techniques

SDTM Automation with Standard CRF Pages Taylor Markway, SCRI Development Innovations, Carrboro, NC

Define.xml 2.0: More Functional, More Challenging

Standards Metadata Management (System)

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

Updates on CDISC Standards Validation

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

warwick.ac.uk/lib-publications

define.xml: A Crash Course Frank DiIorio

Helping The Define.xml User

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

Standards Implementation: It Should be Simple Right? Thursday January 18, 2018

DIA 11234: CDER Data Standards Common Issues Document webinar questions

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

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

Linking Metadata from CDASH to ADaM Author: João Gonçalves Business & Decision Life Sciences, Brussels, Belgium

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

ADaM and traceability: Chiesi experience

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

A SDTM Legacy Data Conversion

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

An Alternate Way to Create the Standard SDTM Domains

Automation of SDTM Programming in Oncology Disease Response Domain Yiwen Wang, Yu Cheng, Ju Chen Eli Lilly and Company, China

How to write ADaM specifications like a ninja.

SAS Application to Automate a Comprehensive Review of DEFINE and All of its Components

OpenCDISC Validator 1.4 What s New?

PhUSE US Connect 2019

Why organizations need MDR system to manage clinical metadata?

SAS, XML, and CDISC. Anthony T Friebel XML Development Manager, SAS XML Libname Engine Architect SAS Institute Inc.

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

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

PharmaSUG 2014 PO16. Category CDASH SDTM ADaM. Submission in standardized tabular form. Structure Flexible Rigid Flexible * No Yes Yes

SAS Clinical Data Integration 2.6

Revision of Technical Conformance Guide on Electronic Study Data Submissions

Transcription:

1

The CDISC Moonshot - Can we do it? Presented by FH-Prof. Dr. Jozef Aerts University of Applied Sciences FH Joanneum Graz, Austria 2

CDISC has grown 3

The CDISC Moonshot The next great step 4

From the CDISC website Are these stages of a CDISC rocket? Oh no these are CDISC silos 5

From silos to rocket stages Most of our standards have their origin in the last century Are not according to "current state of the art" in (bio)medical informatics Have developed along the same lines and traditions we had almost 20 years ago Don't we need a modernization? 6

The CDISC ODM Standard 20 years old, only minor updates And some extensions (Define-XML, SDM-XML, Dataset-XML, CTR-XML) No support for: RESTful web services Flexible and complicated study designs Wearables, insideables Little support for electronic health records Based on the concept of "files" Who still needs data files? We need "data services" 7

ODM 2.0 - the first rocket stage Support for RESTful web services The data can be anyware - not necessarily in files Full integration of electronic health records We need some concepts that are also used by FHIR But clinical research is more complicated (protocol based) Downward compatible Can ODM and FHIR be one standard in 10 years from now? 8

CDISC controlled terminology "Lists" of terms with little of no links between them DIABP and SYSBP are as much related as DIABP with FRMSIZE - really? Refusal to use controlled terminology from the medical world LOINC UCUM ICDx SNOMED 9

An example using UMLS RESTful web services Diastolic BP parent Cardiac pump effectiveness child Height and Weight are not in this diagram! Weight gain Fatigue Nausea Abnorm. heart sounds Dysrhytmia Systolic BP Pulmonary edema Angina "DIABP" and "SYSBP" are related through e.g. "cardiac pump effectiveness" There is no way ever to find out using CDISC-CT alone 10

A LOINC example using UMLS RESTful web services Hepatitis ALB meas. parent LOINC 1751-7 Liver function test (panel) child Galactose Elim. Cap. Total Bilirubin Alkaline Phosph. Alanine Aminotransferase Aspartate Amino- transf. Direct bilirubin Indirect bilirubin Gamma Glutamyl Transpept. "ALB" and "BILI" are related through e.g. "Liver function test" There is no way ever to find out using CDISC-CT alone 11

Answer: Units How much cm is 1 inch? Does CDISC-CT know? http://www.xml4pharmaserver.com:8080/cdiscctservice/rest/ucumtransform/[in_i]/to/cm UCUM Transformation Web Services 12

Units How much is 1 "international unit" pro mg "supercompound" pro g pro kg of "chicken" pro hour in: "international unit" pro ounce "supercompound" pro g pro pound of "chicken" per day? Forget about doing this when using CDISC "units" 13

CDISC Controlled Terminology CT is our "rocket fuel" And we can't afford not to get the highest quality fuel If there is better fuel than "our own invented one", we need to use that Some of our "fuel" is OK, but the most important part isn't 14

SDTM / SEND / ADaM Two dimensional tables Breaking almost any rule of "good database design" Massive amount of data redundancy 30-40% of the variables could be removed Very limited amount of traceability (only through define.xml) Pretty bad (outdated) data model 15

Smart tools can replace data redundancy Reviewers should start using these tools Smart Dataset-XML Viewer 16

SDTM / SEND / ADaM Due to data redundancy and 2-D tables our submission standards have too much weight Like that, we will never reach the moon CDISC should never have given up first principles because of (silly) requests from reviewers who use completely outdated tools It is not too late to slim down SDTM/SEND/ADaM And we should start thinking about alternatives Some people do, but their work is mostly ignored 17

Is SDTM ready for the future? More and more trials with "wearables" and "insideables" "CRF free" Remote clinical trials without any "visits" But SDTM still requires us to submit VISITNUM Clinical trials with virtual sites Read Doug Bain's and Kai Langel's blogs (ClinPal) Shouldn't we rethink a good number of SDTM (outdated) assumptions? 18

Better / smarter validation tools Current process: External company Validation Software Result: 19

Better / smarter validation tools Current process: But you can always describe the false positives in the Reviewer's Guide isn't it? Result: External company Validation Software 20

The "Open Rules for CDISC Standards" Initiative FDA,PMDA,CDISC rules implemented as: Transparent rules Human-readable and machine-executable Use RESTful web services In future also using the SHARE API Updates/corrections over a RESTful web service No more "waiting for the next release" Anyone can develop his own validation system 21

"Open Rules for CDISC Standards" Example - Rule FDAC017 Already implemented in the "Smart Dataset-XML Viewer" http://xml4pharmaserver.com/rulesxquery/index.html 22

The final stage: landing on the moon On average, our spacecraft is circling 6 months (the review time) around the moon before landing The crew is told they are free to use any tools they brought with them, even when they are completely outdated 23

How can review be shortened without any loss of quality - even with quality increase Reviewers should not be allowed to use files anymore All submissions in a single (set of) database(s) E.g. native XML databases The database is the only allowed source of information CDISC volunteers can provide modern tools (e.g. opensource) to regulators that reviewers must at least use 24

Some are even reaching further Initiatives like: RDF Linked Data SDTM-IG in XML Protocol in XML Mostly not official CDISC activities (but shouldn't they?) But regulators are still extremely reluctant to even think about these 25

The Showstoppers Actions required Get rid of SAS-XPT Start mandating LOINC and UCUM Get rid of "not invented here" syndrome Help / convince / force regulatory authorities to use modern technologies 26

Regulators and the "cancer moonshot" FDA is expected to receive US $xx million from the "cancer moonshot" programm If they would invest a few % of that in modern technology (computers, non-relational databases, tools) they would make a huge step forward And the result could be: 27

Acknowledgements All volunteers that fight FOR getting things done better, simpler, more efficient AGAINST "not invented here", "do it as we always have done" mentality Photo credit: NASA/Kim Shiflett 28

Further Acknowledgements Anthony, Dave (2x), Frederic, Geoff, Kerstin, Lauren, Lex, Niels, Peter, Marcelina, Sally, Sam, Vojtech, My ehealth students at the university of applied sciences FH Joanneum in Graz Picture acknowledgements at: www.xml4pharma.com/london_interchange/acknowledgements.html 29

The next step? 30

Disclaimer None of the pictures in this presentation are owned by "PictureDesk", a Vienna-based "picture troll" company. PictureDesk has no rights to any of the pictures in this presentation. Almost all pictures come from either Flickr under a "Creative Commons License" or from NASA put in the public domain, or were reproduced with explicit permission. This presentation is in the public domain. You may use (parts of) it, except for legal action, or discredit the good name of CDISC, XML4Pharma, the University of Applied Science FH Joanneum, and/or Jozef Aerts By downloading this presentation, you agree to pay the sum of US$ 1,000,000 to XML4Pharma when using contents of this presentation for any legal action 31