Dr. Steven J. Eskind, MD

  • Nashville, TN
  • General surgeon
NPI1558369280
Publications
2
State license
1
Year NPI issued
2005
Practice address
1161 21st Ave S, Nashville, TN 37232-2730
Practice phone
Call (615) 875-5794
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Eskind'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. Steven J. Eskind is a general surgeon in Nashville, Tennessee

Dr. Eskind practices in Nashville, Tennessee.

Dr. Eskind's NPI, 1558369280, was assigned on July 7, 2005. Dr. Eskind holds Tennessee license MD10774.

NPI and contact details
NPI enumeration date
July 7, 2005
NPI status
Active
Practice phone
(615) 875-5794
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male

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

Dr. Steven J. Eskind's practice address is in Nashville, Tennessee

Dr. Eskind's practice address in the NPI Registry is 1161 21st Ave S, Nashville, TN 37232-2730. The practice phone is (615) 875-5794.

  • NPI Registry address
    1161 21st Ave S, Nashville, TN 37232-2730Phone(615) 875-5794

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

Dmand AI tracks the EHR system at Dr. Steven J. Eskind's practice

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

EHR by site
SiteEHR vendor and product
Dr. Eskind'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. Eskind 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. Steven J. Eskind is one of 548 general surgeons in Tennessee

Surgery is Dr. Eskind's primary specialty in the NPI Registry, under taxonomy code 208600000X. Dr. Eskind is licensed in Tennessee.

Specialties and state licenses

  • Surgery, TennesseePrimaryLicense MD10774 · taxonomy 208600000X

General surgeons near Dr. Eskind

Counts of general surgeons 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. Steven J. Eskind's patients have a median age of 47

Across all payers, Dmand AI patient panel data puts Dr. Eskind's median patient age at 47, with 100% women.

Dr. Eskind's patients across all payers

Dmand AI patient panel data covers Medicare, Medicaid and commercial patients.

Patient panel by age, all payers

Median age 47

Patient panel by sex, all payers

  • Women100%
  • Men0%

Source: Dmand AI Patient Panel Data

Dr. Steven J. Eskind has 2 publications on record

Dmand AI links 2 papers to Dr. Eskind, published from 2019 to 2024. Dr. Eskind's most frequent co-authors are Kathleen Claire Gallagher, MD and Kyla Terhune, MD.

Papers2
Years published2019 to 2024

Dr. Eskind's most frequent co-authors

Recent publications by Dr. Eskind

See all 2 publications and co-authors

See who Dr. Eskind researches with

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

How network discovery works

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

Sources for Dr. Steven J. Eskind'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
Medicare patients and the all-payer patient panelDmand AI Patient Panel 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. Steven J. Eskind

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. Steven J. Eskind's NPI number?

Dr. Steven J. Eskind's NPI number is 1558369280. It was assigned on July 7, 2005, and it is active in the NPI Registry.

What kind of doctor is Dr. Steven J. Eskind?

Dr. Steven J. Eskind is a general surgeon in Nashville, Tennessee. The primary specialty in the NPI Registry is Surgery Physician (taxonomy code 208600000X).

Where does Dr. Steven J. Eskind practice?

Dr. Eskind practices at 1161 21st Ave S, Nashville, TN 37232-2730.

What is Dr. Steven J. Eskind's office phone number?

The practice phone on file for Dr. Eskind is (615) 875-5794.

What is Dr. Steven J. Eskind's medical license number?

Dr. Eskind holds Tennessee license MD10774.

How long has Dr. Steven J. Eskind been practicing?

Dr. Eskind's NPI was assigned in 2005.

Does Dr. Steven J. Eskind do research?

Dmand AI links 2 publications to Dr. Eskind, published from 2019 to 2024.

Who does Dr. Steven J. Eskind publish with?

Dr. Eskind's most frequent co-authors are Kathleen Claire Gallagher, MD (1 shared paper) and Kyla Terhune, MD (1 shared paper).

Selling to surgery practices?

See general surgeons in Tennessee 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)