LUREE BENJAMIN
NPI 1417691122
Marriage & Family Therapist in Oxford, NC
About Luree Benjamin NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LUREE BENJAMIN (NPI 1417691122) is an individual marriage & family therapist in Oxford, North Carolina, licensed in North Carolina (12395A) and active in the NPI registry since April 2022. She is enrolled in Medicare PECOS.
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)
Luree Benjamin 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 Luree Benjamin's NPI number?
The NPI number for Luree Benjamin is 1417691122. It was assigned to this individual provider in the NPPES registry on April 27, 2022.
Where is Luree Benjamin located?
Luree Benjamin practices at 5129 Stone Lane, Oxford, NC 27565. The listed phone number is (919) 760-6417.
What is Luree Benjamin's specialty?
The primary specialty registered for this NPI is Marriage & Family Therapist with taxonomy code 106H00000X.
Is Luree Benjamin enrolled in Medicare?
Yes. Luree Benjamin is registered in the Medicare PECOS enrollment system.
What insurance does Luree Benjamin accept?
Health plans from Blue Cross and Blue Shield of NC, Oscar Health Plan of North Carolina, Inc and UnitedHealthcare list Luree Benjamin 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 Luree Benjamin was last updated on April 27, 2022. 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.