DR. MOHAMMED ALJAMA MBBS
NPI 1497274005
Student in an Organized Health Care Education/Training Program in Rochester, MN
About Dr. Mohammed Aljama Mbbs NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. MOHAMMED ALJAMA MBBS (NPI 1497274005) is an individual student in an organized health care education/training program in Rochester, Minnesota and active in the NPI registry since September 2017. 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)
Dr. Mohammed Aljama Mbbs 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, MN 55905
ROCHESTER, MN 55905
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 Mohammed Aljama's NPI number?
The NPI number for Mohammed Aljama is 1497274005. It was assigned to this individual provider in the NPPES registry on September 14, 2017.
Where is Mohammed Aljama located?
Mohammed Aljama practices at 200 1st St SW, Rochester, MN 55905. The listed phone number is (507) 284-2511.
What is Mohammed Aljama's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Mohammed Aljama enrolled in Medicare?
Yes. Mohammed Aljama is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Mohammed Aljama was last updated on September 14, 2017. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 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.