Chad A. Hicks, PA-C

  • Toledo, OH
  • Physician assistant
NPI1760992663PAC ID2163784349
Hospital affiliations
3
Industry payments
$71
Medical groups
3
State licenses
2
Year NPI issued
2017
Practice address
2142 N Cove Blvd, Toledo, OH 43606
Practice phone
Call (419) 593-0214
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

ProMedica Toledo Hospital Emergency Center

Toledo, Ohio

See all 7 affiliations

Find Chad Hicks' 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

Chad A. Hicks is a physician assistant in Toledo, Ohio

Chad Hicks practices at ProMedica Toledo Hospital Emergency Center in Toledo, Ohio.

Chad Hicks' NPI, 1760992663, was assigned on October 5, 2017. Chad Hicks holds Ohio license 50.005399RX.

NPI and contact details
Medicare PAC ID
2163784349
NPI enumeration date
October 5, 2017
NPI status
Active
Accepts Medicare assignment
Yes
Practice phone
(419) 593-0214
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
36
Medical school graduation
2016

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

Chad A. Hicks practices at ProMedica Toledo Hospital Emergency Center in Toledo, Ohio

Chad Hicks' primary practice is ProMedica Toledo Hospital Emergency Center, at 2142 N Cove Blvd, Toledo, OH 43606 in Lucas County. The practice phone is (419) 593-0214.

  • ProMedica Toledo Hospital Emergency Center
    2142 N Cove Blvd, Toledo, OH 43606 · Lucas CountyPhone(419) 593-0214

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

Chad A. Hicks is affiliated with 4 sites of care and 3 medical groups

Chad Hicks' primary practice is ProMedica Toledo Hospital Emergency Center in Toledo, Ohio. Chad Hicks is also affiliated with ProMedica Toledo Hospital. The medical group on file is ProMedica Physicians. Dmand AI also links Chad Hicks to 2 more hospitals and 2 medical groups, each named with a free account.

See all 7 affiliations for Chad Hicks

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

Dmand AI tracks the EHR system at Chad A. Hicks' practice

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

EHR by site
SiteEHR vendor and product
ProMedica Toledo Hospital Emergency CenterAvailable with a free account
+3 more sites and 2 medical groupsAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Chad Hicks 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.

Chad A. Hicks is one of 674 physician assistants in Ohio

Medical is Chad Hicks' primary specialty in the NPI Registry, under taxonomy code 363AM0700X. Dmand AI has Chad Hicks' licenses on file in 2 states: Ohio and Michigan.

Specialties and state licenses

  • Medical physician assistant, OhioPrimaryLicense 50.005399RX · taxonomy 363AM0700X
  • Michigan licenseLicense 5601008321

Physician assistants near Chad Hicks

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

Chad A. Hicks' patients have a median age of 74

Across all payers, Dmand AI patient panel data puts Chad Hicks' median patient age at 74, with 53% women.

Chad Hicks' patients across all payers

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

Patient panel by age, all payers

Median age 74

Patient panel by sex, all payers

  • Women53%
  • Men45%

Source: Dmand AI Patient Panel Data

How Chad A. Hicks takes part in Medicare

Chad Hicks 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)

Chad A. Hicks received $71 in industry payments in 2025

CMS Open Payments shows 1 general payment to Chad Hicks from 1 drug or device company in 2025. Food and beverage make up the largest share, 100% of the total. Bayer HealthCare Pharmaceuticals Inc. paid the most, $71.

Companies that paid Chad Hicks the most, 2025 to 2025

Share is of all general payments to this clinician.

See all payments to Chad Hicks

Source: Open Payments (CMS), 2025 data, released July 7, 2026

Sources for Chad A. Hicks'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
Primary practice, affiliations and health systemNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Practice DataDmand AI Affiliation DataDmand AI Org Hierarchy Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel Data
MIPS scores, telehealth, assignment and procedure percentilesDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)
Industry paymentsOpen Payments (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 Chad A. Hicks

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

What is Chad A. Hicks' NPI number?

Chad A. Hicks' NPI number is 1760992663. It was assigned on October 5, 2017, and it is active in the NPI Registry.

What does Chad A. Hicks specialize in?

Chad A. Hicks is a physician assistant in Toledo, Ohio. The primary specialty in the NPI Registry is Medical Physician Assistant (taxonomy code 363AM0700X).

Where does Chad A. Hicks practice?

Chad Hicks practices at 2142 N Cove Blvd, Toledo, OH 43606. Chad Hicks' primary practice is ProMedica Toledo Hospital Emergency Center in Toledo, Ohio. Dmand AI also links Chad Hicks to 2 hospitals and 2 medical groups.

What is Chad A. Hicks' office phone number?

The practice phone on file for Chad Hicks is (419) 593-0214.

What is Chad A. Hicks' medical license number?

Chad Hicks holds Ohio license 50.005399RX, one of the licenses on file in 2 states.

Which states has Chad A. Hicks been licensed in?

Dmand AI has state licenses on file for Chad Hicks in Ohio and Michigan.

Which hospitals is Chad A. Hicks affiliated with?

Chad Hicks is affiliated with ProMedica Toledo Hospital. Dmand AI links Chad Hicks to 2 more hospitals.

What medical group is Chad A. Hicks part of?

Chad Hicks is linked to ProMedica Physicians. Dmand AI links Chad Hicks to 2 more medical groups.

Does Chad A. Hicks accept Medicare?

Yes. CMS lists Chad Hicks as accepting Medicare assignment.

Has Chad A. Hicks received payments from drug or device companies?

CMS Open Payments shows $71 in general payments to Chad Hicks from 1 company from 2025 to 2025. The largest total came from Bayer HealthCare Pharmaceuticals Inc.

How long has Chad A. Hicks been practicing?

Chad Hicks graduated from medical school in 2016, 10 years ago.

Selling to medical 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)