Coding & Billing Audit Sample Plan and Exceptions Tracker

Purpose

This audit plan helps revenue teams and clinicians run focused, defensible coding and billing audits designed to identify coding errors, denial drivers, and documentation gaps. It provides a repeatable sampling approach, a sample-size method you can use or automate, a comprehensive set of audit fields, a denial-cause taxonomy you can adapt, and an exceptions tracker template to assign owners and monitor remediation.

When to Use

• Routine revenue integrity reviews (monthly/quarterly)
• Targeted reviews after a spike in denials or payer audit findings
• Pre-billing spot checks and retrospective record reviews
• Validation of coder training and documentation improvement initiatives

Scope

Define the population before sampling: payer(s), service types (inpatient/outpatient/ED), date range, practitioner(s), facility/location, code ranges (CPT/HCPCS/ICD-10), and whether to include suspected high-risk claims (e.g., high-dollar, DRG outliers, or frequent denials).

Sampling Methodology

Choose the sampling approach that matches your hunger and risk profile. Common options:

• Simple random sampling — good for unbiased estimates across a homogeneous population.
• Stratified sampling — useful when you want representative samples across payers, service lines, or high-risk vs low-risk strata.
• Systematic sampling — efficient when claims are ordered and you want broad coverage (e.g., every 10th claim).
• Targeted sampling — focus on suspected problem areas (new coders, high-denial CPTs, certain payers).

Sample-size formula (proportion estimates)

To estimate how many records to review for a proportion (e.g., percent of claims with coding errors):

n0 = (Z^2 * p * (1 - p)) / E^2

Then adjust for finite population N:

n = n0 / (1 + (n0 - 1) / N)

Where:

• Z = z-score for desired confidence (1.96 for 95% confidence)
• p = expected error proportion (use 0.5 when unsure to be conservative)
• E = desired margin of error (e.g., 0.05 for ±5%)
• N = total population size (total claims in scope)

Example: N = 1,000 claims; assume p = 0.5; E = 0.05; Z = 1.96.

n0 ≈ 384 → adjusted n ≈ 278 records to review.

Notes: For targeted audits or when you prefer practical smaller samples, use a conservative p (0.5) and clearly document the choice and its implications for precision.

Sample-Size Calculator (Suggested Fields for Automation)

• Population size (N)
• Confidence level (e.g., 90%, 95%) → Z value
• Expected error rate (p)
• Margin of error (E)
• Result: suggested sample size (n) and brief explanation

Suggested Audit Fields (Each record reviewed should capture these)

1. Audit ID
2. Claim/Encounter ID
3. Patient MRN (masked in reporting if required)
4. Service Date
5. Provider/Ordering Clinician
6. Facility/Department
7. Payer
8. CPT/HCPCS codes billed
9. ICD-10 diagnosis codes
10. Place of service
11. Initial claim outcome (paid/denied/pended)
12. Denial code (if denied)
13. Auditor's finding (coded correctly / coding error / documentation gap / billing issue / eligibility / prior auth / modifier error / bundling issue)
14. Severity (Minor/Moderate/Critical) — impact on payment or compliance
15. Financial impact estimate (dollar amount of under/overpayment or denial)
16. Root cause category
17. Remediation required (yes/no)
18. Assigned owner for remediation
19. Target remediation date
20. Closure date and verifier
21. Notes and link to supporting documentation

Denial-Cause Taxonomy (adaptable)

• Documentation Insufficient (missing HPI, exam, decision-making)
• Coding Error (incorrect CPT/ICD, wrong code selection)
• Modifier Error (missing or incorrect modifier)
• Bundling / Unbundling
• Eligibility / Coverage
• Prior Authorization Missing
• Duplicate Billing
• Medical Necessity
• Timely Filing
• Payer Policy / Fee Schedule Discrepancy
• System / Transcription Error

Exceptions Tracker Template

Use this tracker to record each exception found, assign responsibility, track remediation steps, and measure closure timeliness. Below is a recommended column set you can implement as a spreadsheet or convert into an interactive form or issue tracker.

• Exception ID
• Audit ID / Claim ID
• Finding summary
• Denial code / payer response
• Root cause (taxonomy code)
• Severity / financial impact
• Assigned owner (name and role)
• Action required (education / documentation correction / coding correction / appeal / process change)
• Target remediation date
• Status (Open / In progress / Remediated / Closed / Escalated)
• Closure date
• Verifier / QA reviewer
• Recurrence flag (yes/no) and notes

Recommended Workflow

1. Define scope and population, choose sampling approach, and compute sample size.
2. Randomize or select sample; lock the sample list for audit integrity.
3. Perform reviews using the audit fields checklist and record structured findings.
4. Create exceptions entries for findings that require action; assign owners and target dates.
5. Track remediation; require closure evidence (e.g., corrected claim, education record, appeal outcome).
6. Aggregate results, compute KPIs, and present trends by payer, provider, code, and root cause.
7. Run targeted follow-up audits where recurrence or systemic issues are identified.

Suggested KPIs and Reports

• Audit error rate (errors / reviewed records)
• Denial rate by cause and payer
• Average time-to-remediation
• % of exceptions closed on or before target date
• Financial impact recovered or prevented
• Recurrence rate for previously remediated issues

Common Pitfalls and How to Avoid Them

• Undefined population or inconsistent inclusion criteria → always document scope.
• Small unrepresentative samples → use stratification when necessary and document assumptions.
• Lack of follow-through on exceptions → assign owners and enforce verification before closure.
• Treating audits as isolated events → embed them into a continuous improvement loop with follow-ups.

Practical Notes for Implementation

Keep audit documentation auditable: timestamp reviews, preserve copies of reviewed charts and payer responses, and record who performed the review. Mask patient identifiers in shared reports as required by privacy policy.

Capability Opportunities (recommended)

This audit plan is ready to be enhanced by platform capabilities:

• Build an interactive sample-size calculator and render it as a small form so reviewers get an immediate sample n (use the platform's interactive form rendering capability).
• Create the exceptions tracker as an interactive submission form that stores entries in JSON so remediation history, ownership, and closure evidence are preserved and reportable.
• Package the audit templates, calculator, taxonomy, and tracker as a reusable toolkit that other teams or sites can copy and tailor to their own hungers and payer mixes.

Next Steps

1. Decide whether you want a manual spreadsheet-based approach or an interactive tracker that stores structured submissions.
2. If interactive, build these forms: Sample-Size Calculator (small form), Audit Record Entry (checklist-style form), Exceptions Tracker (issue / remediation form).
3. Run an initial pilot with a focused sample (e.g., one payer or service line) and refine taxonomy, fields, and owner assignments based on feedback.

Note: Preserve the existing taxonomy and templates as starting points — adapt names, severity definitions, and remediation workflows to match your organization's policies and compliance needs.