DR. JACOB SIDNEY ALEXANDER
NPI 1316556368
Student in an Organized Health Care Education/Training Program in Toledo, OH
About Dr. Jacob Sidney Alexander NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JACOB SIDNEY ALEXANDER (NPI 1316556368) is an individual student in an organized health care education/training program in Toledo, Ohio and active in the NPI registry since July 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)
Dr. Jacob Sidney Alexander 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.
TOLEDO, OH 43614
TOLEDO, OH 43614
TOLEDO, OH 43614
TOLEDO, OH 43614
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 Jacob Alexander's NPI number?
The NPI number for Jacob Alexander is 1316556368. It was assigned to this individual provider in the NPPES registry on July 27, 2020.
Where is Jacob Alexander located?
Jacob Alexander practices at 3000 Arlington Ave, Toledo, OH 43614. The listed phone number is (419) 383-4000.
What is Jacob Alexander's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Jacob Alexander enrolled in Medicare?
Yes. Jacob Alexander is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jacob Alexander was last updated on March 27, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.