LEE ANN SANTORE MD
NPI 1821791955
Surgery in Rochester, MN
About Lee Ann Santore Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LEE ANN SANTORE MD (NPI 1821791955) is an individual surgery provider in Rochester, Minnesota, licensed in Minnesota (77511) and active in the NPI registry since March 2023. She 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)
Lee Ann Santore 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 55905 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 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
ROCHESTER, MN 55905
ROCHESTER, MN 55905
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 Lee Santore's NPI number?
The NPI number for Lee Santore is 1821791955. It was assigned to this individual provider in the NPPES registry on March 27, 2023.
Where is Lee Santore located?
Lee Santore practices at 200 1st St SW, Rochester, MN 55905. The listed phone number is (507) 284-2511.
What is Lee Santore's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Lee Santore enrolled in Medicare?
Yes. Lee Santore is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Lee Santore was last updated on August 16, 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.