ROHAN ALFRED PAPALY
NPI 1295232122
Student in an Organized Health Care Education/Training Program in San Antonio, TX
About Rohan Alfred Papaly NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ROHAN ALFRED PAPALY (NPI 1295232122) is an individual student in an organized health care education/training program in San Antonio, Texas and active in the NPI registry since April 2018. 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)
Rohan Alfred Papaly 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.
FORT SAM HOUSTON, TX 78234
FORT SAM HOUSTON, TX 78234
FORT SAM HOUSTON, TX 78234
FORT SAM HOUSTON, TX 78234
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 Rohan Papaly's NPI number?
The NPI number for Rohan Papaly is 1295232122. It was assigned to this individual provider in the NPPES registry on April 8, 2018.
Where is Rohan Papaly located?
Rohan Papaly practices at 3551 Roger Brooke Dr, San Antonio, TX 78234. The listed phone number is (210) 292-7868.
What is Rohan Papaly's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Rohan Papaly enrolled in Medicare?
Yes. Rohan Papaly is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Rohan Papaly was last updated on April 9, 2018. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 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.