DR. EMMA ZARGARIAN M.D.
NPI 1639182041
Specialist in Baltimore, MD
About Dr. Emma Zargarian M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. EMMA ZARGARIAN M.D. (NPI 1639182041) is an individual specialist in Baltimore, Maryland, licensed in Maryland (D22704) and active in the NPI registry since August 2006. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Other Identifiers 2
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. Emma Zargarian M.d. 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.
TOWSON, MD 21204
TOWSON, MD 21204
TOWSON, MD 21204
BALTIMORE, MD 21204
BALTIMORE, MD 21204
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 Emma Zargarian's NPI number?
The NPI number for Emma Zargarian is 1639182041. It was assigned to this individual provider in the NPPES registry on August 15, 2006. The provider is also known as Dr. Emma Zargarian M.D..
Where is Emma Zargarian located?
Emma Zargarian practices at 6565 N Charles St Suite 501, Baltimore, MD 21204. The listed phone number is (410) 828-8369.
What is Emma Zargarian's specialty?
The primary specialty registered for this NPI is Specialist with taxonomy code 174400000X.
Is Emma Zargarian enrolled in Medicare?
Yes. Emma Zargarian is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Emma Zargarian was last updated on July 8, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 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.