ICD-10 code T84.115D: Left femur, fixation device breakdown

Found our content helpful?

Key takeaways

T84.115D is a billable ICD-10-CM code for mechanical breakdown of an internal fixation device in the left femur.

The 7th character D designates a subsequent encounter, so the breakdown was identified earlier and care is still ongoing.

Breakdown means the hardware structurally failed, which is coded separately from displacement under T84.125D.

Laterality drives the code choice, and the right-femur equivalent is T84.114D.

Practice management software like Pabau flags incomplete documentation before a T84 claim leaves the practice.

ICD-10 code T84.115D is the billable ICD-10-CM diagnosis code for breakdown (mechanical) of internal fixation device of left femur, subsequent encounter. It applies when a patient returns for continued care after a femoral fixation device has already been found to have failed mechanically.

Orthopedic coders reach for T84.115D at follow-up visits, physical therapy evaluations, and pre-operative planning appointments for hardware removal or revision surgery. Coding A instead of D at one of those visits signals a new presentation to the payer, and the claim comes back rejected.

ICD-10 code T84.115D: Definition and billable status

ICD-10 code T84.115D is a valid, specific, billable diagnosis code in the CDC/NCHS ICD-10-CM classification system. It can be submitted on insurance claims for reimbursement without further specification. Below is a structured summary of the code’s key attributes for quick reference.

Clinical description: Mechanical breakdown of internal fixation devices

Mechanical breakdown of an internal fixation device means the hardware itself has structurally failed. Displacement is a different finding, where the device has moved but stayed intact. A periprosthetic fracture is different again, a new break in the bone beside the implant.

Holding those three apart is what keeps code selection inside the right part of the T84.1 subcategory.

Common types of hardware affected include intramedullary nails, bone screws, plates, and wires used in femoral fracture repair. Failure modes range from fatigue fracture of the implant to screw pull-out, nail breakage, and wire migration.

The CMS ICD-10-CM tabular list lists the following approximate synonyms for T84.115D, all of which map to this code:

• Broken nail, left femur, subsequent encounter
• Broken plate, left femur, subsequent encounter
• Broken screw, left femur, subsequent encounter
• Broken wire, left femur, subsequent encounter
• Fractured intramedullary nail, left femur, subsequent encounter
• Hardware failure, left femur fixation device, subsequent encounter

Understanding the 7th character: Subsequent encounter (D)

The 7th character in ICD-10 code T84.115D specifies the encounter type. “D” means the patient is receiving active treatment for a condition that was previously identified and diagnosed. The complication is not new, and the patient is in the healing or management phase.

This is one of the most frequently misapplied concepts in ICD-10-CM Chapter 19. The first visit that treats the hardware failure takes the A character. Every follow-up visit after that takes D instead. Once treatment has concluded and residual effects remain, the sequela character S applies.

According to the ICD-10-CM Official Coding Guidelines, the 7th character reflects the treating provider’s perspective at the time of the encounter.

The patient’s overall treatment history does not set it. A surgeon performing hardware removal for a broken nail codes A for the operative encounter and D for the post-operative visits.

Sibling and related codes for mechanical complications of fixation devices

T84.115D belongs to the T84.1 subcategory covering mechanical complications of internal fixation devices of bones of the limb. Reading the sibling structure as a whole stops left-femur codes being applied to the right femur or to a different bone.

Laterality errors of that kind are a frequent trigger for payer audits, so confirm the side from the clinical documentation before selecting a code.

Note the last two rows. T84.118 and T84.119 carry breakdown of a device in another or an unspecified bone, while T84.19x covers a mechanical complication of a different type altogether.

MS-DRG mapping and reimbursement context for T84.115D

For inpatient hospitalizations, T84.115D maps to MS-DRG groupings in the musculoskeletal and injury/complication categories under CMS’s MS-DRG Definitions Manual.

The precise DRG assignment depends on the principal diagnosis and on any complicating or comorbid conditions (CCs/MCCs) present. Whether a surgical procedure happens during the same admission also matters. T84.115D alone does not determine the DRG.

Coders should verify the current DRG mapping in the FY2026 MS-DRG Definitions Manual, version 43.0 (revised as v43.1). The CMS Physician Fee Schedule lookup tool covers the payment side.

Submitting claims through a clearinghouse that validates code-DRG relationships before transmission reduces rejection risk. It also helps to know which rejection reasons cluster around this code family.

The denial codes in medical billing reference lists the CARC codes that most often accompany T84 claims.

Present on admission (POA) indicator

The POA indicator identifies whether a diagnosis was present when the patient was admitted to the hospital. For T84.115D, confirm the POA status against the current CMS POA exempt list, because the reportable status of complication codes can change between editions.

Mechanical breakdown of a fixation device is, by definition, a complication of a prior procedure. It cannot be present before surgery. So T84.115D will typically carry a POA indicator of “N” in inpatient settings where the admission is for management of the hardware failure. Document the clinical timeline clearly in the record before the claim is finalized.

Documentation requirements for accurate orthopedic complication coding

Having the right documentation in place before coding T84.115D prevents the most common claim rejections. Five checkpoints cover almost all of them:

• Laterality confirmed: The operative report, imaging order, or clinic note must explicitly state “left femur” rather than “femur” or “bilateral.” Unspecified laterality codes exist in ICD-10-CM, but they are not acceptable when the documentation supports specificity.
• Device type documented: The surgeon’s note should name the implant, such as an intramedullary nail, a dynamic hip screw, or a plate and screws. This supports the approximate synonym mapping and separates breakdown from displacement.
• Encounter stage confirmed: The treating provider’s note must establish that this is a follow-up visit for a previously identified breakdown, not a new presentation. The date of initial diagnosis should appear in the problem list or the referring note.
• Imaging referenced: X-ray or CT findings confirming hardware failure should be cited in the encounter note. Coders cannot assign T84.115D on their own without supporting radiographic documentation.
• No active surgical treatment at this encounter: Hardware removal surgery at this visit is likely coded as an initial encounter rather than a subsequent one.

Practices using claims management software with built-in ICD-10 catalogues can flag incomplete documentation fields before a claim leaves the practice. That cuts the back-and-forth with payers that delays payment.

Coding tips and common errors for ICD-10 code T84.115D

Mechanical breakdown claims get denied more often than most coders expect, and the errors are predictable. Three documentation questions decide the code, and the diagram below shows how each answer narrows the choice.

The five failure points below are what billing departments see most across orthopedic claims.

• Do not confuse A with D at follow-up visits. Once the breakdown has been identified and the patient is in ongoing management, every subsequent visit uses the D character. Using A at a second or third visit tells payers the claim may be a duplicate.
• Distinguish mechanical breakdown from displacement. T84.125D covers displacement of an internal fixation device of the left femur, subsequent encounter. Breakdown means the device has structurally failed, and displacement means it has moved position. The imaging report and the surgeon’s note will specify which one is present.
• Do not use T84.115D for the right femur. The correct right-femur equivalent is T84.114D. Laterality errors are a leading reason for claim rejection in T84.1x coding, and they are among the most avoidable.
• Confirm the device is an internal fixation device, not a joint replacement. Hip prosthesis complications code under T84.0xx, not T84.1xx. Mistaking a failed fixation screw for a failed hip replacement component produces a category-level error.
• Sequence T84.115D correctly as a complication code. Per the ICD-10-CM Official Guidelines, Chapter 19 complication codes are generally sequenced as additional codes, with the condition being treated as the principal diagnosis.

Validation before transmission catches several of these errors while the claim can still be corrected. A clearinghouse checks code pairings, laterality conflicts, and payer-specific edits in the same step. The guide to medical claims clearinghouses explains how that submission and validation process runs.

How Pabau keeps T84 complication claims clean before they go out

In most orthopedic practices, the coder rebuilds the encounter after the fact. They read the clinic note, chase the imaging report for confirmation of hardware failure, and check the problem list for the date of initial diagnosis. Only then do they choose the 7th character. Each of those steps is a chance for the wrong character to reach the payer.

Practice management software like Pabau keeps that evidence in one record. The treatment note, the uploaded imaging report, the problem list, and the claim all sit against the same patient. The encounter stage is visible while the code is being chosen. Built-in ICD-10 and CPT catalogues mean the code is picked from a maintained list rather than typed from memory.

From there, claims go out electronically through our Claim.MD clearinghouse integration, and remittance advice comes back into the same system for posting. A rejected T84 claim surfaces with its denial reason attached, so the pattern behind repeat rejections shows up in weeks rather than quarters.

Keep orthopedic complication claims clean before they go out

Pabau holds the clinical note, the imaging report, and the claim against one patient record, with built-in ICD-10 catalogues and Claim.MD clearinghouse submission. See how it handles T84 complication coding for orthopedic and multi-specialty practices.

Book a demo

Conclusion

T84.115D is simple to assign and easy to assign at the wrong moment. The clinical picture at visit one and visit four looks identical in the chart, and only the 7th character separates them. The stage of care sets that character, not the radiographic findings.

So the work that pays off sits upstream of the code. The note has to record the side, the implant, and the date the breakdown was first identified. It also has to say whether this visit treats it actively. Get that right and the code follows in seconds. Practices that fix their note template once stop re-litigating the same denial every quarter.

The trade-off worth remembering is that no payer edit will catch a 7th character that is wrong but valid. That check has to happen in your documentation. Book a demo to see how Pabau keeps the note, the imaging, and the claim in one record for orthopedic practices.

Continue your research

Need to understand how clearinghouse integration reduces T84 claim rejections? How medical claims clearinghouses work covers the end-to-end submission and validation process.

Want a framework for building compliant orthopedic billing documentation? Revenue cycle management explained walks through the documentation-to-payment workflow for specialty practices.

Tracking payments and denials after a T84 claim goes out? Electronic remittance advice explained shows how ERA files speed up payment posting and denial identification.

Frequently asked questions