REBECCA J HAFNER-FOGARTY M.D.
NPI 1497783963
Family Medicine in Avon, MN
About Rebecca J Hafner-fogarty M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
REBECCA J HAFNER-FOGARTY M.D. (NPI 1497783963) is an individual family medicine provider in Avon, Minnesota, licensed in Minnesota (25004) and active in the NPI registry since June 2006. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Rebecca J Hafner-fogarty M.d. 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 56310 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Rebecca Hafner-fogarty's NPI number?
The NPI number for Rebecca Hafner-fogarty is 1497783963. It was assigned to this individual provider in the NPPES registry on June 30, 2006.
Where is Rebecca Hafner-fogarty located?
Rebecca Hafner-fogarty practices at 33491 135th Ave, Avon, MN 56310. The listed phone number is (320) 356-1019.
What is Rebecca Hafner-fogarty's specialty?
The primary specialty registered for this NPI is Family Medicine with taxonomy code 207Q00000X.
Is Rebecca Hafner-fogarty enrolled in Medicare?
Yes. Rebecca Hafner-fogarty is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Rebecca Hafner-fogarty was last updated on July 8, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 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.