LACY D OWENS
NPI 1720558430
Counselor in Tulsa, OK
About Lacy D Owens NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LACY D OWENS (NPI 1720558430) is an individual counselor in Tulsa, Oklahoma, licensed in Oklahoma (8784) and active in the NPI registry since November 2018. She is enrolled in Medicare PECOS and is a graduate of Other (2022).
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare and accepts Medicare assignment
Lacy D Owens is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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.
TULSA, OK 74103
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 Lacy Owens's NPI number?
The NPI number for Lacy Owens is 1720558430. It was assigned to this individual provider in the NPPES registry on November 26, 2018.
Where is Lacy Owens located?
Lacy Owens practices at 102 N Denver Ave, Tulsa, OK 74103. The listed phone number is (918) 582-1200.
What is Lacy Owens's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
Is Lacy Owens enrolled in Medicare?
Yes. Lacy Owens is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Lacy Owens was last updated on October 21, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.