Codes / ICD10CM / S72.399D

S72.399D Other fracture of shaft of unspecified femur, subsequent encounter for closed fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Other Fracture of Shaft of Unspecified Femur, Subsequent Encounter for Closed Fracture with Routine Healing (ICD-10 Code: S72.399D)

Summary

This code describes a fracture of the shaft (diaphysis) of the femur (thigh bone) that does not fit into more specific fracture categories (e.g., transverse, spiral, or comminuted). The term "other" indicates the fracture type is documented but not classified under more precise subcategories. The "subsequent encounter" specifies this is a follow-up visit for the fracture, and "closed fracture with routine healing" means the bone does not penetrate the skin and is healing as expected without complications. Clinical evaluation is required to confirm the fracture's characteristics and management progress.

Causes

Such fractures typically result from high-impact trauma, such as motor vehicle accidents, falls from significant heights, or direct blows to the thigh. Rotational forces or axial loading (e.g., during sports or industrial injuries) can also cause this type of break. Low-energy injuries may occur in individuals with weakened bones.

Risk Factors

  • Participation in high-impact sports or activities.
  • Osteoporosis or other bone-weakening conditions.
  • Advanced age, due to decreased bone density.
  • Prior history of fractures or bone abnormalities.
  • Trauma or accidents involving significant force.

Symptoms

  • Sharp, localized pain in the thigh (may decrease over time as healing progresses).
  • Swelling, bruising, or tenderness around the fracture site (reducing with healing).
  • Gradual improvement in ability to bear weight on the affected leg.
  • Possible residual stiffness or discomfort during movement.

Diagnosis

Physical examination to assess pain, alignment, and functional recovery. Imaging (e.g., X-rays) may be used to confirm healing progress and rule out complications. Documentation of the fracture's status (closed, routine healing) and the encounter type (subsequent) is essential for accurate coding.

Treatment Options

Treatment focuses on monitoring healing and restoring function. This may include pain management, physical therapy to improve mobility and strength, and activity modification. Follow-up appointments ensure the fracture is healing as expected, with adjustments to the care plan if needed.

Prognosis and Follow-Up

With routine healing, most fractures of the femur shaft recover well over time. Follow-up care is important to track progress, address any residual symptoms, and guide rehabilitation. The duration of follow-up depends on the fracture's severity and the patient's response to treatment.

Complications

  • Delayed healing or nonunion (rare with routine healing).
  • Persistent pain or stiffness.
  • Muscle weakness or atrophy from reduced activity.
  • Rarely, malunion (improper healing) or hardware-related issues (if surgery was performed).

Lifestyle & Prevention

  • Engage in weight-bearing exercises to maintain bone density.
  • Use protective gear during high-risk activities.
  • Address underlying bone conditions (e.g., osteoporosis) to reduce fracture risk.
  • Follow post-fracture care instructions to support healing.

When to Seek Professional Help

Seek care if pain worsens, swelling increases, or new symptoms (e.g., numbness, difficulty bearing weight) develop. These may indicate complications requiring prompt evaluation.

Tips for Medical Coders

Document the fracture type (other), encounter type (subsequent), and healing status (closed with routine healing) clearly. Ensure the code aligns with clinical notes confirming the fracture is healing without issues and that this is a follow-up visit. Verify that the femur shaft and unspecified side are documented to support the code.

Book a walkthrough

S72.399D policy automation walkthrough

Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.