ICD code T86.00 – Unspecified bone marrow transplant complication

Key takeaways

T86.00 is the ICD-10-CM code for an unspecified complication of bone marrow transplant, used when the complication type is undocumented.

T86.00 is not a rejection code. Rejection has its own code, T86.01, alongside failure (T86.02) and infection (T86.03).

Do not report Z94.81 with T86.00. An Excludes1 note at Z94 blocks that pair for the same transplant.

T86.0 without a fifth character is a non-billable header and is rejected at adjudication.

Pabau’s claims management software validates ICD-10-CM assignment before submission, so transplant claims reach payers with a complete code set.

ICD-10 code T86.00: Definition and code details

ICD-10 code T86.00 is the billable ICD-10-CM diagnosis code for an unspecified complication of bone marrow transplant.

It is the catch-all within the T86.0 subcategory. Use it when the record confirms a complication of a bone marrow or hematopoietic stem cell transplant but never names it. The code sits in Chapter 19 of ICD-10-CM, which covers injury, poisoning, and certain other consequences of external causes (S00–T88).

T86.00 carries no clinical meaning of its own beyond “something went wrong with the graft, and the note does not say what.” That distinction matters on every claim. Four sibling codes carry the specific meanings — rejection, failure, infection, and other complications.

Verify current-year billable status against the CDC/NCHS ICD-10-CM web tool before submitting claims for any fiscal year. CMS releases annual tabular list updates each October.

What T86.00 covers and what it does not

T86.00 covers an encounter where a complication of a bone marrow or hematopoietic stem cell transplant is documented, but the note never names the complication. Three situations appropriately land on T86.00:

• The note records a “bone marrow transplant complication” with no further qualifier
• The record shows the graft is behaving abnormally, yet no clinician commits to rejection, failure, or infection
• Treatment is started on suspicion of a graft problem before any diagnosis is reached, and the encounter closes without one

The code does not cover the following scenarios. Each one has its own billable code, and each one outranks T86.00 whenever the documentation supports it:

• Rejection: when the note documents that the host is rejecting the graft, use T86.01 (bone marrow transplant rejection)
• Transplant failure: when marrow fails to engraft or loses function, use T86.02
• Post-transplant infection: when an infection is documented as a complication of the transplant, use T86.03
• Any other named complication: a documented complication that is none of the above falls under T86.09
• Graft-versus-host disease: GVHD is a biologically distinct process coded under D89.810–D89.813 in Chapter 3 — never under T86.00

Rejection and GVHD run in opposite directions. In rejection, the host attacks the donor cells. In GVHD, the donor immune cells attack the host. Conflating the two on a claim is both a coding error and a documentation accuracy problem. The CMS ICD-10 coding guidance expects a transplant complication code to match the documented clinical event.

T86.00 in the ICD-10-CM hierarchy

Knowing where T86.00 sits in the ICD-10-CM hierarchy prevents the most common claim error on this family. That error is submitting the non-billable parent T86.0 in place of T86.00. The ladder from chapter to specific code runs as follows:

T86.0 with no trailing digit is a header code, and it will be rejected as invalid. Every claim must carry a five-character code from the family. Practice systems that autofill parent codes create this error silently, so verify the full code string before submission.

Related and sibling codes you must know

T86.0 splits into five five-character codes, and four of them are more specific than T86.00. Coders who work bone marrow transplant encounters regularly need to distinguish the following:

Documentation specificity separates T86.00 from its four siblings, and clinical severity plays no part. A minor documented infection still goes to T86.03. A life-threatening but unnamed graft problem still goes to T86.00. The ladder below shows how a single line in the record moves the encounter between the five codes.

Why T86.00 is often mistaken for a rejection code

Coding cheat sheets, EHR pick lists, and online code lookups often label T86.00 as “bone marrow transplant rejection.” The mislabel has a traceable origin in a different classification.

The World Health Organization’s international ICD-10 is the base classification used outside the United States. Its four-character T86.0 is titled “Bone-marrow transplant rejection and graft-versus-host reaction or disease.” Beneath that parent, WHO ICD-10 does carry its own five-character T86.00, and there it means bone-marrow transplant rejection. That code, with that meaning, is where the mislabeling starts.

ICD-10-CM reuses the same five characters for something else. When the United States built its clinical modification, it subdivided T86.0 into the five codes in the table above and narrowed rejection to T86.01. Reference tools that mapped WHO titles onto ICD-10-CM codes carried “rejection” across to a code that no longer means it.

Any US claim, audit, or risk-adjustment submission follows the ICD-10-CM tabular list. There, T86.00 means the complication type was not documented, and nothing more.

When to use T86.00 vs a more specific complication code

T86.00 is appropriate only when the documentation confirms a bone marrow transplant complication and stops short of naming it. The decision logic runs as follows:

1. Review all encounter documentation — attending notes, transplant coordinator notes, pathology and biopsy reports, and any referenced prior visit records. Complication language can appear anywhere in the record.
2. Look for a named complication — rejection moves the encounter to T86.01, graft failure or non-engraftment to T86.02, and a transplant-related infection to T86.03.
3. Check whether the complication is named but uncommon — a documented complication that fits none of those three belongs to T86.09, not to T86.00.
4. Separate GVHD from the T86 family — graft-versus-host disease is coded from D89.810–D89.813. The T86 tabular note asks for it as an additional code, not a substitute.
5. Query the provider if the documentation is ambiguous — a note reading “possible rejection” or “rejection versus failure” calls for a provider query. Reaching for T86.00 to avoid the query is not a compliant practice.
6. Assign T86.00 only once the steps above come back empty — then add codes for any associated manifestation the record documents. Acute kidney injury, for example, takes N17.x.

The AAPC ICD-10-CM code reference restates the ICD-10-CM Official Guidelines on this point. They discourage routine use of unspecified codes where the documentation supports a more specific one. T86.00 has a legitimate clinical use, because records genuinely do close without a named complication. It should never become a default coding shortcut.

Coding guidelines and sequencing rules

ICD-10-CM Official Guidelines Section I.C.19 governs transplant complication coding. The sequencing rule for T86.00 follows the broader transplant complication framework: when the transplant complication is the reason for the encounter, it sequences first.

• Principal diagnosis: T86.00 sequences as the principal diagnosis when an unspecified bone marrow transplant complication is the primary reason for the admission or outpatient encounter
• What the T86 tabular note says: the “use additional code” instruction at category T86 names three companions. They are graft-versus-host disease (D89.81-), malignancy associated with organ transplant (C80.2), and post-transplant lymphoproliferative disorder (D47.Z1). Z94.81 is not among them
• Z94.81 is excluded, not required: category Z94 carries an Excludes1 note for complications of transplanted organ or tissue. Bone marrow transplant status is not reported alongside T86.00 for the same graft
• Additional manifestation codes: if the complication has produced an associated condition, such as acute kidney injury documented as a consequence, assign the appropriate additional code
• When another condition is principal: the patient may present for something unrelated to the transplant, with the complication incidental. T86.00 then sequences after the primary condition
• External cause codes: T86.00 does not require a Y-series external cause code, because the T86 transplant complication codes are self-contained

Practices can route transplant complication claims electronically through Claim.MD, the US clearinghouse that practice management software like Pabau integrates with. It validates ICD-10-CM codes against current payer edits before submission. Invalid code strings and conflicting pairs get flagged before the claim reaches the payer.

Codes reported alongside T86.00

A single transplant encounter can generate more than one code, and the T86 tabular note names the three companions explicitly. Each is reported in addition to the T86 code when the record documents it.

• Graft-versus-host disease (D89.81-): D89.810 acute, D89.811 chronic, D89.812 acute on chronic, and D89.813 unspecified. GVHD and an unspecified graft complication are not mutually exclusive events, so both are coded when both are documented
• Malignancy associated with organ transplant (C80.2): reported when a post-transplant malignancy is documented, with an additional code identifying the malignancy itself
• Post-transplant lymphoproliferative disorder (D47.Z1): PTLD has its own code and is not folded into T86.00 or T86.09

ICD-10-CM allows codes from different chapters to be reported together, and no Excludes1 note prevents the concurrent use of T86.00 and D89.8xx. The one pairing to avoid is Z94.81, which Chapter 21 excludes from any encounter already carrying a T86 complication code.

Payer requirements and medical necessity documentation

Medicare and commercial payers treat unspecified transplant complication codes with elevated scrutiny. T86.00 is billable, but its “unspecified” qualifier signals to payers that documentation may be incomplete. That can trigger a medical necessity review or an automated audit flag. Payers generally expect the following before a T86.00 claim clears without challenge:

• Transplant date and type: documentation must confirm the original transplant date and whether it was allogeneic (donor marrow) or autologous (the patient’s own stem cells). Allogeneic transplants carry a higher complication risk and are the more common context for T86.0x codes.
• Evidence that a complication occurred: a laboratory, imaging, or pathology finding, or a treating clinician’s explicit statement that the graft is complicated. A patient simply having transplant history is not a complication, and it belongs to Z94.81 instead.
• Treating physician’s narrative: the note should state what was observed, what was ruled out, and how the patient was treated. That supports medical necessity even where the complication is never named.
• A clean code set: the five-character code, no Z94.81 alongside it, and additional codes for GVHD, malignancy, or PTLD where the record documents them.

Pre-submission edits for T86.00 encounters can be built into claims software for practices. Those edits flag a missing document, or an excluded code pair that has slipped onto the claim. Catching either one before adjudication is what keeps payer touchbacks off the billing team’s desk. For the statutory framework, CMS Physician Fee Schedule guidance sets out the medical necessity documentation standards that apply to transplant complication encounters.

Documentation for a transplant encounter runs deeper than code selection alone. Every element of the encounter record should be present and internally consistent before the claim goes out. That runs from the transplant history through to the plan of care.

Common claim denial reasons for T86.00

ICD-10 code T86.00 claims are denied more often than the specific T86.0x codes, because the unspecified qualifier attracts additional payer scrutiny. Five denial triggers appear most consistently in transplant coding audits:

1. Submitting T86.0 instead of T86.00 — the non-billable header code is rejected at adjudication. Autofill in the practice system or a coder shortcut is the usual cause, and a pre-submission edit check catches it.
2. Reporting Z94.81 alongside T86.00 — the Excludes1 note at Z94 makes the pair invalid for the same graft. Payer edits that enforce Excludes1 relationships return the claim rather than pay it.
3. Coding T86.00 when the note names the complication — an auditor who finds “rejection” or “graft failure” in the record recodes the claim. The payer then recoups the difference.
4. Unspecified code flagged for medical necessity audit — some payers run pre-payment review edits on unspecified transplant complication codes. These generate documentation requests rather than outright denials, but the claim does not pay until the practice responds.
5. Incorrect sequencing — when another condition should be the principal diagnosis and T86.00 sequences first in error, the claim may be denied or downgraded. Sequencing drives DRG assignment in inpatient settings.

Reviewing the denial codes a payer returns helps coders match each failure mode to its CARC or RARC reason code. Appeals can then target the specific documentation weakness that caused the denial. Knowing which pattern a T86.00 submission is most likely to trigger is what makes that appeal quick.

Documentation tips for providers

Providers who name the complication let coders reach T86.01, T86.02, or T86.03 instead of falling back on T86.00. That single habit lowers audit exposure and payer friction across the whole transplant caseload. Four documentation practices make the difference:

• Name the complication in the assessment: state whether the graft is being rejected, has failed to engraft, or is infected. “Bone marrow transplant complication” on its own forces a coder to T86.00.
• Reference the supporting result: linking the pathology, culture, or chimerism result to the clinical statement strengthens the medical necessity argument. “Graft failure confirmed on marrow biopsy dated [date]” is sufficient.
• Record the original transplant date and donor type: most payers require these facts, and follow-up notes often omit them. Including them in the assessment or HPI saves the billing team a documentation chase.
• Distinguish rejection from GVHD explicitly: document each separately when both are present. Coding Clinic guidance from the American Hospital Association treats them as distinct entities requiring codes from separate chapters.

Strong documentation does more than improve coding specificity. It underpins the revenue cycle integrity that payers audit when transplant claims are pulled for medical necessity review. Coders should raise a provider query whenever a note describes a graft problem without naming it. Defaulting to T86.00 to close the encounter is the shortcut that later costs the practice a recoupment.

How Pabau keeps transplant complication codes accurate at submission

Most practices catch a T86.00 problem after the remittance arrives. The claim goes out with a header code, an excluded Z94.81 pairing, or an unspecified code the note could have supported more precisely. The billing team learns about it weeks later, through a denial or an audit letter.

Practice management software like Pabau moves that check to the point of coding. Diagnosis codes are held against the current ICD-10-CM tabular list, so an invalid four-character string never reaches a claim form. The clinical note stays attached to the encounter the coder is working from. Claims then leave through the Claim.MD clearinghouse integration, which runs payer edits before submission rather than after it.

A transplant-treating practice sees a shorter denial list and a quicker appeal when one does land. The documentation supporting the code is already filed against the encounter. Coders spend their time on provider queries that improve specificity instead of on rework.

Catch coding errors before the claim leaves the practice

Pabau validates ICD-10-CM assignment, keeps clinical documentation attached to the encounter, and submits electronically through Claim.MD, so transplant-treating practices see fewer denials and faster payment.

Book a demo

Conclusion

ICD-10 code T86.00 fills a narrow slot: a bone marrow transplant complication that the record confirms but never names. Treat it as the code of last resort within T86.0, reached only after rejection, failure, and infection have each been ruled out of the documentation.

The two most preventable errors sit either side of the code itself. Submitting the non-billable parent T86.0 gets the claim rejected outright. Attaching Z94.81 to a T86.00 encounter breaks an Excludes1 rule that payer edits increasingly enforce. Both are pre-submission checks, not appeals problems.

Pabau supports pre-submission ICD-10 validation, so T86.00 claims reach payers with a complete code set and their documentation links already in place. To see how Pabau handles transplant and specialty billing workflows end to end, book a demo.

Continue your research

Need a framework for managing claim denials systematically? Denial management in healthcare covers the end-to-end workflow for identifying, appealing, and preventing recurring denials.

Want to understand how clearinghouses validate ICD-10 codes before submission? How the Claim.MD clearinghouse works explains real-time eligibility checks and claim edit logic in plain terms.

Looking for guidance on building clean claims from the start? What makes a clean claim outlines the elements payers expect to see on every submitted claim, from code sets to supporting documentation.

Frequently asked questions about ICD-10 code T86.00