ARIANNA PARKHIDEH
NPI 1831032440
Student in an Organized Health Care Education/Training Program in Indianapolis, IN
About Arianna Parkhideh NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ARIANNA PARKHIDEH (NPI 1831032440) is an individual student in an organized health care education/training program in Indianapolis, Indiana 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)
Arianna Parkhideh is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 2
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
INDIANAPOLIS, IN 46202
INDIANAPOLIS, IN 46202
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 Arianna Parkhideh's NPI number?
The NPI number for Arianna Parkhideh is 1831032440. It was assigned to this individual provider in the NPPES registry on April 10, 2026.
Where is Arianna Parkhideh located?
Arianna Parkhideh practices at 507 Riley Hospital Drive 5837, Indianapolis, IN 46202. The listed phone number is (317) 948-0003.
What is Arianna Parkhideh's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Arianna Parkhideh enrolled in Medicare?
Yes. Arianna Parkhideh is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Arianna Parkhideh was last updated on April 10, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 months 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.