Dr. Brian N. Naftulin, MD

Dr. Brian N. Naftulin, MD http://cdn.hgimg.com/img/prov/X/C/N/XCNWR_w120h160_v5857.jpg Visit Healthgrades for information on Dr. Brian N. Naftulin, MD. Find Phone & Address information, medical practice history, affiliated hospitals and more.

Specializes in Urology • Male

1561 Creekside Dr Suite 170
Folsom, CA 95630
OverviewPhone & AddressExperienceHospital QualityPatient Satisfaction

Key things you need to know about
Dr. Naftulin:


Phone & Address

Check insurance plans, locations and make an appointment

Accepting new patients?

  • Yes

Dr. Naftulin's Offices

Mercy Medical Group
Mercy Medical Group - Folsom
1561 Creekside Dr Suite 170
Folsom, CA 95630
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. Naftulin's Experience

Research training, expertise and qualifications

Dr. Naftulin's Specialties

Procedures Dr. Naftulin Performs

  • da Vinci® Robotic Surgery
  • Urological Surgery

Conditions Dr. Naftulin Treats

  • Kidney Disease
  • Urinary Disorders

MoreGet the facts on Dr. Naftulin


Hospital Quality

The right hospital is as important as the right doctor

Mercy Hospital of Folsom
1650 Creekside Drive
Folsom, CA 95630
Mercy San Juan Medical Center
6501 Coyle Avenue
Carmichael, CA 95608

See All 3 Hospital Locations

MoreKnow where you'll be treated


9 Facts About Hospital Quality

You have an 85.2% lower risk of dying at a hospital with 5 stars for heart bypass surgery compared to a hospital with a 1 star. Choosing the right hospital is critical to your health. View Slideshow


Patient Satisfaction

Patients' feedback on their experience with Dr. Naftulin


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.