PETYA C YANEVA PT
NPI 1326331265
Physical Therapist in Lakewood, NJ
About Petya C Yaneva Pt NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
PETYA C YANEVA PT (NPI 1326331265) is an individual physical therapist in Lakewood, New Jersey, licensed in Pennsylvania (021032) and active in the NPI registry since May 2011.
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 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Petya Yaneva's NPI number?
The NPI number for Petya Yaneva is 1326331265. It was assigned to this individual provider in the NPPES registry on May 25, 2011.
Where is Petya Yaneva located?
Petya Yaneva practices at 685 River Ave, Lakewood, NJ 08701. The listed phone number is (215) 968-4650.
What is Petya Yaneva'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 Petya Yaneva was last updated on December 6, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.