Codes / ICD10CM / S99.042D

S99.042D Salter-Harris Type IV physeal fracture of left calcaneus, 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 IV physeal fracture of left calcaneus, subsequent encounter for fracture with routine healing
  • Growth plate fracture of the left heel bone (Type IV), follow-up for healing

Summary

This condition represents a Salter-Harris Type IV fracture of the left calcaneus (heel bone) during a subsequent encounter, with evidence of routine healing. Type IV fractures involve a fracture line extending through the metaphysis, physis (growth plate), and epiphysis, potentially affecting both bone growth and joint alignment. The "subsequent encounter" and "routine healing" modifiers indicate ongoing care after the initial injury, with healing progressing as expected. This is typically seen in children or adolescents and requires monitoring to ensure proper recovery.

Causes

Direct trauma or injury to the heel, such as falls, sports-related impacts, or accidents. Sudden force applied to the foot can disrupt the growth plate and adjacent bone structures, leading to this fracture type.

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 heel or surrounding structures may increase vulnerability.

Symptoms

  • Pain and swelling localized to the heel area, though symptoms may be reduced during healing.
  • Difficulty bearing weight or walking on the affected foot, depending on healing progress.
  • Limited range of motion in the ankle or foot, which may improve with recovery.
  • Visible bruising or deformity in severe cases, though these may resolve as healing advances.

Diagnosis

Physical examination to assess healing progress, including tenderness, swelling, and range of motion. Imaging studies (e.g., X-rays) to confirm fracture alignment and healing status. Documentation of routine healing supports the "subsequent encounter" and "routine healing" modifiers.

Treatment Options

  • Immobilization: Casts or braces to stabilize the fracture during healing.
  • Pain management: Medications to alleviate discomfort.
  • Physical therapy: Exercises to restore strength and mobility as healing permits.
  • Monitoring: Regular follow-ups to ensure proper healing and address any complications.

Prognosis and Follow-Up

With routine healing, most patients recover fully without long-term issues. Follow-up care focuses on monitoring growth plate function and joint alignment. Return to normal activities is gradual, guided by clinical assessment and imaging.

Complications

  • Growth disturbances: Potential disruption of normal bone growth if healing is incomplete.
  • Joint alignment issues: Misalignment may affect long-term foot or ankle function.
  • Chronic pain: Rare, but possible if healing is not optimal.

Lifestyle & Prevention

  • Protective footwear: Use during high-impact activities to reduce injury risk.
  • Safe practices: Avoidance of hazardous situations that could lead to falls or trauma.
  • Gradual return to activity: Follow medical guidance to prevent re-injury during recovery.

When to Seek Professional Help

  • Worsening pain or swelling during healing.
  • Difficulty bearing weight or walking.
  • New deformity or reduced range of motion.
  • Signs of infection (e.g., redness, fever) at the injury site.

Tips for Medical Coders

Document the fracture type (Salter-Harris IV), laterality (left), and encounter type (subsequent) clearly. Include evidence of routine healing (e.g., imaging or clinical notes) to support the "subsequent encounter" and "routine healing" modifiers. Ensure all components of the code are accurately reflected in the medical record.

Book a walkthrough

S99.042D policy automation walkthrough

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