The ICD 10 code for anemia of chronic kidney disease is D63.1 — officially described as “Anemia in chronic kidney disease.” This code sits under the category of anemia in other chronic diseases and should never be sequenced as the primary diagnosis. You must code the underlying CKD first (from the N18 series), then follow it with D63.1. Get the sequencing wrong, and you’ll face claim denials.
If you’re a coder, biller, clinician, or student searching for this, here’s what you actually need to know: D63.1 is a manifestation code, meaning it cannot stand alone. It requires dual coding — the CKD etiology code plus D63.1. Below, I’ll walk through exact sequencing rules, the CKD stage codes you’ll pair it with, diagnostic criteria that justify this code, and the common mistakes that trigger audits.
ICD 10 Code D63.1: What It Covers and What It Doesn’t
D63.1 specifically captures anemia that develops as a direct consequence of chronic kidney disease. The kidneys produce about 90% of the body’s erythropoietin (EPO), the hormone that drives red blood cell production. As kidney function deteriorates, EPO production drops, and anemia follows. By CKD stage 3, roughly 5–10% of patients are anemic. By stage 5, that number climbs above 50–70%.
This code does not cover:
- Anemia from acute kidney injury (use the appropriate AKI code + anemia code)
- Iron deficiency anemia that happens to coexist with CKD but isn’t caused by it (use D50.x)
- Anemia of chronic disease unrelated to kidney dysfunction (D63.8)
- Aplastic anemia or myelodysplastic syndromes in CKD patients (separate codes entirely)
The clinical documentation must explicitly link the anemia to CKD. A progress note saying “anemia, CKD stage 4” isn’t enough — the provider needs to state “anemia due to CKD” or “anemia secondary to chronic kidney disease” for D63.1 to be justified.
Correct ICD 10 Sequencing for CKD Anemia
This is where most coding errors happen. D63.1 carries a “Code first” instruction in the ICD-10-CM tabular list, directing you to sequence the underlying kidney disease before the anemia code. Here’s how the sequencing works in practice:
| CKD Stage | Primary Code (Sequenced First) | Secondary Code |
|---|---|---|
| CKD Stage 1 | N18.1 | D63.1 |
| CKD Stage 2 (mild) | N18.2 | D63.1 |
| CKD Stage 3a | N18.31 | D63.1 |
| CKD Stage 3b | N18.32 | D63.1 |
| CKD Stage 4 (severe) | N18.4 | D63.1 |
| CKD Stage 5 | N18.5 | D63.1 |
| End-stage renal disease (ESRD) | N18.6 | D63.1 |
| CKD, stage unspecified | N18.9 | D63.1 |
If the patient is on dialysis, you’ll also add Z99.2 (dependence on renal dialysis). If a kidney transplant is present, add Z94.0. These codes go after D63.1 in the sequencing order.
Example Coding Scenario
A 67-year-old man with CKD stage 4 due to type 2 diabetes presents with hemoglobin of 9.2 g/dL. His anemia is documented as secondary to CKD. He’s on hemodialysis three times per week.
Correct coding sequence:
- E11.22 — Type 2 diabetes mellitus with diabetic chronic kidney disease
- N18.4 — Chronic kidney disease, stage 4 (severe)
- D63.1 — Anemia in chronic kidney disease
- Z99.2 — Dependence on renal dialysis
Diagnostic Criteria: When Is Anemia Clinically Significant in CKD?
KDIGO (Kidney Disease: Improving Global Outcomes) guidelines define anemia in CKD as:
- Hemoglobin < 13.0 g/dL in adult males
- Hemoglobin < 12.0 g/dL in adult females
KDIGO recommends checking hemoglobin in all CKD patients — at least annually in stages 1–3a, twice yearly in stages 3b–5 without dialysis, and every 3 months in dialysis patients. These thresholds matter for coding because payers expect lab evidence supporting a D63.1 claim.
Key Lab Values to Document
| Lab Test | What It Tells You | Typical Range in CKD Anemia |
|---|---|---|
| Hemoglobin (Hgb) | Severity of anemia | Often 8–11 g/dL in moderate CKD |
| Serum Ferritin | Iron stores | <100 ng/mL suggests absolute iron deficiency in non-dialysis; <200 ng/mL in dialysis patients |
| Transferrin Saturation (TSAT) | Iron availability for red cell production | <20% suggests functional iron deficiency |
| Reticulocyte Count | Bone marrow response | Low or inappropriately normal (marrow can’t respond without EPO) |
| Serum Erythropoietin | EPO production capacity | Low or inappropriately normal relative to anemia severity |
| GFR (eGFR) | Kidney function stage | Anemia prevalence rises sharply below 45 mL/min/1.73m² |
A normocytic, normochromic pattern on the CBC (normal MCV, normal MCHC) is the classic finding in CKD anemia. If the MCV is low, suspect concurrent iron deficiency. If it’s elevated, consider B12 or folate deficiency — both of which would warrant additional codes.
Why CKD Causes Anemia: The Pathophysiology Behind D63.1
Damaged kidneys can’t produce adequate erythropoietin. That’s the primary driver. But several other mechanisms pile on:
- Erythropoietin deficiency: The peritubular fibroblasts in the renal cortex are the main EPO source. Fibrosis replaces these cells as CKD progresses.
- Functional iron deficiency: Even when iron stores are adequate, chronic inflammation traps iron in macrophages via hepcidin upregulation. The iron is there — the body just can’t use it.
- Chronic inflammation: Uremia creates a persistent inflammatory state. Elevated IL-6 and TNF-alpha suppress erythropoiesis and shorten red blood cell lifespan from the normal ~120 days to as few as 60–90 days.
- Uremic toxins: Accumulating waste products directly inhibit bone marrow red cell precursors.
- Blood loss: Dialysis patients lose an estimated 1–3 grams of iron per year through the dialysis circuit, blood draws, and GI bleeding from uremic platelet dysfunction.
Treatment Approaches (and Their Coding Implications)
Treatment documentation affects coding because it supports the clinical validity of D63.1 and may require additional procedure or drug administration codes.
Erythropoiesis-Stimulating Agents (ESAs)
Epoetin alfa (Epogen, Procrit) and darbepoetin alfa (Aranesp) are the mainstays. Current KDIGO guidelines recommend initiating ESAs when hemoglobin falls below 10 g/dL, with a target of 10–11.5 g/dL. The FDA black box warning cautions against targeting hemoglobin above 11 g/dL due to increased cardiovascular risk — a finding from the landmark CHOIR and TREAT trials.
For coding, ESA administration in an outpatient setting uses HCPCS codes (e.g., J0885 for epoetin alfa, J0881 for darbepoetin). These are separate from the diagnosis codes.
Iron Supplementation
Intravenous iron is preferred over oral iron in most CKD patients, especially those on dialysis, because uremia impairs gastrointestinal iron absorption. Common IV iron formulations include ferric carboxymaltose (Injectafer), iron sucrose (Venofer), and ferumoxytol (Feraheme).
Iron supplementation is typically initiated when TSAT is <30% and ferritin is <500 ng/mL. If concurrent iron deficiency anemia exists as a separate clinical problem, you may also code D50.9 (iron deficiency anemia, unspecified) alongside D63.1 — but only if the documentation supports both diagnoses as distinct entities.
Red Blood Cell Transfusions
Transfusions are reserved for severe or symptomatic anemia (generally hemoglobin <7 g/dL, or <8 g/dL with cardiovascular symptoms). In patients awaiting kidney transplant, transfusions are avoided when possible because they can cause HLA sensitization, making it harder to find a compatible donor.
Common Coding Mistakes to Avoid
These errors come up repeatedly in audits and claim denials:
- Sequencing D63.1 as the primary code: It’s a manifestation code. The CKD code (N18.x) must come first. Always.
- Using D63.1 without documented causation: The physician must explicitly connect the anemia to CKD in the clinical note. Inference isn’t enough for compliant coding.
- Confusing D63.1 with D64.9: D64.9 is “anemia, unspecified.” If the anemia is due to CKD, D64.9 is wrong and will likely be rejected or downgraded.
- Forgetting to update the CKD stage code: If the patient progresses from stage 3b to stage 4, the N18 code must be updated accordingly. The D63.1 stays the same, but the primary code changes.
- Omitting Z99.2 for dialysis patients: This status code is required when the patient is on chronic dialysis and directly affects reimbursement.
Related ICD 10 Codes You May Need
| Code | Description | When to Use |
|---|---|---|
| D63.1 | Anemia in chronic kidney disease | Anemia directly caused by CKD |
| D63.8 | Anemia in other chronic diseases | Anemia due to chronic disease other than CKD (e.g., rheumatoid arthritis, cancer) |
| D50.9 | Iron deficiency anemia, unspecified | Concurrent iron deficiency documented as separate condition |
| D64.9 | Anemia, unspecified | Only when no specific cause is identified — avoid if CKD-related |
| N18.1–N18.6 | CKD stages 1–5 and ESRD | Primary/etiology code sequenced before D63.1 |
| Z99.2 | Dependence on renal dialysis | Patient on chronic dialysis |
| E11.22 | Type 2 DM with diabetic CKD | When diabetes is the underlying cause of CKD |
Clinical Impact: Why Accurate Coding Matters Beyond Billing
CKD-related anemia isn’t a minor footnote. It’s associated with a 2- to 3-fold increase in mortality risk in CKD patients compared to those without anemia. Left ventricular hypertrophy, heart failure hospitalization, cognitive decline, and reduced exercise capacity are all directly tied to the severity of CKD anemia.
Accurate D63.1 coding drives appropriate resource allocation, triggers care management protocols in health systems, and supports quality metrics tracked by CMS. It also ensures patients get the ESAs and IV iron they need without prior authorization battles rooted in incorrect coding.
Frequently Asked Questions
Can I use D63.1 for anemia in acute kidney injury?
No. D63.1 is specifically for chronic kidney disease. Acute kidney injury (AKI) doesn’t have its own manifestation code for anemia. In AKI with anemia, you’d code the AKI (N17.x) and the anemia separately (likely D64.9 or a more specific anemia code if the cause is identified). If the patient has both AKI and underlying CKD, and the anemia is documented as due to the CKD, then D63.1 may still be appropriate.
What hemoglobin level is needed to code D63.1?
There’s no single hemoglobin cutoff required for coding D63.1. The code is based on the clinical diagnosis documented by the provider, not a specific lab value. That said, KDIGO defines anemia as Hgb <13 g/dL in men and <12 g/dL in women. Payers may question the code if hemoglobin is normal, so documentation of the clinical rationale is important.
Do I need to code both D63.1 and the CKD stage every encounter?
Yes, if the anemia is being addressed or is relevant to the encounter. D63.1 requires the underlying CKD code to be present on the same claim. Both codes should be reported at every visit where the conditions are evaluated, monitored, or treated.
What’s the difference between D63.1 and D63.8?
D63.1 is specifically for anemia caused by chronic kidney disease. D63.8 covers anemia associated with other chronic diseases — like cancer, rheumatoid arthritis, or chronic liver disease. If a patient has CKD and another chronic condition both contributing to anemia, the documentation should clarify which disease is primarily responsible. If the provider attributes it to CKD, use D63.1.
Is D63.1 valid for CKD stage 1 or 2 with anemia?
Technically, yes — if the provider documents that the anemia is due to CKD. However, anemia is uncommon in early CKD stages. Fewer than 5% of stage 1–2 patients are anemic. A reviewer may flag this combination for clinical plausibility, so make sure the documentation clearly explains why the anemia is attributed to early-stage CKD rather than another cause.
Key Takeaways
- D63.1 is the correct ICD 10 code for anemia caused by chronic kidney disease.
- It is a manifestation code — always sequence the CKD stage code (N18.x) first.
- Clinical documentation must explicitly link the anemia to CKD; coders cannot infer causation.
- Add Z99.2 for dialysis-dependent patients and Z94.0 for kidney transplant recipients.
- KDIGO defines CKD anemia as hemoglobin <13 g/dL in men and <12 g/dL in women.
- Treatment with ESAs and IV iron should be reflected in documentation to support medical necessity and the validity of the D63.1 code.
