Alex J. Langton, PA-C

  • Phoenix, AZ
  • Physician assistant
NPI1518502913PAC ID0749617959
Medicare patients, 2024
122
Part D claims, 2024
100
MIPS score, 2024
98
Hospital affiliations
2
Medical groups
4
Practice address
5777 East Mayo Boulevard, Phoenix, AZ 85054
Practice phone
Call (480) 342-4201
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Mayo Clinic Hospital - Phoenix

Hospital · Phoenix, Arizona

See all 6 affiliations

Find Alex Langton'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

Alex J. Langton is a physician assistant in Phoenix, Arizona

Alex Langton practices at Mayo Clinic Hospital - Phoenix in Phoenix, Arizona, part of Mayo Clinic.

Alex Langton's NPI, 1518502913, was assigned on November 10, 2019. Alex Langton holds Arizona license 11309.

NPI and contact details
Medicare PAC ID
0749617959
NPI enumeration date
November 10, 2019
NPI status
Active
Accepts Medicare assignment
Yes
Practice phone
(480) 342-4201
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
33
Medical school graduation
2019

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

Alex J. Langton practices at Mayo Clinic Hospital - Phoenix in Phoenix, Arizona

Alex Langton's primary practice is Mayo Clinic Hospital - Phoenix, at 5777 East Mayo Boulevard, Phoenix, AZ 85054 in Maricopa County. The practice phone is (480) 342-4201.

Source: Dmand AI Affiliation Data

Alex J. Langton is affiliated with 2 sites of care and 4 medical groups

Alex Langton's primary practice is Mayo Clinic Hospital - Phoenix in Phoenix, Arizona, part of Mayo Clinic. Alex Langton is also affiliated with MaineHealth Maine Medical Center. The medical group on file is Mayo Clinic Arizona. Dmand AI also links Alex Langton to 3 more medical groups, each named with a free account.

See all 6 affiliations for Alex Langton

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

Dmand AI tracks the EHR system at Alex J. Langton's practice

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

EHR by site
SiteEHR vendor and product
Mayo Clinic Hospital - PhoenixAvailable with a free account
+1 more site and 3 medical groupsAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Alex Langton practices

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

Alex J. Langton is one of 2,965 physician assistants in Arizona

Physician assistant is Alex Langton's primary specialty in the NPI Registry, under taxonomy code 363A00000X. Dmand AI has Alex Langton's licenses on file in 2 states: Arizona and Maine.

Specialties and state licenses

  • Physician assistant, ArizonaPrimaryLicense 11309 · taxonomy 363A00000X
  • Medical physician assistant, MaineLicense PA2006 · taxonomy 363AM0700X

Physician assistants near Alex Langton

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

Alex J. Langton treated 122 Medicare patients in 2024, average age 77

CMS counts 122 Medicare patients who saw Alex Langton in 2024. The largest group is 75 to 84, with 44 patients. 75% of them have high blood pressure, and 68% have high cholesterol. 35% are also on Medicaid. Their average risk score is 2.44, where 1.00 is the Medicare average, so they are sicker than most Medicare patients.

Across all payers, Dmand AI patient panel data puts Alex Langton's median patient age at 70, with 46% women.

Medicare patients, 2024122
Average age77
Average risk score2.44
Also on Medicaid35%

Alex Langton's Medicare patients by age, 2024

Alex Langton's Medicare patients by sex, 2024

  • Women7057%
  • Men5243%

Chronic conditions among Alex Langton's Medicare patients, 2024

  1. High blood pressure75%
  2. High cholesterol68%
  3. Mood disorders58%
  4. Depression53%
  5. Anxiety52%
  6. Arthritis51%
  7. Heart failure48%
  8. Chronic kidney disease46%

Share of Medicare patients with each condition. A patient can have several.

Alex Langton's patients across all payers

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

Patient panel by age, all payers

Median age 70

Patient panel by sex, all payers

  • Women46%
  • Men53%

Sources: Dmand AI Patient Panel Data; and Medicare Physician & Other Practitioners - by Provider (CMS), 2024 data

Alex J. Langton wrote 100 Medicare Part D claims in 2024

In 2024, Alex Langton wrote 100 Medicare Part D claims for 48 patients. 88% of them were for generic drugs.

Part D claims, 2024100
Part D patients48

Alex Langton's Part D claims by kind of drug, 2024

  • Generic88 claims88%
  • Brand-name12 claims12%

Drug classes CMS tracks in Alex Langton's Part D claims, 2024

  • Antibiotics16%16 of 100 claims

Share of all Part D claims for each drug class CMS reports on. Classes with no claims are left out.

Source: Medicare Part D Prescribers - by Provider (CMS), 2024 data

Alex J. Langton scored 98 out of 100 in Medicare's MIPS program for 2024

CMS publishes a Merit-based Incentive Payment System (MIPS) score of 98 out of 100 for Alex Langton for performance year 2024, reported through an alternative payment model (APM). Alex Langton accepts Medicare assignment, so Medicare's approved amount is taken as full payment.

Accepts Medicare assignment
Yes

Alex Langton's MIPS scores, performance year 2024

  • 98of 100Final score
  • 83.3of 100Quality
  • 100of 100Promoting Interoperability
  • 40of 100Improvement Activities

Each score is out of 100. The final score weighs the categories CMS scored for this clinician.

Sources: Doctors and Clinicians National Downloadable File (CMS); and Clinician Public Reporting: Overall MIPS Performance (CMS), 2024 data, released September 10, 2026

For MedTech and pharma teams

Find physician assistants like Alex Langton by procedure volume and prescribing

Filter 7.4M+ HCPs by Medicare procedures, Part D drugs and Open Payments history, then reach them with verified contacts in one login.

Sources for Alex J. Langton'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 DataMedicare Physician & Other Practitioners - by Provider (CMS) (opens in a new tab)
Part D prescribingMedicare Part D Prescribers - by Provider (CMS) (opens in a new tab)
MIPS scores, telehealth, assignment and procedure percentilesDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)Clinician Public Reporting: Overall MIPS Performance (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 Alex J. Langton

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

What is Alex J. Langton's NPI number?

Alex J. Langton's NPI number is 1518502913. It was assigned on November 10, 2019, and it is active in the NPI Registry.

What does Alex J. Langton specialize in?

Alex J. Langton is a physician assistant in Phoenix, Arizona. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Alex J. Langton practice?

Alex Langton practices at 5777 East Mayo Boulevard, Phoenix, AZ 85054. Alex Langton's primary practice is Mayo Clinic Hospital - Phoenix in Phoenix, Arizona, part of Mayo Clinic. Dmand AI also links Alex Langton to 3 medical groups.

What is Alex J. Langton's office phone number?

The practice phone on file for Alex Langton is (480) 342-4201.

What is Alex J. Langton's medical license number?

Alex Langton holds Arizona license 11309, one of the licenses on file in 2 states.

Which states has Alex J. Langton been licensed in?

Dmand AI has state licenses on file for Alex Langton in Arizona and Maine.

Which hospitals is Alex J. Langton affiliated with?

Alex Langton practices at Mayo Clinic Hospital - Phoenix in Phoenix, Arizona. Alex Langton is also affiliated with MaineHealth Maine Medical Center.

What medical group is Alex J. Langton part of?

Alex Langton is linked to Mayo Clinic Arizona. Dmand AI links Alex Langton to 3 more medical groups.

Does Alex J. Langton accept Medicare?

Yes. CMS lists Alex Langton as accepting Medicare assignment.

What is Alex J. Langton's MIPS score?

Alex Langton's MIPS final score for performance year 2024 is 98 out of 100, reported through an alternative payment model (APM).

How many Medicare patients does Alex J. Langton see?

CMS counts 122 Medicare patients who saw Alex Langton in 2024, with an average age of 77.

How long has Alex J. Langton been practicing?

Alex Langton graduated from medical school in 2019, 7 years ago.

Selling to physician assistant practices?

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