Codes / ICD10CM / S89.019K

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

Summary

A Salter-Harris Type I 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 complete separation through the growth plate (physis) without involving the metaphysis or epiphysis, disrupting bone development in the affected area. The "subsequent encounter for fracture with nonunion" 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 assess for nonunion. Advanced imaging, like CT or MRI, may be used to evaluate bone healing and soft tissue involvement.

Treatment Options

Treatment focuses on promoting fracture union and may include surgical intervention, such as internal fixation, to stabilize the growth plate. Non-surgical options like 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 extent of the nonunion and the effectiveness of treatment. Follow-up care is essential to monitor healing and address any complications. Long-term outcomes may include persistent pain, growth disturbances, or functional limitations if the fracture does not heal properly.

Complications

  • Chronic pain or discomfort.
  • Growth plate damage leading to limb length discrepancy.
  • Arthritis or joint stiffness.
  • 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 a risk of leg trauma.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.
  • Follow post-treatment guidelines to promote healing.

When to Seek Professional Help

Seek immediate medical attention if experiencing severe pain, swelling, or inability to bear weight. Contact a healthcare provider if symptoms worsen or do not improve with treatment, or if there are signs of infection, such as fever or increased redness.

Tips for Medical Coders

Document the encounter as a subsequent visit for a fracture with nonunion. Include details about the fracture's location, type, and healing status. Note any surgical interventions or imaging results to support the diagnosis. Ensure documentation aligns with the specific code requirements for subsequent encounters and nonunion.

Book a walkthrough

S89.019K policy automation walkthrough

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