Dr. Jeffrey A. Strommen, MD

Dr. Jeffrey A. Strommen, MD http://cdn.hgimg.com/img/silhouettes/silhouette-male_w120h160_v1.jpg Get the phone number, address, office locations, and directions for Dr. Jeffrey A. Strommen, MD.

Specializes in Spinal Cord Injury Medicine • Male • Age 51

200 1st St SW
Rochester, MN 55905
OverviewExperienceHospital QualityPatient SatisfactionAppointments & Offices
Healthgrades

7 Tips to Prepare for Your Appointment

The key to a successful appointment is communication. To get the most out of your visit, prepare ahead of time so you can lead the conversation with your doctor. These 7 tips will get you ready

1

Appointments & Offices

Check insurance plans, locations and make an appointment

Is Dr. Strommen accepting new patients?

Yes.

What insurance does he accept?

  • Aetna
  • Amalgamated Clothing & Textile Workers Union
  • Anthem
  • Assurant Health
  • BCBS Illinois
  • Blue Cross and Blue Shield
  • CIGNA
  • Commercial Insurance Company
  • First Choice Health
  • GEHA
  • Humana
  • Medicaid
  • Medical Mutual of Ohio
  • Medicare
  • MultiPlan
More
  • Principal Financial
  • Priority Health
  • Tricare
  • United HealthCare
  • UnitedHealthCare
Less

Office Locations

A
Mayo Clinic
200 1st St SW
Rochester, MN 55905
(507) 284-2511 (Office)
B
Mayo Clinic
200 1st St SW
Rochester, MN 55905
(507) 284-2511 (Office)
  • Free Standing Surgery Center
Loading map. Loading map...

Find the Right Doctor For You.

More Spinal Cord Injury Specialists near Rochester, MN

  • Spinal Cord Injury Specialist
  • Within 100 miles of Rochester, MN 55905
Dr. Mark W. Christopherson, MD
Spinal Cord Injury Medicine
Same location as Dr. Strommen
Dr. Toni J. Hanson, MD
Spinal Cord Injury Medicine
Same location as Dr. Strommen
Dr. Carl W. Chan, MD
Spinal Cord Injury Medicine
Same location as Dr. Strommen
Dr. Gary D. Goldish, MD
Spinal Cord Injury Medicine
70.82 miles away
Dr. Jacalyn A. Kawiecki, MD
Spinal Cord Injury Medicine
76.46 miles away

Find Spinal Cord Injury Specialists Near Rochester, MN

The VideoCalloutContainer had no content.