PORTIA LEIGH BENNETT LPC
NPI 1043003791
Counselor - Professional in Stafford, VA
About Portia Leigh Bennett Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
PORTIA LEIGH BENNETT LPC (NPI 1043003791) is an individual professional provider in Stafford, Virginia, licensed in Virginia (0701014894) and active in the NPI registry since May 2025. She is enrolled in Medicare PECOS, maintains a secondary practice location in Stafford, and is a graduate of Other (1998).
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 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)
Portia Leigh Bennett Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
STAFFORD, VA 22554
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 Portia Bennett's NPI number?
The NPI number for Portia Bennett is 1043003791. It was assigned to this individual provider in the NPPES registry on May 27, 2025.
Where is Portia Bennett located?
Portia Bennett practices at 1745 Richmond Hwy, Stafford, VA 22554. The listed phone number is (540) 288-5245.
What is Portia Bennett's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Portia Bennett enrolled in Medicare?
Yes. Portia Bennett is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Portia Bennett was last updated on May 27, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 14 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.