THOMAS OLTMAN ROSER
NPI 1831884329
Student in an Organized Health Care Education/Training Program in Minneapolis, MN
About Thomas Oltman Roser NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
THOMAS OLTMAN ROSER (NPI 1831884329) is an individual student in an organized health care education/training program in Minneapolis, Minnesota and active in the NPI registry since April 2023. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Names 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)
Thomas Oltman Roser 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.
MINNEAPOLIS, MN 55415
MINNEAPOLIS, MN 55415
MINNEAPOLIS, MN 55415
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 Thomas Roser's NPI number?
The NPI number for Thomas Roser is 1831884329. It was assigned to this individual provider in the NPPES registry on April 10, 2023. The provider is also known as Tom Roser.
Where is Thomas Roser located?
Thomas Roser practices at 701 Park Ave, Minneapolis, MN 55415. The listed phone number is (612) 873-3000.
What is Thomas Roser's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Thomas Roser enrolled in Medicare?
Yes. Thomas Roser is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Thomas Roser was last updated on April 10, 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.