Standards. September 9, 2011

Similar documents
HIT Standards Committee Transitional Vocabulary Task Force Wednesday October 14th, 2015, 10:30 A.M. 12:00 P.M. Et

NQF health information technology glossary. a guide to HIT jargon

THE STIMULUS AND STANDARDS. John D. Halamka MD

Standardized Terminologies Used in the Learning Health System

I. RECOMMENDATIONS RELATED TO THE TIMING OF STAGE 2

GE Healthcare Healthcare IT

HL7 & Meaningful Use. Charles Jaffe, MD, PhD CEO Health Level Seven International. HIMSS 11 Orlando February 23, 2011

Eligible Professionals please see the document: MEDITECH Prepares You for Stage 2 of Meaningful Use: Eligible Professionals.

TEST INSTRUCTIONS FOR CROSS VENDOR EXCHANGE TABLE OF CONTENTS

PUBLIC HEALTH MU OBJECTIVES

Meaningful use. Meaningful data. Meaningful care. The 3M Healthcare Data Dictionary: Enabling effective health information exchange

Shelly Spiro, Executive Director, Pharmacy HIT Collaborative reports no relevant financial relationships.

Meaningful Use Stage 2 Certification: A Guide for EHR Product Managers

Meaningful Use and Public Health

Re: Comments on 2015 Interoperability Standards Advisory Best Available Standards and Implementation Specifications

A Semantic Foundation for Achieving HIE Interoperability

Karen DeSalvo, M.D., M.P.H., M.Sc. May 29, 2015 Page 2 of 7

Guide To Meaningful Use

APTA and Meaningful Use of HIT

VIII. Dentist Crosswalk

Advancing Laboratory Interoperability in Health IT

MEANINGFUL USE. Community Center Readiness Guide Additional Resource #13 Meaningful Use Implementation Tracking Tool (Template) CONTENTS:

How To Use A Pharmacy To Help Your Health Care System

May 7, Dear Dr. Mostashari:

April 22, RE: Advancing Interoperability and Health Information Exchange. Dear Dr. Mostashari:

Increase Participation Through Partial Incentives

Meaningful Use of Certified EHR Technology with My Vision Express*

May 7, Submitted Electronically

Meaningful Use - The Basics

Response to Revisions to the Permanent Certification Program for Health Information Technology NPRM (RIN 0991-AB82)

Certification Guidance for EHR Technology Developers Serving Health Care Providers Ineligible for Medicare and Medicaid EHR Incentive Payments

[RIN 0991-AB82] Table of Contents

Using Patient Portals to Achieve Meaningful Use Stage 2

Meaningful Use Criteria for Eligible Hospitals and Eligible Professionals (EPs)

Role of SNOMED CT in Public Health Surveillance

Qualifying for Medicare Incentive Payments with Crystal Practice Management. Version

Meaningful Use. Michael L. Brody, DPM FACFAOM CCHIT Ambulatory Workgroup HITSP Physician Perspective Technical Committee NYeHC

Overview: Beacon-EHR Vendor Technical Work Group Version 1.0 work products

Understanding the Rules for Creating CVX and MVX Codes

HL7 and Meaningful Use

Meaningful Use Stage 2 as it Relates to the Lab Implementing the Public Health Agency Interface. Interface

Presented by. Terri Gonzalez Director of Practice Improvement North Carolina Medical Society

May 4, Dear Dr. Mostashari:

Stage 2 Eligible Professional Meaningful Use Core Measures Measure 15 of 17 Last Updated: August, 2015

MEANINGFUL USE STAGE FOR ELIGIBLE PROVIDERS USING CERTIFIED EMR TECHNOLOGY

Dear Honorable Members of the Health information Technology (HIT) Policy Committee:

Where to Begin? Auditing the Current EHR System

STAGES 1 AND 2 REQUIREMENTS FOR MEETING MEANINGFUL USE OF EHRs 1

March 15, Dear Dr. Blumenthal:

Health Information Technology: Standards, Implementation Specifications, and

RE: CMS 0033 P; Comments to Meaningful Use Notice of Proposed Rulemaking

Summary of the Proposed Rule for the Medicare and Medicaid Electronic Health Records (EHR) Incentive Program (Eligible Professionals only)

3M Health Information Systems

Federal Register / Vol. 77, No. 171 / Tuesday, September 4, 2012 / Rules and Regulations

May 7, Re: RIN 0991-AB82. Dear Secretary Sebelius:

LIS Vendor Landscape and Options for Meeting ELR Meaningful Use

HITECH Act Update: An Overview of the Medicare and Medicaid EHR Incentive Programs Regulations

COMMUNICATIONS PLAN FOR ELECTRONIC LABORATORY REPORTING COMMUNICATIONS MANAGEMENT PLAN

Medical Billing and EHR Implementation

Client Alert. CMS Releases Proposed Rule On Meaningful Use Of Electronic Health Record Technology

Selecting and Implementing EMRs in the FQHC/CHC Setting. TN Primary Care Association JUNE 26, 2009

Dear Drs. Isham, McGlynn, and MAP Coordinating Committee Members:

Lunch and Learn IFAF 09/24/11. Michael L. Brody, DPM

HIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger

2013 Meaningful Use Dashboard Calculation Guide

Meaningful Use Objectives

Saving the Details for Guidance EXAMPLE 1:

Meaningful Use Stage 2 Update: Deploying SNOMED CT to provide decision support in the EHR

AAP Meaningful Use: Certified EHR Technology Criteria

Standards for Electronic Health Records An Introduction to EHRs runs Two Lines Long

Meaningful Use and Lab Related Requirements

ELECTRONIC HEALTH RECORDS/NATIONAL HEALTH INFORMATION INFRASTRUCTURE: LEGAL ISSUES IN HIPAA AND EMERGING TECHNOLOGIES

Meaningful Use Qualification Plan

RE: Comments on Discussion Draft Ensuring Interoperability of Qualified Electronic Health Records.

MEANINGFUL USE STAGE 2 REQUIREMENTS FOR ELIGIBLE PROVIDERS USING CERTIFIED EMR TECHNOLOGY

Electronic Health Record (EHR) Standards Survey

HL7 and Meaningful Use

Medicare and Medicaid Programs; EHR Incentive Programs

SURVEY QUESTIONNAIRE 2013 AHA ANNUAL SURVEY INFORMATION TECHNOLOGY SUPPLEMENT

HIMSS EHR Association Definitional Model and Application Process. July 2012

May 2, Dear Mr. Posnack:

EHR Incentive Program Stage 2 Objectives Summary CORE OBJECTIVES (You must meet all objectives unless exclusion applies.)

April 28, Dear Secretary Sebelius and Dr. DeSalvo,

Understanding Meaningful Use with a Focus on Testing the HL7 V2 Messaging Standards

Agenda. What is Meaningful Use? Stage 2 - Meaningful Use Core Set. Stage 2 - Menu Set. Clinical Quality Measures (CQM) Clinical Considerations

Achieving Meaningful Use Training Manual

Stage 1 vs. Stage 2 Comparison Table for Eligible Hospitals and CAHs Last Updated: August, 2012

AHA Annual Survey Information Technology Supplement. Healthcare IT Database Download and Data Licensing

Meaningful Use Reporting Quick Reference

Electronic Health Records: Why are they important?

A Guide to Understanding and Qualifying for Meaningful Use Incentives

Data Integrity in an Era of EHRs, HIEs, and HIPAA: A Health Information Management Perspective

April 22, Re: Advancing Interoperability and Health Information Exchange. Dear Dr. Mostashari,

How to Achieve Meaningful Use with ICANotes

HealthFusion MediTouch EHR Stage 2 Proposed Rule Comments

Health Care Information System Standards

Meaningful Use: Stage 1 and 2 Hospitals (EH) and Providers (EP) Lindsey Mongold, MHA HIT Practice Advisor Oklahoma Foundation for Medical Quality

REQUIREMENTS GUIDE: How to Qualify for EHR Stimulus Funds under ARRA

Stage 2 EHR Certification: NLM Vocabulary Update. Betsy Humphreys Deputy Director, NLM

Meaningful Use Stage 2 Administrator Training

Transcription:

Standards September 9, 2011 Farzad Mostashari, MD, ScM National Coordinator for Health Information Technology Department of Health and Human Services 200 Independence Avenue, SW Washington, DC 20201 Dear Dr. Mostashari: The HIT Standards Committee s (HITSC) Clinical Quality Measures Workgroup (CQMWG) and Vocabulary Task Force (VTF) jointly developed recommendations on the assignment of code sets to clinical concepts [data elements] for use in quality measures. The CQMWG and VTF held a series of joint meetings to develop the set of recommendations. This letter transmits the recommendations to the Department of Health and Human Services (HHS) on the assignment of code sets to clinical concepts for use in quality measures. On August 17, 2011, the CQMWG and VTF reported on and discussed their findings with the HITSC, which were subsequently approved as outlined below. BACKGROUND: The Clinical Quality Measures Workgroup and Vocabulary Task Force proposed a list of recommendations that specifically addressed the 23 categories of clinical concepts [categories of data elements] as defined and proposed by the National Quality Forum s Quality Data Model version 3.0 (QDM). (See attached QDM Spreadsheet). Each concept was thoroughly discussed and recommendations agreed upon amongst the Clinical Quality Measures Workgroup and Vocabulary Task Force members over the course of six weeks (from mid-june to July 2011). It was recognized that many vocabulary standards exist; however, it was the mission of the Clinical Quality Measures Workgroup and Vocabulary Task Force to evaluate and further recommend the minimum set of vocabulary standard(s) that would apply to each data element for the purpose of reporting clinical quality measures to the Centers for Medicare and Medicaid Services (CMS). The Joint Clinical Quality Measures Workgroup and Vocabulary Task Force convened on a regular basis to explicitly address the 23 categories of concepts. Each category had been assigned proposed recommended vocabularies based on clinical taxonomy evidence and subject matter expertise contributed by the workgroup members, invited Standards Development Organizations, and others. The Joint Workgroup then proceeded to review the concepts and their corresponding recommendation(s) line-by-line. Thorough discussions occurred weekly to ensure that each 1

concept was properly vetted, taking into account the expert opinions and objective evidence in an effort to apply the minimum set of vocabulary standards necessary. Verbal consensus among the Joint Workgroup was achieved on each call for the concepts that had been discussed in an effort to finalize the draft recommendations. Please refer to the attached Code Sets spreadsheet for further detail about the concepts and their corresponding recommendations. The Joint Workgroup used the following foundation concepts to arrive at their recommendations: A limited number of code sets would be used for quality measures Some code sets may be limited to partial depth Future purpose-specific subsets of code sets will be needed Certified HIT shall be able to process all legal codes in the code set for a given concept Only code sets required in HIT certification would be required for meaningful use incentive payments End state target standards are recommended for quality measure purposes, however some code sets will require transition plans The recommended code sets are being recommended for quality measures only at this time, not for other EHR functions. RECOMMENDATIONS: The Clinical Quality Measures Workgroup and Vocabulary Task Force proposed the following code set recommendations for the 23 categories of concepts in the quality data model: 1. Adverse Effect The concept of Adverse Effect is inclusive of Allergic and Non-Allergic Adverse Effects. The vocabulary standards that have been recommended and would apply are the following: Rx Norm for Medications that caused adverse effect for Non-Medication Substances that caused adverse effect for Adverse effect itself 2. [Patient] Characteristics The category of [patient] Characteristics includes the concepts of Age, Gender, Socioeconomic Status, Ethnicity, Race, and Smoking Status; all of which refer to specific factors about a patient, clinician, provider or facility. The vocabulary standards that have been recommended and would apply are the following: ISO 639-2 constrained to elements in ISO 639-1 for Patient s Preferred Language CDC PHIN-VADS HL7 for Administrative Gender 2

CDC PHIN-VADS HL7 Race and Ethnicity (use broadest range of code sets within CDC listed for Race, Ethnicity, or both combined) LOINC-For assessment instruments, (including tobacco use) -Appropriate Responses to Instruments (including patient preferences and behaviors) (Socio-Economic Status is being further defined by CMS.) Payer Typology of the Public Health Data Standards Consortium for characterizing payers 3. Communication This is inclusive of provision of clinical information from provider to provider, provider to patient, or patient response to provider. 4. Conditions, Diagnosis, and Problems 5. Device 6. [Non-Laboratory] Diagnostic Study LOINC for specific study name for appropriate findings UCUM for specific units of measure 7. Encounter Encounter was considered to include patent-professional interactions that are not limited to face-to-face or billable clinical encounters. SNOMED-CT 8. [Patient] Experience LOINC for assessment instruments appropriate responses 9. Family History LOINC for assessment instruments appropriate responses\ 3

10. Functional Status ICF (International Classification of Functioning, Disability and Health) for categories of function LOINC for assessment instruments for appropriate responses 11. Health Record Component Health Record Component refers to an element of a health IT application. LOINC for naming of the components and for their relationships HL7 for the messaging among systems. 12. Intervention Interventions forms one end of a spectrum with Procedures. LOINC for interactions that produce an assessment or measurable results for appropriate results and interventions that do not produce measurable results (e.g., counseling) 13. Adverse Effect other than Allergy (Intolerance) RxNorm for medications and inert ingredients associated with the adverse effect for Non-medication substances associated with the adverse effect for the adverse effect 14. Laboratory Test LOINC for the test name and its results. for applicable results values UCUM for units of measure 15. Medication RxNorm for medications CVX for vaccinations (acknowledging that vaccinations are treated as medications in some contexts and as a separate category in others) 16. Physical Exam LOINC for assessment instruments for appropriate responses 17. [Patient] Preference LOINC for assessment instruments 4

for appropriate responses 18. Procedure 19. Risk Evaluation LOINC for evaluation instruments for appropriate responses 20. Substance (non-medication) 21. Symptom 22. System Resource System Resource refers to the configuration of an organization (e.g. nurse staff ratios, availability of durable medical equipment, health information technology infrastructure and capabilities, etc.). LOINC for healthcare resources (e.g., staffing) HL7 for EHR functions for equipment 23. Transfer TRANSITION PLANS Current EHR products and quality measures utilized in public and private sector programs today, do not necessarily use the recommended code sets for embedded measures. In order to allow for a transition period, some measure concepts will need interim code set recommendations. The combined working group will present at least preliminary recommended transition plans to the HIT Standards Committee at its September meeting. The transition plan will take into consideration the evaluation of the recommended code sets to adequately express the categories of data elements in a variety of settings, the capacity of current EHRs to support the code sets, the implementation challenges for measure developers to incorporate these sets into existing, retooled, and de novo measures, other technical issues that may arise with further review of requirements to specify the code sets, and implications for certification criteria. 5

CONCLUSION We believe that these recommendations comprise a minimum necessary set of vocabulary standards that will enable effective expression of quality measures and interoperable electronic health record data elements. We appreciate the opportunity to provide these recommendations on the assignment of code sets to clinical concepts for use in quality measures, and look forward to discussion next steps. Sincerely yours, /s/ Jonathan Perlin, Chair, HIT Standards Committee /s/ John Halamka, Vice Chair, HIT Standards Committee Attachment: Glossary of Vocabularies/Standards 6

Appendix: Clinical Quality Measures Workgroup and Vocabulary Task Force September 9, 2011, Transmittal Letter Code Sets Glossary of Vocabularies/Standards ISO 639-2- Codes for the representation of names of languages Part 2: Alpha-3 code, is the second part of the ISO 639 standard, which lists codes for the representation of the names of languages. The three-letter codes given for each language in this part of the standard are referred to as "Alpha-3" codes. ISO 639-1 represents commonly-spoken languages with 2-character codes. CVX/MVX- The CVX code is a numeric string, which identifies the type of vaccine product used. The MVX code is an alphabetic string that identifies the manufacturer of that vaccine. Taken together, the immunization can be resolved to a trade name (the proprietary name of the product). ICF-International Classification of Functioning, Disability, and Health is a classification of the health components of functioning and disability. HL7 EHR System Functional Model-The HL7 HER System Functional Model provides a reference list of functions that may be present in an Electronic Health Record System (EHR-S). The function list is described from a user perspective with the intent to enable consistent expression of system functionality. This EHR-S Model, through the creation of Functional Profiles, enables a standardized description and common understanding of functions sought or available in a given setting (e.g. intensive care, cardiology, office practice in one country or primary care in another country). LOINC-Logical Observation Identifiers Names and Codes (LOINC) is a database and universal standard for identifying medical laboratory observations. LOINC applies universal code names and identifiers to medical terminology related to the Electronic health record. The purpose is to assist in the electronic exchange and gathering of clinical results (such as laboratory tests, clinical observations, outcomes management and research). Payer Typology- Payer Typology is a standard that allows consistent reporting of payer data to public health agencies for health care services and research. PHIN-VADS- the CDC Public Health Information Network (PHIN) Vocabulary Access and Distribution System (VADS) that supports the standards based vocabularies of the PHIN to

promote semantic operability and exchange of consistent information. A web based resource provides a system for accessing, searching, and distribution of vocabularies used within PHIN. RxNorm- RxNorm provides normalized names for clinical drugs and links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software, including those of First Databank, Micromedex, MediSpan, Gold Standard Alchemy, and Multum. By providing links between these vocabularies, RxNorm can mediate messages between systems not using the same software and vocabulary. SNOMED-CT (Systematized Nomenclature of Medicine--Clinical Terms) is a comprehensive clinical terminology, originally created by the College of American Pathologists (CAP) and, as of April 2007, owned, maintained, and distributed by the International Health Terminology Standards Development Organization (IHTSDO), a not-for-profit association in Denmark. UCUM-The Unified Code for Units of Measure is a code system intended to include all units of measure being contemporarily used in international science, engineering, and business. The purpose is to facilitate unambiguous electronic communication of quantities together with their units.

) Adverse Effect: Allergy or Non-Allergy Adverse Effect RX NORM for Medication that caused adverse effect SNOMED-CT for Non-Medication Substances that caused adverse effect SNOMED-CT for Adverse effect I Characteristics referred to CMS Age, Gender, Socioeconomic status, ethnicity, race, etc. Smoking status is included here. Communication SNOMED-CT Condition/ Diagnosis/ Problem (Both Active & Inactive) SNOMED-CT Device SNOMED-CT Non-Laboratory Diagnostic study Encounter (any patient--professional interaction; not restricted to billable event) (Patient) Experience Family History Functional Status Health record component LOINC--for the specific study name SNOMED-CT for appropriate findings UCUM for specific units of measure SNOMED-CT LOINC for assessment instruments SNOMED-CT for appropriate responses LOINC for assessment instruments SNOMED-CT for appropriate responses ICF (International Classification of Functioning, Disability, and Health) for categories of function LOINC for assessment instruments SNOMED-CT for appropriate responses LOINC---for naming of the components and for their relationships HL7 for the messaging among systems

Intervention (part of spectrum of procedures) LOINC for interactions that produce an assessment or measurable results SNOMED-CT for appropriate results and interventions that do not produce measurable results (e.g. counseling) Rx NORM for medications and inert ingredients SNOMED-CT for Non-medication Substances SNOMED-CT for Adverse effect Adverse effect other than allergy (Intolerance) LOINC for the test name and its results UCUM for units of Measures Laboratory test SNOMED-CT for appropriate results RxNorm for medications Medication Physical Exam Required for capture: Vital signs: charts for children 2 20 years, including BMI. CVX for Vaccines as the standard vocabulary (note: vaccines are treated as medications in some contexts and as separate category in others) LOINC for assessment instruments SNOMED-CT for appropriate responses Preference LOINC for assessment instruments SNOMED-CT for appropriate responses Procedure SNOMED-CT Risk evaluation LOINC for evaluation instruments SNOMED-CT for appropriate response SNOMED-CT Substance Symptom SNOMED-CT System resources LOINC for staffing resources HL7 for EHR functions SNOMED-CT for equpment

describe a transfer from one location or service to another measure] SNOMED-CT [Consider Deletion of Concept Category]