Codes / ICD10CM / S89.192D

S89.192D Other 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

  • Other physeal fracture of lower end of left tibia, subsequent encounter for fracture with routine healing

Summary

An other physeal fracture of the lower end of the left tibia is an injury to the growth plate (physis) at the distal left tibia, typically occurring in children and adolescents. This fracture involves a separation through the growth plate, a critical area for bone development. The term "other" indicates a specific type of physeal fracture not classified under more detailed categories (e.g., Salter-Harris types). The injury is documented during a subsequent encounter, meaning it is being treated after the initial phase, and healing is progressing as expected without complications.

Causes

Common causes include trauma from falls, sports injuries, or accidents where impact or stress is applied to the left ankle or lower leg. Direct force, twisting motions, or rotational stress can disrupt the growth plate, leading to fracture. High-impact events or sudden stress to the left tibia may also precipitate this type of fracture.

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.
  • Laterality: Involvement of the left tibia.

Symptoms

  • Pain and tenderness around the ankle or distal left tibia.
  • Swelling and possible bruising near the affected area.
  • Difficulty or reluctance to bear weight on the affected leg.
  • Reduced range of motion in the ankle or knee.

Diagnosis

Diagnosis typically involves a physical examination to assess pain, swelling, and mobility. Imaging studies, such as X-rays or MRI, are used to confirm the fracture and evaluate healing progress. The documentation must specify the fracture type, location (left tibia), and encounter type (subsequent) to support the code.

Treatment Options

Treatment may include immobilization with a cast or brace to stabilize the fracture during healing. Pain management and activity modification are often recommended. Physical therapy may be prescribed to restore strength and mobility once healing is advanced. Surgical intervention is rare for routine healing cases.

Prognosis and Follow-Up

With routine healing, the prognosis is generally favorable, and most fractures heal without long-term issues. Follow-up appointments are scheduled to monitor progress, typically involving periodic imaging to confirm healing. Full recovery may take several weeks to months, depending on the severity of the fracture.

Complications

Complications are uncommon with routine healing but may include delayed union, malunion, or growth plate disturbances. In rare cases, chronic pain or functional limitations may occur. Close monitoring helps minimize these risks.

Lifestyle & Prevention

  • Avoid high-impact activities until cleared by a healthcare provider.
  • Use protective gear during sports or activities with a risk of leg injury.
  • Maintain a healthy diet rich in calcium and vitamin D to support bone health.
  • Follow rehabilitation guidelines to ensure proper healing.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or mobility declines. Contact a provider if signs of infection (e.g., redness, fever) or new deformity appear. Routine follow-up is essential to track healing progress.

Tips for Medical Coders

Document the laterality (left tibia), encounter type (subsequent), and healing status (routine) to accurately assign this code. Ensure clinical notes specify the fracture type and absence of complications. The code S89.192D requires clear documentation of the fracture's location, encounter phase, and healing trajectory.

Book a walkthrough

S89.192D policy automation walkthrough

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