SAMUEL BORGEMENKE DO
NPI 1609716810
Student in an Organized Health Care Education/Training Program in Dayton, OH
About Samuel Borgemenke Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SAMUEL BORGEMENKE DO (NPI 1609716810) is an individual student in an organized health care education/training program in Dayton, Ohio and active in the NPI registry since March 2026. 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)
Samuel Borgemenke 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 45405
DAYTON, OH 45405
DAYTON, OH 45405
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 Samuel Borgemenke's NPI number?
The NPI number for Samuel Borgemenke is 1609716810. It was assigned to this individual provider in the NPPES registry on March 30, 2026.
Where is Samuel Borgemenke located?
Samuel Borgemenke practices at 405 W Grand Ave, Dayton, OH 45405. The listed phone number is (937) 723-3248.
What is Samuel Borgemenke's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Samuel Borgemenke enrolled in Medicare?
Yes. Samuel Borgemenke is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Samuel Borgemenke was last updated on March 30, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.