Codes / ICD10CM / S79.002S

S79.002S Unspecified physeal fracture of upper end of left femur, sequela

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

Unspecified physeal fracture of upper end of left femur, sequela

Summary

An unspecified physeal fracture of the upper end of the left femur, sequela, refers to the residual effects or complications that persist after the initial healing phase of a growth plate (physis) fracture at the proximal femur. This code is used for encounters where the patient experiences ongoing symptoms or functional limitations related to the prior injury. The term "unspecified" indicates that the exact type or location within the physis was not detailed in prior documentation.

Causes

Physeal fractures of the femur are typically caused by acute trauma, such as falls, sports injuries, or direct impacts to the hip or thigh. The force transmitted through the growth plate can disrupt its structure, leading to a fracture. Sequela may arise from incomplete healing, malunion, or other complications during the recovery process.

Risk Factors

  • Common in children and adolescents due to active growth plates.
  • Increased risk during growth spurts when growth plates are weaker.
  • Participation in high-impact activities or sports with sudden stops or direction changes.
  • Prior history of fractures or bone weakness.

Symptoms

  • Chronic pain or discomfort in the hip or upper thigh area.
  • Residual swelling or bruising that persists beyond the typical healing period.
  • Difficulty bearing weight on the leg or walking.
  • Limited range of motion in the hip joint.
  • Possible limb length discrepancy or deformity.

Diagnosis

Diagnosis involves a physical examination to assess pain, swelling, and mobility. Imaging, typically X-rays or MRI, may be used to evaluate the residual effects of the prior fracture, such as malunion, avascular necrosis, or persistent growth plate disruption. Clinical correlation with the patient’s history of the initial injury is essential.

Treatment Options

Treatment focuses on managing symptoms and addressing complications. This may include physical therapy to improve mobility and strength, pain management, or surgical intervention for severe deformities or functional limitations. Orthopedic consultation is often recommended to determine the most appropriate course of action.

Prognosis and Follow-Up

Prognosis depends on the severity of the sequela and the patient’s response to treatment. Regular follow-up is necessary to monitor for ongoing issues, such as growth disturbances or arthritis. Long-term outcomes may vary, with some patients experiencing minimal impairment while others require ongoing care.

Complications

  • Chronic pain or discomfort.
  • Limited mobility or functional impairment.
  • Growth plate disturbances leading to limb length discrepancy.
  • Avascular necrosis of the femoral head.
  • Post-traumatic arthritis.

Lifestyle & Prevention

  • Avoid high-impact activities that may exacerbate symptoms.
  • Engage in low-impact exercises to maintain strength and mobility.
  • Use assistive devices, such as crutches or braces, as recommended.
  • Follow-up with healthcare providers to monitor for complications.

When to Seek Professional Help

Seek medical attention if symptoms worsen, new pain develops, or there are signs of infection (e.g., fever, increased swelling, redness). Prompt evaluation is important for managing complications and preventing further damage.

Tips for Medical Coders

This code is used for sequela of an unspecified physeal fracture of the upper end of the left femur. Documentation should clearly indicate the residual effects or complications related to the prior injury. Ensure the encounter is for a sequela and not an initial or subsequent healing phase. The term "unspecified" should be retained as documented, and no additional details about the fracture type or location should be added.

Book a walkthrough

S79.002S policy automation walkthrough

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