DR. BYRON KEITH ELLIOTT D.D.S., M.S.D.
NPI 1689740920
Dentist - Endodontics in Johnson City, TN
About Dr. Byron Keith Elliott D.d.s., M.s.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. BYRON KEITH ELLIOTT D.D.S., M.S.D. (NPI 1689740920) is an individual endodontics provider in Johnson City, Tennessee, licensed in Tennessee (7026) and active in the NPI registry since November 2006. 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)
Dr. Byron Keith Elliott D.d.s., M.s.d. 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 37601 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Byron Elliott's NPI number?
The NPI number for Byron Elliott is 1689740920. It was assigned to this individual provider in the NPPES registry on November 28, 2006.
Where is Byron Elliott located?
Byron Elliott practices at 122 E Watauga Ave, Johnson City, TN 37601. The listed phone number is (423) 232-5770.
What is Byron Elliott's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Endodontics, with taxonomy code 1223E0200X.
Is Byron Elliott enrolled in Medicare?
Yes. Byron Elliott is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Byron Elliott was last updated on July 8, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 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.