Codes / ICD10CM / S89.129D

S89.129D Salter-Harris Type II physeal fracture of lower end of unspecified tibia, 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 unspecified tibia, subsequent encounter for fracture with routine healing

Summary

A Salter-Harris Type II physeal fracture of the lower end of the unspecified tibia, subsequent encounter for fracture with routine healing, refers to a fracture involving the growth plate (physis) at the distal tibia that extends into the metaphysis. This type of fracture is common in children and adolescents due to open growth plates. The subsequent encounter indicates the patient is receiving follow-up care for a fracture that is healing as expected, without complications. The injury disrupts the growth plate, a critical area for bone development, and may result from trauma to the ankle or lower leg.

Causes

Common causes include trauma from falls, sports injuries, or accidents where force is applied to the ankle or lower leg. Direct impact, twisting motions, or rotational stress can disrupt the growth plate, leading to a fracture that extends into the metaphysis. High-impact events or sudden stress to the tibia may also precipitate this type of injury.

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 tibia.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to bear weight on the affected leg.
  • Visible deformity in severe cases.

Diagnosis

Physical examination to assess pain, swelling, and range of motion. Imaging studies, such as X-rays, are typically used to confirm the fracture type and assess healing progress. Follow-up imaging may be performed to monitor routine healing during subsequent encounters.

Treatment Options

Treatment may include immobilization with a cast or brace to support healing. Pain management and activity modification are often recommended. Physical therapy may be prescribed to restore strength and mobility once healing is underway. Routine follow-up appointments are scheduled to monitor progress.

Prognosis and Follow-Up

With proper treatment, most Salter-Harris Type II fractures heal without long-term issues. Routine healing is expected with appropriate care. Follow-up appointments are necessary to assess healing and adjust treatment as needed. Long-term monitoring may be required to ensure normal growth and function.

Complications

Potential complications include growth plate damage affecting bone development, malunion, or nonunion. Infection or delayed healing may occur in some cases. Early intervention and adherence to treatment plans can minimize risks.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports or activities with a risk of leg injury.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.
  • Follow rehabilitation guidelines to restore strength and prevent re-injury.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or new symptoms develop. Contact a healthcare provider if there is difficulty bearing weight, signs of infection (e.g., fever, redness), or concerns about healing progress.

Tips for Medical Coders

Document the fracture type, location (unspecified tibia), and subsequent encounter status clearly. Note routine healing to support the code. Include details on follow-up care and any imaging or clinical assessments performed. Ensure documentation aligns with the ICD-10-CM guidelines for Salter-Harris fractures and subsequent encounter codes.

Book a walkthrough

S89.129D policy automation walkthrough

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