Codes / ICD10CM / S99.112D

S99.112D Salter-Harris Type I physeal fracture of left metatarsal, 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 I physeal fracture of left metatarsal, subsequent encounter for fracture with routine healing

Summary

This condition represents a Salter-Harris Type I fracture of the left metatarsal growth plate (physis) during a subsequent encounter for fracture care, with evidence of routine healing. Type I fractures involve a complete separation of the growth plate without involvement of the metaphysis or epiphysis. This code is used when the patient is receiving active treatment for the fracture and healing is progressing as expected. The injury typically occurs in children or adolescents, where the growth plate is still active, and requires monitoring to ensure proper recovery and prevent complications.

Causes

Direct trauma or injury to the left foot, such as falls, sports-related impacts, or accidents, can disrupt the growth plate. Sudden force applied to the metatarsals, including twisting or direct blows, may lead to this type of fracture. The injury often results from high-energy events that stress the developing bone structure.

Risk Factors

  • Age: Children and adolescents, as their growth plates are still developing and more susceptible to injury.
  • High-impact activities: Participation in sports like running, jumping, or contact sports.
  • Previous injuries: Prior damage to the metatarsals or surrounding structures may increase vulnerability.

Symptoms

  • Pain and swelling localized to the left metatarsal area.
  • Difficulty bearing weight or walking on the affected foot.
  • Limited range of motion in the toes or midfoot.
  • Visible bruising or tenderness over the fracture site.

Diagnosis

Diagnosis is typically made through clinical evaluation and imaging studies, such as X-rays, which confirm the Salter-Harris Type I fracture pattern and assess healing progress. The provider will review the patient's history of injury, physical examination findings, and imaging results to determine the fracture's status and healing trajectory.

Treatment Options

Treatment focuses on immobilization, such as casting or bracing, to allow the growth plate to heal. Pain management and activity modification are often recommended. Follow-up imaging may be used to monitor healing, and physical therapy could be prescribed to restore function once healing is sufficient.

Prognosis and Follow-Up

With proper care, the prognosis for routine healing is generally favorable. Follow-up appointments are necessary to assess healing progress and adjust treatment as needed. Long-term monitoring may be required to ensure normal growth and function of the affected metatarsal.

Complications

Potential complications include growth plate damage leading to abnormal bone growth, chronic pain, or reduced mobility. In rare cases, improper healing could result in deformity or long-term functional impairment.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use appropriate footwear and protective gear during sports.
  • Maintain a healthy diet to support bone healing and growth.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or there are signs of infection (e.g., redness, fever). Prompt evaluation is necessary if the patient experiences difficulty walking or if the injury does not improve with initial care.

Tips for Medical Coders

This code is specific to a subsequent encounter for fracture care with routine healing. Documentation should clearly indicate the fracture type (Salter-Harris Type I), location (left metatarsal), and healing status (routine). Coders should verify that the encounter aligns with active treatment and that the healing process is progressing as expected to support accurate coding.

Book a walkthrough

S99.112D policy automation walkthrough

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