ANDREW MANAHAN
NPI 1811699135
Student in an Organized Health Care Education/Training Program in New York, NY
About Andrew Manahan NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ANDREW MANAHAN (NPI 1811699135) is an individual student in an organized health care education/training program in New York, New York, licensed in Connecticut (84832) and active in the NPI registry since March 2023. 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)
Andrew Manahan is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
NEW YORK, NY 10032
NEW YORK, NY 10032
NEW YORK, NY 10032
NEW YORK, NY 10032
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 Andrew Manahan's NPI number?
The NPI number for Andrew Manahan is 1811699135. It was assigned to this individual provider in the NPPES registry on March 20, 2023.
Where is Andrew Manahan located?
Andrew Manahan practices at 622 W 168th St, New York, NY 10032. The listed phone number is (212) 305-6100.
What is Andrew Manahan's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Andrew Manahan enrolled in Medicare?
Yes. Andrew Manahan is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Andrew Manahan was last updated on June 3, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.