Codes / ICD10CM / S49.092S

S49.092S Other physeal fracture of upper end of humerus, left arm, sequela

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Other physeal fracture of upper end of humerus, left arm, sequela (ICD-10 Code: S49.092S)

Summary

This code describes a sequela (late effect) of a previous physeal fracture involving the growth plate at the upper end of the left humerus. Physeal fractures are common in children and adolescents due to the relative weakness of open growth plates during development. The "sequela" designation indicates the condition is a residual effect following the healing of the initial fracture, such as chronic pain, limited mobility, or other long-term consequences.

Causes

The sequela arises from a prior physeal fracture of the upper humerus, typically caused by trauma like a fall onto an outstretched hand or a direct blow to the shoulder. These injuries often occur during sports, play, or accidents involving forceful arm movement. The sequela represents the lasting impact of the original injury after the acute healing phase has concluded.

Risk Factors

  • Age (most common in children and adolescents with open growth plates at the time of initial injury)
  • Incomplete or improper healing of the original fracture
  • High-impact activities or sports that stress the affected arm
  • Anatomical factors affecting bone strength or growth plate integrity

Symptoms

  • Chronic pain or discomfort in the shoulder or upper arm
  • Persistent limited range of motion
  • Mild swelling or stiffness
  • Possible visible deformity in severe cases
  • Difficulty with daily activities requiring arm movement

Diagnosis

Diagnosis involves a physical examination to assess pain, swelling, and range of motion, combined with imaging studies like X-rays to evaluate the residual effects of the healed fracture. A detailed patient history, including the mechanism and timing of the original injury, is essential to confirm the sequela status. Clinical correlation with prior treatment records may also be necessary.

Treatment Options

Treatment focuses on managing symptoms and improving function, which may include:

  • Physical therapy to restore range of motion and strength
  • Pain management with medications or other modalities
  • Orthopedic devices (e.g., braces) for support
  • Surgical intervention in cases of significant deformity or functional impairment

Prognosis and Follow-Up

Prognosis depends on the severity of the initial injury and the effectiveness of healing. Most patients experience gradual improvement with appropriate management, though some may have persistent limitations. Regular follow-up with an orthopedic specialist is recommended to monitor progress and adjust treatment as needed.

Complications

  • Chronic pain or discomfort
  • Permanent limited range of motion
  • Growth disturbances (e.g., limb length discrepancy)
  • Arthritis or joint degeneration over time
  • Need for ongoing medical or rehabilitative care

Lifestyle & Prevention

  • Avoid high-impact activities that stress the affected arm until cleared by a healthcare provider
  • Engage in low-impact exercises to maintain mobility and strength
  • Use proper protective gear during sports or activities
  • Follow post-injury rehabilitation guidelines to minimize long-term effects

When to Seek Professional Help

Seek medical attention if symptoms worsen, new pain or swelling develops, or functional limitations interfere with daily activities. Prompt evaluation is important to address complications or adjust treatment plans.

Tips for Medical Coders

This code is used for the sequela of a physeal fracture of the upper humerus, left arm. Document the residual effects (e.g., chronic pain, limited mobility) and confirm the prior fracture history. Ensure the "sequela" designation is appropriate for late effects following the healing phase, not acute or active treatment encounters.

Book a walkthrough

S49.092S policy automation walkthrough

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