DR. HENRY MEILMAN M.D.
NPI 1346243615
Internal Medicine - Cardiovascular Disease in Owings Mills, MD
About Dr. Henry Meilman M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. HENRY MEILMAN M.D. (NPI 1346243615) is an individual cardiovascular disease provider in Owings Mills, Maryland, licensed in Maryland (D0032106) and active in the NPI registry since May 2005. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
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)
Dr. Henry Meilman M.d. is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 21117 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Henry Meilman's NPI number?
The NPI number for Henry Meilman is 1346243615. It was assigned to this individual provider in the NPPES registry on May 31, 2005.
Where is Henry Meilman located?
Henry Meilman practices at 4 Chetwick Ct, Owings Mills, MD 21117. The listed phone number is (410) 363-1198.
What is Henry Meilman's specialty?
The primary specialty registered for this NPI is Internal Medicine, specializing in Cardiovascular Disease, with taxonomy code 207RC0000X.
Is Henry Meilman enrolled in Medicare?
Yes. Henry Meilman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Henry Meilman was last updated on July 22, 2011. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 15 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.