ICD code T86.39 – Other complications of heart-lung transplant

Key takeaways

T86.39 is a valid, billable ICD-10-CM code for FY2026 covering post-transplant complications in combined heart-lung recipients only — not heart-only or lung-only transplant patients.

The code is a residual bucket for complications that are not rejection (T86.31), failure (T86.32), or infection (T86.33). Physician documentation must explicitly support the “other” designation.

Z94.3 (heart and lungs transplant status) is routinely sequenced alongside T86.39, and omitting it is a frequent denial trigger.

Pabau’s claims management software validates required claim fields, such as membership and authorization numbers, before a transplant claim is submitted.

ICD-10 Code T86.39: Definition and billable status for FY2026

ICD-10 Code T86.39 is a specific, billable ICD-10-CM code valid for FY2026 encounters.

Its official descriptor is “Other complications of heart-lung transplant.” The code lives within the T86 parent category, “Complications of transplanted organs and tissue.” Its T86.3x subcategory is reserved for combined heart-lung transplant complications. According to the CDC/NCHS ICD-10-CM web tool, T86.39 carries no 7th character requirement and is reported at the 5-character level.

The T86.3x subcategory contains four sibling codes. T86.39 sits at the residual end, so it is only appropriate when none of the three more specific codes applies:

T86.39 has no 7th character extension. Some coders confuse this with other injury-category codes that do require A/D/S suffixes. The CMS ICD-10 codes page confirms T86.39 is reported as a 5-character code at every encounter type.

What T86.39 covers: Included complications of heart-lung transplant

“Other” in T86.39 names a defined set of post-transplant complications whose clinical mechanisms differ from rejection, failure, and infection. Coders sometimes read the word as “unspecified,” which sends the claim out on the wrong code. Physicians and CDI specialists need a working list of what legitimately belongs here so documentation queries land correctly.

Complications that fall under T86.39 include:

• Chronic allograft vasculopathy (CAV): Progressive intimal hyperplasia of transplanted coronary and pulmonary vessels, distinct from acute rejection episodes
• Bronchiolitis obliterans syndrome (BOS): Fibrotic airway obstruction following lung component transplant, when documented as chronic allograft dysfunction rather than active rejection
• Post-transplant lymphoproliferative disorder (PTLD): Lymphoid proliferation arising from immunosuppression, reported here unless a separate malignancy code is more appropriate
• Drug-induced complications: Calcineurin inhibitor nephrotoxicity, corticosteroid-associated complications, and other immunosuppression-related adverse effects attributed to the transplant management regimen
• Hemodynamic instability of transplanted organ: Documented hemodynamic dysfunction not meeting failure criteria per physician assessment
• Airway complications: Anastomotic dehiscence or stenosis of the bronchial anastomosis documented as a structural, non-infectious complication

One qualifier runs through all six. The physician must document the complication and the clinical reasoning that places it outside rejection, failure, and infection. A vague “transplant complication” note does not support the code.

T86.39 vs adjacent heart-lung transplant complication codes

The four T86.3x codes are mutually exclusive at any given encounter. Picking the wrong sibling code is one of the most common claim denial patterns on transplant complication claims, according to the AAPC’s ICD-10-CM coding resources. The table below maps each code to its clinical presentation and the key documentation language coders should look for.

How T86.39 differs from heart-only and lung-only transplant complication codes

T86.39 applies exclusively to patients who received a combined heart-lung transplant. Using it for a heart-only or lung-only recipient is a coding error that generates a medical necessity mismatch on audit. The FY2026 tabular list keeps the T86.3x subcategory structurally separate from the heart-only (T86.2x) and lung-only (T86.81x) subcategories. This distinction matters most in large transplant centers where all three patient populations coexist.

Confirm the transplant type from the patient’s surgical history before selecting any T86.3x code. The heart-only and lung-only rows above are where most misassignments start, because the sibling codes look alike at a glance. T86.29 and T86.81 are category headers rather than billable codes, so a claim carrying either one is rejected on specificity.

Excludes notes and code limitations

T86.39 carries both Excludes1 and category-level note guidance that coders must review before reporting. Misapplying these exclusions is a source of claim edits and CDI queries.

Key exclusions and limitations:

• Graft-versus-host disease (GVHD): Reported separately using D89.81x (D89.810 acute, D89.811 chronic, D89.812 acute on chronic, D89.813 unspecified). GVHD sits outside the T86.3x structure and must never be collapsed into T86.39.
• Malignancy arising in a transplanted organ: If PTLD has progressed to a diagnosed lymphoma, a neoplasm code from Chapter 2 takes precedence over T86.39. The transplant complication code may still be reportable as a secondary code, depending on the encounter context.
• Pre-existing conditions unrelated to the transplant: T86.39 requires a causal relationship between the documented complication and the transplant itself. Coincidental conditions in a transplant recipient do not qualify.
• Failure to thrive vs. specific complication: A vague note of “not doing well post-transplant” does not support T86.39. The complication category must be identifiable as distinct from rejection, failure, and infection.

In complex multi-system cases, route a CDI query before assigning T86.39 to an ambiguous encounter. Reproducing the excludes notes verbatim from the tabular list at the point of coding is the safest practice.

Required Z codes to report alongside T86.39

Transplant complication encounters almost always involve a cluster of Z codes that capture transplant status and ongoing medication regimens. Omitting one can trigger a denial for insufficient clinical context. Practice management software like Pabau handles the administrative side of that. Its tools for cleaner claims management check each claim for membership numbers and authorization codes before it is submitted.

Four Z codes appear on transplant complication claims often enough to build into your coding checklist.

Sequencing rule: When the patient presents specifically because of the complication covered by T86.39, that code is the principal diagnosis. Z94.3 follows as an additional code. If the encounter is a scheduled follow-up and the complication is an incidental finding, Z09 or Z76.89 may take the principal position. T86.39 then moves to secondary.

ICD-10-CM Official Guidelines Section II governs inpatient principal diagnosis selection. Section IV governs outpatient encounters. Verify the current FY2026 guidelines for any recent sequencing updates.

Clinical documentation requirements for T86.39

Supporting T86.39 requires more than a chart note mentioning a transplant complication. The physician documentation must carry four distinct elements before a coder can assign this code. Transplant codes sit among the highest-scrutiny codes at audit. A note that would pass for a routine encounter often will not pass here.

The four documentation elements required:

1. Confirmed combined heart-lung transplant history: The note must identify the patient as a combined heart-lung recipient, not a heart-only or lung-only patient. A surgical history reference, prior records, or an explicit physician statement all satisfy this.
2. Named complication: The specific complication must be named, rather than described vaguely as a “transplant-related issue.” Acceptable examples: “chronic allograft vasculopathy,” “bronchiolitis obliterans syndrome,” “calcineurin inhibitor nephrotoxicity.”
3. Causal link to the transplant: The physician must connect the complication to the transplant itself. “CAV in the setting of prior heart-lung transplantation” meets this standard; “CAV” alone does not.
4. Implicit or explicit exclusion of rejection, failure, and infection: The note need not read “this is not rejection.” However, the documented clinical picture must be inconsistent with those categories, or the physician must have ruled them out explicitly. A CDI query is appropriate whenever a named complication could plausibly be rejection- or failure-related.

CDI query triggers for T86.39:

• Documentation states “transplant complication” without naming the specific type
• Declining graft function documented without a named mechanism (possible T86.32 instead)
• Immunosuppressive drug adverse effect noted but causative relationship to the transplant not explicitly stated
• Biopsy result showing changes consistent with rejection without the physician explicitly using that term

Those four elements resolve into three checks that run in order. An encounter failing any of them does not get T86.39.

Common claim denials for T86.39 and how to avoid them

Transplant complication claims carry above-average denial rates because payers apply heightened scrutiny to high-cost patient populations. A systematic pre-submission review catches most of what a payer would reject. Reading the denial codes a payer returns on transplant encounters also helps coders build a targeted appeal rather than a generic one.

Appeal timelines matter as much as the coding itself on transplant accounts. Most commercial payers require appeals within 60-180 days of the initial denial. Transplant cases often involve multiple payers, such as Medicare plus a commercial secondary, and each carries its own window.

Payer and pre-authorization considerations

Heart-lung transplant patients typically fall under transplant-specific managed care plans or Medicare coverage that includes heightened utilization management. Practices should verify payer policies before submitting T86.39 claims for high-cost management encounters. Compliance on a transplant account also means documenting that pre-authorization was obtained where the plan required it. A clean claim submission carries every required code, authorization number, and modifier before it leaves the practice.

Key payer considerations for T86.39 claims:

• Pre-authorization triggers: Most commercial payers and Medicare Advantage plans require prior authorization for inpatient admissions in transplant patients. Outpatient management of chronic complications, including CAV surveillance and BOS monitoring, may also require authorization. Verify with each payer, and never assume outpatient follow-up is automatically covered.
• High-cost drug billing: When T86.39 accompanies a claim for immunosuppressive agents billed separately, such as tacrolimus under HCPCS codes, some payers apply medical necessity edits. The T86.39 diagnosis supports the drug’s medical necessity when the documentation links the medication to active complication management.
• CMS Medicare policies: CMS does not publish a National Coverage Determination specific to T86.39, but local coverage determinations from Medicare Administrative Contractors may apply. Check your regional MAC’s policies for heart-lung transplant follow-up services, since they vary by jurisdiction.
• When T86.39 alone is insufficient: Some payers require a secondary diagnosis code naming the specific complication alongside T86.39, such as a CAV-specific or BOS code. T86.39 identifies the transplant relationship, and the second code supplies the medical necessity detail. Check the payer’s code-pair edit policies before submission.

How Pabau keeps transplant complication claims moving

Most practices find a missing authorization number only after the payer rejects the claim. A biller rebuilds the submission, resubmits, and waits out another adjudication cycle. On a transplant account with two payers in sequence, that adds weeks to payment on a high-value claim.

Pabau validates each claim against the fields the payer requires before it leaves the practice. Membership numbers, authorization codes, and payer identifiers are checked at submission, and anything incomplete is flagged for the biller to correct. Claims then go out electronically through the Claim.MD clearinghouse or direct to Medicare.

Choosing between T86.39 and T86.31 stays with the coder and the CDI team, where it belongs. Pabau clears the administrative half of the denial pile, so the claims your billers chase are the ones that turn on clinical documentation.

Submit transplant claims with every required field present

Pabau checks membership numbers, authorization codes, and payer identifiers on each claim before submission. Electronic claims go out through Claim.MD or direct to Medicare, so fewer transplant claims come back on administrative errors.

Book a demo

Conclusion

T86.39 is a physician-driven code with a narrow job. Before assigning it, confirm the patient received a combined heart-lung transplant. Check that the note names the complication and places it outside rejection, failure, and infection. Then pair Z94.3 and sequence by the reason for the encounter.

Where the documentation is thin, a CDI query costs far less than an appeal. Move the query into the coding step rather than the denial step, and T86.39 accounts stop consuming rework time.

Pabau’s claims management software checks each transplant claim for the membership numbers, authorization codes, and payer identifiers it needs before submission. Book a demo to see how that works against your own transplant billing workflow.

Continue your research

Need a framework for managing claim denials systematically? Denial management in healthcare walks through a structured approach to tracking, appealing, and preventing recurring denials across all code types.

Want to understand how clearinghouse validation works? What makes a clean claim explains the pre-submission checks that stop transplant complication claims from failing on technical grounds.

Looking for broader transplant billing compliance context? Medical billing compliance requirements covers documentation, sequencing, and audit readiness across high-complexity patient populations.

Frequently asked questions