ICD code R30.0 – Dysuria (painful urination)

Key takeaways

R30.0 is the billable ICD-10-CM code for dysuria, used only while no underlying cause such as UTI or cystitis is confirmed.

In outpatient care, report R30.0 until a definitive diagnosis is documented, then switch to the confirmed condition’s code.

Strangury is indexed to R30.0. Its sibling R30.1 codes vesical tenesmus, a painful urge to void that keeps going after the bladder is empty.

The most common denial comes from reporting R30.0 next to a confirmed diagnosis in the same note, because the confirmed code replaces the symptom code.

Structured encounter notes in Pabau, the practice management and EHR platform we build, capture the symptom detail and pending tests that support R30.0 at audit.

ICD-10 code R30.0: Definition and billable status

ICD-10 code R30.0 is a billable, specific ICD-10-CM diagnosis code for dysuria, the medical term for painful urination. It also covers strangury, the slow and painful passage of urine.

The code has been valid since ICD-10-CM took effect on October 1, 2015, and it carries over unchanged into the FY2026 and FY2027 code sets. Its parent, R30, is a non-billable category header.

The CDC/NCHS ICD-10-CM web tool lists R30.0 under the R30 category alongside R30.1 (vesical tenesmus) and R30.9 (painful micturition, unspecified). R30.0 and R30.9 are distinct codes. R30.0 is the better choice whenever the documented symptom is specifically dysuria.

R30.0 code description and clinical meaning

Dysuria is the medical term for pain, burning, stinging, or discomfort during or immediately after urination. Clinically, it encompasses several related patient-reported presentations.

• Painful urination NOS: Pain without a specified location or mechanism, documented by the provider as a presenting complaint
• Burning sensation on urination: The most common patient-reported descriptor; maps directly to R30.0
• Stinging on micturition: A sharper quality of pain during urine passage
• Pain on micturition: A broader descriptor encompassing suprapubic or urethral discomfort triggered by voiding
• Strangury: Slow, drop-by-drop passage of urine with painful spasm, which the ICD-10-CM index also sends to R30.0

R30.0 codes the symptom itself, not an underlying disease. The classification reflects that the provider has documented the complaint but has not yet established a confirmed etiology. Once a definitive diagnosis is made, that condition’s code replaces R30.0 entirely.

Acute vs chronic presentation

ICD-10-CM R30.0 does not distinguish between acute and chronic onset. Both map to the same code when the underlying cause is unestablished. Chronic dysuria with a confirmed cause, such as interstitial cystitis (N30.10/N30.11), requires the specific confirmed-condition code rather than R30.0.

R30.0 inclusions and exclusions

The ICD-10-CM tabular list carries an Excludes1 note under the R30 category. That note, plus the guideline on confirmed diagnoses, governs when R30.0 may be used.

An Excludes1 note means the two codes cannot be reported together on the same claim. Psychogenic pain on urination (F45.8) and R30.0 are mutually exclusive. The “superseded when confirmed” entries are not Excludes1 notes. They follow the guideline in Section I.C.18, which drops a symptom code once a confirmed diagnosis explains the symptom.

R30.0 vs R30.1: Dysuria vs vesical tenesmus

R30.1 is not a synonym for R30.0. It codes vesical tenesmus, a persistent and painful urge to urinate that continues even when little or no urine passes. Strangury, the slow, drop-by-drop passage of urine with painful spasm, is indexed to R30.0 rather than R30.1. The distinction matters because each code needs different documentation behind it.

When encounter notes describe both painful urination and a constant, ineffective urge to void, query the provider before assigning either code. Assigning R30.0 when documentation clearly supports vesical tenesmus is a specificity error that may surface at audit.

When to use ICD-10 code R30.0 vs a confirmed diagnosis code

Section I.C.18 of the ICD-10-CM Official Guidelines limits a symptom code such as R30.0 to encounters that end without a definitive diagnosis. The decision list below applies to outpatient encounters.

1. Dysuria is the only documented finding at close of encounter: Report R30.0. No confirmed condition is known.
2. Urinalysis is positive and provider documents UTI: Report N39.0 (urinary tract infection, site not specified). R30.0 is not reported, because the symptom is integral to the confirmed diagnosis.
3. Provider documents acute cystitis: Report N30.0x. R30.0 is not separately reported.
4. Provider documents urethritis: Report N34.1. R30.0 is not separately reported.
5. Provider documents “rule out UTI” or “probable UTI” in an outpatient setting: Report R30.0. Section IV of the Official Guidelines codes uncertain outpatient diagnoses to the sign or symptom. A “probable” or “suspected” condition is not coded as confirmed.

The setting changes the answer for uncertain diagnoses, so the flow below splits outpatient encounters from inpatient discharges.

The key variable is whether the provider’s assessment section of the note documents a confirmed condition. If it does, the confirmed code replaces R30.0, regardless of whether laboratory results are pending at the time of coding.

Common conditions causing dysuria and their ICD-10 codes

The conditions below are the most frequent confirmed diagnoses that replace R30.0 once an etiology is established. Each supersedes the symptom code on the claim for that encounter. N39.0 is the most common replacement, once a urinalysis or culture confirms infection.

Documentation requirements for R30.0

Payers reviewing R30.0 claims look for two facts in the note. The symptom was the reason for the encounter, and no confirmed diagnosis was available at the close of the visit. Missing any of the elements below is the second most common path to denial.

• Presenting complaint: The note must document patient-reported painful, burning, or stinging urination as the reason for the visit. A chief complaint of “UTI” without confirmed infection does not automatically support R30.0 or N39.0. The provider’s assessment determines which code applies.
• Negative or pending findings: A urinalysis may be ordered with results not yet back at the time of coding. Document the test as ordered and note that results are pending. This supports using R30.0 for the encounter.
• Assessment language: The provider’s assessment must reflect a symptom-level conclusion (e.g., “dysuria, etiology unclear” or “painful urination, UA pending”) rather than a confirmed condition. If the note says “cystitis,” code the cystitis.
• Diagnostic workup ordered: Documentation of urinalysis (UA), urine culture, or cystoscopy ordered for the visit supports medical necessity for the visit and the code. Record each order in the encounter note itself, not only in the lab system.

The CMS ICD-10 codes guidance and the ICD-10-CM Official Guidelines Section IV (Outpatient) govern these requirements. HIPAA requires covered entities to use ICD-10-CM for diagnosis coding in HIPAA-covered transactions. R30.0 must come from the code set in force on the date of service.

CPT codes commonly billed with R30.0

The table below lists the CPT codes most frequently submitted on the same claim as R30.0. Each pairing should reflect genuine medical necessity documented in the encounter note.

Payers run Correct Coding Initiative (CCI) edits on these pairings quarterly. Billing 81001 and 81003 together on the same date, for example, can trigger an edit because they overlap in method. Confirm active edits against the AAPC Codify ICD-10-CM lookup or the CMS CCI tables before submitting.

Common R30.0 claim denial reasons

R30.0 denials cluster around a small set of repeatable errors. Each one comes back with a reason code on the remittance, and our guide to medical billing denial codes explains how to read them.

• Confirmed diagnosis documented in the same note: The single most common denial cause. If the provider’s assessment mentions “cystitis,” “UTI confirmed,” or “urethritis,” the symptom code is not separately billable. The confirmed code replaces R30.0, not supplements it.
• Insufficient medical necessity documentation: The note does not clearly establish why the visit was medically necessary. The presenting complaint, the provider’s reasoning, and any tests ordered must all appear in the record.
• Using R30.0 as principal inpatient diagnosis without guideline support: Inpatient rules differ significantly, as the inpatient vs outpatient section below explains. Payers may flag R30.0 as the principal inpatient diagnosis when a confirmed condition should have been coded instead.
• Payer-specific LCD restrictions: Some Medicare Administrative Contractors (MACs) limit reimbursement for specific CPT+R30.0 pairings under Local Coverage Determinations. Check the applicable MAC’s LCD before billing cystoscopy (52000) with R30.0 as the sole indication.
• Stale code year: Submitting a code valid in FY2024 on a FY2025 date of service, or vice versa. Verify the effective date range matches the DOS.

Effective denial management workflows catch most of these before submission. Claims management software connected to your EHR and clearinghouse helps most here. It checks the diagnosis code against the CPT code before the claim leaves the practice, not after a denial comes back.

R30.0 in inpatient vs outpatient settings

The correct use of R30.0 differs materially between care settings, governed by two separate sections of the ICD-10-CM Official Guidelines.

The inpatient rule reverses the outpatient one. A provider who documents “probable pyelonephritis” in an inpatient discharge summary directs the coder to code pyelonephritis as the principal diagnosis, not R30.0. In outpatient encounters, the same phrase requires coding only the sign or symptom.

Understanding medical billing fundamentals across care settings helps billing staff apply the correct standard without defaulting to symptom codes in all contexts.

ICD-10-CM codes related to R30.0

The R30-R39 block covers the full range of symptoms and signs associated with the urinary system. Coders documenting urinary complaints frequently encounter the following codes alongside R30.0.

R30.0 may be reported alongside other symptom codes from the R30-R39 block. Each must be documented as an independent complaint, with no confirmed diagnosis explaining them. Dysuria with frequent daytime voiding, for example, takes R30.0 plus ICD-10 code R35.0 for the frequency. The same logic runs through every symptom code in the R chapter. Code the documented symptoms, then switch to the confirmed code once the cause is established.

How Pabau supports accurate R30.0 coding and claims

Most R30.0 denials start in the note, not the claim. The coder reads a free-text assessment, misses “cystitis” in the last line, and the symptom code goes out next to a confirmed diagnosis. Or the urinalysis was ordered but never recorded, and the visit loses its medical necessity.

Pabau, the practice management and EHR platform we build, keeps the presenting complaint, the orders and the assessment in one structured encounter record. The coder sees whether a cause was named before choosing between R30.0 and the confirmed code.

US claims then go out through our Claim.MD integration, which runs eligibility checks and returns ERA remittances to the same patient record.

The result is fewer resubmissions for symptom-code errors, and denials that are easier to trace back to the note that caused them.

Code R30.0 claims right the first time

Pabau keeps the encounter note, the diagnosis code and the claim in one record. US practices submit claims through our Claim.MD integration, with eligibility checks before the claim goes out.

Book a demo

Conclusion

Treat R30.0 as a code with an expiry date. It belongs on the claim while dysuria is the only documented finding, and it comes off the moment the provider names a cause.

The habit worth building is one last read of the assessment before coding. That single check catches the confirmed-diagnosis denial, the tenesmus mix-up and the inpatient “probable” rule. It is also the cheapest step toward submitting a clean claim on the first pass.

Book a demo to see how Pabau puts the encounter note, the diagnosis code and the claim in front of your coders in one place.

Continue your research

Need a clearinghouse integration for R30.0 and other ICD-10 claims? Pabau’s Claim.MD clearinghouse guide explains how the integration handles electronic claim submission and ERA remittances.

Want to understand how claim denials are managed end to end? Electronic remittance advice (ERA) explained walks through reading 835 remittance files and matching denial codes to R30.0 and other symptom claims.

Want the bigger billing picture? Revenue cycle management for medical practices covers how symptom-code encounters fit into the broader billing and collections workflow.

Frequently asked questions