ICD code T86.93 – Unspecified transplanted organ and tissue infection

Key Takeaways

T86.93 is the billable ICD-10-CM code for an infection of a transplanted organ or tissue when the record never names the transplant site

The code already specifies the complication as infection, so the only unspecified element is which organ or tissue was transplanted

Bone marrow transplant infections belong to T86.03 and stem cell transplant complications to T86.5, never to T86.93

T86.93 carries a use additional code instruction to specify the infection, so a second code almost always belongs on the claim

Pabau’s claims management software flags T86.93 claims that reach the payer without the transplant site or organism documented

ICD-10 code T86.93: Quick reference

T86.93 sits within Chapter 19 of ICD-10-CM (Injury, poisoning and certain other consequences of external causes), under category T86 (Complications of transplanted organs and tissue). The table below covers the reference data coders need before building a claim.

According to the CMS ICD-10 codes page, T86.93 has been a valid, billable code since ICD-10-CM took effect in October 2015. Coders can confirm current-year status using the CDC/NCHS ICD-10-CM web tool.

What T86.93 covers: Code definition and clinical scope

T86.93 reports an infection involving a transplanted organ or tissue where the documentation does not identify which organ or tissue was transplanted. The complication type is settled, because the code names infection. The transplant site is the part the record leaves open.

That reading reverses what most coders assume when they first meet the code. The word “unspecified” in the T86.9 subcategory attaches to the graft, not to the complication. Every T86.9x code describes an unspecified transplanted organ and tissue, then names a different complication.

Because ICD-10-CM already supplies an infection code for each transplant site, T86.93 should be rare in a well-documented chart. It is the fallback the classification provides when the note records a graft infection without recording the graft.

• Site named in the record: Assign the site-specific infection code, such as T86.13 for a kidney transplant or T86.43 for a liver transplant
• Site absent from the record: T86.93 applies, and a physician query is the correct next step before the claim goes out
• Infection organism known: Add the code that specifies the infection, following the use additional code note at T86.93
• Graft function unaffected: A T86 code is assigned only where the complication affects the transplanted organ, per the ICD-10-CM official guidelines

One point of confusion deserves naming early. T86.93 is not a bone marrow transplant code, and neither are T86.90, T86.91 or T86.92. Bone marrow transplant complications sit in the separate T86.0x subcategory, which the next sections cover in detail. For background on medical billing fundamentals in complex specialty care, Pabau’s reference guide covers the wider workflow context.

Instructional notes that apply to T86.93

T86.93 carries no Excludes1 or Excludes2 note of its own. What it does carry are instructional notes at three levels of the tabular list, and each one changes what else belongs on the claim.

The Z94 rule catches a surprising number of transplant claims. Post-transplant charts often default to a status code such as Z94.0, and the status code survives into the claim after the complication code is added. Strip it out before submission. The same notes play out differently once the graft is named. See the guide to ICD-10 code T86.19 for other complications of kidney transplant.

T86.90, T86.91, T86.92 and T86.99 vs T86.93: Choosing within the subcategory

The T86.9 subcategory holds five codes. All five describe a transplanted organ or tissue that the record does not identify. What separates them is the complication reported.

The practical rule runs in two steps. First ask whether the record names the transplanted organ or tissue, because a named graft moves the claim out of T86.9 entirely. Then ask which complication the physician documented, which selects the final character.

Coders who work the second question first tend to land on T86.93 far more often than the chart supports. For additional ICD-10-CM diagnostic code references, Pabau’s coding library covers a range of specialty categories.

Documentation requirements for ICD-10 code T86.93

Using T86.93 without adequate documentation is the fastest route to a records request on transplant claims. The physician record must support three elements before the code can be assigned.

1. A prior transplant is confirmed: The record must establish that the patient received a transplanted organ or tissue. Transplant date and procedure details should appear somewhere in the chart, even where the operative site is missing from this encounter’s note.
2. The infection involves the graft and affects its function: Culture results, imaging, or the physician’s statement must tie the infection to the graft. A post-transplant infection that leaves graft function intact does not belong in T86.
3. The transplant site is genuinely absent: Search the chart before assigning T86.93. Where the operative report, problem list, or prior encounters name the graft, the site-specific infection code applies instead.

The third element is where most T86.93 assignments fall apart. Auditors routinely find the transplant site recorded elsewhere in the same chart, which converts a valid unspecified code into an unsupported one.

Billers should also confirm that the encounter type is reflected consistently on the claim. T86.9x codes carry no 7th-character extension, so the revenue code, place of service, and supporting documentation have to do that work. Inconsistency between claim fields and the record is a common audit trigger.

Submitting a clean claim on T86.93 requires that the physician’s note and the claim form tell the same clinical story. Anything less invites automatic denial before human review.

Payer requirements and prior-authorization notes

CMS and commercial payers apply extra scrutiny to transplant complication codes, because transplant care is a high-cost service category. T86.93 attracts attention for a further reason: an unspecified transplant site suggests the documentation was thin rather than the clinical picture unclear.

• No national coverage determination targets T86.93: Coverage is governed by the transplant type and the service billed, not by the diagnosis code itself. Check with your Medicare Administrative Contractor (MAC) for Local Coverage Determinations that govern post-transplant follow-up care.
• Specificity requirement: Some payers hold claims that carry an unspecified-site code when the member’s transplant history is already on file. Expect a request for medical records rather than an outright denial, which still delays reimbursement.
• Inpatient grouping: As a principal diagnosis, T86.93 groups to MS-DRG 919, 920 or 921, the complications of treatment family. The split across those three DRGs depends on documented MCC and CC conditions, so secondary diagnoses matter to payment.
• HCC risk adjustment: Whether T86.93 carries Hierarchical Condition Category value varies by CMS-HCC model year. HCC mapping changes annually, so verify against the current CMS-HCC tables before assuming capture.

Understanding medical billing compliance guidelines for specialty categories helps transplant programs set correct payer expectations before claims are submitted. See also procedure codes for specialized care for a parallel example of how payer documentation expectations differ in complex specialty billing.

Common claim denial reasons for T86.93

T86.93 denials cluster around four root causes. Each has a specific coder action that resolves the underlying problem rather than simply resubmitting the same claim.

Structured denial management strategies applied systematically to T86.93 claims stop the same errors from recurring across the transplant program’s billing cycle. Read denial codes in medical billing alongside the patterns above. The CARC and RARC codes on a remittance then map onto the root causes in this table.

Reduce transplant complication claim denials with Pabau

Pabau’s integrated claims management flags incomplete documentation on codes like T86.93 before submission, helping transplant and specialty practices reduce avoidable denials and speed up reimbursement.

Book a demo

Code sequencing rules: When T86.93 is principal vs secondary

The ICD-10-CM official guidelines for transplant complications require two codes to describe the event fully. The T86 code comes first, followed by a code that identifies the complication. For T86.93 that second code specifies the infection.

Inpatient sequencing

Under UHDDS guidelines, the principal diagnosis is the condition established after study to be chiefly responsible for the admission. T86.93 can lead when the patient is admitted to treat a graft infection and no other condition better explains the admission.

T86.93 becomes a secondary code when a different condition drove the admission. Sepsis is the common example: the sepsis code leads, and T86.93 records the transplant infection that produced it. Both codes belong on the claim in that scenario.

Outpatient sequencing

For outpatient encounters, ICD-10-CM directs coders to report the condition chiefly responsible for the visit. Where no condition is established, the sign or symptom is reported instead. T86.93 can lead on an outpatient claim when the visit exists to manage the graft infection.

Sequencing rules apply the same way across Chapter 19. The other ICD-10 diagnosis code guides in Pabau’s coding library work through the decisions in other categories.

Site-specific infection codes and other adjacent T86 codes

Almost every T86.93 assignment has a better alternative waiting in the same category. ICD-10-CM supplies an infection code for each named transplant site, and the table below lists them.

Bone marrow and stem cell transplants are not coded to T86.9x

This is the single most consequential miscoding pattern around T86.93. Hematopoietic stem cell transplant patients are frequent users of transplant complication codes, which tempts coders toward the T86.9x block.

ICD-10-CM keeps those complications elsewhere. Bone marrow transplant complications run from T86.00 through T86.09, with T86.03 for infection. T86.5 covers complications of stem cell transplant. Neither route passes through T86.9x, which exists only for grafts the record does not name.

Graft-versus-host disease and other use additional codes

Graft-versus-host disease is coded from D89.81-, and the note at category T86 asks coders to add it alongside the transplant complication code. GVHD does not replace T86.93, and T86.93 does not replace GVHD. Where both are documented, both are reported.

• D89.810, D89.811, D89.812, D89.813: Acute, chronic, acute-on-chronic and unspecified graft-versus-host disease
• C80.2: Malignant neoplasm associated with transplanted organ, added when a post-transplant malignancy is documented
• D47.Z1: Post-transplant lymphoproliferative disorder, a recognized complication of long-term immunosuppression

The AAPC ICD-10-CM lookup provides a useful cross-reference for the boundaries between these code families. For a free verification check, the ICD List lookup tool mirrors official CMS and NCHS data and flags valid versus invalid codes.

How practice management software streamlines transplant complication coding

Practices billing T86.93 usually lose revenue for a documentation reason rather than a coding one. The transplant site or the infection detail never reaches the claim, and nothing in the workflow catches it. An integrated billing platform closes that loop.

• Pre-submission claim scrubbing: Pabau’s claims management software flags T86.93 submissions that lack supporting documentation. The most common denial trigger is caught before the claim reaches the payer.
• ICD-10 code lookup built in: Coders search, verify, and assign codes inside the same platform used for scheduling and records. The site-specific alternative to T86.93 is one search away.
• Clearinghouse integration: Pabau integrates with Claim.MD clearinghouse integration, routing claims to thousands of US payers. Real-time eligibility checks and electronic remittance advice tell practices within hours whether a T86.93 claim has cleared.
• Denial tracking and workflow: Claims denied on T86.93 are logged with the CARC code and routed to the correct coder. Nothing sits unresolved in a denial queue. The medical claims clearinghouse workflow guide explains how this loop closes in practice.

High-volume post-transplant billing lives or dies on handoffs between the clinical note and the claim. Documentation prompts and claim scrubbing in the same system remove most of those handoff errors.

Conclusion

T86.93 is a valid, billable code with a narrow job: Reporting an infection of a transplanted organ or tissue that the record never names. The complication is specific, and only the graft site is missing.

Most claims that carry it should have carried a site-specific code such as T86.03, T86.13 or T86.43 instead. Adding the code that specifies the infection, sequencing against UHDDS guidance, and dropping the Z94 status code resolve the rest.

Pabau’s integrated claims management builds those checks into the billing workflow. T86.93 claims then reach the payer with the documentation they need. To see how it works for your program, book a demo with the team.

Continue your research

List Item #1

List Item #2

Frequently asked questions