BASEM FANOUS DPM
NPI 1336173871
Podiatrist in Cando, ND
About Basem Fanous Dpm NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BASEM FANOUS DPM (NPI 1336173871) is an individual podiatrist in Cando, North Dakota, licensed in North Dakota (32) and active in the NPI registry since July 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 6
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Basem Fanous Dpm 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 58324 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 4
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 Basem Fanous's NPI number?
The NPI number for Basem Fanous is 1336173871. It was assigned to this individual provider in the NPPES registry on July 10, 2006.
Where is Basem Fanous located?
Basem Fanous practices at Hwy 281N, Cando, ND 58324. The listed phone number is (701) 968-2541.
What is Basem Fanous's specialty?
The primary specialty registered for this NPI is Podiatrist with taxonomy code 213E00000X.
Is Basem Fanous enrolled in Medicare?
Yes. Basem Fanous is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Basem Fanous was last updated on July 9, 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.