DEVIN J SHAH
NPI 1336836253
Surgery in Richmond, VA
About Devin J Shah NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DEVIN J SHAH (NPI 1336836253) is an individual surgery provider in Richmond, Virginia, licensed in Virginia (0116037913) and active in the NPI registry since April 2023. 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)
Devin J Shah 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 23298 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
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
RICHMOND, VA 23298
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 Devin Shah's NPI number?
The NPI number for Devin Shah is 1336836253. It was assigned to this individual provider in the NPPES registry on April 20, 2023.
Where is Devin Shah located?
Devin Shah practices at Vcuhs Dept Of General Surgery Residency 1001 East Leigh Street, Richmond, VA 23298. The listed phone number is (804) 628-7497.
What is Devin Shah's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Devin Shah enrolled in Medicare?
Yes. Devin Shah is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Devin Shah was last updated on July 8, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.