Dr. John E. Lassetter, MD

Dr. John E. Lassetter, MD http://d1ffafozi03i4l.cloudfront.net/img/prov/X/Y/2/XY24D_w120h160.jpg Patient Surveys for Dr. John E. Lassetter, MD, Idaho Falls, ID, Interventional Cardiology & Cardiology & Internal Medicine

Specializes in Interventional Cardiology • Male • Age 55

2001 S Woodruff Ave Ste 3
Idaho Falls, ID 83404
OverviewExperienceHospital QualityPatient SatisfactionAppointments & Offices
Healthgrades
patient satisfaction matters

8 Facts About Patient Satisfaction Surveys

Patient satisfaction surveys provide a standardized way of reporting about healthcare experiences. But there can be more than meets the eye when reviewing scores. Here's what you should know

Patient Satisfaction

Patients' feedback on their experience with Dr. Lassetter

Dr. John E. Lassetter, MD
Are you Dr. Lassetter?
Post a response on your personalized profile.

Likelihood to Recommend

5.0
  • 5 responses
  • 1 review
1 5 5

5 out of 5

More Details

5 out of 5
-Idaho Falls, ID |

I have gone to many many cardiologists to help with symptoms from my PFO and Dr. Lassetter listened and made the whole experience very simple. He worked with my insurance and there was not problem to get it covered. He explained that there were no guarantees but thought it would help me. I feel amazing after the surgery! He really listens and has a big heart. He knows his stuff. Best doc ever

Flag Comment
Was this review helpful? Yes No

Find the Right Doctor For You.

  • Interventional Cardiology
Dr. Andrew Carter, DO
Cardiology
Same location as Dr. Lassetter
Dr. Paul Gerlach, MD
Cardiology
0.85 miles away
Dr. John Chambers Jr., MD
Cardiology
0.85 miles away
Dr. Thomas Maley, MD
Cardiology
Same location as Dr. Lassetter
Dr. Patrick D. Gorman, MD
Cardiology
Same location as Dr. Lassetter
Dr. Ricky Latham, MD
Cardiology
0.73 miles away
Dr. Fernando Grigera, MD
Cardiology
46.93 miles away
Dr. Andrew Carter, DO
Interventional Cardiology
0.77 miles away

Find Interventional Cardiology Specialists Near Idaho Falls, ID

The VideoCalloutContainer had no content.