OLESYA VIESTENZ
NPI 1841509924
Optometrist in Tigard, OR
About Olesya Viestenz NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
OLESYA VIESTENZ (NPI 1841509924) is an individual optometrist in Tigard, Oregon, licensed in Oregon (3521ATI) and active in the NPI registry since October 2010. She 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)
Olesya Viestenz 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 97224 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 2
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 Olesya Viestenz's NPI number?
The NPI number for Olesya Viestenz is 1841509924. It was assigned to this individual provider in the NPPES registry on October 6, 2010.
Where is Olesya Viestenz located?
Olesya Viestenz practices at 7485 SW Bridgeport Rd, Tigard, OR 97224. The listed phone number is (503) 495-5821.
What is Olesya Viestenz's specialty?
The primary specialty registered for this NPI is Optometrist with taxonomy code 152W00000X.
Is Olesya Viestenz enrolled in Medicare?
Yes. Olesya Viestenz is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Olesya Viestenz was last updated on May 13, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.