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

Similar documents
SDTM domains by query - is it possible?

Standards Metadata Management (System)

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

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

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

AUTOMATED CREATION OF SUBMISSION-READY ARTIFACTS SILAS MCKEE

Optimization of the traceability when applying an ADaM Parallel Conversion Method

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

Helping The Define.xml User

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

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

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

SDTM Validation Rules in XQuery

What is high quality study metadata?

Lex Jansen Octagon Research Solutions, Inc.

Standardizing FDA Data to Improve Success in Pediatric Drug Development

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

Pharmaceutical Applications

Standardising The Standards The Benefits of Consistency

Automated Creation of Submission-Ready Artifacts Silas McKee, Accenture, Pennsylvania, USA Lourdes Devenney, Accenture, Pennsylvania, USA

Specification of a Cardiovascular Metadata Model: A Consensus Standard

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

DADC Submission Instructions

Improving CDISC SDTM Data Quality & Compliance Right from the Beginning

Test Procedure for (c) Record Demographics

AZ CDISC Implementation

Welcome / Introductions

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

Bay Area CDISC Network: PhUSE Working Group for Inspection Site Selection Data Standards

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

Data Standards with and without CDISC

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

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

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

ADaM and traceability: Chiesi experience

Improving Metadata Compliance and Assessing Quality Metrics with a Standards Library

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

CDISC Standards and the Semantic Web

The application of SDTM in a disease (oncology)-oriented organization

DIA 11234: CDER Data Standards Common Issues Document webinar questions

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

ADaM for Medical Devices: Extending the Current ADaM Structures

Mapping and Terminology. English Speaking CDISC User Group Meeting on 13-Mar-08

PharmaSUG Paper PO21

Standards Driven Innovation

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

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

Reducing SAS Dataset Merges with Data Driven Formats

DCDISC Users Group. Nate Freimark Omnicare Clinical Research Presented on

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

How to write ADaM specifications like a ninja.

Out-of-the-box %definexml

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

Study Data Reviewer s Guide Completion Guideline

ADaM Reviewer s Guide Interpretation and Implementation

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

Considerations on creation of SDTM datasets for extended studies

Overview of HASH Objects Swarnalatha Gaddam, Cytel Inc. Hyderabad, India

PharmaSUG Paper PO22

Introduction to ADaM and What s new in ADaM

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

An Efficient Solution to Efficacy ADaM Design and Implementation

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

Terminology Harmonization

What is the ADAM OTHER Class of Datasets, and When Should it be Used? John Troxell, Data Standards Consulting

SDTM-ETL 4.0 Preview of New Features

Updates on CDISC Standards Validation

Advanced Visualization using TIBCO Spotfire and SAS

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

Cost-Benefit Analysis of Retrospective vs. Prospective Data Standardization

Metadata and ADaM.

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

Riepilogo e Spazio Q&A

Creating a Data Shell or an Initial Data Set with the DS2 Procedure

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

2013 Local Arts Agency Salary & Benefits Summary EXECUTIVE DIRECTOR / PRESIDENT / CEO

Study Data Reviewer s Guide. FDA/PhUSE Project Summary

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

MethodDefs, ValueLists and WhereClauses:

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

Page 1 of 6 SURVEY: PROJECT TECH

Lab Results Interface (LRI) The Flexible Implementation Guide (IG) Standards and Interoperability Framework Initiative (ONC) Ken McCaslin, FHL7

Dataset-XML - A New CDISC Standard

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

PharmaSUG Paper AD21

PharmaSUG Paper DS24

An Alternate Way to Create the Standard SDTM Domains

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

THE 2018 CENTER FOR DIVERSITY IN PUBLIC HEALTH LEADERSHIP TRAINING PROGRAMS ONLINE GUIDLINES

Global Checklist to QC SDTM Lab Data Murali Marneni, PPD, LLC, Morrisville, NC Sekhar Badam, PPD, LLC, Morrisville, NC

Robust approach to create Define.xml v2.0. Vineet Jain

Conversion of Company Standard Trial Data to SDTM

Step by Step to PROC CDISC and More

Data Management Problems and Possible Solutions. My Background. Problems in Managing Data 6/8/2016

A Linked Data Translation Approach to Semantic Interoperability

CRF Design for Data Standards. David A. Scocca

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

Traceability Look for the source of your analysis results

New Approach to Graph Databases

Introduction to Define.xml

Transcription:

Towards better data Johannes Ulander Standardisation and Harmonisation Specialist S-Cubed PhUSE SDE Beerse, 2017-11-28 Agenda What is data? Current state of submissions Introduction to linked data and graph db How does this improve quality? Summary 1

Disclaimer No magic tricks All similarities to actual data is intentional Everything is actual data CDISC pilot submission available at http://www.cdisc.org But sometimes I ve made it power point friendly No data was harmed during the making of this presentation How we think of data 2

1/8/18 Is this the data we re looking for? Current state of submissions FDA @ PhUSE CSS 2016 From a presentation by Mary Doi, M.D., M.S. (FDA CDER) FDA @ PhUSE CSS 2017 From a presentation by Crystal Allard, Special Assistant to the Director Office of Computational Science 3

Rate of Change 10 9 8 7 6 5 4 3 2 1 0 1 2 3 4 5 6 7 Series1 7 Left and Right Sides We map from here to datasets inconsistently We design here without fully understanding the right hand side 8 4

We Need Control Constant new versions Rate-of-change of versions Precision Which version am I using? Visibility What changed? When did it change? What is the impact of the change? Ease-of-use Make it easier to use Machine readable 9 Is there another way of managing clinical data? Could linked data or graph db provide something? 5

Introduction to linked data and graph db Site ID: 1 City: London Site Works at Investigator Name: Dr.X 11 Introduction to linked data and graph db Site ID: 1 City: London Site Works at Investigator Name: Dr.X Investigator Name: Dr. Who Site ID: 2 City: Leeds Site Investigator Name: Dr. Y 12 6

Race/Ethnicity MULTIPLE X + X Sex Name: Female X X Subject Ethnicity Name: Not Hispanic or Latino USUBJID: 1 Race Name: Asian Race Name: Black or African American 13 The graph can be queried Don t need to change the question 7

Medical History Disease Name: Tinnitus USUBJID:01-701-1015 Subject Disease Name: Alzheimer s USUBJID:01-701-1148 Subject Significant pre-existing condition 15 How does this impact data quality? What would happen if we had tools that we re built upon linked data? 8

Tools built with linked data Form Nodes view Form view Form built with Biomedical Concepts Tool with linked data Add controlled terminology 9

Tool with linked data Form and terminology 3.0.0 3.1.0 Enables impact analysis - Gives us control of version changes Electronic Health Records (EHR) vs. Clinical data Uses UCUM units and LOINC codes Can they share definitions? 10

Tool with linked data: Map definitions UCUM units and LOINC codes = Mapping = Shares the same definition! Tool with linked data Form + mappings We just need some data here! 11

EHR demo server in US Built on FHIR - Uses UCUM units and LOINC codes Updated graph with EHR data - Machine readable - Machine understandable - Traversal - EHR and Clinical Data can share definitions 12

Updated graph Add SDTM metadata Linked data + Query = SDTM Domain MATCH (s:subject)-[]->(n), (s:subject)-[]-(study:study) WHERE s.usubjid = '1' AND n.domain = 'MH' RETURN study.name as STUDYID, s.usubjid as USUBJID, n.domain as DOMAIN, n.name as MHTERM, n.stdtc as MHSTDTC 13

SDTM domains are outputs from the graph First exposure to study treatment MATCH (s:subject)-[]->(n), (s:subject)-[]-(study:study) WHERE s.usubjid = '1' AND n.domain = EX' EX Part of the query Not duplicated Not mapped MATCH (s:subject)-[]->(n), (s:subject)-[]-(study:study) WHERE s.usubjid = '1' AND n.domain = DS' DS DM MATCH (s:subject)-[]->(n), (s:subject)-[]-(study:study) WHERE s.usubjid = '1' AND n.domain = DM' Summary Linked data solves many of our current problems which cannot be solved with two dimensional structures (relational databases) Excels at handling complex information No structural boundaries, Metadata and Data merged Gives us precision and Enables control No mapping Impact management Version control EHR and Clinical Data can co-exist Next steps: Focus on how we represent knowledge 28 14

Thanksfor listening Contact Information Email: ju@a3informatics.com More information at: www.a3informatics.com A3 Informatics 2017 29 15