WENDY BETH SUMNER ALEXANDER PA-C
NPI 1285616938
Physician Assistant - Surgical in Nashville, TN
About Wendy Beth Sumner Alexander Pa-c NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
WENDY BETH SUMNER ALEXANDER PA-C (NPI 1285616938) is an individual surgical provider in Nashville, Tennessee, licensed in Tennessee (PA765) and active in the NPI registry since November 2005. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 4
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Wendy Beth Sumner Alexander Pa-c is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
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 Wendy Sumner Alexander's NPI number?
The NPI number for Wendy Sumner Alexander is 1285616938. It was assigned to this individual provider in the NPPES registry on November 17, 2005.
Where is Wendy Sumner Alexander located?
Wendy Sumner Alexander practices at 1310 24th Ave S, Nashville, TN 37212. The listed phone number is (615) 873-8357.
What is Wendy Sumner Alexander's specialty?
The primary specialty registered for this NPI is Physician Assistant, specializing in Surgical, with taxonomy code 363AS0400X.
Is Wendy Sumner Alexander enrolled in Medicare?
Yes. Wendy Sumner Alexander is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Wendy Sumner Alexander was last updated on September 8, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 days 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.