MS. SHARON A. LOPUZZO N.P.
NPI 1760507941
Nurse Practitioner - Adult Health in New York, NY
About Ms. Sharon A. Lopuzzo N.p. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MS. SHARON A. LOPUZZO N.P. (NPI 1760507941) is an individual adult health provider in New York, New York, licensed in New York (F302122) and active in the NPI registry since March 2007. 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)
Ms. Sharon A. Lopuzzo N.p. 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 10032 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 Sharon Lopuzzo's NPI number?
The NPI number for Sharon Lopuzzo is 1760507941. It was assigned to this individual provider in the NPPES registry on March 20, 2007.
Where is Sharon Lopuzzo located?
Sharon Lopuzzo practices at 622 W.168th St. Ny-Presbyterian Hospital (ph 137), New York, NY 10032. The listed phone number is (212) 305-4612.
What is Sharon Lopuzzo's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Adult Health, with taxonomy code 363LA2200X.
Is Sharon Lopuzzo enrolled in Medicare?
Yes. Sharon Lopuzzo is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Sharon Lopuzzo 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.