Chat with GenHealth to automate any coding or chart task.
Name of the Condition
Unspecified physeal fracture of upper end of unspecified femur, subsequent encounter for fracture with nonunion
Summary
An unspecified physeal fracture of the upper end of the femur, with subsequent encounter for fracture with nonunion, refers to a growth plate (physis) injury at the proximal femur that has failed to heal properly. The term "unspecified" indicates the exact type or location within the physis is not detailed, and "subsequent encounter" denotes follow-up care after the initial injury. This condition typically occurs in children or adolescents and involves monitoring or intervention for a fracture that has not united (healed) as expected.
Causes
Physeal fractures of the upper femur are usually caused by acute trauma, such as falls, sports injuries, or direct impacts to the hip or thigh. The force transmitted across the growth plate can disrupt its structure, leading to a fracture. Nonunion may result from inadequate immobilization, poor blood supply, infection, or excessive movement during the healing phase.
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.
- Factors that impair healing, such as poor nutrition, smoking, or underlying medical conditions.
Symptoms
- Persistent or worsening pain around the hip or upper thigh.
- Swelling or bruising that does not resolve.
- Difficulty bearing weight on the leg or walking.
- Limited range of motion in the hip joint.
- Possible deformity or instability at the fracture site.
Diagnosis
Diagnosis involves a physical examination to assess pain, swelling, and mobility. Imaging, typically X-rays, is used to identify the fracture and evaluate the alignment and healing progress. Advanced imaging, such as CT or MRI, may be used to assess nonunion or associated complications. Clinical history of the initial injury and prior treatment is also considered.
Treatment Options
Treatment depends on the severity of nonunion and patient factors. Options may include:
- Immobilization with a cast or brace to stabilize the fracture.
- Surgical intervention, such as internal fixation with pins, screws, or plates, to promote healing.
- Bone grafting to stimulate bone growth.
- Physical therapy to restore function and strength.
- Pain management and activity modification.
Prognosis and Follow-Up
Prognosis varies based on the extent of nonunion and treatment response. Early intervention improves outcomes. Follow-up care involves regular imaging to monitor healing and functional assessments. Long-term monitoring may be needed to address growth disturbances or joint issues.
Complications
- Chronic pain or instability.
- Growth plate damage leading to limb length discrepancy or deformity.
- Avascular necrosis (loss of blood supply to the bone).
- Infection, particularly with surgical intervention.
- Arthritis or joint dysfunction.
Lifestyle & Prevention
- Avoid high-impact activities until cleared by a healthcare provider.
- Ensure proper nutrition, including calcium and vitamin D, to support bone health.
- Use protective gear during sports or activities with fall risks.
- Follow post-injury care instructions to promote healing.
When to Seek Professional Help
Seek medical attention if:
- Pain worsens or does not improve with rest.
- Swelling, bruising, or deformity is noticeable.
- Difficulty walking or bearing weight persists.
- Signs of infection, such as fever or increased redness, develop.
Tips for Medical Coders
Document the encounter as a subsequent visit for fracture with nonunion. Include details on the fracture's location (upper end of femur), the physeal involvement, and the nonunion status. Note any interventions or imaging results that confirm nonunion. Ensure the documentation supports the "subsequent encounter" and "nonunion" components of the code.
S79.009K policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.