Codes / ICD10CM / S89.042S

S89.042S Salter-Harris Type IV physeal fracture of upper end of left tibia, sequela

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Salter-Harris Type IV physeal fracture of upper end of left tibia, sequela

Summary

A Salter-Harris Type IV physeal fracture of the upper end of the left tibia is a growth plate injury involving a fracture that extends through the metaphysis, physis, and epiphysis of the proximal tibia. The "sequela" designation indicates this is a residual condition resulting from the initial injury, with ongoing effects such as growth disturbances, joint alignment issues, or chronic pain. This type of fracture disrupts bone development and requires long-term monitoring due to its potential impact on limb function.

Causes

The initial fracture typically results from trauma, such as falls, sports injuries, or accidents involving force to the knee or lower leg. Direct impact, twisting motions, or axial loading can disrupt the growth plate, leading to this type of fracture. The sequela arises from incomplete healing, malunion, or complications during the recovery process.

Risk Factors

  • Age: More common in children and adolescents due to open growth plates, with residual effects persisting into adulthood.
  • Activity Level: Participation in contact sports or activities with a risk of leg trauma increases the likelihood of initial injury.
  • Anatomical Factors: Variations in bone structure or growth plate vulnerability may contribute to poor healing outcomes.

Symptoms

  • Chronic pain or discomfort around the knee or proximal tibia.
  • Swelling or deformity in the affected area.
  • Difficulty bearing weight on the affected leg.
  • Limited range of motion in the knee.
  • Possible limb length discrepancy or angular deformity.

Diagnosis

Physical examination to assess pain, swelling, and range of motion. Imaging tests, such as X-rays or MRI, are used to evaluate residual bone alignment, growth plate integrity, and signs of chronic changes. Clinical history of the initial injury and prior treatment is essential for context.

Treatment Options

Management focuses on addressing residual symptoms and functional limitations. Options may include physical therapy to improve mobility, orthopedic devices for support, pain management, or surgical intervention for severe deformities or growth disturbances. Treatment is tailored to the specific sequelae and patient needs.

Prognosis and Follow-Up

Prognosis depends on the severity of the initial injury and healing outcomes. Some patients may experience long-term functional limitations, while others recover with minimal impact. Regular follow-up with an orthopedic specialist is recommended to monitor growth, joint alignment, and address any emerging issues.

Complications

  • Chronic pain or arthritis in the knee joint.
  • Limb length discrepancy or angular deformity.
  • Growth plate arrest leading to uneven limb development.
  • Reduced range of motion or stiffness.

Lifestyle & Prevention

  • Avoid high-impact activities that stress the affected leg.
  • Use protective gear during sports or physical activities.
  • Maintain a healthy weight to reduce joint stress.
  • Follow prescribed rehabilitation protocols to optimize recovery.

When to Seek Professional Help

Seek medical attention if you experience worsening pain, new swelling, difficulty walking, or signs of infection (e.g., redness, fever). Prompt evaluation is important for managing complications or adjusting treatment plans.

Tips for Medical Coders

Document the residual effects of the initial fracture, including any chronic symptoms, functional limitations, or anatomical changes. Ensure the sequela designation is supported by clinical evidence of long-term consequences from the Salter-Harris Type IV fracture. Include details about prior treatment and current functional status to justify the code assignment.

Book a walkthrough

S89.042S policy automation walkthrough

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