Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Common Name: Stress Fracture
- Medical Term: Stress fracture, left foot, subsequent encounter for fracture with routine healing
Summary
A stress fracture in the left foot is a small crack or severe bruising within a bone, typically resulting from repetitive stress or overuse. This code indicates a subsequent encounter for a fracture with routine healing, meaning the fracture is progressing as expected without complications.
Causes
Stress fractures in the left foot commonly arise from repetitive force or overuse, such as prolonged running, jumping, or high-impact activities. Sudden increases in physical activity intensity or volume, improper training techniques, and inadequate recovery can also contribute to their development.
Risk Factors
- Participation in high-impact sports or activities that involve repetitive weight-bearing
- Sudden escalation in activity level without proper conditioning
- Underlying bone conditions like osteoporosis or osteopenia
- Poor footwear or biomechanical abnormalities affecting gait
- Nutritional deficiencies, particularly in calcium or vitamin D
Symptoms
- Localized pain that worsens with activity and improves with rest
- Swelling, tenderness, or bruising around the affected area
- Pain that may persist even at rest in advanced cases
- Possible difficulty bearing weight on the affected limb
Diagnosis
Diagnosis involves a physical examination to assess pain, swelling, and tenderness. Imaging tests such as X-rays, MRI, or bone scans may be used to confirm the fracture, especially if it is not visible on initial X-rays. The subsequent encounter code indicates the fracture is healing routinely, so documentation should reflect ongoing monitoring and expected progress.
Treatment Options
- Rest and avoidance of activities that exacerbate the injury
- Use of protective footwear or braces to stabilize the foot
- Physical therapy to strengthen surrounding muscles and improve flexibility
- Gradual return to activity while monitoring for symptoms
- Pain management as needed
Prognosis and Follow-Up
With proper treatment and adherence to activity modifications, most stress fractures heal within 6–8 weeks. Routine follow-up ensures the fracture is healing as expected, and imaging may be repeated if symptoms persist or worsen. Return to high-impact activities should be gradual to prevent re-injury.
Complications
- Delayed healing or nonunion if activity is not adequately restricted
- Progression to a complete fracture with continued stress
- Chronic pain or functional limitations if not properly managed
- Recurrence, especially with premature return to high-impact activities
Lifestyle & Prevention
- Gradually increase activity intensity and volume to avoid overuse
- Wear supportive, well-fitting footwear appropriate for the activity
- Maintain bone health through adequate nutrition, including calcium and vitamin D
- Incorporate strength training and flexibility exercises to support the foot and ankle
- Allow sufficient rest and recovery between high-impact sessions
When to Seek Professional Help
Seek medical attention if pain worsens, does not improve with rest, or is accompanied by significant swelling, bruising, or difficulty bearing weight. Prompt evaluation is important if symptoms suggest the fracture is not healing as expected or if there are signs of complications.
Tips for Medical Coders
This code (M84.375D) is used for a subsequent encounter for a stress fracture of the left foot with routine healing. Documentation should clearly indicate the fracture is progressing normally, with no signs of delayed healing, nonunion, or complications. The "subsequent encounter" modifier (D) applies when the patient is receiving active treatment for the fracture during the healing phase, and routine healing is confirmed. Ensure clinical notes reflect ongoing monitoring and expected recovery to support accurate coding.
Medical Policies and Guidelines
Related policies from health plans
M84.375D policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.