MR. LEWIS H LOQUASTO FNP-BC, FMHPNP-BC
NPI 1639384910
Nurse Practitioner - Family in Rochester, NY
About Mr. Lewis H Loquasto Fnp-bc, Fmhpnp-bc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MR. LEWIS H LOQUASTO FNP-BC, FMHPNP-BC (NPI 1639384910) is an individual family provider in Rochester, New York, licensed in New York (341323) and active in the NPI registry since May 2007. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 3
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. Lewis H Loquasto Fnp-bc, Fmhpnp-bc 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 14613 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 Lewis Loquasto's NPI number?
The NPI number for Lewis Loquasto is 1639384910. It was assigned to this individual provider in the NPPES registry on May 11, 2007.
Where is Lewis Loquasto located?
Lewis Loquasto practices at 595 Seneca Pkwy, Rochester, NY 14613. The listed phone number is (585) 719-0779.
What is Lewis Loquasto's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Lewis Loquasto enrolled in Medicare?
Yes. Lewis Loquasto is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Lewis Loquasto was last updated on January 15, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 months 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.