Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Salter-Harris Type I physeal fracture of lower end of humerus, right arm, subsequent encounter for fracture with malunion (ICD-10 Code: S49.111P)
Summary
This code describes a Salter-Harris Type I fracture involving the growth plate (physeal) at the lower end of the right humerus, classified as a subsequent encounter for fracture with malunion. Salter-Harris Type I fractures involve a separation of the growth plate without displacement of the bone fragments. Malunion indicates the fracture has healed in a non-anatomic position, which may affect function. These injuries are most common in children and adolescents due to the relative weakness of the growth plate compared to surrounding bone.
Causes
Trauma, such as a fall onto an outstretched hand or a direct blow to the elbow, is the primary cause. These injuries often occur during sports, play, or accidents involving forceful arm movement. Malunion may result from inadequate initial treatment, poor healing, or excessive movement during the recovery period.
Risk Factors
- Age (most common in children and adolescents with open growth plates)
- Participation in high-impact sports or activities
- Prior growth plate injuries or developmental conditions affecting bone strength
- Inadequate immobilization or non-compliance with treatment during initial healing
Symptoms
- Persistent pain or discomfort at the elbow or lower arm
- Limited range of motion in the right arm
- Visible deformity or abnormal alignment
- Difficulty moving or using the right arm
- Swelling or tenderness at the fracture site
Diagnosis
Diagnosis relies on a physical examination to assess pain, swelling, and range of motion, combined with imaging studies like X-rays to visualize the fracture and confirm malunion. A detailed patient history, including the mechanism of injury and prior treatment, is essential. Advanced imaging (e.g., CT or MRI) may be used to evaluate healing and alignment.
Treatment Options
Treatment focuses on managing symptoms and addressing functional impairment. Options may include physical therapy to improve range of motion and strength, pain management, or surgical intervention if malunion causes significant functional limitations. The approach depends on the severity of the malunion and the patient’s age and activity level.
Prognosis and Follow-Up
Prognosis varies based on the degree of malunion and its impact on function. Most patients recover with appropriate treatment, but some may experience long-term limitations. Regular follow-up is necessary to monitor healing, assess function, and adjust treatment as needed. Children may require ongoing evaluation to ensure normal growth and development.
Complications
- Chronic pain or discomfort
- Reduced range of motion or functional impairment
- Growth disturbances (e.g., limb length discrepancy)
- Increased risk of future fractures
- Need for additional interventions (e.g., surgery)
Lifestyle & Prevention
- Avoid high-impact activities until cleared by a healthcare provider.
- Use protective equipment during sports or activities.
- Follow rehabilitation guidelines to optimize healing.
- Maintain a healthy diet to support bone health.
When to Seek Professional Help
Seek medical attention if you experience worsening pain, new deformity, or difficulty moving the arm. Prompt evaluation is important if symptoms do not improve with conservative management or if there are signs of infection (e.g., redness, fever).
Tips for Medical Coders
This code is specific to a subsequent encounter for a Salter-Harris Type I physeal fracture of the lower humerus, right arm, with malunion. Document the encounter type (subsequent) and the presence of malunion clearly. Ensure the fracture location (lower end of humerus, right arm) and type (Salter-Harris Type I) are accurately recorded. Use this code only when the fracture has healed in a non-anatomic position and the patient is receiving follow-up care.
S49.111P policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.