RILEY HARMS
NPI 1649782384
Physician Assistant - Surgical in Tampa, FL
About Riley Harms NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
RILEY HARMS (NPI 1649782384) is an individual surgical provider in Tampa, Florida and active in the NPI registry since November 2017. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Riley Harms is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 4
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
TAMPA, FL 33619
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 Riley Harms's NPI number?
The NPI number for Riley Harms is 1649782384. It was assigned to this individual provider in the NPPES registry on November 3, 2017.
Where is Riley Harms located?
Riley Harms practices at 10740 Palm River Rd Ste 300, Tampa, FL 33619. The listed phone number is (813) 651-3300.
What is Riley Harms's specialty?
The primary specialty registered for this NPI is Physician Assistant, specializing in Surgical, with taxonomy code 363AS0400X.
Is Riley Harms enrolled in Medicare?
Yes. Riley Harms is registered in the Medicare PECOS enrollment system.
What insurance does Riley Harms accept?
Health plans from AvMed list Riley Harms as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Riley Harms was last updated on November 3, 2017. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 years 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.