Introduction
A urology practice can perform a perfect cystoscopy, document it thoroughly, and still lose revenue or draw payer scrutiny. That risk usually comes from a mismatch between what happened and what got coded, billed, or supported in the chart.
Medicare's claims-review data shows how common this mismatch is. In a sample of established-patient office visits, documentation supported a lower E/M level than billed in 120 claims and a higher level than billed in 7 others, according to CMS's FY2025 data. Both directions cost practices money.
This guide covers coding quality audits for independent urology practices, both professional-fee and procedure-related coding. You'll learn what audits evaluate, how audit types differ, and a workable process for running one. The aim is turning findings into process change, not a report that sits in a folder.
Key Takeaways
- A coding audit compares documentation, codes, modifiers, and payer rules to find compliance and revenue-cycle problems.
- Look for overcoding and undercoding, including missed billable services and unsupported code selection.
- Scope the audit to your practice's actual mix of providers, payers, procedures, and known risk areas.
- Findings only matter if followed by education, correction, and a re-audit.
What Is a Urology Medical Coding Quality Audit—and Why Does It Matter?
A coding quality audit is a structured review of selected patient encounters and claims. It asks one core question: does the medical record support the diagnosis codes, procedure codes, E/M level, modifiers, and units that were actually billed?
Coders can only report what the documentation supports. If a provider performs a service but doesn't document it clearly, the coder has no basis to bill it, and the practice loses revenue it earned. The reverse is just as damaging: a code that outpaces the note creates compliance exposure.
What a Good Audit Accomplishes
A well-run audit typically aims to:
- Improve coding accuracy across providers and encounter types
- Identify compliance exposure before a payer or regulator finds it
- Reduce denials that stem from preventable errors
- Capture services that were performed but never billed
- Generate targeted education instead of generic training
Common Findings in Urology Audits
Audits of urology encounters tend to surface a recognizable set of issues:
- Upcoding or undercoding of E/M visits
- Unbundling services that should be reported together
- Outdated or deleted codes still in use
- Diagnoses that don't match documented findings
- Missing medical-necessity documentation
- Incorrect or missing modifiers
- Services documented in the chart but never submitted on a claim
Urology carries its own documentation patterns. Office visits, in-office procedures, surgical cases, diagnostic testing, and postoperative care each follow different coding rules. A generalist audit that doesn't account for cystoscopy workflows, stone-treatment units, or global-period rules will miss the risks that actually apply to a urology practice.
Types of Medical Coding Quality Audits
There's no single, universally agreed-upon "three-type" system for coding audits. Different organizations describe audit categories differently, and the categories overlap. What matters more is choosing a framework that fits an independent practice's size and risk profile.
Scope-Based Categories
Two scope-based categories cover most practical needs:
- Broad or comprehensive audit – Reviews a representative sample across providers, payers, services, and code families. Useful as a baseline to understand overall coding health before narrowing focus.
- Focused or targeted audit – Examines one defined risk area: a specific urology procedure, an E/M pattern, a modifier, a payer policy, a denial trend, a single provider, or a recent coding change.
Timing-Based Categories
Audits are also sometimes grouped by when they happen relative to claim submission:
- Prospective (pre-bill) review – Catches issues before claims go out the door.
- Concurrent review – Evaluates documentation and coding while the workflow is still active.
- Retrospective review – Examines completed encounters and paid, denied, or rejected claims to find patterns after the fact.
Each timing approach has tradeoffs. Pre-bill review prevents errors but slows billing. Concurrent review keeps feedback close to the encounter but needs real-time staffing. Retrospective review is efficient but only catches problems after they've already affected cash flow.
Specialty-Relevant Audit Types
Within these broader categories, a few urology-relevant variations are worth naming:
- Documentation and clinical validation reviews test whether the record actually supports the reported diagnosis and service.
- Denial and revenue-integrity reviews trace payer rejections, underpayments, and missed charges back to their coding or workflow cause.
- Provider onboarding or education audits check whether new physicians, advanced practice providers, coders, or billing staff are applying current rules correctly.
An internal review works well for routine monitoring. An external review adds value when:
- Objectivity matters more than speed
- Specialty-specific expertise is thin in-house
- Staff workload is already stretched
- Leadership wants to validate the team's assumptions about coding accuracy
How to Conduct a Urology Medical Coding Quality Audit
Define Scope Before Selecting Records
Start by answering three questions:
- Is this audit compliance-focused, revenue-cycle-focused, educational, or investigating a known issue?
- Which providers, locations, payers, dates of service, and procedure families are included?
- Which coding rules, payer policies, and authoritative sources will serve as the review standard?
Build a Risk-Based Sample
OIG's 2023 guidance and its earlier physician-practice guidance both support combining random selection with risk-based targeting. There's no fixed formula for sample size, but a practical approach includes:
- Random records across the practice's normal volume
- Targeted records from high-volume services
- Claims tied to unusual code combinations or frequent denials
- Encounters involving new providers or newly adopted procedures
- Follow-up samples tied to prior audit findings
Review Each Encounter Consistently
Use the same checklist for every chart:
- Confirm patient, provider, date of service, place of service, and payer details.
- Compare the note against diagnosis codes, CPT/HCPCS codes, E/M level, modifiers, units, and billed charges.
- Check medical necessity, procedure specifics, laterality, complications, and global-period status.
- Verify the coding reflects the full service, without adding unsupported diagnoses or dropping supported ones.
Categorize and Report Findings
Group findings into clear categories:
- Documentation gaps
- Coding errors
- Charge-entry mistakes
- Payer-policy issues
- Training gaps
Distinguish a one-off mistake from a repeated pattern. Prioritize by compliance risk and financial effect, not just error count.
A useful report covers scope, methodology, findings with examples, root causes, and recommended corrective actions. Note strengths as well as gaps.
Set a Repeatable Cadence
A baseline comprehensive review followed by periodic targeted or random reviews works for most practices. Schedule an interim review outside the regular cadence when you see:
- A spike in denials
- New payer scrutiny
- Provider turnover
- A newly added procedure line
Urology-Specific Coding Risks to Include in the Audit Scope
Certain risk areas show up again and again in urology coding audits:
- E/M modifiers 24 and 25. Modifier 25 needs a significant, separately identifiable same-day E/M with documentation that separates it from the procedure. Modifier 24 needs a clearly unrelated postoperative service, not routine recovery (AUA coding tips).
- Procedural and surgical coding. Documentation must support technique, anatomy, laterality, findings, and complications. A missing RT or LT modifier on a kidney or ureteral procedure is an avoidable rejection an audit should catch quickly.
- Bundling and modifier 59. Modifier 59 and its X{EPSU} subset codes identify distinct procedural services and drive many unbundling denials. Confirm documentation supports a truly separate service before applying them.
- Payer-specific edits and prior authorization. Most interventional urology procedures need approval from commercial payers and many Medicare Advantage plans. Confirm authorization was obtained and matches the service billed.
- Medical-necessity documentation. Urodynamics and similar diagnostic tests often carry local coverage requirements on diagnosis detail and clinical findings needed to support the claim.
- Diagnosis-documentation gaps. Watch for symptom-versus-confirmed-diagnosis confusion, missing laterality or acuity, and diagnoses that don't clearly link to the billed procedure.
Codes, modifiers, and payer edits change regularly. Any specific code example should be verified against current CPT, ICD-10-CM, HCPCS, CMS NCCI edits, and the relevant payer policy before it's used to change a workflow.
Turning Audit Findings Into Lasting Improvement
An audit report that nobody acts on doesn't improve anything. Each material finding needs a corrective-action plan with:
- An assigned owner
- A due date
- The affected workflow
- A way to confirm the fix actually happened
Make Education Specific
Generic compliance training rarely changes behavior. Education works better when it targets the actual error pattern, such as:
- Documentation specificity for a particular procedure type
- Modifier selection logic for recurring denial codes
- Payer-specific edit requirements
- E/M level selection under current MDM or time-based guidance
Re-Audit and Monitor
Run a follow-up audit after remediation, using comparable records, and compare results against the original findings. Beyond the formal re-audit, keep an eye on leading indicators:
- Recurring denial reasons
- Volume of corrected claims
- Provider query volume
- Coding turnaround time
A single denied surgical claim can outweigh dozens of small ones in dollar terms, so track denials by dollars, not just by count.
Audit findings often point to questions bigger than coding itself: capacity, staffing, or where charge capture is breaking down.
GrowUrology publishes free, ungated tools and plain-English explainers that let practices model those operational and financial questions using their own numbers. The calculators run in the browser and don't require patient information, so practices can test scenarios like capacity or procedure profitability without touching protected health data.
Conclusion
A urology coding quality audit works as a continuous control, not a one-time inspection. Define the risk, review a representative sample, document what you find, fix the process behind it, and check again later.
If a full audit program isn't feasible yet, start smaller: pick one high-risk area, such as modifier 25 or laterality on urologic procedures, run a focused review, and expand the scope as the findings guide you.
Coding rules, payer policies, and regulatory guidance change often. Confirm current requirements with authoritative sources and qualified compliance professionals before changing any billing practice.
Frequently Asked Questions
What are coding quality audits?
They're structured reviews of documentation, codes, modifiers, claims, and payer requirements. The goal is to identify accuracy gaps, compliance exposure, documentation weaknesses, and revenue-cycle problems before they compound.
What are the three types of quality audits?
By timing, the three types are prospective (before submission), concurrent (during the encounter cycle), and retrospective (after payment). Practices also plan audits by scope as comprehensive or focused reviews.
How often should a urology practice audit its coding?
Start with a baseline comprehensive review, then run periodic targeted or random reviews based on risk and recent changes. A spike in denials or a new procedure line is a good reason to audit sooner than scheduled.
What's the difference between an internal and external coding audit?
An internal audit uses existing staff and is faster to schedule. An external audit adds objectivity, specialty-specific expertise, and a way to validate assumptions your own team may not catch.
Does a coding audit assume fraud?
No. Most findings are documentation gaps, training gaps, or workflow errors, not intentional misconduct. Treating every error as fraud without proper evidence undermines the audit's value as an improvement tool.
