NEHAL LAKDAWALA MEDICAL STUDENT
NPI 1083390793
Student in an Organized Health Care Education/Training Program in Derby, CT
About Nehal Lakdawala Medical Student NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
NEHAL LAKDAWALA MEDICAL STUDENT (NPI 1083390793) is an individual student in an organized health care education/training program in Derby, Connecticut and active in the NPI registry since June 2023. He is enrolled in Medicare PECOS.
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)
Nehal Lakdawala Medical Student is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
DERBY, CT 06418
DERBY, CT 06418
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 Nehal Lakdawala's NPI number?
The NPI number for Nehal Lakdawala is 1083390793. It was assigned to this individual provider in the NPPES registry on June 26, 2023.
Where is Nehal Lakdawala located?
Nehal Lakdawala practices at 130 Division St, Derby, CT 06418. The listed phone number is (203) 732-7327.
What is Nehal Lakdawala's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Nehal Lakdawala enrolled in Medicare?
Yes. Nehal Lakdawala is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Nehal Lakdawala was last updated on March 28, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 16 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.