ALI GOLSHANI D.D.S.
NPI 1790167617
Dentist in Lakeway, TX
About Ali Golshani D.d.s. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ALI GOLSHANI D.D.S. (NPI 1790167617) is an individual dentist in Lakeway, Texas, licensed in Texas (31091) and active in the NPI registry since June 2015. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Ali Golshani D.d.s. is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 78738 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Other Providers at the Same Location NPPES 2
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Ali Golshani's NPI number?
The NPI number for Ali Golshani is 1790167617. It was assigned to this individual provider in the NPPES registry on June 27, 2015.
Where is Ali Golshani located?
Ali Golshani practices at 5329 Serene Hills Dr Ste 104, Lakeway, TX 78738. The listed phone number is (512) 334-0345.
What is Ali Golshani's specialty?
The primary specialty registered for this NPI is Dentist with taxonomy code 122300000X.
Is Ali Golshani enrolled in Medicare?
Yes. Ali Golshani is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ali Golshani was last updated on March 20, 2018. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 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.