DR. LYCHENE NMANKAN WOLO SAAH LPC
NPI 1083206528
Counselor - Professional in Fort Worth, TX
About Dr. Lychene Nmankan Wolo Saah Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. LYCHENE NMANKAN WOLO SAAH LPC (NPI 1083206528) is an individual professional provider in Fort Worth, Texas, licensed in Texas (80274) and active in the NPI registry since February 2021. She maintains a secondary practice location in Houston.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Accepted Insurance
Other Providers at the Same Location NPPES 17
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
FORT WORTH, TX 76107
FORT WORTH, TX 76107
FORT WORTH, TX 76107
FORT WORTH, TX 76107
FORT WORTH, TX 76107
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 Lychene Saah's NPI number?
The NPI number for Lychene Saah is 1083206528. It was assigned to this individual provider in the NPPES registry on February 5, 2021.
Where is Lychene Saah located?
Lychene Saah practices at 1300 S University Dr Ste 306, Fort Worth, TX 76107. The listed phone number is (844) 824-8775.
What is Lychene Saah's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
What insurance does Lychene Saah accept?
Health plans from Blue Cross and Blue Shield of Texas, Imperial Insurance Companies, Inc., Oscar Insurance Company and UnitedHealthcare list Lychene Saah 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 Lychene Saah was last updated on September 19, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.