MS. CHASE B SPIEGEL MSW, CMSW, LMSW
NPI 1275648198
Social Worker in Memphis, TN
About Ms. Chase B Spiegel Msw, Cmsw, Lmsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MS. CHASE B SPIEGEL MSW, CMSW, LMSW (NPI 1275648198) is an individual social worker in Memphis, Tennessee, licensed in Tennessee (6371) and active in the NPI registry since August 2006. She is enrolled in Medicare PECOS and is a graduate of Michigan State University College Of Human Medicine (1992).
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 and accepts Medicare assignment
Ms. Chase B Spiegel Msw, Cmsw, Lmsw is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Chase Spiegel's NPI number?
The NPI number for Chase Spiegel is 1275648198. It was assigned to this individual provider in the NPPES registry on August 20, 2006.
Where is Chase Spiegel located?
Chase Spiegel practices at 1716 Autumn Ave, Memphis, TN 38112. The listed phone number is (901) 206-4131.
What is Chase Spiegel's specialty?
The primary specialty registered for this NPI is Social Worker with taxonomy code 104100000X.
Is Chase Spiegel enrolled in Medicare?
Yes. Chase Spiegel is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Chase Spiegel was last updated on October 16, 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.