MRS. AIMEE E FASS LCMHC
NPI 1417205634
Counselor - Mental Health in Layton, UT
About Mrs. Aimee E Fass Lcmhc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MRS. AIMEE E FASS LCMHC (NPI 1417205634) is an individual mental health provider in Layton, Utah, licensed in Utah (7775888-6009) and active in the NPI registry since August 2012. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 2
Accepted Insurance
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Mrs. Aimee E Fass Lcmhc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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 Aimee Fass's NPI number?
The NPI number for Aimee Fass is 1417205634. It was assigned to this individual provider in the NPPES registry on August 20, 2012.
Where is Aimee Fass located?
Aimee Fass practices at 920 Heritage Park Blvd Ste 200H, Layton, UT 84041. The listed phone number is (385) 393-4804.
What is Aimee Fass's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.
Is Aimee Fass enrolled in Medicare?
Yes. Aimee Fass is registered in the Medicare PECOS enrollment system.
What insurance does Aimee Fass accept?
Health plans from BridgeSpan Health Company and Regence BlueCross BlueShield of Utah list Aimee Fass as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Aimee Fass was last updated on January 29, 2020. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.