Codes / ICD10CM / S89.112S

S89.112S Salter-Harris Type I physeal fracture of lower 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 I physeal fracture of lower end of left tibia, sequela

Summary

A Salter-Harris Type I physeal fracture of the lower end of the left tibia, sequela, refers to the residual effects of a previously diagnosed growth plate fracture at the distal left tibia. This condition involves a complete separation of the growth plate (physis) without extension into the metaphysis or epiphysis, typically occurring in children and adolescents. The "sequela" designation indicates that the fracture has healed, but long-term consequences or complications persist, requiring ongoing management or monitoring.

Causes

The initial fracture causing this sequela results from trauma to the ankle or lower leg, such as falls, sports injuries, or accidents involving direct impact, twisting, or rotational stress. The sequela reflects the aftermath of the injury, where the growth plate has healed but may leave lasting effects like growth disturbances, functional limitations, or chronic pain.

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

  • Persistent pain or discomfort around the ankle or distal tibia.
  • Reduced range of motion or stiffness in the affected leg.
  • Visible deformity or limb length discrepancy.
  • Recurrent swelling or instability in the ankle joint.

Diagnosis

Diagnosis involves a thorough clinical evaluation, including a review of the patient’s medical history and the initial fracture event. Imaging studies, such as X-rays or MRI, may be used to assess residual bone alignment, growth plate integrity, and any ongoing structural abnormalities. Functional assessments to evaluate mobility and pain levels are also conducted to determine the impact of the sequela.

Treatment Options

Treatment focuses on managing symptoms and addressing complications. This may include physical therapy to improve strength and mobility, pain management strategies, or orthopedic interventions if growth disturbances or deformities are present. In some cases, surgical correction may be necessary to restore function or correct limb alignment.

Prognosis and Follow-Up

Prognosis depends on the severity of the initial injury and the presence of complications. Most patients recover with appropriate management, but long-term follow-up is often required to monitor for growth-related issues or functional limitations. Regular assessments by an orthopedic specialist help ensure optimal outcomes and address any emerging concerns.

Complications

  • Growth disturbances, such as limb length discrepancy or angular deformity.
  • Chronic pain or stiffness in the ankle or lower leg.
  • Reduced mobility or functional limitations.
  • Increased risk of future fractures in the affected area.

Lifestyle & Prevention

  • Avoid high-impact activities that stress the ankle or lower leg.
  • Use protective gear during sports or recreational activities.
  • Maintain a healthy weight to reduce stress on bones and joints.
  • Follow post-injury rehabilitation guidelines to support recovery.

When to Seek Professional Help

Seek medical attention if you experience worsening pain, new swelling, or difficulty bearing weight on the affected leg. Persistent functional limitations or signs of deformity also warrant evaluation by a healthcare provider.

Tips for Medical Coders

Document the sequela clearly, noting the history of the Salter-Harris Type I physeal fracture and any residual effects. Ensure the code S89.112S is used only when the condition represents a late effect of the initial fracture, with supporting clinical details to justify the sequela designation.

Book a walkthrough

S89.112S policy automation walkthrough

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