Codes / ICD10CM / S99.139D

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

Summary

This condition describes a Salter-Harris Type III fracture of an unspecified metatarsal bone, occurring during a subsequent encounter for fracture with routine healing. Type III fractures involve a fracture line extending through the growth plate (physis) and into the epiphysis, potentially affecting joint surfaces. These injuries typically occur in children or adolescents with active growth plates and require monitoring to ensure proper healing and prevent 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.
  • Possible deformity or tenderness at the fracture site.

Diagnosis

Diagnosis involves a 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. The "subsequent encounter" designation indicates ongoing monitoring during the healing phase, with routine healing suggesting no complications.

Treatment Options

Treatment may include immobilization with a cast or splint to stabilize the fracture. Pain management and activity modification are often recommended. Follow-up imaging may be used to monitor healing. In some cases, surgical intervention may be necessary if the fracture disrupts joint alignment.

Prognosis and Follow-Up

With proper treatment, most Salter-Harris Type III fractures heal without long-term issues. Routine healing indicates a favorable outcome, but follow-up care is essential to ensure the growth plate and joint function are not compromised. Regular monitoring helps detect any delayed healing or complications.

Complications

Potential complications include growth plate damage leading to limb length discrepancies or angular deformities. Joint stiffness or arthritis may develop if the fracture affects the joint surface. In rare cases, nonunion or malunion of the fracture can occur.

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 is severely limited. Contact a healthcare provider if signs of infection (e.g., redness, fever) or new deformity appear. Follow-up appointments are important to monitor healing progress.

Tips for Medical Coders

Document the fracture type (Salter-Harris Type III), the affected bone (unspecified metatarsal), and the encounter type (subsequent for fracture with routine healing). Ensure clinical notes support the "routine healing" status to justify the code. Include details on imaging or treatment to confirm the diagnosis and healing phase.

Book a walkthrough

S99.139D policy automation walkthrough

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