Dr. Ramesh Bansal, MD

Dr. Ramesh Bansal, MD http://d1ffafozi03i4l.cloudfront.net/img/silhouettes/silhouette-male_w120h160_v1.jpg Get the phone number, address, office locations, and directions for Dr. Ramesh Bansal, MD.

Specializes in Cardiology • Male • Age 66

11234 Anderson St Rm 7700H
Loma Linda, CA 92354
OverviewExperienceHospital QualityPatient SatisfactionAppointments & Offices
Recommended Reading
1

Appointments & Offices

Check insurance plans, locations and make an appointment

Is Dr. Bansal accepting new patients?

If you are a new patient, please check with Dr. Bansal before scheduling an appointment.

What insurance does he accept?*

More
Less
* Please verify this information when scheduling an appointment.

Office Locations

A
Loma Linda University Med Ctr
Loma Linda University Internation Heart Institute
11234 Anderson St Rm 7700H
Loma Linda, CA 92354
(909) 558-4201 (Office)
(909) 558-4212 (Fax)
Loading map...

Know Before You Go

7 Surprising Facts About Heart Disease

Most people know a healthy lifestyle helps your heart. But you may be surprised by what you don't know.

7 Complications of Heart Disease

When the heart gets less blood than it needs, complications can develop.

How Alcohol Affects Your Heart Health

Is red wine really good for your heart?  The research is mixed.

Find the Right Doctor For You.

  • Cardiology
Dr. Michael Y. Chan, MD
Cardiology
39.21 miles away
Dr. Rami Turk, MD
Cardiology
Same location as Dr. Bansal
Dr. Islam Abudayyeh, MD
Cardiology
Same location as Dr. Bansal
Dr. Ronald Lo, MD
Clinical Cardiac Electrophysiology
0.65 miles away
Dr. David Choe, MD
Cardiology
Same location as Dr. Bansal
Dr. Rajesh S. Banker, MD
Clinical Cardiac Electrophysiology
47.92 miles away
Dr. Michael D. Moran, MD
Interventional Cardiology
39.37 miles away
Dr. Ramin Assadi Azarbaijani, MD
Cardiology
Same location as Dr. Bansal
Dr. Vilma Torres, MD
Cardiology
Same location as Dr. Bansal
Dr. Andrew A. Zadeh, MD
Cardiology
6.01 miles away
Dr. Ramin B. Ashtiani, MD
Cardiology
29.45 miles away
The VideoCalloutContainer had no content.