ICD-10 Code T86.13: Kidney transplant infection

ICD-10 Code T86.13 is the billable ICD-10-CM diagnosis code for kidney transplant infection. It documents an infectious complication in a patient who has received a renal allograft. The code has been valid for HIPAA-covered transactions since October 1, 2015, and remains current.

Coders working with transplant patients often reach for the unspecified T86.10 out of habit. When the note supports an infection, T86.13 is the more specific and correct choice.

This reference covers the code’s billable status, its siblings in the T86.1x family, the documentation that justifies it, and the errors that cost practices money.

Found our content helpful?

Key takeaways

T86.13 is the billable ICD-10-CM code for kidney transplant infection, distinct from rejection (T86.11) and failure (T86.12).

The code has been valid for HIPAA-covered transactions since October 1, 2015, and remains current for FY2026.

Documentation must confirm the infection and, where possible, name the causative organism for co-coding.

Practice management software like Pabau tracks ICD-10 submissions and claim denials for transplant encounters.

ICD-10 Code T86.13: Code overview and billable status

ICD-10 Code T86.13 is a billable and specific code under the International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM).

It is valid for use in HIPAA-covered electronic transactions, confirmed by the CDC/NCHS ICD-10-CM web tool. The code sits within the broader T86 chapter covering complications of transplanted organs and tissues. Its parent is T86.1, complications of kidney transplant.

Per CMS ICD-10 coding guidance, T86.13 has not been revised since its introduction and carries no pending modifications for FY2026. Coders who work across several complication categories can check the sibling entries in the ICD-10-CM code index before settling on a specificity tier.

T86.1 code family: Kidney transplant complications

T86.13 belongs to the T86.1x family, which covers complications specific to kidney transplants. Each sibling code maps to a distinct clinical complication type. Using the wrong sibling produces a claim that misstates the encounter, which can trigger denials or audit flags.

Which sibling applies comes down to what the physician wrote. Read as a single decision, the choice is quicker to make than a table of definitions.

Approximate synonyms and clinical inclusions

Several clinical terms and index references map to T86.13 in the ICD-10-CM alphabetic index. Coders and clinicians may encounter these descriptions in documentation:

• Kidney transplant with infection
• Renal transplant infection
• Post-transplant infection (renal)
• Infection following kidney transplantation
• Kidney allograft infection

These synonyms all index to T86.13 in the official ICD-10-CM tabular list. When one of these phrases appears in physician documentation, T86.13 is the appropriate code.

The complication still has to belong to the transplanted kidney, rather than to a post-operative infection unrelated to the graft. The AAPC ICD-10-CM code lookup can help coders confirm index pathways for edge-case terminology.

Excludes notes and coding guidance

ICD-10-CM instructional notes for the T86.1x family carry clinical and billing weight. Misreading an Excludes1 note can produce a claim that is non-compliant with official guidelines.

Use additional code instruction: The ICD-10-CM tabular list instructs coders to add a second code identifying the causative organism where it is documented. A T86.13 claim should therefore carry a B-series code from the B00-B99 infectious diseases chapter whenever the treating clinician has named the pathogen.

Common pairings include bacterial, fungal, and viral organisms. The B-code you select has to match documented laboratory or clinical findings. Coders should never assign an organism code on assumption alone.

Excludes1 consideration: The T86 category carries Excludes1 notes for conditions that cannot be coded together. An Excludes1 note means the two conditions do not coexist, so neither may be reported alongside the other on one claim. Always verify the current official tabular list before coding. The AAPC entry for T86.13 works as a quick cross-check against the CMS tabular file.

Documentation requirements for kidney transplant infection coding

Accurate documentation is the foundation of a defensible T86.13 claim. Incomplete records push coders toward the unspecified T86.10, which carries lower clinical specificity and can flag for payer review.

The following elements should appear in the medical record to justify T86.13:

• Confirmed infection: A physician statement, or documented findings such as fever, elevated inflammatory markers, or a positive culture in the transplant recipient
• Transplant status: Prior history of kidney transplant documented, confirming the patient’s status as a renal allograft recipient
• Causative organism (where possible): Laboratory results identifying the pathogen, which support co-coding of a B-series organism code
• Complication linkage: An explicit clinical connection between the infection and the transplanted organ, not a coincidental infection in a transplant recipient
• CKD staging (if applicable): Where chronic kidney disease co-exists, its stage recorded separately, so coders can judge whether a co-code fits the instructional notes

How to distinguish T86.13 from transplant rejection codes

T86.11 (rejection) and T86.12 (failure) are the sibling codes most often confused with T86.13 (infection). The clinical and billing stakes differ for each. Payers, transplant registries, and clinical quality programs all use these codes to track distinct post-transplant outcomes.

When documentation is ambiguous, coders should query the physician rather than default to T86.10. The query takes minutes at coding time, and it protects both the practice at audit and the accuracy of the patient record.

Coding tips and common errors for kidney transplant infection

Even experienced coders make avoidable errors with T86.13 claims. Most originate from documentation habits rather than from misunderstanding the code itself.

• Do not default to T86.10: The unspecified code is appropriate only when documentation genuinely does not support a more specific one. If the physician has documented an infection, T86.13 is the correct code. Choosing T86.10 instead understates clinical complexity and may affect case mix index and DRG assignment.
• Add the organism code when supported: Leaving out the B-series organism code when culture results sit in the chart costs the claim its clinical specificity. Payers may also weigh that second code when judging medical necessity for anti-infective treatments.
• Check sequencing for the principal diagnosis: In an inpatient setting, the condition chiefly responsible for the admission determines the principal diagnosis. If the patient was admitted because of the transplant infection, T86.13 may serve as principal. If the infection is a co-existing condition, T86.13 becomes a secondary code instead. Sequencing errors affect DRG assignment and reimbursement.
• Verify CKD co-coding per instructional notes: Where chronic kidney disease is documented and the instructional notes support co-coding, assign the appropriate N18.x code. Confirm the current tabular instructions first, as this guidance changes periodically.
• Use ICD-10-CM, not ICD-9-CM: T86.13 has no exact ICD-9-CM equivalent. If a practice still runs a legacy system that references ICD-9 codes, flag the encounter for crosswalk verification before submission.

Denial reason codes show which T86.13 claims failed and why. Practices that process electronic remittance advice through their clearinghouse can trace those codes back to sequencing and specificity errors. The same documentation fault then stops repeating next quarter.

How Pabau keeps T86.13 claims accurate from note to remittance

In most practices the transplant note lives in one system and the claim is built in another. A coder re-keys the diagnosis, and the denial only surfaces when the remittance arrives weeks later. By then the encounter is cold and the physician has moved on.

Practice management software like Pabau holds the encounter, the diagnosis code, and the claim in one patient record. Pabau’s first-pass claims management checks the code against the note before submission, so an unspecified T86.10 gets caught inside the practice.

For US practices, the Claim.MD integration submits coded claims electronically to thousands of US payers and processes remittances back into the same record. Real-time eligibility checks run across over 400 payers, so staff spend less time on manual lookups before a transplant visit.

Submit ICD-10 transplant claims without rework

Pabau builds the claim from the encounter note and submits it electronically through Claim.MD to thousands of US payers. Eligibility checks across over 400 payers and ERA processing cut the manual steps that create T86.13 denials.

Book a demo

Conclusion

T86.13 applies whenever a kidney transplant patient has a documented infectious complication, and nothing about the code is optional once the note supports it. Defaulting to the unspecified T86.10 understates the encounter, distorts case mix data, and puts DRG accuracy at risk.

The work that decides the code happens before the claim goes out. Confirm the infection, link it to the transplanted kidney, and name the organism where the lab results allow it. Book a demo to see how Pabau turns a transplant note into a coded claim that survives payer review.

Continue your research

Need to understand how transplant claims move through the clearinghouse? Claim.MD clearinghouse overview explains how electronic claims reach US payers and where ICD-10 codes are validated.

Seeing repeated claim rejections on complex diagnosis codes? Denial management in healthcare covers how to categorize, track, and resolve claim denials systematically.

Want a primer on how ICD-10 fits into the broader billing cycle? Revenue cycle management fundamentals walks through each stage from encounter to payment, including diagnosis coding workflows.

Frequently asked questions