TINCHU RUBY VARGHESE
NPI 1972440543
Nurse Practitioner - Family in Lakewood, NJ
About Tinchu Ruby Varghese NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
TINCHU RUBY VARGHESE (NPI 1972440543) is an individual family provider in Lakewood, New Jersey, licensed in Pennsylvania (SP035559) and active in the NPI registry since May 2026. She is enrolled in Medicare PECOS and is a graduate of Other (2025).
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)
Tinchu Ruby Varghese 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 08701 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 Tinchu Ruby Varghese's NPI number?
The NPI number for Tinchu Ruby Varghese is 1972440543. It was assigned to this individual provider in the NPPES registry on May 1, 2026.
Where is Tinchu Ruby Varghese located?
Tinchu Ruby Varghese practices at 1999 Cedarbridge Ave, Lakewood, NJ 08701. The listed phone number is (401) 585-9573.
What is Tinchu Ruby Varghese's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Tinchu Ruby Varghese enrolled in Medicare?
Yes. Tinchu Ruby Varghese is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Tinchu Ruby Varghese was last updated on May 1, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.