DR. JEFFERY W. KAZE DMD
NPI 1235157736
Dentist in Union City, TN
About Dr. Jeffery W. Kaze Dmd NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JEFFERY W. KAZE DMD (NPI 1235157736) is an individual dentist in Union City, Tennessee, licensed in Tennessee (10123) and active in the NPI registry since July 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dr. Jeffery W. Kaze Dmd 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 38261 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 6
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
UNION CITY, TN 38261
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 Jeffery Kaze's NPI number?
The NPI number for Jeffery Kaze is 1235157736. It was assigned to this individual provider in the NPPES registry on July 17, 2006.
Where is Jeffery Kaze located?
Jeffery Kaze practices at 201 W Main St, Union City, TN 38261. The listed phone number is (530) 339-1264.
What is Jeffery Kaze's specialty?
The primary specialty registered for this NPI is Dentist with taxonomy code 122300000X.
Is Jeffery Kaze enrolled in Medicare?
Yes. Jeffery Kaze is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jeffery Kaze was last updated on July 29, 2015. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 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.