Codes / ICD10CM / S72.442D

S72.442D Displaced fracture of lower epiphysis (separation) of left femur, subsequent encounter for closed fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Displaced fracture of lower epiphysis (separation) of left femur, subsequent encounter for closed fracture with routine healing

Summary

This condition involves a displaced fracture of the lower epiphysis (growth plate) of the left femur, resulting in separation of the epiphyseal segment from the main bone. The fracture is classified as a subsequent encounter for a closed fracture with routine healing, indicating the skin remains intact and the fracture is progressing normally without complications. The fracture affects the distal (lower) portion of the femur, near the knee joint, and may involve the growth plate or adjacent structures.

Causes

High-impact trauma, such as falls, motor vehicle accidents, or direct blows to the thigh. Sports injuries or physical altercations. Stress fractures from repetitive overuse or strenuous activity.

Risk Factors

  • Advanced age, which may lead to decreased bone density.
  • Osteoporosis or other bone-weakening conditions.
  • Participation in high-risk activities or contact sports.
  • Prior history of femur fractures or bone disorders.
  • Age (more common in children and adolescents due to the presence of the epiphyseal plate).

Symptoms

  • Mild to moderate pain in the knee or thigh region.
  • Residual swelling or bruising at the fracture site.
  • Gradual improvement in weight-bearing ability as healing progresses.
  • Possible stiffness or limited range of motion during recovery.

Diagnosis

Physical examination to assess pain, swelling, and limb alignment. Imaging studies, such as X-rays or CT scans, to confirm fracture healing and alignment. Review of prior imaging to compare with current status. Assessment of functional recovery, including range of motion and weight-bearing capacity.

Treatment Options

Monitoring of fracture healing through periodic imaging. Pain management with analgesics or anti-inflammatory medications. Physical therapy to restore strength, flexibility, and mobility. Gradual return to weight-bearing activities as tolerated. Use of assistive devices (e.g., crutches) during early recovery if needed.

Prognosis and Follow-Up

Most fractures with routine healing progress well, with full recovery expected over several weeks to months. Follow-up appointments to assess healing and functional status. Return to normal activities is typically possible once pain resolves and strength is restored. Long-term monitoring may be recommended for children to ensure proper growth plate function.

Complications

Delayed union or nonunion of the fracture. Malunion (improper healing leading to misalignment). Residual stiffness or limited range of motion. Rare risk of avascular necrosis (loss of blood supply to the bone) in severe cases.

Lifestyle & Prevention

Avoid high-impact activities until cleared by a healthcare provider. Engage in low-impact exercises (e.g., swimming, cycling) to maintain fitness during recovery. Ensure adequate calcium and vitamin D intake to support bone health. Use protective gear during sports or high-risk activities. Maintain a healthy weight to reduce stress on bones.

When to Seek Professional Help

Increased pain, swelling, or bruising. New or worsening deformity of the leg. Inability to bear weight or move the leg. Signs of infection (e.g., fever, redness, drainage). Numbness, tingling, or weakness in the leg or foot.

Tips for Medical Coders

Document the encounter as a subsequent visit for a closed fracture with routine healing. Include details on fracture alignment, healing progress, and functional status. Note any restrictions on activity or use of assistive devices. Ensure documentation supports the "subsequent encounter" and "routine healing" criteria for accurate coding.

Book a walkthrough

S72.442D policy automation walkthrough

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