RYAN GARRISON
NPI 1265137780
Student in an Organized Health Care Education/Training Program in Temple, TX
About Ryan Garrison NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
RYAN GARRISON (NPI 1265137780) is an individual student in an organized health care education/training program in Temple, Texas and active in the NPI registry since April 2023. 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)
Ryan Garrison 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.
TEMPLE, TX 76508
TEMPLE, TX 76508
TEMPLE, TX 76508
TEMPLE, TX 76508
TEMPLE, TX 76508
TEMPLE, TX 76508
TEMPLE, TX 76508
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 Ryan Garrison's NPI number?
The NPI number for Ryan Garrison is 1265137780. It was assigned to this individual provider in the NPPES registry on April 3, 2023.
Where is Ryan Garrison located?
Ryan Garrison practices at 2401 S 31st St # 11ag062, Temple, TX 76508. The listed phone number is (254) 724-5815.
What is Ryan Garrison's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Ryan Garrison enrolled in Medicare?
Yes. Ryan Garrison is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Ryan Garrison was last updated on March 26, 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.
