“Data Quality Tools You Can Use” (Part 2) Charlene Colon, Clinical Data Analyst Womack Army Medical Center, Fort Bragg, NC 7 June 2006.

Slides:



Advertisements
Similar presentations
EAS IV: ASD Table and DQ Business Rules
Advertisements

RiO R2 Enhancement overview. R2 changes and updates to Functionality Local System Administration New enhanced user administration screen with tab facilitates.
Data Quality Management Control (DQMC) Program
PCC Data Entry Coding Que Albuquerque Area Office Coding Que Training 1/18/07 – 1/19/07.
Section 1: Process to create EAS Interface File  DoD Batch and Timecard Status Report  DoD Employee Missing Payroll Data Report  Distribute Labor Cost.
Best Practices in Clinical Coding Panel: Capt. Clarence Thomas, Jr. BUMED, Ms. Michele Gowen, RHIA, CCS, and Ms. Erica Kreyenbuhl, CPC PAD Symposium 20.
MHS - Using 2008 Telephone Call Codes 1 New 2008 CPT Telephone Call Codes How to code in the MHS UBO Program Manager Dial in: CONF. CODE.
Health Care Claim Preparation & Transmission Chapter 8 OT 232 Lecture 2 1OT 232 Ch 8 lecture 1.
1 AHLTA Data Quality Management Course February 2009 Data Quality Management Course February 2009 DHIMS Sustainment.
“Process Checks for Data Quality ” Data Quality Management Control Program TRICARE Data Quality Course May 2010.
“Essentials for Data Quality ” Data Quality Management Control Program TRICARE Data Quality Course March 2011.
OUTLINE Section 1: DMHRSi Project Creating a new project
From Registration to Accounts Receivable – The Whole Can of Worms 2007 UBO/UBU Conference 1 Briefing:Implementing EHR is More than Pushing the On Button.
SHELLY GUFFEY MAKING THE MOST OF YOUR REVENUE CYCLE MANAGEMENT TECHNOLOGY
Coding Overview and the DQ Manager March Why Worry About Data Quality? I turned in my Data Quality Statement. Aren’t I done for the month?? I submitted.
Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout.
OUTLINE Section 1: DMHRSi Project Creating a new project
“Essentials for Data Quality ” Data Quality Management Control Program TRICARE Data Quality Course May 2011.
Data Quality Management Control (DQMC) Program DQMC Program Review List for FY 2012.
TMA Uniform Business Office Program Manager September 2011 Data Quality: UBO & The Revenue Cycle.
Data Quality: Uniform Business Office & The Revenue Cycle DHA Uniform Business Office Program Manager January 2015.
© 2013 The McGraw-Hill Companies, Inc. All rights reserved. Chapter 9 Tests, Procedures, and Codes.
Medication History: Keeping our patients safe. How do we get all of the correct details?
ZIMS With Medical Release 2.0 R2 An overview of the Medical Module in ZIMS and how it impacts the Animal Husbandry (R1) Module 1.
1 Implementation and Training Provider Taxonomy Changes for HIPAA 837 Claims Processing Audience for Training Database Administrators Clinical users The.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force Data Quality Management Program TSgt Jody Callender Air Force Data.
Data Quality Management Control Program
A “One A Day” Plan for Maximum Performance Charlene Colon, Clinical Data Analyst Womack Army Medical Center, Fort Bragg, NC 15 February 2006.
“Essentials for Data Quality”
Provider Specialty Code Table Aug 2006 Update Prepared by the UBO Program Support Team DSN x4072 Eastern Daylight Time Tuesday, 22 Aug 06, 10:00.
1 Clinical Documentation and Coding: The Way Forward CAPT Rebecca McCormick-Boyle Assistant Deputy Chief, Current Operations, BUMED M3B.
Workload Assignment Module Get up to speed. WAM Objectives Upon completion of this session, you will have: Understanding of how WAM interface works, and.
Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout.
Headquarters U. S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e U.S. AIR FORCE Data Quality Management Control (DQMC) Program TSgt.
Internal Management Controls Tri-SERVICE MEPRS CONFERENCE 28 August 2007.
Navy Data Quality Management Control (DQMC) Program DQMCP Conference February 2009.
Copyright © 2007, Oracle. All rights reserved. Managing Concurrent Requests.
MHS IM/IT Program The Military Electronic Health Record (EHR) AHLTA Update for the TRICARE Data Quality Training Course September 2006.
Outpatient Itemized Billing CY2006 Rate Package Update Release Presented by the UBO Program Support Team Dates: June 6, 2006 – 0800 & 1400 EDT June 8,
“Business Rules & Process Checks for Data Quality ” Data Quality Management Control Program TRICARE Data Quality Course September 2010.
Data Quality Management Program FY 06 Changes. Outline Introduction DQ Review List & Commander’s Statements DQ Data Submission Schedule.
“Medically Ready Force…Ready Medical Force” Data Quality Management Control (DQMC) Program DQMC Program Review List for FY 2016.
Attachment #11 - Agenda Item 5.12 “ Helping frontline users to perform their day-to-day jobs ” 21 October Medical Affirmative Claims MAC Enhancement.
2010 UBO/UBU Conference Health Budgets & Financial Policy 1 Briefing: Painting The Auditing Picture Date: 23 March 2010 Time: 1400–1450.
2010 UBO/UBU Conference Navy Medicine DQMC Breakout Session FY11 DQ Guidance and FY12 Preview.
2010 UBO/UBU Conference Title: AHLTA-Related Issues for Coders Session: W
0 eCPIC Admin Training: OMB Submission Packages and Annual Submissions These training materials are owned by the Federal Government. They can be used or.
Data Quality: UBO & The Revenue Cycle
2010 UBO/UBU Conference 1 Briefing: MTF Coding Audit Results for FY2007 Records Date: 23 March 2010 Time: 1610–1700.
Data Quality Management Control (DQMC) Program DQMC Program Review List for FY 2011.
“Data Flows, Processes and Errors – Oh My!” Clinical Data Analyst Womack Army Medical Center, Fort Bragg, NC May 2008.
“Data Checks for Data Quality” Clinical Data Analyst Womack Army Medical Center, Fort Bragg, NC February 2010.
2010 UBO/UBU Conference Title: MEPRS and the Performance Based Assessment Model (PBAM) Session: W UNCLASSIFIED.
To code, or not to code: that is the question: Whether 'tis nobler in the mind to suffer (786.5) The calls and s of outrageous fortune, Or to take.
“Essentials… ” Data Quality Management Control Program TRICARE Data Quality Course September 2012.
Data Quality Management Control (DQMC) Program DQMC Program Review List for FY 2012.
DHHS COE Meeting Agenda February 11, 2010 Welcome Introductions Contract Compliance Reporting Questions and Answers DHHS Open Windows Update.
TMA Data Quality Course - ADM
Military Health System, PPS, Benchmarking, Anesthesia Information Management Systems and YOU ?
TRI-SERVICE MEPRS CONFERENCE HOW TO ANALYZE AND IDENTIFY OUTLIER AVAILABLE FTE DATA IN OUTPATIENT ‘B’ ACCOUNTS Presented by Burma Barfield, Nicole Meyers,
Coding, How it all Connects Lesvia O Millican, CPC AETC Coding Consultant.
MEPRS Data Sources and Differences: EAS IV Repository vs. M2 Herb Escobar Axiom Resource Management
MEPRS Data Sources & Applications: EAS IV Repository vs. M Tri-Service MEPRS Conference Lansdowne, VA Herb Escobar
2010 UBO/UBU Conference Title: MEPRS and the Performance Based Assessment Model (PBAM) Speaker: Richard Meyer Session: W UNCLASSIFIED.
Reports for Managers Wendy Funk Kennell and Associates.
1 Direct Care Prof Encounters TMA / WISDOM Excerpt Direct Care Professional Encounters.
2010 UBO/UBU Conference Title: Data Integrity Breakouts (Navy) DQ – FY11 DQMC Guidance Speaker: Colleen Rees & Team Session: T
Business Objects Overview
Title: MEPRS Tools: MEPRS Early Warning & Control System (MEWACS)
Depart Process for Attendings and Residents
Presentation transcript:

“Data Quality Tools You Can Use” (Part 2) Charlene Colon, Clinical Data Analyst Womack Army Medical Center, Fort Bragg, NC 7 June 2006

2 Objectives  Explain Visit Workload vs Encounter Services  Overview of ADM Features  Coding Table Update Coordination  Encounter Data “Tune-Up”  Back-Up Slides - Interface Status Reporting Womack Army Medical Center Fort Bragg, NC Charlene Colon, Clinical Data Analyst Information Management Division, Clinical Data Team Womack Army Medical Center Fort Bragg, NC Charlene Colon, Clinical Data Analyst Information Management Division, Clinical Data Team

3 First There Was …

4 The “Bubble” Sheet…

5 No More Bubble Sheets… Key elements associated with the CHCS Visit, not updatable in ADM Only elements in Reverse Video can be updated in ADM Enter data in ADM with INSERT OFF

6 And Now…

7 Why the Focus?  Standardize data collection methods  Compare workload and productivity  Measure efficiency per Provider FTE  Forecast demand for services  Establish performance benchmarks  Identify trends and utilization  Calculate costs of services  Assess and improve quality of services

8 Encounter Services  ICD-9 Code – Why the Patient was seen? -Diagnosis and Chief Compliant  CPT Code – What was done to address the patient problem? -Physician/Provider Services -Procedures Performed and Units of Service -Modifiers (explain additional details about the Service or Procedure)  HCPCS Code - What services/supplies were provided?  Evaluation & Management Code (CPT Code): -Setting Inpatient, Emergency Room, Preventive Service, Consult, etc. -Level of Services Complexity (Minimal, Low, Moderate, or High)

9 Correct Coding…

10 Basic Features  Standard Coding Look-Up Tables: -ICD-9 (including Military Unique Codes) -CPT/HCPCS -Modifiers (CHCS Modifier Mapping Table – KG ADS MODIFIER)  Clinic Favorites Coding Lists  Each patient encounter must contain: -1 Diagnosis Code -1 E&M (or “99499” entered as a “Placeholder”)  Secondary Providers -Supervising, Attending, Paraprofessional, Assisting, GME, Operating Provider, Surgeon, Anesthesia and Nurse  Creates Admission, Daily & Disposition RNDS* Encounters to capture Inpatient Attending Provider Professional Services -Industry Based Workload Alignment (IBWA)  AHLTA encounters “Written-Back” to ADM (SADR Write-Back) -When encounter is signed as “Complete” or Updated and re-signed  Encounters Reviewed as “Complete” in the CCE update ADM

11 Additional Features  HIPAA Standard elements: -Cause of Injury (and associated elements) -Geographic Location of Injury (Motor Vehicle Accidents) -Pregnancy Related (and associated elements)  Additional E&M Codes (up to 2 Additional E&M Codes)  Diagnosis Code Priority (Links Procedure to Dx)  CPT Code Units of Service (per CPT Code)  CPT Code Modifiers (up to 3 – per CPT Code)  Additional Provider Face-To-Face Time Calculator  Military Unique ICD-9 Codes (ICD-9 Code Extenders) -V70.5 4PRE-DEPLOYMENT EXAMINATION -V70.5 5DURING DEPLOYMENT EXAMINATION -V70.5 6POST-DEPLOYMENT EXAMINATION  Encounter Disposition (Inpatient and Ambulatory)

12 Visits vs Encounters  An “ENCOUNTER” = Services Provided -Documents reason for seeking care -Captures medical services provided -Establishes level of professional service and decision making -Identifies Staff (By Name) providing the services  A Count Visit is Always an Encounter, but not all Encounters meet the definition of a Count Visit for reporting in WAM/EAS IV, EAS “Eligible” Encounters and Worldwide Workload (WWR)  DQMC Statement 8. a) - # SADR encounters / # WWR visits -# SADRS should always be equal to or greater than Visits

13 PENDING vs PENDING  PENDING “Visit” Status: (Bad…) -Incomplete Workload  PENDING “SADR” Status: (Good…) -Encounters Coded as Complete or Updated, that pass SADR Edits, will be included in the next daily SADR ASCII batch file -SADR Nightly process is tasked to run ~2130 each night, in CHCS Includes ADM & AHLTA completed encounters Includes ADM, AHLTA and CCE Updates See Notes View for additional information

14 Coding Table Updates  ICD-9 – Updated per Fiscal Year  CPT/HCPCS – Updated per Calendar Year (Effective 1 Jan 06)  There is NO “Grace” period to implement table updates  ADM only maintains CURRENT YEAR Code Tables  Downstream Impacts: -Prior year codes not available for prior year encounters in ADM -CCE supports the use of correct codes, based on Date of Service, but the correct codes will be rejected by ADM -AHLTA Provider/Clinic maintained templates will allow obsolete codes to be selected, but will be rejected by ADM  Establish a Code Table Update/Synchronization Plan! -Plan/Discuss Code Table Update synchronization with AHLTA, CHCS, TPOCS, CCE, EAS, and any other system affected... -Identify planned release dates for each system -Identify any coding backlogs potentially impacted -Ensure “Review Complete” status in CCE for all billable encounters -Document the Update/Install Date for each system for future reference

15 Air Force Data, Data Everywhere… MDR M2 WWR (Count Visits) EAS IV “Eligible” Encounters CPT Codes Units of ServiceWAM Count Visits & Raw Services SIDR (Admissions) SADR (Encounters) TPOCS Billable Encounters PDTS Worldwide Workload Report Standard Ambulatory & Inpatient Data Record EAS Repository EAS IV Extract MHS Data Repository MHS Mart Service Repository Pharmacy Data Transaction System Pop Health Portal CCE Coding Compliance Editor Clinical Data Mart TRICARE Ops Center Navy Army Interface Errors DoD/VA SHARE

16 Interface Status Reports 1.ADM Interface Error Report -CHCS ADM Menu Option Report #5 -Errors – Encounter failed SADR edits – Not sent to CCE -Warnings – May impact TPOCS encounter data 2.CCE Interface Error Report -CHCS Menu Option CCE -Report of CCE Write-Back errors -ADM not updated to generate updated SADR 3.AHLTA Write-Back Error Report -Coordinate with your AHLTA System Admin to run the report -ASCII File of AHLTA Write-Back errors -AHLTA encounter not accepted or received by ADM -SADR not created -Encounter not sent to TPOCS, CCE or EAS

17 Encounter Data “Tune-Up”

18 ADM Reports Menu STYL User Prompt Style 1 Appointments with No ADM Records by Clinic 2 ADM Patients with 3rd Party Insurance 3 ADM Compliance Report 4 ADM Records with Unresolved Coding Issues 5 Interface Transmission Status of ADM Record 6 Encounter Summary Report by Clinic/Provider 7 For Clinic Use Only Report 8 Encounter Specific Code Report by Clinic/Provider 9 Top Number Encounter Report 10 Appointment/Encounter Count Report 11 Patient Encounter Records Report STYL User Prompt Style 1 Appointments with No ADM Records by Clinic 2 ADM Patients with 3rd Party Insurance 3 ADM Compliance Report 4 ADM Records with Unresolved Coding Issues 5 Interface Transmission Status of ADM Record 6 Encounter Summary Report by Clinic/Provider 7 For Clinic Use Only Report 8 Encounter Specific Code Report by Clinic/Provider 9 Top Number Encounter Report 10 Appointment/Encounter Count Report 11 Patient Encounter Records Report Detailed “How To” run the ADM Compliance Report

19 Compliance Report (IBWA) Type ADS to access the Ambulatory Data Module Select PAD System Menu Option: ADS Ambulatory Data Module Select Ambulatory Data Module Option: 2 Ambulatory Data Reports Select Ambulatory Data Reports Option: 3 ADM Compliance Report Select (D)MIS ID, (U)ser current division as filtering type or (Q)uit: U// D Select (O)ne, (M)ultiple, (A)ll DMIS ID or (Q)uit: A// O Select DMIS ID: WOMACK AMC Select (C)linic, (P)rovider as primary sort or (Q)uit: C// C Select (O)ne, (M)ultiple, (A)ll ADM clinics or (Q)uit: A// M +* ADMISSIONS EKAA * AMIC CL BIAB Summarize by provider (Y)es, (N)o, or (Q)uit: Y// N Select (D)MIS, (M)EPR, (C)linic clinic sort order or (Q)uit: C// Select (O)ne, (M)ultiple, (A)ll appointment status or (Q)uit: A// A Include inpatient admitted by another service (Y)es, (N)o, or (Q)uit: Y// Y Select (C)ount, (N)on-Count, (E)rror non-count, (B)oth as workload type or (Q)uit: B// B Select (M)onth and year, (S)pecific start and stop as date range or (Q)uit: S// M Enter Month & Year: Apr 2006// (Apr 2006) Do you want to proceed with this report? No// Y Select DEVICE: Q  Select EKAA for IBWA RNDS* Encounters and one other Clinic  Choose “No” to Summarize by Provider

20 IBWA % Compliance  Generate the ADM Compliance Report -# Completed IBWA Encounters  Generate the WWR to calculate: -# OBDS -# Dispositions 07 Feb For Official Use Only Page 1 Ambulatory Data Module ADM Compliance Report by Clinic From: Dec 2005 Thru: Dec 2005 Clinic PAS Complete Incomplete % Total ADM Total ADM Total Compliance ================================================================================ 0089 EKAA IBWA CLINIC BAA0 INTERNAL MEDICINE-OBS Grand Total

21 Show Me the Data!

22 SADR Data Workbook  Import Daily SADR extracts: -Excel Macro parses SADR file by DMIS -SADR SHOOTER.mdb  Copy/Paste into Excel Workbook  “Ready Data” for your “DQ Radar”  Identify trends for user feedback  Supports DQ Process Improvement  Drill Down into specific problem areas  Create encounter data reconciliation lists for Clinic Staff See Notes View for additional “How To” information

23 DQ “Check Points”  Allied Health Coding (PT/OT, Audiology, Mental Health, Optometry, etc.) -MTFs will be decremented for incorrect Allied Health E&M Coding!  E&M Coding for Nurses and Technicians -Important Training Issue for Nurses and Technicians with RN Wellness Role in AHLTA  E&M Distribution: -By Provider -By 4 th Level FCC -New vs Established Encounters -Sick vs Well Encounters -New vs Consult Encounters  Diagnosis Capture (Frequency and Tabular Lists)  Procedures/Services and Supplies  Updated Encounters -Also review CCE Coder/Provider Comparison Report  Provider Medical Specialty (Direct Care <=905)

24 Allied Health Locations Allied Health Locations should not have E&M Services CPT Codes for procedures performed by Allied Health Providers identify the Professional Services provided Prepare reconciliation list for Clinic Staff

25 The “99499” Placeholder  The “99499” E&M Code Placeholder is required when E&M Services were not provided  E&M Code is optional for APV and encounters (June 2005)  E&M Code is also not required for Non-Count Visits (June 2005)  Current recommendation is to continue to enter the E&M Code Placeholder -TPOCS still requires the “99499” Placeholder

26 E&M By Specialty RNs (600)/Techs (900) with Physician Level E&M Services Prepare Reconciliation List for Clinic Staff Provide Option to correct in either AHLTA or ADM Click on any cell to display detailed data for review

27 Drill Down Reconciliation  Copy the APPT_IENs  Prepare CHCS Query File to identify patient encounters for reconciliation

28 Appointment IEN  CHCS Appointment Internal Entry Number (IEN) included in the SADR is also the Record ID in M2  Use ` (Grave Key) and Appointment IEN to identify specific encounters in CHCS to support reconciliation: -FM->IFE->PATIENT APPOINTMENT -FM->IFE->KG ADC DATA  Create Query List to paste into CHCS PATIENT APPOINTMENT File or KG ADC DATA File: -` ` `

29 CHCS Ad-Hoc Query Output from what file: PATIENT APPOINTMENT// ( entries) NAME: GS CCC PT NAME EXTRA FF Replace DESCRIPTION: 1>DQ RADAR Reconciliation Flat File EDIT Option: READ ACCESS: &SHARKPONDFLYsharkpondflyQq Replace WRITE ACCESS: &SHARKPONDFLYsharkpondflyQq Replace First Print FIELD: "`"_NUMBER;X// Then Print FIELD: "^"_RA DATE TIME(APPOINTMENT DATE/TIME);X Replace Then Print FIELD: "^"_PROVIDER;X// Then Print FIELD: "^"_MEPRS;X// By 'MEPRS', do you mean the PATIENT APPOINTMENT 'MEPRS CODE' Field? YES// (YES) Then Print FIELD: "^"_NAME;X// Then Print FIELD: "^"_WORKLOAD TYPE;X// Then Print FIELD: "^"_APPOINTMENT TYPE;X Replace Then Print FIELD: Heading: Footnote: Store Print logic in Template: GS CCC PT NAME EXTRA FF//

30 Measuring Performance Appointments Visits Encounters RVU  Planned  Open  Booked  Kept  No-Show  Cancelled (Patient)  Cancelled (MTF)  Cancelled (TOL)  Walk-In/Sick-Call  Occ-Svc  T-CONS  ADMIN  Open (Not Coded)  Complete  LWOBS  Population Risk  Outcomes  Practice Profile  Quality of Services Capacity Workload Services Weighted Value  Simple RVU  Average RVU/Encounter  RVU/Provider FTE/Day  Prospective Payment System (PPS) RVU  EAS RVU (Facility) Focus Shifting from “Counting Visits” to Measuring Work/Services Provided

31 Questions?

Back Up Slides for ADM Interface Status Reporting

33 ADM Interface Errors ADM Errors FY 06Total ERR: 209 Appt_status null or missing. (AHTLA Completed Encounter with change to Admin in CHCS EOD)118 ERR: 222 Disposition missing based on status. (No-Show then changed to Kept)60 ERR: 240 Found E&M code where not allowed. (Cancelled with Encounter Coding still in record)14 ERR: 243 Ambulatory flag set where not allowed.1 ERR: 251 Disposition Type does not match Patient Status (Change DC to Release w/o Limitations)38 ERR: 253 No provider associated with a CPT code. (New as of June 2005)3 ERR: 254 Injury Related data missing (HIPAA Injury Related data)1 ERR: 257 Supervising Provider is required. (New as of June 2005 Warning 457: Required Supervising Provider not entered in AHLTA Grand Total311  ADM Interface Error Report lists key elements to facilitate reconciliation: -Coordinate reconciliation coordination with responsible Clinic Staff -Errors prevent SADR from being created -Warnings may impact billable encounters -457 Warnings – Not currently included in the EAS SADR Extract (since June 2005) -CHCS Fix planned for Summer 2006 to allow encounters in Warning Status to be sent to EAS

34 CCE Interface Errors 26 May Personal Data - Privacy Act of 1974 (PL ) Page 1 CCE INTERFACE ERROR REPORT From: 01 Apr Thru: 25 May ================================================================================ DIVISION: WOMACK AMC FT BRAGG NC Invalid CPT code: Apr 30 Dec EMERGENCY ROOM BIAA Invalid CPT code: J Apr 30 Mar WFM-TEAM HONOR BGAA Invalid Secondary Provider Role Apr 22 Mar REFRACTIVE EYE CTR BBDQ Invalid patient IEN: Apr 26 Mar GYNECOLOGY APV BCB5 Invalid Secondary Provider May 25 Apr WFM-TEAM DUTY BGAA Injury Cause Code is missing May 30 Nov AMIC CL BIAB Injury Date is missing May 22 May WFM-TEAM DUTY BGAA Modifier 27 is not valid for code Apr 03 Apr RHC TEAM 2 BGAR Dx/Priority mismatch for

35 AHLTA Write-Back Errors