DR. FREDERICK SAMUEL BENNER PH.D., LPC
NPI 1265463616
Counselor - Professional in Lewistown, PA
About Dr. Frederick Samuel Benner Ph.d., Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. FREDERICK SAMUEL BENNER PH.D., LPC (NPI 1265463616) is an individual professional provider in Lewistown, Pennsylvania, licensed in Pennsylvania (PC003860) and active in the NPI registry since July 2006. He is enrolled in Medicare PECOS and is a graduate of Other (2007).
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 (PECOS)
Dr. Frederick Samuel Benner Ph.d., Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 2
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
LEWISTOWN, PA 17044
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 Frederick Benner's NPI number?
The NPI number for Frederick Benner is 1265463616. It was assigned to this individual provider in the NPPES registry on July 5, 2006.
Where is Frederick Benner located?
Frederick Benner practices at 27 N Brown St, Lewistown, PA 17044. The listed phone number is (717) 242-1428.
What is Frederick Benner's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Frederick Benner enrolled in Medicare?
Yes. Frederick Benner is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Frederick Benner was last updated on July 17, 2014. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 12 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.