Log inBook a demoStart free trial
Log inStart free trial

Dr. Stephen N. Oesterle, MD

  • Minneapolis, MN
  • Cardiologist
NPI1629107511
Publications
60
State licenses
3
Year NPI issued
2007
Practice address
Medtronic Inc., Ms Lc 400, Minneapolis, MN 55432
Practice phone
Call (763) 505-3020
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Oesterle'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. Stephen N. Oesterle is a cardiologist in Minneapolis, Minnesota

Dr. Oesterle practices in Minneapolis, Minnesota.

Dr. Oesterle's NPI, 1629107511, was assigned on March 5, 2007. Dr. Oesterle graduated from Yale School of Medicine in 1977. Dr. Oesterle's Massachusetts license number on file is 44175.

NPI and contact details
NPI
1629107511NPI Registry (opens in a new tab)
NPI enumeration date
March 5, 2007
NPI status
Active
Practice phone
(763) 505-3020
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Medical school graduation
1977

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

Dr. Stephen N. Oesterle's practice address is in Minneapolis, Minnesota

Dr. Oesterle's practice address in the NPI Registry is Medtronic Inc., Ms Lc 400, Minneapolis, MN 55432. The practice phone is (763) 505-3020.

  • NPI Registry address
    Medtronic Inc., Ms Lc 400, Minneapolis, MN 55432Phone(763) 505-3020

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

Dmand AI tracks the EHR system at Dr. Stephen N. Oesterle's practice

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

EHR by site
SiteEHR vendor and product
Dr. Oesterle'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. Oesterle 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.

Try for freeBook a meeting

Dr. Stephen N. Oesterle is one of 540 cardiologists in Minnesota

Cardiovascular disease is Dr. Oesterle's primary specialty in the NPI Registry, under taxonomy code 207RC0000X. Dmand AI has Dr. Oesterle's licenses on file in 3 states: Massachusetts, California and Maryland.

Specialties and state licenses

  • Cardiovascular disease, MassachusettsPrimaryLicense 44175 · 1979 to 2017 · taxonomy 207RC0000X
  • California licenseSince 1980
  • Maryland license1992 to 1993

Cardiologists near Dr. Oesterle

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

540cardiologists in Minnesota190cardiologists in Minneapolis

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

Dr. Stephen N. Oesterle has 60 publications on record

Dmand AI links 60 papers to Dr. Oesterle. The most frequent topics are Coronary Disease, Stents and Coronary Angiography. Dr. Oesterle has published most often in Circulation. Dr. Oesterle's most frequent co-authors are Alan Ching-Yuen Yeung, MD, Peter J. Fitzgerald, MD and John S. Schroeder, MD.

Papers60

Topics Dr. Oesterle writes about most

  • Coronary Disease
  • Stents
  • Coronary Angiography
  • Coronary Vessels
  • Angioplasty, Balloon, Coronary
  • Myocardial Revascularization
  • Ultrasonography, Interventional
  • Cardiac Catheterization

Dr. Oesterle's most frequent co-authors

Recent publications by Dr. Oesterle

See all 60 publications and co-authors

See who Dr. Oesterle researches with

Physician Network Discovery turns co-authorship, shared hospitals and shared groups into a map of who Dr. Oesterle 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

Dr. Stephen N. Oesterle has 1 award and honors on record

Dmand AI lists 1 award for Dr. Oesterle.

Awards and honors for Dr. Oesterle

  1. Undated
    • Whos Who

Source: Dmand AI Professional Profile Data

Dr. Stephen N. Oesterle graduated from Yale School of Medicine

Dr. Oesterle graduated from Yale School of Medicine in 1977.

  1. Medical schoolYale School of Medicine

Source: Dmand AI Professional Profile Data

Sources for Dr. Stephen N. Oesterle'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
Awards and committee rolesDmand AI Professional Profile Data
Training, board certification and membershipsDmand AI Professional Profile Data
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. Stephen N. Oesterle

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. Stephen N. Oesterle's NPI number?

Dr. Stephen N. Oesterle's NPI number is 1629107511. It was assigned on March 5, 2007, and it is active in the NPI Registry.

What kind of doctor is Dr. Stephen N. Oesterle?

Dr. Stephen N. Oesterle is a cardiologist in Minneapolis, Minnesota. The primary specialty in the NPI Registry is Cardiovascular Disease Physician (taxonomy code 207RC0000X).

Where does Dr. Stephen N. Oesterle practice?

Dr. Oesterle practices at Medtronic Inc., Ms Lc 400, Minneapolis, MN 55432.

What is Dr. Stephen N. Oesterle's office phone number?

The practice phone on file for Dr. Oesterle is (763) 505-3020.

What is Dr. Stephen N. Oesterle's medical license number?

Dr. Oesterle's Massachusetts license number on file is 44175, one of the licenses on file in 3 states.

Which states has Dr. Stephen N. Oesterle been licensed in?

Dmand AI has state licenses on file for Dr. Oesterle in Massachusetts (1979 to 2017), California (since 1980) and Maryland (1992 to 1993).

Where did Dr. Stephen N. Oesterle go to medical school?

Dr. Oesterle graduated from Yale School of Medicine in 1977.

How long has Dr. Stephen N. Oesterle been practicing?

Dr. Oesterle graduated from medical school in 1977, 49 years ago.

Does Dr. Stephen N. Oesterle do research?

Dmand AI links 60 publications to Dr. Oesterle.

Who does Dr. Stephen N. Oesterle publish with?

Dr. Oesterle's most frequent co-authors are Alan Ching-Yuen Yeung, MD (15 shared papers), Peter J. Fitzgerald, MD (6 shared papers) and John S. Schroeder, MD (6 shared papers).

Selling to cardiovascular disease practices?

See cardiologists in Minnesota by site of care and group

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

Start free trialBook a demo
  • 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)
Read the Cookie Policy