SAMANTHA NICOLE RUDMAN LCPC
NPI 1841855434
Counselor - Professional in Salisbury, MD
About Samantha Nicole Rudman Lcpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SAMANTHA NICOLE RUDMAN LCPC (NPI 1841855434) is an individual professional provider in Salisbury, Maryland, licensed in Maryland (LC15999) and active in the NPI registry since May 2019. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Other Names 1
Other Identifiers 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)
Samantha Nicole Rudman Lcpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
SALISBURY, MD 21804
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 Samantha Rudman's NPI number?
The NPI number for Samantha Rudman is 1841855434. It was assigned to this individual provider in the NPPES registry on May 8, 2019. The provider is also known as Samantha Kline Lgpc.
Where is Samantha Rudman located?
Samantha Rudman practices at 6508 Deer Pointe Dr Ste 4, Salisbury, MD 21804. The listed phone number is (410) 742-6016.
What is Samantha Rudman's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Samantha Rudman enrolled in Medicare?
Yes. Samantha Rudman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Samantha Rudman was last updated on January 28, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 months 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.