TAMANTHA WHITE APRN, FNP-BC
NPI 1245624378
Nurse Practitioner - Family in Danbury, CT
About Tamantha White Aprn, Fnp-bc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
TAMANTHA WHITE APRN, FNP-BC (NPI 1245624378) is an individual family provider in Danbury, Connecticut, licensed in Connecticut (13908) and active in the NPI registry since March 2015. She is enrolled in Medicare PECOS and is a graduate of Mercy College (2023).
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)
Tamantha White Aprn, Fnp-bc 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 06810 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 Tamantha White's NPI number?
The NPI number for Tamantha White is 1245624378. It was assigned to this individual provider in the NPPES registry on March 26, 2015.
Where is Tamantha White located?
Tamantha White practices at 35 White St, Danbury, CT 06810. The listed phone number is (203) 816-2255.
What is Tamantha White's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Tamantha White enrolled in Medicare?
Yes. Tamantha White is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Tamantha White was last updated on September 19, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 10 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.