ICD code T86.19 – Other complication of kidney transplant

Key takeaways

ICD-10 Code T86.19 covers other complications of kidney transplant not elsewhere classified, effective October 1, 2025 for the 2026 ICD-10-CM edition.

T86.19 is a billable, specific code. Use it only when the complication is documented but does not qualify as rejection (T86.11), infection (T86.12), or failure (T86.13).

Z94.0 (kidney transplant status) is the standard companion code. CKD stage codes and causative organism codes may also apply depending on documentation.

Practice management software like Pabau tracks T86.1x denials by code, so a missing companion code surfaces before you resubmit.

What is ICD-10 Code T86.19?

ICD-10 Code T86.19 is the billable ICD-10-CM diagnosis code for “other complication of kidney transplant.” It covers documented post-transplant complications that fall outside the named subcodes for rejection, infection, and failure.

According to the CDC/NCHS ICD-10-CM tool, T86.19 is valid for reimbursement in the 2026 ICD-10-CM edition, effective October 1, 2025. It belongs to category T86 (Complications of transplanted organs and tissue). Within that category it sits in the T86.1x subcategory, which is reserved for kidney transplant complications.

The “other” designation follows standard ICD-10-CM convention. Within a subcategory, the residual “other” code carries the clinical scenarios the classification does not name explicitly. For a kidney transplant that includes transplant-associated nephropathy, post-transplant lymphoproliferative disorder in the allograft, and calcineurin inhibitor nephrotoxicity.

Each of those still needs the physician to name the complication. The note must also leave rejection, infection, and failure aside as the primary mechanism.

ICD-10 Code T86.19 in the T86.1x code family

T86.19 sits at the end of the T86.1x subcategory, which covers complications of kidney transplant under the broader T86 category. Placing T86.19 against its siblings is the most practical step a coder can take before assigning it.

The table below maps every T86.1x sibling, adapted from the AAPC ICD-10-CM code lookup. Match the physician’s wording to the row that describes it. Each sibling also has its own page in our diagnostic code library.

How T86.19 differs from T86.10, T86.11, T86.12, and T86.13

The key distinction is specificity vs. residual category. T86.10 (unspecified) is for cases where the physician acknowledges a complication exists but does not document its nature. T86.19 (other) is for cases where the physician has named the complication, but that complication does not fit rejection, infection, or failure.

T86.11 requires documented rejection, supported by biopsy findings or clinical criteria consistent with immune-mediated graft injury. T86.12 requires documented infection of the transplanted organ, with the causative organism coded additionally when identified. T86.13 applies when the graft has failed, often evidenced by return to dialysis or listing for re-transplant.

T86.19 carries the named complications the subcategory does not list separately. Immunosuppressant nephrotoxicity, post-transplant erythrocytosis, and allograft-associated hypertension all belong here once the physician documents them as complications of the graft. Primary non-function lands here too, where the graft never worked but the note avoids the word failure.

A query to the physician settles the ambiguous notes. The chart below walks the same decision in the order a coder meets it.

Documentation requirements for kidney transplant complication coding

ICD-10 Code T86.19 requires physician documentation that does two jobs. The note must name the complication and tie it causally to the transplanted kidney.

The CMS ICD-10-CM coding guidelines are clear that coders may not infer specificity. If the record states only “kidney transplant complication,” T86.10 is the correct assignment. T86.19 is appropriate only when the complication is named.

• Named complication: The physician must state what the complication is. “Calcineurin inhibitor nephrotoxicity” is sufficient. “Post-transplant problem” is not.
• Causal link to the transplanted kidney: The record must establish that the complication follows from the transplant. An incidental condition in a patient who happens to have a transplant does not qualify.
• Rejection, infection, and failure ruled out or not indicated: The documentation should not suggest rejection, infection, or failure as the primary mechanism. If the physician describes both nephrotoxicity and early rejection signs, query before assigning T86.19 alone.
• Transplant status confirmed: Some documentation systems require the transplant history to appear in the record for this encounter. Z94.0 (kidney transplant status) typically addresses this as a companion code.

When documentation is incomplete, CDI specialists should query the attending or transplant nephrologist. Queries should ask for the specific nature of the complication and whether rejection, infection, or graft failure is implicated. Adding this step before claim submission substantially reduces the risk of a denial based on lack of specificity.

Companion and additional codes used with ICD-10 Code T86.19

T86.19 rarely stands alone. The ICD-10-CM guidelines for transplant complications direct coders to add companion codes that complete the clinical picture. The codes below are the ones that apply most often.

• Z94.0 (Kidney transplant status): Signals to the payer that the patient has a functioning or previously functioning transplanted kidney. Most CDI resources recommend including this code whenever any T86.1x code is assigned, though sequencing guidance can vary by payer. Confirm the sequence your MAC expects before you submit.
• CKD stage codes (N18.1-N18.6): Post-transplant chronic kidney disease is common. If the physician documents CKD stage alongside the T86.19 complication, code the CKD stage additionally. The combination of T86.19 + N18.x is clinically valid and payer-accepted when documented.
• Causative agent codes: For calcineurin inhibitor nephrotoxicity, a code for the drug/adverse effect may be appropriate. Coders should follow the ICD-10-CM adverse effects and poisoning guidelines to determine sequencing.
• Z98.85 (Transplanted organ removal status): Used when the transplanted kidney has been removed and the patient carries that history. It does not apply while T86.19 is coded for an active complication.

For claims submitted to US payers, Pabau, our practice management software, connects to the Claim.MD clearinghouse. That connection supports electronic remittance and eligibility checks across thousands of US payers. Checking eligibility before submission and reading the remittance afterwards surfaces the companion codes a particular payer expects. That remittance often shows whether a companion code decided payment or denial.

Common coding errors and how to avoid them

Three patterns account for most of the preventable errors on T86.19 claims. Each one responds to the approach set out in our guide to denial management strategies. Find the pattern, trace it to the root cause, then fix the upstream process rather than reworking claims one by one.

• Using T86.10 when documentation supports specificity: Coders default to “unspecified” (T86.10) because the query step feels time-consuming. When the physician’s note contains language like “drug-induced nephropathy” or “post-transplant hypertension,” T86.19 is the right code and T86.10 is incorrect. Unspecified coding when specificity is available is an audit flag under ICD-10-CM guidelines.
• Confusing “other” with “unspecified”: The two labels are not interchangeable. “Other” means the complication is known but has no named code of its own. “Unspecified” means the complication type was never documented. Assigning T86.19 without a documented type is a coding error, and T86.10 applies instead.
• Missing the Z94.0 companion code: Many practices submit T86.19 without Z94.0, then receive a denial or a payer request for additional documentation. Add Z94.0 as a routine companion whenever any T86.1x code is assigned, and document the sequencing rationale in your coding notes.
• Not querying when documentation is ambiguous: Terms like “graft dysfunction” or “post-transplant complication NOS” do not clearly support T86.19 over T86.10. A structured query to the physician resolves the ambiguity and protects the practice from retrospective audit findings.

Coding accuracy on T86.19 protects revenue as much as it satisfies compliance. Denied claims need rework and resubmission, and an appeal consumes far more staff time than a pre-submission query.

ICD-10-CM coding guidelines for transplant complications

The ICD-10-CM Official Guidelines for Coding and Reporting, co-published by CMS and CDC, address transplant complications in the injury and external cause chapter. The core principle is narrow.

A complication of a transplanted organ is coded only when the physician documents the complication and its relationship to that organ. A condition that merely occurs in a transplant patient is not automatically a transplant complication.

Verify the current wording of any T86.1x code against the CDC/NCHS ICD-10-CM tool before you submit. The tabular entry confirms billable status and shows the Excludes notes sitting above the subcategory.

• Complication vs. incidental condition: If a transplant patient develops hypertension that the physician explicitly links to the transplant (transplant-associated hypertension), code T86.19. If the physician documents essential hypertension with no causal link to the transplant, code I10 instead.
• Sequencing: When T86.19 is the reason for the encounter, it sequences as the principal diagnosis. When it is an additional finding alongside another reason for the visit, sequence it as a secondary diagnosis. Payer guidance and the official guidelines both support that order.
• Chronic vs. acute complications: The T86.1x family does not subdivide by acuity. T86.19 applies whether the “other complication” is acute (sudden allograft dysfunction due to drug toxicity) or chronic (progressive transplant nephropathy).
• CKD in transplant patients: Per official guidelines, a transplant patient with CKD does not automatically get a transplant failure code. Code the CKD with N18.x and the transplant status with Z94.0. Where the physician documents the CKD itself as transplant failure, T86.13 applies instead.

Coding teams can build the Z94.0 check into the claims software billers use. A T86.19 claim missing its companion code then gets flagged before submission. Catching it there costs a minute of a coder’s time, while catching it after a denial costs an appeal.

How Pabau supports transplant complication coding and claim follow-up

Transplant complication denials are often tracked in a spreadsheet rebuilt from remittance PDFs each month. The code that failed, the companion code that was missing, and the resubmission date sit in three separate places. The pattern surfaces only once the quarter closes.

Pabau keeps coding, claim submission, and remittance against the same patient record. Claims go out through the Claim.MD clearinghouse, and the remittance comes back against the encounter it belongs to. T86.19 denials can then be listed by code rather than hunted invoice by invoice.

Your billers see which companion code was missing on each denied claim. The documentation conversation with the transplant team then starts from a list of specific encounters.

Simplify transplant complication billing

Pabau’s claims management software connects to the Claim.MD clearinghouse and tracks denials by code. A missing companion code surfaces before the claim goes out.

Book a demo

Conclusion

T86.19 is the right assignment only when the physician names the complication and ties it to the graft. Where that sentence is missing from the note, the code is T86.10, whatever the clinical picture suggests.

Practices seeing repeated T86.19 denials should audit the three errors above before appealing another claim. A query template agreed with the transplant nephrologist resolves more of them than any change to the billing workflow. Book a demo to see how Pabau tracks T86.1x denials by code for your billing team.

Continue your research

Need a broader overview of transplant-related billing? What is medical billing explains the end-to-end claim lifecycle from encounter to payment posting.

Seeing high denial rates on complication codes? Denial management in healthcare covers how to categorize, track, and resolve denial patterns systematically.

Want to verify RCM metrics across your transplant coding team? What is revenue cycle management outlines the key performance indicators practices use to measure billing health.

Frequently asked questions