Codes / ICD10CM / S89.029K

S89.029K Salter-Harris Type II physeal fracture of upper end of unspecified tibia, 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 unspecified tibia, subsequent encounter for fracture with nonunion

Summary

A Salter-Harris Type II physeal fracture of the upper end of the unspecified tibia is a growth plate injury affecting the proximal tibia, typically occurring in children and adolescents. This fracture involves a separation through the growth plate (physis) with a metaphyseal fragment, disrupting bone development in the area. The "subsequent encounter for fracture with nonunion" designation indicates this is a follow-up visit for a fracture that has failed to heal properly.

Causes

Common causes include trauma from falls, sports injuries, or accidents where force is applied to the knee or lower leg. Direct impact, twisting motions, or axial loading can disrupt the growth plate, leading to this type of fracture. Nonunion may result from inadequate initial treatment, poor blood supply, or excessive movement at the fracture site.

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.
  • Treatment History: Prior inadequate immobilization or surgical intervention.

Symptoms

  • Persistent pain and tenderness around the knee or proximal tibia.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to bear weight on the affected leg.
  • Limited range of motion in the knee.
  • Visible or palpable abnormal movement at the fracture site.

Diagnosis

Physical examination to assess pain, swelling, and range of motion. Imaging tests, such as X-rays, are typically used to confirm separation at the growth plate and identify the metaphyseal fragment. Advanced imaging, like CT or MRI, may be used to evaluate nonunion and assess bone healing. Clinical history of prior fracture and treatment is also considered.

Treatment Options

Treatment may involve surgical intervention, such as internal fixation, to stabilize the fracture and promote healing. Non-surgical options, including prolonged immobilization or bone grafting, may be considered depending on the severity. Physical therapy is often recommended to restore function and strength.

Prognosis and Follow-Up

Prognosis depends on the success of treatment and the extent of nonunion. Regular follow-up with imaging is necessary to monitor healing. Long-term outcomes may include residual pain, limited mobility, or growth disturbances if the growth plate is affected.

Complications

  • Chronic pain or instability in the knee.
  • Growth plate damage leading to limb length discrepancy or angular deformity.
  • Arthritis or joint dysfunction over time.
  • Need for additional surgeries if nonunion persists.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports or activities with fall risks.
  • Follow prescribed rehabilitation protocols to optimize healing.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.

When to Seek Professional Help

Seek immediate medical attention if there is severe pain, inability to bear weight, visible deformity, or signs of infection (e.g., fever, redness, drainage) at the fracture site.

Tips for Medical Coders

Document the encounter as a subsequent visit for fracture with nonunion. Include details about the fracture's location, type (Salter-Harris II), and confirmation of nonunion through imaging or clinical assessment. Ensure the encounter is coded as a follow-up for a fracture that has not healed, distinguishing it from acute or healing fractures.

Book a walkthrough

S89.029K policy automation walkthrough

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