Dr. Daniel Duggleby, MD

  • Salt Lake City, UT
  • Emergency medicine physician
NPI1487614962
Medicare services, 2018
29
Hospital affiliations
1
State license
1
Year NPI issued
2006
Practice address
500 Foothill Blvd., Salt Lake City, UT 84148
Practice phone
Call (801) 584-1211
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Duggleby'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. Daniel Duggleby is an emergency medicine physician in Salt Lake City, Utah

Dr. Duggleby practices at George E. Wahlen Department of Veterans Affairs Medical Center in Salt Lake City, Utah, part of Veterans Health Administration.

Dr. Duggleby's NPI, 1487614962, was assigned on March 27, 2006. Dr. Duggleby holds Utah license 170131-1205.

NPI and contact details
NPI enumeration date
March 27, 2006
NPI status
Active
Practice phone
(801) 584-1211
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

Dr. Daniel Duggleby practices at George E. Wahlen Department of Veterans Affairs Medical Center in Salt Lake City, Utah

Dr. Duggleby's primary practice is George E. Wahlen Department of Veterans Affairs Medical Center, at 500 Foothill Blvd., Salt Lake City, UT 84148 in Salt Lake County. The practice phone is (801) 584-1211.

Source: Dmand AI Affiliation Data

Dr. Daniel Duggleby is affiliated with 1 site of care

Dr. Duggleby's primary practice is George E. Wahlen Department of Veterans Affairs Medical Center in Salt Lake City, Utah, part of Veterans Health Administration. Dr. Duggleby's employer is on file too: a hospital.

See Dr. Duggleby's affiliation in Dmand AI

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

Dmand AI tracks the EHR system at Dr. Daniel Duggleby's practice

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

EHR by site
SiteEHR vendor and product
George E. Wahlen Department of Veterans Affairs Medical CenterAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Dr. Duggleby practices

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

Dr. Daniel Duggleby is one of 547 emergency medicine physicians in Utah

Emergency medicine is Dr. Duggleby's primary specialty in the NPI Registry, under taxonomy code 207P00000X. Dr. Duggleby is licensed in Utah.

Specialties and state licenses

  • Emergency medicine, UtahPrimaryLicense 170131-1205 · taxonomy 207P00000X

Emergency medicine physicians near Dr. Duggleby

Counts of emergency medicine physicians 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. Daniel Duggleby billed Medicare for 29 services in 2018

CMS data shows 29 Medicare services from Dr. Duggleby across 2 procedure codes in 2018. Medicare paid $3,469 for them. Every service was in a facility, such as a hospital, rather than an office.

Medicare services, 201829
Paid by Medicare$3,469
Procedure codes2

Dr. Duggleby's Medicare services by type, 2017 to 2018

  • 2017
  • 2018
Office and hospital visits
2017: 362018: 2919%

Dr. Duggleby compared with the Utah median for emergency medicine physicians, 2018

  • Dr. Duggleby
  • Utah median
Medicare services
29vs 21987% below

Medians across 532 emergency medicine physicians in Utah with Dmand AI profiles that report each measure.

Dr. Duggleby's most billed Medicare procedure codes, 2018

CMS publishes codes billed for 11 or more Medicare patients. Each label is the code family; CPT descriptions are licensed by the AMA.

See all procedures by Dr. Duggleby

Need commercial claims for Dr. Duggleby?

Medicare shows one payer. Book a meeting to get commercial claims data for Dr. Duggleby and other emergency medicine physicians in Utah.

Book a meeting

Sources: Medicare Physician & Other Practitioners - by Provider and Service (CMS), 2024 data; and Dmand AI Peer Benchmarks

Dr. Daniel Duggleby's patients have a median age of 35

Across all payers, Dmand AI patient panel data puts Dr. Duggleby's median patient age at 35, with 0% women.

Dr. Duggleby's patients across all payers

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

Patient panel by age, all payers

Median age 35

Patient panel by sex, all payers

  • Women0%
  • Men100%

Source: Dmand AI Patient Panel Data

For MedTech and pharma teams

Find emergency medicine physicians like Dr. Duggleby 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 Dr. Daniel Duggleby'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 services and procedure codesMedicare Physician & Other Practitioners - by Provider and Service (CMS) (opens in a new tab)
State medians for the same specialtyDmand AI Peer Benchmarks
Medicare patients and the all-payer patient panelDmand AI Patient Panel 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. Daniel Duggleby

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. Daniel Duggleby's NPI number?

Dr. Daniel Duggleby's NPI number is 1487614962. It was assigned on March 27, 2006, and it is active in the NPI Registry.

What kind of doctor is Dr. Daniel Duggleby?

Dr. Daniel Duggleby is an emergency medicine physician in Salt Lake City, Utah. The primary specialty in the NPI Registry is Emergency Medicine Physician (taxonomy code 207P00000X).

Where does Dr. Daniel Duggleby practice?

Dr. Duggleby practices at 500 Foothill Blvd., Salt Lake City, UT 84148. Dr. Duggleby's primary practice is George E. Wahlen Department of Veterans Affairs Medical Center in Salt Lake City, Utah, part of Veterans Health Administration.

What is Dr. Daniel Duggleby's office phone number?

The practice phone on file for Dr. Duggleby is (801) 584-1211.

What is Dr. Daniel Duggleby's medical license number?

Dr. Duggleby holds Utah license 170131-1205.

Which hospitals is Dr. Daniel Duggleby affiliated with?

Dr. Duggleby practices at George E. Wahlen Department of Veterans Affairs Medical Center in Salt Lake City, Utah.

Does Dr. Daniel Duggleby accept Medicare?

Yes. CMS data shows Dr. Duggleby billed Medicare for 29 services in 2018.

What services does Dr. Daniel Duggleby bill to Medicare?

In 2018, Dr. Duggleby's most billed Medicare services were emergency department visit (99285) and emergency department visit (99284).

How long has Dr. Daniel Duggleby been practicing?

Dr. Duggleby's NPI was assigned in 2006.

Selling to emergency medicine practices?

See emergency medicine physicians 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)