DR. BEANCA CHU DDS
NPI 1427135847
Dentist - Pediatric Dentistry in Huntington Beach, CA
About Dr. Beanca Chu Dds NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. BEANCA CHU DDS (NPI 1427135847) is an individual pediatric dentistry provider in Huntington Beach, California, licensed in California (46254) and active in the NPI registry since November 2006.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Accepted Insurance
Other Providers at the Same Location NPPES 13
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
HUNTINGTON BEACH, CA 92646
HUNTINGTON BEACH, CA 92646
HUNTINGTON BEACH, CA 92646
HUNTINGTON BEACH, CA 92646
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 Beanca Chu's NPI number?
The NPI number for Beanca Chu is 1427135847. It was assigned to this individual provider in the NPPES registry on November 1, 2006. The provider is also known as Dr. Beanca Chu Dds.
Where is Beanca Chu located?
Beanca Chu practices at 20932 Brookhurst St Suite 102, Huntington Beach, CA 92646. The listed phone number is (714) 962-9302.
What is Beanca Chu's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Pediatric Dentistry, with taxonomy code 1223P0221X.
What insurance does Beanca Chu accept?
Health plans from Anthem Blue Cross and Blue Shield, Blue Cross and Blue Shield of Montana, Blue Cross and Blue Shield of Oklahoma and Blue Cross and Blue Shield of Texas list Beanca Chu as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Beanca Chu was last updated on February 8, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.