ICD code T86.90 – Unspecified complication of unspecified transplanted organ and tissue

Found our content helpful?

Key takeaways

ICD-10 code T86.90 is a billable FY2026 code for unspecified complication of unspecified transplanted organ and tissue, effective October 1, 2025.

Use T86.90 only when the record names neither the transplanted organ nor the complication type. Look for a more specific T86.x code first.

T86.90 is not on the CMS POA-exempt list. Inpatient claims must carry an actively assigned POA indicator of Y, N, W, or U.

Never report a Z94.x transplant status code with a T86 complication code for the same organ. An Excludes1 note at Z94 blocks that pair.

The category’s use additional code note calls for D89.81-, C80.2, or D47.Z1 whenever one of those conditions is documented.

ICD-10 code T86.90: Definition and billable status

ICD-10 code T86.90 is the billable diagnosis code for a complication in a transplant recipient. It applies when the record names neither the organ nor the type of complication. Both elements are unspecified, which places the code at the broadest level of the T86 category.

Billable means the code is complete as written and can stand as a diagnosis on a submitted claim. It does not mean the code is a good choice. T86.90 passes a format edit and still invites a documentation request from the payer.

Quick reference: T86.90 code details

Where T86.90 sits in the ICD-10-CM hierarchy

T86.90 descends from chapter 19 through the T80-T88 block, which covers complications of surgical and medical care not classified elsewhere. The T86 category then splits by organ, and the T86.9 subcategory holds the codes used when the organ is unknown.

• S00-T88: Injury, poisoning and certain other consequences of external causes
• T80-T88: Complications of surgical and medical care, not elsewhere classified
• T86: Complications of transplanted organs and tissue
• T86.9: Complications of unspecified transplanted organ and tissue
• T86.90: Unspecified complication of unspecified transplanted organ and tissue

The T86.9 subcategory contains five billable codes. Four of them name a complication type, and only T86.90 leaves the complication unstated.

When to use ICD-10 code T86.90

T86.90 is appropriate when two facts are missing from the clinical record at the same time. Those two facts are the organ transplanted and the nature of the complication. Meeting only one of those conditions calls for a different code, as the grid below sets out.

• Both organ and complication unspecified: The note states “post-transplant complication” without identifying the organ or specifying rejection, failure, or infection. T86.90 is the correct code.
• Organ known, complication unspecified: Do not use T86.90. Use the organ-specific unspecified code, such as T86.10 for unspecified kidney transplant complication.
• Organ unspecified, complication known: Do not use T86.90. Use T86.91, T86.92, T86.93, or T86.99, depending on which complication the physician documented.
• Both organ and complication known: T86.90 is never appropriate. Assign the most specific T86.x code available.

In practice, T86.90 should work as a temporary placeholder pending a physician query, not a routine assignment. The CMS ICD-10-CM coding resources reinforce that coders must assign the highest level of specificity the documentation supports. Using T86.90 on a final coded record without a query attempt signals a missed CDI opportunity.

T86.90 is not POA exempt, so an inpatient claim carrying it still needs an actively assigned present-on-admission indicator. Facilities that assume otherwise leave the field blank and collect clearinghouse edits.

T86.90 vs. more specific transplant complication codes

The T86 category contains organ-specific and complication-specific codes at every level. The table below maps T86.90 against the siblings coders confuse it with most often.

The distinction between T86.90 and T86.99 trips up many coders. Under ICD-10-CM conventions, “.90” means both dimensions are unspecified. “.99” means the complication type is known while the organ remains unspecified.

Assigning T86.99 when only the organ is documented would be equally incorrect. The CDC/NCHS ICD-10-CM tool exposes the full T86 hierarchy for verification, and our ICD-10-CM code index collects the neighboring transplant entries.

Approximate synonyms and alternate terms

Documentation rarely uses the code’s official wording. The phrases below all map to T86.90 when neither the organ nor the complication type appears anywhere in the record.

• Post-transplant complication, unspecified
• Complication of transplanted organ, organ not stated
• Transplant-related problem, type not documented
• Graft complication, unspecified site
• Complication of transplanted tissue, not otherwise specified

Treat each of these as a query trigger rather than a coding answer. If the chart names the graft anywhere, the organ-specific code replaces T86.90.

Excludes notes and the Z94 transplant status conflict

Z94.x transplant status codes are not companion codes for T86.90. The tabular list places an Excludes1 note at Z94 reading “complications of transplanted organ or tissue – see Alphabetical Index”. An Excludes1 note means the two codes are never reported together for the same organ.

The logic behind the note is straightforward. A Z94 code reports a functioning graft with no complication. A T86 code reports a graft that has developed one. The same organ cannot be both at the same encounter.

Section I.C.21.c.3 of the ICD-10-CM Official Guidelines makes the same point from the other direction. A status code is not assigned when another code on the claim already carries the information it would supply. Once T86.90 establishes that the patient has a transplanted organ, the status code adds nothing.

For T86.90 the rule bites harder still. Assigning a Z94 code means you know which organ was transplanted. Once the organ is known, the organ-specific T86.1x through T86.8x entry replaces T86.90.

The Z94 codes below are the status codes coders most often reach for. Use them when a functioning graft is documented and no complication of that graft is present at the encounter.

Two exceptions survive the note. It applies organ by organ, so a patient may carry a status code for one organ and a complication code for another. Guideline I.C.14.a.2 also directs coders to report Z94.0 with the appropriate N18 code when chronic kidney disease persists after a kidney transplant.

Additional codes the T86 category requires

The T86 category carries a “use additional code” instruction, and that note is where a second code on the claim comes from. It directs coders to identify other transplant complications present at the encounter, naming three in particular.

Guideline I.C.19.g.3 explains the structure. T86 codes are combination codes that carry the transplant complication itself, so the second code identifies the specific condition rather than the transplant history. Where a malignancy is coded with C80.2, an additional code for the specific malignancy is also reported.

If none of these conditions is documented, T86.90 stands alone. Nothing in the tabular list requires a second code for a complication that has not been described.

ICD-10-CM coding guidelines for transplant complication codes

The FY2026 ICD-10-CM Official Guidelines for Coding and Reporting govern the whole T86 category. Four conventions matter most when T86.90 is on the record.

• Complication must affect graft function: A T86 code is assigned only when the documented condition affects the function of the transplanted organ. A condition unrelated to the graft is coded on its own.
• Use additional codes: Report D89.81-, C80.2, or D47.Z1 when those conditions are documented, per the category’s instructional note.
• Excludes1 restrictions: Z94.x status codes for the same organ are blocked by the Excludes1 note at Z94. Read the notes printed at T86 and at T80-T88 before finalizing any assignment.
• Sequencing: When the transplant complication is the reason for the encounter, the T86 code is the principal diagnosis. When it is incidental to a different encounter, it is reported as an additional code.
• 7th character extension: T86 codes take no 7th character. The five-character code T86.90 is complete as written.

Practices submitting claims electronically should confirm that T86.90 clears their clearinghouse edits before final submission. A claim passes cleanly when the code is valid, sequenced correctly, and carrying a POA indicator where the setting requires one.

The AAPC ICD-10-CM code reference works as a secondary check on billable status and guideline notes alongside the official tabular list.

MS-DRG mapping for T86.90

On inpatient claims, T86.90 runs through the CMS IPPS grouper like any other diagnosis. The DRG that results depends on the principal diagnosis and on the complications documented during the same stay.

Under MS-DRG v43.0, T86.90 groups to DRG 919, DRG 920, and DRG 921. Those are complications of treatment with MCC, with CC, and without CC or MCC. All three sit in MDC 21, injuries, poisonings and toxic effects of drugs.

Relative weights move every year with the IPPS final rule, so read the FY2026 figure from the current CMS MS-DRG Definitions Manual. Check Appendix C of that manual for the code’s CC or MCC designation as a secondary diagnosis, along with its exclusion list.

Present on admission (POA) indicator

T86.90 does not appear on the CMS POA exempt code list. The exempt list has not carried any T86 code across FY2023 through FY2026, and no addition, deletion, or revision file has changed that.

POA reporting is therefore required on every inpatient claim that carries T86.90. The coder assigns one of four values based on what the record shows.

• Y: The complication was present at the time the inpatient admission order was written.
• N: The complication developed after admission.
• W: The provider cannot clinically determine whether the complication was present on admission.
• U: The documentation is insufficient to decide, which should prompt a query rather than a submission.

The blank or “1” value reserved for exempt codes is not available here. A transplant recipient admitted with a complication usually warrants Y, but the timing has to come from the record rather than from the diagnosis.

ICD-9-CM crosswalk: Legacy code equivalent

Practices running legacy systems, or comparing pre-2015 claims against current data, need the approximate ICD-9-CM equivalent. The mapping is not exact, because ICD-10-CM encodes more detail than ICD-9-CM could hold.

ICD-10-CM replaced ICD-9-CM for US payers on October 1, 2015. No ICD-9-CM code has been billable on a primary claim since that date, so the crosswalk serves trend analysis rather than submission.

Documentation requirements and physician query guidance

T86.90 signals incomplete documentation. CDI specialists should treat its presence on a working record as a query trigger, not a final answer. The query should happen before the record is coded and closed, not after a denial arrives.

That sequencing changes what the claim is worth. A query submitted before claim submission can change the code assignment, improve the inpatient DRG, and prevent a denial. A query submitted after a denial requires a corrected claim, appeals processing, and a payment delay measured in weeks.

Query triggers for T86.90

Consider a physician query when any of the following appears in the clinical record alongside a transplant complication note.

• The documentation mentions a “post-transplant complication” or “transplant-related issue” without naming the organ.
• Labs or imaging suggest organ-specific dysfunction, such as rising creatinine consistent with kidney rejection, but the note uses generic language.
• The patient’s history documents a prior transplant, but the attending’s note for this encounter omits the organ.
• The complication is described clinically, as “graft dysfunction” or “acute rejection episode”, without a diagnosis the tabular list recognizes.
• Multiple transplants appear in the patient’s history, leaving the affected organ ambiguous.

Per AHIMA and AAPC query practice standards, queries must be compliant. They should not lead the physician, must offer multiple response options including “clinically unable to determine”, and must be documented in the medical record.

A compliant query that produces a specific diagnosis, such as kidney transplant rejection, lets the coder move from T86.90 to T86.11. That is a materially different code for reimbursement and quality reporting.

Common coding errors with T86.90

Several patterns of misuse appear consistently in transplant complication audits. Recognizing them reduces denials and improves specificity before the billing cycle closes.

• Using T86.90 when a specific code is available: The most common error. If the chart documents kidney rejection anywhere, T86.11 or T86.12 applies. Reserve T86.90 for records where specificity cannot be obtained without a query.
• Adding a Z94 status code alongside T86.90: The Excludes1 note at Z94 blocks that pairing for the same organ. Reporting both invites an edit rejection. It also tends to reveal that an organ-specific T86 code was available all along.
• Confusing T86.90 with T86.99: T86.99 covers other complications when the organ is unspecified but the complication type is known. Using T86.99 for a genuinely unspecified complication is a convention error, and so is the reverse.
• POA indicator errors: T86.90 is not POA exempt, so the indicator cannot be left blank or reported as exempt. Assign Y, N, W, or U from the documentation. A missing value triggers an edit failure at the clearinghouse.
• Omitting a required additional code: When GVHD, transplant-associated malignancy, or PTLD is documented, the category’s instructional note requires D89.81-, C80.2, or D47.Z1 as well.
• No query documentation: Using T86.90 as a final code without a documented query attempt, or a rationale for why specificity was unavailable, creates audit exposure.

Facilities with high volumes of T86.90 on final coded records should examine whether their query workflows are working as intended. A compliance program that flags the code automatically for CDI review catches most of them before submission.

Unspecified diagnosis codes rank among the top denial triggers for transplant-related encounters, so denial management work pays off fastest here.

How Pabau supports transplant complication coding

Accurate transplant complication coding depends on capturing the right clinical detail at the point of care, not retrospectively.

Pabau, practice management software for healthcare practices, puts ICD-10 code selection inside the clinical encounter. The coder then works from the detail the physician has just recorded, using our claims management software.

For US practices, the clearinghouse connection validates ICD-10 codes against payer edits before the claim leaves the building. An unspecified assignment such as T86.90 surfaces while the encounter is still fresh. The coder can then chase the missing organ or complication detail from the physician who wrote the note.

Remittance data flows back into the same record, so denial patterns tied to unspecified codes stay visible. A billing lead can see where T86.90 keeps appearing and fix the documentation upstream, rather than reworking one claim at a time.

Manage ICD-10 coding workflows in one place

Pabau’s claims management software supports accurate ICD-10 code selection and documentation workflows. See how Pabau helps coders move from unspecified codes to specific diagnoses before claim submission.

Book a demo

Conclusion

ICD-10 code T86.90 is valid and billable for FY2026, but it should rarely survive to a final coded record. Its correct use is narrow, because both the transplanted organ and the complication type must be genuinely undocumented.

When either element is available, a more specific T86.x code applies. When neither is, a compliant physician query belongs in the record before it closes.

Two details decide whether the claim holds up. T86.90 is not POA exempt, so the inpatient indicator has to be assigned from the documentation. A Z94 transplant status code is not its companion, and pairing the two for the same organ breaks an Excludes1 rule. To see how Pabau supports this workflow across your practice, book a demo with our team.

Continue your research

Wondering which clearinghouse edits catch unspecified codes? Claim.MD clearinghouse overview explains how electronic claim submission works for complex diagnosis codes.

Dealing with unspecified code denials? Denial codes in medical billing covers the most common denial reason codes and how to respond.

Building a CDI review workflow? Medical billing compliance sets out the audit standards a T86.90 assignment has to survive.

Want fewer corrected claims? Clean claim submission walks through what a payer checks before it accepts a claim.

Frequently asked questions