BAKTHA KUMAR
NPI 1376242297
Social Worker - Clinical in Union, NJ
About Baktha Kumar NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BAKTHA KUMAR (NPI 1376242297) is an individual clinical provider in Union, New Jersey, licensed in New Jersey (44SC01333700) and active in the NPI registry since February 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)
Baktha Kumar 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 07083 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Baktha Kumar's NPI number?
The NPI number for Baktha Kumar is 1376242297. It was assigned to this individual provider in the NPPES registry on February 28, 2023.
Where is Baktha Kumar located?
Baktha Kumar practices at 1702 Van Ness Ter, Union, NJ 07083. The listed phone number is (908) 591-8681.
What is Baktha Kumar's specialty?
The primary specialty registered for this NPI is Social Worker, specializing in Clinical, with taxonomy code 1041C0700X.
Is Baktha Kumar enrolled in Medicare?
Yes. Baktha Kumar is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Baktha Kumar was last updated on February 28, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.