ICD-10 Code N29: Other disorders of kidney and ureter

Key Takeaways

ICD-10 Code N29 is a billable diagnosis code for other disorders of kidney and ureter caused by a disease classified elsewhere.

N29 always requires a ‘Code First’ instruction: the underlying disease (such as amyloidosis, nephrocalcinosis, or schistosomiasis) must be sequenced before N29.

Excludes1 conditions (cystinosis, gonorrhea, syphilis, tuberculosis) cannot be coded alongside N29 since they have their own dedicated kidney disorder codes.

Pabau’s claims management software helps nephrology and urology practices flag manifestation codes and sequence diagnoses correctly at the point of care.

Most kidney disorder coding errors do not come from misidentifying the condition. They come from missing the sequencing step. ICD-10 Code N29 is a manifestation code, which means it cannot stand alone on a claim; the underlying disease driving the renal involvement must be coded first. Get this wrong and the claim either denies or triggers a coding audit.

This reference covers ICD-10 Code N29’s billable status, the etiology-manifestation convention, Excludes1 and Excludes2 notes, closely related codes, and the documentation requirements that payers expect when this code appears on a claim. It targets nephrology, urology, and internal medicine coders working under the 2026 ICD-10-CM code set.

ICD-10 Code N29: definition and clinical description

ICD-10 Code N29 classifies kidney and ureter disorders that a separately coded underlying systemic or infectious disease causes. The full code descriptor is “Other disorders of kidney and ureter in diseases classified elsewhere.” The phrase “in diseases classified elsewhere” signals that N29 follows the etiology-manifestation convention and cannot be sequenced as a principal diagnosis.

N29 sits within Chapter 14: Diseases of the Genitourinary System (N00-N99), subcategory N25-N29 “Other disorders of kidney and ureter.” For EHR integration for clinical coding workflows, this hierarchical position matters: the chart must capture both the systemic etiology and the renal manifestation as linked diagnoses, not as two separate unrelated problems.

Synonyms accepted under N29 include cortical nephrocalcinosis and “disorder of kidney and ureter in diseases classified elsewhere” as a general descriptor. These synonyms appear in the ICD-10-CM Index to Diseases and Injuries and help coders locate N29 when the clinical note uses different terminology.

Billable status and code hierarchy

N29 is a valid, billable ICD-10-CM diagnosis code for fiscal year 2026. The Centers for Medicare and Medicaid Services (CMS) require ICD-10-CM codes on all billing claims with a date of service on or after October 1, 2015, under the HIPAA mandate. N29 satisfies this requirement and can appear on professional and institutional claims.

Within the N25-N29 subcategory, the adjacent codes are:

The key distinction between N28.9 and N29 comes down to causation. N28.9 covers kidney and ureter disorders where no systemic etiology is documented. N29 requires a documented systemic disease as the driver. When the clinical note identifies amyloidosis, nephrocalcinosis, or schistosomiasis as the cause of the renal disorder, N29 is the correct code, not N28.9.

Etiology-manifestation convention and “Code First” instruction

The Code First instruction is the defining coding rule for N29. According to the CDC/NCHS ICD-10-CM official guidelines, when a code carries a “Code First” note, coders must not assign it as the principal diagnosis. The underlying etiology always comes first; the manifestation code (N29) follows.

The three etiology codes explicitly listed in the Tabular List under N29 are:

• Amyloidosis (E85.-): a group of diseases in which abnormal proteins (amyloid fibrils) deposit in organs, including the kidneys. The specific amyloidosis subtype should be coded to the highest degree of specificity within E85.
• Nephrocalcinosis (E83.59): calcium deposits within the kidney tissue, most commonly caused by high calcium levels in the blood or urine from metabolic disorders.
• Schistosomiasis (B65.0-B65.9): parasitic infection caused by Schistosoma species. Urogenital schistosomiasis (B65.0) is the subtype most commonly associated with urinary tract and renal involvement.

This list is not exhaustive. Other systemic diseases that cause kidney or ureter disorders “classified elsewhere” may also pair with N29, provided the clinical documentation clearly links the renal manifestation to the underlying condition. The coder should not assume this link; the physician’s note must state it, or the coder must confirm it through a query.

Sequencing example

A patient presents with renal involvement documented as secondary to systemic amyloidosis (E85.9). The correct claim sequence is:

1. E85.9 – Amyloidosis, unspecified (the etiology, sequenced first)
2. N29 – Other disorders of kidney and ureter in diseases classified elsewhere (the manifestation, sequenced second)

Reversing this order, or submitting N29 without the etiology code, will typically result in a claim denial or a request for more documentation.

Excludes1 notes: codes that cannot be used with ICD-10 Code N29

Excludes1 means mutually exclusive. When an Excludes1 note appears, coders cannot assign both codes at the same patient encounter. N29 carries Excludes1 for kidney and ureter disorders arising from four specific diseases, because each has a dedicated code within the Tabular List that already captures the renal manifestation.

A common audit finding is N29 appearing alongside A54.21, A52.75, or A18.11 on the same claim. This is always a coding error. If the underlying disease is one of the four Excludes1 conditions, the coder should drop N29 and use the disease-specific code alone — it already covers both the etiology and the manifestation.

Practices using claims management software can configure code pair edits to flag this combination before claims submission, preventing denials rather than chasing appeals.

Reduce coding errors before they reach the payer

Pabau's claims management tools help nephrology and urology practices flag manifestation code sequencing issues and Excludes1 conflicts at the point of documentation, not after a denial.

Book a demo

Related codes and crosswalks

Understanding where N29 sits relative to its neighbors helps coders choose the right code when the clinical picture is not immediately clear. The table below shows the most relevant adjacent and related codes for ICD-10 diagnostic code reference purposes.

For ICD-10-CM code lookups and official crosswalk data, the AAPC Codify ICD-10-CM lookup and the ICD List code database both provide detailed tabular list views, inclusion terms, and adjacent code navigation for N29. Practices managing complex nephrology documentation also benefit from consistent ICD-10-CM coding conventions applied across all diagnostic encounters.

Documentation requirements for accurate N29 claims

Payers reviewing N29 claims expect specific documentation elements. Missing any one of these can trigger extra information requests or outright denials on manifestation-code claims.

• Explicit causal linkage: The physician note must state that the kidney or ureter disorder is caused by, secondary to, or a manifestation of the named systemic disease. Phrases like “amyloidosis with renal involvement” or “kidney disorder due to schistosomiasis” establish the link. A co-morbidity list alone does not meet this bar.
• Specificity of the underlying disease: Code the etiology to the highest level of specificity available. “Amyloidosis” alone maps to E85.9 (unspecified); if the type is documented (hereditary amyloidosis, E85.1; organ-limited amyloidosis, E85.4), use the more specific code.
• Diagnosis confirmation: The treating physician must confirm the diagnosis before coders assign N29. Coders must not infer the link from lab values or imaging findings alone.
• Supporting workup documentation: For amyloidosis-related N29 claims, payers typically expect biopsy results. For schistosomiasis, parasite testing or serology results support the diagnosis. Documentation of the diagnostic workup strengthens the claim record.

Implementing structured digital intake forms in nephrology and urology workflows ensures staff ask the causal linkage question consistently at every encounter, not just when it is clinically obvious. Secondary diagnosis documentation standards across ICD-10-CM share the same underlying principle: the link between the primary condition and the secondary manifestation must be explicit in the note.

Practices operating under HIPAA-compliant documentation practices will find that the detail requirements for N29 align well with general HIPAA minimum-necessary standards for clinical record keeping. Both push toward complete, condition-specific documentation rather than shorthand entries.

Coding guidelines and common mistakes

The ICD-10-CM Official Guidelines for Coding and Reporting, published jointly by the World Health Organization and CMS/NCHS, govern N29 sequencing. Section I.A covers the etiology-manifestation convention in full. Three mistakes account for the majority of N29 coding errors.

Mistake 1: sequencing N29 before the etiology

Placing N29 in the first diagnosis position on the claim is a hard rule violation. Many practice management systems and clearinghouses flag manifestation codes submitted without an etiology code immediately preceding them. If your software does not catch this, a manual sequencing check is required before every N29 claim goes out. Direct primary care EHR workflows that handle complex chronic disease patients are especially prone to this error when multiple problems are entered in the wrong order.

Mistake 2: using N29 with an Excludes1 condition

Coding N29 alongside A18.11, A52.75, A54.21, or E72.0 on the same encounter is a code pair conflict. These four conditions are mutually exclusive with N29 because their dedicated codes already capture the renal manifestation. The correct action is to remove N29 and keep only the disease-specific code. Coders who regularly review ICD-10-CM coding conventions around Excludes1 notes build the habit of checking these notes before finalising any claim where N29 appears.

Mistake 3: coding N29 from an unlinked clinical note

A note that lists two diagnoses side by side without explicitly linking them does not support N29. “Patient has amyloidosis. Patient has renal insufficiency.” is not sufficient documentation. The coder either needs the note to say “renal disorder secondary to amyloidosis” or must send a physician query. Defaulting to N28.9 until the link is confirmed is the conservative and compliant approach. Consistent use of compliance management software with built-in query workflows reduces the turnaround time on these confirmations.

Using N29 in nephrology and urology practice workflows

N29 appears most commonly in nephrology outpatient encounters, internal medicine complex chronic disease visits, and urology referrals where the patient has a known systemic disease with documented renal involvement. Coders reach for N29 less often in emergency settings, where the primary presentation typically drives sequencing toward the acute condition rather than the underlying chronic disease.

For practices managing amyloidosis patients, N29 will appear repeatedly across encounters as the clinical team monitors the renal manifestation over time. Using client record documentation that carries forward diagnosis code sequences across visits reduces the risk of sequencing inconsistency between encounters. Inconsistent sequencing across a single patient’s records is a red flag in payer audits.

Schistosomiasis-related N29 claims are more common in practices serving immigrant populations from sub-Saharan Africa, the Middle East, and parts of South America where the parasite is widespread. Internal medicine and functional medicine software platforms that support complex multi-diagnosis documentation make it easier to capture the full etiology chain when multiple systemic factors are at play.

From an admin standpoint, practices should ensure their practice management software supports code-pairing logic and allows coders to flag diagnosis sequences for clinical review before submission. This is where technology and documentation discipline work together to protect revenue. Pabau’s claims management software is designed to support exactly this kind of pre-submission review, reducing the N29-related denial rate before it accumulates into a revenue problem.

Conclusion

ICD-10 Code N29 is simpler in description than it is in practice. Getting it right means verifying the causal link in the documentation, sequencing the etiology before the manifestation, and steering clear of the four Excludes1 conditions that have their own dedicated renal disorder codes.

For nephrology and urology practices submitting these claims regularly, the difference between clean N29 claims and a pattern of denials often comes down to workflow infrastructure. Pabau’s digital intake forms and structured clinical documentation tools help practices capture the causal linkage language that N29 demands, while the claims management layer catches sequencing errors before they reach the payer. To see how Pabau handles complex diagnostic code workflows in practice, book a demo.

Continue your research

Need a complete ICD-10 reference for intraparenchymal diagnoses? Intraparenchymal hemorrhage ICD-10 codes covers sequencing rules and documentation requirements for another complex manifestation code category.

Managing compliance documentation across your practice? Compliance management software from Pabau helps practices build audit-ready workflows for complex ICD-10 claims.

Looking to streamline clinical record keeping for chronic disease patients? Client record documentation in Pabau carries diagnosis sequences forward across encounters, reducing inconsistency on repeat N29 claims.

Frequently Asked Questions