JAMES RAMSARRAN DO
NPI 1356284947
Student in an Organized Health Care Education/Training Program in Philadelphia, PA
About James Ramsarran Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JAMES RAMSARRAN DO (NPI 1356284947) is an individual student in an organized health care education/training program in Philadelphia, Pennsylvania and active in the NPI registry since April 2026. 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)
James Ramsarran Do 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.
PHILADELPHIA, PA 19131
PHILADELPHIA, PA 19131
PHILADELPHIA, PA 19131
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 James Ramsarran's NPI number?
The NPI number for James Ramsarran is 1356284947. It was assigned to this individual provider in the NPPES registry on April 10, 2026.
Where is James Ramsarran located?
James Ramsarran practices at 4170 City Ave, Philadelphia, PA 19131. The listed phone number is (215) 871-6100.
What is James Ramsarran's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is James Ramsarran enrolled in Medicare?
Yes. James Ramsarran is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for James Ramsarran was last updated on April 10, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.