Study guide

18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use

AHIMA Certified Documentation Integrity Practitioner CDIP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Authoritative Coding Resources & Conventions

1.1 Official Coding Resources: Scope, Authority & Research 1.2 General Coding Conventions, Punctuation & Instructional Notes 1.3 Chapter-Specific and Setting-Specific Coding Guidelines

2 Chapter 2: Principal & Secondary Diagnosis Determination

2.1 UHDDS Definitions & Principal Diagnosis Selection 2.2 Two or More Diagnoses Equally Meeting Criteria 2.3 Secondary Diagnosis Reporting Standards & POA Status

3 Chapter 3: Procedure Coding & Sequencing Standards

3.1 ICD-10-PCS Root Operations & Inpatient Procedure Coding 3.2 Principal Procedure Selection & Surgical Sequencing 3.3 Applying Official References to Ambiguous Records

4 Chapter 4: Inpatient Prospective Payment & DRG Grouping

4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels 4.2 Working vs. Final DRG Assignment & Optimization vs. Maximization 4.3 CDI-Coding Reconciliation & Annual Regulatory Updates

5 Chapter 5: Enterprise CDI Promotion & Program Value

5.1 Articulating CDI Value to C-Suite & Hospital Leadership 5.2 Organizational Models, Inpatient/Outpatient Scope & Staffing 5.3 Cross-Functional Collaboration: HIM, Quality & Case Management

6 Chapter 6: Cross-Functional Alignment & Improvement Projects

6.1 Partnering with Nursing, Pharmacy & Allied Health Professionals 6.2 Documentation Improvement Project Identification & Scoping 6.3 Executing, Piloting & Measuring CDI Project Outcomes

7 Chapter 7: Physician Champion Engagement & Clinical Advocacy

7.1 Selection, Role & Credibility of the CDI Physician Champion 7.2 Peer-to-Peer Engagement, Coaching & Overcoming Resistance 7.3 Developing Standard CDI Operational Policies & Procedures

8 Chapter 8: Compliant Policy Architecture & Query Governance

8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction 8.2 Medical Record Integration of Provider Query Responses 8.3 Policies for Electronic, Paper, and Verbal Query Communications

9 Chapter 9: Query Escalation & Professional Communication

9.1 Chain of Command & Protocols for Unanswered Queries 9.2 Conflict Resolution & Professional Feedback Mechanisms 9.3 Assessing Stakeholder Learning Needs & Specialty Curricula

10 Chapter 10: Educational Delivery & Broader Healthcare Impacts

10.1 Delivery Methods: Microlearning, Case Studies & Grand Rounds 10.2 Documentation Impacts on Clinical Research & Epidemiology 10.3 Documentation Impacts on Case Management, LOS & Reimbursement

11 Chapter 11: Clinical Record Synthesis & Encounter Trajectory

11.1 Synthesizing Provider Notes, Consults & Progress Trajectory 11.2 Interpreting Diagnostic Imaging, Pathology & Labs 11.3 Resolving Conflicting, Ambiguous & Copy-Forward Entries

12 Chapter 12: Advanced Clinical Concepts & Review Prioritization

12.1 Pharmacotherapy, Clinical Trajectories & Disease Correlations 12.2 Inpatient Review Prioritization: High-Risk & High-Volume 12.3 Payer Prioritization, Length of Stay & Re-Review Cadence

13 Chapter 13: Clinical Indicator Mapping & Gap Recognition

13.1 Systematic Identification of Documentation Gaps 13.2 Sepsis Definitions, SEP-1, and Coding 13.3 AKI Criteria, Tubular Injury, and CKD Staging

14 Chapter 14: Diagnostic Precision in High-Impact Conditions

14.1 Respiratory Failure: Acuity, Evidence, and Sequencing 14.2 Heart Failure Phenotype, Acuity, and Hypertensive Combinations 14.3 Encephalopathy, Delirium, and Acute Cognitive Change

15 Chapter 15: Clinical Validation & Complication Discrepancies

15.1 Malnutrition Assessment, Severity, and Provider Documentation 15.2 Principles of a Compliant, Nonleading Query 15.3 Open-Ended, Multiple-Choice, and Yes/No Queries

16 Chapter 16: Query Mechanics & Direct Provider Collaboration

16.1 Electronic Query Systems, Templates, and Technology Oversight 16.2 Collaborating With the Appropriate Query Recipient 16.3 Capturing and Clarifying Query Responses

17 Chapter 17: Quality Indicators & Post-Discharge Clarification

17.1 Present on Admission Clarification and Selected HAC Rules 17.2 Clarifying Acuity, Cause, Site and Severity 17.3 Post-Discharge Query Opportunities and Limits 17.4 Managing Post-Discharge Query Workflows

18 Chapter 18: CDI Operational Dashboards & Quality Auditing

18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use 18.2 Internal CDI Quality Audits and Reviewer Calibration 18.3 Query Trends: Understanding the Process and Provider Experience

19 Chapter 19: Benchmarking, Productivity & Data-Driven Workflow

19.1 Provider Documentation Benchmarking 19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay 19.3 Evaluating CDI Professional Performance 19.4 Using Data to Design CDI Workflow and Staffing

20 Chapter 20: Ethical CDI Standards & Regulatory Frameworks

20.1 Applying AHIMA Ethics to CDI Decisions 20.2 Responding to Financial Pressure and Upcoding Risks 20.3 Maintaining Competence and Professional Integrity

21 Chapter 21: Regulatory Compliance & Enforcement Landscapes

21.1 False Claims, Overpayments and Referral Laws 21.2 Regulatory Agencies, Review Contractors and Appeals 21.3 EHR Templates, Copied Text and Record Integrity

22 Chapter 22: Technology Risks & Second-Level Review Protocols

22.1 CAC, NLP and AI: Context, Oversight and Performance 22.2 Selecting Cases for Second-Level Review 22.3 Conducting and Closing a Second-Level Review

23 Chapter 23: Clinical Validation Queries & Risk Mitigation

23.1 Clinical Validation and Coding Clarification 23.2 Clinical Validation Queries and Denial Evidence 23.3 Detecting Leading, Biased and Unsupported Queries

24 Chapter 24: Noncompliant Query Remediation & Query Lifecycle Management

24.1 Query Remediation and Corrective Action 24.2 Query Timeframes, Aging and Measurement 24.3 Query Records, Retention and Evidence Preservation

18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use

Key Takeaways Explain This Topic AI

Define population, unit, numerator, denominator, timing, exclusions and ownership before comparing dashboard rates; eligible-cohort coverage differs from assigned-review completion.

Record query rate counts distinct reviewed records with one or more queries; query density counts queries and can differ when one encounter receives several questions.

Response and agreement measures require matched query cohorts, explicit outcome definitions and observation windows; agreement per query sent differs from agreement among answers.

AHIMA’s KPI brief sets no universal industry query or agreement rate; unusual results are investigation signals, not proof of poor practice or clinical excellence.

Use local aging and escalation rules, verify actual account-hold reasons and distinguish open queries from DNFB; neither automation nor a particular response rate guarantees billing outcomes.

Last updated: October 2026

Departmental Metrics: Definitions, Calculations and Dashboard Use

A dashboard should connect a measured result to a decision: which records need review, which queries need follow-up, or which process needs investigation. A percentage without a defined population, counting unit and time window can mislead even when its arithmetic is correct.

The AHIMA 2022 CDI KPI practice brief recommends explicit definitions in departmental policy. It describes organizational variation and states that there is no industry standard for query or agreement rates. The ACDIS September 2026 query-practice Q&A likewise discusses differing survey results and local expectations. A respondent's practice or survey category is useful context, not a mandatory national target.

Write the metric dictionary before the dashboard

For each measure, define the numerator, denominator, unit, eligible population, time period, source system, exclusions, duplicate handling and responsible owner. Also state when the data become mature enough to compare. Keep the same definitions across periods or identify the change clearly.

An admission-cohort report follows the admissions selected for that cohort; it is not interchangeable with a report of all reviews performed that month. An encounter reviewed three times remains one encounter for a unique-record coverage measure but creates three review activities. Similarly, two queries on one encounter are two queries and one queried record.

Coverage and assigned-review completion

For an explicitly defined eligible admission cohort, a useful coverage measure is:

Coverage = Distinct eligible encounters receiving an initial review Eligible encounters in the cohort × 100 % \text{Coverage} = \frac{\text{Distinct eligible encounters receiving an initial review}}{\text{Eligible encounters in the cohort}} \times 100\% Coverage = Eligible encounters in the cohort Distinct eligible encounters receiving an initial review ​ × 100%

By contrast, AHIMA's review-rate example uses records reviewed divided by records assigned for review . That measures completion of assigned work. If a program assigns only a subset of eligible admissions, a high assignment-completion rate can coexist with lower population coverage. Show both if both questions matter. Do not silently replace the eligible population with the assigned workqueue.

Define what counts as a completed initial review and the local timing expectation. Short stays, staffing, education work, clinical complexity, scope and technology affect capacity. A bed-to-FTE ratio or coverage goal must be justified for that program; it is not established by declaring a universal 18–22-bed staffing standard or an 80–90% coverage requirement.

Re-review: distinguish activity from completion

Subsequent review helps assess evolving documentation and new results. Define which encounters or review opportunities are due under the local clinical workflow. The follow-up schedule can consider clinical change, unresolved issues and pending results rather than a national ICU-versus-floor clock.

A local due-review completion measure could be completed eligible follow-up opportunities divided by all follow-up opportunities due in the period. For example, 72 completed out of 90 due opportunities is 80% . Count opportunities consistently: if two reviews are due for the same encounter, both numerator and denominator must use opportunities.

Total follow-up reviews divided by distinct patients instead measures activity intensity and can exceed 100%. It does not show the percentage of required reviews completed unless each patient represents exactly one due review. Neither a particular follow-up percentage nor high initial coverage proves that complications were found or missed; assess documentation and sampled review quality.

Query rate: records and query counts answer different questions

AHIMA's recommended record-based approach is:

Record query rate = Distinct reviewed records with one or more queries Distinct records reviewed × 100 % \text{Record query rate} = \frac{\text{Distinct reviewed records with one or more queries}}{\text{Distinct records reviewed}} \times 100\% Record query rate = Distinct records reviewed Distinct reviewed records with one or more queries ​ × 100%

The brief also recognizes calculations based on actual query counts. If that convention is used, label it clearly. Queries per reviewed record , sometimes expressed per 100 reviewed records, measures query density rather than the proportion of encounters queried. Several questions on one encounter increase density without increasing the number of queried encounters.

Hypothetical example: A cohort contains 500 eligible admissions. CDI reviews 425 distinct encounters. Eighty-five of those encounters have at least one query, with 100 total queries sent.

  • Measure Calculation Result
  • Cohort coverage 425 ÷ 500 × 100 85.0%
  • Record query rate 85 ÷ 425 × 100 20.0%
  • Query density 100 ÷ 425 × 100 23.5 queries per 100 reviewed records
  • Queried share of all eligible admissions 85 ÷ 500 × 100 17.0%; a different denominator and question

Do not increase query volume to reach a target. A low rate may reflect strong documentation, narrow review scope or missed opportunities; a high rate may reflect a broader scope, complex cases or unnecessary queries. Examine case mix, query purpose and sampled records before selecting an explanation. Separate concurrent, retrospective and automated/manual queries when that distinction helps interpretation.

Response and agreement require matched cohorts

Response rate uses queries with a response meeting the department's definition divided by queries sent in the same defined cohort. State the response deadline and observation cutoff. Counting every response received this month over every query sent this month can mix older answers with new questions and produce a misleading result.

Define how routing errors, withdrawn queries, “unable to determine” and other dispositions are counted. A new query still within its response window should not be treated as a failed timely response without explaining the reporting method. Show pending work separately when a cohort has not yet matured.

Agreement rate also needs an explicit outcome definition. AHIMA's published equation uses queries meeting the defined agreed outcome divided by queries sent . Some local reports calculate agreement among answered queries instead; those two results are not interchangeable. State whether the unit is a query or a health record, and how an alternative diagnosis, greater specificity, inability to determine or a clinical-validation response is classified.

For a mature hypothetical cohort with 110 queries sent, 108 qualifying responses and 107 locally defined agreed outcomes:

Response rate: 108 ÷ 110 × 100 = 98.2% .

Agreement using queries sent: 107 ÷ 110 × 100 = 97.3% .

Agreement among responses: 107 ÷ 108 × 100 = 99.1% .

These are three different measurements from the same cohort. A provider's supported alternative answer can be a successful clarification even when it does not meet a particular administrative “agreement” definition. The 2026 query brief protects independent provider judgment; it does not require agreement with a suggested diagnosis.

An unusually high agreement trend can justify checking the query content, outcome mapping or provider workflow. AHIMA identifies that possibility, while also noting that 100% can occur and setting no universal agreement standard. The percentage alone establishes neither leading queries nor exceptional clinical quality. A low response rate likewise warrants investigation of access, routing, coverage, workload and definition problems before attributing disengagement or imposing a diagnosis-focused remedy.

Build operational and management views

View Useful fields Decision it supports

Review workqueue Encounter identifier, eligibility, last review, due reason, assigned reviewer Allocate work without counting repeated reviews as new coverage.

Open queries Recipient, delivery time, policy deadline, current status and coverage route Follow up on the actual question and identify workflow barriers.

Discharged accounts Billing status, verified hold reason, query owner and other open account work Determine whether a query is actually preventing final billing.

Trend and quality report Defined rates, denominators, service lines, query types and sampled quality findings Choose education or process changes and assess their effects over time.

Aging buckets should reflect local policy and distinguish calendar from business time. Under/over 48 or 72 hours are possible design choices, not national regulatory thresholds. Automation and NLP can assist prioritization, but are not mandatory dashboard architecture and do not replace clinical review or compliant query governance.

Use the actual account status when linking query activity to finance. Under HFMA MAP definitions , DNFB differs from final-billed-not-submitted status; an open post-bill query is not automatically DNFB. A dashboard can reveal a suspected bottleneck, but a notification feature does not guarantee a response, claim release or reduced receivables. Validate the account-level causes, take a specific action and monitor both timeliness and documentation quality.