DR. SINDHU VIKASH M.D.
NPI 1770164097
Student in an Organized Health Care Education/Training Program in Bronx, NY
About Dr. Sindhu Vikash M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. SINDHU VIKASH M.D. (NPI 1770164097) is an individual student in an organized health care education/training program in Bronx, New York and active in the NPI registry since April 2021. 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. Sindhu Vikash M.d. is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 4
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
BRONX, NY 10461
BRONX, NY 10461
BRONX, NY 10461
BRONX, NY 10461
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 Sindhu Vikash's NPI number?
The NPI number for Sindhu Vikash is 1770164097. It was assigned to this individual provider in the NPPES registry on April 19, 2021.
Where is Sindhu Vikash located?
Sindhu Vikash practices at 1400 Pelham Pkwy South, Jacobi Medical Center, Bronx, NY 10461. The listed phone number is (718) 918-5642.
What is Sindhu Vikash's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Sindhu Vikash enrolled in Medicare?
Yes. Sindhu Vikash is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Sindhu Vikash was last updated on May 10, 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.