OHDSI population-level estimation workgroup meeting

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Automated Evaluation of Runtime Object States Against Model-Level States for State-Based Test Execution Frank(Weifeng) Xu, Gannon University Dianxiang.
HP Quality Center Overview.
Chapter 3: Modularization
July 11 th, 2005 Software Engineering with Reusable Components RiSE’s Seminars Sametinger’s book :: Chapters 16, 17 and 18 Fred Durão.
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
United Nations Economic Commission for Europe Statistical Division Applying the GSBPM to Business Register Management Steven Vale UNECE
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Performing the Study Data Collection
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Identify steps for understanding and solving the
 Three-Schema Architecture Three-Schema Architecture  Internal Level Internal Level  Conceptual Level Conceptual Level  External Level External Level.
Instructor Resource Chapter 15 Copyright © Scott B. Patten, Permission granted for classroom use with Epidemiology for Canadian Students: Principles,
The Bahrain Branch of the UK Cochrane Centre In Collaboration with Reyada Training & Management Consultancy, Dubai-UAE Cochrane Collaboration and Systematic.
Population level estimation workgroup Martijn Schuemie Marc Suchard.
CS491B Software Design Lab Writing Project Report Chengyu Sun California State University, Los Angeles.
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
Supervisor : Prof . Abbdolahzadeh
Space FSW Conference 2016 Matthew Conte Software Engineer
OHDSI 2016 Population Level Estimation Symposium talk
Testability.
Martijn Schuemie, Marc Suchard, Patrick Ryan, Tomas Bergvall
Constructing OHDSI network studies
Theme (v): Managing change
The comparative self-controlled case series (CSCCS)
FeatureExtraction v2.0 Martijn Schuemie.
Population level estimation best practices
Modern Systems Analysis and Design Third Edition
OHDSI Method Evaluation
Patrick Ryan, PhD Janssen Research and Development
A critical assessment of the utility of the case-control design in population-based databases Martijn Schuemie.
Globey's World Abstract End-Product Description Technical Approach
Automation of systematic reviews: the reviewer’s viewpoint
Population level estimation workgroup
Software Life Cycle “What happens in the ‘life’ of software”
Reproducing Graham et al using the CohortMethod package
Martijn Schuemie, PhD Janssen Research and Development
Martijn Schuemie, PhD Janssen Research and Development
Designing and executing OHDSI studies
Method benchmark update
Supplementary Table 1. PRISMA checklist
CS 641 – Requirements Engineering
CS 641 – Requirements Engineering
Method evaluation Martijn Schuemie.
OHDSI estimation-methods papers in progress
DISCUSSION.
Organization of Paper Summary or Abstract Introduction
Exam Technique.
UK Link Technology Refresh
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Introduction to Configuration Management
SDMX: Enabling World Bank to automate data ingestion
Introduction to Software Testing
Modern Systems Analysis and Design Third Edition
Martijn Schuemie, Peter Rijnbeek, Jenna Reps, Marc Suchard
Yearly Maintenance Process (for existing messages)
Modern Systems Analysis and Design Third Edition
How to read a paper or one way to read a paper
Estimation, Revision Control, Rose, and More?
External Validation of Existing Stroke Risk Models
Lecture 06:Software Maintenance
CS 240 – Advanced Programming Concepts
OHDSI’s mission To improve health by empowering a community to collaboratively generate the evidence that promotes better health decisions and better care.
Utility Billing Balancing the Accounts Receivable
Extreme Programming.
Rapid software development
SOFTWARE DEVELOPMENT LIFE CYCLE
rePLay: A Hardware Framework for Dynamic Optimization
LEGEND Reproducible, systematized, open source approach at scale
Presentation transcript:

OHDSI population-level estimation workgroup meeting Martijn Schuemie, PhD Janssen Research and Development

Previous Eastern Hemisphere meeting January 11 Erica Voss: - Using Established Knowledge in Population-Level Estimation In a Systematic Way

Previous Western Hemisphere meeting January 18 Martijn Schuemie: Current OHDSI papers being written Confidence interval calibration

Current OHDSI papers being written See spreadsheet

Study reproducibility

What do epi studies currently look like? Data set Paper

A journey from data set to paper Most epidemiologists view a study as a journey from data set to paper. The protocol might be your map You will come across obstacles that you will have to overcome Several steps will require manual intervention In the end, it will be impossible to retrace your exact steps

Current epi studies are non-reproducible How do we know what happened? How do we know if it was done correctly? How do we know how well it worked? How could we be more efficient? How can we deal with more complex studies? How can multiple people work together on the same analysis? How could other reproduce this study on a different database?

What should OHDSI studies look like? Paper Database A study should be like a pipeline A fully automated process from database to paper ‘Performing a study’ = building the pipeline

Example: Keppra – angioedema study OHDSI study: Does exposure to Keppra (levetiracetam) lead to an increased risk of angioedema? Compared to phenytoin https://github.com/OHDSI/StudyProtocols/tree/master/KeppraAngioedema

Full traceability Study package contains Cohort definitions (e.g. angioedema definition) OhdsiRTools::insertCohortDefinitionInPackage(2193, "Angioedema") All analysis details for the CohortMethod package CohortMethod package describes data extraction Code to generate tables and figures Code to generate full report

Full traceability R environment snapshot OhdsiRTools::insertEnvironmentSnapshotInPackage("KeppraAngioedema")

We can check for correctness We can review the study code We should make the study code publicly available as part of the paper Large parts of the study are automatically checked using unit tests

We can evaluate how well the study worked Included 100 negative control outcomes Results show little residual confounding when using propensity score matching

Writing the study was very efficient Reuse of R code in CohortMethod, DatabaseConnector, SqlRender, EmpiricalCalibration, etc. Implementation took days instead of months Next study will be faster

Complexity is not a problem Use software engineering approaches to deal with complexity: Abstraction Encapsulation Writing clear code Re-use

Several people can work on the same analysis through version control Mary Version 2 History of changes: How did the final analysis come about? Version control system Version 1 Version 2 Use for everything: Protocol Analysis code Paper X Me Version 1 Version 2 Version 3 Version 2 Time

Commit log

Easy to rerun on different data The Keppra – Angioedema study was run on: Columbia University EHR Stanford EHR Cerner (University of Texas) Pharmetrics Plus (IMS) Optum Truven CCAE Truven MDCD Truven MDCR …

Viewing a study as a pipeline has many advantages Full traceability Ability to check for correctness Ability to evaluate using controls More efficient Ability to deal with complexity Ability to work with several people on one analysis Easy to rerun on different data

Two dimensions of reproducibility From database to paper Database Paper Version 1.0 From inception to publication Version 0.2 Version 0.1

Version control supports the 2nd dimension

Conclusions Most epi studies lack reproducibility 1st dimension: From database to paper 2nd dimension: From inception to publication Studies should be viewed as pipelines The pipeline should be published as part of the paper

Next workgroup meetings Eastern hemisphere: Februari 22 NO MEETING ON FEBRUARI 8! 3pm Hong Kong / Taiwan 4pm South Korea 5:30pm Adelaide 8am Central European time 7am UK time Western hemisphere: Februari 2 6pm Central European time 12pm New York 9am Los Angeles / Stanford http://www.ohdsi.org/web/wiki/doku.php?id=projects:workgroups:est-methods