MR. CHRISTOPHER GALGANO PAC
NPI 1013027895
Physician Assistant in Fayetteville, NC
About Mr. Christopher Galgano Pac NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MR. CHRISTOPHER GALGANO PAC (NPI 1013027895) is an individual physician assistant in Fayetteville, North Carolina, licensed in North Carolina (0010-03377) and active in the NPI registry since August 2006. 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)
Mr. Christopher Galgano Pac 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 28301 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 Christopher Galgano's NPI number?
The NPI number for Christopher Galgano is 1013027895. It was assigned to this individual provider in the NPPES registry on August 30, 2006.
Where is Christopher Galgano located?
Christopher Galgano practices at 2300 Ramsey St Ste 184, Fayetteville, NC 28301. The listed phone number is (910) 488-2120.
What is Christopher Galgano's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Christopher Galgano enrolled in Medicare?
Yes. Christopher Galgano is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Christopher Galgano was last updated on June 14, 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.