BEN HUMMELL JR. LMFT, LPC
NPI 1376922351
Counselor - Professional in Ashland, OR
About Ben Hummell Jr. Lmft, Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BEN HUMMELL JR. LMFT, LPC (NPI 1376922351) is an individual professional provider in Ashland, Oregon, licensed in Oregon (C3898) and active in the NPI registry since May 2015. He is enrolled in Medicare PECOS, maintains a secondary practice location in Mill Valley, and is a graduate of Other (2012).
NPPES Registry Identity
Specialties & Licenses 2
Secondary Practice Location 1
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
Ben Hummell Jr. Lmft, Lpc 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.
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 Ben Hummell's NPI number?
The NPI number for Ben Hummell is 1376922351. It was assigned to this individual provider in the NPPES registry on May 24, 2015.
Where is Ben Hummell located?
Ben Hummell practices at 149 Clear Creek Dr Unit 102, Ashland, OR 97520. The listed phone number is (541) 201-8115.
What is Ben Hummell's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Ben Hummell enrolled in Medicare?
Yes. Ben Hummell 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 Ben Hummell was last updated on March 17, 2020. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.