PHAT T HO PA
NPI 1487504742
Physician Assistant in San Jose, CA
About Phat T Ho Pa NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
PHAT T HO PA (NPI 1487504742) is an individual physician assistant in San Jose, California and active in the NPI registry since January 2026. He 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)
Phat T Ho Pa 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 95116 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 3
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
SAN JOSE, CA 95116
SAN JOSE, CA 95116
SAN JOSE, CA 95116
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 Phat Ho's NPI number?
The NPI number for Phat Ho is 1487504742. It was assigned to this individual provider in the NPPES registry on January 28, 2026.
Where is Phat Ho located?
Phat Ho practices at 1855 Alum Rock Ave, San Jose, CA 95116. The listed phone number is (408) 254-7524.
What is Phat Ho's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Phat Ho enrolled in Medicare?
Yes. Phat Ho is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Phat Ho was last updated on May 12, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.