MR. STEPHEN ROOD DEXTER
NPI 1124287636
Audiologist in Glendale, AZ
About Mr. Stephen Rood Dexter NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MR. STEPHEN ROOD DEXTER (NPI 1124287636) is an individual audiologist in Glendale, Arizona and active in the NPI registry since June 2008. He maintains 2 additional practice locations.
NPPES Registry Identity
Specialties & Licenses 3
Secondary Practice Locations 2
Other Identifiers 2
Accepted Insurance
Areas of Expertise CMS Part B claims 7
Services this provider delivered to Medicare fee-for-service patients, from the CMS Medicare utilization data. Higher counts generally reflect more experience with a service; care delivered outside Medicare is not included.
Other Providers at the Same Location NPPES 11
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
GLENDALE, AZ 85306
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 Stephen Dexter's NPI number?
The NPI number for Stephen Dexter is 1124287636. It was assigned to this individual provider in the NPPES registry on June 9, 2008.
Where is Stephen Dexter located?
Stephen Dexter practices at 5750 W Thunderbird Rd Ste F600, Glendale, AZ 85306. The listed phone number is (602) 863-4203.
What is Stephen Dexter's specialty?
The primary specialty registered for this NPI is Audiologist with taxonomy code 231H00000X.
What insurance does Stephen Dexter accept?
Health plans from Blue Cross Blue Shield of Arizona list Stephen Dexter 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 Stephen Dexter was last updated on April 24, 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.