AARON SAEZ LSW
NPI 1720619372
Counselor - Mental Health in Columbus, OH
About Aaron Saez Lsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
AARON SAEZ LSW (NPI 1720619372) is an individual mental health provider in Columbus, Ohio, licensed in Ohio (I.2304857) and active in the NPI registry since February 2020. He is enrolled in Medicare PECOS and is a graduate of Other (2020).
NPPES Registry Identity
Specialties & Licenses 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)
Aaron Saez Lsw 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 Aaron Saez's NPI number?
The NPI number for Aaron Saez is 1720619372. It was assigned to this individual provider in the NPPES registry on February 3, 2020.
Where is Aaron Saez located?
Aaron Saez practices at 230 Fenway Rd, Columbus, OH 43214. The listed phone number is (614) 389-2180.
What is Aaron Saez's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.
Is Aaron Saez enrolled in Medicare?
Yes. Aaron Saez is registered in the Medicare PECOS enrollment system.
What insurance does Aaron Saez accept?
Health plans from CareSource, MedMutual, Oscar Health Insurance, Oscar Insurance Corporation of Ohio and UnitedHealthcare list Aaron Saez 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 Aaron Saez was last updated on March 4, 2024. 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.