ICD code T86.49 – Other liver transplant complications

Key takeaways

T86.49 covers liver transplant complications other than rejection, failure, or infection, including biliary stricture and vascular complications.

The code is billable at 5 characters with no 7th-character extension required.

Z94.4 (liver transplant status) is not assigned with T86.4- codes, because the complication code already tells the payer the patient has a transplanted liver.

Add a code for the specific complication, such as K83.1 for a biliary stricture. Add D89.81-, C80.2 or D47.Z1 when GVHD or a transplant-related malignancy is documented.

T86.40 (unspecified) applies only when the physician documents no complication type. T86.49 needs the complication named in the record.

ICD-10 code T86.49: Definition and scope of “other” liver transplant complications

ICD-10 code T86.49 describes a complication of a transplanted liver that the treating physician documents specifically.

The complication does not meet the clinical definitions for rejection, failure or infection. “Other” here means a distinct complication type is present and charted. It simply has no subcategory of its own in the T86.4- family.

Clinical scenarios appropriately assigned ICD-10 code T86.49 include:

• Biliary stricture or biliary leak post-transplant
• Hepatic artery thrombosis not classified elsewhere in the Tabular List
• Portal vein thrombosis in a transplant patient
• Ischemic cholangiopathy following liver transplant
• Graft-related vascular complications (other than those coded elsewhere)
• Post-transplant lymphoproliferative disorder when the physician links it to the graft, with D47.Z1 as an additional code

If the physician charts a complication but gives no type detail, the correct code is T86.40. T86.49 requires the record to name the complication, because that detail is what separates it from the unspecified code.

T86.4x code family: Inclusions and exclusions

The T86.4- subcategory contains five codes, each for a distinct complication type. The physician’s wording, not the coder’s judgment, decides which sibling applies.

Category T86 carries a “use additional code” note for three related conditions. They are graft-versus-host disease (D89.81-), malignancy associated with organ transplant (C80.2), and PTLD (D47.Z1). When the physician documents one of them, it is coded alongside the T86 code rather than instead of it. Complications of bone marrow transplant have their own subcategory, T86.0-, and are never coded from T86.4.

How T86.49 differs from T86.41, T86.42, and T86.43

The choice between T86.49 and its siblings rests on the terms the physician documents. Clinical severity and the coder’s reading of lab values don’t change it. Rejection terms point to T86.41, and failure terms point to T86.42. Work through this order before assigning any T86.4- code:

1. Rejection documented? Assign T86.41. Look for terms: “acute rejection,” “chronic rejection,” “hyperacute rejection,” “antibody-mediated rejection,” or “AMR.”
2. Failure documented? Assign T86.42. Look for terms: “primary non-function,” “graft failure,” or “hepatic graft loss.”
3. Infection documented and linked to transplant? Assign T86.43. The physician must explicitly link the infection to the transplanted organ. A concurrent infection not attributed to the graft is coded separately.
4. Specific complication documented but none of the above? Assign T86.49. This is the correct code for biliary, vascular, structural, or immunologic complications the physician names but that fall outside the three defined categories.
5. Complication documented without type? Assign T86.40. Do not assume specificity that the record does not contain.

A common error looks like this. A coder sees “post-transplant biliary complication” and reaches for T86.40 because the note doesn’t say “rejection” or “failure.” Biliary stricture is a named complication, so it belongs under T86.49. Query the physician when the note says only “transplant complication” with no further description.

Additional codes and sequencing for T86.49

T86.49 is rarely coded in isolation. The T86 “use additional code” note and the Official Guidelines direct coders to add a code for the specific complication. Any related condition the physician documents is coded too.

Liver transplant status (Z94.4) is not one of them. Category Z94 carries an Excludes1 note for complications of transplanted organs or tissue. Guideline I.C.21.c.3 also says a status code is not used when the diagnosis code already includes that information. T86.49 already identifies a transplanted liver, so Z94.4 stays off the claim.

Sequencing rule: T86.49 is sequenced as the principal diagnosis when the complication is the reason for the encounter. The code for the specific complication (e.g. K83.1 for biliary obstruction) follows it, per the Chapter 19 transplant complication guidelines. Immunosuppressant status codes come after those. Do not add Z94.4.

7th character and external cause code requirements

T86.49 does not require a 7th character. The code is complete at 5 characters, and adding an extension makes it an invalid code, so the claim is rejected.

Coders get caught out because T86.49 sits in Chapter 19 next to injury codes that do require 7th characters. Those use A for initial encounter, D for subsequent encounter and S for sequela. The 7th-character rule applies to injury, poisoning and other codes that carry a 7th-character table, mainly in S00-T79. Category T86, in the complication-of-care block (T80-T88), has no 7th-character table, so no extension applies to T86.49.

External cause codes are not routinely required by payers for T86.49 encounters. Some Medicare Administrative Contractors (MACs) may request them for specific procedure claims. Check the applicable MAC’s local coverage determination (LCD) before submission.

Documentation requirements for accurate T86.49 coding

Coding accuracy for T86.49 depends entirely on what the physician documents. Vague language pushes the claim to T86.40 or, worse, to a denial for insufficient medical necessity.

The physician record must contain all of the following to support T86.49 and to support submitting a clean claim:

• Explicit linkage: The note must connect the complication to the transplanted liver, not just mention both in the same document. Language like “biliary stricture of transplanted liver” or “hepatic artery thrombosis complicating liver transplant” establishes the link.
• Complication type named: The record must name the specific type of complication, such as “biliary,” “vascular” or “structural.” That detail is what separates it from unspecified T86.40.
• Transplant history confirmed: The chart must document the patient’s prior liver transplant, either in the history or as an active problem. This supports the T86.4- category itself, which already carries the transplant status.
• Supporting findings: Relevant lab values (elevated LFTs, bilirubin trends), imaging results (hepatic Doppler, MRCP, liver biopsy), or procedure notes substantiate the complication.
• Immunosuppression status: The medication list or problem list should reflect current immunosuppressive therapy to support the Z79.62- or Z79.69 status code.

If the note reads “transplant complication – follow up” with nothing further, query the physician before assigning T86.49. A query answered with the complication type unlocks the more specific code and protects the claim from medical necessity denial.

Payer requirements and prior authorization considerations

Medicare processes T86.49 claims under standard Part B or Part A rules depending on the care setting. Inpatient encounters use MS-DRGs that group liver transplant complication codes. Verify DRG assignment with your facility coder to confirm the complication code carries the expected DRG weight.

For electronic remittance advice processing, payers return CARC/RARC codes that give the denial reason. Keep a log of denial codes on T86.4- claims. The same reasons tend to recur, and a short checklist built from them catches many before resubmission.

Commercial payers vary significantly. Common requirements include:

• Prior authorization for repeat imaging or procedures tied to the complication
• Medical necessity narrative submitted with the claim for high-cost complication management
• Transplant program identification number on the claim form
• Coordination of benefits confirmation when the patient has Medicare plus a commercial plan

Check each commercial payer’s coverage policy, and your MAC’s LCDs, every year. Transplant complication billing policies can change with each fiscal year update.

Common claim denial reasons for liver transplant ICD-10 billing

T86.49 claims are denied for predictable, correctable reasons. A consistent denial management routine catches them before they reach the payer. Here are six common denial types and the corrective action for each:

For more on matching denial codes to corrective actions, the denial codes in medical billing guide covers common CARC/RARC pairings on transplant complication claims.

Coding examples: T86.49 in clinical practice

The following scenarios illustrate correct code assignment across three common clinical situations. Each example reflects the documentation standard required to support the selected codes.

Example 1: Biliary stricture post-transplant

A patient with a liver transplant from three years prior presents with elevated bilirubin and jaundice. MRCP confirms an anastomotic biliary stricture. The physician’s note reads: “Biliary stricture of transplanted liver – scheduling ERCP for balloon dilation.”

Correct codes: T86.49 (principal) + K83.1 (obstruction of bile duct) + Z79.621 (if on tacrolimus or another calcineurin inhibitor). Z94.4 is not assigned, because T86.49 already identifies the transplanted liver.

Example 2: Hepatic artery thrombosis

A transplant patient admitted for abdominal pain undergoes a Doppler ultrasound revealing hepatic artery thrombosis. The attending documents: “Hepatic artery thrombosis complicating liver transplant – urgent vascular surgery consult.”

Correct codes: T86.49 (principal) + the appropriate thrombosis or vascular code for the hepatic artery, plus an immunosuppressant status code if one applies. Keep this code set on file next to the claim in your claims management software, so nobody rebuilds it from memory at each admission.

Example 3: When NOT to use T86.49

A patient’s discharge summary reads: “Liver transplant recipient with transplant complication – managed conservatively.” No specific complication type is documented.

Correct code: T86.40 (unspecified), not T86.49. The physician has not named a complication type. Query for specificity before discharge when possible. A specific complication documented before the claim drops supports T86.49 and lowers the risk of a later denial.

ICD-10-CM Chapter 19 context: Where T86.49 sits

Understanding the hierarchical context helps coders navigate the Tabular List and apply the correct Excludes1/Excludes2 notes. T86.49 sits within this structure:

• Chapter 19 (S00-T88): Injury, poisoning, and certain other consequences of external causes
• Block T80-T88: Complications of surgical and medical care, not elsewhere classified
• Category T86: Complications of transplanted organs and tissues
• Subcategory T86.4: Complications of liver transplant
• Code T86.49: Other complications of liver transplant

Complication-of-care codes are classified in Chapter 19 (T80-T88), not by organ system. So transplant complication codes sit there rather than in Chapter 11 (diseases of the digestive system). A biliary stricture in a native liver is coded from K83 alone. The same stricture in a transplanted liver is coded first from T86.49, with the K83 code added after it.

How Pabau reduces denials on T86.49 claims

Many T86.49 denials start before the claim is built. The usual causes are a note without organ linkage, a code set copied from an old encounter, or coverage nobody checked. Billing teams then find the problem weeks later, in a remittance file.

Pabau, the practice management platform we build, keeps the clinical note, the invoice and the claim on one patient record. Through its Claim.MD integration, Pabau turns invoices into electronic CMS-1500 claims and sends them to thousands of US payers. Eligibility is checked in real time before submission, and electronic remittance advice (ERA) comes back into the same system.

The result is fewer resubmissions. Your team catches a missing complication code or an unlinked note while the encounter is still fresh, before a denial arrives.

Reduce transplant coding denials with smarter claims management

Pabau integrates with Claim.MD to check eligibility before submission and process ERAs. Your billing team spends less time on rework.

Book a demo

Conclusion

T86.49 rewards precise documentation and punishes guesswork. If the physician names the complication and links it to the transplanted liver, T86.49 plus a code for that complication completes the claim. Adding Z94.4 on top is a coding error the guidelines rule out, however cautious it feels.

The practical move is to fix your templates now. Pair T86.49 with the specific complication code, keep immunosuppressant status codes current, and query the physician whenever the note says only “transplant complication.” To see how Pabau handles eligibility checks and remittance for these encounters, read about its Claim.MD clearinghouse integration.

Book a demo to see how Pabau helps your billing team code transplant complications accurately and get claims paid the first time.

Continue your research

Need to understand denial codes on returned claims? Denial codes in medical billing maps the most common CARC and RARC pairings returned on transplant complication claims.

Want to validate claims before submission? Submitting a clean claim covers the pre-submission checklist that catches missing companion codes before they cause denials.

Looking for ERA processing guidance? Electronic remittance advice explains how to read and act on 835 transaction files returned after claim adjudication.

Is the graft itself failing? ICD-10 code T86.42 covers liver transplant failure, including primary non-function and graft loss.

Building a denial follow-up routine? Denial management in healthcare shows how to track, fix and resubmit denied claims before the appeal window closes.

Frequently asked questions