Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Salter-Harris Type II physeal fracture of lower end of left tibia, sequela
Summary
A Salter-Harris Type II physeal fracture of the lower end of the left tibia, sequela, refers to the residual effects or chronic changes resulting from a prior fracture through the growth plate (physis) at the distal left tibia that extended into the metaphysis. This condition represents the long-term consequences of the injury, which may include persistent symptoms, structural changes, or functional limitations. Sequela indicates that the fracture has healed but left lasting effects, often requiring ongoing management or monitoring.
Causes
The sequela arises from a previous Salter-Harris Type II physeal fracture of the distal left tibia, typically caused by trauma such as falls, sports injuries, or accidents involving force to the ankle or lower leg. The initial injury disrupted the growth plate and metaphysis, and the sequela reflects the body’s response to that prior event, including potential malunion, growth disturbances, or chronic pain.
Risk Factors
- Age: More common in children and adolescents due to open growth plates, which increase the risk of growth plate injury and subsequent sequela.
- Severity of Initial Injury: Higher-energy trauma or incomplete healing of the original fracture may increase the likelihood of residual effects.
- Anatomical Factors: Variations in bone structure or growth plate vulnerability can predispose to long-term complications.
Symptoms
- Persistent pain or discomfort around the ankle or distal tibia.
- Swelling or deformity in the affected area.
- Difficulty bearing weight or limited range of motion in the ankle.
- Possible leg length discrepancy or growth abnormalities.
Diagnosis
Diagnosis involves a clinical evaluation of the patient’s history, including the prior fracture, and physical examination to assess residual symptoms. Imaging studies, such as X-rays or MRI, may be used to identify structural changes, malunion, or growth disturbances. The "sequela" designation confirms that the current condition is a direct result of the previous injury.
Treatment Options
Treatment focuses on managing symptoms and addressing functional limitations. Options may include physical therapy to improve mobility, pain management, orthotic devices, or surgical intervention for severe deformities. The approach depends on the specific residual effects and the patient’s functional needs.
Prognosis and Follow-Up
Prognosis varies based on the severity of the sequela and the patient’s response to treatment. Regular follow-up is important to monitor for complications, such as growth abnormalities or chronic pain. Long-term outcomes may include persistent symptoms or the need for ongoing care to maintain function.
Complications
- Chronic pain or discomfort.
- Growth disturbances, such as leg length discrepancy.
- Arthritis or joint stiffness in the affected area.
- Functional limitations affecting mobility or activity levels.
Lifestyle & Prevention
- Avoid high-impact activities that may exacerbate symptoms.
- Use supportive footwear or orthotics to stabilize the ankle.
- Engage in low-impact exercises to maintain mobility and strength.
- Follow up with healthcare providers to monitor for changes in symptoms or function.
When to Seek Professional Help
Seek medical attention if symptoms worsen, new pain or deformity develops, or there are signs of infection (e.g., redness, swelling, fever). Prompt evaluation is important to address complications or adjust treatment as needed.
Tips for Medical Coders
When coding for this condition, use the ICD-10-CM code S89.122S to represent the sequela of a Salter-Harris Type II physeal fracture of the lower end of the left tibia. Ensure documentation clearly links the current condition to the prior fracture and specifies the residual effects. Verify that the "sequela" designation is appropriate based on the patient’s history and clinical findings.
S89.122S policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.