DR. JOHN CHARLES HAGAN III MD
NPI 1922091297
Ophthalmology in Kansas City, MO
About Dr. John Charles Hagan Iii Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JOHN CHARLES HAGAN III MD (NPI 1922091297) is an individual ophthalmology provider in Kansas City, Missouri, licensed in Missouri (R6034) and active in the NPI registry since August 2005.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 2
Accepted Insurance
Medicare Quality Performance CMS QPP · MIPS
Performance in the CMS Quality Payment Program: the MIPS final score across four weighted categories, and the individual quality measures reported to Medicare.
Reported Quality Measures
Other Providers at the Same Location NPPES 8
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
KANSAS CITY, MO 64155
KANSAS CITY, MO 64155
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 Hagan's NPI number?
The NPI number for John Hagan is 1922091297. It was assigned to this individual provider in the NPPES registry on August 23, 2005.
Where is John Hagan located?
John Hagan practices at 9401 N Oak Trfy Ste 200, Kansas City, MO 64155. The listed phone number is (816) 478-1230.
What is John Hagan's specialty?
The primary specialty registered for this NPI is Ophthalmology with taxonomy code 207W00000X.
What insurance does John Hagan accept?
Health plans from Anthem Blue Cross and Blue Shield and Blue Cross and Blue Shield of Kansas City list John Hagan 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 Hagan was last updated on December 6, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 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.