Dr. Jeffrey L. Hackman, MD

  • Kansas City, MO
  • Emergency medical services (emergency medicine) physician
NPI1114989183
Publications
2
State license
1
Year NPI issued
2006
Practice address
2301 Holmes St, Kansas City, MO 64108-2640
Practice phone
Call (816) 404-1500
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Hackman'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. Jeffrey L. Hackman is an emergency medical services (emergency medicine) physician in Kansas City, Missouri

Dr. Hackman practices in Kansas City, Missouri.

Dr. Hackman's NPI, 1114989183, was assigned on April 5, 2006. Dr. Hackman holds Missouri license 2003028773.

NPI and contact details
NPI enumeration date
April 5, 2006
NPI status
Active
Practice phone
(816) 404-1500
Professional email
Get email
Personal email
Get email
Mobile number
Get number

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

Dr. Jeffrey L. Hackman's practice address is in Kansas City, Missouri

Dr. Hackman's practice address in the NPI Registry is 2301 Holmes St, Kansas City, MO 64108-2640. The practice phone is (816) 404-1500.

  • NPI Registry address
    2301 Holmes St, Kansas City, MO 64108-2640Phone(816) 404-1500

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

Dmand AI tracks the EHR system at Dr. Jeffrey L. Hackman's practice

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

EHR by site
SiteEHR vendor and product
Dr. Hackman'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. Hackman 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. Jeffrey L. Hackman is one of 36 emergency medical services (emergency medicine) physicians in Missouri

Emergency medical services is Dr. Hackman's primary specialty in the NPI Registry, under taxonomy code 207PE0004X. Dr. Hackman is licensed in Missouri.

Specialties and state licenses

  • Emergency medical services (emergency medicine), MissouriPrimaryLicense 2003028773 · taxonomy 207PE0004X

Emergency medical services (emergency medicine) physicians near Dr. Hackman

Counts of emergency medical services (emergency medicine) physicians with a Dmand AI profile, by place and practice. Each opens the list.

36emergency medical services (emergency medicine) physicians in Missouri
8emergency medical services (emergency medicine) physicians in Kansas City

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

Dr. Jeffrey L. Hackman has 2 publications on record

Dmand AI links 2 papers to Dr. Hackman in 2022. Dr. Hackman's most frequent co-authors are William W. Feaster, MD and Ray Walter Segebrecht, MD.

Papers2

Dr. Hackman's most frequent co-authors

Recent publications by Dr. Hackman

See all 2 publications and co-authors

See who Dr. Hackman researches with

Physician Network Discovery turns co-authorship, shared hospitals and shared groups into a map of who Dr. Hackman works with, so you can find a warm path to the right emergency medical services (emergency medicine) physicians.

How network discovery works

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

Sources for Dr. Jeffrey L. Hackman'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
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. Jeffrey L. Hackman

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. Jeffrey L. Hackman's NPI number?

Dr. Jeffrey L. Hackman's NPI number is 1114989183. It was assigned on April 5, 2006, and it is active in the NPI Registry.

What kind of doctor is Dr. Jeffrey L. Hackman?

Dr. Jeffrey L. Hackman is an emergency medical services (emergency medicine) physician in Kansas City, Missouri. The primary specialty in the NPI Registry is Emergency Medical Services (Emergency Medicine) Physician (taxonomy code 207PE0004X).

Where does Dr. Jeffrey L. Hackman practice?

Dr. Hackman practices at 2301 Holmes St, Kansas City, MO 64108-2640.

What is Dr. Jeffrey L. Hackman's office phone number?

The practice phone on file for Dr. Hackman is (816) 404-1500.

What is Dr. Jeffrey L. Hackman's medical license number?

Dr. Hackman holds Missouri license 2003028773.

How long has Dr. Jeffrey L. Hackman been practicing?

Dr. Hackman's NPI was assigned in 2006.

Does Dr. Jeffrey L. Hackman do research?

Dmand AI links 2 publications to Dr. Hackman.

Who does Dr. Jeffrey L. Hackman publish with?

Dr. Hackman's most frequent co-authors are William W. Feaster, MD (1 shared paper) and Ray Walter Segebrecht, MD (1 shared paper).

Selling to emergency medical services practices?

See emergency medical services (emergency medicine) physicians in Missouri 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)