ICD code T86.09 – Other bone marrow transplant complications

Key takeaways

T86.09 is for a named bone marrow transplant complication with no code of its own. T86.00 is unspecified, T86.01 rejection, T86.02 failure and T86.03 infection.

Graft-versus-host disease is D89.81-, never a T86.0x code.

T86.09 is a complete, billable five-character code for FY2026, so it never takes a 7th character such as XA.

Transplants of stem cells from peripheral blood or cord blood use T86.5, so confirm the graft source first.

A clean T86.09 claim shows a documented transplant, a named complication and a stated link between the two.

ICD-10 code T86.09 covers named complications with no code of their own

ICD-10 code T86.09 is the billable code for other complications of bone marrow transplant. Use it when the physician names a complication and no other T86.0 code describes it. It’s an “other specified” code, so it never stands in for a vague note.

The code sits in Chapter 19 of ICD-10-CM, under category T86 for complications of transplanted organs and tissue. You can browse the neighboring codes in our ICD-10-CM codes library. CMS lists T86.09 as valid and billable for FY2026, which began October 1, 2025.

Complications that commonly land here include:

• Engraftment syndrome
• Hepatic veno-occlusive disease, also called sinusoidal obstruction syndrome, with K76.5 added
• Transplant-associated thrombotic microangiopathy (TA-TMA), with M31.11 added
• Infusion reactions to the marrow product that no other code describes

A few conditions never belong here. Graft-versus-host disease (GVHD) is D89.81-, never a T86.0x code. Rejection is T86.01, failure is T86.02, and an infected transplant is T86.03. When the provider documents one of these, the more specific code wins.

The T86.0 family splits bone marrow complications five ways

Each sibling code answers one question: what went wrong with the graft? The table lines up all five, so you can rule codes out quickly.

Two of these sound alike but do opposite jobs. T86.00 means the type of complication is unknown. T86.09 means the type is known and has no code of its own. Mixing them up is easy, and payers notice when the record doesn’t match.

Stem cells from blood move the claim to T86.5

Before you open T86.0 at all, check where the graft came from. ICD-10-CM separates marrow grafts from stem cells collected any other way:

• Marrow harvested from the donor’s bone goes to T86.0-
• Stem cells collected from peripheral blood go to T86.5
• Stem cells from umbilical cord blood also go to T86.5

Many transplant teams now collect stem cells from blood rather than marrow. So a note that says “stem cell transplant” doesn’t prove a bone marrow code. Check the transplant record, and query the physician when the source isn’t stated.

T86.09 vs T86.00 and T86.01 turns on the physician’s wording

The right code depends on what the physician wrote, not on what the coder infers. Here’s how common phrases in the record map to the codes.

The rule of thumb is short. A named complication that isn’t rejection, failure or infection goes to T86.09. Documented rejection always goes to T86.01, and graft failure goes to T86.02.

The decision path below puts the graft check, the wording check and the partner codes in one view.

T86.09 needs a partner code, not a 7th character

T86.09 is complete at five characters. Many injury codes in Chapter 19 need a 7th character, but T86 codes take none. So T86.09XA isn’t a valid code, and a claim carrying it fails the payer’s front-end edits.

What T86.09 does need is a second code. The ICD-10-CM Official Guidelines describe a transplant complication with two codes. One is the T86 code, and the other names the specific condition. Common partners include:

• K76.5 for hepatic veno-occlusive disease
• M31.11 for transplant-associated thrombotic microangiopathy, which tells you to code the T86.0- complication first
• D89.81- for graft-versus-host disease
• D47.Z1 for post-transplant lymphoproliferative disorder

Here’s how that plays out. Say a patient is admitted two weeks after an allogeneic marrow transplant with TA-TMA, and the attending links it to the transplant. You’d report T86.09 first, then M31.11, because the M31.11 note asks for the T86 code first.

The guidelines also set a limit. A T86 code applies only when the complication affects the function of the transplanted tissue. A post-transplant problem unrelated to the graft gets its own code, without T86.09.

Documentation has to tie the complication to the transplant

Payers want the record to show a clear chain from the transplant to the complication. Before you code, confirm these five points.

• Transplant history: the record states the patient had a bone marrow transplant, allogeneic or autologous. Operative notes, the transplant discharge summary and problem list entries all count.
• Graft source: the record says whether the cells came from marrow, peripheral blood or cord blood. That choice decides between T86.0- and T86.5.
• Named complication: “Engraftment syndrome” is enough. “BMT complication” alone isn’t, unless a query answer names the type.
• Provider documentation: a physician, NP or PA with treating authority documents the complication. A nursing note on its own doesn’t carry the code.
• Causal link: the note says the complication is due to the transplant. “Engraftment syndrome following recent allogeneic BMT” does the job.

Sound medical billing compliance means this record is complete before the claim goes out. An addendum written after a denial is much harder to defend on audit.

Medicare pays for the care the complication needed

Medicare Part A covers most inpatient transplant admissions. Meanwhile, the MS-DRG depends on the principal diagnosis, the procedures and any complications, not on T86.09 alone.

Two groupings come up often in transplant care. MS-DRG 014 covers allogeneic bone marrow transplant stays. MS-DRG 803 is “Other O.R. procedures of blood and blood-forming organs with MCC” in MDC 16. Confirm the final grouping in the CMS MS-DRG definitions, since it reacts to the full code set.

Medical necessity works the same way. T86.09 alone doesn’t justify an inpatient stay. Instead, the severity and treatment of the named complication do, so the note has to show both. Commercial payers usually follow Medicare’s lead, though each one may add its own transplant rules.

Five mistakes that get T86.09 claims denied

T86.09 denials follow a predictable pattern. Catching these five before submission beats appealing them later.

• Missing transplant history: the payer can’t see the link to a prior transplant. Fix it by sending the transplant discharge summary or a problem list entry.
• Specificity mismatch: the claim says T86.09, but the record documents rejection or failure. Recode to T86.01 or T86.02, or query the provider.
• Invalid 7th character: the claim lists T86.09XA or T86.09XD, which don’t exist. Submit plain T86.09 instead.
• Wrong transplant type: a blood stem cell transplant was coded to T86.0-. Check the graft source and use T86.5 where it applies.
• No query on a vague note: the record only says “BMT complication,” yet T86.09 was assigned. Query during the stay, not after discharge.

Tracking denials by reason code shows which of these keeps coming back at your practice. A structured denial management workflow makes that pattern visible, so you can fix documentation where it starts. Pair it with a clean claim process to stop avoidable errors before submission.

Run this checklist before a T86.09 claim goes out

A short manual pass catches most T86.09 errors. Work through it with the chart open, because these are judgment calls for the coder.

• The graft was bone marrow, not stem cells from peripheral blood or cord blood.
• The physician named the complication, and it isn’t rejection, failure, infection or GVHD.
• The note links the complication to the transplant.
• The code reads T86.09, with no 7th character.
• A partner code names the condition, such as K76.5, M31.11 or D47.Z1.
• Any “code first” instruction is followed, as with M31.11.
• The transplant history is ready to send if the payer asks for records.

How claims management software keeps T86.09 claims moving

Transplant claims often stall on admin. A coder retypes codes from the chart, chases a missing member ID and then resubmits. Each round trip pushes back payment on a costly stay.

In Pabau’s claims management software, the claim pre-fills from the patient record. Its ICD-10-CM lookup library helps coders find T86.09 and its partner codes quickly. Pabau also checks that required claim fields are complete before the claim can be sent.

In the US, claims go out through Claim.MD, with eligibility checks and submission to thousands of US payers. Your coders still own the code choice. They just spend less time retyping and chasing missing fields.

Send transplant claims without the rework

Pabau pre-fills claims from the patient record, gives coders a searchable ICD-10-CM library and checks required fields before submission. Fewer claims come back for missing details.

Book a demo

Conclusion

T86.09 rewards coders who slow down at two points. The first is the graft source, since stem cells collected from blood belong to T86.5. The second is the physician’s wording, because only a named complication earns this code.

If your team sees transplant patients often, turn the checklist above into a standing query template. Queries sent during the stay cost far less than appeals after discharge. The trade-off is a little extra time with the physician up front, and it pays for itself.

Book a demo to see how Pabau pre-fills transplant claims and checks required fields before they reach the payer.

Continue your research

Need a framework for tracking transplant-related claim denials? Denial codes in medical billing explains common CARC denial reason codes and how to build an appeal workflow around them.

Submitting 837P claims for complex inpatient cases? Understanding the 837 file covers the electronic claim format, loop structure, and how ICD-10 codes map to the 837P transaction.

Verifying patient eligibility before a transplant-related admission? Insurance eligibility verification outlines the real-time eligibility process and what to confirm before complex claims are built.

Frequently asked questions