DR. ROGER W SCOTT DDS
NPI 1821110552
Dentist - General Practice in Daytona Beach, FL
About Dr. Roger W Scott Dds NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. ROGER W SCOTT DDS (NPI 1821110552) is an individual general practice provider in Daytona Beach, Florida, licensed in Florida (DN0011875) and active in the NPI registry since April 2007. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
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. Roger W Scott Dds 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 32118 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 Roger Scott's NPI number?
The NPI number for Roger Scott is 1821110552. It was assigned to this individual provider in the NPPES registry on April 4, 2007. The provider is also known as Dr. Jeffrey A Scott Dds.
Where is Roger Scott located?
Roger Scott practices at 212 Oakridge Blvd, Daytona Beach, FL 32118. The listed phone number is (386) 255-3626.
What is Roger Scott's specialty?
The primary specialty registered for this NPI is Dentist, specializing in General Practice, with taxonomy code 1223G0001X.
Is Roger Scott enrolled in Medicare?
Yes. Roger Scott is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Roger Scott 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.