Amanda Boyer, PA-C

  • Baltimore, MD
  • Physician assistant
NPI1952705352
Hospital affiliations
1
Medical groups
2
State license
1
Year NPI issued
2014
Practice address
301 Saint Paul Place, Baltimore, MD 21202
Practice phone
Call (410) 332-9237
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Mercy Medical Center

Hospital · Baltimore, Maryland

See all 3 affiliations

Find Amanda Boyer'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

Amanda Boyer is a physician assistant in Baltimore, Maryland

Amanda Boyer practices at Mercy Medical Center in Baltimore, Maryland, part of Mercy Medical Center.

Amanda Boyer's NPI, 1952705352, was assigned on October 14, 2014. Amanda Boyer holds Maryland license C0005573.

NPI and contact details
NPI enumeration date
October 14, 2014
NPI status
Active
Practice phone
(410) 332-9237
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Female

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

Amanda Boyer practices at Mercy Medical Center in Baltimore, Maryland

Amanda Boyer's primary practice is Mercy Medical Center, at 301 Saint Paul Place, Baltimore, MD 21202 in Baltimore City. The practice phone is (410) 332-9237.

  • Mercy Medical Center
    301 Saint Paul Place, Baltimore, MD 21202 · Baltimore CityPhone(410) 332-9237

Source: Dmand AI Affiliation Data

Amanda Boyer is affiliated with 1 site of care and 2 medical groups

Amanda Boyer's primary practice is Mercy Medical Center in Baltimore, Maryland, part of Mercy Medical Center. The medical group on file is Mercy Personal Physicians Downtown. Dmand AI also links Amanda Boyer to 1 more medical group, named with a free account.

See all 3 affiliations for Amanda Boyer

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

Dmand AI tracks the EHR system at Amanda Boyer's practice

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

EHR by site
SiteEHR vendor and product
Mercy Medical CenterAvailable with a free account
+1 medical groupAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Amanda Boyer practices

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

Amanda Boyer is one of 2,452 physician assistants in Maryland

Physician assistant is Amanda Boyer's primary specialty in the NPI Registry, under taxonomy code 363A00000X. Amanda Boyer is licensed in Maryland.

Specialties and state licenses

  • Physician assistant, MarylandPrimaryLicense C0005573 · taxonomy 363A00000X

Physician assistants near Amanda Boyer

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

Amanda Boyer's patients have a median age of 31

Across all payers, Dmand AI patient panel data puts Amanda Boyer's median patient age at 31, with 75% women.

Amanda Boyer's patients across all payers

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

Patient panel by age, all payers

Median age 31

Patient panel by sex, all payers

  • Women75%
  • Men25%

Source: Dmand AI Patient Panel Data

Sources for Amanda Boyer'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 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 Amanda Boyer

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

What is Amanda Boyer's NPI number?

Amanda Boyer's NPI number is 1952705352. It was assigned on October 14, 2014, and it is active in the NPI Registry.

What does Amanda Boyer specialize in?

Amanda Boyer is a physician assistant in Baltimore, Maryland. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Amanda Boyer practice?

Amanda Boyer practices at 301 Saint Paul Place, Baltimore, MD 21202. Amanda Boyer's primary practice is Mercy Medical Center in Baltimore, Maryland, part of Mercy Medical Center. Dmand AI also links Amanda Boyer to 1 medical group.

What is Amanda Boyer's office phone number?

The practice phone on file for Amanda Boyer is (410) 332-9237.

What is Amanda Boyer's medical license number?

Amanda Boyer holds Maryland license C0005573.

Which hospitals is Amanda Boyer affiliated with?

Amanda Boyer practices at Mercy Medical Center in Baltimore, Maryland.

What medical group is Amanda Boyer part of?

Amanda Boyer is linked to Mercy Personal Physicians Downtown. Dmand AI links Amanda Boyer to 1 more medical group.

How long has Amanda Boyer been practicing?

Amanda Boyer's NPI was assigned in 2014.

Selling to physician assistant practices?

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