ALEXANDRA JANDA
NPI 1356929319
Student in an Organized Health Care Education/Training Program in Houston, TX
About Alexandra Janda NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ALEXANDRA JANDA (NPI 1356929319) is an individual student in an organized health care education/training program in Houston, Texas and active in the NPI registry since March 2021. 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)
Alexandra Janda 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
HOUSTON, TX 77030
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 Alexandra Janda's NPI number?
The NPI number for Alexandra Janda is 1356929319. It was assigned to this individual provider in the NPPES registry on March 31, 2021.
Where is Alexandra Janda located?
Alexandra Janda practices at 6431 Fannin St Msb 2.116b, Houston, TX 77030. The listed phone number is (713) 500-7643.
What is Alexandra Janda's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Alexandra Janda enrolled in Medicare?
Yes. Alexandra Janda is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Alexandra Janda was last updated on April 15, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.