ALEXANDER TYLER PROUTY DO
NPI 1013610195
Student in an Organized Health Care Education/Training Program in Englewood, OH
About Alexander Tyler Prouty Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ALEXANDER TYLER PROUTY DO (NPI 1013610195) is an individual student in an organized health care education/training program in Englewood, Ohio and active in the NPI registry since March 2023. He is enrolled in Medicare PECOS and maintains a secondary practice location in Dayton.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Alexander Tyler Prouty Do is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Alexander Prouty's NPI number?
The NPI number for Alexander Prouty is 1013610195. It was assigned to this individual provider in the NPPES registry on March 27, 2023.
Where is Alexander Prouty located?
Alexander Prouty practices at 9000 N Main St Ste G-35, Englewood, OH 45415. The listed phone number is (937) 734-6784.
What is Alexander Prouty's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Alexander Prouty enrolled in Medicare?
Yes. Alexander Prouty is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Alexander Prouty was last updated on June 16, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 57 days 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.