JEFFREY SLOCUM
NPI 1942733803
Counselor - Professional in Uncasville, CT

Active since April 07, 2017
262 ROUTE 163 APT 2, UNCASVILLE, CT 06382(860) 447-1717 Get Directions Write a Review

NPPES record last updated: April 7, 2017. Verified against the NPPES registry weekly; last sync: August 02, 2026.

About Jeffrey Slocum NPPES

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

JEFFREY SLOCUM (NPI 1942733803) is an individual professional provider in Uncasville, Connecticut, licensed in Connecticut (003157) and active in the NPI registry since April 2017.

NPPES Registry Identity

NPI1942733803
Entity TypeIndividualMale
Primary Taxonomy101YP2500X
Provider Legal NameJEFFREY SLOCUM
Location Address262 ROUTE 163 APT 2Uncasville, CT 06382-2118
Mailing Address262 Route 163 Apt 2Uncasville, CT 06382-2118
Sole ProprietorYes
Enumeration DateApril 7, 2017
NPI 1942733803 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyCounselor · ProfessionalBehavioral Health & Social Service Providers
Taxonomy Code101YP2500X
License Licensed in CT · 003157
262 ROUTE 163 APT 2, Uncasville, CT 06382

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

The NPI number for Jeffrey Slocum is 1942733803. It was assigned to this individual provider in the NPPES registry on April 7, 2017.

Where is Jeffrey Slocum located?

Jeffrey Slocum practices at 262 Route 163 Apt 2, Uncasville, CT 06382. The listed phone number is (860) 447-1717.

What is Jeffrey Slocum's specialty?

The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.

When was this NPI record last updated?

The NPPES record for Jeffrey Slocum was last updated on April 7, 2017. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 9 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.