BRIAN ANDREW LINGLE MSW
NPI 1821771684
Counselor - Mental Health in Skandia, MI

Active since August 09, 2023
630 DALTON RD, SKANDIA, MI 49885(906) 361-3559 Get Directions Write a Review

NPPES record last updated: August 9, 2023. Verified against the NPPES registry weekly; last sync: August 02, 2026.

About Brian Andrew Lingle Msw NPPES

Official registry information on file with the National Plan and Provider Enumeration System.

BRIAN ANDREW LINGLE MSW (NPI 1821771684) is an individual mental health provider in Skandia, Michigan and active in the NPI registry since August 2023.

NPPES Registry Identity

NPI1821771684
Entity TypeIndividualMale
Primary Taxonomy101YM0800X
Provider Legal NameBRIAN ANDREW LINGLECredential: MSW
Location Address630 DALTON RDSkandia, MI 49885-9403
Mailing Address630 Dalton RdSkandia, MI 49885-9403 · (906) 361-3559
Sole ProprietorYes
Enumeration DateAugust 9, 2023
NPPES CertifiedAugust 9, 2023
NPI 1821771684 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyCounselor · Mental HealthBehavioral Health & Social Service Providers
Taxonomy Code101YM0800X
630 DALTON RD, Skandia, MI 49885

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 Lingle's NPI number?

The NPI number for Brian Lingle is 1821771684. It was assigned to this individual provider in the NPPES registry on August 9, 2023.

Where is Brian Lingle located?

Brian Lingle practices at 630 Dalton Rd, Skandia, MI 49885. The listed phone number is (906) 361-3559.

What is Brian Lingle's specialty?

The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.

When was this NPI record last updated?

The NPPES record for Brian Lingle was last updated on August 9, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.