SOFIA NEVES-GILCHER MA, LAC
NPI 1235761537
Counselor - Professional in West Caldwell, NJ
About Sofia Neves-gilcher Ma, Lac NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SOFIA NEVES-GILCHER MA, LAC (NPI 1235761537) is an individual professional provider in West Caldwell, New Jersey and active in the NPI registry since February 2020. She is enrolled in Medicare PECOS and is a graduate of Other (2007).
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
Sofia Neves-gilcher Ma, Lac 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 Sofia Neves-gilcher's NPI number?
The NPI number for Sofia Neves-gilcher is 1235761537. It was assigned to this individual provider in the NPPES registry on February 5, 2020.
Where is Sofia Neves-gilcher located?
Sofia Neves-gilcher practices at 175 Fairfield Ave Apt C, West Caldwell, NJ 07006. The listed phone number is (973) 886-8300.
What is Sofia Neves-gilcher's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Sofia Neves-gilcher enrolled in Medicare?
Yes. Sofia Neves-gilcher 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 Sofia Neves-gilcher was last updated on February 5, 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.
