1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion:

Slides:



Advertisements
Similar presentations
SDTM Implementation Guide Version 3.1.2
Advertisements

ADaM Implementation Guide: It’s Almost Here. Are You Ready?
Joint TC Meeting: EHR – RCRIM RCRIM Overview HL7 Working Group Meeting January, 2007 Presented by: Ed Tripp Program Director, eSubmissions Abbott (RCRIM.
BRIDG Overview Clinical Observation Interoperability March 18, 2008.
Protocol Author Process People Technology
What’s New with CDISC Wayne R. Kubick CDISC CTO.
Quick tour of CDISC’s ADaM standard
Healthcare Link Initiatives: Bridging Clinical Research and Healthcare May 29, 2008 Bay Area Users’ Group Landen Bain CDISC Liaison to Healthcare.
Copyright © 2013, SAS Institute Inc. All rights reserved. LEVERAGE THE CDISC DATA MODEL TO STREAMLINE ANALYTICAL WORKFLOWS KELCI J. MICLAUS, PH.D. RESEARCH.
An Introduction to Clinical Data Acquisition Standards Harmonization (CDASH) Loryn Thorburn © 2010 PAREXEL International | Confidential.
Geospatial standards Beyond FGDC Geog 458: Map Sources and Errors March 3, 2006.
Copyright © 2005, SAS Institute Inc. All rights reserved. Maintaining a Validated SAS Toolset Co-Presenters: Edward Helton and Patricia Halley.
Status of US Implementation of ISO Metadata October 2005 Lynda Wayne US Federal Geographic Data Committee / GeoMaxim Sharon Shin US Federal Geographic.
Gregory Steffens Novartis Associate Director, Programming NJ CDISC Users’ Group 17 April 2014 Supplemental Qualifiers.
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.
Bay Area CDISC Implmentation Network – July 13, 2009 How a New CDISC Domain is Made Carey Smoak Team Leader CDISC SDTM Device Team.
SDTM Validation Rules Sub-team CDISC INTRAchange Feb 26 th, 2014.
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.
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.
© 2011 Octagon Research Solutions, Inc. All Rights Reserved. The contents of this document are confidential and proprietary to Octagon Research Solutions,
Remapping of Codes (and of course Decodes) in Analysis Data Sets for Electronic Submissions Joerg Guettner, Lead Statistical Analyst Bayer Pharma, Wuppertal,
HL7 Study Data Standards Project Crystal Allard CDER Office of Computational Science Food and Drug Administration February 13,
Qualification Process for Standard Scripts Hosted in the Open Source Repository ABSTRACT Dante Di Tommaso 1 and Hanming Tu 2 Tehran 1 F. Hoffmann-La Roche.
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
Overview and feed-back from CDISC European Interchange 2008 (From April 21 st to 25 th, COPENHAGEN) Groupe des Utilisateurs Francophones de CDISC Bagneux.
Update on SDTMIG v and SDTM v. 1.2 Bay Area User Group Meeting May 2008 Fred Wood Octagon Research Solutions.
MODULE B: Case Report Forms Jane Fendl & Denise Thwing April 7, Version: Final 07-Apr-2010.
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
1 RCRIM Vocab-BRIDG Session Wednesday, Session Q2 19 September 2007.
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
MED INF HIT Integration, Interoperability & Standards ASTM E-31 January 14, 2010 By Imran Khan.
Kopenhagen, 22 April 2008 German CDISC User Group.
Research based, people driven CDISC ADaM Datasets - from SDTM to submission CDISC Experience Exchange and ADaM Workshop 15 Dec 2008 Zoë Williams, LEO Pharma.
Public Health Reporting Initiative Stage 3 Sprint: Implementation Guide Development Phone: x
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
Research Study Data Standards Standards for research study data for submission to regulatory authorities Standard development divided into three parts:
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.
FDA Standards Development and Implementation Randy Levin, M.D. Director, Office of Information Management Center for Drug Evaluation and Research Food.
1 CDISC HL7 Project FDA Perspective Armando Oliva, M.D. Office of Critical Path Programs FDA.
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.
An Introduction to Data Lifecycle Plans ® Kit Howard Kestrel Consultants Data Lifecycle Plan ® is a registered trademark of Kestrel Consultants.
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.
CDISC submission standard
Event-Level Narrative
Dave Iberson-Hurst CDISC VP Technical Strategy
CDISC and related initativies
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
28 January 2004 Mineko FUJIMOTO Motohide NISHI Masahiro YOKOKAWA
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.
Traceability between SDTM and ADaM converted analysis datasets
In-Depth Report from Optimizing Data Standards Working Group
Clinical Observation Interoperability March 18, 2008
Statistical Programming
Visualizing Subject Level Data in Clinical Trial Data
W3C HCLS Task Force on Drug Safety and Efficacy
An FDA Statistician’s Perspective on Standardized Data Sets
Safety analysis of clinical trials in NDA submissions JSM 2018, Jul
Safety Analytics Workshop – Computational Science Symposium 2019
Version 1 Version 2 Review Published
PhUSE: Pooling WHODrug B3 Format
Presentation transcript:

1CDISC 2002 RCRIM – Standard Domains Agenda NCI Presentation Standard Domains Working Group Goals Introduction to FDA Information Model (FIM) Discussion: Moving forward on HL7 CR Standard Domains CDISC, FIM or both

2CDISC 2002 Standard Domains for Clinical Research Data - Goals To identify alternatives for incorporating CDISC data models that represent typical safety and efficacy data domains used in clinical research into HL7 as accredited standards, implementation guides, documents, etc. and to expand these models with standardized codes and controlled terminology To develop standard messages for transmitting clinical research data (such as lab data) Overlaps with CDISC ODM, LAB and SDS teams.

3CDISC 2002 Standard Domains for CR Data – Discussion Points Identifying ways to get CDISC submission domain models published as an HL7 document or standard Exploring opportunities to utilize HL7 work in vocabularies and codes to improve the SDS models Consider applying the ISO standard for metadata to the models Promote interaction with multiple groups: (CDISC, NCI, FDA, CDC-NACCR, Professional Societies) Continue current activities to explore an HL7 implementation of the LAB model and an HL7 rendition of the ODM.

SDS V. 2.0 Domain Models Demographics Disposition Exposure Labs (Chemistry, Hematology, Urinalysis) Physical Exam Medical History Concomitant Medications Adverse Events Vitals (Horizontal) Vitals (Vertical) ECG (Horizontal) ECG (Vertical)

Patient Profile Spec vs. SDS 2.0: Key Differences 1. Removes common selection variables a. Can be joined into views by data warehouse 2. Uses more normalized Demographics a. Standardizes fixed set of core required variables b. Can represent any additional characteristics in separate Subject Characteristics table 3. Introduces new Study Summary table a. Will simplify document creation and record key attributes of studies (not required for pilot) 4. Classification of variable roles: Subject identifiers, Topic, timing, qualifiers 5. Introduces concepts of controlled terminology and standardized content requirements

Patient Profile Structures Demo- graphics Subject Characteristics Adverse Events Studies Subject Events Observations Assessments Attributes/Trtment ECG Physical Exam Medical History Con Meds Exposure Labs Vital Signs Disposition Findings

FDA Information Model Structures Demo- graphics Subject Charstics Adverse Events Studies ECG Physical Exam Medical History Con Meds Exposure Labs Vital Signs Disposition InterventionsEventsFindings

8CDISC 2002 Differences between SDS and FIM Merges 12 different domains into 3 types (+ Demographics) Drops 2 character domain prefix; adds as variables Patient population flags Precision variable Variable name changes due to generalization

9CDISC 2002 Standards and the Change Process Industry FDA CDISC Standards

10CDISC 2002 Issues FIM acceptance by Statisticians FIM Compatibility with current DM/Stats processes and sponsor standards to produce CRTs and Analysis Files Impact on CDISC SDS team and implementers Where to draw the line between current models and FIM? Comprehensiveness – SDS modeled only most common 80/20 data variables per domain – will that suffice for all data? What about other unique variables? Analysis variables? Other domains? Timeframe/transition – SAS datasets require tools to be in place to be useful (for viewing, merging, etc.) Would FDA accept CDISC SDS or FIM format in interim?

11CDISC 2002 Options for Moving Forward Freeze CDISC SDS at V 2.0; cease model development until FDA publishes guidance SDS can continue with implementation guidance Publish V 2.1 as CDISC Doc only FDA Publishes FIM FDA accepts V 2.1 as well as FIM format files? Publish V 2.1 as CDISC/HL7 Doc Publish V 3.0 based on FIM as HL7 Metadata Document RCRIM Publishes FIM