SCOTT CORSI LCSW
NPI 1891247722
Social Worker - Clinical in Hurricane, UT
About Scott Corsi Lcsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SCOTT CORSI LCSW (NPI 1891247722) is an individual clinical provider in Hurricane, Utah and active in the NPI registry since October 2016. He is enrolled in Medicare PECOS.
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)
Scott Corsi 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 84737 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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.
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 Scott Corsi's NPI number?
The NPI number for Scott Corsi is 1891247722. It was assigned to this individual provider in the NPPES registry on October 26, 2016.
Where is Scott Corsi located?
Scott Corsi practices at 176 S Regional Park Rd, Hurricane, UT 84737. The listed phone number is (435) 986-8568.
What is Scott Corsi's specialty?
The primary specialty registered for this NPI is Social Worker, specializing in Clinical, with taxonomy code 1041C0700X.
Is Scott Corsi enrolled in Medicare?
Yes. Scott Corsi is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Scott Corsi was last updated on January 21, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 months 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.