Evan Thomas Moore, PA-C

  • Fredericksburg, VA
  • Physician assistant
NPI1629794417
Affiliated sites
1
Medical groups
2
State license
1
Year NPI issued
2022
Practice address
15 S Gateway Dr Ste 101, Fredericksburg, VA 22406
Practice phone
Call (540) 368-5603
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Nextcare Urgent Care

Urgent Care - Additional Location · Fredericksburg, Virginia

See all 3 affiliations

Find Evan Moore'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

Evan Thomas Moore is a physician assistant in Fredericksburg, Virginia

Evan Moore practices at Nextcare Urgent Care in Fredericksburg, Virginia.

Evan Moore's NPI, 1629794417, was assigned on October 13, 2022.

NPI and contact details
NPI enumeration date
October 13, 2022
NPI status
Active
Practice phone
(540) 368-5603
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
30
Medical school graduation
2022

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

Evan Thomas Moore practices at Nextcare Urgent Care in Fredericksburg, Virginia

Evan Moore's primary practice is Nextcare Urgent Care, at 15 S Gateway Dr Ste 101, Fredericksburg, VA 22406. The practice phone is (540) 368-5603.

  • Nextcare Urgent Care
    15 S Gateway Dr Ste 101, Fredericksburg, VA 22406Phone(540) 368-5603

Source: Dmand AI Affiliation Data

Evan Thomas Moore is affiliated with 1 site of care and 2 medical groups

Evan Moore's primary practice is Nextcare Urgent Care in Fredericksburg, Virginia. The medical group on file is NextCare Urgent Care. Dmand AI also links Evan Moore to 1 more medical group, named with a free account.

Nextcare Urgent CareUrgent Care - Additional Location · Fredericksburg, VirginiaPrimary
NextCare Urgent CarePrimary care group, Tempe, AZ1 medical groupName with a free account
See all 3 affiliations for Evan Moore

Source: Dmand AI Affiliation Data

Dmand AI tracks the EHR system at Evan Thomas Moore's practice

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

EHR by site
SiteEHR vendor and product
Nextcare Urgent CareAvailable 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 site where Evan Moore 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.

Evan Thomas Moore is one of 3,636 physician assistants in Virginia

Physician assistant is Evan Moore's primary specialty in the NPI Registry, under taxonomy code 363A00000X.

Specialties and state licenses

  • Physician assistantPrimarytaxonomy 363A00000X

Physician assistants near Evan Moore

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

Evan Thomas Moore's patients have a median age of 10

Across all payers, Dmand AI patient panel data puts Evan Moore's median patient age at 10, with 42% women.

Evan Moore's patients across all payers

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

Patient panel by age, all payers

Median age 10

Patient panel by sex, all payers

  • Women42%
  • Men58%

Source: Dmand AI Patient Panel Data

Sources for Evan Thomas Moore'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 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 Evan Thomas Moore

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

What is Evan Thomas Moore's NPI number?

Evan Thomas Moore's NPI number is 1629794417. It was assigned on October 13, 2022, and it is active in the NPI Registry.

What does Evan Thomas Moore specialize in?

Evan Thomas Moore is a physician assistant in Fredericksburg, Virginia. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Evan Thomas Moore practice?

Evan Moore practices at 15 S Gateway Dr Ste 101, Fredericksburg, VA 22406. Evan Moore's primary practice is Nextcare Urgent Care in Fredericksburg, Virginia. Dmand AI also links Evan Moore to 1 medical group.

What is Evan Thomas Moore's office phone number?

The practice phone on file for Evan Moore is (540) 368-5603.

What medical group is Evan Thomas Moore part of?

Evan Moore is linked to NextCare Urgent Care. Dmand AI links Evan Moore to 1 more medical group.

How long has Evan Thomas Moore been practicing?

Evan Moore graduated from medical school in 2022, 4 years ago.

Selling to physician assistant practices?

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