MRS. LARISSA IVANOVNA RUN PA-C
NPI 1225337132
Physician Assistant in Las Vegas, NV
About Mrs. Larissa Ivanovna Run Pa-c NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MRS. LARISSA IVANOVNA RUN PA-C (NPI 1225337132) is an individual physician assistant in Las Vegas, Nevada, licensed in Nevada (PA1268) and active in the NPI registry since March 2011. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
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)
Mrs. Larissa Ivanovna Run Pa-c 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 89147 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 Larissa Run's NPI number?
The NPI number for Larissa Run is 1225337132. It was assigned to this individual provider in the NPPES registry on March 17, 2011. The provider is also known as Mrs. Larissa Ivanovna Run Pa-C.
Where is Larissa Run located?
Larissa Run practices at 9701 West Flamingo Rd #4, Las Vegas, NV 89147. The listed phone number is (702) 240-3929.
What is Larissa Run's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Larissa Run enrolled in Medicare?
Yes. Larissa Run is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Larissa Run was last updated on October 10, 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.