MS. TENESHA VANIA SENIOR LMSW
NPI 1508505520
Social Worker - Clinical in Mount Vernon, NY
About Ms. Tenesha Vania Senior Lmsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MS. TENESHA VANIA SENIOR LMSW (NPI 1508505520) is an individual clinical provider in Mount Vernon, New York, licensed in New York (113248) and active in the NPI registry since May 2022. She is enrolled in Medicare PECOS and is a graduate of Other (2021).
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Ms. Tenesha Vania Senior Lmsw is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 10550 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Tenesha Senior's NPI number?
The NPI number for Tenesha Senior is 1508505520. It was assigned to this individual provider in the NPPES registry on May 27, 2022.
Where is Tenesha Senior located?
Tenesha Senior practices at 11 Park Ave Apt 4F, Mount Vernon, NY 10550. The listed phone number is (914) 356-6593.
What is Tenesha Senior's specialty?
The primary specialty registered for this NPI is Social Worker, specializing in Clinical, with taxonomy code 1041C0700X.
Is Tenesha Senior enrolled in Medicare?
Yes. Tenesha Senior is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Tenesha Senior was last updated on May 27, 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.