DR. RANYA ALNATOUR
NPI 1083275879
Psychologist - Clinical Child & Adolescent in Houston, TX
About Dr. Ranya Alnatour NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. RANYA ALNATOUR (NPI 1083275879) is an individual clinical child & adolescent provider in Houston, Texas, licensed in Texas (38999) and active in the NPI registry since June 2019. She is enrolled in Medicare PECOS and maintains a secondary practice location in Dallas.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dr. Ranya Alnatour 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.
HOUSTON, TX 77030
HOUSTON, TX 77030
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 Ranya Alnatour's NPI number?
The NPI number for Ranya Alnatour is 1083275879. It was assigned to this individual provider in the NPPES registry on June 24, 2019.
Where is Ranya Alnatour located?
Ranya Alnatour practices at 6701 Fannin St, Houston, TX 77030. The listed phone number is (832) 824-1000.
What is Ranya Alnatour's specialty?
The primary specialty registered for this NPI is Psychologist, specializing in Clinical Child & Adolescent, with taxonomy code 103TC2200X.
Is Ranya Alnatour enrolled in Medicare?
Yes. Ranya Alnatour is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ranya Alnatour was last updated on September 4, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 days 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.