TRACEY LYNETTE WILSON
NPI 1952062317
Counselor in Fairfax, VA
About Tracey Lynette Wilson NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
TRACEY LYNETTE WILSON (NPI 1952062317) is an individual counselor in Fairfax, Virginia and active in the NPI registry since January 2022. 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)
Tracey Lynette Wilson is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 2
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Tracey Wilson's NPI number?
The NPI number for Tracey Wilson is 1952062317. It was assigned to this individual provider in the NPPES registry on January 6, 2022.
Where is Tracey Wilson located?
Tracey Wilson practices at 3613 Chain Bridge Rd Ste D, Fairfax, VA 22030. The listed phone number is (703) 397-8163.
What is Tracey Wilson's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
Is Tracey Wilson enrolled in Medicare?
Yes. Tracey Wilson is registered in the Medicare PECOS enrollment system.
What insurance does Tracey Wilson accept?
Health plans from Providence Health Plan list Tracey Wilson 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 Tracey Wilson was last updated on January 6, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.