ALEXA L. ROSETTA
NPI 1396682134
Physician Assistant in Phoenix, AZ
About Alexa L. Rosetta NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ALEXA L. ROSETTA (NPI 1396682134) is an individual physician assistant in Phoenix, Arizona and active in the NPI registry since April 2026. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Alexa L. Rosetta is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 85014 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Other Providers at the Same Location NPPES 11
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
PHOENIX, AZ 85014
Frequently Asked Questions NPPES & CMS
Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.
What is Alexa Rosetta's NPI number?
The NPI number for Alexa Rosetta is 1396682134. It was assigned to this individual provider in the NPPES registry on April 30, 2026.
Where is Alexa Rosetta located?
Alexa Rosetta practices at 1313 E Osborn Rd Ste 150, Phoenix, AZ 85014. The listed phone number is (602) 264-4431.
What is Alexa Rosetta's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Alexa Rosetta enrolled in Medicare?
Yes. Alexa Rosetta is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Alexa Rosetta was last updated on July 30, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 41 days ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.