Dr. Carlos Almeida, MD

Dr. Carlos Almeida, MD http://d1ffafozi03i4l.cloudfront.net/img/silhouettes/silhouette-male_w120h160_v1.jpg Dr. Carlos Almeida, MD, Appointments, Prospect, CT, Internal Medicine

Specializes in Internal Medicine • Male • Age 43

166 Waterbury Rd Ste 300
Prospect, CT 06712
OverviewExperienceHospital QualityPatient SatisfactionAppointments & Offices
Recommended Reading
1

Appointments & Offices

Check insurance plans, locations and make an appointment

Is Dr. Almeida accepting new patients?

  • Yes.

What insurance does he accept?*

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

Office Locations

A
Primary Care Partners
166 Waterbury Rd Ste 300
Prospect, CT 06712
(203) 709-5300 (Office)
Loading map...

Know Before You Go

The Painkiller and Constipation Connection

If you're taking narcotic or opioid pain medicines, constipation is a likely side effect.

10 Surprising Migraine Facts

Suffer from migraines? Here are several facts you need to know.

Heart Healthy Pain Relief

Know the safest types of pain relief for patients with high heart disease risk.

6 Surprising Facts About Asthma

There’s a lot happening under the surface with asthma that might surprise you. 

Vitamin Deficiencies and Diabetes

Studies suggest a lack of certain nutrients in your diet may affect how diabetes develops. 

Find the Right Doctor For You.

  • Internal Medicine
Dr. Edmund P. Quinn, MD
Internal Medicine
1.61 miles away
Dr. Dmitry Albin, MD
Internal Medicine
Same location as Dr. Almeida
Dr. Adepeju Champion, MD
Internal Medicine
4.14 miles away
Dr. Julia Zefirova, MD
Internal Medicine
Same location as Dr. Almeida
Dr. Jeffrey Stein, MD
Internal Medicine
3.13 miles away
Dr. Lynn Phillips, MD
Internal Medicine
4.14 miles away
Dr. Leslie Coopersmith, MD
Internal Medicine
2.99 miles away
Dr. James Uberti, MD
Internal Medicine
Same location as Dr. Almeida
Dr. Frank Longo, MD
Internal Medicine
4.1 miles away
Dr. Alexander Alvarez, MD
Internal Medicine
Same location as Dr. Almeida
The VideoCalloutContainer had no content.