BRIAN DANIEL KNOX M.D.
NPI 1477748358
Internal Medicine in Tampa, FL
About Brian Daniel Knox M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRIAN DANIEL KNOX M.D. (NPI 1477748358) is an individual internal medicine provider in Tampa, Florida, licensed in Florida (ME100143) and active in the NPI registry since September 2007. He maintains a secondary practice location in Plymouth.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
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 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
TAMPA, FL 33612
TAMPA, FL 33612
TAMPA, FL 33612
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 Knox's NPI number?
The NPI number for Brian Knox is 1477748358. It was assigned to this individual provider in the NPPES registry on September 13, 2007.
Where is Brian Knox located?
Brian Knox practices at 13330 Usf Laurel Dr, Tampa, FL 33612. The listed phone number is (813) 821-8038.
What is Brian Knox's specialty?
The primary specialty registered for this NPI is Internal Medicine with taxonomy code 207R00000X.
What insurance does Brian Knox accept?
Health plans from Molina Healthcare list Brian Knox 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 Knox was last updated on July 30, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.