Yusef A. Hammuda, PA

  • Toledo, OH
  • Physician assistant
NPI1659624351
Medicare patients, 2024
110
Part D claims, 2024
276
Hospital affiliations
1
Medical groups
10
State license
1
Practice address
2213 Cherry Street, Toledo, OH 43608
Practice phone
Call (419) 251-3232
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Yusef Hammuda'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

Yusef A. Hammuda is a physician assistant in Toledo, Ohio

Yusef Hammuda practices at Mercy Health - St. Vincent Medical Center in Toledo, Ohio, part of Bon Secours Mercy Health.

Yusef Hammuda's NPI, 1659624351, was assigned on October 18, 2012. Yusef Hammuda holds Ohio license 50.003550.

NPI and contact details
NPI enumeration date
October 18, 2012
NPI status
Active
Practice phone
(419) 251-3232
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
40
Medical school graduation
2012

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

Yusef A. Hammuda practices at Mercy Health - St. Vincent Medical Center in Toledo, Ohio

Yusef Hammuda's primary practice is Mercy Health - St. Vincent Medical Center, at 2213 Cherry Street, Toledo, OH 43608 in Lucas County. The practice phone is (419) 251-3232.

Source: Dmand AI Affiliation Data

Yusef A. Hammuda is affiliated with 1 site of care and 10 medical groups

Yusef Hammuda's primary practice is Mercy Health - St. Vincent Medical Center in Toledo, Ohio, part of Bon Secours Mercy Health. The medical group on file is Emergency Professional Services of Ohio, Inc. Dmand AI also links Yusef Hammuda to 9 more medical groups, each named with a free account.

See all 11 affiliations for Yusef Hammuda

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

Dmand AI tracks the EHR system at Yusef A. Hammuda's practice

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

EHR by site
SiteEHR vendor and product
Mercy Health - St. Vincent Medical CenterAvailable with a free account
+9 medical groupsAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Yusef Hammuda practices

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

Yusef A. Hammuda is one of 4,524 physician assistants in Ohio

Physician assistant is Yusef Hammuda's primary specialty in the NPI Registry, under taxonomy code 363A00000X. Yusef Hammuda is licensed in Ohio.

Specialties and state licenses

  • Physician assistant, OhioPrimaryLicense 50.003550 · taxonomy 363A00000X

Physician assistants near Yusef Hammuda

Counts of physician assistants 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

Yusef A. Hammuda treated 110 Medicare patients in 2024, average age 74

CMS counts 110 Medicare patients who saw Yusef Hammuda in 2024. The largest group is 65 to 74, with 49 patients. 75% of them have high blood pressure, and 69% have high cholesterol. 14% are also on Medicaid. Their average risk score is 1.41, where 1.00 is the Medicare average.

Across all payers, Dmand AI patient panel data puts Yusef Hammuda's median patient age at 47, with 57% women.

Medicare patients, 2024110
Average age74
Average risk score1.41
Also on Medicaid14%

Yusef Hammuda's Medicare patients by age, 2024

Yusef Hammuda's Medicare patients by sex, 2024

  • Women6963%
  • Men4137%

Chronic conditions among Yusef Hammuda's Medicare patients, 2024

  1. High blood pressure75%
  2. High cholesterol69%
  3. Arthritis60%
  4. Anxiety37%
  5. Mood disorders31%
  6. Chronic kidney disease30%
  7. Depression30%
  8. Ischemic heart disease26%

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

Yusef Hammuda's patients across all payers

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

Patient panel by age, all payers

Median age 47

Patient panel by sex, all payers

  • Women57%
  • Men42%

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

Yusef A. Hammuda wrote 276 Medicare Part D claims in 2024

In 2024, Yusef Hammuda wrote 276 Medicare Part D claims for 202 patients. 94% of them were for generic drugs.

Part D claims, 2024276
Part D patients202

Yusef Hammuda's Part D claims by kind of drug, 2024

  • Generic260 claims94%
  • Brand-name and other16 claims6%

Drug classes CMS tracks in Yusef Hammuda's Part D claims, 2024

  • Opioids18%51 of 276 claims
  • Antibiotics32%89 of 276 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), 2024 data

For MedTech and pharma teams

Find physician assistants like Yusef Hammuda 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 Yusef A. Hammuda'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 DataMedicare Physician & Other Practitioners - by Provider (CMS) (opens in a new tab)
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 Yusef A. Hammuda

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

What is Yusef A. Hammuda's NPI number?

Yusef A. Hammuda's NPI number is 1659624351. It was assigned on October 18, 2012, and it is active in the NPI Registry.

What does Yusef A. Hammuda specialize in?

Yusef A. Hammuda is a physician assistant in Toledo, Ohio. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Yusef A. Hammuda practice?

Yusef Hammuda practices at 2213 Cherry Street, Toledo, OH 43608. Yusef Hammuda's primary practice is Mercy Health - St. Vincent Medical Center in Toledo, Ohio, part of Bon Secours Mercy Health. Dmand AI also links Yusef Hammuda to 9 medical groups.

What is Yusef A. Hammuda's office phone number?

The practice phone on file for Yusef Hammuda is (419) 251-3232.

What is Yusef A. Hammuda's medical license number?

Yusef Hammuda holds Ohio license 50.003550.

Which hospitals is Yusef A. Hammuda affiliated with?

Yusef Hammuda practices at Mercy Health - St. Vincent Medical Center in Toledo, Ohio.

What medical group is Yusef A. Hammuda part of?

Yusef Hammuda is linked to Emergency Professional Services of Ohio, Inc. Dmand AI links Yusef Hammuda to 9 more medical groups.

How many Medicare patients does Yusef A. Hammuda see?

CMS counts 110 Medicare patients who saw Yusef Hammuda in 2024, with an average age of 74.

How long has Yusef A. Hammuda been practicing?

Yusef Hammuda graduated from medical school in 2012, 14 years ago.

Selling to physician assistant practices?

See physician assistants in Ohio 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)