Codes / ICD10CM / S12.14XD

S12.14XD Type III traumatic spondylolisthesis of second cervical vertebra, subsequent encounter for fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Type III traumatic spondylolisthesis of second cervical vertebra, subsequent encounter for fracture with routine healing

Summary

This condition involves a Type III traumatic spondylolisthesis of the second cervical vertebra (C2), with the encounter classified as a subsequent visit for a fracture showing routine healing. Spondylolisthesis refers to the displacement of one vertebra relative to another, and Type III indicates a specific pattern of injury involving the C2 vertebra. The "subsequent encounter" modifier denotes follow-up care after the initial injury, while "routine healing" indicates the fracture is progressing normally without complications.

Causes

Type III traumatic spondylolisthesis of the second cervical vertebra is typically caused by high-impact trauma, such as motor vehicle accidents, falls from height, or direct force to the head or neck. The trauma disrupts the vertebral and ligamentous structures, leading to the displacement of C2 relative to adjacent vertebrae. Underlying bone conditions, like osteoporosis, may increase susceptibility to such injuries.

Risk Factors

  • Participation in high-risk activities (e.g., contact sports, extreme sports)
  • Osteoporosis or other bone-weakening conditions
  • Advanced age, due to decreased bone density
  • History of neck injuries or spinal abnormalities

Symptoms

  • Neck pain or stiffness
  • Reduced range of motion in the neck
  • Swelling or bruising around the neck area
  • Potential neurological symptoms (e.g., numbness, tingling, weakness) if the spinal cord or nerves are affected

Diagnosis

Diagnosis involves a physical examination and imaging studies, such as X-rays, CT scans, or MRIs, to assess the fracture's location, displacement, and potential spinal cord involvement. A thorough evaluation of healing progress is conducted to confirm routine healing and guide subsequent care.

Treatment Options

Treatment may include immobilization with a cervical collar or brace to stabilize the spine, pain management, and physical therapy to restore mobility and strength. Surgical intervention is rarely needed for routine healing but may be considered if instability persists. Follow-up imaging may be used to monitor healing.

Prognosis and Follow-Up

With routine healing, the prognosis is generally favorable, though recovery time varies. Follow-up care focuses on monitoring healing progress, managing symptoms, and preventing complications. Most patients regain function with appropriate rehabilitation, but long-term follow-up may be necessary to assess spinal stability.

Complications

Potential complications include persistent neck pain, reduced mobility, or delayed union of the fracture. Rarely, neurological deficits or spinal instability may occur if healing is not routine.

Lifestyle & Prevention

  • Avoid high-risk activities that may cause neck trauma
  • Maintain bone health through diet and exercise
  • Use protective gear during sports or activities with fall risks
  • Follow post-injury care instructions to support healing

When to Seek Professional Help

Seek medical attention if symptoms worsen, new neurological symptoms develop, or there is increased pain or swelling. Immediate care is needed for signs of spinal cord compression, such as difficulty breathing or loss of bladder/bowel control.

Tips for Medical Coders

Document the encounter as a subsequent visit for fracture with routine healing. Ensure clinical notes specify the Type III traumatic spondylolisthesis of C2 and confirm healing progress. The code S12.14XD requires clear documentation of the fracture type, subsequent encounter, and routine healing status to support accurate coding.

Medical Policies and Guidelines

Related policies from health plans

Book a walkthrough

S12.14XD policy automation walkthrough

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