Megan Aylor, PA-C

  • Manassas, VA
  • Physician assistant
NPI1659262525PAC ID0244725067
Hospital affiliations
2
Medical group
1
State license
1
Year NPI issued
2025
Practice address
8700 Sudley Rd, Manassas, VA 20110
Practice phone
Call (703) 369-8736
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

UVA Health Prince William Medical Center

Hospital · Manassas, Virginia

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

Megan Aylor is a physician assistant in Manassas, Virginia

Megan Aylor practices at UVA Health Prince William Medical Center in Manassas, Virginia, part of University of Virginia.

Megan Aylor's NPI, 1659262525, was assigned on July 10, 2025. Megan Aylor holds Virginia license 0110011125.

NPI and contact details
Medicare PAC ID
0244725067
NPI enumeration date
July 10, 2025
NPI status
Active
Practice phone
(703) 369-8736
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Female
Estimated age
27
Medical school graduation
2025

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

Megan Aylor practices at UVA Health Prince William Medical Center in Manassas, Virginia

Megan Aylor's primary practice is UVA Health Prince William Medical Center, at 8700 Sudley Rd, Manassas, VA 20110 in Manassas City. The practice phone is (703) 369-8736.

Source: Dmand AI Affiliation Data

Megan Aylor is affiliated with 2 sites of care and 1 medical group

Megan Aylor's primary practice is UVA Health Prince William Medical Center in Manassas, Virginia, part of University of Virginia. Megan Aylor is also affiliated with UVA Health Haymarket Medical Center. The medical group on file is Emergency Medicine Physicians (EMP).

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

Dmand AI tracks the EHR system at Megan Aylor's practice

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

EHR by site
SiteEHR vendor and product
UVA Health Prince William Medical CenterAvailable with a free account
+1 more affiliated siteAvailable 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 Aylor practices

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

Megan Aylor is one of 3,636 physician assistants in Virginia

Physician assistant is Megan Aylor's primary specialty in the NPI Registry, under taxonomy code 363A00000X. Megan Aylor is licensed in Virginia.

Specialties and state licenses

  • Physician assistant, VirginiaPrimaryLicense 0110011125 · taxonomy 363A00000X

Physician assistants near Megan Aylor

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

Megan Aylor's patients have a median age of 37

Across all payers, Dmand AI patient panel data puts Megan Aylor's median patient age at 37, with 61% women.

Megan Aylor's patients across all payers

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

Patient panel by age, all payers

Median age 37

Patient panel by sex, all payers

  • Women61%
  • Men39%

Source: Dmand AI Patient Panel Data

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

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 Aylor's NPI number?

Megan Aylor's NPI number is 1659262525. It was assigned on July 10, 2025, and it is active in the NPI Registry.

What does Megan Aylor specialize in?

Megan Aylor is a physician assistant in Manassas, Virginia. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Megan Aylor practice?

Megan Aylor practices at 8700 Sudley Rd, Manassas, VA 20110. Megan Aylor's primary practice is UVA Health Prince William Medical Center in Manassas, Virginia, part of University of Virginia.

What is Megan Aylor's office phone number?

The practice phone on file for Megan Aylor is (703) 369-8736.

What is Megan Aylor's medical license number?

Megan Aylor holds Virginia license 0110011125.

Which hospitals is Megan Aylor affiliated with?

Megan Aylor practices at UVA Health Prince William Medical Center in Manassas, Virginia. Megan Aylor is also affiliated with UVA Health Haymarket Medical Center.

What medical group is Megan Aylor part of?

Megan Aylor is linked to Emergency Medicine Physicians (EMP).

How long has Megan Aylor been practicing?

Megan Aylor graduated from medical school in 2025, 1 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)