DR. JEFFREY M GITELMAN D.D.S.
NPI 1629056361
Dentist - Oral and Maxillofacial Surgery in Washington, DC
About Dr. Jeffrey M Gitelman D.d.s. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JEFFREY M GITELMAN D.D.S. (NPI 1629056361) is an individual oral and maxillofacial surgery provider in Washington, District Of Columbia, licensed in District Of Columbia (2822) and active in the NPI registry since January 2006.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 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.
WASHINGTON, DC 20036
WASHINGTON, DC 20036
WASHINGTON, DC 20036
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 Jeffrey Gitelman's NPI number?
The NPI number for Jeffrey Gitelman is 1629056361. It was assigned to this individual provider in the NPPES registry on January 4, 2006.
Where is Jeffrey Gitelman located?
Jeffrey Gitelman practices at 1234 19th St NW 508, Washington, DC 20036. The listed phone number is (202) 223-3391.
What is Jeffrey Gitelman's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Oral and Maxillofacial Surgery, with taxonomy code 1223S0112X.
What insurance does Jeffrey Gitelman accept?
Health plans from Anthem Blue Cross and Blue Shield, Blue Cross and Blue Shield of Montana, Blue Cross and Blue Shield of Oklahoma and Blue Cross and Blue Shield of Texas list Jeffrey Gitelman 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 Jeffrey Gitelman was last updated on September 11, 2008. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 17 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.