Codes / ICD10CM / S59.221D

S59.221D Salter-Harris Type II physeal fracture of lower end of radius, 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 lower end of radius, right arm, subsequent encounter for fracture with routine healing

Summary

This condition describes a Salter-Harris Type II fracture involving the growth plate (physeal) at the lower end of the right radius bone, occurring during a subsequent encounter for fracture care with evidence of routine healing. It typically affects children and adolescents and involves a fracture through the growth plate and a portion of the metaphysis. The injury is often the result of trauma to the forearm near the wrist joint.

Causes

Salter-Harris Type II physeal fractures commonly occur due to direct impact, such as a fall onto an outstretched hand, or forceful twisting of the forearm. These injuries are frequently associated with activities involving sudden stops, collisions, or high-impact forces.

Risk Factors

  • Children and adolescents are at higher risk due to the presence of growth plates.
  • Participation in contact sports or activities with a high likelihood of falls increases risk.
  • Certain genetic or metabolic conditions affecting bone development may also elevate susceptibility.

Symptoms

  • Pain and swelling near the wrist or forearm.
  • Difficulty moving the wrist or hand.
  • Tenderness to touch at the fracture site.
  • Possible visible deformity or bruising around the affected area.

Diagnosis

Physical examination by a healthcare professional to assess pain, swelling, and range of motion. Imaging tests, especially X-rays, to visualize the fracture and determine its extent. Additional imaging (e.g., MRI) may be used if the fracture is not clearly visible on X-rays.

Treatment Options

  • Immobilization using a cast or splint to support the fracture during healing.
  • Pain management with over-the-counter or prescription medications.
  • Physical therapy to restore strength and range of motion after immobilization.
  • Surgical intervention may be required for severe or displaced fractures.

Prognosis and Follow-Up

With appropriate treatment, most Salter-Harris Type II fractures heal without long-term complications. Routine follow-up appointments are necessary to monitor healing progress and ensure proper recovery. The duration of follow-up depends on the severity of the fracture and the patient's response to treatment.

Complications

  • Premature closure of the growth plate, potentially leading to limb length discrepancy.
  • Malunion or nonunion of the fracture.
  • Chronic pain or stiffness in the wrist or forearm.
  • Nerve or blood vessel damage in severe cases.

Lifestyle & Prevention

  • Use protective gear during sports or activities with a high risk of falls.
  • Ensure proper technique and supervision in activities involving the wrist or forearm.
  • Maintain bone health through a balanced diet rich in calcium and vitamin D.
  • Avoid high-impact activities until fully healed and cleared by a healthcare provider.

When to Seek Professional Help

Seek immediate medical attention if experiencing severe pain, swelling, or deformity after an injury. Contact a healthcare provider if symptoms worsen or do not improve with initial treatment, or if there are signs of infection (e.g., fever, increased redness, or drainage from the injury site).

Tips for Medical Coders

When coding for this condition, ensure the documentation specifies the Salter-Harris Type II classification, the right arm involvement, and the subsequent encounter for fracture with routine healing. Verify that the encounter aligns with the "subsequent encounter" phase of fracture care and that healing is documented as routine. Accurate coding requires clear documentation of the fracture type, location, and healing status.

Book a walkthrough

S59.221D policy automation walkthrough

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