SHELBY RHEA ALMANZA OTR/L
NPI 1932768629
Occupational Therapist - Physical Rehabilitation in Midwest City, OK
About Shelby Rhea Almanza Otr/l NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SHELBY RHEA ALMANZA OTR/L (NPI 1932768629) is an individual physical rehabilitation provider in Midwest City, Oklahoma, licensed in Oklahoma (5322) and active in the NPI registry since June 2019.
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
Medicare Quality Performance CMS QPP · MIPS
Performance in the CMS Quality Payment Program: the MIPS final score across four weighted categories, and the individual quality measures reported to Medicare.
Other Providers at the Same Location NPPES 7
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
MIDWEST CITY, OK 73110
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 Shelby Almanza's NPI number?
The NPI number for Shelby Almanza is 1932768629. It was assigned to this individual provider in the NPPES registry on June 6, 2019.
Where is Shelby Almanza located?
Shelby Almanza practices at 351 N Air Depot Blvd Ste X, Midwest City, OK 73110. The listed phone number is (405) 732-1766.
What is Shelby Almanza's specialty?
The primary specialty registered for this NPI is Occupational Therapist, specializing in Physical Rehabilitation, with taxonomy code 225XP0019X.
What insurance does Shelby Almanza accept?
Health plans from Blue Cross and Blue Shield of Texas list Shelby Almanza 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 Shelby Almanza was last updated on June 6, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.