Codes / ICD10CM / S89.112D

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

Summary

A Salter-Harris Type I physeal fracture of the lower end of the left tibia, subsequent encounter for fracture with routine healing, refers to a follow-up visit for a previously diagnosed growth plate fracture at the distal left tibia. This fracture involves a complete separation of the growth plate (physis) without extending into the metaphysis or epiphysis, typically seen in children and adolescents. The "subsequent encounter" indicates the patient is in the healing phase, and "routine healing" confirms the fracture is progressing as expected without complications.

Causes

The initial fracture causing this condition results from trauma to the ankle or lower leg, such as falls, sports injuries, or accidents involving direct impact, twisting, or rotational stress. The subsequent encounter reflects ongoing management of the healing process, which may include monitoring for proper bone union and addressing any residual symptoms.

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 or tenderness around the ankle or distal left tibia, though typically reduced during healing.
  • Mild swelling or bruising, if present, should be decreasing over time.
  • Possible stiffness or mild discomfort with movement, depending on healing progress.
  • Ability to bear weight, as healing advances.

Diagnosis

Diagnosis during the subsequent encounter involves reviewing the initial injury, imaging (e.g., X-rays) to confirm routine healing, and clinical assessment of symptoms. The provider evaluates the fracture site for stability, alignment, and signs of proper bone union. Documentation should reflect the healing status and any adjustments to the treatment plan.

Treatment Options

Treatment focuses on monitoring healing and supporting recovery. This may include:

  • Continued immobilization (e.g., cast or brace) if needed.
  • Physical therapy to restore strength and range of motion.
  • Pain management as appropriate.
  • Follow-up imaging to confirm complete healing before resuming normal activities.

Prognosis and Follow-Up

With routine healing, the prognosis is generally favorable, and most patients recover fully without long-term issues. Follow-up appointments ensure the fracture heals properly and address any concerns. Return to activities is gradual, guided by the provider’s assessment of healing progress.

Complications

Complications are rare with routine healing but may include delayed union, growth plate disturbance, or persistent pain. Close monitoring helps detect and manage these issues early.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a provider.
  • Use protective gear during sports to reduce injury risk.
  • Maintain a healthy diet to support bone healing.
  • Follow the provider’s recommendations for activity restrictions.

When to Seek Professional Help

Seek care if symptoms worsen (e.g., increased pain, swelling, or difficulty bearing weight), or if there are signs of infection (e.g., redness, warmth, or fever). Prompt evaluation ensures any complications are addressed quickly.

Tips for Medical Coders

Use this code for a subsequent encounter (D) for a Salter-Harris Type I physeal fracture of the lower left tibia with confirmed routine healing. Document the encounter type (subsequent) and healing status (routine) to support code assignment. Ensure laterality (left) and fracture details align with the code’s specificity.

Book a walkthrough

S89.112D policy automation walkthrough

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