ICD code T86.40 – Unspecified complication of liver transplant

Found our content helpful?

Key takeaways

ICD-10 Code T86.40 covers liver transplant complications where documentation does not specify rejection, failure, infection, or another defined type.

The T86.4 subcategory has five billable children: T86.40, T86.41, T86.42, T86.43, and T86.49.

T86.40 is billable and valid for FY2026 (effective October 1, 2025) for HIPAA-covered transactions.

Always query the provider before defaulting to T86.40 if the record suggests a specific complication type but does not name it.

Pabau’s claims management tools help transplant care teams document and submit T86.4x codes accurately through the Claim.MD clearinghouse integration.

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

ICD-10 Code T86.40 is a billable, diagnosis-specific ICD-10-CM code for an unspecified complication of liver transplant. It is valid from October 1, 2025 through September 30, 2026 (FY2026).

According to the Centers for Medicare and Medicaid Services (CMS), the code is valid for HIPAA-covered transactions. Use it when documentation supports a liver transplant complication without naming the type. Rejection, failure, infection, and other named complications each have their own code in the same subcategory.

The code sits in the ICD-10-CM injury and poisoning chapter (S00-T88), under the transplanted organ complications block T80-T88. Within that block it belongs to the T86.4x family, which covers liver-specific transplant outcomes. Knowing where T86.40 sits in that hierarchy is what stops a coder reaching for the header code or the wrong sibling.

Code details at a glance

The following table summarizes the core reference data for T86.40 that coders and clinicians need before submitting a claim.

Coders can verify this code’s current status using the CDC/NCHS ICD-10-CM web tool, which mirrors the official tabular list updated each October 1.

T86.40 code hierarchy

T86.40 sits four levels deep in the ICD-10-CM hierarchy. Knowing the parent codes matters when payers return claims with hierarchy-related edits or when EMR systems require a higher-level code for encounter grouping.

The AAPC and other professional coding bodies confirm that T86.4 is a non-billable header code. Five child codes carry billable status: T86.40, T86.41, T86.42, T86.43, and T86.49. A coder selecting only T86.4 on a claim will receive a payer rejection for invalid code specificity.

That header-and-child pattern repeats across the ICD-10-CM code set. The same specificity test applies well beyond transplant coding, so the habit of checking for a billable child transfers to every other T-code family.

Instructional notes that govern T86.40 and its siblings

The tabular list attaches several instructions to this part of the T86 category. They change which additional codes belong on the claim, so read them before you finalize the encounter.

• Use additional codes for other transplant complications. The T86 category directs coders to identify graft-versus-host disease (D89.81-), malignancy associated with organ transplant (C80.2), and post-transplant lymphoproliferative disorder (D47.Z1) with their own codes.
• T86.43 requires a code for the organism or infection. When infection is documented, add the code that names it, such as cytomegalovirus infection (B25.-).
• The complication must affect the transplanted organ. A condition that happens to occur in a transplant patient is not a transplant complication unless the provider ties it to the graft.
• Z94.4 does not pair with a T86.4x code. Liver transplant status describes a functioning graft with no documented complication. It is not reported alongside T86.40 for the same organ and encounter.

Synonyms and approximate terms for T86.40

ICD-10-CM indexes list several approximate synonyms that map to T86.40. These are the clinical phrases that point to this code rather than a more specific sibling. They turn up in physician notes, discharge summaries, and operative reports.

• Complication of liver transplant, unspecified
• Liver transplant complication, type not specified
• Hepatic transplant complication, unspecified
• Post-liver transplant complication, unspecified
• Liver graft complication, unspecified
• Unspecified hepatic allograft complication

When the physician documents “liver transplant complication” without further qualification, T86.40 is the appropriate code. Coders should not infer rejection, failure, or infection from non-specific language such as “the transplant is not doing well” without explicit physician confirmation.

The five billable codes in the T86.4x family

T86.40 is the least specific member of the T86.4x family. The table below shows all five billable codes, their descriptions, and the clinical distinction that governs which one applies. Accurate selection between these codes is the most common coding challenge in transplant documentation.

Two of these codes get mixed up more than the rest. T86.43 covers infection of the graft or the transplant site. T86.49 covers a named complication that is mechanical, vascular, or biliary. A hepatic artery thrombosis or an anastomotic biliary stricture is T86.49, not T86.43.

T86.40 answers one question about the record. Does the note name a type? A phrase such as “possible rejection” names a suspicion, so query the provider before assigning T86.41. Coding probable or possible conditions as confirmed is a compliance violation.

When to use T86.40 instead of a specific code

One question decides it. Does the documentation name the specific type of complication? If it does, code the named type. If it does not, use T86.40. The chart below maps the wording you will see in a note onto the code it supports.

Follow this decision sequence before assigning the code:

1. Review the complete record. Check the discharge summary, progress notes, and attending physician’s assessment. Look for language that names rejection, failure, infection, biliary stricture, vascular complication, or another specific diagnosis tied to the transplanted liver.
2. Distinguish confirmed from suspected. ICD-10-CM Official Guidelines require that only confirmed diagnoses be coded for inpatient encounters. “Possible rejection” or “rule out failure” does not support T86.41 or T86.42.
3. Match the named complication to its code. Rejection takes T86.41 and graft failure takes T86.42. A documented infection of the graft or transplant site takes T86.43. Any other named complication, such as biliary stricture or hepatic artery thrombosis, takes T86.49.
4. Query the provider when ambiguous. If the note says the transplant is “showing signs of dysfunction” but does not specify a type, submit a compliant clinical documentation improvement (CDI) query. This protects coding accuracy and keeps the claim defensible on audit.
5. Assign T86.40 only when specificity is genuinely absent. Confirm first that the record supports none of T86.41, T86.42, T86.43, or T86.49. Once that is settled, T86.40 is the correct code, and you should not upgrade it without physician confirmation.
6. Add any secondary codes required. If the complication caused a secondary condition (e.g., acute kidney injury from tacrolimus toxicity), code that condition additionally per sequencing guidelines.

Tracking how often T86.40 turns up across a transplant population shows where documentation needs work. A department that reports it far more than its peers is usually writing thinner notes. Auditing that pattern belongs in any medical billing compliance program.

Common T86.40 coding errors that trigger denials

Most T86.40 denials trace back to one of five avoidable mistakes. Each one is visible in the record before the claim goes out.

• Coding T86.40 when the note names an infection. Cholangitis, an intra-abdominal abscess, or CMV hepatitis in the graft supports T86.43, and the payer can see that language in the record.
• Sending T86.43 for a mechanical or vascular problem. Biliary strictures, bile leaks, and hepatic artery or portal vein thrombosis belong to T86.49.
• Reporting Z94.4 alongside T86.40. Liver transplant status and a transplant complication code do not travel together for the same organ and encounter.
• Submitting the header code T86.4. It is not billable, and the claim comes back as invalid for specificity.
• Coding a suspected complication as confirmed. “Rule out rejection” is not T86.41, and an outpatient record with no confirmed complication does not support T86.40 either.

A routine post-transplant follow-up with a well-functioning graft and no documented problem is not a T86.40 encounter. Z94.4 carries that visit on its own.

Documentation requirements for T86.40

For a claim carrying T86.40 to survive payer review, the clinical record must support all three of these elements:

• History of liver transplant. The record must establish that the patient has a transplanted liver, through surgical history or an explicit statement in the attending’s note. Z94.4 cannot do that job here, since the status code is not reported with a T86.4x complication code for the same encounter.
• Documented complication. The treating physician must explicitly document a complication related to the transplant. A general statement that the patient is “post-transplant follow-up” is not sufficient. The note must name a problem, abnormality, or complication arising from or affecting the transplanted organ.
• Absence of specificity. The record must lack documentation that names the complication as rejection (T86.41), failure (T86.42), infection (T86.43), or another defined type (T86.49). If the record contains any of those specific terms, T86.40 is no longer the right code.

Payers use these three criteria to validate unspecified complication claims. A claim is vulnerable to denial if it misses the transplant history, lacks explicit complication documentation, or carries T86.40 where the record supports T86.41.

Practices handling high volumes of transplant follow-up encounters need that detail in front of the coder before the claim goes out. A structured client record that keeps surgical history and complication notes together does most of that work.

T86.40 code history and annual updates

T86.40 has maintained continuous validity across recent ICD-10-CM fiscal years. The table below shows its recent revision history. Transplant complication codes in this family have been stable, with no restructuring or deletion in recent cycles.

ICD-10-CM codes are updated annually on October 1. Practices should verify code validity each fiscal year. The official AAPC Codify ICD-10-CM lookup reflects the current-year tabular list.

Submitting a code from a prior fiscal year after the October 1 cutoff is a common payer rejection trigger on transplant claims. Long-term follow-up patients are the usual casualties, since their encounters often span a fiscal year boundary.

How Pabau supports liver transplant complication coding

Accurate post-liver transplant diagnosis codes depend on documentation quality at every stage of the encounter. Practice management software like Pabau keeps the note and the claim in one system.

Its claims software for coders ties clinical documentation, ICD-10 code assignment, and electronic claim submission into a single workflow. The coder sees what the physician wrote without chasing it across systems.

Transplant care teams commonly face two problems. First, physicians document complications in progress notes but do not carry the specificity forward to the discharge summary. That leaves coders with ambiguous records that default to T86.40 when T86.41, T86.43, or T86.49 might be supportable.

Second, follow-up encounters for stable post-transplant patients often lack complication documentation. That leaves the coder choosing between T86.40 and Z94.4 with little to go on.

Pabau addresses both. Structured clinical notes prompt the physician for completeness, and the Claim.MD clearinghouse integration validates the claim before it is submitted. Diagnosis codes are checked against the current ICD-10-CM catalog, so a retired or mistyped code is caught before the payer sees it.

For practices managing transplant follow-up populations, cleaner documentation upstream means fewer T86.40 assignments that should have been specific.

Pabau also supports HIPAA-compliant claim transmission. Transplant complication codes such as T86.40 travel on HIPAA 837P transactions, and Pabau keeps those transactions within payer and regulatory requirements.

Reduce unspecified transplant complication codes with better documentation

Pabau connects clinical documentation and ICD-10 claim submission in one workflow, helping transplant care teams move from T86.40 to specific codes supported by the record. See how it works for your practice.

Book a demo

Conclusion

T86.40 earns its place on a claim only after T86.41 through T86.49 have each been ruled out of the record. Reach it at the end of a documentation check, never at the start of one. A CDI query takes a few minutes, while a specificity denial costs the whole claim.

Practices that audit their T86.40 volume each quarter find the pattern quickly. Where one department reports it far more than the rest, physician education usually closes the difference.

For practices submitting transplant-related claims electronically, Pabau’s built-in ICD-10 coding tools and clearinghouse integration catch errors before they reach the payer. Book a demo and bring your own transplant documentation challenges to the conversation.

Continue your research

Need to understand how ICD-10 denial patterns affect your bottom line? Denial management in healthcare covers the most common coding-related denial triggers and how to address them.

Want to verify clean claim standards before submission? What makes a clean claim outlines the documentation and coding accuracy requirements payers use to auto-adjudicate claims.

Looking for a broader overview of transplant-related billing processes? What is medical billing explains how ICD-10 codes like T86.40 connect to the full revenue cycle from documentation to payment.

Frequently asked questions