JOSHUA ARAM OLSON
NPI 1679315212
Emergency Medicine in Omaha, NE
About Joshua Aram Olson NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JOSHUA ARAM OLSON (NPI 1679315212) is an individual emergency medicine provider in Omaha, Nebraska, licensed in Nebraska (9937) and active in the NPI registry since June 2024. 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)
Joshua Aram Olson is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 68198 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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.
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 Joshua Olson's NPI number?
The NPI number for Joshua Olson is 1679315212. It was assigned to this individual provider in the NPPES registry on June 12, 2024.
Where is Joshua Olson located?
Joshua Olson practices at 981150 Nebraska Medical Ctr, Omaha, NE 68198. The listed phone number is (402) 559-6637.
What is Joshua Olson's specialty?
The primary specialty registered for this NPI is Emergency Medicine with taxonomy code 207P00000X.
Is Joshua Olson enrolled in Medicare?
Yes. Joshua Olson is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Joshua Olson was last updated on June 12, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.