ICD-10 Code T86.01: Bone marrow transplant rejection

ICD-10 Code T86.01 is the billable ICD-10-CM diagnosis code for bone marrow transplant rejection, valid for FY2026 claims. It took effect on October 1, 2025, in the 2026 ICD-10-CM edition maintained by CMS and the National Center for Health Statistics.

T86.01 sits inside the T86 category, which covers complications of transplanted organs and tissue. Assign it only when the recipient’s immune system attacks transplanted bone marrow or hematopoietic stem cells. The physician has to write that rejection down, separately from failure and from graft-versus-host disease.

Found our content helpful?

Key takeaways

T86.01 is a billable ICD-10-CM code for bone marrow transplant rejection, effective October 1, 2025.

Five codes share the T86.0 subcategory, so read all five before you settle on T86.01.

T86.01 is distinct from T86.02 (transplant failure) and T86.00 (unspecified), and the physician must name rejection.

Graft-versus-host disease belongs to the D89.81- series and is never reported as T86.01.

The T86 category asks for additional codes covering GvHD, transplant-related malignancy (C80.2), and PTLD (D47.Z1).

ICD-10 Code T86.01: Code overview and billable status

ICD-10 Code T86.01 is a billable, specific ICD-10-CM diagnosis code valid for reimbursement submissions in FY2026. Below is the core reference data coders need at a glance.

Billable status means T86.01 can be submitted as a principal or a secondary diagnosis. It does not guarantee reimbursement. Payer medical necessity policy and the clinical documentation still have to support the diagnosis independently.

Clinical description: What is bone marrow transplant rejection?

Bone marrow transplant rejection is an immune-mediated process. The recipient’s immune system recognizes the transplanted hematopoietic cells as foreign and mounts a response to destroy them. Graft-versus-host disease runs the other way, with donor immune cells attacking the recipient’s tissues.

Rejection occurs most commonly in allogeneic transplants, where donor and recipient are different individuals. The recipient’s residual or recovering immune system generates cytotoxic T lymphocytes and antibodies against donor marrow antigens. That response either prevents engraftment or destroys engrafted cells after an initial success.

Clinical indicators that support a rejection diagnosis include:

• Failure of engraftment confirmed by bone marrow biopsy or chimerism studies
• Declining donor chimerism after initial engraftment
• Pancytopenia without an alternative explanation, such as infection or drug toxicity
• Physician documentation explicitly stating “bone marrow transplant rejection”
• Absence of graft-versus-host disease markers that would explain the clinical picture

For coding purposes, the distinction between rejection and failure rests entirely on physician documentation, not on laboratory values alone. A coder cannot assign T86.01 from declining blood counts without an explicit physician statement of rejection.

ICD-10-CM code hierarchy: Where ICD-10 Code T86.01 sits

Understanding the hierarchy helps coders navigate the T86 category and select the correct level of specificity. The ICD-10-CM classification places T86.01 under a layered parent structure.

T86.0 is a subcategory, not a billable code. Coders have to select a specific code at the T86.0x level. Code to the highest level of specificity the documentation supports, and T86.01 is that level when rejection is stated.

Sibling codes under T86.0: Bone marrow transplant complications

Five codes share the T86.0 subcategory, each covering a distinct clinical scenario. Picking the wrong one is the most frequent transplant coding error coders report.

When the record supports rejection alongside another complication, assign both codes in the correct sequence. Never fall back on an unspecified code where the documentation supports a more specific one. Our ICD-10-CM code index lists the neighboring T86 entries if you need to check one.

T86.01 vs T86.02: Rejection vs failure

Rejection and failure are clinically and mechanistically distinct, yet coders frequently assign T86.02 when T86.01 is correct, or the reverse. The clinical record is the deciding document.

If the physician’s note says “graft failure” but later clarifies “immune-mediated rejection,” query the physician or code to the most specific documented term. Never read ambiguous language in favor of a more specific code without physician clarification.

T86.01 vs graft-versus-host disease: Coding the difference

Graft-versus-host disease (GvHD) is coded using the D89.81x series, not under T86. The pathophysiology runs in the opposite direction from rejection, and the codes reflect that distinction.

GvHD subcodes under D89.81x separate acute (D89.810), chronic (D89.811), acute on chronic (D89.812), and unspecified (D89.813) presentations. The physician must document the GvHD type for the coder to select the appropriate subcode.

Using T86.01 for a GvHD presentation, or D89.81x for a rejection presentation, is a coding error that may attract audit scrutiny. The three possibilities separate cleanly once you line up the mechanism against the word in the note.

Documentation requirements for coding T86.01

The ICD-10-CM Official Guidelines require that a diagnosis code be supported by physician documentation in the medical record. For T86.01, that means the record must contain specific language confirming rejection.

Required elements in the medical record:

1. Transplant history: documentation that the patient previously received a bone marrow or hematopoietic stem cell transplant, with the date and donor relationship where available
2. Explicit rejection diagnosis: the attending or transplant physician must write rejection, graft rejection, or immune-mediated graft rejection
3. Clinical indicators: supporting evidence such as chimerism studies showing loss of donor cells, biopsy findings, or a workup that favors rejection
4. Ruling out alternative diagnoses: the record should say whether the presentation is rejection, failure, or GvHD, particularly where these overlap clinically
5. Status and treatment plan: documentation of the current management approach, which contextualizes whether the complication is active or resolved

Where the documentation is ambiguous, query the physician rather than default to an unspecified code. A note reading “possible rejection” does not support T86.01 in the outpatient setting. ICD-10-CM guidelines prohibit coding a possible diagnosis as though it were confirmed.

Coding guidelines and sequencing rules for T86.01

The ICD-10-CM Tabular List carries instructional notes at the T86 category level. Payers can deny a claim where those notes are not followed.

• Use additional code: the T86 category carries a use-additional-code note. Where the record documents graft-versus-host disease, add the applicable D89.81- code. Add C80.2 for a malignancy associated with the transplant, and D47.Z1 for post-transplant lymphoproliferative disorder.
• Sequencing as principal vs. secondary diagnosis: T86.01 may be sequenced as the principal diagnosis when the rejection is the main reason for the admission. It drops to a secondary diagnosis when the visit treats another condition and the rejection is managed alongside it.
• Seventh-character requirements: T86.01 does not require a seventh character for episode of care, unlike many other T-codes. The code is complete as submitted.

Sequencing errors are cheapest to catch before the claim leaves the practice. A scrubbing step that reads the T86 instructional note and checks for the additional codes will stop most of them at entry.

Common coding errors with ICD-10 Code T86.01

Five error patterns account for most T86.01 denials and audit flags. Each one has a documentation fix that costs less than an appeal.

• Defaulting to T86.00 when rejection is documented: if the physician has stated rejection, the unspecified code is wrong. T86.00 is reserved for records that genuinely cannot support a more specific assignment.
• Assigning T86.02 on clinical inference: pancytopenia or graft loss in the labs does not by itself mean failure. Where the physician has not documented failure, the coder cannot infer it. Query the provider.
• Using T86.01 for GvHD presentations: coders unfamiliar with the distinction sometimes reach for T86.01 when the presentation is graft-versus-host disease. GvHD takes a D89.81- code instead.
• Missing additional code instructions: assigning T86.01 alone when the record also documents GvHD, transplant-related malignancy, or PTLD leaves the claim incomplete.
• Coding rejection as principal when it is not: where the admission treats an unrelated condition, T86.01 is a secondary code. Missequencing can affect DRG assignment and reimbursement.

Tracking which denial reasons recur on T86.01 claims points to the upstream documentation problem causing them.

A run of identical denials usually traces back to one phrase the transplant team keeps writing, and a short education session fixes it. Root-cause work of this kind is what denial management in healthcare means in practice, rather than appealing claims one at a time.

Stem cell transplant rejection and T86.01: Is there a difference?

T86.01 applies to rejection following both classic bone marrow transplantation and hematopoietic stem cell transplantation. That includes peripheral blood stem cell and cord blood transplants. The ICD-10-CM classification does not distinguish between these procedural sources at the T86.01 level.

Clinically, rejection in allogeneic transplantation follows the same immune-mediated pathway whatever the source. The recipient’s reconstituting immune system identifies donor hematopoietic cells as non-self and attacks them.

Whether the cells came from marrow, from peripheral blood after mobilization, or from cord blood, the coding is the same once rejection is documented.

The documentation requirement does not change with the cell source. The physician must state rejection, rather than failure or a generic complication. Practices treating haploidentical or mismatched recipients see rejection more often, so those records deserve a closer read.

The billing team’s claims management software should hold that distinction at the coding stage. Doing so protects both revenue integrity and audit readiness.

How Pabau keeps transplant complication claims clean

Most hematology billing teams catch a T86.01 problem after the denial arrives. The coder reads the note in one system and submits the claim from another. The missing D89.81- code only surfaces when the payer sends the claim back.

Practice management software like Pabau keeps the clinical note and the claim in one record. The diagnosis the physician documented is the diagnosis attached to the charge. A coder checking T86.01 can read the rejection statement without opening a second system.

Claims go out electronically with the code set the note supports, and denials come back tagged by reason and by code. That gives the billing lead a count of how many T86.01 claims failed, and why, instead of a stack of individual appeals.

Struggling with transplant complication coding workflows?

Pabau’s claims management software helps hematology and oncology practices submit clean transplant complication claims, track denials by code, and keep documentation audit-ready. See how it works for your team.

Book a demo

Conclusion

T86.01 turns on one word in the medical record. Where the physician writes rejection, the code is right. Where the note says failure, or describes GvHD, it is the wrong code.

So the work worth doing sits upstream of the claim. A short query to the transplant physician, sent before the encounter is coded, settles the question the payer would otherwise settle for you. Add the D89.81-, C80.2 and D47.Z1 codes the record supports, and the claim carries its own justification.

The trade-off is a few minutes of query time against a rework cycle measured in weeks. Book a demo to see how Pabau ties the rejection statement in the note to the code on the claim.

Continue your research

Need a primer on medical billing fundamentals? What is medical billing covers the end-to-end claim lifecycle from documentation through payment posting.

Want to understand how clearinghouses validate ICD-10 claims? Medical claims clearinghouse guide explains how payer edits catch sequencing errors before submission.

Looking to reduce transplant claim denials systematically? Denial management in healthcare outlines root-cause analysis approaches for persistent claim denial patterns.

Frequently asked questions