HUMZA MOGHIS MIAN MD
NPI 1043847288
Student in an Organized Health Care Education/Training Program in Dayton, OH
About Humza Moghis Mian Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
HUMZA MOGHIS MIAN MD (NPI 1043847288) is an individual student in an organized health care education/training program in Dayton, Ohio and active in the NPI registry since March 2020. 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)
Humza Moghis Mian 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.
DAYTON, OH 45409
DAYTON, OH 45409
DAYTON, OH 45409
DAYTON, OH 45409
DAYTON, OH 45409
DAYTON, OH 45409
DAYTON, OH 45409
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 Humza Mian's NPI number?
The NPI number for Humza Mian is 1043847288. It was assigned to this individual provider in the NPPES registry on March 26, 2020.
Where is Humza Mian located?
Humza Mian practices at 30 E Apple St Ste 2200, Dayton, OH 45409. The listed phone number is (937) 208-2127.
What is Humza Mian's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Humza Mian enrolled in Medicare?
Yes. Humza Mian is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Humza Mian was last updated on March 26, 2020. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.