Codes / ICD10CM / S42.192D

S42.192D Fracture of other part of scapula, left shoulder, subsequent encounter for fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Fracture of other part of scapula, left shoulder, subsequent encounter for fracture with routine healing

Summary

A fracture of other part of the scapula, left shoulder, subsequent encounter for fracture with routine healing, refers to a follow-up visit for a previously diagnosed break in a specific, non-specified portion of the left shoulder blade bone. This code applies when the fracture is in the healing phase with expected, uncomplicated progress. The condition involves damage to a distinct segment of the scapula, such as the coracoid process or spine, and is documented during a routine check-up to assess healing status.

Causes

Traumatic injury is the primary cause of fractures to other parts of the scapula. Common mechanisms include falls, motor vehicle accidents, sports-related impacts, or direct blows to the shoulder or upper back. High-energy trauma, such as that from a collision, often results in fractures of specific scapular structures. The subsequent encounter code is used when the initial injury has been treated, and the focus is on monitoring routine healing.

Risk Factors

  • Participation in contact sports or high-impact activities.
  • Osteoporosis or other bone-weakening conditions.
  • Advanced age, which may increase susceptibility to falls.
  • Previous shoulder or upper arm injuries that affect bone integrity.

Symptoms

  • Pain in the shoulder or upper back, especially with movement.
  • Swelling, bruising, or tenderness over the affected scapular area.
  • Limited range of motion in the shoulder joint.
  • Difficulty lifting or rotating the arm.
  • In severe cases, visible deformity or instability.

Diagnosis

Diagnosis typically involves a physical examination to assess pain, swelling, and range of motion. Imaging studies, such as X-rays or CT scans, are used to confirm the fracture location and healing progress. The subsequent encounter code is appropriate when the fracture is healing as expected, with no signs of complications like nonunion or malunion.

Treatment Options

Treatment focuses on pain management, immobilization (if needed), and physical therapy to restore function. Routine follow-up may include monitoring for healing through imaging and adjusting rehabilitation plans. Surgical intervention is rarely required for uncomplicated fractures in this category.

Prognosis and Follow-Up

Prognosis is generally favorable for fractures with routine healing, especially with proper care and rehabilitation. Follow-up visits are scheduled to assess progress, ensure the fracture is healing correctly, and address any functional limitations. Most patients regain full or near-full shoulder function over time.

Complications

  • Nonunion or delayed healing.
  • Malunion (improper healing).
  • Chronic pain or stiffness.
  • Nerve or blood vessel damage (rare).

Lifestyle & Prevention

  • Use protective gear during high-impact activities.
  • Maintain bone health through diet and exercise.
  • Avoid falls by modifying home environments (e.g., removing tripping hazards).
  • Follow post-injury rehabilitation guidelines to support healing.

When to Seek Professional Help

Seek medical attention if pain worsens, swelling increases, or movement becomes more limited. Signs of infection (e.g., fever, redness) or new deformity also warrant prompt evaluation.

Tips for Medical Coders

Use this code for a subsequent encounter when the fracture is healing routinely. Document the encounter as a follow-up for a previously diagnosed scapular fracture, with evidence of expected progress. Ensure the fracture site is specified as the left shoulder and that the healing is uncomplicated. Avoid using this code for initial encounters or fractures with complications.

Book a walkthrough

S42.192D policy automation walkthrough

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