Codes / ICD10CM / S72.132E

S72.132E Displaced apophyseal fracture of left femur, subsequent encounter for open fracture type I or II with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Displaced apophyseal fracture of left femur, subsequent encounter for open fracture type I or II with routine healing

Summary

This condition involves a displaced fracture of the apophyseal region of the left femur, documented during a subsequent encounter for an open fracture type I or II with routine healing. The apophysis is a bony growth area where tendons or ligaments attach, and the fracture fragments are separated from their normal anatomical position. The open fracture classification indicates the skin was breached but limited, and routine healing confirms the fracture is progressing without complications.

Causes

Apophyseal fractures commonly result from direct trauma, such as falls or high-impact injuries, particularly in adolescents during growth spurts. They can also occur from repetitive stress, such as in athletes engaged in activities like running or jumping. Weakened bone structure from conditions like osteoporosis may increase susceptibility, though this is less common in younger populations.

Risk Factors

  • Adolescence, especially during periods of rapid growth.
  • Participation in high-impact sports or activities.
  • History of previous injuries to the hip or thigh.
  • Underlying bone conditions that weaken the apophysis.

Symptoms

  • Localized pain at the hip or thigh, often worsened by movement or pressure.
  • Swelling, tenderness, or bruising around the affected area.
  • Difficulty bearing weight on the leg.
  • Possible limping or altered gait.

Diagnosis

Physical examination to assess pain, swelling, and tenderness. Imaging studies, including X-rays or MRI, to confirm the fracture and evaluate displacement or associated soft tissue injury. Documentation of the fracture type (open I or II) and healing status is critical for accurate coding.

Treatment Options

Treatment may include immobilization with a cast or brace to stabilize the fracture, pain management, and physical therapy to restore mobility and strength. Surgical intervention is rarely needed for apophyseal fractures but may be considered if displacement is severe. Routine follow-up ensures healing progresses as expected.

Prognosis and Follow-Up

With proper treatment, most apophyseal fractures heal without long-term complications. Follow-up appointments monitor healing progress, and physical therapy may be recommended to regain full function. Routine healing indicates the fracture is responding to treatment, and activity restrictions are typically lifted as healing advances.

Complications

Potential complications include nonunion (failure to heal), malunion (improper healing), or persistent pain. Infection is a risk with open fractures, though routine healing reduces this likelihood. Long-term issues like chronic pain or limited mobility are uncommon with appropriate care.

Lifestyle & Prevention

Avoid high-impact activities until cleared by a healthcare provider. Strengthening exercises for the hip and thigh may help prevent future injuries. Proper warm-up and technique in sports can reduce trauma risk. Adequate nutrition, including calcium and vitamin D, supports bone health.

When to Seek Professional Help

Seek immediate care for severe pain, inability to bear weight, or signs of infection (e.g., fever, increased redness, pus). Follow up with a provider if pain worsens, swelling persists, or mobility does not improve as expected.

Tips for Medical Coders

Document the fracture type (open I or II), subsequent encounter status, and routine healing to support accurate coding. Ensure clinical notes specify the left femur and apophyseal involvement. Verify that the encounter is classified as "subsequent" and that healing is documented as routine to align with the code’s requirements.

Book a walkthrough

S72.132E policy automation walkthrough

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