ICD code T86.858 – Other complications of intestine transplant

Key takeaways

ICD-10 Code T86.858 is a billable, specific code for other (NEC) complications of intestine transplant, valid for FY2026 HIPAA-covered transactions.

It sits under parent code T86.85 (Complication of intestine transplant) and is distinct from rejection (T86.850), failure (T86.851), infection (T86.852), and unspecified (T86.859).

Use T86.858 only when the physician documents a specific complication that is not rejection, failure, or infection. T86.859 applies when the complication type is never stated.

Claims management software like Pabau’s connects the coded diagnosis to submission, so transplant teams catch specificity problems before the claim goes out.

ICD-10 Code T86.858: Definition and billable status

ICD-10 Code T86.858 is a specific, billable ICD-10-CM code for documented post-intestinal-transplant complications that the other T86.85x codes do not capture.

The CMS ICD-10-CM code set confirms T86.858 as valid for all HIPAA-covered electronic transactions in FY2026. The National Center for Health Statistics (NCHS) maintains that list and revises it every year.

“Billable/specific” in ICD-10-CM terminology means the code is granular enough for claim submission. Parent codes such as T86.85 cannot be billed on their own. Coders have to select a fifth-character extension, and T86.858 is that extension for the NEC category.

ICD-10 hierarchy: Where T86.858 sits

T86.858 belongs to the Injury, Poisoning and Certain Other Consequences of External Causes chapter (S00-T88) of ICD-10-CM. Knowing its position in the tree stops coders from billing a non-billable parent code.

It also stops them reaching for a transplant complication code that belongs to another organ. Our ICD-10-CM code reference follows the same parent-to-child logic across every chapter.

Sibling codes in the T86.85x subcategory

Five codes share the T86.85 parent, and selecting the wrong one is the most frequent error on intestine transplant cases. Each code maps to a distinct, mutually exclusive clinical condition. Where the documentation supports rejection, failure, or infection, T86.858 is incorrect however similar the clinical picture looks.

The order you rule those categories out in is what decides the code. Work down the subcategory: rejection first, then failure, then infection, and only then the NEC and unspecified codes. The path below shows where each documented condition lands.

What “other complications” means in T86.858

“Other complications” in ICD-10-CM terminology means “not elsewhere classified” (NEC). The physician has documented a specific complication, but it does not match the named conditions in T86.850, T86.851, or T86.852.

The complication is known and written down, and it simply falls outside those three categories. That is the distinction from T86.859, where the complication type is never stated.

According to the CDC/NCHS ICD-10-CM web tool, the approximate synonyms for T86.858 include “intestine transplant complications NEC.” Clinical contexts that may qualify include graft-versus-host-related manifestations limited to the intestinal graft.

Post-transplant lymphoproliferative disorder localized to the transplanted segment also qualifies, as does chronic allograft enteropathy that is not specified as rejection.

Applying T86.858 to small bowel or multivisceral transplant cases takes physician documentation that explicitly links the complication to the transplanted organ. Where the clinical mapping is uncertain, confirm the assignment against AHA Coding Clinic before the claim is built.

• Applies to: small bowel (intestinal) transplant complications NEC
• Applies to: multivisceral transplant complications NEC where the intestine is the documented primary transplanted organ
• Does not apply to: rejection (use T86.850), failure (use T86.851), infection (use T86.852), or a complication the physician has not characterized (use T86.859)

T86.858 vs T86.859: Choosing the right code

T86.858 applies when a specific complication is documented. T86.859 applies when no complication type is stated at all. The distinction carries direct reimbursement consequences. Payers scrutinize unspecified codes on high-acuity transplant cases, and a T86.859 claim submitted without a physician query may trigger a medical necessity review.

When to use T86.858: Clinical scenarios

Intestine transplantation is performed for patients with irreversible intestinal failure, most commonly short bowel syndrome. Post-transplant follow-up produces a range of complications that transplant center coders see regularly. Each documented complication has to be matched to the most specific available code before the claim is built.

T86.858 applies in these scenarios:

• Chronic allograft enteropathy documented by the transplant physician as a distinct complication, without a finding of active rejection on biopsy
• Post-transplant lymphoproliferative disorder (PTLD) localized to the transplanted intestinal segment, where the physician links it to the transplant rather than to a systemic condition
• Graft dysmotility or functional complications documented as a transplant complication and not attributed to failure or rejection
• Anastomotic complications such as stricture or leak, explicitly attributed to the intestinal transplant and short of graft failure
• Multivisceral transplant cases where the intestinal component generates a documented complication NEC that is distinct from the other transplanted organs

In each scenario the physician’s note has to name the complication and link it to the transplant. It also has to sit outside the definitions of rejection, failure, and infection. Where the documentation is ambiguous, query the physician before assigning T86.858.

Documentation requirements for T86.858

Documentation is what separates a clean T86.858 claim from one that defaults to T86.859 or comes back for more information. Three elements have to be present in the physician’s note.

• Named complication: The physician has to identify the specific type of complication in a diagnosis statement or impression. “Intestine transplant complication” on its own does not support T86.858. The complication must be named, for example “chronic allograft enteropathy” or “anastomotic stricture attributable to the intestinal transplant”.
• Causal link to the transplanted organ: The note has to connect the complication to the intestine transplant rather than to an unrelated condition. Co-existing diagnoses are coded separately where applicable.
• Exclusion of more specific categories: The documentation should indicate, explicitly or by clinical context, that the complication is not rejection, failure, or infection. Biopsy results, laboratory values, and the clinical reasoning that rules those categories out all support T86.858 over its siblings.

Where documentation is incomplete, AHIMA guidelines recommend a physician query rather than a default to an unspecified code. Submitting T86.858 on the strength of an informal conversation rather than a signed attestation raises audit risk.

Common coding errors to avoid

Intestine transplant complication coding produces predictable errors across transplant centers. Catching them in a pre-submission review costs far less than working them on appeal.

• Defaulting to T86.859 when T86.858 is documented: Where the physician has named a complication that is not rejection, failure, or infection, T86.859 is incorrect. Query the physician if the complication type is unclear, rather than dropping to the less specific code.
• Using T86.858 when a more specific code applies: If biopsy or lab findings support rejection (T86.850), failure (T86.851), or infection (T86.852), those codes take precedence. T86.858 is not a fallback when documentation for a named sibling code is present.
• Omitting the additional code for the specific complication: T86.858 identifies the transplant context only. ICD-10-CM instructs coders to use an additional code for the complication itself, such as D47.Z1 for post-transplant lymphoproliferative disorder.
• Incorrect sequencing: Whether T86.858 is principal or secondary depends on the circumstances of admission, per ICD-10-CM Official Guidelines Section I.C.19. There is no universal sequencing rule. The principal diagnosis is the condition established after study to be chiefly responsible for the encounter.
• Applying T86.858 to non-intestine transplant cases: This code is specific to intestine transplants. Kidney (T86.1x), liver (T86.4x), and heart (T86.2x) transplant complications have their own subcategories. Cross-checking the organ against the code category prevents misassignment at category level.

Related ICD-10 codes to know

Transplant coordinators and coders working intestine transplant cases meet the full T86.85x family, plus the broader T86 codes for other transplanted organs. The AAPC ICD-10-CM code lookup displays the whole T86 hierarchy for cross-reference.

Submitting and managing T86.858 claims

Once the code is selected and the documentation supports it, the submission workflow matters as much as the coding decision. Transplant complication claims are high-acuity encounters, and payers review them closely for medical necessity and diagnostic specificity.

Submitting through a clearinghouse with a built-in ICD-10 catalog reduces the format errors that hide a valid code at the payer’s front door. A rejected file never reaches an adjudicator, so the coding work behind it counts for nothing.

Meeting clean claim standards on a transplant encounter takes three checks before the file goes out:

• Confirm the principal diagnosis sequencing follows the ICD-10-CM Official Guidelines.
• Verify that the additional code for the specific complication is included where it is required.
• Confirm the ICD-10-CM code version matches the fiscal year of the service date.

Code history and FY2026 validity

T86.858 has been valid in the ICD-10-CM tabular list since the system was implemented in the United States, with no substantive description changes through FY2026. The CMS ICD-10-CM FY2026 update files confirm that the code is still active.

Check validity every year, because CMS and NCHS release updates each October for the new fiscal year. Codes can be deleted, revised, or have their descriptions amended.

How Pabau supports transplant coding and claim submission

Most transplant centers keep the clinical note in one system and the claim in another. A coder reads the note, assigns T86.858 or one of its siblings, and rekeys the code into a separate billing tool. Specificity gets lost at each hand-off, and the physician query that would have fixed it arrives after billing has closed.

Pabau is practice management software that holds the documentation and the claim in one patient record. Pabau’s claims management software carries the coded diagnosis from the encounter into the claim itself. The code the physician’s note supports is the code the payer receives.

Its pre-submission review flags sequencing problems, a missing additional complication code, and a code version that predates the service date. Coders spend less time reworking transplant claims after a denial, and coordinators can see which encounters are still waiting on a query.

Streamline transplant billing with built-in coding support

Pabau connects your clinical documentation to claims submission. Transplant coordinators and coding teams can send ICD-10 Code T86.858 and its siblings with the right specificity.

Book a demo

Conclusion

Intestine transplant complication coding comes down to one question. Has the physician named a complication that is not rejection, failure, or infection? If the answer is yes, ICD-10 Code T86.858 is the correct choice over T86.859.

Where the note is ambiguous, raise the query before billing closes. A query costs a coder minutes, while an unspecified code on a high-acuity transplant claim can cost a whole review cycle. Book a demo to see how Pabau keeps transplant documentation and claim submission in one record.

Continue your research

Need to understand how denial patterns affect transplant claims? Denial management in healthcare covers the most common denial reasons and the pre-submission review that catches coding errors early.

Want to see how clearinghouse submissions work in practice? Claim.MD clearinghouse explains how Pabau’s US clearinghouse integration processes 837P claims, checks eligibility, and returns ERA data.

Looking for a primer on the full billing cycle? What is medical billing walks through the process from diagnosis coding to payment posting, and where specificity decisions bite hardest.

Frequently asked questions