ICD-10 Code T86.298: Other complications of heart transplant

Key Takeaways

ICD-10 Code T86.298 is the billable ICD-10-CM code for other complications of heart transplant not classified elsewhere in the T86.2x subcategory.

T86.29 is the non-billable parent; only T86.290 (cardiac allograft vasculopathy) and T86.298 are billable child codes.

Common clinical scenarios include PTLD, calcineurin inhibitor nephrotoxicity, and de novo autoimmune conditions in heart transplant recipients.

Pabau’s claims management software supports accurate post-transplant complication coding and reduces claim errors with integrated documentation workflows.

ICD-10 Code T86.298: Definition and clinical classification

ICD-10 Code T86.298 is a billable code that covers every post-transplant cardiac complication not elsewhere classified within the T86.2x subcategory. It’s the code that coders most frequently reach for when documentation describes something atypical in a transplant recipient’s clinical course.

T86.298 is a valid, billable ICD-10-CM diagnosis code effective for claims with a date of service on or after October 1, 2015, per CMS ICD-10-CM mandate. It sits within the broader T86 category (Complications of transplanted organs and tissue) under the S00-T88 chapter range covering injury, poisoning, and certain other consequences of external causes.

The hierarchy that coders need to navigate is straightforward:

• T86 – Complications of transplanted organs and tissue (category header, non-billable)
• T86.2 – Complications of heart transplant (subcategory header, non-billable)
• T86.29 – Other complications of heart transplant (non-billable parent)
• T86.290 – Cardiac allograft vasculopathy (billable)
• T86.298 – Other complications of heart transplant (billable)

Per the ICD List code reference, T86.29 must never appear on a claim. When the documentation points to “other complications,” coders must drill down to either T86.290 or T86.298 depending on whether the specific complication is cardiac allograft vasculopathy or something else entirely.

T86.298 code information at a glance

Before billing, teams need a quick reference for T86.298’s key attributes. The table below consolidates the essential facts.

Cardiac transplant complication coding: T86.290 vs T86.298

The distinction between T86.290 and ICD-10 Code T86.298 matters for both coding accuracy and reimbursement. Getting it wrong means a claim that either under-reports the clinical picture or codes a non-billable parent by mistake.

T86.290 is reserved for one condition only: cardiac allograft vasculopathy (CAV). This is a form of accelerated coronary artery disease unique to transplanted hearts, caused by immune-mediated injury to the donor vasculature. If the physician’s documentation specifically names CAV, T86.290 is the correct code, full stop.

T86.298 covers everything else within the “other complications” bucket. In practice, that includes a clinically diverse range of post-transplant conditions:

• Post-transplant lymphoproliferative disorder (PTLD) – EBV-driven lymphoid proliferation occurring in immunosuppressed recipients
• Calcineurin inhibitor nephrotoxicity – renal impairment secondary to tacrolimus or cyclosporine therapy
• De novo autoimmune conditions – new-onset autoimmune diseases arising post-transplant
• Drug-induced complications – adverse effects of immunosuppressive regimens not captured by more specific codes
• Other specified allograft dysfunction – graft-related complications not meeting criteria for rejection (T86.21), failure (T86.22), or infection (T86.23)

When documentation is ambiguous, query the treating physician before assigning T86.298. The AAPC recommends querying for specificity rather than defaulting to an unspecified or residual code where the clinical picture supports a more precise option. Use the AAPC Codify ICD-10-CM lookup to cross-reference the full T86 subcategory when reviewing related codes.

Related heart transplant ICD-10 codes and when to use them

Understanding T86.298 requires knowing the full T86.2x family. Each sibling code covers a distinct clinical scenario, and payers may audit claims where T86.298 appears alongside codes that should supersede it.

Beyond the T86.2x family, two additional codes frequently appear alongside T86.298 in post-transplant encounters:

• Z94.1 (Heart transplant status) – Report this as a secondary code whenever a transplant recipient presents, regardless of whether a complication is the primary reason for the visit. It provides critical context for payers.
• Z98.85 (Transplanted organ removal status) – Used when the transplanted heart has been removed and documents that the patient previously had a transplant that is no longer in situ.

For teams handling complex ICD-10 coding across multiple specialties, keeping the T86 hierarchy mapped to clinical workflows reduces query volume and rework. The CDC/NCHS ICD-10-CM web tool provides the official 2026 tabular list for verifying code validity and hierarchy before submission.

Documentation requirements for ICD-10 Code T86.298

T86.298 is a residual code, which makes documentation the most consequential part of coding it correctly. Payers can and do audit these claims, particularly in high-cost DRG groups involving transplant recipients.

The medical record must support three things before T86.298 is assigned:

1. Confirmation of heart transplant history – The record must establish that the patient is a cardiac transplant recipient. If not already in the problem list, Z94.1 as a secondary code makes this explicit to coders and payers alike.
2. Identification of a specific complication – The physician’s note must name or describe a post-transplant complication. “Post-transplant follow-up” alone does not support T86.298. The complication must be stated or clearly implied in the assessment.
3. Exclusion of more specific codes – The record must not describe rejection, failure, infection, or cardiac allograft vasculopathy. If those conditions are present, the appropriate named sibling code (T86.21 through T86.290) takes precedence over T86.298.

Where documentation gaps exist, a structured query process matters. Good patient intake forms built around transplant follow-up workflows help capture the specific complication language that coding teams need, reducing back-and-forth with physicians post-encounter.

For practices managing HIPAA-compliant clinical documentation, building documentation templates specifically for post-transplant encounters ensures coders consistently receive the clinical specificity T86.298 requires.

Streamline transplant complication coding with Pabau

Pabau's claims management and digital forms tools help transplant care teams document complications accurately and submit cleaner claims, reducing denials on complex post-transplant encounters.

Book a demo

Sequencing and combination rules for ICD-10 complication codes

T86.298 follows standard sequencing principles under the ICD-10-CM Official Guidelines. When the complication coded by T86.298 is the reason for the encounter, it sequences as the principal diagnosis. When the encounter is for a non-complication reason and the transplant complication is incidental, T86.298 sequences as an additional code.

Combination coding scenarios that arise frequently in transplant clinics:

• T86.298 + drug adverse effect code – When the complication is a direct adverse effect of immunosuppressive therapy (e.g., nephrotoxicity from tacrolimus), add the appropriate adverse effect code from the T36-T50 range. The drug code identifies the causative agent; T86.298 identifies the transplant-complication nature of the encounter.
• T86.298 + Z94.1 – Add Z94.1 as a secondary code in virtually every transplant-related encounter. Payers use this flag to process claims correctly through transplant-specific DRG pathways.
• T86.298 + organ-specific complication codes – If PTLD is documented, T86.298 captures the transplant-complication context while additional codes for the lymphoproliferative disorder provide the clinical specificity payers need for medical necessity review.

Practices that maintain structured clinical records with complete problem lists reduce sequencing errors on transplant claims because the full complication picture is visible to coders before they touch the claim. This is where EHR integration for post-transplant workflows directly reduces rework.

Billing and reimbursement guidance for heart transplant complication codes

Heart transplant complication claims are high-scrutiny encounters. Both Medicare and commercial payers apply medical necessity review to T86.298 submissions, particularly where the complication is not clearly described in the clinical documentation attached to the claim.

Key billing considerations for T86.298:

• DRG assignment – T86.298 maps to transplant-related DRGs under the MS-DRG system. Precise complication coding affects DRG weight and reimbursement level. Coding T86.20 (unspecified) instead of T86.298 can reduce DRG weight and underpay the encounter.
• Medical necessity documentation – Payers reviewing T86.298 claims will look for clinical notes that justify the encounter as medically necessary. The complication must be described as actively managed, not merely historical.
• Claim scrubbing – Most clearinghouses flag T86.29 (the non-billable parent) as an edit. However, T86.298 passes most scrubbers cleanly. The risk is the reverse: coders defaulting to T86.20 (unspecified) when T86.298 is the more accurate code, leaving reimbursement on the table.
• Commercial vs. Medicare payer rules – Medicare follows CMS ICD-10-CM guidelines directly. Commercial payers may apply additional LCD/NCD criteria. Check payer-specific policies before billing T86.298 for conditions like PTLD, where separate oncology codes may be required under some payer contracts.

Using claims management software built for transplant billing workflows reduces the risk of non-billable parent codes slipping through and ensures T86.298 is paired with the correct secondary codes before submission. The CMS ICD-10 codes page is the authoritative source for annual updates to the T86 subcategory.

For transplant programs with complex comorbidity profiles, compliance management tools that flag incomplete documentation before claim submission prevent the audit exposure that residual codes like T86.298 can attract when clinical notes are thin.

Post-transplant care management and coding workflows

The clinical reality of heart transplant follow-up is that most encounters involve multiple concurrent issues: immunosuppression titration, surveillance for rejection, screening for long-term complications, and management of comorbidities. Coding these encounters accurately means understanding which conditions map to T86.298 and which belong elsewhere.

A structured coding workflow for post-transplant encounters:

1. Review the physician assessment for explicit complication language. Look for terms like “PTLD,” “calcineurin nephrotoxicity,” “de novo autoimmune hepatitis,” or “allograft dysfunction, other specified.”
2. Check against the T86.2x exclusion list. If the note describes rejection, failure, infection, or CAV, those codes supersede T86.298.
3. Confirm T86.298 validity for the current fiscal year. Use the CDC/NCHS ICD-10-CM web tool to verify the code is active for the date of service.
4. Add required secondary codes. Z94.1 is near-universal. Drug adverse effect codes apply when immunosuppressant toxicity is the documented complication.
5. Document the sequencing rationale. For inpatient claims, note why T86.298 sequences as principal vs. additional in the coding record.

Practices managing ongoing post-transplant patient care workflows benefit from integrating these coding decision points into the EHR encounter template itself, so the clinical narrative and the code assignment align before the claim is generated. This is especially relevant for outpatient transplant clinics where encounter volume is high and coder query time is limited.

Conclusion

Heart transplant complication coding hinges on specificity. ICD-10 Code T86.298 is the correct billing code when the documented complication is real, post-transplant in origin, and does not fit any of the named T86.2x categories. Using T86.20 (unspecified) when T86.298 is supported by the record leaves reimbursement unclaimed and weakens audit defense.

For transplant programs looking to reduce coding errors and denial rates on complex post-transplant encounters, Pabau’s integrated documentation and claims management tools close the gap between clinical documentation and clean claim submission. Book a demo to see how Pabau supports transplant billing workflows end to end.

Continue your research

Need a reference for related ICD-10 neurological complication codes? Intraparenchymal hemorrhage ICD-10 codes walks through a similarly complex complication coding scenario with sequencing guidance.

Handling post-procedural anxiety documentation in transplant contexts? Situational anxiety ICD-10 code covers coding comorbid psychological conditions in medically complex patients.

Looking for HIPAA-compliant documentation workflows for your clinic? HIPAA compliance for medical offices covers the documentation standards that support defensible coding and audit-ready records.

Frequently Asked Questions