ICD code T87.0X1 – Reattached right upper extremity complications

Key takeaways

T87.0X1 is a complete, billable six-character code for complications of a reattached right upper extremity.

Category T87 takes no 7th character, so T87.0X1A, T87.0X1D and T87.0X1S are invalid codes.

The X in the fifth position is a placeholder, and dropping it (T87.01) makes the claim reject.

The note must show a prior replantation, the right side and a named complication.

Stump problems with no replant belong to T87.3 to T87.5, not T87.0X1.

ICD-10 code T87.0X1 is complete at six characters

ICD-10 code T87.0X1 reports a complication of a reattached part of the right upper extremity. It sits in Chapter 19 (S00-T88), under category T87. Unlike most injury codes in that chapter, it takes no 7th character. The six characters you see are the full, billable code.

That missing 7th character catches out coders who spend their days on injury codes. The structure of the code explains why.

The placeholder X holds the side digit in place

Each character in T87.0X1 has one job. Read left to right, the code narrows from category to side.

The X simply fills the fifth position. That way the side digit always lands sixth, across T87.0X1, T87.0X2 and T87.0X9. Leave it out and T87.01 is not a valid code. Front-end edits reject it before anyone opens the chart.

The opposite slip happens too. Out of habit, a coder may tack on A, D or S. T87.0X1A does not exist, so it rejects just as fast. When you set up an encoder, check its output against the CMS ICD-10-CM code files.

T87.0X1 covers complications after a right arm replant

T87.0X1 applies only when a part of the right upper extremity was surgically reattached. That includes the shoulder, arm, forearm, wrist, hand and individual fingers. Complications the provider links to the reattachment include:

• Necrosis of the replanted part, from skin down to deeper tissue
• Wound dehiscence at the replantation site
• Vascular compromise, arterial or venous, after surgery
• Infection, such as cellulitis involving the reattached part
• Other complications the provider ties directly to the reattachment

The link to the replant decides the code. A note reading “infection, right index finger” with no mention of replantation does not support T87.0X1.

Stump problems and look-alikes belong to other codes

Several similar scenarios sit outside T87.0X1. Coding them here invites denials and audit questions.

• Stump problems with no replant: T87.3- is neuroma of amputation stump, T87.4- is infection of amputation stump, and T87.5- is necrosis of amputation stump.
• Phantom limb syndrome: G54.6 (with pain) or G54.7 (without pain), not a T87 code.
• The original traumatic amputation: S48-, S58- and S68- codes report the acute injury itself.
• Prosthetic and implant complications: T84-T85 cover internal devices.
• Unrelated arm problems: code them separately, since T87.0X1 is no catch-all.

T87.0X1 carries no Excludes1 note. The Excludes2 notes that apply point to birth trauma, obstetric trauma, artificial opening status, burns and corrosions, and other postprocedural complications. Excludes2 means “not included here”, so both codes may appear when both conditions exist.

Neighboring T87 codes change with limb and side

These selected codes from the T87 family follow the same pattern. Most mix-ups happen in the sixth character. A replanted ear, nose or scalp moves to T87.2, which has no side digit at all.

T87.0X9 is valid, but avoid it as a default. Laterality can come from any clinician’s note in the record. If the side is still unclear, query the provider first.

Put together, two questions settle the code. Was the part reattached, and which limb and side does the note name? When the answer points elsewhere, find matching diagnosis codes in our full library.

Sequencing puts T87.0X1 first, then the condition

When the visit is mainly for the replant complication, list T87.0X1 first. Then add a code that names the condition, if T87.0X1 alone does not describe it.

External cause codes are a separate decision. No national rule requires them, although many payers and state data programs ask for them. Where you do report them, pick codes that tell the story:

• Y83.- for a later complication of surgery, with no misadventure at the time of the procedure
• W31.- (contact with other and unspecified machinery), or similar, if the payer wants the original injury mechanism
• Y92.- and Y93.- describe place of occurrence and activity, reported once at the initial injury encounter

That last point matters at follow-up. Place and activity codes rarely belong on a later complication claim, and external cause codes never go first.

A worked example shows the codes in order

Picture a patient whose right index finger was reattached after a table-saw injury. Five weeks later, they come back with redness and swelling at the replant site.

The surgeon writes “cellulitis of the replanted right index finger, status post replantation”. That single line gives the coder the side, the history and the complication. The claim then reads:

1. T87.0X1, first-listed, for the complication of the reattached right upper extremity
2. L03.011, cellulitis of right finger, to name the infection
3. Y83.- or W31.-, only if this payer asks for external cause detail

Notice two absences. T87.0X1 carries no 7th character, and no Y92 or Y93 code appears at this late visit.

Three details in the note support T87.0X1

A coder needs three things before assigning T87.0X1. If any one is missing, query the provider before the claim goes out.

1. The right side is confirmed. “Upper extremity” alone points to T87.0X9 until the side is clarified.
2. The replantation is on record. A line like “status post right thumb replantation” separates T87.0X1 from a stump code.
3. The complication has a name. “Problem with reattached hand” is too vague, while dehiscence, necrosis or infection is clear.

An unclear note deserves a query, not a guess. Tracking queries as part of revenue cycle management shows which notes keep missing the same detail.

How a T87.0X1 claim moves and where it trips up

T87.0X1 does not set the payment. The CPT codes for the treatment do, and T87.0X1 supports their medical necessity. On a CMS-1500 it goes in Box 21, and on a UB-04 in the diagnosis fields.

Next, the claim passes clearinghouse edits, then payer front-end edits, then adjudication. Invalid codes stop it at the first two steps. Documentation problems surface later, as denials or record requests. Revision surgery or vascular repair often needs prior authorization, so check the plan first.

Sorting rejections by trigger, a core habit of denial management, exposes patterns fast. Repeated invalid-code rejections usually mean the EHR mangles the code at export.

Before you submit, run this T87.0X1 checklist

A minute here saves weeks of rework later. Check each point against the chart:

• The code reads exactly T87.0X1, with X in the fifth position and no 7th character.
• The side in the note matches the sixth character, 1 for right.
• The note names both the replantation and the complication.
• A second code names the condition wherever T87.0X1 alone does not.
• External cause codes appear only if the payer wants them, and never first.

Pabau surfaces T87.0X1 rejections while the visit is fresh

Most T87.0X1 trouble starts in the chart and shows up weeks later as a rejection. Pabau, the practice management and billing platform we build, keeps the note, the invoice and the claim in one patient record.

US claims go out electronically through Claim.MD, which returns clearinghouse and payer rejections before adjudication. Your team works those rejections inside Pabau, which makes claims management faster for the billing team. Staff then correct the claim from the same record, so medical billing work stays in one place.

Catch T87.0X1 rejections before adjudication

Pabau sends US claims through Claim.MD, which returns clearinghouse and payer rejections early. Your team corrects and resubmits from the patient record.

Book a demo

Conclusion

T87.0X1 rewards precision more than memory. The code is short, complete at six characters and narrower than it looks. Treat the replant as the deciding fact, because without one you are probably looking at a stump code.

Fix your encoder once, so the X stays and no 7th character sneaks in. After that, the risk sits in the note, where a quick query costs less than chasing a clean claim later. Book a demo to see how Pabau surfaces claim rejections while your team can still fix them.

Continue your research

Need a process for rejected claims? Denial management in healthcare walks through identifying, appealing and preventing claim rejections.

Where does diagnosis coding fit in the bigger picture? Revenue cycle management explained follows a claim from booking to payment.

What makes a claim pass the first time? Clean claims covers the checks that keep submissions out of rework.

Side missing from the note? ICD-10 code T87.0X9 covers a reattached arm with no documented side, and when to query instead.

Was the replant an ear, nose or scalp? ICD-10 code T87.2 explains coding complications of other reattached body parts.

Frequently asked questions