DR. ANDREW DAMIAN LEBAMOFF DO
NPI 1720870777
Student in an Organized Health Care Education/Training Program in Dayton, OH
About Dr. Andrew Damian Lebamoff Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. ANDREW DAMIAN LEBAMOFF DO (NPI 1720870777) is an individual student in an organized health care education/training program in Dayton, Ohio and active in the NPI registry since May 2025. 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. Andrew Damian Lebamoff Do 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
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 Andrew Lebamoff's NPI number?
The NPI number for Andrew Lebamoff is 1720870777. It was assigned to this individual provider in the NPPES registry on May 17, 2025.
Where is Andrew Lebamoff located?
Andrew Lebamoff practices at 1 Wyoming St, Dayton, OH 45409. The listed phone number is (937) 208-3882.
What is Andrew Lebamoff's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Andrew Lebamoff enrolled in Medicare?
Yes. Andrew Lebamoff is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Andrew Lebamoff was last updated on May 17, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 17 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.