ASHLEY WEAVER LPC
NPI 1790367225
Counselor - Professional in King Of Prussia, PA
About Ashley Weaver Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ASHLEY WEAVER LPC (NPI 1790367225) is an individual professional provider in King Of Prussia, Pennsylvania, licensed in Pennsylvania (PC010316) and active in the NPI registry since April 2021. She is enrolled in Medicare PECOS and maintains a secondary practice location in Media.
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)
Ashley Weaver Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 14
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
KING OF PRUSSIA, PA 19406
KING OF PRUSSIA, PA 19406
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 Ashley Weaver's NPI number?
The NPI number for Ashley Weaver is 1790367225. It was assigned to this individual provider in the NPPES registry on April 23, 2021.
Where is Ashley Weaver located?
Ashley Weaver practices at 357 S Gulph Rd Ste 260, King Of Prussia, PA 19406. The listed phone number is (610) 892-3800.
What is Ashley Weaver's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Ashley Weaver enrolled in Medicare?
Yes. Ashley Weaver is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ashley Weaver was last updated on June 29, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 40 days 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.