Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Salter-Harris Type II physeal fracture of lower end of ulna, left arm, sequela
Summary
This condition represents a Salter-Harris Type II physeal fracture at the lower end of the ulna in the left arm, classified as a sequela. Salter-Harris Type II fractures extend through the physis (growth plate) and into the metaphysis, typically affecting children and adolescents. The sequela designation indicates residual effects following the healing of the initial fracture, such as chronic pain, deformity, or functional impairment.
Causes
Salter-Harris Type II physeal fractures commonly occur due to direct impact, such as a fall onto an outstretched hand, or forceful twisting of the forearm. These injuries are frequent in activities involving sudden stops, collisions, or falls, where the growth plate’s relative weakness compared to surrounding bone contributes to the fracture pattern. The sequela arises from incomplete healing or complications during the recovery process.
Risk Factors
- Children and adolescents are at higher risk due to the presence of growth plates.
- Participation in contact sports or activities with a high likelihood of falls increases risk.
- Certain genetic or metabolic conditions affecting bone development may also elevate susceptibility.
- Delayed or inadequate treatment of the initial fracture can increase the likelihood of sequela.
Symptoms
- Chronic pain or discomfort in the wrist or forearm.
- Reduced range of motion or stiffness in the affected arm.
- Visible deformity or malalignment of the wrist or forearm.
- Functional limitations, such as difficulty gripping or lifting objects.
Diagnosis
Diagnosis involves a thorough clinical evaluation, including a review of the patient’s medical history and the initial fracture. Imaging studies, such as X-rays or MRI, may be used to assess residual bone alignment, joint integrity, and any ongoing structural abnormalities. The healthcare provider will also evaluate functional limitations and pain levels to determine the impact of the sequela.
Treatment Options
Treatment focuses on managing symptoms and improving function. This may include physical therapy to restore mobility and strength, pain management strategies, or orthopedic interventions like bracing or surgery to correct deformities. The approach is tailored to the specific residual effects and the patient’s functional needs.
Prognosis and Follow-Up
Prognosis varies depending on the severity of the sequela and the effectiveness of treatment. Regular follow-up appointments are essential to monitor healing, address ongoing symptoms, and adjust treatment plans as needed. Long-term outcomes may include persistent mild discomfort or reduced mobility, but many patients achieve significant improvement with appropriate care.
Complications
- Chronic pain or arthritis in the affected joint.
- Growth disturbances, such as limb length discrepancy.
- Persistent deformity or functional impairment.
- Reduced quality of life due to activity limitations.
Lifestyle & Prevention
- Engage in regular physical therapy to maintain or improve mobility.
- Use protective gear during sports or activities to prevent reinjury.
- Follow a balanced diet rich in calcium and vitamin D to support bone health.
- Avoid overexertion of the affected arm during recovery.
When to Seek Professional Help
Seek medical attention if you experience worsening pain, new deformity, or a sudden decrease in function. Prompt evaluation is important to address complications and adjust treatment plans as needed.
Tips for Medical Coders
This code is used for a sequela of a Salter-Harris Type II physeal fracture of the lower ulna, left arm. Documentation should clearly indicate the residual effects of the initial fracture, such as chronic pain, deformity, or functional impairment. Ensure the sequela is directly linked to the prior fracture and that the encounter is for managing these long-term effects.
S59.022S policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.