DR. GURKARAN SINGH MD
NPI 1851086730
Internal Medicine in Avondale, AZ
About Dr. Gurkaran Singh Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. GURKARAN SINGH MD (NPI 1851086730) is an individual internal medicine provider in Avondale, Arizona, licensed in California (201784) and active in the NPI registry since April 2023. He is enrolled in Medicare PECOS and maintains a secondary practice location in Santa Clara.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 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)
Dr. Gurkaran Singh 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 85392 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 Gurkaran Singh's NPI number?
The NPI number for Gurkaran Singh is 1851086730. It was assigned to this individual provider in the NPPES registry on April 7, 2023.
Where is Gurkaran Singh located?
Gurkaran Singh practices at 12801 W Windsor Ave, Avondale, AZ 85392. The listed phone number is (480) 259-7508.
What is Gurkaran Singh's specialty?
The primary specialty registered for this NPI is Internal Medicine with taxonomy code 207R00000X.
Is Gurkaran Singh enrolled in Medicare?
Yes. Gurkaran Singh is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Gurkaran Singh was last updated on August 16, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.