ARINZE JASON OCHUBA
NPI 1396405387
Student in an Organized Health Care Education/Training Program in Baltimore, MD
About Arinze Jason Ochuba NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ARINZE JASON OCHUBA (NPI 1396405387) is an individual student in an organized health care education/training program in Baltimore, Maryland and active in the NPI registry since December 2021. 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)
Arinze Jason Ochuba 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.
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
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 Arinze Ochuba's NPI number?
The NPI number for Arinze Ochuba is 1396405387. It was assigned to this individual provider in the NPPES registry on December 18, 2021.
Where is Arinze Ochuba located?
Arinze Ochuba practices at 600 N Wolfe St, Baltimore, MD 21287. The listed phone number is (410) 955-5000.
What is Arinze Ochuba's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Arinze Ochuba enrolled in Medicare?
Yes. Arinze Ochuba is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Arinze Ochuba was last updated on December 18, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.