KOMAL PANDYA DNP
NPI 1700698412
Nurse Practitioner - Family in Teaneck, NJ
About Komal Pandya Dnp NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KOMAL PANDYA DNP (NPI 1700698412) is an individual family provider in Teaneck, New Jersey, licensed in New Jersey (26NJ15177300) and active in the NPI registry since January 2025. She is enrolled in Medicare PECOS and maintains a secondary practice location in Mountain Lakes.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Komal Pandya Dnp 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 Komal Pandya's NPI number?
The NPI number for Komal Pandya is 1700698412. It was assigned to this individual provider in the NPPES registry on January 21, 2025.
Where is Komal Pandya located?
Komal Pandya practices at 400 Frank W Burr Blvd Ste 22, Teaneck, NJ 07666. The listed phone number is (201) 907-0442.
What is Komal Pandya's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Komal Pandya enrolled in Medicare?
Yes. Komal Pandya is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Komal Pandya was last updated on May 23, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 14 months 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.