Profile Photo of Dr. Brian A. Gray, MD

Dr. Brian A. Gray, MD Visit Healthgrades for information on Dr. Brian A. Gray, MD. Find Phone & Address information, medical practice history, affiliated hospitals and more.

Specializes in Internal Medicine • Male

520 Medical Dr Ste 200
Bountiful, UT 84010
OverviewPhone & AddressExperienceHospital QualityPatient Satisfaction

Key things you need to know about
Dr. Gray:


Phone & Address

Check insurance plans, locations and make an appointment

Dr. Gray's Offices

Lakeview Internal Medicine
Lakeview Internal Medicine
520 Medical Dr Ste 200
Bountiful, UT 84010
MoreSchedule an appointment

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


Dr. Gray's Experience

Research training, expertise and qualifications

Dr. Gray's Specialties

  • Internal Medicine

More About Dr. Gray's Background

MoreGet the facts on Dr. Gray


Hospital Quality

The right hospital is as important as the right doctor

Lakeview Hospital
630 Medical Dr
Bountiful, UT 84010

MoreKnow where you'll be treated


9 Facts About Hospital Quality

Patients’ risk of dying during a hospital stay for heart bypass surgery could be 87.4% lower, on average, at a hospital rated 5 stars compared to a hospital rated 1 star for that procedure. Choosing the right hospital is critical to your health. View Slideshow


Patient Satisfaction

Patients' feedback on their experience with Dr. Gray

Have you recently visited Dr. Gray?

Be the first to evaluate Dr. Gray by taking our Patient Satisfaction Survey.

Your feedback will help other patients make informed decisions, and let the doctor know how he's doing.


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

The VideoCalloutContainer had no content.