DR. GLENNIS JARRETT D.D.S.
NPI 1669438321
Dentist - General Practice in Hampton, VA
About Dr. Glennis Jarrett D.d.s. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. GLENNIS JARRETT D.D.S. (NPI 1669438321) is an individual general practice provider in Hampton, Virginia, licensed in New Jersey (DI018579) and active in the NPI registry since April 2006.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Other Identifiers 1
Accepted Insurance
Other Providers at the Same Location NPPES 9
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
LANGLEY AFB, VA 23665
LANGLEY AFB, VA 23665
HAMPTON, VA 23665
HAMPTON, VA 23665
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 Glennis Jarrett's NPI number?
The NPI number for Glennis Jarrett is 1669438321. It was assigned to this individual provider in the NPPES registry on April 21, 2006. The provider is also known as Dr. Glennis Payton D.D.S..
Where is Glennis Jarrett located?
Glennis Jarrett practices at 76 Nealy Blvd, Hampton, VA 23665. The listed phone number is (757) 764-6824.
What is Glennis Jarrett's specialty?
The primary specialty registered for this NPI is Dentist, specializing in General Practice, with taxonomy code 1223G0001X.
What insurance does Glennis Jarrett accept?
Health plans from Blue Cross and Blue Shield of Montana, Blue Cross and Blue Shield of Oklahoma, Blue Cross and Blue Shield of Texas, Humana and Renaissance Dental list Glennis Jarrett 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 Glennis Jarrett was last updated on January 23, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 months 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.