RILEY OSTERTAG PA-C
NPI 1801290614
Physician Assistant - Medical in Prior Lake, MN
About Riley Ostertag Pa-c NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
RILEY OSTERTAG PA-C (NPI 1801290614) is an individual medical provider in Prior Lake, Minnesota, licensed in Minnesota (11694) and active in the NPI registry since October 2014. She is enrolled in Medicare PECOS and is a graduate of Other (2014).
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)
Riley Ostertag Pa-c is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 15
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
PRIOR LAKE, MN 55372
PRIOR LAKE, MN 55372
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 Riley Ostertag's NPI number?
The NPI number for Riley Ostertag is 1801290614. It was assigned to this individual provider in the NPPES registry on October 22, 2014. The provider is also known as Riley Blythe Pa-C.
Where is Riley Ostertag located?
Riley Ostertag practices at 2330 Sioux Trl NW, Prior Lake, MN 55372. The listed phone number is (952) 496-6150.
What is Riley Ostertag's specialty?
The primary specialty registered for this NPI is Physician Assistant, specializing in Medical, with taxonomy code 363AM0700X.
Is Riley Ostertag enrolled in Medicare?
Yes. Riley Ostertag is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Riley Ostertag was last updated on July 22, 2015. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 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.