Codes / ICD10CM / S49.111D

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

Summary

This code represents a Salter-Harris Type I fracture, which involves a complete separation of the growth plate (physeal) at the lower end of the right humerus. It is classified as a subsequent encounter for fracture with routine healing, indicating the patient is receiving follow-up care after the initial injury. These fractures are common in children and adolescents due to the relative weakness of the growth plate compared to surrounding bone. The injury typically affects the distal humeral physis, where the upper arm bone meets the elbow joint.

Causes

Trauma is the primary cause, often resulting from a fall onto an outstretched hand or a direct blow to the elbow. Sports-related injuries, such as those from gymnastics or contact sports, are frequent mechanisms. The force applied to the elbow can disrupt the growth plate without necessarily fracturing the adjacent bone.

Risk Factors

  • Age (most common in children and adolescents with open growth plates)
  • Participation in high-impact or contact sports
  • Prior growth plate injuries or developmental abnormalities
  • Activities involving repetitive stress on the elbow

Symptoms

  • Pain and swelling localized to the elbow or lower arm
  • Tenderness over the distal humeral growth plate
  • Limited range of motion in the affected arm
  • Possible visible deformity in severe cases
  • Difficulty moving or bearing weight on the arm

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. The subsequent encounter status indicates the fracture is healing as expected, with no signs of complications.

Treatment Options

  • Immobilization: A cast or splint may be used to stabilize the arm during healing.
  • Closed reduction: Manual realignment of the bone fragments without surgery.
  • Surgical intervention: Required for displaced or unstable fractures to restore proper alignment.
  • Treatment aims to promote proper healing and prevent long-term complications.

Prognosis and Follow-Up

With appropriate treatment, most Salter-Harris Type I fractures heal without long-term issues. Routine follow-up ensures the fracture is healing correctly and the patient regains full function. The subsequent encounter code reflects ongoing monitoring during the healing phase.

Complications

  • Premature closure of the growth plate, potentially leading to limb length discrepancy
  • Chronic pain or stiffness
  • Reduced range of motion
  • Malunion or nonunion of the fracture

Lifestyle & Prevention

  • Use protective gear during sports or high-risk activities.
  • Ensure proper technique and supervision in physical activities.
  • Maintain bone health through a balanced diet rich in calcium and vitamin D.
  • Avoid overuse or repetitive stress on the elbow.

When to Seek Professional Help

Seek medical attention if there is increased pain, swelling, or deformity, or if the arm cannot be moved. Prompt evaluation is important if healing does not progress as expected or if new symptoms develop.

Tips for Medical Coders

This code is specific to the right arm and indicates a subsequent encounter for fracture with routine healing. Documentation should confirm the laterality (right arm), the fracture type (Salter-Harris Type I), and the healing status (routine healing) to support accurate coding. The "subsequent encounter" modifier reflects ongoing care after the initial injury, not active treatment of complications.

Book a walkthrough

S49.111D policy automation walkthrough

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