DR. JOHN P BEYER D.D.S., PH.D.
NPI 1255411203
Dentist - Orthodontics and Dentofacial Orthopedics in Minneapolis, MN
About Dr. John P Beyer D.d.s., Ph.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JOHN P BEYER D.D.S., PH.D. (NPI 1255411203) is an individual orthodontics and dentofacial orthopedics provider in Minneapolis, Minnesota, licensed in Minnesota (D10767) and active in the NPI registry since October 2006.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
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.
MINNEAPOLIS, MN 55455
MINNEAPOLIS, MN 55455
MINNEAPOLIS, MN 55455
MINNEAPOLIS, MN 55455
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 John Beyer's NPI number?
The NPI number for John Beyer is 1255411203. It was assigned to this individual provider in the NPPES registry on October 16, 2006.
Where is John Beyer located?
John Beyer practices at 515 Delaware St SE 6-320 Moos Tower, Minneapolis, MN 55455. The listed phone number is (612) 625-3903.
What is John Beyer's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Orthodontics and Dentofacial Orthopedics, with taxonomy code 1223X0400X.
What insurance does John Beyer 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 John Beyer 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 John Beyer 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.