MR. BADRUZ RAIHAN ZAMAN PA
NPI 1811938988
Physician Assistant - Medical in Silversping, MD
About Mr. Badruz Raihan Zaman Pa NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MR. BADRUZ RAIHAN ZAMAN PA (NPI 1811938988) is an individual medical provider in Silversping, Maryland, licensed in Maryland (C0002568) and active in the NPI registry since June 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 3
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Mr. Badruz Raihan Zaman Pa is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Areas of Expertise CMS Part B claims
Services this provider delivered to Medicare fee-for-service patients, from the CMS Medicare utilization data. Higher counts generally reflect more experience with a service; care delivered outside Medicare is not included.
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 Badruz Zaman's NPI number?
The NPI number for Badruz Zaman is 1811938988. It was assigned to this individual provider in the NPPES registry on June 9, 2006.
Where is Badruz Zaman located?
Badruz Zaman practices at 1500 Forresst Glen Road, Silversping, MD 20147. The listed phone number is (301) 754-7500.
What is Badruz Zaman's specialty?
The primary specialty registered for this NPI is Physician Assistant, specializing in Medical, with taxonomy code 363AM0700X.
Is Badruz Zaman enrolled in Medicare?
Yes. Badruz Zaman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Badruz Zaman was last updated on February 27, 2008. 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.