BRIAN CHRISTOPHER PATERSON DMD, MD
NPI 1427383983
Dentist - Oral and Maxillofacial Surgery in Matawan, NJ
About Brian Christopher Paterson Dmd, Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRIAN CHRISTOPHER PATERSON DMD, MD (NPI 1427383983) is an individual oral and maxillofacial surgery provider in Matawan, New Jersey, licensed in New Jersey (22DI02597600) and active in the NPI registry since October 2009.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
Other Providers at the Same Location NPPES 12
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
MATAWAN, NJ 07747
MATAWAN, NJ 07747
MATAWAN, NJ 07747
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 Brian Paterson's NPI number?
The NPI number for Brian Paterson is 1427383983. It was assigned to this individual provider in the NPPES registry on October 16, 2009.
Where is Brian Paterson located?
Brian Paterson practices at 158 Main St Suite 103, Matawan, NJ 07747. The listed phone number is (732) 566-7648.
What is Brian Paterson's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Oral and Maxillofacial Surgery, with taxonomy code 1223S0112X.
What insurance does Brian Paterson accept?
Health plans from BEST Life, Blue Cross and Blue Shield of Alabama, Blue Cross and Blue Shield of Montana, Blue Cross and Blue Shield of Oklahoma and Blue Cross and Blue Shield of Texas and 6 other insurers list Brian Paterson 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 Brian Paterson was last updated on June 22, 2015. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 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.