© 2011 The MITRE Corporation. All rights Reserved. Lessons Learned Behavioral Health eMeasure (BHeM) Project Saul A. Kravitz, PhD July 30, 2012.

Slides:



Advertisements
Similar presentations
Concept Map as the Basis of Documentation 余 靜 雲余 靜 雲.
Advertisements

Donald T. Simeon Caribbean Health Research Council
Quality Measures Vendor Tiger Team December 13, 2013.
S&I Framework Testing HL7 V2 Lab Results Interface and RI Pilot Robert Snelick National Institute of Standards and Technology June 23 rd, 2011 Contact:
CHAPTER © 2011 The McGraw-Hill Companies, Inc. All rights reserved. 2 The Use of Health Information Technology in Physician Practices.
Schizophrenia and other Psychotic Disorders
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 1 Assuming the Role of the Systems Analyst
SDLC and Related Methodologies
US Perspectives on HIT Adoption and Assessment under Meaningful Use Blackford Middleton, MD, MPH, MSc Partners HealthCare System, Inc. Harvard Medical.
Lecture Nine Database Planning, Design, and Administration
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
The Process of Scope and Standards Development
Page of 11 The Pennsylvania Child Welfare Training Program308: Adult Psychopathology: Bipolar Disorder 1 The Pennsylvania Child Welfare Training Program.
SCHIZOPHRENIA & OTHER PSYCHOTIC DISORDERS
Where do we go from here????. First – a Little History.
What is Business Analysis Planning & Monitoring?
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Meaningful Use: Clinical Quality Measures Dwane J. McGowan 18 th April, 2013.
Research to Reform: Are we making progress? Measuring the adoption, meaningful use, and impacts of health IT September 15, 2009 Floyd.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
UNIT 5 SEMINAR.  According to your text, in an acute care setting, an electronic health record integrates electronic data from multiple clinical systems.
1 5.1 Software Engineering Practice  Provide value to the user  KIS—keep it simple!  Maintain the product and project “vision”  What you produce,
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Mental and Behavioral Disorders 1. Mental, Behavioral and Neurodevelopment Disorders (F01- F99)  Codes in this chapter include disorders of psychosocial.
Data Intermediaries and Meaningful Use: Quality Measure Innovation, Calculation and Reporting Recommendations from Data Intermediary Tiger Team.
Using Human Component Mapping TO ANALYSE & INTEGRATE HUMAN FACTORS ISSUES & RECORDS WITH RAILWAY HAZARD LOGS 1 Dr. Amanda C. Elliott, Simon Macmull & Harry.
A Model-Driven Approach to Interoperability and Integration in Systems of Systems Gareth Tyson Adel Taweel Steffen Zschaler Tjeerd Van Staa Brendan Delaney.
BIPOLAR DISORDER DR GIAN LIPPI CONSULTANT PSYCHIATRIST
Update in the Treatment of Depressive Disorders Renee Lamm MD ABPN, ABAM FAPA, FAAFP.
Update in the Treatment of Depressive Disorders Renee Lamm MD ABPN, ABAM FAPA, FAAFP.
Coverage Indications, Limitations, and/or Medical Necessity This policy limits CYP2C19 (CPT 81225) and CYP2D6 (CPT 81226) genetic testing to defined indications.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Understanding eMeasures – And Their Impact on the EHR June 3, 2014 Linda Hyde, RHIA.
Quality Measures in Electronic Health records Jacob Reider, MD Medical Director, Allscripts Co-Chair EHRA Acceleration Working Group.
1 Modeling System Requirements with Use Cases. 2 Why Do We Need Use Cases? Primary challenge in a system design process –ability to elicit correct and.
Shaul Lev-Ran, MD Shalvata Mental Health Center
USHIK: A Meaningful Use One-Stop Shop Health Information Technology Standards Council J. Michael Fitzmaurice, Ph.D. Agency for Healthcare Research and.
Systems Development Life Cycle
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Context Process0. student Data Flow Diagram Progression.
Quality Improvement: Overview of Principles and Techniques
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
CONFIDENTIAL & PROPRIETARY Expanding the Reach of Predictive Models: Using Clinical, HRA, and Consumer Data Dan Dunn, PhD, Senior VP of R&D, Ingenix The.
XML Hong Nguyen National University HTM 520 HIE. Introduction Extensible Markup Language Foundation technology for web services Developed in 1996 ◦ Transport.
Course: Software Engineering – Design I IntroductionSlide Number 1 What is a specification Description of a (computer) system, which:  is precise;  defines.
Clinical Quality Workgroup April 10, 2014 Commenting on the ONC Voluntary 2015 Edition Proposed Rule Marjorie Rallins– co-chair Danny Rosenthal –co-chair.
CCBHC Prospective Payment System (PPS) Technical Assistance (TA) Session 5 Webinar: Identification of Special Populations February 25, :30-4:00pm.
Behavioral Health INTEGRATION Recent literature, conceptual frameworks & options for next steps October 16, 2013 Mark Gibson Director Center for Evidence-based.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Bipolar II Disorder. Involves – Major Depressive Episodes and – Hypomanic Episodes Bipolar IIvsBipolar I (Hypomanic + MDD) (Manic + MDD)
PSY 436 Instructor: Emily Bullock Yowell, Ph.D.
Bipolar I Disorder Derek S. Mongold MD.
Chapter 1 The Systems Development Environment
Implementation of ICD 10 deadline
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Major Depressive Disorder: Latest Clinical Update
A bit more about Read Codes and SNOMED CT
הפרעות במצב הרוח MOOD DISORDERS.
PSY 436 Instructor: Emily E. Bullock, Ph.D.
Chapter 1 The Systems Development Environment
How Should We Select and Define Trial Estimands
Presentation transcript:

© 2011 The MITRE Corporation. All rights Reserved. Lessons Learned Behavioral Health eMeasure (BHeM) Project Saul A. Kravitz, PhD July 30, 2012

© 2011 The MITRE Corporation. All rights Reserved. Background ■Behavioral Health eMeasure Project –Sponsors: ONC and SAMHSA –Objective: Develop Portfolio of Behavioral Health Measures –Output: 10 eSpecified CQMs, 2 included in NPRM ■Novel Development Approach –Collaborative eMeasures and shared value set development –Model eSpecfication development with shared value sets –Develop portfolio of value sets supporting all 10 eSpecs ■Project Organization –Measure steward collaboration –eSpecification: NCQA (4), TJC (2), and MITRE (4) –Value Set Development: Apelon, Inc 2

© 2011 The MITRE Corporation. All rights Reserved. Lessons Learned ■eMeasures Intent and Selection ■Concept Development Identification ■Collaborative eMeasure and Shared Value Set Development ■Value of Impartial Review ■Importance of Testing ■eMeasures Tools Utilization ■Project Management Oversight 3

© 2011 The MITRE Corporation. All rights Reserved. Measure Intent and Selection 4 ■NQF-endorsed CQMs include –Intent (e.g., diabetics’ feet should be examined) –Data Source (e.g., claims data) –Logic ■Retooling a CQM preserves intent, replaces data source, adjusts logic ■Some CQMs will only work with a specific data source Lesson: eSpecifications of CQMs should be considered as closely related implementations of the intent of CQMs with alternate data sources

© 2011 The MITRE Corporation. All rights Reserved. Single Intent, Multiple Implementations 5 NQF0580: Bipolar Manic Agent Claims DataProvider EHR DataACO EHR Data NQF endorsedBHeMFuture? All three implementations of NQF0580 share intent: bipolar patients should be medicated appropriately Data sources and logic differ Sensitivity and specificity will differ

© 2011 The MITRE Corporation. All rights Reserved. Collaborative eMeasure and Shared Value Set Development ■BHeM Project separated eMeasure logic specification from value set development –Value set developer captured measure developer intent –MITRE and measure developer review of value sets –Iterative process to reconcile ■Traditional expression of value sets is an enumeration of code values (“extensional”) –Difficult to review –Difficult to maintain –Doesn’t take advantage of hierarchy of vocabularies ■Expression of Value sets as “recipes” (“intensional) –Much easier to review and maintain –Leverages hierarchy of vocabularies 6

© 2011 The MITRE Corporation. All rights Reserved. Traditional Extensional Value Set 7 …and many more Severe mixed bipolar I disorder with psychotic features, mood-incongruent Severe mixed bipolar I disorder with psychotic features Mixed bipolar I disorder in full remission Chronic bipolar II disorder, most recent episode major depressive Severe bipolar II disorder, most recent episode major depressive, in full remission Mild bipolar disorder Severe bipolar I disorder, single manic episode with psychotic features, mood-congruent Bipolar disorder Severe bipolar I disorder, single manic episode without psychotic features Bipolar I disorder, single manic episode with postpartum onset Severe manic bipolar I disorder without psychotic features Bipolar II disorder, most recent episode major depressive Mixed bipolar I disorder Bipolar I disorder, most recent episode manic with catatonic features Bipolar affective disorder, current episode manic Bipolar affective disorder, currently manic, mild Bipolar affective disorder, currently manic, moderate Bipolar affective disorder, currently manic, severe, with psychosis Bipolar affective disorder, currently manic, in full remission Bipolar affective disorder, current episode depression Bipolar affective disorder, currently depressed, mild Bipolar affective disorder, currently depressed, moderate Bipolar affective disorder, currently depressed, severe, with psychosis Bipolar affective disorder, currently depressed, in full remission

© 2011 The MITRE Corporation. All rights Reserved. Intensional Value Set Description 8 Lessons: Communication between developers of value sets and measure stewards is essential Value set recipes for clinical concepts should be specified ‘intensionally ’ Include codes that are in active use Include codes that apply to Humans

© 2011 The MITRE Corporation. All rights Reserved. Value of Impartial Review ■Independent reviews resulted in improvements to measure design –Simplification of the proposed measures –Identification of errors and issues with data and logic –Elimination of data elements –Improved feasibility ■Improved accuracy and generality of value sets ■Simplified and clarified measure logic based on development and review of test cases 9 Lesson: eMeasures and Value Sets intended for inclusion in national quality programs should be reviewed by 3rd party with focus on feasibility, correctness, and computability.

© 2011 The MITRE Corporation. All rights Reserved. Importance of Testing ■BHeM eSpecification deliverables included test data and outcomes in a common format –Specified at concept, not code level –Identify logical errors in eMeasures –Identify scenarios not considered by eSpecifiers –Facilitate testing Lesson: Testing is essential –Test data and outcomes should be required in documentation of eMeasures –Automated testing for conformance with test data should be the rule 10