ICD code T86.12 – Kidney transplant failure

Key takeaways

T86.12 is the billable code for kidney transplant failure, meaning the graft has lost function.

Rejection alone goes to T86.11, and infection of the transplanted kidney goes to T86.13.

Post-transplant CKD alone is not a complication, so it takes N18.- plus Z94.0, not T86.12.

Z94.0 is commonly added as a status code, but no tabular note makes it mandatory with T86.12.

Most T86.12 problems start in the note, so query the provider when failure is not stated plainly.

ICD-10 code T86.12 means the kidney graft has failed

ICD-10 code T86.12 is the billable ICD-10-CM code for kidney transplant failure. You use it when the physician documents that the transplanted kidney has lost function. That is a different finding from rejection, which has its own code, T86.11.

The code has been valid since October 1, 2015, and it is still active for FY2026. It has no child codes, so T86.12 is the complete code on the claim. It sits in Chapter 19, under category T86 for complications of transplanted organs and tissue.

Pick the right T86.1 code before you pick anything else

The T86.1 subcategory holds five codes. Each one answers a different question about the graft. So the first job is matching the physician’s exact word to the right sibling.

The mix-up is easy to understand. A rejected kidney can go on to fail, and both words can appear in the same chart. Still, the codes record different findings. Rejection describes an immune attack on the graft. Failure describes the result, a kidney that no longer does its job.

The chart below maps each documented finding to its code, including the CKD-only and unclear-wording cases.

What T86.12 covers, and what it leaves out

T86.12 covers a transplanted kidney that has stopped working, as the physician documents it. Terms such as “graft failure”, “allograft failure” and “loss of graft function” all point here. The code stays the same whether the failure is described as acute or chronic.

T86.12 does not cover these situations:

• Rejection of the transplanted kidney without documented failure. Use T86.11.
• Infection of the transplanted kidney. Use T86.13, plus a code for the infection.
• Chronic kidney disease in a transplant patient with no complication documented. Use N18.- by stage, plus Z94.0.
• Complications of other transplanted organs. Use the organ-specific code in category T86.
• Post-transplant lymphoproliferative disorder. Report D47.Z1 as its own additional code.

Labs and imaging alone never support the code. A rising creatinine or a falling GFR helps the physician reach a diagnosis. The coder, however, needs the diagnosis itself written in the record.

Walk the chart: What a failure diagnosis needs

The coder’s job is to translate the physician’s words, not to infer a diagnosis. For T86.12, the chart needs a clear statement that the graft has failed or lost function.

Work through the note in this order:

1. The diagnosis statement: Look for “failure”, “graft loss” or “loss of function” in the physician’s assessment, discharge summary or problem list.
2. The link to the transplant: Confirm the physician ties the loss of function to the transplanted kidney, not to a separate condition.
3. Rejection wording: If the note says “rejection” and nothing about failure, you are looking at T86.11, not T86.12.
4. Supporting findings: Biopsy results, creatinine trends and a return to dialysis support the diagnosis. They do not replace it.
5. Related conditions: Note any documented CKD stage, dialysis dependence and long-term immunosuppressant use for the secondary codes.

Here is a quick example. A patient six years after transplant returns with poor graft function. The nephrologist writes “chronic allograft failure, restarting hemodialysis.” That supports T86.12, with N18.6 and Z99.2 when ESRD and dialysis dependence are documented.

Now compare a second patient. The note says “stable CKD stage 3a after kidney transplant” and names no complication. That chart supports N18.31 and Z94.0. It does not support T86.12.

Codes that often travel with T86.12

T86.12 rarely goes out alone. The table below lists the secondary codes you will see most, and when each one belongs on the claim.

Sequence T86.12 first when the graft failure is the reason for the encounter. When another condition drives the visit, that condition goes first and T86.12 follows. Before you submit, check current notes in AAPC’s ICD-10-CM lookup and the CDC/NCHS ICD-10-CM browser tool.

The guideline that decides failure versus CKD

The Official Guidelines for Coding and Reporting handle this in two places. Section I.C.19.g.3.b covers kidney transplant complications. It says T86.1- is assigned for documented complications, such as transplant failure or rejection.

The same section adds a limit that matters for T86.12. A kidney transplant may not fully restore kidney function, so CKD after a transplant is expected. T86.1- is not assigned for that CKD unless a complication such as failure is documented.

Section I.C.14.a.2 says the same thing from the CKD side. It directs you to code the CKD stage with N18 and add Z94.0. Both sections end the same way: when it is unclear whether a complication exists, query the provider.

Two more rules apply to uncertain wording. Inpatient coding may report a diagnosis documented as “probable” or “suspected” at discharge. Outpatient coding may not, so “possible graft failure” on a clinic note does not support T86.12. Read the current-year CMS ICD-10-CM guidelines for the full text, since sound medical billing compliance depends on applying them every time.

How a T86.12 claim moves, and what trips it up

A T86.12 claim passes through the same stages as any other diagnosis claim. Each stage has its own failure point.

1. Charting: The physician documents the encounter. A note that says “rejection” when the team means “failure” sends the wrong code downstream.
2. Coding: The coder picks the T86.1 sibling and the secondary codes. This is where CKD alone gets miscoded as graft failure.
3. Scrubbing: Claim edits check code validity and CPT pairings. A missing CKD stage or an invalid code stops the claim here.
4. Payer review: The payer may ask for records. A chart without an explicit failure statement will not hold up.
5. Remittance: The electronic remittance advice file shows any adjustment or denial codes, so your team can see what went wrong.

These are the mistakes that show up most often at those stages. A steady denial management workflow catches them before they repeat.

Before you submit: A T86.12 checklist

Run through these checks before the claim leaves your system. Each one takes seconds and removes a common cause of rework.

• The physician’s note states failure, graft loss or loss of function in plain words.
• The failure is tied to the transplanted kidney, not to another condition.
• Rejection or infection, if documented, has its own code, T86.11 or T86.13.
• Any documented CKD stage is coded with the matching N18.- code.
• Dialysis dependence (Z99.2) and immunosuppressant use (Z79.6-) are added when documented.
• Z94.0 is added where your payer or facility policy asks for it.
• T86.12 is sequenced first when graft failure is the reason for the encounter.
• Uncertain wording on an outpatient note has been queried, not coded.

A clean claim passes all eight checks and still carries the right CPT codes for the services billed.

CPT codes commonly billed with T86.12

Graft failure encounters bring a familiar set of procedure codes. The exact mix depends on the setting and on whether a biopsy or dialysis is involved. Logging each service with its diagnosis in your claims management software makes every pairing easy to check.

Check every CPT and ICD-10 pairing against current National Correct Coding Initiative edits before submission. Payer edits can also differ from the national set.

How Pabau helps you get T86.12 right the first time

Most T86.12 errors start with a coder reading a note in one system and building a claim in another. The wording that separates failure from rejection gets lost between the two.

Pabau, the practice management and billing platform we build, keeps the clinical note, the diagnosis codes and the claim on the same patient record. Your coder can check the physician’s exact wording before the claim is built. Claims then go out electronically through our Claim.MD integration, and remittance data comes back to the same record.

The result is fewer claims that go out with the wrong T86.1 sibling, and faster fixes when a payer does push back.

Catch T86.12 coding errors before the claim goes out

Pabau keeps the physician note, the codes and the claim in one place. Your team can check the diagnosis wording before billing and send claims electronically via Claim.MD.

Book a demo

Conclusion

T86.12 turns on one word in the chart. When the physician documents failure or loss of graft function, the code fits. When the note says rejection, infection or stable CKD, a different code tells the story better.

So build the habit of reading the assessment before you open the code set. Query early when the wording is unclear, because a two-minute query costs less than a denied claim. Book a demo to see how Pabau keeps notes and claims together for your transplant patients.

Continue your research

Need to understand the clearinghouse that routes your T86.12 claims? Claim.MD clearinghouse guide explains how electronic claim submission and ERA processing work for US medical practices.

Want a structured framework for managing transplant claim denials? Denial codes in medical billing covers the remittance advice codes that appear when payers deny T86.12 and related transplant claims.

Building a clean-claim checklist for nephrology? Superbill guide for medical practices walks through the coding fields, including secondary diagnoses, that an encounter should capture before billing.

Does the note say rejection rather than failure? ICD-10 code T86.11 covers kidney transplant rejection and the wording that supports it.

No complication type named in the chart? ICD-10 code T86.10 explains when the unspecified kidney transplant code applies.

Frequently asked questions