Codes / ICD10CM / S89.329

S89.329 Salter-Harris Type II physeal fracture of lower end of unspecified fibula

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 unspecified fibula

Summary

A Salter-Harris Type II physeal fracture of the lower end of the unspecified 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.

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 location. The Salter-Harris classification system helps identify the specific fracture pattern, which is critical for determining treatment. Additional imaging, like MRI or CT scans, may be used if the fracture is not clearly visible on X-rays or to assess associated injuries.

Treatment Options

Treatment depends on the severity and displacement of the fracture. Nonsurgical options include immobilization with a cast or splint to allow healing. Surgical intervention may be necessary for displaced fractures to realign the bone and stabilize the growth plate. Physical therapy is often recommended during recovery to restore strength and mobility.

Prognosis and Follow-Up

Prognosis is generally favorable with appropriate treatment, but outcomes depend on the extent of growth plate involvement and proper alignment. Regular follow-up appointments are necessary to monitor healing and assess for potential growth disturbances. Long-term monitoring may be required to ensure normal bone development.

Complications

Potential complications include growth plate damage leading to limb length discrepancies or angular deformities. Infection, nonunion, or malunion of the fracture may also occur. Early intervention and adherence to treatment plans can reduce these risks.

Lifestyle & Prevention

Preventive measures include using proper protective equipment during sports and ensuring safe play environments. Strengthening exercises for the ankle and lower leg may help reduce injury risk. Avoiding high-impact activities until fully healed is important to prevent re-injury.

When to Seek Professional Help

Seek medical attention if there is severe pain, inability to bear weight, visible deformity, or signs of infection (e.g., fever, increased swelling, redness). Prompt evaluation is crucial to prevent complications and ensure proper healing.

Tips for Medical Coders

When coding S89.329, ensure the documentation specifies the fracture as Salter-Harris Type II and involves the lower end of the fibula without indicating laterality. Verify that the injury is physeal (growth plate) and not another fracture type. Accurate documentation of the fracture mechanism and anatomical location is essential for correct code assignment.

Book a walkthrough

S89.329 policy automation walkthrough

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