DR. ALEXANDER SERGEY LITVINOV DDS
NPI 1194812974
Dentist - Dental Public Health in Philadelphia, PA
About Dr. Alexander Sergey Litvinov Dds NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. ALEXANDER SERGEY LITVINOV DDS (NPI 1194812974) is an individual dental public health provider in Philadelphia, Pennsylvania, licensed in Pennsylvania (DS043891) and active in the NPI registry since October 2006.
NPPES Registry Identity
Specialties & Licenses 2
Accepted Insurance
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
PHILADELPHIA, PA 19140
PHILADELPHIA, PA 19140
Frequently Asked Questions NPPES & CMS
Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.
What is Alexander Litvinov's NPI number?
The NPI number for Alexander Litvinov is 1194812974. It was assigned to this individual provider in the NPPES registry on October 5, 2006.
Where is Alexander Litvinov located?
Alexander Litvinov practices at 3223 N Broad St, Philadelphia, PA 19140. The listed phone number is (215) 707-2863.
What is Alexander Litvinov's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Dental Public Health, with taxonomy code 1223D0001X.
What insurance does Alexander Litvinov accept?
Health plans from Anthem Blue Cross and Blue Shield, BEST Life, Blue Cross and Blue Shield of Alabama, Blue Cross and Blue Shield of Montana and Blue Cross and Blue Shield of Oklahoma and 7 other insurers list Alexander Litvinov as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Alexander Litvinov was last updated on January 9, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 years ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.