1 / 21

Workgroup

Workgroup. Clinical Quality Measure Workgroup Jim Walker & Karen Kmetik , Co- Chairs. May 7, 2012 - 4:30 pm – 5:30 pm. Agenda. 4:30 p.m. Call to Order/Roll Call MacKenzie Robertson, Office of the National Coordinator 4:35 p.m. Review of Agenda Jim Walker, Chair

dannon
Download Presentation

Workgroup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Workgroup • Clinical Quality Measure Workgroup • Jim Walker & Karen Kmetik, Co-Chairs May 7, 2012 - 4:30 pm – 5:30 pm

  2. Agenda 4:30 p.m. Call to Order/Roll Call MacKenzie Robertson, Office of the National Coordinator 4:35 p.m. Review of Agenda Jim Walker, Chair 4:40 p.m. Review: CQM Essential Components Tiger Team Value Set Recommendations 5:10 p.m. Update: Characteristics of Optimal Clinical Quality Measures for Health IT Tiger Team 5:25 p.m. Public Comment 5:30 p.m. Adjourn Office of the National Coordinator for Health Information Technology

  3. Essential Components Update • Developed recommendations regarding usable and useful value sets for MU Stage 2: • Review draft recommendations with full WG • E-mail final poll, week of May 16 • Report to Standards Committee May 24 Office of the National Coordinator for Health Information Technology

  4. Scope of Recommendations • In scope: ImperativeValue Set infrastructure to support MU2 • Validation of vocabulary codes • Internet hosting & delivery of value sets • Content standard for serving value sets • Transfer standard for serving value sets • Out of scope: Longer term infrastructure • Discoverability • Curation, including harmonization & maintenance of codes and verification of semantic validity • Governance, content management, versioning Office of the National Coordinator for Health Information Technology

  5. Recommendations Recommendation 1.0: Establish NLM as a single authority for the validation of value sets used in Stage 2 quality measures. NLM should serve as a single source of truth for MU2 value sets, and should publish periodic updates to reflect changes within the underlying vocabularies and/or changes made by value set stewards. • ONC should coordinate with other agencies, value set stewards, and consensus organizations as needed for value set hosting and serving/delivery. • NLM will cross-check the accuracy of Stage 2 Clinical Quality Measure value sets by comparing value set codes and descriptors against appropriate source vocabularies to assess value set validity, and will suggest edits to value set stewards to ensure the validity of vocabulary codes, names, and vocabulary system version. Recommendation 2.0: ONC should expedite recommendations of the Implementation Workgroup (Jan 2012) and Vocabulary Task Force (April 2010) related to establishment of a publicly available value set repository. Office of the National Coordinator for Health Information Technology

  6. Recommendations Recommendation 3.0: The value set repository established by NLM should build upon the IHE Sharing Value Sets (SVS) profile for storing and serving value sets, and incorporate Common Terminology Service 2 (CTS2) methods for managing vocabularies referenced by value sets. Recommendation 4.0: Establish a web service for human and machine consumption of Meaningful Use 2 value sets. Consider NLM, AHRQ, or CDC as the Internet host for validated value sets. • Provide output in commonly used formats, e.g., tab-delimited, spreadsheet or XML formats, suitable for import into SQL tables, and web service delivery. • Support the creation of web-based views based on quality measure and value set names and numerical identifiers, QDM Category, code systems & code system versions used. Office of the National Coordinator for Health Information Technology

  7. MU2 Value Set Validation & Delivery Validation Delivery Controlled Value Sets Publicly Available Controlled Value Sets Publicly Available Human readable web page Machine readable web services Office of the National Coordinator for Health Information Technology

  8. Swim Lanes Quality Measure / Value Set Developer NLM Consensus Org • Receive value sets • Store value sets inpublicly available value set repository • Provide feedback to developers re: code validity • Request clarification from developers as needed • Make validity edits to value sets • Serve value sets in human & machine readable form • Deliver value sets to NLM for endorsed measures • Value Set Harmonization • Create value set • Deliver value sets to NLM (non-endorsed measures) • Receive feedback from NLM re: code validity • Provide clarification as needed • Incorporate edits into base value set Office of the National Coordinator for Health Information Technology

  9. What a repository might look like Office of the National Coordinator for Health Information Technology

  10. What a repository might look like

  11. Characteristics of Optimal ClinicalMeasures for Health IT Update The Characteristics of Optimal Clinical Quality Measures for Health IT Tiger Team will focus on identifying the attributes of optimal clinical quality measures that are created or “re-tooled” for use in Health IT. Office of the National Coordinator for Health Information Technology

  12. Tiger Team Scope The characteristics of optimal clinical quality measures evaluated by this Tiger Team are from a technical lens, not from the perspective of the importance of the quality measure per se. We are interested in applying this technical lens to measures we have and those we seek (e.g., longitudinal, patient-reported, clinical outcomes). Office of the National Coordinator for Health Information Technology

  13. Goals & Timeline Identify the attributes of optimal clinical quality measures that are created or “re-tooled” for use in Health IT. Emphasis on “re-thinking” vs. “re-tooling.” • Draft report to Tiger Team May 9 • Email distribution to full WG May 16 • Report to Standards Committee May 24 Office of the National Coordinator for Health Information Technology

  14. Tiger Team Scope The characteristics of optimal clinical quality measures evaluated by this Tiger Team are from a technical lens and a workflow lens, not from the perspective of the importance of the quality measure per se. We are interested in applying this technical lens to measures we have and those we seek (e.g., longitudinal, patient-reported, clinical outcomes). Office of the National Coordinator for Health Information Technology

  15. What Makes an Optimal Quality Measure? Reduces variations in interpretation Reduces workarounds and hard-coding of choices Office of the National Coordinator for Health Information Technology

  16. Usability Definitions • The data may be available now or could be available with reasonable workflow changes. • Redundancy – The data capture should reduce re-entry unless entering it again provides value, such as in clinical decision support, care coordination, or verification process. Office of the National Coordinator for Health Information Technology 15

  17. Feasibility Definitions • EHR Feasibility – Functionality to support the quality measure exists in most EHRs or could exit within reason for stretch quality measures (data accessible). • EHR Enabled – The quality measure is enabled due to data being in electronic format. These items are difficult to measure on paper or non-electronic formats. Office of the National Coordinator for Health Information Technology 16

  18. Accuracy Definitions • Accuracy – For clinical quality measures to be optimal, they need to be accurate, and accuracy has four parts: • Data are captured correctly and queried correctly (clear, detailed specifications) • Process of collection has few errors and does not require re-entry of data unless it provides value (eg, verification, care coordination, clinical decision support) • Knowledge that the data itself are accurate irrespective of capture mechanism • Assumptions are not made about how the collection happens, but instead guidance is provided Office of the National Coordinator for Health Information Technology 17

  19. Standard Terminology Definitions • Standard Terminology Usage (shared meaning) - Data needed for quality measures should be captured using standard terminology to reduce variations in interpretation and to reduce hard-coding of choices and workarounds. • We want confidence that practice A/EHR A and practice B/EHR B are using the same terminology for data elements • The data should be easily aggregated because the data are using common standards as dictionaries. For example, everyone uses the same value set to identify the population of patients with diabetes for a particular measure. Office of the National Coordinator for Health Information Technology 18

  20. Applying These Criteria to Different Types of Measures: Process Clinical outcome Patient-reported outcome Change over time (delta) Interpreting results from study (e.g., feasibility testing at practice sites, data sets, surveys) Office of the National Coordinator for Health Information Technology

  21. Discussion Discussion Office of the National Coordinator for Health Information Technology

More Related