Codes / ICD10CM / S89.322D

S89.322D Salter-Harris Type II physeal fracture of lower end of left fibula, subsequent encounter for fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Salter-Harris Type II physeal fracture of lower end of left fibula, subsequent encounter for fracture with routine healing

Summary

A Salter-Harris Type II physeal fracture of the lower end of the left fibula is an injury to the growth plate (physis) at the distal fibula, typically occurring in children and adolescents. This fracture involves a separation through the growth plate with a metaphyseal fragment, a critical area for bone development. The injury is characterized by a fracture line extending through the physis and into the metaphysis, often resulting from shear or tensile forces. The term "subsequent encounter" indicates this is a follow-up visit for the fracture, and "routine healing" means the fracture is progressing normally without complications.

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. The mechanism often involves a sudden load or torque applied to the ankle joint.

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.

Symptoms

  • Pain and tenderness around the ankle or distal fibula.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to bear weight on the affected leg.
  • Visible deformity in severe cases.

Diagnosis

Diagnosis typically involves a physical examination to assess pain, swelling, and range of motion. Imaging studies, such as X-rays, are used to confirm the fracture type and assess healing progress. The "subsequent encounter" status implies prior documentation of the fracture, and routine healing is confirmed through clinical evaluation and imaging showing progressive bone union.

Treatment Options

Treatment may include immobilization with a cast or brace to support healing, followed by gradual weight-bearing and physical therapy to restore function. Pain management and activity modification are often recommended. Routine follow-up ensures the fracture heals properly without complications.

Prognosis and Follow-Up

With proper treatment, most Salter-Harris Type II fractures heal without long-term issues. Routine healing indicates a favorable prognosis, but follow-up appointments are necessary to monitor progress and adjust care as needed. Long-term outcomes depend on the severity of the injury and adherence to treatment plans.

Complications

Potential complications include growth plate damage leading to limb length discrepancy or angular deformity, though routine healing reduces this risk. Infection or delayed union may occur but are uncommon with appropriate care.

Lifestyle & Prevention

Preventive measures include using proper protective gear during sports, avoiding high-risk activities, and ensuring safe play environments. Maintaining bone health through nutrition and regular exercise can support recovery and reduce future fracture risk.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or there are signs of infection (e.g., redness, fever). New or worsening deformity, inability to bear weight, or persistent symptoms after initial treatment also warrant evaluation.

Tips for Medical Coders

Document the fracture type, location (left fibula), and healing status (routine) to support the code S89.322D. Ensure the "subsequent encounter" context is clear, indicating follow-up care for a fracture with normal healing. Clinical notes should reflect the absence of complications and confirm routine progress.

Book a walkthrough

S89.322D policy automation walkthrough

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