GIANNIL JARAMILLO LCSW
NPI 1053181578
Social Worker - Clinical in Teaneck, NJ
About Giannil Jaramillo Lcsw NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
GIANNIL JARAMILLO LCSW (NPI 1053181578) is an individual clinical provider in Teaneck, New Jersey, licensed in New Jersey (44SC06281900) and active in the NPI registry since January 2024. She is enrolled in Medicare PECOS and is a graduate of Other (2012).
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)
Giannil Jaramillo 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 07666 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Giannil Jaramillo's NPI number?
The NPI number for Giannil Jaramillo is 1053181578. It was assigned to this individual provider in the NPPES registry on January 5, 2024.
Where is Giannil Jaramillo located?
Giannil Jaramillo practices at 100 Elizabeth Ave, Teaneck, NJ 07666. The listed phone number is (551) 223-1222.
What is Giannil Jaramillo's specialty?
The primary specialty registered for this NPI is Social Worker, specializing in Clinical, with taxonomy code 1041C0700X.
Is Giannil Jaramillo enrolled in Medicare?
Yes. Giannil Jaramillo is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Giannil Jaramillo was last updated on January 10, 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.