KAITE GO
NPI 1033676549
Nurse Practitioner - Family in Concord, CA
About Kaite Go NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KAITE GO (NPI 1033676549) is an individual family provider in Concord, California, licensed in California (95008372) and active in the NPI registry since February 2019. 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)
Kaite Go 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 94520 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 Kaite Go's NPI number?
The NPI number for Kaite Go is 1033676549. It was assigned to this individual provider in the NPPES registry on February 21, 2019.
Where is Kaite Go located?
Kaite Go practices at 2185 Pacheco St, Concord, CA 94520. The listed phone number is (925) 676-0300.
What is Kaite Go's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Kaite Go enrolled in Medicare?
Yes. Kaite Go is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Kaite Go was last updated on October 31, 2023. 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.