DR. OLGA VISHNEVA D.O.
NPI 1619409950
Anesthesiology in Neptune City, NJ
About Dr. Olga Vishneva D.o. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. OLGA VISHNEVA D.O. (NPI 1619409950) is an individual anesthesiology provider in Neptune City, New Jersey, licensed in New Jersey (25MB11269100) and active in the NPI registry since March 2017. She is enrolled in Medicare PECOS and maintains a secondary practice location in Brooklyn.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 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)
Dr. Olga Vishneva D.o. 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.
NEPTUNE TOWNSHIP, NJ 07753
NEPTUNE, NJ 07753
NEPTUNE, NJ 07753
NEPTUNE, NJ 07753
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 Olga Vishneva's NPI number?
The NPI number for Olga Vishneva is 1619409950. It was assigned to this individual provider in the NPPES registry on March 28, 2017.
Where is Olga Vishneva located?
Olga Vishneva practices at 1945 Route 33, Neptune City, NJ 07753. The listed phone number is (732) 775-5500.
What is Olga Vishneva's specialty?
The primary specialty registered for this NPI is Anesthesiology with taxonomy code 207L00000X.
Is Olga Vishneva enrolled in Medicare?
Yes. Olga Vishneva is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Olga Vishneva was last updated on April 15, 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.