Dr. Carmel M. Halley, MD

  • Cleveland, OH
  • Cardiologist
NPI1861668444
Publications
13
State license
1
Year NPI issued
2008
Practice address
F15 Dept Of Cardiovascular Medicine, Cleveland, OH 44195-0001
Practice phone
Call (216) 268-9122
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Halley's professional email, personal email and mobile number

Dmand AI checks each channel through healthcare-specific waterfall enrichment. See what is on file with a free account, with practice phones, licenses and affiliations.

View contacts for free

Dr. Carmel M. Halley is a cardiologist in Cleveland, Ohio

Dr. Halley practices in Cleveland, Ohio.

Dr. Halley's NPI, 1861668444, was assigned on May 5, 2008. Dr. Halley holds Ohio license 57.012032.

NPI and contact details
NPI enumeration date
May 5, 2008
NPI status
Active
Practice phone
(216) 268-9122
Professional email
Get email
Personal email
Get email
Mobile number
Get number

Sources: NPPES NPI Registry (CMS); and Dmand AI Professional Profile Data

Dr. Carmel M. Halley's practice address is in Cleveland, Ohio

Dr. Halley's practice address in the NPI Registry is F15 Dept Of Cardiovascular Medicine, Cleveland, OH 44195-0001. The practice phone is (216) 268-9122.

  • NPI Registry address
    F15 Dept Of Cardiovascular Medicine, Cleveland, OH 44195-0001Phone(216) 268-9122

Sources: NPPES NPI Registry (CMS); and Dmand AI Practice Data

Dmand AI tracks the EHR system at Dr. Carmel M. Halley's practice

Dmand AI tracks the electronic health record (EHR) system at each site where Dr. Halley practices. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
Dr. Halley's practiceAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Dr. Halley practices

Dmand AI maps EHR vendors, IT decision makers and buying committees across each health system and 6.2K+ hospitals, with verified contacts in the same login.

Dr. Carmel M. Halley is one of 945 cardiologists in Ohio

Cardiovascular disease is Dr. Halley's primary specialty in the NPI Registry, under taxonomy code 207RC0000X. Dr. Halley is licensed in Ohio.

Specialties and state licenses

  • Cardiovascular disease, OhioPrimaryLicense 57.012032 · taxonomy 207RC0000X

Cardiologists near Dr. Halley

Counts of cardiologists with a Dmand AI profile, by place and practice. Each opens the list.

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; and Dmand AI Peer Benchmarks

Dr. Carmel M. Halley has 13 publications on record

Dmand AI links 13 papers to Dr. Halley, published from 2011 to 2022. 2013 was the busiest year, with 3. The most frequent topics are Stroke Volume, Diastole and Heart Failure. Dr. Halley has published most often in ESC Heart Fail. Dr. Halley's most frequent co-authors are Wael A. Jaber, MD, Wael Adnan Aljaroudi, MD and Richard A. Grimm, DO.

Papers13
Years published2011 to 2022

Dr. Halley's papers by year, 2011 to 2022

Topics Dr. Halley writes about most

  • Stroke Volume
  • Diastole
  • Heart Failure
  • Ventricular Dysfunction, Left
  • Cardiomyopathy, Dilated
  • Echocardiography
  • Leukocytes, Mononuclear
  • Ultrasonography

Dr. Halley's most frequent co-authors

Recent publications by Dr. Halley

See all 13 publications and co-authors

See who Dr. Halley researches with

Physician Network Discovery turns co-authorship, shared hospitals and shared groups into a map of who Dr. Halley works with, so you can find a warm path to the right cardiologists.

How network discovery works

Sources: PubMed (National Library of Medicine); and Dmand AI Research Linkage

Sources for Dr. Carmel M. Halley's profile data

Sources for the data on this page
Data on this pageSource
NPI, name, sex, specialty and licensesNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Professional Profile Data
Practice locations and phoneNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Practice Data
Publications, topics and co-authorsPubMed (National Library of Medicine) (opens in a new tab)Dmand AI Research Linkage
EHR at each practice siteDmand AI Technology Install Data
Similar physiciansDmand AI Affiliation Data

Data last refreshed October 2026Report an inaccuracyRemove my information

FAQ

Frequently asked questions about Dr. Carmel M. Halley

Spotted something out of date? Email hello@dmand.ai and we will check the record. Contact details live in the free trial.

What is Dr. Carmel M. Halley's NPI number?

Dr. Carmel M. Halley's NPI number is 1861668444. It was assigned on May 5, 2008, and it is active in the NPI Registry.

What kind of doctor is Dr. Carmel M. Halley?

Dr. Carmel M. Halley is a cardiologist in Cleveland, Ohio. The primary specialty in the NPI Registry is Cardiovascular Disease Physician (taxonomy code 207RC0000X).

Where does Dr. Carmel M. Halley practice?

Dr. Halley practices at F15 Dept Of Cardiovascular Medicine, Cleveland, OH 44195-0001.

What is Dr. Carmel M. Halley's office phone number?

The practice phone on file for Dr. Halley is (216) 268-9122.

What is Dr. Carmel M. Halley's medical license number?

Dr. Halley holds Ohio license 57.012032.

How long has Dr. Carmel M. Halley been practicing?

Dr. Halley's NPI was assigned in 2008.

Does Dr. Carmel M. Halley do research?

Dmand AI links 13 publications to Dr. Halley, published from 2011 to 2022.

Who does Dr. Carmel M. Halley publish with?

Dr. Halley's most frequent co-authors are Wael A. Jaber, MD (5 shared papers), Wael Adnan Aljaroudi, MD (4 shared papers) and Richard A. Grimm, DO (4 shared papers).

Selling to cardiovascular disease practices?

See cardiologists in Ohio by site of care and group

Find the practices, groups and hospitals they work with, and the right people to contact at each.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)