MR. JING FENG GOOI
NPI 1689246472
Counselor in Buffalo, NY
About Mr. Jing Feng Gooi NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MR. JING FENG GOOI (NPI 1689246472) is an individual counselor in Buffalo, New York and active in the NPI registry since July 2021. He is enrolled in Medicare PECOS and is a graduate of Other (2021).
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 and accepts Medicare assignment
Mr. Jing Feng Gooi is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Jing Feng Gooi's NPI number?
The NPI number for Jing Feng Gooi is 1689246472. It was assigned to this individual provider in the NPPES registry on July 12, 2021.
Where is Jing Feng Gooi located?
Jing Feng Gooi practices at 3350 Main St, Buffalo, NY 14214. The listed phone number is (716) 835-4011.
What is Jing Feng Gooi's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
Is Jing Feng Gooi enrolled in Medicare?
Yes. Jing Feng Gooi is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Jing Feng Gooi was last updated on July 12, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.