DR. TIMOTHY GEORGE BRICCA D.D.S.
NPI 1376768010
Dentist - General Practice in Larkspur, CA
About Dr. Timothy George Bricca D.d.s. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. TIMOTHY GEORGE BRICCA D.D.S. (NPI 1376768010) is an individual general practice provider in Larkspur, California, licensed in California (30763) and active in the NPI registry since April 2007. 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)
Dr. Timothy George Bricca D.d.s. 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 94939 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Timothy Bricca's NPI number?
The NPI number for Timothy Bricca is 1376768010. It was assigned to this individual provider in the NPPES registry on April 16, 2007.
Where is Timothy Bricca located?
Timothy Bricca practices at 1201 Larkspur Landing Circle Ste A, Larkspur, CA 94939. The listed phone number is (415) 461-6060.
What is Timothy Bricca's specialty?
The primary specialty registered for this NPI is Dentist, specializing in General Practice, with taxonomy code 1223G0001X.
Is Timothy Bricca enrolled in Medicare?
Yes. Timothy Bricca is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Timothy Bricca was last updated on July 8, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 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.