ROSHAN SAI TADI MD
NPI 1508486879
Surgery in Tucson, AZ
About Roshan Sai Tadi Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ROSHAN SAI TADI MD (NPI 1508486879) is an individual surgery provider in Tucson, Arizona, licensed in Arizona (80407) and active in the NPI registry since April 2020. 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)
Roshan Sai Tadi 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 85712 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 3
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 Roshan Tadi's NPI number?
The NPI number for Roshan Tadi is 1508486879. It was assigned to this individual provider in the NPPES registry on April 16, 2020.
Where is Roshan Tadi located?
Roshan Tadi practices at 5240 E Knight Dr Ste 116, Tucson, AZ 85712. The listed phone number is (520) 320-5665.
What is Roshan Tadi's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Roshan Tadi enrolled in Medicare?
Yes. Roshan Tadi is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Roshan Tadi was last updated on September 14, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 22 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.