Dr. Jay G. Hacking, MD

  • Fredericksburg, VA
  • Anesthesiologist
NPI1356542393PAC ID1052503745
Medicare services, 2024
49
Medicare patients, 2024
147
Hospital affiliations
1
Medical group
1
State license
1
Practice address
4600 Spotsylvania Parkway, Fredericksburg, VA 22408
Practice phone
Call (540) 498-4000
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Spotsylvania Regional Medical Center

Hospital · Fredericksburg, Virginia

Find Dr. Hacking'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. Jay G. Hacking is an anesthesiologist in Fredericksburg, Virginia

Dr. Hacking practices at Spotsylvania Regional Medical Center in Fredericksburg, Virginia, part of HCA Healthcare.

Dr. Hacking's NPI, 1356542393, was assigned on May 29, 2007. Dr. Hacking graduated from Baylor College of Medicine in 2006. Dr. Hacking holds Virginia license 0101247679.

NPI and contact details
Medicare PAC ID
1052503745
NPI enumeration date
May 29, 2007
NPI status
Active
Accepts Medicare assignment
Yes
Practice phone
(540) 498-4000
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
46
Medical school graduation
2006

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; Dmand AI Affiliation Data; and Doctors and Clinicians National Downloadable File (CMS)

Dr. Jay G. Hacking practices at Spotsylvania Regional Medical Center in Fredericksburg, Virginia

Dr. Hacking's primary practice is Spotsylvania Regional Medical Center, at 4600 Spotsylvania Parkway, Fredericksburg, VA 22408 in Spotsylvania County. The practice phone is (540) 498-4000.

Source: Dmand AI Affiliation Data

Dr. Jay G. Hacking is affiliated with 1 site of care and 1 medical group

Dr. Hacking's primary practice is Spotsylvania Regional Medical Center in Fredericksburg, Virginia, part of HCA Healthcare. The medical group on file is Surgical Anesthesia Associates.

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

Dmand AI tracks the EHR system at Dr. Jay G. Hacking's practice

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

EHR by site
SiteEHR vendor and product
Spotsylvania Regional 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. Hacking practices

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

Dr. Jay G. Hacking is one of 1,215 anesthesiologists in Virginia

Anesthesiology is Dr. Hacking's primary specialty in the NPI Registry, under taxonomy code 207L00000X. Dr. Hacking is licensed in Virginia.

Specialties and state licenses

  • Anesthesiology, VirginiaPrimaryLicense 0101247679 · taxonomy 207L00000X

Anesthesiologists near Dr. Hacking

Counts of anesthesiologists 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. Jay G. Hacking billed Medicare for 49 services in 2024

CMS data shows 49 Medicare services from Dr. Hacking across 3 procedure codes in 2024, for 147 Medicare patients. Medicare paid $2,339 for them. Every service was in a facility, such as a hospital, rather than an office.

Medicare services, 202449
Medicare patients147
Paid by Medicare$2,339
Procedure codes3

Dr. Hacking's Medicare services by type, 2018 to 2024

  • 2018
  • 2024
Anesthesia
2018: 132024: 35169%
Surgery
2018: 02024: 14

Dr. Hacking compared with the Virginia median for anesthesiologists, 2024

  • Dr. Hacking
  • Virginia median
Medicare services
49vs 14265% below
Medicare patients
147vs 21632% below

Medians across 1,171 anesthesiologists in Virginia with Dmand AI profiles that report each measure.

Dr. Hacking's most billed Medicare procedure codes, 2024

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. Hacking

Need commercial claims for Dr. Hacking?

Medicare shows one payer. Book a meeting to get commercial claims data for Dr. Hacking and other anesthesiologists in Virginia.

Book a meeting

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

Dr. Jay G. Hacking treated 147 Medicare patients in 2024, average age 75

CMS counts 147 Medicare patients who saw Dr. Hacking in 2024. The largest group is 65 to 74, with 65 patients. 75% of them have high blood pressure, and 75% have high cholesterol. 8% are also on Medicaid. Their average risk score is 1.26, where 1.00 is the Medicare average.

Across all payers, Dmand AI patient panel data puts Dr. Hacking's median patient age at 56, with 61% women.

Medicare patients, 2024147
Average age75
Average risk score1.26
Also on Medicaid8%

Dr. Hacking's Medicare patients by age, 2024

CMS leaves out age groups with fewer than 11 patients.

Dr. Hacking's Medicare patients by sex, 2024

  • Women7551%
  • Men7249%

Chronic conditions among Dr. Hacking's Medicare patients, 2024

  1. High blood pressure75%
  2. High cholesterol75%
  3. Arthritis59%
  4. Ischemic heart disease42%
  5. Diabetes41%
  6. Mood disorders29%
  7. Anxiety28%
  8. Atrial fibrillation28%

Share of Medicare patients with each condition. A patient can have several.

Dr. Hacking's patients across all payers

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

Patient panel by age, all payers

Median age 56

Patient panel by sex, all payers

  • Women61%
  • Men39%

Sources: Dmand AI Patient Panel Data; and Medicare Physician & Other Practitioners - by Provider (CMS), 2024 data

How Dr. Jay G. Hacking takes part in Medicare

Dr. Hacking accepts Medicare assignment, so Medicare's approved amount is taken as full payment.

Accepts Medicare assignment
Yes

Source: Doctors and Clinicians National Downloadable File (CMS)

For MedTech and pharma teams

Find anesthesiologists like Dr. Hacking 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.

Dr. Jay G. Hacking graduated from Baylor College of Medicine

Dr. Hacking graduated from Baylor College of Medicine in 2006.

  1. Medical schoolBaylor College of Medicine

Source: Dmand AI Professional Profile Data

Sources for Dr. Jay G. Hacking'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 DataMedicare Physician & Other Practitioners - by Provider (CMS) (opens in a new tab)
MIPS scores, telehealth, assignment and procedure percentilesDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)
Training, board certification and membershipsDmand AI Professional Profile 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. Jay G. Hacking

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. Jay G. Hacking's NPI number?

Dr. Jay G. Hacking's NPI number is 1356542393. It was assigned on May 29, 2007, and it is active in the NPI Registry.

What kind of doctor is Dr. Jay G. Hacking?

Dr. Jay G. Hacking is an anesthesiologist in Fredericksburg, Virginia. The primary specialty in the NPI Registry is Anesthesiology Physician (taxonomy code 207L00000X).

Where does Dr. Jay G. Hacking practice?

Dr. Hacking practices at 4600 Spotsylvania Parkway, Fredericksburg, VA 22408. Dr. Hacking's primary practice is Spotsylvania Regional Medical Center in Fredericksburg, Virginia, part of HCA Healthcare.

What is Dr. Jay G. Hacking's office phone number?

The practice phone on file for Dr. Hacking is (540) 498-4000.

What is Dr. Jay G. Hacking's medical license number?

Dr. Hacking holds Virginia license 0101247679.

Which hospitals is Dr. Jay G. Hacking affiliated with?

Dr. Hacking practices at Spotsylvania Regional Medical Center in Fredericksburg, Virginia.

What medical group is Dr. Jay G. Hacking part of?

Dr. Hacking is linked to Surgical Anesthesia Associates.

Does Dr. Jay G. Hacking accept Medicare?

Yes. CMS data shows Dr. Hacking billed Medicare for 49 services in 2024, and Dr. Hacking accepts Medicare assignment.

How many Medicare patients does Dr. Jay G. Hacking see?

CMS counts 147 Medicare patients who saw Dr. Hacking in 2024, with an average age of 75.

What services does Dr. Jay G. Hacking bill to Medicare?

In 2024, Dr. Hacking's most billed Medicare services were anesthesia (00811), anesthesia (00731) and surgery: brain, spine and nerves (64447).

Where did Dr. Jay G. Hacking go to medical school?

Dr. Hacking graduated from Baylor College of Medicine in 2006.

How long has Dr. Jay G. Hacking been practicing?

Dr. Hacking graduated from medical school in 2006, 20 years ago.

Selling to anesthesiology practices?

See anesthesiologists in Virginia 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)