BRIAN P. HEINZ LPCC
NPI 1760624316
Counselor in Mentor, OH
About Brian P. Heinz Lpcc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRIAN P. HEINZ LPCC (NPI 1760624316) is an individual counselor in Mentor, Ohio, licensed in Ohio (E.2102654) and active in the NPI registry since March 2009. He 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)
Brian P. Heinz Lpcc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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.
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 Brian Heinz's NPI number?
The NPI number for Brian Heinz is 1760624316. It was assigned to this individual provider in the NPPES registry on March 28, 2009.
Where is Brian Heinz located?
Brian Heinz practices at 7232 Justin Way, Mentor, OH 44060. The listed phone number is (440) 578-8200.
What is Brian Heinz's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
Is Brian Heinz enrolled in Medicare?
Yes. Brian Heinz is registered in the Medicare PECOS enrollment system.
What insurance does Brian Heinz accept?
Health plans from CareSource list Brian Heinz 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 Brian Heinz was last updated on February 24, 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.