ICD code T86.5 – Complications of stem cell transplant

Key takeaways

T86.5 is a billable ICD-10-CM code for complications of stem cell transplant from peripheral blood or umbilical cord, with no subcodes by complication type.

Use T86.5 when physician documentation names ‘stem cell transplant’ as the prior procedure. A documented ‘bone marrow transplant’ routes to the T86.0- subcodes instead.

GVHD is expected only after allogeneic transplants. An autologous HSCT claim coded with GVHD is likely to trigger a payer audit.

Pabau’s claims management software integrates with Claim.MD to submit, track, and reconcile transplant complication claims against Medicare and commercial payer requirements.

ICD-10 Code T86.5: Definition and billable status

ICD-10 Code T86.5 is the official diagnosis code for complications of stem cell transplant, valid and billable for fiscal years 2025, 2026, and 2027. ICD-10-CM is maintained by the Centers for Medicare and Medicaid Services (CMS) and the National Center for Health Statistics (NCHS).

The code sits within the T80-T88 range (complications of surgical and medical care, not elsewhere classified) inside Chapter 19. Its parent category is T86 (complications of transplanted organs and tissues), which covers every transplanted organ type from kidney through liver.

What T86.5 covers: Included conditions

T86.5 applies to complications of a hematopoietic stem cell transplant (HSCT) when the physician’s documentation uses the term “stem cell transplant.” A complication of a bone marrow transplant codes to T86.0- instead.

The CDC/NCHS ICD-10-CM tabular list gives two inclusion terms for this code:

• Complications from stem cells from peripheral blood
• Complications from stem cells from umbilical cord

T86.5 has no subtypes for failure, rejection, infection or graft-versus-host disease (GVHD). Those details are captured with secondary codes under the “use additional code” instruction, with GVHD coded from D89.81-.

GVHD is the most clinically significant complication of allogeneic HSCT. Autologous HSCT does not produce GVHD under normal circumstances, so a GVHD code on an autologous transplant claim is a payer audit risk.

Includes notes, excludes notes, and code also instructions

The T86 category and the T86.5 code carry official instructional notes that govern what can and cannot be coded alongside them. Coders must read these before assigning T86.5 on any claim.

For the T86 category, the tabular list tells coders to use additional codes for any applicable transplant complications, such as graft-versus-host disease. Secondary codes also identify the infectious organism and the nature of a failure or rejection. Always verify the current year’s instructional notes in the active ICD-10-CM tabular list from the AAPC codify tool or the official CMS release.

T86.5 vs T86.09: Key differences for coders

T86.5 covers complications of stem cell transplant. T86.09 covers other complications of bone marrow transplant (T86.0- covers unspecified, rejection, failure, infection and other). The two codes describe distinct procedures, and physician documentation language determines which applies.

The key audit point: a bone marrow transplant codes to T86.0-, and a stem cell transplant codes to T86.5. When the record mixes “bone marrow transplant” and “stem cell transplant”, query the physician before you assign either code. The diagram below maps each documentation term to the code it supports.

Neighboring codes in the T86 category

The full T86 category covers complications of every major transplant type. Understanding where T86.5 sits helps coders recognize when to step to a more specific code and when T86.5 is the right level of specificity.

T86.5 stands out within this category because it has no subcodes by complication type. The kidney and heart ranges, by contrast, break out failure, rejection, and infection separately. Use the “use additional code” instruction to provide that specificity through secondary diagnosis codes.

How to assign T86.5 correctly: Documentation requirements

Correct T86.5 assignment depends on six documentation elements. A record missing any of these is a denial risk before the claim reaches the payer. Coding teams who know the basics of medical billing can turn the list below into a pre-submission checklist.

1. Physician documentation names “stem cell transplant” as the prior procedure. “Hematopoietic stem cell transplant,” “HSCT,” “peripheral blood stem cell transplant,” or “PBSCT” all qualify. “Bone marrow transplant” alone routes to T86.0-.
2. Complication type is identified in the record (failure, rejection, infection, or other specified). Unspecified complication is permissible but reduces coding accuracy and may affect DRG assignment.
3. Causal relationship is explicit. The physician must document that the complication is attributable to the transplant, not an incidental condition. “Infection in HSCT patient” is weaker than “post-HSCT opportunistic infection.”
4. Secondary codes are assigned per the “use additional code” instruction. That means the causative organism for infections and immunosuppressant adverse effect codes where applicable. When GVHD is documented after an allogeneic transplant, add the specific code from D89.81- (D89.810, D89.811, D89.812 or D89.813 for unspecified).
5. Z94.84 (stem cell transplant status) is assigned per instructional notes when applicable. Verify the current tabular instruction, as the relationship between Z94.84 and T86.5 on the same claim can vary by payer policy.
6. Sequencing follows UHDDS rules. T86.5 is principal when the complication is the reason for the encounter. It is secondary when the patient was admitted for treatment of the underlying malignancy and the complication is also managed.

Allogeneic vs autologous stem cell transplant: Coding impact

T86.5 applies to both allogeneic and autologous HSCT complications. The distinction matters for secondary code assignment, not for the primary T86.5 assignment itself.

Allogeneic transplants use donor cells, creating the immunological conflict that produces GVHD. When GVHD is documented in an allogeneic HSCT patient, assign the appropriate GVHD code as a secondary diagnosis.

Autologous transplants use the patient’s own cells, so GVHD is not expected. A claim pairing autologous HSCT documentation with a GVHD code will likely trigger a payer audit and a denial. Record the transplant type clearly so the coder never has to infer it.

Using Z94.84 alongside T86.5

Z94.84 (stem cell transplant status) indicates the patient has received a stem cell transplant. When a complication is coded as T86.5, Z94.84 may be added per the instructional notes in the current tabular list.

Verify the exact instruction in the active code year. Some payers apply their own rules about whether Z94.84 is redundant when T86.5 is present. Never assign Z94.84 alone when an active complication warrants T86.5.

Payer requirements and pre-authorization for T86.5 claims

Payer requirements for stem cell transplant complication claims vary by MAC jurisdiction and insurer. The guidelines below reflect general Medicare and commercial payer patterns. Always confirm with the specific payer’s LCD or coverage policy before submitting.

• Facility requirements: check the payer’s coverage policy or LCD for facility requirements before you submit a T86.5 claim.
• Medical necessity documentation: the complication encounter must be medically necessary. The physician’s note must describe the clinical presentation, the complication diagnosis, and the treatment plan. Vague documentation (“patient seen post-transplant”) does not establish necessity.
• Inpatient vs outpatient claim type: inpatient T86.5 claims map to MS-DRGs. The applicable DRG depends on the complication type and the principal diagnosis. Outpatient claims use the standard APC/OPPS framework. DRG assignments change with annual IPPS rules, so verify the current mapping through CMS ICD-10 coding resources for the active fiscal year.
• Commercial payer prior authorization: most commercial insurers require prior authorization for HSCT procedures. Complication management following an authorized transplant is generally covered. Some payers still require notification or a separate authorization for inpatient complication admissions.
• Coordination of benefits: many HSCT patients have both Medicare and commercial coverage. Claims software that routes primary and secondary claims in sequence reduces manual errors when two payers share an encounter.

Meeting medical billing compliance requirements for transplant claims means documenting three facts in every encounter note, not only at admission. Those are the transplant history, the complication type, and the medical necessity.

Common claim denial reasons for ICD-10 Code T86.5

T86.5 claims deny for a predictable set of reasons. Most trace back to documentation or sequencing errors made before the claim leaves the practice. A denial management workflow logs each pattern per claim, so the same error isn’t repeated on the next transplant encounter.

• Wrong code selected: a T86.0- code is assigned instead of T86.5, or the reverse, because the notes use both terms. One says “bone marrow transplant” and another says “stem cell transplant.” The fix is a pre-coding check of the transplant history and a physician query when the terms conflict.
• Missing transplant history documentation: the claim carries T86.5 but the record contains no prior transplant documentation. Payers require evidence of the underlying transplant to accept a complication code. Include the transplant history in the problem list or H&P.
• Complication not supported by documentation: T86.5 is assigned without a clearly documented complication in the record. The code requires a documented complication. Routine post-transplant monitoring without one codes to Z94.84 and the relevant Z-code for the encounter reason, not T86.5.
• Sequencing error: T86.5 is listed as principal when the reason for admission was something else (such as a hematologic malignancy that prompted the original transplant). T86.5 becomes principal only when the complication itself is the reason for the encounter per UHDDS guidelines.
• Missing required secondary codes: the claim omits codes that a “use additional code” instruction calls for. These include the organism in infection complications, GVHD codes for allogeneic transplants, and immunosuppressant adverse effect codes. Payer claim edits often check for these pairs. Looking up the returned denial codes points to the missing pair faster.
• Payer-specific LCD/NCD non-compliance: some Medicare Administrative Contractors have Local Coverage Determinations for HSCT that specify documentation requirements beyond the ICD-10-CM guidelines. Check the applicable MAC’s LCD before submitting to avoid jurisdictional denials. The Medicare Coverage Database lists the active LCDs for each jurisdiction.

How claims management software prevents T86.5 denials

Without dedicated software, a coder checks each T86.5 claim by hand. They read the transplant history, confirm the procedure term, then hunt for every secondary code the tabular instructions call for. When a claim comes back denied, someone matches the denial code to the error and resubmits.

Pabau, the practice management platform we build, includes claims management software that connects to the Claim.MD clearinghouse. Claims go out electronically, eligibility checks run before submission, and electronic remittance advice (ERA) comes back against the claim.

For a T86.5 claim, that means a coverage problem shows up before submission instead of as a denial weeks later. Primary and secondary payers run through the same workflow, which suits HSCT patients with both Medicare and commercial coverage.

Submit transplant complication claims without the rework

Pabau integrates with Claim.MD to handle electronic claim submission, eligibility checks and ERA for oncology and transplant billing teams.

Book a demo

Conclusion

T86.5 is easy to find and easy to get wrong, because the physician’s wording decides it. Build the procedure-term check into your coding workflow before the claim is created. A coder who confirms “stem cell transplant” and the instructed secondary codes up front avoids the denials described above.

The trade-off is a slower first pass on each transplant claim. It pays back when a clean claim gets paid on first submission instead of returning weeks later with a CARC.

Book a demo to see how Pabau checks eligibility and submits T86.5 claims through Claim.MD before they reach the payer.

Continue your research

Need a framework for tracking transplant claim denials? Denial management in healthcare covers the workflows that reduce CARC-coded rejections before they affect your reimbursement cycle.

Want to understand the clearinghouse behind your claims? Claim.MD clearinghouse overview explains how payer routing, real-time eligibility, and ERA processing work for inpatient and outpatient claims.

Confused about 837 file submission for inpatient transplant claims? 837 file guide covers the structure, required fields, and common submission errors for 837I and 837P transactions.

Frequently asked questions