Codes / ICD10CM / S89.292G

S89.292G Other physeal fracture of upper end of left fibula, subsequent encounter for fracture with delayed healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Other physeal fracture of upper end of left fibula, subsequent encounter for fracture with delayed healing
  • Also known as: Growth plate fracture of the proximal left fibula (other type), delayed healing, subsequent encounter

Summary

An other physeal fracture of the upper end of the left fibula, subsequent encounter for fracture with delayed healing, refers to a growth plate injury at the proximal left fibula that has not healed as expected during follow-up care. This condition typically occurs in children and adolescents, where the growth plate (physis) is disrupted, and healing progress is slower than anticipated. The term "other" indicates a specific subtype of physeal fracture not classified under standard Salter-Harris types, while "delayed healing" denotes prolonged recovery.

Causes

Common causes include initial trauma from falls, sports injuries, or accidents that apply force to the leg. Direct impact or twisting motions can disrupt the growth plate. Delayed healing may result from inadequate immobilization, poor blood supply, or underlying factors affecting bone repair.

Risk Factors

  • Age: More common in children and adolescents due to open growth plates.
  • Activity Level: Participation in contact sports or high-impact activities.
  • Anatomical Factors: Variations in bone structure or growth plate vulnerability.
  • Initial Injury Severity: Higher trauma may increase healing delays.

Symptoms

  • Persistent pain and tenderness around the fibula.
  • Swelling or bruising that does not resolve.
  • Difficulty bearing weight on the affected leg.
  • Limited range of motion in the ankle or knee.

Diagnosis

Diagnosis involves a physical examination to assess pain, swelling, and mobility. Imaging, such as X-rays or MRI, evaluates fracture alignment and healing progress. Comparison with prior imaging helps confirm delayed healing. Clinical judgment determines if healing is progressing slower than expected.

Treatment Options

Treatment focuses on promoting healing, which may include extended immobilization (casting or bracing), activity modification, or physical therapy to restore function. In some cases, surgical intervention may be considered to stabilize the fracture. Pain management and monitoring for complications are also part of the plan.

Prognosis and Follow-Up

Prognosis depends on the fracture type, patient age, and adherence to treatment. Most physeal fractures heal with proper care, but delayed healing may extend recovery time. Regular follow-up appointments with imaging are necessary to track progress and adjust treatment as needed.

Complications

  • Prolonged pain or functional limitations.
  • Risk of growth disturbances if the growth plate is affected.
  • Possible need for additional interventions if healing does not improve.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports to reduce injury risk.
  • Follow rehabilitation guidelines to support healing.
  • Maintain a balanced diet rich in calcium and vitamin D to aid bone health.

When to Seek Professional Help

Seek care if pain worsens, swelling increases, or mobility declines. Contact a provider if the affected leg cannot bear weight or if signs of infection (e.g., redness, fever) appear. Prompt evaluation is important for managing delayed healing.

Tips for Medical Coders

Document the fracture type (physeal, other), location (upper end of left fibula), and encounter status (subsequent) clearly. Specify "delayed healing" to justify the code. Include details on imaging, treatment, and follow-up to support medical necessity. Ensure documentation aligns with clinical findings and coding guidelines.

Book a walkthrough

S89.292G policy automation walkthrough

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