Direct Referenced Codes – Update

Slides:



Advertisements
Similar presentations
Quality Measures Vendor Tiger Team December 13, 2013.
Advertisements

Query Health QRDA Requirements
Minet Javellana, RN Eligible Professionals eCQM Project Lead
QIDAM Issues and proposals for a logical model For discussion during HL7 WG Meeting in Jan 2014 Thursday Q3.
Introduction ICD-10-CM Overview Presented By Erline Franks CCS-P.
Coding Clinical Encounters. Definition of Terms: CPT E/M and Procedure Codes The CPT E/M section is divided into broad categories such as office visits,
VSAC Users’ Forum Thursday, January 15 2:00 – 3:00 PM, EST.
Chapter 19.   How to select the evaluation and management level of service Objective.
1 Work Plan for Testing the LIS and EHR Systems Define Test Flow based from Work Flow Define a testing methodology Develop high-level requirements for.
1 APCD Analytical Workgroup May 30,
Performance Measures 101 Presenter: Peggy Ketterer, RN, BSN, CHCA Executive Director, EQRO Services Health Services Advisory Group June 18, :15 p.m.–4:45.
Session III: Application and Authoring Luke Rasmussen Feinberg School of Medicine, Northwestern AMIA.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
Query Health Concept-to-Codes (C2C) SWG Meeting #12 March 6,
Measure Authoring Tool: An Introduction Please dial-in to the number provided below. We will begin shortly. Webinar Call-In Information.
Nursing Library Training using Sunrise Press data.
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
Understanding eMeasures – And Their Impact on the EHR June 3, 2014 Linda Hyde, RHIA.
Performance Measures 101 Presenter: Peggy Ketterer, RN, BSN, CHCA Executive Director, EQRO Services Health Services Advisory Group March 28, :00.
Recommendations on QRDA Category-III Aggregate Report for Query Health Results Format Srinivas Velamuri, Software Architect, Telligen.
Standards Analysis Summary vMR –Pros Designed for computability Compact Wire Format Aligned with HeD Efforts –Cons Limited Vendor Adoption thus far Represents.
Care Provision. EHR Functional Lists (HL7) Patient History lists – Allergies Medications Immunizations Medical Equipment Orders/Interventions Results.
New York State DOH Health Home Care Management Reporting Tool (HH-CMART) Support Calls – Session #3 March 6,
Query Health Technical WG 6/14/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm QRDA Discussion2:10 – 3:00 pm.
Query Health Technical WG 5/10/2012. Agenda TopicTime Slot Administrative stuff and reminders2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm HQMF Consensus.
New York State DOH Health Home Care Management Reporting Tool (HH-CMART) Support Calls – Session #6 March 27,
QDM and vMR Harmonization. Background  Initial discussion at HL7 Working Group Meeting in January  Goal is to have one model for quality that can support.
Structured Data Capture (SDC) FHIR SDC Pilots Template
Implementation Workgroup Udayan Mandavia, iPatientCare, Inc. With: Kedar Mehta and Arnaz Bharucha July 28, 2014 Constraining the CCDA User Experience Presentation.
Clinical Terminology and One Touch Coding for EPIC or Other EHR
EHR Coding and Reimbursement
ICD-10 Updates & review.
T3/Tutorials: Data Submission
Procedure Note (V3) ** = Required sections
EHR Incentive Program 2017 Program Requirements
QRDA I STU R5 Updates Since pre-ballot content Review
UDI Key Features: Medical Device Integration
Superbills.
HQMF Change Review Februrary 17th, 2017.
Nursing Special Interest Subgroup – Observables Mapping
DATABASE SEARCH & REVIEW GETTING STARTED GUIDE FOR EMIS WEB USERS
The subcontract template
SCC P2P – Collaboration Made Easy Contract Management training
Overview of Request for Comments ONC 2017 Interoperability Standards Advisory ONC looking for comments on any last revisions, additions, or recommendations.
WP1: D 1.3 Standards Framework Status June 25, 2015
Patient Volume Pitfalls Massachusetts Medicaid EHR Incentive Program September 19 & 20, 2017 Hello, and welcome. Thanks for joining us today to.
Component 11/Unit 7 Implementing Clinical Decision Support
VSAC and Quality Measures
Lucrecia Johnson MSW, LSW Mary Bartlett MSW, LISW-S
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.3 Manage Medication List aka DC in EHR-S FM
19 Medical Coding.
Frequently asked questions
eHIVQUAL & Azara Concluding the 2016 Review April 19, 2017
ECDS Early Childhood Data System Texas Student Data System August 2018
Relevant and Pertinent Short Survey Results
1115 Behavioral Health Learning Collaborative
Nutrition Care Plan: Stakeholder Call
2-1-1 Automated Verifications
Please mute yourselves, on phone or computer. Thank you.
TELPAS Alternate Student Eligibility
HEDIS® Compliance Audit™ and Supplemental data
Employee Self Service – Benefit Enrollments
Relevant and Pertinent Short Survey Results
To start the presentation, click on this button in the lower right corner of your screen. The presentation will begin after the screen changes and you.
Medical Insurance Coding
Commentary General Comments:
Medical Students Documenting in the EMR
Use Synthea Generated Patient Data for Clinical Quality Measure – Case Study: CMS165 Controlling High Blood Pressure Peter Li, OSEHRA 2/21/2019.
Observation vs Inpatient
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

Direct Referenced Codes – Update A Direct Referenced Code is a single code, not a member of a value set Reason – “Hiding” a single code within a value set creates additional overhead and hides the intellectual property of the code system. Note: Value sets containing a single code may still be allowed: All except 1 code in a value set has been retired by the code system (no need to convert to direct referenced code) Additional concepts are forthcoming but only 1 code is currently available – E.g., only 1 medication in a class is FDA approved but others are expected – a single code Value set is appropriate

Direct Referenced Codes using HQMF [Includes Value Sets and Direct Referenced Codes] HQMF Measures Published in 2017 for Reporting 2018 HQMF Measures Published in 2018 for Reporting 2019 Data Criteria Section (Examples from CMS136): "Diagnosis: Narcolepsy" using "Narcolepsy Grouping Value Set (2.16.840.1.113883.3.464.1003.114.12.1011)" "Encounter, Performed: Behavioral Health Follow-up Visit" using "Behavioral Health Follow-up Visit Grouping Value Set (2.16.840.1.113883.3.464.1003.101.12.1054)" "Encounter, Performed: Discharge Services- Observation Care" using "Discharge Services- Observation Care Grouping Value Set (2.16.840.1.113883.3.464.1003.101.12.1039)" Data Criteria Section (Examples from CMS136): "Diagnosis: Narcolepsy” "Encounter, Performed: Behavioral Health Follow-up Visit” ” Encounter, Performed: Discharge Services- Observation Care” Terminology Section "Narcolepsy Grouping Value Set (2.16.840.1.113883.3.464.1003.114.12.1011)" "Behavioral Health Follow-up Visit Grouping Value Set (2.16.840.1.113883.3.464.1003.101.12.1054)” “Observation Care Discharge Day Management 99217 CPT 2016 2.16.840.1.113883.6.12” NEW SECTION Value Sets Direct Referenced Codes Note: Value set and direct referenced code examples are for demonstration purposes only.

QRDA – Moving to 2019 Reporting For 2019 Reporting Option 1 For 2018 Reporting QRDA Category I v4 QDM 4.3 Template Value Set OID Value (code) QRDA Category I v5 QDM 5.02 Template Value Set OID Value (code) Direct Referenced Codes (no OID)

QRDA – Moving to 2019 Reporting Opening the discussion about allowing direct referenced codes (i.e., codes without a value set OID) generated further discussion about the need for OIDs universally when also submitting a code. Justification for removing the value set OID from QRDA Category I: If a single instance of a code exists in the EHR and it is included in 2 or more value sets referenced in a measure, the sender must submit the code for each referenced value set. I.e., the QRDA contains multiple references to the same code instance. If the QRDA did not require the value set OID, each instance of the code could be submitted only once. Risks of removing the value set OID requirement completely: Those sending QRDA files would need to retool. Some vendors indicate the retooling would not be problematic and it would remove the need for duplication. Those receiving QRDA files would need to retool AND to validate if the codes received are in the required value sets using data from VSAC rather than the OIDs in the QRDA file. For 2019 Reporting Option 1 QRDA Category I v5 QDM 5.02 Template Value Set OID Value (code) Direct Referenced Codes (no OID)

QRDA – Moving to 2019 Reporting For 2019 Reporting Option 2 – Remove the requirement to send the value set OID For 2019 Reporting Option 1 For 2018 Reporting QRDA Category I v4 QDM 4.3 Template Value Set OID Value (code) QRDA Category I v5 QDM 5.02 Template Value Set OID Value (code) Direct Referenced Codes (no OID) QRDA Category I v5 QDM 5.02 Template Value (code) Direct Referenced Codes (no OID) OR

QRDA – Moving to 2019 Reporting (for NOT DONE) For 2018 Reporting – Data Elements NOT DONE For 2019 Reporting Option 1 – Data Elements NOT DONE For 2019 Reporting Option 2 – Data Elements NOT DONE QRDA Category I v4 QDM 4.3 Template negated Value Set OID NO VALUE QRDA Category I v5 QDM 5.02 Template negated Value Set OID NO VALUE or negated Direct Referenced Codes (no OID) QRDA Category I v5 QDM 5.02 Template NO VALUE or negated Direct Referenced Codes (no OID) OR negated Value Set OID For Data Elements NOT DONE, there is no difference between the options. The OID is still required if a value set exists

Example of duplicates – medication administered – route is repeated so 20 duplicates