...

ICD 10 Code for UTI: N39.0 Coding, Documentation, and Billing Guide

ICD-10 code for UTI showing medical billing documentation for urinary tract infection diagnosis and coding.
ICD-10 code for UTI showing medical billing documentation for urinary tract infection diagnosis and coding.
Touseef Riaz
Written by Touseef Riaz Founder, UControl Billing

A chart that says “UTI” does not always lead to the same ICD 10 CM code.

That is where UTI coding gets tricky.

A patient may come to primary care with burning urination, frequency, and a positive urine test. The provider may document “UTI, site not specified.” In that situation, N39.0, urinary tract infection, site not specified, can fit the record.

But suppose the assessment says acute cystitis without hematuria. The coder now has a site-specific diagnosis and should review N30.00 rather than defaulting to N39.0.

The difference seems small when you read the diagnoses side by side. From a coding standpoint, it changes the code selection.

The same issue comes up with pyelonephritis, urethritis, pregnancy related urinary infections, neonatal UTI, candidiasis, and even cases where the chart contains pyuria but never establishes an infection.

For physicians, nurse practitioners, physician assistants, coders, and billing teams, the safest approach starts with one question:

What urinary condition did the provider actually establish in the medical record?

From there, review the anatomical site, clinical details, applicable ICD 10 CM conventions, and the Tabular List instructions before finalizing the diagnosis code.

This guide focuses on that process. It explains when N39.0 fits, when another code belongs on the claim, how documentation affects the decision, and where common UTI coding mistakes occur.

What Is the ICD 10 Code for a UTI?

For a urinary tract infection where the documentation does not identify the site, the ICD 10 CM code is:

N39.0, Urinary tract infection, site not specified

The wording matters. N39.0 does not mean “all UTIs.” It specifically describes a urinary tract infection for which the site has not been specified.

That makes N39.0 useful when the provider establishes the infection but does not document whether it involves the bladder, kidney, urethra, or another specific part of the urinary tract.

Consider this assessment:

Assessment: UTI.

If the provider does not establish a more specific urinary diagnosis elsewhere in the record, the documentation may support N39.0.

Now compare it with:

Assessment: Acute cystitis without hematuria.

The second diagnosis identifies the bladder condition and gives the coder information about acuity and hematuria. The coder should therefore review the appropriate N30 code rather than treating the diagnosis as an unspecified UTI.

That is the central issue with N39.0. The code works when the documentation leaves the infection site unspecified. It should not replace a more specific diagnosis that the provider has already documented.

N39.0 Does Not Mean “Use This for Any UTI”

One of the easiest UTI coding mistakes is treating N39.0 as a universal UTI code.

The code description itself tells you what limits its use: site not specified.

If the provider documents cystitis, the infection has a documented site. If the provider documents pyelonephritis, the record identifies a kidney infection. If the provider documents urethritis, the diagnosis identifies the urethra.

In each situation, the coder needs to move beyond the general term “UTI.”

This becomes especially important when the same encounter contains both general and specific language.

For example:

“Patient presents with dysuria and frequency. UA positive. Assessment: UTI, acute cystitis without hematuria.”

The word “UTI” appears in the note, but the assessment also identifies acute cystitis without hematuria. The more specific diagnosis provides the information needed to review the N30 category.

The coder should not simply select N39.0 because it happens to contain the word “UTI.”

Other UTI ICD -10 Codes List

Codes Code Description
N30.00 acute cystitis without hematuria
N30.01 acute cystitis with hematuria
N30.10 Interstitial cystitis (chronic) without hematuria
N30.11 Interstitial cystitis (chronic)with hematuria
N30.20 Other chronic cystitis without hematuria
N30.21 Other chronic cystitis with hematuria
N30.30 Trigonitis without hematuria
N30.31 Trigonitis with hematuria
N30.40 Irradiation cystitis without hematuria
N30.41 Irradiation cystitis with hematuria
N30.80 Other cystitis without hematuria
N30.81 Other cystitis with hematuria
N30.90 Cystitis, unspecified without hematuria
N30.91 Cystitis, unspecified with hematuria
N34.0 Urethral abscess
N34.1 Nonspecific urethritis
N34.2 Other urethritis
N34.3 Urethral syndrome, unspecified
N39.0 Urinary tract infection, site not specified
N39.9 Disorder of urinary system, unspecific

 

When N39.0 Is Appropriate

N39.0 fits a record in which the provider has established a urinary tract infection but has not identified the anatomical site.

A typical example might look like this:

Assessment:
“Urinary tract infection, site not specified.”

The provider has established the condition and has also made clear that the site remains unspecified.

Another example:

Assessment:
“UTI. Culture pending. No evidence of pyelonephritis. Site not specified.”

Again, the record supports an unspecified urinary tract infection.

The coder should still review the complete record before finalizing the claim. The assessment may contain more specific information elsewhere. The history, examination, diagnostic findings, and plan can also provide context, but the coder should not independently create a diagnosis that the provider has not established.

What N39.0 Tells the Payer

A diagnosis code communicates more than the name of a condition.

N39.0 tells the payer that the provider documented a urinary tract infection but did not identify the infection site.

It does not tell the payer:

  • that the infection involves the bladder
  • that the patient has pyelonephritis
  • that the patient has urethritis
  • that the infection is acute
  • that hematuria accompanies the infection
  • which organism caused the infection

Those details require documentation and, where applicable, additional or more specific codes.

That distinction helps explain why a coder should not add clinical specificity that the medical record does not support.

N39.0 and Cystitis Are Not Interchangeable

Cystitis and an unspecified UTI may appear similar in everyday clinical conversation, but ICD 10 CM coding treats them differently.

Cystitis identifies inflammation of the bladder. The N30 category contains the relevant cystitis codes.

For example:

Diagnosis documented Code to review
Acute cystitis without hematuria N30.00
Acute cystitis with hematuria N30.01
Cystitis, unspecified without hematuria N30.90
Cystitis, unspecified with hematuria N30.91

The important part is not memorizing four codes. It is recognizing what information changes the code.

If the provider documents acute cystitis without hematuria, the documentation supplies three useful pieces of information:

The condition is cystitis.

The condition is acute.

The documentation does not report hematuria.

That information allows the coder to select a more specific code than N39.0.

Example: How One Phrase Changes the Coding Decision

Consider these two assessments:

Assessment A:
“UTI, site not specified.”

Assessment B:
“Acute cystitis without hematuria.”

The first points toward N39.0.

The second points toward N30.00.

The patient’s symptoms could look nearly identical in both encounters. The coding difference comes from the provider’s documented diagnosis.

N39.0 and Pyelonephritis

Pyelonephritis represents a kidney infection, so it should not be treated as an unspecified UTI.

For an acute case, N10, acute pyelonephritis, is the relevant code to review.

A patient with fever, flank pain, urinary symptoms, and other findings may clinically raise concern for a kidney infection. But coding still depends on what the provider documents.

For example:

“Acute pyelonephritis.”

This gives the coder a specific diagnosis.

By contrast:

“UTI. Dysuria and frequency. No site documented.”

This does not establish pyelonephritis merely because the patient has urinary symptoms.

The coder should not move a patient from N39.0 to N10 based on an assumption about clinical severity.

N39.0 and Urethritis

Urethritis belongs to the N34 category.

Examples include:

  • N34.1, nonspecific urethritis
  • N34.2, another urethritis
  • N34.3, urethral syndrome, unspecified

Again, the provider’s diagnosis controls the selection.

A patient can have dysuria without having a documented UTI. Dysuria also can occur with urethral conditions and other urinary or genital disorders.

That is why coders should resist the temptation to turn every urinary symptom or abnormal urine test into N39.0.

UTI Symptoms Are Not the Same as a UTI Diagnosis

This point deserves its own section because it causes confusion in outpatient coding.

A patient may report:

  • burning during urination
  • increased urinary frequency
  • urgency
  • pelvic discomfort
  • cloudy urine
  • blood in the urine

Those findings can prompt a UTI workup. They do not, by themselves, tell the coder which diagnosis the provider established.

Imagine an encounter where the provider writes:

“Dysuria. UA ordered. Await culture.”

The coder should not independently convert that assessment into N39.0.

Now consider:

“UTI, site not specified. Treat with antibiotic. Culture sent.”

The provider has documented the infection, and N39.0 may fit if no more specific site or condition appears in the record.

The difference lies in the assessment, not in the patient’s symptom list.

What If the Urine Culture Identifies an Organism?

A urine culture can add useful information to the record, especially when it identifies the organism responsible for an infection.

But the culture result should not replace the provider’s diagnostic documentation.

For N39.0, ICD 10 CM includes an instruction to use an additional code from the B95 to B97 categories to identify an infectious agent when applicable.

For example, if the provider documents an unspecified site UTI and the record establishes E. coli as the causative organism, the coding team should review the appropriate additional organism code.

The important distinction is this:

N39.0 describes the urinary infection and its unspecified site. An additional organism code can identify the infectious agent.

The organism code does not turn N39.0 into cystitis or pyelonephritis.

Common UTI Coding Situations

UTI With Site Not Documented

Documentation:
“UTI, site not specified.”

Code:
N39.0

The diagnosis identifies a urinary infection but does not identify its anatomical location.

Acute Cystitis Without Hematuria

Documentation:
“Acute cystitis without hematuria.”

Code:
N30.00

The provider has supplied the site, acute status, and hematuria status.

Acute Cystitis with Hematuria

Documentation:
“Acute cystitis with hematuria.”

Code:
N30.01

The presence of hematuria changes the code selection.

Acute Pyelonephritis

Documentation:
“Acute pyelonephritis.”

Code:
N10

The diagnosis identifies a kidney infection.

Pyuria Without a Documented UTI

Documentation:
“Pyuria. No UTI diagnosed.”

The coder should not automatically report N39.0.

Pyuria has its own code, R82.81, and N39.0 contains an Excludes1 instruction for pyuria.

The lesson here is straightforward: an abnormal test result and a diagnosed infection are not automatically the same thing.

When N39.0 Should Not Be Used

The Tabular List contains important exclusions for N39.0.

Candidiasis of the Urinary Tract

Urinary tract candidiasis falls under the applicable B37.4 category rather than N39.0.

Neonatal UTI

Neonatal urinary tract infection uses P39.3 rather than N39.0.

Pyuria

R82.81 identifies pyuria. The presence of pyuria alone does not establish an unspecified UTI.

Site Specific Urinary Infection

When documentation identifies cystitis, urethritis, pyelonephritis, or another specific urinary condition, the coder should review that condition’s code rather than automatically selecting N39.0.

These instructions matter because ICD 10 CM coding depends on more than finding a familiar term in the Index. The coder must also check the Tabular List and follow its instructions.

UTI Coding When the Patient Is Pregnant

Pregnancy changes the coding review.

A pregnant patient with a urinary infection should not automatically receive N39.0 simply because the provider writes “UTI.”

The coder should determine whether the infection complicates pregnancy and then review the applicable pregnancy codes and sequencing instructions.

This is one of the situations where a general urinary system code can give an incomplete picture of the encounter.

The same principle applies to other special populations. Neonatal infections, for example, have their own coding structure.

Recurrent UTI: What Should the Coder Look For?

The phrase “recurrent UTI” deserves a careful read.

It can describe an active infection in a patient who has experienced previous infections. It can also appear in the medical history when the patient does not have an active infection during the current encounter.

Those are not the same coding situation.

Compare:

“Recurrent UTI. Current symptoms and positive culture. Treat today.”

with:

“History of recurrent UTI. No current infection.”

The first describes a current clinical problem. The second describes medical history.

The coder should read the assessment and plan carefully before assigning an active infection code.

Do not assume that the word “recurrent” alone determines the diagnosis code.

Catheter Associated UTI Requires Documentation of the Relationship

A urinary catheter in the patient’s chart does not automatically make an infection catheter associated.

The record needs to establish the relationship when the coding guidelines require that relationship.

For example:

“UTI associated with indwelling urinary catheter.”

This provides a materially different documentation picture from:

“History of Foley catheter. Current UTI.”

The coder should review the complete documentation and the applicable device complication guidelines before assigning a catheter related diagnosis.

This is another reason why coding directly from a problem list or isolated laboratory result can produce the wrong answer.

UTI Coding Errors That Show Up in Real Charts

The Coder Stops at the First “UTI” Mention

A note may mention UTI in the history and later document acute cystitis in the assessment.

If the coder stops reading after finding the first occurrence of “UTI,” the claim may receive N39.0 even though the provider documented a more specific diagnosis.

The Coder Treats a Positive UA as the Diagnosis

Urinalysis findings can support the provider’s clinical evaluation. They do not allow the coder to invent a diagnosis.

The claim needs to reflect the provider’s documented condition.

The Coder Ignores the Tabular List

Finding N39.0 through an encoder or code search is only part of the job.

The coder still needs to review the Tabular List for Excludes notes and other instructions.

The Coder Uses N39.0 for Cystitis

This often happens when the coder treats “UTI” and “cystitis” as interchangeable terms.

They are not interchangeable for ICD 10 CM code selection.

The Coder Adds an Organism Without Checking the Coding Instructions

A culture result may identify an organism, but the coder should check whether an additional organism code applies and whether the provider documentation supports the diagnosis.

UTI Documentation Tips for Providers

Providers can make UTI coding considerably easier by being specific in the assessment.

Instead of documenting only:

“UTI.”

consider documenting the diagnosis that the clinical evidence supports.

For example:

“Acute cystitis without hematuria.”

or:

“Acute pyelonephritis.”

or:

“UTI, site not specified.”

The goal is not to add detail that the clinical record cannot support. The goal is to state the diagnosis clearly enough that the coder does not have to guess what the provider meant.

If the organism matters to the diagnosis, document the relevant culture information and clinical interpretation.

If the patient has a catheter and the provider establishes a relationship between the device and infection, document that relationship.

Clear assessment language gives the coding team something concrete to work with.

UTI Billing: What Should the Revenue Cycle Team Review?

UTI coding errors can start before the claim reaches the payer.

A billing team reviewing these encounters should check whether the diagnosis on the claim matches the provider’s documentation.

A useful pre submission review includes:

  • Diagnosis: Does the claim reflect the provider’s final diagnosis?
  • Specificity: Did the provider identify cystitis, pyelonephritis, urethritis, or another specific condition?
  • Exclusions: Does N39.0 have an Excludes1 instruction that applies?
  • Additional codes: Does the Tabular List call for another code?
  • Date of service: Is the practice using the ICD 10 CM code set applicable to that date?
  • Documentation: Can the diagnosis reported on the claim be supported by the medical record?

These checks are especially useful when a practice handles a large volume of primary care, urgent care, family medicine, urology, or women’s health encounters.

Final Thoughts

N39.0 has a narrow job in ICD 10 CM coding.

It identifies a urinary tract infection when the site has not been specified.

It should not become the automatic answer whenever a chart contains the word “UTI.”

The coding decision should follow the diagnosis documented by the provider. If the record establishes acute cystitis, review the appropriate N30 code. If it establishes acute pyelonephritis, review N10. If it documents urethritis, review N34. If the record contains pyuria without a diagnosed infection, do not turn that finding into N39.0.

The same careful review applies to pregnancy related infections, neonatal UTI, candidiasis, catheter associated infections, and cases where a culture identifies an organism.

Coders and billing teams must read the assessment completely, identify the condition and site, check the Tabular List, and code only what the documentation supports.

That approach produces a cleaner connection between the clinical note, the diagnosis code, and the claim.

Share this :

Touseef Riaz, Founder and CEO of UControl Billing
Author & Revenue Cycle Management Expert

Founder & CEO at UControl Billing

10+ Years RCM Expertise HIA-LI Member MGMA Member Healthcare Revenue Cycle

A couple of years ago, I executed the effective plan of creating a Medical billing and Coding company named UControl Billing. The company aims to bring revolutionary advancements to foster medical billing and coding revenues. As an official member of HIA-LI and MGMA, I feel honored in providing networking opportunities, problem-solving, and improving the revenue management cycle.

Medical Billing Medical Coding Revenue Cycle Management Practice Revenue Performance Claims & Denials

Amount
You're Missing

We audit your last 30 days of claims and deliver a written report with a real recovery figure

    FREE CONSULTATION

    Get Your Free Billing Review

    Find out how your practice can improve revenue and reduce claim delays.

    ✓ No obligation   |   ✓ Expert RCM Review

    Our Latest Posts

    Scroll to Top