SHAWN JAMES SENTER MD
NPI 1801470331
Surgery in Lubbock, TX
About Shawn James Senter Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SHAWN JAMES SENTER MD (NPI 1801470331) is an individual surgery provider in Lubbock, Texas, licensed in Texas (W2355) and active in the NPI registry since May 2021. He is enrolled in Medicare PECOS.
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)
Shawn James Senter Md 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 79410 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Other Providers at the Same Location NPPES 15
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 Shawn Senter's NPI number?
The NPI number for Shawn Senter is 1801470331. It was assigned to this individual provider in the NPPES registry on May 11, 2021.
Where is Shawn Senter located?
Shawn Senter practices at 3509 22nd St, Lubbock, TX 79410. The listed phone number is (806) 799-7928.
What is Shawn Senter's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Shawn Senter enrolled in Medicare?
Yes. Shawn Senter is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Shawn Senter was last updated on August 26, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.