Codes / ICD10CM / S99.119D

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

Summary

This condition describes a Salter-Harris Type I fracture of an unspecified metatarsal bone in the foot, occurring during a subsequent encounter for fracture care with evidence of routine healing. Salter-Harris Type I fractures involve a complete separation of the growth plate (physis) without involvement of the metaphysis or epiphysis. These injuries typically occur in children or adolescents, where the growth plate is still active, and require monitoring to ensure proper healing and prevent long-term complications.

Causes

Direct trauma or injury to the 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 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 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" designation indicates ongoing care after the initial injury, with routine healing confirmed by clinical and radiographic findings.

Treatment Options

Treatment may include immobilization with a cast or brace to support healing, pain management, and activity modification. Physical therapy is often recommended to restore strength and mobility once healing is established. Follow-up imaging may be used to monitor progress.

Prognosis and Follow-Up

With proper treatment, most Salter-Harris Type I fractures heal without long-term complications. Routine healing is expected in this scenario, but follow-up care is important to ensure the growth plate heals correctly and function is restored. Regular monitoring by a healthcare provider is recommended during the healing process.

Complications

Potential complications include growth plate damage leading to limb length discrepancies or angular deformities, though these are less common with Type I fractures. Incomplete healing or delayed union may occur if the injury is not managed appropriately.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use proper footwear and protective gear during sports.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.
  • Gradually return to activity under medical guidance to prevent re-injury.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or mobility does not improve with treatment. Signs of infection, such as redness, warmth, or fever, also require prompt evaluation.

Tips for Medical Coders

This code is used for a subsequent encounter for fracture care with routine healing. Documentation should specify the fracture type (Salter-Harris Type I), the affected bone (unspecified metatarsal), and evidence of routine healing. Ensure the encounter is classified as "subsequent" and not initial or acute.

Book a walkthrough

S99.119D policy automation walkthrough

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