Cardiologists in Kansas

  • Cardiovascular disease
  • Kansas
Cardiologists
193
Linked to a hospital or group
167
Hospitals with a cardiologist
87
Medical groups with a cardiologist
46
Cities
26

There are 193 cardiologists in Kansas. Kansas University Physicians has the most, 37, and The University of Kansas Hospital has the most affiliated cardiologists, 62. Kansas City is home to 53, and 49% finished medical school 30 or more years ago.

Find work emails and mobile numbers for all 193 Kansas cardiologists

Validated work emails and mobile numbers for Kansas cardiologists, found through healthcare waterfall enrichment, with a free Dmand AI account.

View contacts for free

Kansas cardiologists, listed A to Z by last name (151 to 176 of 176)

Each cardiologist on the list has cardiovascular disease as their primary specialty and a Kansas practice address. The list shows the NPI and city, and how many hospitals and medical groups each one practices with. A free account names every hospital and group, with validated contacts.

Filter this list with a free account

Sort and filter all 193 Kansas cardiologists by city, hospital, medical group, the EHR they use and Medicare volume in Dmand AI.

Filter in Dmand AI
Kansas cardiologists, A to Z, 151 to 176
CardiologistHospitalsMedical groupsEmail and phone
Patrick G. Sheehy, MDTopeka · NPI 16997040151 hospital1 groupContacts
Robert D. Simari, MDKansas City · NPI 1831177294-1 groupContacts
Ashley Ruzicka Simmons, MDKansas City · NPI 12058403601 hospital1 groupContacts
Vasvi Singh, MDLenexa · NPI 16596528165 hospitals1 groupContacts
James A.m. Smith, DOWichita · NPI 16199739063 hospitals3 groupsContacts
Rachel Helene Sosland, MDLenexa · NPI 10231739295 hospitals3 groupsContacts
Lloyd D. Stahl, MDLeawood · NPI 13260984925 hospitals3 groupsContacts
Dusan Aleksandar Stanojevic, MDKansas City · NPI 17707822295 hospitals2 groupsContacts
Richard A. Steckley, MDWichita · NPI 16896370926 hospitals6 groupsContacts
Siva Sagar Taduru, MDKansas City · NPI 15688498755 hospitals2 groupsContacts
Jason T. Tauke, MDWichita · NPI 16896376475 hospitals5 groupsContacts
Drew Jackson Thomas, DOLenexa · NPI 1235626334--Contacts
Jean-Alfred Thomas II, MDKansas City · NPI 11344375695 hospitals2 groupsContacts
William Patrick Tinker, MDCoffeyville · NPI 18412532591 hospital3 groupsContacts
James L. Vacek, MDKansas City · NPI 1932212404--Contacts
Sagar R. Vadhar, DOHays · NPI 19729534381 hospital8 groupsContacts
Michael Vlach, MDKansas City · NPI 18419864371 hospital-Contacts
Kalyan Wagle, MDHays · NPI 16395761845 hospitals1 groupContacts
Andrew Sebastian Waters, MDOverland Park · NPI 15384560255 hospitals2 groupsContacts
Brian C. Weiford, MDKansas City · NPI 11442425385 hospitals2 groupsContacts
Stephanie A. WindishOlathe · NPI 19123138835 hospitals5 groupsContacts
Lambert A. Wu, MDTopeka · NPI 1144304585--Contacts
Andrea N. Yang, MDLeawood · NPI 18412848412 hospitals1 groupContacts
Darrell J. Youngman, DOEmporia · NPI 10139704411 hospital1 groupContacts
K. Michael Zabel, MDLawrence · NPI 18412482673 hospitals1 groupContacts
Martin H. Zink III, MDOverland Park · NPI 19826531505 hospitals4 groupsContacts

Showing 151 to 176 of 176 Kansas cardiologists

The list shows the 176 cardiologists with a public profile. The other 17 are counted in the total and searchable with a free account.

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

For health IT teams

Find Kansas cardiologists by the EHR they use

Dmand AI has the EHR for 176 of 193 Kansas cardiologists, at their hospital and their practice. Filter by Epic, Oracle Health, MEDITECH, athenahealth and more, then reach them with validated work emails and mobile numbers.

Dmand AI

Find the right contacts among Kansas cardiologists

Search 193 Kansas cardiologists by hospital, medical group and the EHR they use, with validated work emails and mobile numbers.

  • 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)