RUMI YOKOTA NP
NPI 1336482363
Nurse Practitioner in Palo Alto, CA
About Rumi Yokota Np NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
RUMI YOKOTA NP (NPI 1336482363) is an individual nurse practitioner in Palo Alto, California, licensed in California (22784) and active in the NPI registry since March 2013. 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)
Rumi Yokota Np 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 94304 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 Rumi Yokota's NPI number?
The NPI number for Rumi Yokota is 1336482363. It was assigned to this individual provider in the NPPES registry on March 28, 2013.
Where is Rumi Yokota located?
Rumi Yokota practices at 725 Welch Rd, Palo Alto, CA 94304. The listed phone number is (650) 497-8000.
What is Rumi Yokota's specialty?
The primary specialty registered for this NPI is Nurse Practitioner with taxonomy code 363L00000X.
Is Rumi Yokota enrolled in Medicare?
Yes. Rumi Yokota is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Rumi Yokota was last updated on March 30, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.