KU IN KANG
NPI 1902267461
Physician Assistant in Hagatna, GU
About Ku In Kang NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KU IN KANG (NPI 1902267461) is an individual physician assistant in Hagatna, Guam, licensed in Guam (PA-110) and active in the NPI registry since March 2016. 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)
Ku In Kang 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 96932 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
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
HAGATNA, GU 96932
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 Ku In Kang's NPI number?
The NPI number for Ku In Kang is 1902267461. It was assigned to this individual provider in the NPPES registry on March 11, 2016.
Where is Ku In Kang located?
Ku In Kang practices at 302 South Route 4 207, Hagatna, GU 96932. The listed phone number is (671) 477-2873.
What is Ku In Kang's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Ku In Kang enrolled in Medicare?
Yes. Ku In Kang is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ku In Kang was last updated on March 11, 2016. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 10 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.