Jacob A. Haslem, DDS

  • Saint George, UT
  • Dentist
NPI1922237379
Part D claims, 2026
21
Hospital affiliations
3
Medical group
1
State license
1
Year NPI issued
2009
Practice address
1380 East Medical Center Drive, Saint George, UT 84790
Practice phone
Call (435) 251-2100
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

St. George Regional Hospital

Hospital · Saint George, Utah

See all 5 affiliations

Find Jacob Haslem'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

Jacob A. Haslem is a dentist in Saint George, Utah

Jacob Haslem practices at St. George Regional Hospital in Saint George, Utah, part of Intermountain Health.

Jacob Haslem's NPI, 1922237379, was assigned on July 7, 2009. Jacob Haslem holds Arizona license 7797.

NPI and contact details
NPI enumeration date
July 7, 2009
NPI status
Active
Practice phone
(435) 251-2100
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male

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

Jacob A. Haslem practices at St. George Regional Hospital in Saint George, Utah

Jacob Haslem's primary practice is St. George Regional Hospital, at 1380 East Medical Center Drive, Saint George, UT 84790 in Washington County. The practice phone is (435) 251-2100.

Source: Dmand AI Affiliation Data

Jacob A. Haslem is affiliated with 4 sites of care and 1 medical group

Jacob Haslem's primary practice is St. George Regional Hospital in Saint George, Utah, part of Intermountain Health. Jacob Haslem is also affiliated with Tuba City Regional Health Care Corporation. The medical group on file is Tuba City Regional Health. Dmand AI also links Jacob Haslem to 1 more hospital and 1 behavioral health center, each named with a free account. Jacob Haslem's employer is on file too: a hospital.

See all 5 affiliations for Jacob Haslem

Sources: Dmand AI Affiliation Data; and Dmand AI Org Hierarchy Data

Dmand AI tracks the EHR system at Jacob A. Haslem's practice

Dmand AI tracks the electronic health record (EHR) system at each site where Jacob Haslem practices, 4 sites in all. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
St. George Regional HospitalAvailable with a free account
+3 more affiliated sitesAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Jacob Haslem practices

Dmand AI maps EHR vendors, IT decision makers and buying committees across Intermountain Health and 6.2K+ hospitals, with verified contacts in the same login.

Jacob A. Haslem is one of 300 dentists in Utah

Dentist is Jacob Haslem's primary specialty in the NPI Registry, under taxonomy code 122300000X. Jacob Haslem is licensed in Arizona.

Specialties and state licenses

  • Dentist, ArizonaPrimaryLicense 7797 · taxonomy 122300000X

Dentists near Jacob Haslem

Counts of dentists 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

Jacob A. Haslem's patients have a median age of 12

Across all payers, Dmand AI patient panel data puts Jacob Haslem's median patient age at 12, with 50% women.

Jacob Haslem's patients across all payers

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

Patient panel by age, all payers

Median age 12

Patient panel by sex, all payers

  • Women50%
  • Men50%

Source: Dmand AI Patient Panel Data

Jacob A. Haslem wrote 21 Medicare Part D claims in 2026

In 2026, Jacob Haslem wrote 21 Medicare Part D claims for 17 patients. 95% of them were for generic drugs.

Part D claims, 202621
Part D patients17

Jacob Haslem's Part D claims by kind of drug, 2026

  • Generic20 claims95%
  • Brand-name and other1 claims5%

Drug classes CMS tracks in Jacob Haslem's Part D claims, 2026

  • Antibiotics90%19 of 21 claims

Share of all Part D claims for each drug class CMS reports on. Classes with no claims are left out.

Source: Medicare Part D Prescribers - by Provider (CMS), 2026 data

For MedTech and pharma teams

Find dentists like Jacob Haslem by procedure volume and prescribing

Filter 7.4M+ HCPs by Medicare procedures, Part D drugs and Open Payments history, then reach them with verified contacts in one login.

Sources for Jacob A. Haslem'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 phoneDmand AI Affiliation Data
Primary practice, affiliations and health systemDmand AI Affiliation DataDmand AI Org Hierarchy Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel Data
Part D prescribingMedicare Part D Prescribers - by Provider (CMS) (opens in a new tab)
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 Jacob A. Haslem

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

What is Jacob A. Haslem's NPI number?

Jacob A. Haslem's NPI number is 1922237379. It was assigned on July 7, 2009, and it is active in the NPI Registry.

What does Jacob A. Haslem specialize in?

Jacob A. Haslem is a dentist in Saint George, Utah. The primary specialty in the NPI Registry is Dentist (taxonomy code 122300000X).

Where does Jacob A. Haslem practice?

Jacob Haslem practices at 1380 East Medical Center Drive, Saint George, UT 84790. Jacob Haslem's primary practice is St. George Regional Hospital in Saint George, Utah, part of Intermountain Health. Dmand AI also links Jacob Haslem to 1 hospital and 1 behavioral health center, and a free account names each one.

What is Jacob A. Haslem's office phone number?

The practice phone on file for Jacob Haslem is (435) 251-2100. Dmand AI also checks direct phone and mobile numbers, available with a free account.

What is Jacob A. Haslem's email address?

Dmand AI checks professional and personal email addresses for Jacob Haslem through healthcare-specific waterfall enrichment. They are available with a free Dmand AI account.

What is Jacob A. Haslem's medical license number?

Jacob Haslem holds Arizona license 7797.

Which hospitals is Jacob A. Haslem affiliated with?

Jacob Haslem practices at St. George Regional Hospital in Saint George, Utah. Jacob Haslem is also affiliated with Tuba City Regional Health Care Corporation. Dmand AI links Jacob Haslem to 1 more hospital, named with a free account.

What medical group is Jacob A. Haslem part of?

Jacob Haslem is linked to Tuba City Regional Health.

Who employs Jacob A. Haslem?

Dmand AI has Jacob Haslem's employer on file: a hospital. The organization's name is available with a free Dmand AI account.

Who does Jacob A. Haslem practice with?

Dmand AI links 228 HCPs to Jacob Haslem's primary medical group, 13 of them dentists. A free account lists them, with verified contacts.

How long has Jacob A. Haslem been practicing?

Jacob Haslem's NPI was assigned in 2009.

What EHR does Jacob A. Haslem's practice use?

Dmand AI tracks the EHR system at St. George Regional Hospital and at 3 more affiliated sites. The vendor and product are available with a free Dmand AI account.

Selling to dentist practices?

See dentists in Utah 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)