LOUDONNA HAUMPO LCSW
NPI 1871973859
Counselor - Mental Health in Yukon, OK
About Loudonna Haumpo Lcsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LOUDONNA HAUMPO LCSW (NPI 1871973859) is an individual mental health provider in Yukon, Oklahoma and active in the NPI registry since June 2015. She is enrolled in Medicare PECOS and is a graduate of Other (2012).
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Loudonna Haumpo Lcsw is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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 Loudonna Haumpo's NPI number?
The NPI number for Loudonna Haumpo is 1871973859. It was assigned to this individual provider in the NPPES registry on June 4, 2015.
Where is Loudonna Haumpo located?
Loudonna Haumpo practices at 101 Lochwood Cir, Yukon, OK 73099. The listed phone number is (405) 570-0470.
What is Loudonna Haumpo's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.
Is Loudonna Haumpo enrolled in Medicare?
Yes. Loudonna Haumpo is registered in the Medicare PECOS enrollment system.
What insurance does Loudonna Haumpo accept?
Health plans from Blue Cross and Blue Shield of Oklahoma, Medica and Mending Health list Loudonna Haumpo 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 Loudonna Haumpo was last updated on September 30, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.