Codes / ICD10CM / S89.222K

S89.222K Salter-Harris Type II physeal fracture of upper end of left fibula, subsequent encounter for fracture with nonunion

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Salter-Harris Type II physeal fracture of upper end of left fibula, subsequent encounter for fracture with nonunion
  • Also known as: Type II growth plate fracture of the proximal left fibula (subsequent encounter, nonunion)

Summary

A Salter-Harris Type II physeal fracture of the upper end of the left fibula is an injury to the growth plate (physis) at the proximal left fibula, typically occurring in children and adolescents. This fracture involves a separation through the growth plate with a metaphyseal fragment, distinguishing it from other Salter-Harris types. The term "subsequent encounter" indicates this is a follow-up visit for the fracture, and "nonunion" means the bone has failed to heal properly after an expected period.

Causes

Common causes include trauma from falls, sports injuries, or accidents where an impact or stress is applied to the leg. Direct force or twisting motions can disrupt the growth plate, leading to this specific fracture pattern. Nonunion may result from inadequate immobilization, poor blood supply, infection, or excessive movement during healing.

Risk Factors

  • Age: More common in children and adolescents due to open growth plates.
  • Activity Level: Participation in contact sports or activities that may cause physical impact.
  • Anatomical Factors: Variations in bone structure or growth plate vulnerability.
  • Delayed Treatment: Prolonged time to initial care may increase nonunion risk.
  • Comorbidities: Conditions like diabetes or smoking that impair healing.

Symptoms

  • Persistent pain and tenderness around the left fibula.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to move the affected leg.
  • Visible deformity in severe cases.
  • Lack of healing progress noted on follow-up imaging.

Diagnosis

Physical examination to assess pain, swelling, and range of motion. Imaging tests, such as X-rays or CT scans, confirm the fracture type and evaluate for nonunion. Comparison with prior imaging helps determine healing status. Clinical history of the initial injury and treatment is also considered.

Treatment Options

Treatment focuses on promoting bone healing and may include immobilization with a cast or brace, surgical intervention (e.g., bone grafting, fixation), or physical therapy to restore function. Pain management and monitoring for complications are also part of care.

Prognosis and Follow-Up

Prognosis depends on the severity of nonunion and response to treatment. Follow-up visits monitor healing progress, with imaging used to assess bone union. Long-term outcomes may include residual pain or limited mobility if healing is incomplete.

Complications

  • Chronic pain or discomfort.
  • Limited range of motion or functional impairment.
  • Increased risk of future fractures.
  • Potential need for additional surgery.

Lifestyle & Prevention

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

When to Seek Professional Help

Seek care if pain worsens, swelling increases, or mobility declines. Prompt evaluation is needed if signs of infection (e.g., redness, fever) or new deformity appear.

Tips for Medical Coders

Document the fracture type (Salter-Harris II), location (upper end of left fibula), encounter type (subsequent), and nonunion status clearly. Include details on treatment provided and any imaging results confirming nonunion to support code assignment. Ensure documentation aligns with the clinical scenario to justify the "subsequent encounter" and "nonunion" modifiers.

Book a walkthrough

S89.222K policy automation walkthrough

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