KASEN DANAE ANDERSON LPC
NPI 1265025167
Counselor - Professional in Overland Park, KS
About Kasen Danae Anderson Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KASEN DANAE ANDERSON LPC (NPI 1265025167) is an individual professional provider in Overland Park, Kansas, licensed in Texas (80983) and active in the NPI registry since February 2021.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Accepted Insurance
Other Providers at the Same Location NPPES 4
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
OVERLAND PARK, KS 66210
OVERLAND PARK, KS 66210
OVERLAND PARK, KS 66210
OVERLAND PARK, KS 66210
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 Kasen Anderson's NPI number?
The NPI number for Kasen Anderson is 1265025167. It was assigned to this individual provider in the NPPES registry on February 11, 2021. The provider is also known as Kasen Danae Keller Lpc.
Where is Kasen Anderson located?
Kasen Anderson practices at 9225 Indian Creek Pkwy Ste 750, Overland Park, KS 66210. The listed phone number is (816) 506-3819.
What is Kasen Anderson's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
What insurance does Kasen Anderson accept?
Health plans from Anthem Blue Cross and Blue Shield, Blue Cross and Blue Shield of Kansas City, Oscar Insurance Company, Providence Health Plan and UnitedHealthcare list Kasen Anderson 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 Kasen Anderson was last updated on January 3, 2024. 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.