YI-MING JONATHAN LIAU
NPI 1316640469
Student in an Organized Health Care Education/Training Program in Kansas City, MO
About Yi-ming Jonathan Liau NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
YI-MING JONATHAN LIAU (NPI 1316640469) is an individual student in an organized health care education/training program in Kansas City, Missouri and active in the NPI registry since March 2023. 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)
Yi-ming Jonathan Liau is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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.
KANSAS CITY, MO 64108
KANSAS CITY, MO 64108
KANSAS CITY, MO 64108
KANSAS CITY, MO 64108
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 Yi-ming Liau's NPI number?
The NPI number for Yi-ming Liau is 1316640469. It was assigned to this individual provider in the NPPES registry on March 27, 2023.
Where is Yi-ming Liau located?
Yi-ming Liau practices at 2301 Holmes St, Kansas City, MO 64108. The listed phone number is (818) 406-4878.
What is Yi-ming Liau's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Yi-ming Liau enrolled in Medicare?
Yes. Yi-ming Liau is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Yi-ming Liau was last updated on March 27, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.