ASHKON OLYAIE PA
NPI 1407397326
Physician Assistant in Union City, CA
About Ashkon Olyaie Pa NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ASHKON OLYAIE PA (NPI 1407397326) is an individual physician assistant in Union City, California, licensed in California (PA68162) and active in the NPI registry since March 2017. He is enrolled in Medicare PECOS and is a graduate of Other (2025).
NPPES Registry Identity
Specialties & Licenses 2
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Ashkon Olyaie Pa 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 94587 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Ashkon Olyaie's NPI number?
The NPI number for Ashkon Olyaie is 1407397326. It was assigned to this individual provider in the NPPES registry on March 10, 2017.
Where is Ashkon Olyaie located?
Ashkon Olyaie practices at 32530 Almaden Blvd Apt 120, Union City, CA 94587. The listed phone number is (510) 921-9605.
What is Ashkon Olyaie's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Ashkon Olyaie enrolled in Medicare?
Yes. Ashkon Olyaie is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ashkon Olyaie was last updated on May 11, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.