CHASE HUNTER SMITH
NPI 1346051729
Student in an Organized Health Care Education/Training Program in Birmingham, AL
About Chase Hunter Smith NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
CHASE HUNTER SMITH (NPI 1346051729) is an individual student in an organized health care education/training program in Birmingham, Alabama and active in the NPI registry since January 2025. 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)
Chase Hunter Smith 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.
BIRMINGHAM, AL 35233
BIRMINGHAM, AL 35233
BIRMINGHAM, AL 35233
BIRMINGHAM, AL 35233
BIRMINGHAM, AL 35233
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 Chase Smith's NPI number?
The NPI number for Chase Smith is 1346051729. It was assigned to this individual provider in the NPPES registry on January 15, 2025.
Where is Chase Smith located?
Chase Smith practices at 625 19th St S, Birmingham, AL 35233. The listed phone number is (205) 934-6007.
What is Chase Smith's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Chase Smith enrolled in Medicare?
Yes. Chase Smith is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Chase Smith was last updated on April 1, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.