Codes / ICD10CM / S22.021K

S22.021K Stable burst fracture of second thoracic vertebra, subsequent encounter for fracture with nonunion

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Stable burst fracture of second thoracic vertebra, subsequent encounter for fracture with nonunion (ICD-10-CM: S22.021K)

Summary

This condition involves a stable burst fracture of the second thoracic vertebra (T2) during a subsequent encounter, where the fracture has failed to heal (nonunion). A stable burst fracture typically involves the vertebral body fracturing with fragments extending outward but without significant spinal instability or neurological compromise. The "subsequent encounter" modifier indicates follow-up care after the initial injury, and "nonunion" denotes a fracture that has not healed within the expected timeframe despite treatment.

Causes

Stable burst fractures of the thoracic vertebrae are commonly caused by trauma, such as falls, motor vehicle accidents, or direct high-impact forces to the spine. Osteoporosis or other bone-weakening conditions can predispose to this fracture type. Nonunion may result from inadequate immobilization, poor blood supply to the fracture site, infection, or excessive movement during healing.

Risk Factors

  • Age (older adults with reduced bone density)
  • Osteoporosis or metabolic bone disorders
  • High-impact trauma exposure
  • History of prior vertebral fractures
  • Smoking or poor nutrition affecting bone healing
  • Inadequate initial treatment or immobilization

Symptoms

  • Persistent mid-back pain localized to the T2 region
  • Limited range of motion or stiffness
  • Tenderness at the injury site
  • Possible neurological symptoms (e.g., numbness, weakness) if the nonunion affects spinal stability
  • No signs of routine healing (e.g., reduced pain or improved mobility)

Diagnosis

Physical examination to assess pain, deformity, and neurological function. Imaging studies, including X-rays, CT scans, or MRI, to confirm the fracture pattern, evaluate spinal stability, and assess for nonunion. Additional tests (e.g., bone scans) may be used to assess bone healing. Evaluation of bone density if osteoporosis is suspected.

Treatment Options

Treatment focuses on promoting healing or managing symptoms. Options may include prolonged immobilization (e.g., braces), pain management, physical therapy, or surgical intervention (e.g., bone grafting, spinal fusion) if nonunion persists. Underlying conditions like osteoporosis may require medical management.

Prognosis and Follow-Up

Prognosis depends on the severity of the nonunion and response to treatment. Nonunion may lead to chronic pain or spinal instability. Regular follow-up with imaging is necessary to monitor healing. Long-term management may involve ongoing pain control, activity modification, or surgical correction.

Complications

  • Chronic pain
  • Spinal instability
  • Neurological deficits (e.g., numbness, weakness)
  • Need for surgical intervention
  • Reduced quality of life due to persistent symptoms

Lifestyle & Prevention

  • Avoid high-impact activities that risk re-injury.
  • Maintain bone health through adequate nutrition (e.g., calcium, vitamin D) and exercise.
  • Use proper body mechanics to reduce spinal stress.
  • Follow prescribed immobilization or activity restrictions during healing.

When to Seek Professional Help

Seek care if experiencing worsening pain, new neurological symptoms (e.g., numbness, weakness), or signs of infection (e.g., fever, redness). Persistent symptoms without improvement after initial treatment also warrant evaluation.

Tips for Medical Coders

Document the fracture type (stable burst), vertebral level (T2), and encounter type (subsequent) clearly. Specify "nonunion" to indicate failed healing. Ensure clinical documentation supports the diagnosis and encounter context. Code S22.021K is used for follow-up care of a stable burst fracture of T2 with nonunion.

Book a walkthrough

S22.021K policy automation walkthrough

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