LEXALYNN AVILANES
NPI 1245867753
Physical Therapist in Bel Air, MD
About Lexalynn Avilanes NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LEXALYNN AVILANES (NPI 1245867753) is an individual physical therapist in Bel Air, Maryland, licensed in Maryland (26847) and active in the NPI registry since March 2020. She maintains a secondary practice location in Bel Air.
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.
Secondary Practice Location 1
Group Practice 1
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 Lexalynn Avilanes's NPI number?
The NPI number for Lexalynn Avilanes is 1245867753. It was assigned to this individual provider in the NPPES registry on March 25, 2020.
Where is Lexalynn Avilanes located?
Lexalynn Avilanes practices at 112 Seevue Ct Apt B, Bel Air, MD 21014. The listed phone number is (443) 803-3310.
What is Lexalynn Avilanes'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 Lexalynn Avilanes was last updated on March 25, 2020. 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.