Pulmonary function technologists in the United States

  • Pulmonary function technologist
  • United States
Pulmonary function technologists
59
Linked to a hospital or group
2
Hospitals with a pulmonary function technologist
1
States and territories
23

There are 59 pulmonary function technologists in the US. California has the most, 16, and Ashford Hospital has the most affiliated pulmonary function technologists of any hospital, 1.

Find work emails and mobile numbers for all 59 US pulmonary function technologists

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

View contacts for free

California has the most pulmonary function technologists, with 16

There are 59 pulmonary function technologists in the US, according to Dmand AI data. Illinois is second with 6, and Pennsylvania third with 4.

States with the most pulmonary function technologists
#StatePulmonary function technologists
1California16
2Illinois6
3Pennsylvania4
4Texas4
5Oregon4
6Kansas3
7Maryland3
8Florida3
9Washington2
10Arizona1

Top 10 of 23 states and territories with a pulmonary function technologist

Pulmonary function technologists in every other state and territory

  • Wyoming1
  • New Jersey1
  • Indiana1
  • Virginia1
  • Massachusetts1
  • Puerto Rico1
  • Washington, DC1
  • Kentucky1
  • Ohio1
  • Tennessee1
  • Louisiana1
  • Oklahoma1
  • Nevada1

Source: NPPES NPI Registry (CMS)

For health IT teams

Find US pulmonary function technologists by the EHR they use

Dmand AI has the EHR for 31 of 59 US pulmonary function 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.

Ashford Hospital has the most affiliated pulmonary function technologists of any US hospital, with 1

US pulmonary function technologists are affiliated with 1 hospitals in all.

Hospitals with the most pulmonary function technologists in the US
#HospitalPulmonary function technologists
1Ashford HospitalSan Juan, PR1

Top 1 of 1 US hospitals with an affiliated pulmonary function technologist

See every hospital and group for each US pulmonary function technologist

Each public profile names one place a pulmonary function technologist practices. A free account shows all of them, with the employer, the EHR and validated contacts.

Try for free

Source: Dmand AI Affiliation Data

Government and correctional health sites are the most common site of care for US pulmonary function technologists, with 1

1 also practice at hospitals. A pulmonary function technologist can practice at several kinds of site, so the shares overlap.

US pulmonary function technologists by site of care

  1. Government and correctional health sites1
  2. Hospitals1

Sources: Dmand AI Affiliation Data and Dmand AI Practice Data

Every US pulmonary function 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 US pulmonary function 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

Pulmonary function technologists are HCPs whose primary specialty is pulmonary function technologist (taxonomy code 225B00000X), with an active NPI and a US practice address.

FAQ

Frequently asked questions about pulmonary function technologists in the US

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

How many pulmonary function technologists are in the US?

59 pulmonary function technologists have an active NPI, a US practice address and pulmonary function technologist (taxonomy code 225B00000X) as their primary specialty. 2 of them are linked to a hospital or medical group.

Which state has the most pulmonary function technologists?

California, with 16, followed by Illinois with 6 and Pennsylvania with 4.

What is the taxonomy code for pulmonary function technologist?

225B00000X is the NPPES taxonomy code for pulmonary function technologist. Sub-specialties with their own code are counted on their own lists.

Dmand AI

Find the right contacts among US pulmonary function technologists

Search 59 US pulmonary function technologists by state, 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)