Profile Photo of Dr. David J. Klashman, MD

Dr. David J. Klashman, MD Visit Healthgrades for information on Dr. David J. Klashman, MD. Find Phone & Address information, medical practice history, affiliated hospitals and more.

Specializes in Rheumatology • Male • Age 57

23441 Madison St Ste 340
Torrance, CA 90505
OverviewPhone & AddressExperienceHospital QualityPatient Satisfaction

Key things you need to know about
Dr. Klashman:


Phone & Address

Check insurance plans, locations and make an appointment

Accepting new patients?

  • Yes

Dr. Klashman's Offices

Arthritis Treatment Center
Arthritis Treatment Center
23441 Madison St Ste 340
Torrance, CA 90505
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. Klashman's Experience

Research training, expertise and qualifications

Dr. Klashman's Specialties

  • Rheumatology

Procedures Dr. Klashman Performs

Conditions Dr. Klashman Treats

MoreGet the facts on Dr. Klashman


Hospital Quality

The right hospital is as important as the right doctor

Providence Little Company of Mary Medical Center San Pedro
1300 W 7th St
San Pedro, CA 90732
Torrance Memorial Medical Center
3330 Lomita Blvd
Torrance, CA 90505

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. Klashman


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.