Codes / ICD10CM / S49.021D

S49.021D Salter-Harris Type II physeal fracture of upper end of humerus, right arm, subsequent encounter for fracture with routine 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, right arm, subsequent encounter for fracture with routine healing (ICD-10 Code: S49.021D)

Summary

This code describes a Salter-Harris Type II fracture involving the growth plate (physeal) at the upper end of the right humerus, with subsequent encounter for fracture with routine healing. This type of fracture 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 during development. The "subsequent encounter" modifier indicates follow-up care after the initial injury, and "routine healing" confirms the fracture is progressing normally without complications.

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. The fracture may result from acute injury or repetitive stress over time.

Risk Factors

  • Age (most common in children and adolescents with open growth plates)
  • Participation in high-impact sports or activities
  • Prior growth plate injuries
  • Anatomical factors, such as weaker or less developed growth plates

Symptoms

  • Pain and swelling at the shoulder or upper arm
  • Limited range of motion
  • Visible deformity in severe cases
  • Difficulty moving the arm
  • 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 its location at the growth plate. A detailed patient history, including the mechanism of injury and prior treatment, is also important. The "subsequent encounter" modifier requires documentation of follow-up care, while "routine healing" is confirmed by imaging showing progressive bone union without complications.

Treatment Options

  • Immobilization: A sling or cast may be used to stabilize the arm during healing.
  • Closed reduction: Manual realignment of the bone fragments without surgery, if needed.
  • Physical therapy: To restore range of motion and strength as healing progresses.
  • Monitoring: Regular follow-up imaging to assess healing status.

Prognosis and Follow-Up

With proper treatment, most Salter-Harris Type II fractures heal without long-term complications. Follow-up care is essential to monitor healing and ensure the growth plate is not disrupted. Routine healing typically occurs within 4-6 weeks, but recovery may vary based on the severity of the fracture and patient age.

Complications

  • Growth plate disruption leading to limb length discrepancy
  • Premature closure of the growth plate
  • Chronic pain or stiffness
  • Malunion or nonunion of the fracture

Lifestyle & Prevention

  • Use protective gear during high-impact sports or activities.
  • Avoid falls by maintaining balance and using proper techniques.
  • Strengthen shoulder and arm muscles to support the joint.
  • Follow post-injury guidelines to prevent re-injury during healing.

When to Seek Professional Help

Seek medical attention if symptoms worsen, such as increased pain, swelling, or deformity, or if there is difficulty moving the arm. Immediate care is needed for signs of infection, nerve damage, or compromised blood flow.

Tips for Medical Coders

This code requires documentation of the fracture type (Salter-Harris Type II), laterality (right arm), and encounter type (subsequent with routine healing). Ensure the medical record specifies the fracture's progression and confirms routine healing to support the "subsequent encounter" and "routine healing" modifiers.

Book a walkthrough

S49.021D policy automation walkthrough

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