Megan Dawn Eppens, FNP-BC

  • Prescott, AZ
  • Family nurse practitioner
NPI1316243447
Hospital affiliations
1
State licenses
2
Year NPI issued
2011
Practice address
1003 Willow Creek Road, Prescott, AZ 86301
Practice phone
Call (928) 445-2700
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Find Megan Eppens' 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

Megan Dawn Eppens is a family nurse practitioner in Prescott, Arizona

Megan Eppens practices at Dignity Health, Yavapai Regional Medical Center West in Prescott, Arizona, part of CommonSpirit Health.

Megan Eppens' NPI, 1316243447, was assigned on February 8, 2011. Megan Eppens holds Arizona license AP8766.

NPI and contact details
NPI enumeration date
February 8, 2011
NPI status
Active
Practice phone
(928) 445-2700
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Female
Estimated age
42
Medical school graduation
2010

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

Megan Dawn Eppens practices at Dignity Health, Yavapai Regional Medical Center West in Prescott, Arizona

Megan Eppens' primary practice is Dignity Health, Yavapai Regional Medical Center West, at 1003 Willow Creek Road, Prescott, AZ 86301 in Yavapai County. The practice phone is (928) 445-2700.

Source: Dmand AI Affiliation Data

Megan Dawn Eppens is affiliated with 1 site of care

Megan Eppens' primary practice is Dignity Health, Yavapai Regional Medical Center West in Prescott, Arizona, part of CommonSpirit Health.

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

Dmand AI tracks the EHR system at Megan Dawn Eppens' practice

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

EHR by site
SiteEHR vendor and product
Dignity Health, Yavapai Regional Medical Center WestAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Megan Eppens practices

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

Megan Dawn Eppens is one of 6,007 family nurse practitioners in Arizona

Family is Megan Eppens' primary specialty in the NPI Registry, under taxonomy code 363LF0000X. Dmand AI has Megan Eppens' licenses on file in 2 states: Arizona and Missouri.

Specialties and state licenses

  • Family nurse practitioner, ArizonaPrimaryLicense AP8766 · taxonomy 363LF0000X
  • Missouri licenseLicense 2011003374

Family nurse practitioners near Megan Eppens

Counts of family nurse practitioners 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

Megan Dawn Eppens' patients have a median age of 75

Across all payers, Dmand AI patient panel data puts Megan Eppens' median patient age at 75, with 69% women.

Megan Eppens' patients across all payers

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

Patient panel by age, all payers

Median age 75

Patient panel by sex, all payers

  • Women69%
  • Men27%

Source: Dmand AI Patient Panel Data

Sources for Megan Dawn Eppens'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 Megan Dawn Eppens

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

What is Megan Dawn Eppens' NPI number?

Megan Dawn Eppens' NPI number is 1316243447. It was assigned on February 8, 2011, and it is active in the NPI Registry.

What does Megan Dawn Eppens specialize in?

Megan Dawn Eppens is a family nurse practitioner in Prescott, Arizona. The primary specialty in the NPI Registry is Family Nurse Practitioner (taxonomy code 363LF0000X).

Where does Megan Dawn Eppens practice?

Megan Eppens practices at 1003 Willow Creek Road, Prescott, AZ 86301. Megan Eppens' primary practice is Dignity Health, Yavapai Regional Medical Center West in Prescott, Arizona, part of CommonSpirit Health.

What is Megan Dawn Eppens' office phone number?

The practice phone on file for Megan Eppens is (928) 445-2700.

What is Megan Dawn Eppens' medical license number?

Megan Eppens holds Arizona license AP8766, one of the licenses on file in 2 states.

Which states has Megan Dawn Eppens been licensed in?

Dmand AI has state licenses on file for Megan Eppens in Arizona and Missouri.

Which hospitals is Megan Dawn Eppens affiliated with?

Megan Eppens practices at Dignity Health, Yavapai Regional Medical Center West in Prescott, Arizona.

How long has Megan Dawn Eppens been practicing?

Megan Eppens graduated from medical school in 2010, 16 years ago.

Selling to family practices?

See family nurse practitioners in Arizona 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)