ERIN M RAHIM LPC
NPI 1861812281
Counselor - Professional in Leesburg, VA
About Erin M Rahim Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ERIN M RAHIM LPC (NPI 1861812281) is an individual professional provider in Leesburg, Virginia, licensed in Virginia (0701007638) and active in the NPI registry since April 2014. She is enrolled in Medicare PECOS, maintains a secondary practice location in Leesburg, and is a graduate of Other (2004).
NPPES Registry Identity
Specialties & Licenses 2
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 and accepts Medicare assignment
Erin M Rahim Lpc is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Erin Rahim's NPI number?
The NPI number for Erin Rahim is 1861812281. It was assigned to this individual provider in the NPPES registry on April 24, 2014.
Where is Erin Rahim located?
Erin Rahim practices at 211 Gibson St NW Ste 220, Leesburg, VA 20176. The listed phone number is (703) 799-5465.
What is Erin Rahim's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Erin Rahim enrolled in Medicare?
Yes. Erin Rahim is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Erin Rahim was last updated on October 11, 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.