Codes / ICD10CM / S89.311P

S89.311P Salter-Harris Type I physeal fracture of lower end of right fibula, subsequent encounter for fracture with malunion

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Salter-Harris Type I physeal fracture of lower end of right fibula, subsequent encounter for fracture with malunion

Summary

A Salter-Harris Type I physeal fracture of the lower end of the right fibula, subsequent encounter for fracture with malunion, refers to a growth plate injury at the distal right fibula that has healed abnormally. This fracture involves a separation through the growth plate without involving the metaphysis or epiphysis, a critical area for bone development. The "subsequent encounter" indicates follow-up care after the initial injury, and "malunion" confirms the fracture has healed in a misaligned position, potentially affecting function or growth.

Causes

Common causes include trauma from falls, sports injuries, or accidents where impact or stress is applied to the ankle or lower leg. Direct force, twisting motions, or rotational stress can disrupt the growth plate, leading to fracture. Inadequate immobilization or premature weight-bearing during healing may contribute to malunion.

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 or Inadequate Treatment: Improper immobilization or non-compliance with post-injury care.

Symptoms

  • Persistent pain or discomfort around the ankle or distal fibula.
  • Swelling or deformity at the affected site.
  • Difficulty bearing weight or limited range of motion.
  • Visible or palpable misalignment of the fibula.

Diagnosis

Diagnosis involves a physical examination to assess pain, swelling, and deformity. Imaging studies, such as X-rays or CT scans, are used to confirm malunion by evaluating bone alignment and growth plate integrity. Comparison with prior imaging may help assess healing progression. Clinical correlation with the patient’s history of injury and treatment is essential.

Treatment Options

Treatment focuses on managing symptoms and addressing functional impairment. Options may include physical therapy to improve mobility and strength, orthotic devices for support, or surgical intervention to realign the bone if malunion causes significant issues. Pain management and activity modification are often part of the plan.

Prognosis and Follow-Up

Prognosis depends on the severity of malunion and its impact on growth or function. Mild cases may have minimal long-term effects, while severe malunion could lead to chronic pain or limb length discrepancy. Regular follow-up with imaging and clinical assessments is necessary to monitor healing and address complications.

Complications

  • Chronic pain or discomfort.
  • Limited mobility or range of motion.
  • Limb length discrepancy or angular deformity.
  • Increased risk of future fractures.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports or activities with fall risks.
  • Follow post-injury care instructions to promote proper healing.
  • Maintain a healthy diet to support bone health.

When to Seek Professional Help

Seek care if pain worsens, swelling increases, or mobility declines. Prompt evaluation is needed if deformity is visible or if there are signs of nerve or vascular compromise, such as numbness or discoloration.

Tips for Medical Coders

Document the encounter as a subsequent visit for fracture with malunion. Include details on the fracture’s location (distal right fibula), type (Salter-Harris I), and confirmation of malunion. Ensure the record specifies the fracture is healed but misaligned, and note any treatment or follow-up plans.

Book a walkthrough

S89.311P policy automation walkthrough

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