Codes / ICD10CM / S89.391K

S89.391K Other physeal fracture of lower end of right fibula, subsequent encounter for fracture with nonunion

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Other physeal fracture of lower end of right fibula, subsequent encounter for fracture with nonunion

Summary

An other physeal fracture of the lower end of the right fibula, subsequent encounter for fracture with nonunion, refers to a growth plate (physis) injury at the distal right fibula that has failed to heal properly during follow-up care. This code is used when the fracture demonstrates nonunion, meaning the bone fragments have not fused as expected. The term "other" indicates a specific type of physeal fracture not classified under more detailed subcategories, while "subsequent encounter" denotes ongoing management after the initial injury.

Causes

Common causes include trauma from falls, sports injuries, or accidents where impact or stress is applied to the right ankle or lower leg. Direct force, twisting motions, or rotational stress can disrupt the growth plate, leading to fracture. The mechanism often involves sudden or excessive force applied to the ankle joint.

Risk Factors

  • Age: More common in children and adolescents due to open growth plates.
  • Activity Level: Participation in contact sports or activities with a risk of leg trauma.
  • Anatomical Factors: Variations in bone structure or growth plate vulnerability.
  • Delayed Treatment: Inadequate initial management or prolonged immobilization.
  • Poor Blood Supply: Reduced circulation to the fracture site.

Symptoms

  • Persistent pain and tenderness around the right ankle or distal fibula.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to bear weight on the affected leg.
  • Visible deformity in severe cases.
  • Lack of healing progress over time.

Diagnosis

Diagnosis involves a physical examination to assess pain, swelling, and mobility. Imaging studies, such as X-rays or CT scans, are used to confirm nonunion by showing a persistent gap between bone fragments or absence of callus formation. Additional tests, like MRI, may evaluate soft tissue involvement or blood supply. Clinical history of the initial injury and prior treatment is also considered.

Treatment Options

Treatment may include surgical intervention, such as bone grafting or internal fixation, to promote healing. Non-surgical options like prolonged immobilization or electrical stimulation might be attempted first. Pain management and physical therapy are often part of the plan to restore function and address mobility issues.

Prognosis and Follow-Up

Prognosis depends on the severity of nonunion and response to treatment. Follow-up care involves regular imaging to monitor healing progress and adjust treatment as needed. Long-term outcomes may include persistent pain or limited mobility if healing is incomplete.

Complications

  • Chronic pain or discomfort.
  • Limited range of motion in the ankle.
  • Increased risk of future fractures.
  • Potential need for additional surgeries.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports or activities with fall risks.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.
  • Follow post-injury care instructions closely to reduce nonunion risk.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or mobility declines. Persistent symptoms after initial treatment warrant evaluation to rule out nonunion or other complications.

Tips for Medical Coders

Document the presence of nonunion and the subsequent encounter status clearly. Include details about the fracture's location (right fibula) and the failure of healing to support accurate coding. Ensure clinical notes align with the diagnosis and treatment provided.

Book a walkthrough

S89.391K policy automation walkthrough

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