BRIAN GESE
NPI 1831507102
Physical Therapist in Prosser, WA
About Brian Gese NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRIAN GESE (NPI 1831507102) is an individual physical therapist in Prosser, Washington, licensed in Washington (PT60477464) and active in the NPI registry since July 2014.
NPPES Registry Identity
Specialties & Licenses
- Diagnose and manage movement dysfunction and enhance physical and functional abilities.
- Restore, maintain, and promote not only optimal physical function but optimal wellness and fitness and optimal quality of life as it relates to movement and health.
- Prevent the onset, symptoms, and progression of impairments, functional limitations, and disabilities that may result from diseases, disorders, conditions, or injuries.
- Treat conditions of the musculoskeletal, neuromuscular, cardiovascular, pulmonary, and/or integumentary systems.
- Address the negative effects attributable to unique personal and environmental factors as they relate to human performance.
Other Providers at the Same Location NPPES 15
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
PROSSER, WA 99350
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 Brian Gese's NPI number?
The NPI number for Brian Gese is 1831507102. It was assigned to this individual provider in the NPPES registry on July 30, 2014.
Where is Brian Gese located?
Brian Gese practices at 326 Chardonnay Ave, Prosser, WA 99350. The listed phone number is (509) 786-6626.
What is Brian Gese's specialty?
The primary specialty registered for this NPI is Physical Therapist with taxonomy code 225100000X.
When was this NPI record last updated?
The NPPES record for Brian Gese was last updated on July 30, 2014. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 12 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.