ICD code D72.829 – Leukocytosis, unspecified

Key takeaways

D72.829 is the billable ICD-10-CM code for elevated white blood cell count, unspecified, and it’s valid for FY2027.

Use it for a raised WBC count with no specified cell line or cause, whether the note says “leukocytosis” or “elevated WBC.”

D72.828 is only for a specified elevation not classified elsewhere, while D72.820 to D72.825 cover named subtypes such as lymphocytosis and bandemia.

The provider must state the finding’s clinical significance, because a lab value alone doesn’t support the code.

Pabau handles eligibility checks, electronic claim submission and ERA remittances through its Claim.MD integration.

ICD-10 code D72.829 at a glance: Raised WBC, no named cell line

ICD-10 code D72.829 is the billable code for an elevated white blood cell count when the record names no cell line and no cause. It appears in the FY2027 ICD-10-CM code files CMS publishes for October 1, 2026 onward.

The table below gives the identifiers coders check most often.

Leukocytosis codes to D72.829 only when no cell line is named

Leukocytosis is a white blood cell (WBC) count above the laboratory’s reference range, usually found on a complete blood count (CBC). In adults, that range commonly tops out around 11,000 cells/µL.

In D72.829, “unspecified” means the record doesn’t name which cell line is raised or classify the elevation any further. The Alphabetic Index sends both “Leukocytosis” and “Elevated, white blood cell count” to D72.829. So the provider’s choice between those two phrases doesn’t change the code.

That makes the code a holding place for what the chart knows today. It isn’t the right choice when the note names a subtype with its own code, such as lymphocytosis (D72.820) or bandemia (D72.825).

It also drops out when a confirmed condition explains the raised count. Findings routinely associated with a confirmed disease aren’t coded separately (Section I.B.5).

Inclusions and exclusions: Where the D72 notes send other counts

These are the FY2027 tabular notes for D72.829 and the headings above it. Excludes1 notes on a parent code carry down to D72.829 as well.

Two notes catch coders out. The D72 category’s Excludes1 note lists basophilia and points it to D72.824, so a documented basophilia codes there and never to D72.829. The other is eosinophilia, because a raised eosinophil count goes to D72.1-, never to D72.82-.

Leukemoid reaction (D72.823) isn’t an Excludes1 note for D72.829. It’s a sibling code in D72.82, so documentation that names a leukemoid reaction simply codes there.

D72.829 vs D72.828: Specificity picks the code, not wording

The choice turns on how specific the documentation is about the cell line or the cause. Whether the provider wrote “leukocytosis” doesn’t decide it.

Work down the table in order. If the note names a subtype, code the subtype. If it describes a specified elevation that no subtype code covers, D72.828 applies. If it describes a raised count and no more, D72.829 is correct. Query the provider when the differential points to a subtype the note doesn’t name.

The decision path below runs the same checks in the order a coder meets them, starting with the provider’s statement.

Three charts that support D72.829, and how to sequence each

All three notes below support D72.829. What changes between them is whether it’s listed first or second.

• Scenario 1, abnormal CBC with workup ordered: A patient’s CBC shows a WBC of 13,500 cells/µL. The physician writes “elevated WBC, repeat CBC with differential,” and no cause is confirmed. D72.829 applies even though the note never says “leukocytosis.” List it first if the raised count is the focus of the visit.
• Scenario 2, incidental finding on pre-operative labs: Pre-surgical bloodwork shows a raised WBC count. The surgeon notes “incidental leukocytosis, will monitor,” and surgery goes ahead. The condition that prompted surgery comes first, and D72.829 is a secondary code.
• Scenario 3, follow-up for a known raised count: A patient returns to review a repeat CBC after an earlier raised result. The physician documents “leukocytosis, etiology under investigation.” D72.829 is first-listed because the raised count is the reason for the visit.

Sequencing note: Outpatient and physician-office coding follows Section IV of the guidelines, which uses the first-listed diagnosis. That’s the condition chiefly responsible for the visit. “Principal diagnosis” is the inpatient term from Section II. Once a cause is confirmed, code the cause, and drop D72.829 if the raised count is integral to it.

How a D72.829 claim moves from CBC to payment

D72.829 rarely travels alone. Its job is to justify a visit or a lab line, and the claim follows a predictable path for an outpatient encounter.

1. The CBC results. The lab flags a WBC count above its reference range, and the result lands in the chart.
2. The provider assesses it. The note names the raised count, says it matters and sets a plan, such as a repeat CBC with differential.
3. The coder assigns the code. With no subtype or confirmed cause documented, D72.829 goes in box 21 of the CMS-1500 or its 837P equivalent.
4. Each line points to it. The diagnosis pointer in box 24E links D72.829 to every line it supports, such as the visit or an in-office test.
5. The payer runs its edits. Medicare checks lab lines against the Blood Counts NCD or a local LCD, while commercial plans apply their own policy.
6. The remittance comes back. The 835 ERA shows the payment or a denial reason code, which tells your team what to fix.

Whoever bills the repeat test, it usually goes out as 85025 with a differential or 85027 without one. Make sure the lab order carries D72.829 too, or the lab’s own claim can stall on medical necessity.

Four things the note needs before D72.829 holds up

A lab value on its own doesn’t support D72.829. Abnormal findings are coded only when the provider indicates their clinical significance (Section III.B).

These four documentation elements support clean claim submission with D72.829:

1. A documented raised WBC count: The CBC result, typically above 11,000 cells/µL in adults, appears in the record or is referenced in the note.
2. A provider statement about the finding: The assessment names the raised count and shows it’s clinically significant. “Leukocytosis,” “elevated WBC” and similar wording all support D72.829, so the specific word isn’t required.
3. No named subtype or confirmed cause: The note doesn’t name a cell line with its own code. No confirmed condition explains the elevation either, or that condition gets coded instead.
4. A plan tied to the finding: Further workup, monitoring or treatment shows the finding shaped care. That supports medical necessity, which many payer policies look for.

HCC coding context: D72.829 isn’t a payment HCC in the CMS-HCC risk adjustment model. Mappings change, so confirm against the current one before relying on that. In risk-adjusted settings, still apply the MEAT criteria (Monitor, Evaluate, Assess, Treat) to show the finding was addressed. When documentation is ambiguous, follow AHIMA and ACDIS query practice rather than coding by inference.

Three guideline sections govern how D72.829 is used

Three parts of the FY2027 ICD-10-CM Official Guidelines for Coding and Reporting govern how D72.829 is assigned and sequenced. Sound ICD-10 billing compliance means applying all three consistently.

• Section I.B.4-5, signs and symptoms: Signs and symptoms are acceptable codes when no related definitive diagnosis has been established. Findings routinely associated with a confirmed disease aren’t coded separately, so a raised count explained by a documented infection usually isn’t.
• Section I.B.18, unspecified codes: Sign, symptom and unspecified codes have acceptable, even necessary, uses. Each encounter is coded to the level of certainty known, so D72.829 is accurate when no cell line is named.
• Sections II and IV, sequencing: Inpatient coding selects a principal diagnosis (Section II). Outpatient and physician coding lists first the condition chiefly responsible for the visit (Section IV).

The CMS ICD-10 codes page publishes the annual coding guidelines as a free download. Check D72.829’s tabular notes each October, when the new code year takes effect.

Before you submit: A D72.829 checklist

Run through these six checks before the claim goes out. Each one heads off a denial covered further down.

• The CBC result is in the chart or quoted in the note.
• The provider’s assessment calls the raised count significant, in whatever words they use.
• The differential, if one was run, doesn’t point to a subtype the note should name.
• No confirmed diagnosis on this encounter explains the elevation.
• D72.829 is listed first only when the raised count drove the visit.
• The diagnosis pointer links D72.829 to each line it supports, and the lab order carries it as well.

Payers judge D72.829 by the service it supports

D72.829 is a billable terminal code, but payers don’t all treat it the same way. Submission requirements vary by payer type and jurisdiction.

Knowing the medical billing fundamentals matters here, because “unspecified” codes can draw closer documentation review.

• Medicare: CMS has no National Coverage Determination (NCD) for D72.829 as a standalone diagnosis. Coverage for labs ordered for it follows the lab NCD, such as NCD 190.15 (Blood Counts), or a Local Coverage Determination (LCD). LCDs are issued by Medicare Administrative Contractors (MACs), so covered-diagnosis lists vary by jurisdiction.
• Commercial payers: Check the Medicare LCD where the plan follows it, or the commercial payer’s own medical policy or covered-diagnosis list. Do it for the accompanying lab CPT codes before submission.
• Prior authorization: D72.829 doesn’t trigger prior authorization on its own. Where it applies, prior authorization is linked to the procedure or service billed, so check each payer’s policy for specialty services ordered.

Pabau’s billing software connects to Claim.MD, so practices run eligibility checks and submit CMS-1500/837P claims electronically. ERA remittances come back the same way, so payments and denial reasons reach your team. Code selection stays with your coders.

Common D72.829 mistakes that end in denials

D72.829 denial patterns are predictable, and the same root causes appear across payer types. Sound denial management workflows catch most of them before submission.

When appealing, attach the CBC result and the relevant part of the provider’s note. Show that no more specific code applied at that encounter. With Pabau’s claims tools for billers, ERA remittance data comes back through Claim.MD, so your team sees each denial reason against its claim.

Each denial also carries a claim adjustment reason code. Our guide to medical billing denial codes explains the common ones and how to respond to each.

Sibling codes in D72 that sit beside D72.829

D72.829 is one of several terminal codes in subcategories D72.81 and D72.82. Together they cover decreased and elevated WBC counts, with named subtypes for each direction.

The CDC/NCHS ICD-10-CM web tool lets coders browse the D72 tabular list by fiscal year. Use it to confirm descriptors, inclusion terms and exclusion notes against the current release.

How Pabau keeps D72.829 claims moving

Choosing between D72.829 and its siblings is the coder’s call. Getting the claim paid also depends on eligibility, clean submission and hearing quickly when a payer pushes back.

Pabau handles those steps through Claim.MD. Your team runs eligibility checks before the visit, then submits CMS-1500/837P claims electronically.

ERA remittances come back through Claim.MD, so payments and denial reasons sit against each claim. Your team can then decide what to correct and resubmit, without chasing paper remittances.

Manage D72.829 claims without the rework cycle

Pabau’s Claim.MD integration runs eligibility checks, submits CMS-1500/837P claims electronically and brings ERA remittances back to each claim. See how it fits your billing workflow.

Book a demo

Conclusion

Treat D72.829 as the code for what the chart knows today. A raised count with no named cell line and no confirmed cause belongs here, whatever word the provider chose.

The trade-off is that unspecified codes invite a second look. A clear statement of significance and a plan tied to the finding answer that look before a payer asks. Once a differential names a cell line, move to the subtype code at the next encounter.

Book a demo to see how Pabau runs eligibility checks, sends 837P claims and brings ERA remittances back to each D72.829 claim through Claim.MD.

Continue your research

Need a full picture of how clearinghouse submission works? Pabau’s Claim.MD clearinghouse guide walks through how electronic claims reach payers and how remittances come back.

Getting denials on lab-linked claims? Denial codes in medical billing explains the most common CARC denial codes and how to respond to each one.

Want to understand ERA remittance data? Electronic remittance advice explained covers how 835 ERA files carry denial reasons back to your practice management system.

Frequently asked questions