KAITLIN E. SMITH LCSW
NPI 1609388867
Social Worker - Clinical in Glastonbury, CT
About Kaitlin E. Smith Lcsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KAITLIN E. SMITH LCSW (NPI 1609388867) is an individual clinical provider in Glastonbury, Connecticut, licensed in Connecticut (11626) and active in the NPI registry since October 2017. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Other Names 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Kaitlin E. Smith Lcsw is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 06033 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Kaitlin Smith's NPI number?
The NPI number for Kaitlin Smith is 1609388867. It was assigned to this individual provider in the NPPES registry on October 27, 2017. The provider is also known as Katie E. Pagel.
Where is Kaitlin Smith located?
Kaitlin Smith practices at 2389 Main St Ste 1, Glastonbury, CT 06033. The listed phone number is (860) 629-0107.
What is Kaitlin Smith's specialty?
The primary specialty registered for this NPI is Social Worker, specializing in Clinical, with taxonomy code 1041C0700X.
Is Kaitlin Smith enrolled in Medicare?
Yes. Kaitlin Smith is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Kaitlin Smith was last updated on April 21, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.