SHARON ELIZABETH PERRINE LPC
NPI 1417666934
Counselor - Professional in Manassas, VA
About Sharon Elizabeth Perrine Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SHARON ELIZABETH PERRINE LPC (NPI 1417666934) is an individual professional provider in Manassas, Virginia, licensed in Virginia (0701011935) and active in the NPI registry since November 2022. She 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)
Sharon Elizabeth Perrine Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
MANASSAS, VA 20109
MANASSAS, VA 20109
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 Sharon Perrine's NPI number?
The NPI number for Sharon Perrine is 1417666934. It was assigned to this individual provider in the NPPES registry on November 23, 2022. The provider is also known as Sharon Elizabeth Willis.
Where is Sharon Perrine located?
Sharon Perrine practices at 7969 Ashton Ave, Manassas, VA 20109. The listed phone number is (703) 792-7800.
What is Sharon Perrine's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Sharon Perrine enrolled in Medicare?
Yes. Sharon Perrine is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Sharon Perrine was last updated on November 23, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.