ANJITHA VALIYIL
NPI 1477347011
Student in an Organized Health Care Education/Training Program in Pittsburgh, PA
About Anjitha Valiyil NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ANJITHA VALIYIL (NPI 1477347011) is an individual student in an organized health care education/training program in Pittsburgh, Pennsylvania and active in the NPI registry since April 2025. 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)
Anjitha Valiyil 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.
PITTSBURGH, PA 15219
PITTSBURGH, PA 15219
PITTSBURGH, PA 15219
PITTSBURGH, PA 15219
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 Anjitha Valiyil's NPI number?
The NPI number for Anjitha Valiyil is 1477347011. It was assigned to this individual provider in the NPPES registry on April 8, 2025.
Where is Anjitha Valiyil located?
Anjitha Valiyil practices at 1515 Locust St, Pittsburgh, PA 15219. The listed phone number is (412) 232-7677.
What is Anjitha Valiyil's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Anjitha Valiyil enrolled in Medicare?
Yes. Anjitha Valiyil is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Anjitha Valiyil was last updated on April 8, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 16 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.