KRIS LANHAM
NPI 1700720943
Student in an Organized Health Care Education/Training Program in Peoria, IL
About Kris Lanham NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
KRIS LANHAM (NPI 1700720943) is an individual student in an organized health care education/training program in Peoria, Illinois and active in the NPI registry since April 2026. The provider is enrolled in Medicare PECOS and maintains a secondary practice location in Peoria.
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)
Kris Lanham 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.
PEORIA, IL 61636
PEORIA, IL 61636
PEORIA, IL 61636
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 Kris Lanham's NPI number?
The NPI number for Kris Lanham is 1700720943. It was assigned to this individual provider in the NPPES registry on April 17, 2026.
Where is Kris Lanham located?
Kris Lanham practices at 221 NE Glen Oak Ave, Peoria, IL 61636. The listed phone number is (309) 672-5522.
What is Kris Lanham's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Kris Lanham enrolled in Medicare?
Yes. Kris Lanham is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Kris Lanham was last updated on April 17, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.