KIMBERLY SPARROW LPC
NPI 1962180836
Counselor - Professional in North Chesterfield, VA
About Kimberly Sparrow Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KIMBERLY SPARROW LPC (NPI 1962180836) is an individual professional provider in North Chesterfield, Virginia, licensed in Virginia (0701011027) and active in the NPI registry since July 2023. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Kimberly Sparrow Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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 Kimberly Sparrow's NPI number?
The NPI number for Kimberly Sparrow is 1962180836. It was assigned to this individual provider in the NPPES registry on July 10, 2023.
Where is Kimberly Sparrow located?
Kimberly Sparrow practices at 8800 Elkview Ct, North Chesterfield, VA 23236. The listed phone number is (434) 222-5132.
What is Kimberly Sparrow's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Kimberly Sparrow enrolled in Medicare?
Yes. Kimberly Sparrow is registered in the Medicare PECOS enrollment system.
What insurance does Kimberly Sparrow accept?
Health plans from Providence Health Plan list Kimberly Sparrow 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 Kimberly Sparrow was last updated on July 10, 2023. 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.