ROHITH REDDY ALURU MD
NPI 1578407516
Student in an Organized Health Care Education/Training Program in Detroit, MI
About Rohith Reddy Aluru Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ROHITH REDDY ALURU MD (NPI 1578407516) is an individual student in an organized health care education/training program in Detroit, Michigan and active in the NPI registry since April 2026. 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)
Rohith Reddy Aluru 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.
DETROIT, MI 48236
DETROIT, MI 48236
DETROIT, MI 48236
DETROIT, MI 48236
DETROIT, MI 48236
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 Rohith Aluru's NPI number?
The NPI number for Rohith Aluru is 1578407516. It was assigned to this individual provider in the NPPES registry on April 20, 2026.
Where is Rohith Aluru located?
Rohith Aluru practices at 22201 Moross Rd Ste 50, Detroit, MI 48236. The listed phone number is (313) 343-7774.
What is Rohith Aluru's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Rohith Aluru enrolled in Medicare?
Yes. Rohith Aluru is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Rohith Aluru was last updated on April 20, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.