DR. JOHN PATRICK BOWMAN DMD
NPI 1649591272
Dentist - Pediatric Dentistry in Westminster, CO
About Dr. John Patrick Bowman Dmd NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JOHN PATRICK BOWMAN DMD (NPI 1649591272) is an individual pediatric dentistry provider in Westminster, Colorado, licensed in Colorado (DEN.00203324) and active in the NPI registry since June 2010. He maintains a secondary practice location in Toledo.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Accepted Insurance
Other Providers at the Same Location NPPES 4
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
WESTMINSTER, CO 80023
WESTMINSTER, CO 80023
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 Bowman's NPI number?
The NPI number for John Bowman is 1649591272. It was assigned to this individual provider in the NPPES registry on June 17, 2010.
Where is John Bowman located?
John Bowman practices at 14422 Orchard Pkwy Ste 200, Westminster, CO 80023. The listed phone number is (303) 254-5437.
What is John Bowman's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Pediatric Dentistry, with taxonomy code 1223P0221X.
What insurance does John Bowman accept?
Health plans from Anthem Blue Cross and Blue Shield, BEST Life, Blue Cross and Blue Shield of Montana, Blue Cross and Blue Shield of Oklahoma and Blue Cross and Blue Shield of Texas and 5 other insurers list John Bowman 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 Bowman was last updated on November 8, 2018. 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.