Codes / ICD10CM / S49.022G

S49.022G Salter-Harris Type II physeal fracture of upper end of humerus, left arm, subsequent encounter for fracture with delayed healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Salter-Harris Type II physeal fracture of upper end of humerus, left arm, subsequent encounter for fracture with delayed healing (ICD-10 Code: S49.022G)

Summary

This code represents a Salter-Harris Type II fracture involving the growth plate (physeal) at the upper end of the left humerus, with delayed healing during a subsequent encounter. This fracture type occurs when the growth plate and a portion of the metaphysis separate from the rest of the bone, typically in children and adolescents due to the relative weakness of the physis. The "subsequent encounter" and "delayed healing" modifiers indicate ongoing care for a fracture that is not progressing as expected.

Causes

Trauma, such as a fall onto an outstretched hand or a direct blow to the shoulder, is the primary cause. These injuries often occur during sports, play, or accidents involving forceful arm movement. Delayed healing may result from inadequate immobilization, poor blood supply, or underlying health conditions affecting bone repair.

Risk Factors

  • Age (most common in children and adolescents with open growth plates)
  • Participation in high-impact sports or activities
  • Prior growth plate injuries
  • Conditions affecting bone healing (e.g., nutritional deficiencies, metabolic disorders)

Symptoms

  • Persistent pain and swelling at the shoulder or upper arm
  • Limited range of motion
  • Visible deformity in severe cases
  • Difficulty moving the arm
  • Prolonged healing time compared to typical fracture recovery

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 its location at the growth plate. A detailed patient history, including the mechanism of injury and previous treatment, is also important. Imaging may show signs of delayed union or nonunion.

Treatment Options

  • Immobilization: Continued use of a sling or cast to stabilize the fracture.
  • Monitoring: Regular follow-up imaging to assess healing progress.
  • Surgical intervention: Considered if healing does not improve with conservative measures.
  • Rehabilitation: Physical therapy to restore function once healing progresses.

Prognosis and Follow-Up

Prognosis depends on the extent of the fracture and adherence to treatment. Delayed healing may prolong recovery, but most fractures eventually heal with appropriate care. Follow-up appointments are essential to monitor progress and adjust treatment as needed.

Complications

  • Nonunion (failure of the bone to heal)
  • Malunion (healing in an incorrect position)
  • Growth disturbances due to damage to the growth plate
  • Chronic pain or stiffness

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 to reduce injury risk.
  • Follow post-injury care instructions carefully to promote healing.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or there is new deformity. Contact a healthcare provider if mobility does not improve or if signs of infection (e.g., redness, fever) develop.

Tips for Medical Coders

This code requires documentation of the fracture type (Salter-Harris II), location (upper end of left humerus), encounter type (subsequent), and healing status (delayed). Coders should verify that the medical record supports each component, including evidence of delayed healing (e.g., imaging reports or clinical notes). The "subsequent encounter" modifier indicates active treatment for a condition with inadequate response to prior therapy.

Book a walkthrough

S49.022G policy automation walkthrough

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