DR. LAVANYA JYOTHI GUNNAM MBBS
NPI 1184358749
Student in an Organized Health Care Education/Training Program in Summit, NJ
About Dr. Lavanya Jyothi Gunnam Mbbs NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. LAVANYA JYOTHI GUNNAM MBBS (NPI 1184358749) is an individual student in an organized health care education/training program in Summit, New Jersey and active in the NPI registry since July 2022. She 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)
Dr. Lavanya Jyothi Gunnam Mbbs 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.
SUMMIT, NJ 07901
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 Lavanya Jyothi Gunnam's NPI number?
The NPI number for Lavanya Jyothi Gunnam is 1184358749. It was assigned to this individual provider in the NPPES registry on July 11, 2022.
Where is Lavanya Jyothi Gunnam located?
Lavanya Jyothi Gunnam practices at 99 Beauvoir Ave, Summit, NJ 07901. The listed phone number is (908) 522-2000.
What is Lavanya Jyothi Gunnam's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Lavanya Jyothi Gunnam enrolled in Medicare?
Yes. Lavanya Jyothi Gunnam is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Lavanya Jyothi Gunnam was last updated on July 11, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.