ICD-10-CM Code R31.9: Hematuria, Unspecified

Key Takeaways

R31.9 is billable for unspecified hematuria presentation

N02.9 codes recurrent or persistent hematuria pathology

Type 1 Excludes rules prevent dual symptom coding

R31.0 specifies gross hematuria versus microscopic

Documentation must justify code selection over symptom codes

ICD-10-CM Hematuria: Clinical Coding Overview

Hematuria – blood in the urine – presents coding challenges because ICD-10-CM distinguishes between symptom codes, chronic pathology codes, and codes capturing hematuria as a feature of underlying conditions. Clinicians billing for hematuria evaluation must select codes that reflect whether the presentation is isolated, recurrent, or secondary to another diagnosis.

According to the Centers for Medicare and Medicaid Services (CMS), the R31 code family sits within the “Symptoms and signs involving the genitourinary system” chapter. The parent code R31 is non-billable – only its subcodes carry specificity for claims submission. This structure forces coders to choose between gross versus microscopic presentation, or defer to unspecified when clinical documentation does not establish either.

The World Health Organization (WHO) ICD-10 classification establishes R31 as a symptom code rather than a disease diagnosis. When hematuria indicates chronic glomerular disease, coders must pivot to the N02 series instead. This distinction between symptom and pathology codes determines which diagnostic category the claim falls under and influences payer review patterns.

ICD-10-CM Hematuria Code R31.9: Hematuria, Unspecified

R31.9 is the default billable code when clinical documentation confirms hematuria but does not specify whether the blood is visible (gross) or microscopic. This code applies to isolated presentations without established recurrence patterns or identifiable underlying pathology at the time of encounter.

CMS updated the R31.9 descriptor in the 2026 code set to emphasise unspecified nature. The code captures initial hematuria evaluations where urinalysis confirms blood but further investigation has not yet occurred. Practices using claims management software can validate R31.9 against encounter notes to ensure documentation supports unspecified status rather than a more specific subcode.

R31.9 carries no modifier requirements and accepts both outpatient and inpatient settings. The code does not imply severity – it simply indicates that hematuria is present but uncharacterised. When follow-up reveals gross versus microscopic presentation, coders should transition to R31.0 or R31.1 in subsequent claims.

ICD-10-CM Hematuria Code Clinical Scenarios for R31.9

A 42-year-old presents with routine urinalysis showing 10-15 RBC per high-power field. The patient reports no visible blood. Documentation states “hematuria, etiology unclear.” R31.9 applies because the finding is microscopic but the clinician has not yet specified R31.1.

A 68-year-old with a history of benign prostatic hyperplasia presents with urinalysis positive for blood. Documentation reads “hematuria noted, unclear if related to BPH.” Because the clinician has not attributed the hematuria to an underlying condition, R31.9 remains the appropriate symptom code rather than coding the BPH alone.

An urgent care visit captures “patient reports pink-tinged urine, dipstick positive for blood.” The documentation does not describe volume, frequency, or visibility clearly. R31.9 supports this unspecified presentation until further workup clarifies gross versus microscopic status.

ICD-10-CM Code N02.9: Recurrent and Persistent Hematuria

N02.9 shifts the coding context from symptom to chronic glomerular pathology. This code applies when hematuria recurs over multiple encounters or persists despite treatment, indicating underlying kidney morphology changes rather than isolated symptom presentation.

The CDC ICD-10-CM web tool classifies N02.9 under “Diseases of the genitourinary system” rather than symptoms. This distinction matters because payers apply different medical necessity criteria to pathology codes versus symptom codes. N02.9 implies chronicity and often triggers nephrology referral requirements under payer policies.

Documentation supporting N02.9 must establish recurrence across at least two separate encounters or persistent hematuria lasting longer than the acute evaluation period. A single episode, even if prolonged, does not satisfy N02.9 coding criteria. Clinics using integrated EHR systems can flag patients with multiple hematuria encounters to prompt consideration of N02.9 rather than repeated R31.9 claims.

N02.9 Hematuria ICD-10 Code vs R31.9: Differentiating Recurrence

R31.9 applies to isolated or initial presentations. N02.9 applies when documentation confirms recurrence or persistence. A 55-year-old with hematuria on three separate urinalyses over six months meets N02.9 criteria if the clinician documents “recurrent hematuria.” The same patient presenting for the first time codes as R31.9.

Persistent hematuria differs from recurrent. Persistent means continuous presence across multiple tests without resolution. Recurrent means episodic – the hematuria resolves and returns. Both qualify for N02.9, but documentation language must explicitly state persistence or recurrence to justify the code.

When transitioning from R31.9 to N02.9, the encounter note should reference prior episodes. “Patient returns with hematuria, third occurrence in four months” supports N02.9. “Patient presents with hematuria” without historical context supports R31.9 even if the EHR shows prior visits.

ICD-10-CM Hematuria Chart: Code Selection by Clinical Context

This table reflects CMS ICD-10 code list structures for hematuria presentations. The R31 series separates symptom codes by visibility and character, while N02 series indicates chronic glomerular pathology. N30.01 demonstrates how hematuria codes nest within condition-specific codes when hematuria is a documented feature of the primary diagnosis.

Gross Hematuria ICD-10 Code: R31.0 Documentation Standards

R31.0 applies when documentation confirms visible blood in urine. “Gross hematuria” signals the clinician has observed or the patient has reported red, pink, or cola-coloured urine. This specificity moves the code from R31.9 to R31.0 and often triggers different diagnostic protocols under payer policies.

Visibility matters because gross hematuria carries higher risk associations than microscopic hematuria. According to ResDAC ICD coding guidance, R31.0 supports more extensive workup authorisations including cystoscopy and imaging studies. Payers link R31.0 to bladder cancer screening protocols, particularly in patients over 50 with smoking history.

Documentation supporting R31.0 should describe the observation. “Patient reports red urine for two days” meets the threshold. “Dipstick positive for blood” does not – dipstick findings without visible blood support microscopic hematuria codes instead. When the patient reports visible blood but urinalysis shows only trace microscopic blood, code based on the clinical assessment documented in the encounter note.

R31.0 vs R31.9: When Gross Hematuria Is Unspecified

If documentation states “hematuria, query gross” or “possible gross hematuria,” R31.9 remains appropriate until the clinician confirms visibility. Uncertainty defaults to unspecified status. Coding R31.0 based on patient report alone without clinician corroboration risks downcoding on review.

Practices should train clinical staff to ask patients whether urine appears red or pink to support R31.0 coding. “Have you seen blood in your urine?” yields codable information. Recording the patient’s affirmative answer in the encounter note justifies R31.0 even when office urinalysis shows cleared or minimal blood.

Automate Hematuria Code Validation

Pabau's EHR flags incomplete documentation when R31.9 appears in encounters containing gross hematuria descriptors. The system prompts coders to review for R31.0 specificity before claim submission, reducing denials from undercoding symptom presentations.

Book a demo

Type 1 Excludes Rules for ICD-10-CM Hematuria Codes

ICD-10-CM Type 1 Excludes notes indicate mutually exclusive coding. According to CMS coding guidelines, R31 codes carry Type 1 Excludes for “hematuria included with underlying conditions.” This rule prevents double-coding when hematuria appears as a documented feature of another diagnosis.

N30.01 demonstrates this exclusion. Acute cystitis with hematuria is coded as N30.01 alone – adding R31.9 creates a coding error because the N30.01 descriptor already captures the hematuria. The same principle applies to other genitourinary conditions where hematuria is an expected finding.

Clinics using digital intake forms can pre-populate condition lists that trigger hematuria exclusion checks. When a clinician documents both cystitis and hematuria, the system should prompt: “Hematuria is captured by N30.01. Remove R31.X code?” This workflow prevents inadvertent Type 1 Excludes violations that delay payment.

Common Type 1 Excludes Scenarios

A patient presents with acute cystitis documented as the primary diagnosis. The encounter note mentions “dysuria with hematuria.” Code N30.01 only. Do not add R31.9 or R31.0.

A patient with known kidney stones presents with gross hematuria attributed to stone passage. The urologist documents “renal calculus with associated hematuria.” Code the calculus diagnosis (N20.0) without R31.0 because the hematuria is secondary to the stone and the stone code takes precedence.

A patient with documented glomerulonephritis presents with recurrent hematuria. The nephrologist codes the glomerulonephritis diagnosis without adding N02.9 because the hematuria is already implied by the nephritis code’s clinical definition.

Documentation Requirements for Hematuria ICD-10 Code Selection

CMS requires clinical documentation to justify code specificity. For hematuria codes, this means encounter notes must explicitly describe visibility, frequency, duration, and context. Generic statements like “hematuria present” support R31.9 but nothing more specific.

Documentation supporting R31.0 requires phrases like “patient reports red-coloured urine” or “visual inspection confirms blood-tinged specimen.” For R31.21 (asymptomatic microscopic), the note should state “incidental microscopic hematuria on routine screen, patient asymptomatic.” These descriptors provide clear rationale for code selection during payer review.

N02.9 documentation must establish chronicity. “Patient returns with hematuria, third episode in five months” supports recurrence. “Persistent microscopic hematuria over three months despite treatment” supports persistence. Without temporal markers, coders cannot justify N02.9 over R31.9.

Hematuria ICD-10 Billing Documentation Templates

Practices can standardise hematuria documentation using templates integrated into AI-powered clinical note generation tools. A template prompts clinicians to specify: visible versus microscopic, first occurrence versus recurrent, symptomatic versus asymptomatic, and associated symptoms (dysuria, frequency, urgency).

Template fields include checkboxes for gross visibility, date of prior hematuria episodes, and dropdown menus for associated diagnoses. When completed, the template auto-generates documentation phrases that map directly to code descriptors. This approach reduces ambiguous language that forces coders to default to R31.9 when a more specific code applies.

For billing workflows, templates should flag when hematuria appears alongside conditions carrying Type 1 Excludes. An alert reading “Cystitis diagnosis present – hematuria captured by N30.01, remove R31.X?” prevents coding errors before claim submission.

Acute Cystitis with Hematuria: N30.01 Coding Rules

N30.01 captures acute bladder infection when hematuria is a documented feature. This combination code eliminates the need for separate R31.X coding. The descriptor “Acute cystitis with hematuria” signals that blood in urine is expected and already accounted for in the diagnosis.

When encounter documentation states “acute cystitis” without mentioning hematuria, coders should use N30.00 (acute cystitis without hematuria) instead. If urinalysis shows blood but the clinician does not document hematuria in their assessment, coding from lab results alone risks downcoding. The clinical assessment must explicitly state the hematuria for N30.01 to apply.

Payers scrutinise N30.01 claims for antibiotic prescriptions and culture orders. The code implies bacterial infection, so documentation should include dysuria, frequency, urgency, or other cystitis symptoms. Hematuria alone without inflammatory symptoms does not support N30.01 – that presentation codes as R31.X with further investigation pending.

N30.01 vs R31.9: When Hematuria Accompanies Cystitis

A 34-year-old presents with dysuria, frequency, and gross hematuria. Urinalysis shows white blood cells and blood. The clinician diagnoses acute cystitis. Code N30.01 captures both the infection and the hematuria. Do not add R31.0.

A 50-year-old with a history of recurrent UTIs presents with hematuria but no dysuria or urgency. Urinalysis shows blood but no white cells or bacteria. The clinician orders culture and plans follow-up. Code R31.9 because the presentation does not meet cystitis criteria. If culture returns positive and the patient develops symptoms, subsequent encounters may code N30.01.

A patient treated for cystitis two weeks ago returns with persistent hematuria. Symptoms of infection have resolved. The clinician documents “post-cystitis hematuria, resolving.” Code R31.9 for the isolated hematuria at this encounter rather than N30.01 because the acute infection has cleared.

ICD-10-CM Hematuria Billing Compliance Strategies

Compliance begins with specificity. Generic “hematuria” documentation without modifiers forces R31.9 usage even when clinical context supports more specific codes. Practices should audit coding patterns quarterly to identify R31.9 overuse relative to R31.0, R31.1, and R31.2X subcodes.

Tracking R31.9-to-N02.9 transitions helps identify patients with chronic hematuria who should shift to pathology coding. Clinics using integrated scheduling and documentation systems can flag patients with three or more R31.9 encounters within six months. This triggers clinician alerts to document recurrence or persistence in subsequent visits, enabling N02.9 coding if appropriate.

Type 1 Excludes violations represent the most common hematuria coding error. Practices should implement pre-claim edits that flag R31.X codes appearing alongside N30.01, N20.X, or other conditions where hematuria is an expected finding. Manual review before submission prevents denials and reduces rework.

Hematuria ICD-10 Denial Prevention Workflows

Build coding templates that prompt for gross versus microscopic specification during initial hematuria encounters. When urinalysis results populate the chart, the system should ask: “Is blood visible to patient?” Yes triggers R31.0 prompts. No triggers R31.2X prompts. Unanswered defaults to R31.9.

For repeat hematuria presentations, pre-load prior encounter dates into the coding interface. When the same patient presents with hematuria for a third time, display prior dates and prompt: “Document recurrence for N02.9 consideration?” This workflow moves chronicity assessment from retrospective audit to point-of-care coding.

Implement real-time payer policy checks that compare selected codes against coverage criteria. Some payers require specific modifiers or additional documentation for R31.0 claims in patients over 50. Surfacing these requirements during encounter coding reduces post-submission denials.

Expert Picks

Need guidance on claims management integration? Claims Management Software embeds ICD-10 validation rules directly into billing workflows, flagging common hematuria coding errors before claim submission.

Documenting recurrent conditions efficiently? Client Record Systems surface prior encounter summaries during chart review, making it easier to identify patients meeting N02.9 recurrence criteria.

Standardising clinical documentation across providers? Echo AI Clinical Documentation generates structured notes from clinician dictation, ensuring hematuria descriptors meet ICD-10 specificity requirements without manual template navigation.

Conclusion: ICD-10-CM Hematuria Code Selection for Billing Accuracy

Hematuria coding requires clinicians to distinguish symptom presentation from chronic pathology, isolated episodes from recurrent patterns, and visible blood from microscopic findings. R31.9 serves as the unspecified default when documentation lacks specificity. R31.0 applies when gross hematuria is documented. N02.9 replaces symptom codes when recurrence or persistence is established.

Type 1 Excludes rules prevent dual coding when hematuria appears as a feature of primary diagnoses like cystitis or kidney stones. Practices must embed these exclusion rules into coding workflows to prevent denials. Specificity in clinical documentation – describing visibility, frequency, and chronicity – enables accurate code selection and supports payer reviews.

Quarterly audits of R31.9 usage patterns identify opportunities to shift patients to more specific codes or transition chronic presentations to N02.9 pathology codes. Integrated EHR systems that surface prior hematuria encounters during coding reduce retrospective rework and improve first-pass billing accuracy.

Frequently Asked Questions