Log inBook a demoStart free trial
Log inStart free trial

Surgical technologists in Tennessee

  • Surgical technologist
  • Tennessee
Surgical technologists
207
Linked to a hospital or group
1
Cities
16

There are 207 surgical technologists in Tennessee. Brentwood is home to 132.

Find work emails and mobile numbers for all 207 Tennessee surgical technologists

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

View contacts for free

Tennessee surgical technologists, listed A to Z by last name

Each surgical technologist on the list has surgical technologist as their primary specialty and a Tennessee 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 207 Tennessee surgical technologists by city, hospital, medical group, the EHR they use and Medicare volume in Dmand AI.

Filter in Dmand AI
Tennessee surgical technologists, A to Z
Surgical technologistHospitalsMedical groupsEmail and phone
Philip Andre' Laponsie, CNIM, REEGTKingsport · NPI 1568912442--Contacts

The list shows the 1 surgical technologists with a public profile. The other 206 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 Tennessee surgical technologists by the EHR they use

Dmand AI has the EHR for 18 of 207 Tennessee surgical technologists, 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.

Try for freeBook a meeting

Brentwood has the most surgical technologists in Tennessee, with 132

132surgical technologists in Brentwood
56surgical technologists in Nashville
3surgical technologists in Chattanooga
3surgical technologists in Memphis

Surgical technologists practice in 16 Tennessee cities. Every city with 10 or more has its own page.

Source: NPPES NPI Registry (CMS)

Ambulatory surgery centers are the most common site of care for Tennessee surgical technologists, with 1

A surgical technologist can practice at several kinds of site, so the shares overlap.

Tennessee surgical technologists by site of care

  1. Ambulatory surgery centers1

Sources: Dmand AI Affiliation Data and Dmand AI Practice Data

Every Tennessee surgical technologist profile shows current hospitals and groups, Medicare activity and NPI details

  • Primary practiceThe main place they practice, with its type and cityOn every profile
  • Every site of careEach hospital, clinic and group where they practice nowWith a free account
  • EmployerThe organization they work for, when one is on fileWith a free account
  • Medicare servicesServices and procedure codes billed to Medicare, from CMSOn every profile
  • Medicare Part D prescribingClaims and drug costs from Part D, from CMSOn every profile
  • Industry paymentsPayments from drug and device makers, from CMS Open PaymentsOn every profile
  • Publications and clinical trialsResearch papers and trials linked to the NPI, when on fileOn every profile
  • Licenses and graduation yearState license numbers and medical school graduation yearOn every profile
  • NPI detailsNPI, enumeration date, primary taxonomy and practice addressOn every profile
  • Work email and mobile numberFound on request through healthcare waterfall enrichment, then validatedWith a free account
  • EHR in useThe EHR at each site where they practiceWith a free account
  • Colleagues at each siteThe clinicians they work with at each hospital and groupWith a free account

Free account: 30 days free, self-serve, no credit card.

Sources: NPPES NPI Registry (CMS), Medicare Physician & Other Practitioners (CMS), Open Payments (CMS) and Dmand AI Affiliation Data

Sources for the Tennessee surgical technologist directory

Sources for the data on this page
Data on this pageSource
HCPs, types and specialtiesNPPES NPI Registry (CMS) and Dmand AI Professional Profile Data
Sites of care, hospitals and medical groupsDmand AI Affiliation Data

Data last refreshed October 2026Report an inaccuracyRemove my information

Surgical technologists are HCPs whose primary specialty is surgical technologist (taxonomy code 246ZS0410X), with an active NPI and a Tennessee practice address.

FAQ

Frequently asked questions about surgical technologists in Tennessee

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

How many surgical technologists are in Tennessee?

207 surgical technologists have an active NPI, a Tennessee practice address and surgical technologist (taxonomy code 246ZS0410X) as their primary specialty. 1 of them are linked to a hospital or medical group.

Which Tennessee cities have the most surgical technologists?

Brentwood, with 132, followed by Nashville (56) and Chattanooga (3). Surgical technologists practice in 16 Tennessee cities in all.

What is the taxonomy code for surgical technologist?

246ZS0410X is the NPPES taxonomy code for surgical technologist. Sub-specialties with their own code are counted on their own lists.

How can I contact surgical technologists in Tennessee?

Dmand AI finds validated work emails, mobile numbers and practice phone numbers for surgical technologists in Tennessee through healthcare waterfall enrichment, matched to the site where each one practices now. They are available with a free Dmand AI account: 30 days free, self-serve, no credit card.

Dmand AI

Find the right contacts among Tennessee surgical technologists

Search 207 Tennessee surgical technologists by hospital, medical group and the EHR they use, with validated work emails and mobile numbers.

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