navy data quality management control program (dqmcp) dqmcp conference navy breakout

69
Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Upload: charles-ralf-hodge

Post on 17-Dec-2015

219 views

Category:

Documents


5 download

TRANSCRIPT

Page 1: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Navy Data Quality Management Control Program (DQMCP)Navy Data Quality Management Control Program (DQMCP)

DQMCP Conference Navy BreakoutDQMCP Conference Navy Breakout

Page 2: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Dilbert on Data Quality…

Page 3: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

DQMCP Components

Commander’s Statement

Navy DQMCP Roles and Responsibilities

DQMC Process Flow and Deadlines

1

4

3

2

Page 4: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

• Critical MTF Staff: Commanding Officer / ESC, Data Quality Manager, Data Quality Assurance Team

• DQMC Review List: Internal tool to identify and correct financial / clinical workload data and processes

• Monthly DQMC Commander’s Statement: Monthly statement forwarded through the MTF Regional Command to BUMED and TMA

DQMCP Components1

MTF DQMCP Components

Page 5: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

• Meets Regularly With DQMC Manager• Acts as Subject Matter Experts • Identifies / Resolves Internal DQMC Issues• Team Membership (minimum):

– MEPRS– Coding / PAD / Medical Records– CHCS, AHLTA, and ADM Experts– Physician / Provider Champion– Executive Link– Business Analysts

DQMCP Components1

DQMCP MTF Teams

Page 6: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Leadership commitment and DQMC structure

Timely and accurate

Ensure accurate,

complete and timely data

IA, access breach

Organizational

Factors

Data Input

Data Output

Security

DQMCP Review ListDQMCP Components1

System administrator

ID, IT business

processes

System Design

and Training

Page 7: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Navy DQMCP Roles and Responsibilities2

BUMEDProgram management, oversight,

policy and strategies.

MTFsDQMCP execution, Review List,

Commander’s Statement, CO briefs, and communication of issues to

regional representatives.

NMSCSystems execution,

website maintenance / development, and DQMCP support.

REGIONSRegional consolidation of Commander’s Statements, DQMCP coordination, issue

resolution, audits and training.

Page 8: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

BUMED NMSC NAVMISSA NME

Navy DQMCP Roles and Responsibilities2

NCA NMW

DQMCP Points of Contact

Page 9: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

NAVMISSA Consolidated Call Center“Who do I call?”

– Toll Free: 1-866-755-NAVY (6289)– Commercial: 304-367-9462– E-mail: [email protected]

“How do I know the status of my problem?”– Broken functions to existing products are closely monitored by the NMSC

DQMC Program Manager. – Weekly status reports are posted to the DM SharePoint site for visibility. – Your problem is not considered solved until you say it is solved.

“What if I have a new need or good idea?”– MTFs are encouraged to provide any proposed requirements or ideas for

improvement to their Regional DQ Manager.– BUMED and Regional DQ Managers will vote and prioritize items based on

available resources.

Navy DQMCP Roles and Responsibilities2

Page 10: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Recurring DQMCP TasksDQMC Process Flow and Deadlines3

Daily Monthly Annually

• SADR Transmission• End of Day (EOD)• Coding Compliance

• SIDR Transmission• WWR Transmission• Appt. File Transmission• DRG File Transmission• EAS File Transmission• EAS / FinancialReconciliation

• DMHRSi Timecards100% Completed

• MEWACS Review• Coding Audits• DQMCP Review List• Commander’s Statement

• Coding Table Updates• DMIS ID Table Updates• EAS Table Updates• MEPRS Code Changes

Page 11: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

DQMCP System Process FlowDQMC Process Flow and Deadlines3

Page 12: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Reporting Timeframes for DQMCPDQMC Process Flow and Deadlines3

* Timeframes may be updated as the year progresses, be sure to obtain the most current version from the BUMED Financial Guidance Portal at: www.navmedfinancial.org

Page 13: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Commander’s Statement Overview

• 11 Questions, 37 Individual Elements

• Submitted monthly to BUMED via the Regional Commands (and sent to TMA via BUMED)

• Signed and reviewed by the Commanding Officer

• The month reported on the statement is two months behind the current month (March’s submission is for January data)

• When a system-wide issue prevents completing an element on the eDQ, BUMED will provide a standard response for the MTFs to use.

Commander’s Statement4

Page 14: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

Commander’s Statement Overview

• For any question where a difference between an MTF’s submission and the automatic eDQ calculation is greater than 2%, a NAVMISSA Trouble Ticket # (and source for the local number) must be included in the comments section.

• MTFs are required to provide comments, an MHS Trouble Ticket and a POAM for actions being taken to resolve non-compliant (<80%) metrics and metrics that have significantly decreased (10% or more) from the prior month.

Commander’s Statement4

Page 15: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

1a : EOD Every Appointment, Every Day

Commander’s Statement – End of Day (EOD)4

1 (a)

Methodology:• Two timeframes:

• Clinics with normal hours complete EOD by midnight • 24 / 7 Clinics complete EOD by 0600 the next calendar day

• 1a - # of Appointments Closed by midnight (or 0600) / # of Appointments• Metric is dependent on the receipt of each site’s DQMC Appointment Audit File

Includes:• MEPRS Codes B*** and FBN*• Appointment status KEPT, WALK-IN or SICK CALL

Excludes:• Appointment status of T-CON, CANCELLED, ADMIN or LWOBS• Appointments not within the reporting month

*Auto-Populated by the NAVMISSA eDQ*

*Local Data Should be Calculated Using the BUMED Approved CHCS Ad-hoc*

Page 16: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

1a : Historical EOD

Commander’s Statement – End of Day (EOD)4

1 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 17: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

1a : EOD Calculation Accuracy

Commander’s Statement – End of Day (EOD)4

1 (a)

NOLA transition impacted the file receipts at NAVMISSA, inflating the

calculation difference (blue data points are adjusted to reflect actual data

received).

NOLA transition impacted the file receipts at NAVMISSA, inflating the

calculation difference (blue data points are adjusted to reflect actual data

received).

NMSC and NAVMISSA Tiger Team On-Site

NMSC and NAVMISSA Tiger Team On-Site

BUMED 2% Goal

BUMED 2% Goal

Page 18: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2a : Historical SADRs Coded in 3 Business Days

Commander’s Statement – Coding Timeliness4

2 (a)

Methodology:• Compliance is determined by the number of business days between the

appointment date and the date a SADR is transmitted.• 2a - # of SADRs coded within 3 business days / Total SADRs

Includes:• MEPRS Codes B*** and FBN*

Excludes:• APVs• SADR Appointment Status CANCELLED, LWOBS, ADMIN or TCON• Weekends and Federal Holidays

*Auto-Populated by the NAVMISSA eDQ*

Page 19: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2a : Historical SADR Coding

Commander’s Statement – Coding Timeliness4

2 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 20: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2b : APVs Coded in 15 Calendar Days

Commander’s Statement – Coding Timeliness4

2 (b)

Methodology:• Compliance is determined by the number of calendar days between the APV date

and the date a SADR is transmitted.• 2b - # of APVs coded within 15 calendar days / Total APVs

Includes:• MEPRS Codes B**5, B**6 and B**7.• Note: APV flag is not currently used as it is not consistently utilized.

Excludes:• All other MEPRS Codes• SADR Appointment Status CANCELLED, LWOBS, ADMIN or TCON

*Auto-Populated by the NAVMISSA eDQ*

Page 21: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2b : Historical APV Coding

Commander’s Statement – Coding Timeliness4

2 (b)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 22: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2a and 2b : SADR Compliance Calculation Accuracy

Commander’s Statement – Coding Timeliness4

2 (a, b)

NOLA transition impacted the file receipts at NAVMISSA, sites with transmission issues were removed from the metrics on this slide

(retransmitting impacts the SADR Extract Date).

NOLA transition impacted the file receipts at NAVMISSA, sites with transmission issues were removed from the metrics on this slide

(retransmitting impacts the SADR Extract Date).

NMSC and NAVMISSA Tiger Team On-Site

NMSC and NAVMISSA Tiger Team On-Site

Tiger Team impact on the calculations was minimal as only a small percentage of SADRs fall on the

border of compliance where a methodology change would have an influence.

However, since January 2009 (FM4) sites have steadily been more accepting of the eDQ calculation

as sites are educated on how to calculate the two metrics. Also, the elimination of TCONs from the

FY10 metric has reduced local variation.

Tiger Team impact on the calculations was minimal as only a small percentage of SADRs fall on the

border of compliance where a methodology change would have an influence.

However, since January 2009 (FM4) sites have steadily been more accepting of the eDQ calculation

as sites are educated on how to calculate the two metrics. Also, the elimination of TCONs from the

FY10 metric has reduced local variation.

Page 23: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2c : SIDRs Coded in 30 Calendar Days

Commander’s Statement – Coding Timeliness4

2 (c)

Methodology:• Compliance is determined by the number of calendar days between the disposition

date (“E” records) and the date a SIDR is coded (“D” records).• Date coded is determined by the DRG assignment date transmitted to NAVMISSA

in the DRG file.• 2c - # of SIDRs coded within 30 calendar days / Total SIDRs

Includes:• All “D” and “E” SIDRs

Excludes:• SIDR files received after the 15th of the month freeze.• Any “F” or “C” SIDRs• Resource Sharing and VA workload

*Auto-Populated by the NAVMISSA eDQ*

Page 24: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

2c : Historical SIDR Coding

Commander’s Statement – Coding Timeliness4

2 (c)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 25: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

3a : MEPRS/EAS Financial Reconciliation3b: MEWACS Reviewed and Anomalies Explained

Commander’s Statement – MEPRS Reconciliation4

3 (a, b)

Methodology:• Both questions are answered “Yes” or “No” by each MTF.• 3a – Financial reconciliation must be completed, validated and approved prior to

the monthly MEPRS transmission. BUMED policy is to answer “Yes”, since this process is performed by BUMED.

• 3b – MTFs must review the current version, regardless of whether it matches the reporting month or not (this question should always be “Yes”).

Includes:• Not applicable

Excludes:• Not applicable

Page 26: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

3a : Historical MEPRS/EAS Financial Reconciliation3b: Historical MEWACS Review

Commander’s Statement – MEPRS Reconciliation4

3 (a, b)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 27: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

3c : DMHRSi Timecards Submitted by Suspense3d: DMHRSi Timecards Approved by Suspense

Commander’s Statement – MEPRS Reconciliation4

3 (c, d)

Methodology:• Both questions are provided by BUMED.• 3c - Timecards “Submitted”, “Working”, “Rejected” or “Approved” / Total

Timecards on the BUMED DMHRSi Interim Report Date• 3d – Timecards “Approved” / Total Timecards on the BUMED DMHRSi Final

Report Date

Includes:• Not applicable

Excludes:• 3c does not include “Not Submitted” or “Working”

Page 28: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

3c : Historical DMHRSi Timecard Submission3d: Historical DMHRSi Timecard Approval

Commander’s Statement – MEPRS Reconciliation4

3 (c, d)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 29: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

4a : MEPRS/EAS in 45 Calendar Days4b : SIDR by 4th Calendar Day4c : WWR by 4th Calendar Day

Commander’s Statement – Data Transmission4

4 (a-c)

Methodology:• All three measures are “Yes” or “No” and calculated based on the day the files

were successfully transmitted to NAVMISSA, not when the transmissions were attempted.

• If 4a is “No”, questions 8c and 8d should use local WAM data.• Note: For 4b and 4c, compliance is measured by 5th Business Day and 10th

Calendar day for TMA reporting purposes.

Includes:• MEPRS/EAS – 1 File per Parent DMIS• SIDR / WWR – Number of files expected is MTF dependent.

Excludes:• Re-submissions (updated data) do not count against this metric.

*Auto-Populated by the NAVMISSA eDQ*

Page 30: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

4a : Historical MEPRS/EAS4b : Historical SIDR4c : Historical WWR

Commander’s Statement – Data Transmission4

4 (a-c)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 31: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

4d : SADR Transmitted Daily

Commander’s Statement – Data Transmission4

4 (d)

Methodology:• SADR transmissions are reported as a percentage, since they are the only file

transmitted multiple times in a month.• Every DMIS (Parent and Child) should have a SADR file transmitted each day

(even if the file is empty).• Logic for sites (especially overseas) is based on time zones and CHCS ETU

settings.

Includes:• All Navy DMIS IDs.

Excludes:• Not applicable.

*Auto-Populated by the NAVMISSA eDQ*

Page 32: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

4d : Historical SADR

Commander’s Statement – Data Transmission4

4 (d)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 33: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5a : DRG Accuracy

Commander’s Statement – Inpatient Coding Audit4

5 (a)

Methodology:• # of correct DRG codes / Total # of DRG codes

Includes:• 30 Inpatient dispositions per reporting month (or 100% if fewer than 30

dispositions).

Excludes:• Resource sharing and VA facilities report “N/A” for this metric.• MTFs without any inpatient services or external partnerships report “N/A” for the

entire 5-series (5a-5f).

Page 34: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5a : Historical DRG Accuracy

Commander’s Statement – Inpatient Coding Audit4

5 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 35: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5b : Inpatient Professional Services Rounds E&M Accuracy5c : Inpatient Professional Services Rounds ICD9 Accuracy5d : Inpatient Professional Services Rounds CPT Accuracy

Commander’s Statement – Inpatient Coding Audit4

5 (b-d)

Methodology:• 5b – # of Correct E&M codes / Total # of E&M codes documented and expected• 5c – # of Correct ICD9 codes / Total # of ICD9 codes documented and expected• 5d – # of Correct CPT codes / Total # of CPT codes documented and expected• Note: The denominator is not the # of IPS rounds audited.

Includes:• One calendar day of the attending professional services during each audited hospitalization

(from 5a) is randomly selected. For admissions greater than one day, odd registration numbers have the first day audited, even numbers the second day.

Excludes:• MTFs without any inpatient services or external partnerships report “N/A” for the

entire 5-series (5a-5f).

Page 36: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5b : Historical IPS Rounds E&M Accuracy5c : Historical IPS Rounds ICD9 Accuracy5d : Historical IPS Rounds CPT Accuracy

Commander’s Statement – Inpatient Coding Audit4

5 (b-d)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 37: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5e : DD Form 2569 Completed and Current5f : DD Form 2569 Correct in CHCS Patient Insurance Information

Module (PIIM)

Commander’s Statement – Inpatient Coding Audit4

5 (e, f)

Methodology:• 5e – # of Available DD 2569’s (completed and signed within the last 12 months) /

# of Non-Active Duty records audited• 5f – # of Records from the numerator of 5e correct in PIIM / Numerator from 5e• Notice that the basis for 5f is the number from 5e that are completed and signed

within the last 12 months.

Includes:• Non-Active Duty Records.• Overseas MTFs now report both 5e and 5f.

Excludes:• Active Duty records.

Page 38: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

5e : Historical DD Form 2569 Completed and Current5f : Historical DD Form 2569 Correct in CHCS Patient Insurance

Information Module (PIIM)

Commander’s Statement – Inpatient Coding Audit4

5 (e, f)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 39: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6a : Encounter Documentation Available

Commander’s Statement – Outpatient Coding Audit4

6 (a)

Methodology:• Consists of 30 randomly selected records.• If a record is documented as being checked out within the facility, it is counted as

available. If a record is documented as being checked out to a patient, it is not counted as available.

• 6a – # of Available records / 30

Includes:• Documentation from medical record, loose (hard copy) or electronic documentation

(AHLTA)

Excludes:• Not applicable

Page 40: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6a : Historical Encounter Documentation Availability

Commander’s Statement – Outpatient Coding Audit4

6 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 41: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6b : Outpatient Encounter E&M Accuracy6c : Outpatient Encounter ICD9 Accuracy6d : Outpatient Encounter CPT Accuracy

Commander’s Statement – Outpatient Coding Audit4

6 (b-d)

Methodology:• 6b – # of Correct E&M codes / Total # of E&M codes documented and expected• 6c – # of Correct ICD9 codes / Total # of ICD9 codes documented and expected• 6d – # of Correct CPT codes / Total # of CPT codes documented and expected• Note: The denominator is not the # of encounters audited.

Includes:• Not applicable.

Excludes:• Not applicable.

Page 42: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6b : Historical Outpatient Encounter E&M Accuracy6c : Historical Outpatient Encounter ICD9 Accuracy6d : Historical Outpatient Encounter CPT Accuracy

Commander’s Statement – Outpatient Coding Audit4

6 (b-d)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 43: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6e : DD Form 2569 Completed and Current6f : DD Form 2569 Correct in CHCS Patient Insurance Information

Module (PIIM)

Commander’s Statement – Outpatient Coding Audit4

6 (e, f)

Methodology:• 6e – # of Available DD 2569’s (completed and signed within the last 12 months) /

# of Non-Active Duty records audited• 6f – # of Records from the numerator of 6e correct in PIIM / Numerator from 6e• Notice that the basis for 6f is the number from 6e that are completed and signed

within the last 12 months.

Includes:• Non-Active Duty Records.• Overseas MTFs now report both 6e and 6f.

Excludes:• Active Duty records.

Page 44: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

6e : Historical DD Form 2569 Completed and Current6f : Historical DD Form 2569 Correct in CHCS Patient Insurance

Information Module (PIIM)

Commander’s Statement – Outpatient Coding Audit4

6 (e, f)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 45: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7a : APV Encounter Documentation Available

Commander’s Statement – APV Coding Audit4

7 (a)

Methodology:• Sample size must be a minimum of 30 APVs (or 100%, if less than 30 APVs were

completed).• If a record is documented as being checked out within the facility, it is counted as

available. If a record is documented as being checked out to a patient, it is not counted as available.

• 7a – # of Available records / 30 (or all APVs if less than 30)

Includes:• Documentation from medical record, loose (hard copy) or electronic documentation

(AHLTA)

Excludes:• Not applicable

Page 46: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7a : Historical APV Encounter Documentation Availability

Commander’s Statement – APV Coding Audit4

7 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 47: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7b : APV Encounter ICD9 Accuracy7c : APV Encounter CPT Accuracy

Commander’s Statement – APV Coding Audit4

7 (b, c)

Methodology:• Sample size must be a minimum of 30 APVs (or 100%, if less than 30 APVs were completed).

• 7b – # of Correct ICD9 codes / Total # of ICD9 codes documented and expected• 7c – # of Correct CPT codes / Total # of CPT codes documented and expected• Note: The denominator is not the # of encounters audited.

Includes:• Not applicable.

Excludes:• Not applicable.

Page 48: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7b : Historical APV Encounter ICD9 Accuracy7c : Historical APV Encounter CPT Accuracy

Commander’s Statement – APV Coding Audit4

7 (b, c)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 49: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7d : DD Form 2569 Completed and Current7e : DD Form 2569 Correct in CHCS Patient Insurance Information

Module (PIIM)

Commander’s Statement – APV Coding Audit4

7 (d, e)

Methodology:• 7d – # of Available DD 2569’s (completed and signed within the last 12 months) /

# of Non-Active Duty records audited• 7e – # of Records from the numerator of 6e correct in PIIM / Numerator from 7d• Notice that the basis for 7e is the number from 7d that are completed and signed

within the last 12 months.

Includes:• Non-Active Duty Records.• Overseas MTFs now report both 7d and 7e.

Excludes:• Active Duty records.

Page 50: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

7d : Historical DD Form 2569 Completed and Current7e : Historical DD Form 2569 Correct in CHCS Patient Insurance

Information Module (PIIM)

Commander’s Statement – APV Coding Audit4

7 (d, e)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 51: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8a : SADR to WWR Comparison

Commander’s Statement – Workload Comparison4

8 (a)

Methodology:• SADRs transmitted to NAVMISSA are used to calculate the numerator.• WWR workload category “Outpatient Visits” is used for the denominator.• The percentage should always be less than or equal to 100%. If the percentage is

greater than 100%, the number reported to TMA will be adjusted (i.e. 102% = 98%)• 8a - # of SADRs (Count) / WWR Outpatient Visits

Includes:• MEPRS Codes B*** and FBN*, Count SADRs only• APVs and Resource Sharing are included.

Excludes:• SADR Appointment Status CANCELLED, LWOBS, or ADMIN

*Auto-Populated by the NAVMISSA eDQ*

Page 52: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8a : Historical SADR to WWR Comparison

Commander’s Statement – Workload Comparison4

8 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 53: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8a : SADR Calculation Accuracy

Commander’s Statement – Workload Comparison4

8 (a)

NOLA transition impacted the file receipts at NAVMISSA, inflating the

“COUNT” and “NON-COUNT” calculation difference (blue data points

are adjusted to reflect actual data received).

NOLA transition impacted the file receipts at NAVMISSA, inflating the

“COUNT” and “NON-COUNT” calculation difference (blue data points

are adjusted to reflect actual data received).

NMSC and NAVMISSA Tiger Team On-Site

NMSC and NAVMISSA Tiger Team On-Site

BUMED 2% Goal

BUMED 2% Goal

Page 54: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8b : SIDR to WWR Comparison

Commander’s Statement – Workload Comparison4

8 (b)

Methodology:• SIDRs transmitted to NAVMISSA are used to calculate the numerator.• WWR workload category “Dispositions” is used for the denominator.• The percentage should always be less than or equal to 100%. If the percentage is

greater than 100%, the number reported to TMA will be adjusted (i.e. 102% = 98%)• 8b - # of SIDR Dispositions / WWR Dispositions

Includes:• “D” SIDRs

Excludes:• “E” or “F” SIDRs• Resource Sharing or VA workload

*Auto-Populated by the NAVMISSA eDQ*

Page 55: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8b : Historical SIDR to WWR Comparison

Commander’s Statement – Workload Comparison4

8 (b)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 56: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8c : EAS Visits to WWR Visits Comparison

Commander’s Statement – Workload Comparison4

8 (c)

Methodology:• EAS Visits are pulled from the EAS repository by NAVMISSA.• WWR workload category “Outpatient Visits” is used for the denominator.• The percentage should always be less than or equal to 100%. If the percentage is

greater than 100%, the number reported to TMA will be adjusted (i.e. 102% = 98%)

• 8c - # of EAS Visits / WWR Outpatient Visits• Note: If an MTF answers “No” for 4a, MTFs should use WAM data.

Includes:• MEPRS Codes B*** and FBN*• APVs and Resource Sharing are included.

Excludes:• Not Applicable

*Auto-Populated by the NAVMISSA eDQ*

Page 57: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8c : Historical EAS Visits to WWR Visits Comparison

Commander’s Statement – Workload Comparison4

8 (c)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 58: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8d : EAS Dispositions to WWR Dispositions

Commander’s Statement – Workload Comparison4

8 (d)

Methodology:• EAS Dispositions are pulled from the EAS repository by NAVMISSA.• WWR workload category “Dispositions” is used for the denominator.• The percentage should always be less than or equal to 100%. If the percentage is

greater than 100%, the number reported to TMA will be adjusted (i.e. 102% = 98%)

• 8d - # of EAS Dispositions / WWR Dispositions• Note: If an MTF answers “No” for 4a, MTFs should use WAM data.

Includes:• EAS Dispositions and WWR Dispositions should also match the “D” + “E” SIDR

total used in 2c.

Excludes:• Resource Sharing and VA workload

*Auto-Populated by the NAVMISSA eDQ*

Page 59: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8d : Historical EAS Dispositions to WWR Dispositions

Commander’s Statement – Workload Comparison4

8 (d)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 60: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8e : Inpatient Professional Services Rounds to WWR Bed Days + Dispositions Comparison

Commander’s Statement – Workload Comparison4

8 (e)

Methodology:• IPS Rounds are obtained from the MTF SADR Transmissions.• WWR workload categories “Dispositions” and “Occupied Bed Days” are used for

the denominator.• 8e - # of IPS Rounds / WWR OBDs + Dispositions

Includes:• All A*** MEPRS Codes

Excludes:• Any E*** MEPRS Codes

*Auto-Populated by the NAVMISSA eDQ*

Page 61: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8e : Historical IPS Rounds to WWR Bed Days + Dispositions Comparison

Commander’s Statement – Workload Comparison4

8 (e)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 62: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

8e : IPS Rounds Calculation Accuracy

Commander’s Statement – Workload Comparison4

8 (e)

NOLA transition impacted the file receipts at NAVMISSA (blue data

points are adjusted to reflect actual data received).

NOLA transition impacted the file receipts at NAVMISSA (blue data

points are adjusted to reflect actual data received).

NMSC and NAVMISSA Tiger Team On-Site

NMSC and NAVMISSA Tiger Team On-Site

BUMED 2% Goal

BUMED 2% Goal

Page 63: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

9a : AHLTA Utilization

Commander’s Statement – AHLTA Utilization4

9 (a)

Methodology:• The “Source System” field in MTF SADR Transmissions is used to determine

whether the encounter was created in AHLTA or another system. This is also the same field used in M2.

• This metric only needs to be above 80% to be green, since AHLTA is not designed for all clinics.

• 9a - # of AHLTA Encounters / Total # of Encounters

Includes:• MEPRS Codes B*** and FBN*• ER, Optometry and other MEPRS Clinics are all included (BUMED 6040)

Excludes:• Updates (eliminates the issue of CHCS or ADM updates changing the source

system)

*Auto-Populated by the NAVMISSA eDQ*

Page 64: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

9a : Historical AHLTA Utilization

Commander’s Statement – AHLTA Utilization4

9 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 65: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

9a : AHLTA Utilization Calculation Accuracy

Commander’s Statement – AHLTA Utilization4

9 (a)

NMSC and NAVMISSA Tiger Team On-Site

NMSC and NAVMISSA Tiger Team On-Site

One Navy MTF utilized the incorrect methodology to report their AHLTA

utilization (i.e. AHLTA Utilization cannot be greater than 100%, etc.).

One Navy MTF utilized the incorrect methodology to report their AHLTA

utilization (i.e. AHLTA Utilization cannot be greater than 100%, etc.).

Page 66: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

10a : Potential Duplicate Patient Records

Commander’s Statement – Duplicate Patients4

10 (a)

Methodology:• A standard CHCS report is provided to Host sites and is used to provide the raw

data for this metric.• Only sites that are a CHCS Host report this metric (others report “N/A”).• This metric is not “graded” (red/yellow/green) on the TMA report.• 10a - # of Potential Duplicate Encounters

Includes:• CHCS Host Sites

Excludes:• Sites that are not CHCS Hosts

Page 67: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

10a : Historical Potential Duplicate Patient Records

Commander’s Statement – Duplicate Patients4

10 (a)

*Note that the vertical axis on the historical charts is adjusted to better display trends*

Page 68: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout

11a : Commander’s Signature

Commander’s Statement – Commander’s Signature4

11 (a)

Methodology:• The Commander or Officer in Charge signs the Commander’s Statement indicating

that it has been reviewed and acknowledged.• This cannot be signed “By Direction”. If the CO/OIC is away, the “Acting” may sign.• This metric should always be “Yes”.

Includes:• Not Applicable.

Excludes:• Not Applicable.

Page 69: Navy Data Quality Management Control Program (DQMCP) DQMCP Conference Navy Breakout