HUNTER SCOTT LITZ
NPI 1215731401
Student in an Organized Health Care Education/Training Program in Durham, NC
About Hunter Scott Litz NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
HUNTER SCOTT LITZ (NPI 1215731401) is an individual student in an organized health care education/training program in Durham, North Carolina and active in the NPI registry since April 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)
Hunter Scott Litz is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 7
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
DURHAM, NC 27705
DURHAM, NC 27705
DURHAM, NC 27705
DURHAM, NC 27705
DURHAM, NC 27705
DURHAM, NC 27705
DURHAM, NC 27705
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 Hunter Litz's NPI number?
The NPI number for Hunter Litz is 1215731401. It was assigned to this individual provider in the NPPES registry on April 4, 2025.
Where is Hunter Litz located?
Hunter Litz practices at 2301 Erwin Road, Durham, NC 27705. The listed phone number is (919) 684-8111.
What is Hunter Litz's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Hunter Litz enrolled in Medicare?
Yes. Hunter Litz is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Hunter Litz was last updated on April 4, 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.