DR. BRIAN LEONARD DIZON MD/PHD
NPI 1194068338
Student in an Organized Health Care Education/Training Program in Bethesda, MD
About Dr. Brian Leonard Dizon Md/phd NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. BRIAN LEONARD DIZON MD/PHD (NPI 1194068338) is an individual student in an organized health care education/training program in Bethesda, Maryland and active in the NPI registry since April 2013. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dr. Brian Leonard Dizon Md/phd is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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.
BETHESDA, MD 20892
BETHESDA, MD 20892
BETHESDA, MD 20892
BETHESDA, MD 20892
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 Dizon's NPI number?
The NPI number for Brian Dizon is 1194068338. It was assigned to this individual provider in the NPPES registry on April 5, 2013.
Where is Brian Dizon located?
Brian Dizon practices at 9000 Rockville Pike, Bethesda, MD 20892. The listed phone number is (301) 594-0529.
What is Brian Dizon's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Brian Dizon enrolled in Medicare?
Yes. Brian Dizon is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Brian Dizon was last updated on July 21, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.