ASMAA AHMED MD
NPI 1710618657
Student in an Organized Health Care Education/Training Program in Rochester, NY
About Asmaa Ahmed Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ASMAA AHMED MD (NPI 1710618657) is an individual student in an organized health care education/training program in Rochester, New York and active in the NPI registry since June 2022. 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)
Asmaa Ahmed Md 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.
ROCHESTER, NY 14621
ROCHESTER, NY 14621
ROCHESTER, NY 14621
ROCHESTER, NY 14621
ROCHESTER, NY 14621
ROCHESTER, NY 14621
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 Asmaa Ahmed's NPI number?
The NPI number for Asmaa Ahmed is 1710618657. It was assigned to this individual provider in the NPPES registry on June 21, 2022.
Where is Asmaa Ahmed located?
Asmaa Ahmed practices at 1425 Portland Ave Bldg 3, Rochester, NY 14621. The listed phone number is (585) 922-4000.
What is Asmaa Ahmed's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Asmaa Ahmed enrolled in Medicare?
Yes. Asmaa Ahmed is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Asmaa Ahmed was last updated on June 4, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 14 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.