© CDISC 2015 Paul Houston CDISC Europe Foundation Head of European Operations 1 CTR 2 Protocol Representation Implementation Model Clinical Trial Registration.

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)
Principal Statistical Programmer Accovion GmbH, Marburg, Germany
CDISC Open Source and low-cost Solutions
DC2001, Tokyo DCMI Registry : Background and demonstration DC2001 Tokyo October 2001 Rachel Heery, UKOLN, University of Bath Harry Wagner, OCLC
© by cellconsult.com Application Testing & Test Management.
Experience and process for collaborating with an outsource company to create the define file. Ganesh Sankaran TAKE Solutions.
Managing and Analyzing Clinical Data
What’s New with CDISC Wayne R. Kubick CDISC CTO.
The Importance of CDASH
Kendle Implementation of Clinical Data Acquisition Standards Harmonization Dr Elke Sennewald Kendle 9th German CDISC User Group Meeting Berlin, 28 September.
Emerging Technologies Project Prioritization Washington DC, March 18 th 2013.
1 CSL Workshop, October 13-14, 2005 ESDI Workshop on Conceptual Schema Language and Tools - Aim, Scope, and Issues to be Addressed Anders Friis-Christensen,
© 2008 Octagon Research Solutions, Inc. All Rights Reserved. 1 PhUSE 2010 Berlin * Accessing the metadata from the define.xml using XSLT transformations.
7. German CDISC User Group Meeting Define.xml Generator ODM Validator (define.xml validation) 2010/03/11 Dimitri Kutsenko Marianne Neumann.
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
Contents Integrating clinical trial data Working with CROs
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
Confidential - Property of Navitas Accelerate define.xml using defineReady - Saravanan June 17, 2015.
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
Emerging Technologies Semantic Web and Data Integration This meeting will start at 5 min past the hour As a reminder, please place your phone on mute unless.
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.
Basel, September 2, 2008 Work Stream Templates. 2 CDISC User Group Work Streams Goals Sharing of expertise and knowledge –Sharing of useful tools (e.g.
Development Process and Testing Tools for Content Standards OASIS Symposium: The Meaning of Interoperability May 9, 2006 Simon Frechette, NIST.
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
Overview of CDISC standards and use cases along the E2E data management process Dr. Philippe Verplancke ESUG Marlow, UK 27 May 2009.
WG4: Standards Implementation Issues with CDISC Data Models Data Guide Subteam Summary of Review of Proposed Templates and Next Steps July 23, 2012.
From PDF to RDF – Representing the CDISC Foundational Standards
© CDISC CDISC Day – Milano Europe CDISC Coordinating Committee (E3C) CDISC Operations CDISC Europe Foundation 30 September 2015.
Copyright © 2015, SAS Institute Inc. All rights reserved. Future Drug Applications with No Tables, Listings and Graphs? PhUSE Annual Conference 2015, Vienna.
1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL 17 December 2015.
Interchange vs Interoperability Main Entry: in·ter·op·er·a·bil·i·ty : ability of a system... to use the parts or equipment of another system Source: Merriam-Webster.
Emerging Technologies Semantic Web and Data Integration This meeting will start at 5 min past the hour As a reminder, please place your phone on mute unless.
© CDISC CDISC Roadmap © CDISC CDISC Strategic Goals #1 Promote and support the continued global adoption of.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Structured Protocol Representation for the Cancer Biomedical Informatics Grid: caSPR and caPRI.
Accurate  Consistent  Compliant Contact: i4i the structured content company the structured content company.
Mark Wheeldon, Formedix CDISC UK Network June 7, 2016 PRACTICAL IMPLEMENTATION OF DEFINE.XML.
Basel, September 2, 2008 Work Stream Summary define.xml/eSubmissions.
Submission Standards: The Big Picture Gary G. Walker Associate Director, Programming Standards, Global Data Solutions, Global Data Management.
End-to-End With Standards – A Regulatory Reviewer’s Perspective
Paul Houston CDISC Europe Foundation Head of European Operations
Dave Iberson-Hurst CDISC VP Technical Strategy
CTR: Clinical Trial Registries
Validation of CDISC data sets, current practice and future
define.xml/eSubmissions
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.
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.
Monika Kawohl Statistical Programming Accovion GmbH
EudraCT Public information on Clinical Trials - update
Why use CDISC for trials not submitted to regulators?
MAKE SDTM EASIER START WITH CDASH !
CPT and Disclosure: Connecting Critical Processes
Traceability between SDTM and ADaM converted analysis datasets
BR&R Biomedical Research & Regulation
The JISC IE Metadata Schema Registry
CDISC UK Network Jun-16 – Welwyn
Why a Common Protocol Template?
Business Cases and Advantages of eCTD v4.0
CPT and Disclosure: Connecting Critical Processes
History and Evolution of CPT Releases
Monika Kawohl Statistical Programming Accovion GmbH
Emerging Technologies
History and Evolution of CPT Releases
Work Stream Templates Basel, September 2, 2008.
Presentation transcript:

© CDISC 2015 Paul Houston CDISC Europe Foundation Head of European Operations 1 CTR 2 Protocol Representation Implementation Model Clinical Trial Registration & Results 2 PRIM CTR Clinical Trial Registration CTR – (Clinical Trial Registration) & CTR2 & (PRIM)

© CDISC 2015 Goal of the project Develop a draft standard, specification and XML- Schema to cover Clinical Trial Registrations of Study Designs to: ClinicalTrials.gov Eudra-CT Other WHO primary registries obeys the 20 base requirements of the WHO Trial results is out of scope for this stage 2 CTR Status - Published

© CDISC 2015 What can it be used for? Software vendors can develop software that provides a “develop once, submit multiple” solution, i.e. One software tool for generating CTR submissions to as well ClinicalTrials.gov as to Eudra-CT as to … Starting from scratch or from an existing Study Design in ODM Improve beginning to end integrity of data with extended protocol elements and SDM elements 3

✗✔✔✔✔✔✔ Sponsor Systems Vendor Application Other WHO primary registers WHO ICTRP Trial Design SDTM EudraCT.xml CTR-XML EudraCT ODM CDISC CT CTR SDM core CDISC CTR1 - WHO 20 TLD WHO ICTRP 20 TLD Protocol ClinicalTrials.gov CDISC - PRM ICMJE/CONSORT Target Trial Registries ICMJE/PRM/WHO overlap WHO 20 transform ✔ ✗ Core ICMJE/PRM

Thanks to….

© CDISC 2015 Protocol Representation Implementation Model PRIM Next Stage 6 CTR 2 Clinical Trial Registration & Results new standards Looking for Sponsors and team members now. Required contributions of $250K Stakeholders: EMA,FDA, PMDA, NIH, WHO,Trialscope, EFPIA, PhRMA etc, Southampton University, Nuffield - Oxford Uni

© CDISC 2015 Project Goals 7 Project ‘Optimus’ as a second stage of CDISC CTR will focus on defining fully structured protocol and results summary elements. The CTR 2 standard will therefore utilize and necessitate the development of a new Protocol standard – PRIM. The goal of these two new standards being: To advance the beginning to end support of clinical trials Ensure CDISC Standards are compliant and utilize IDMP terminologies Create reliable and structured trial repositories

© CDISC 2015 PRIM Deliverables A definitive Protocol schema that can be implemented in software. A protocol model implemented in SHARE and integrated into a beginning-to-end CDISC metadata model. RDF and XML export formats. Extensions to SDM,CTR, SDTM, and ADaM where appropriate. A short user guide to explain how to use the SHARE content and tools, including examples Controlled vocabulary sets with relationships expressed to the foundational standards

© CDISC 2015 PRIM Drivers To enable traceability of all protocol and Statistical Analysis Plan elements throughout the study achieving true beginning to end support of clinical trial elements Improve protocol quality and minimize amendments though re-use and consistency checks Improves reporting by explicitly aligning study objectives and endpoints with the data being captured and analyzed. Give greater flexibility, structure and reliability to biomarker design and analysis More effective EDC Study Setup Easier preparation of submission deliverables

© CDISC 2015 CTR 2 Deliverables A set of registration standard elements represented in an extended version of ODM and where appropriate mapped to the standards metadata model in SHARE. Summary result data elements as defined by the stakeholders and extensible as desired (ADaM and Define-XML data set configurations to present summary results ) A short user guide to explain how to use the SHARE content and tools, including examples. Controlled vocabulary sets with relationships expressed to the foundational standards

© CDISC 2015 CTR2 drivers Create structured and traceable results summary data sets for registries and publications to allow the same information to be accurately replicated around the worlds registries. to increase the accuracy and reliability of the information in trial registries with structured and study metadata linked data Negate human error in data entry and build in validation rules Harmonisation with regulatory IDMP requirements Further enrich the registries with more extensive summary information to support more granular searching

✗✔✔✔✔✔✔ Sponsor Systems Vendor Application PRIMe - Protocol Other WHO primary registers WHO ICTRP External unmapped requirements CTR-XML EudraCT CDISC CT Results CDISC CTR2 - Phase 1 - CDISC PRIMe, IDMP, Results Summary PRIMeIDMP ClinicalTrials.gov Target Trial Registries Results CPT-Transcelerate CDISC - PRM FDA Protocol EudraCT ClinicalTrials.gov Consort EBM rec ADaM/Define EudraCT ClinicalTrials.gov Consort EBM rec ADaM/Define ODMODM ODMODM New Registration transform transforms IDMP CVs ResultsResults ProtocolProtocol CT.gov + FDA, PMDA, EMA new requirements CT.gov + FDA, PMDA, EMA new requirements IDMPIDMP IDMPIDMP

Drug 26 FE Iron 8 0 Oxygen 20 CA Calcium Future meta data & terminology possibilities for MDRs and registries

© CDISC 2015 CTR3 14 Continue Harmonization Enrich Results datasets Evidence Based Medicine Extend granularity of info to include links to external Terminologies, site identifiers, ORCHIDS etc. Look at CDASH extensions

15 Strength through collaboration.