VANN HAUSER
NPI 1053112359
Student in an Organized Health Care Education/Training Program in Inverness, FL
About Vann Hauser NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
VANN HAUSER (NPI 1053112359) is an individual student in an organized health care education/training program in Inverness, Florida and active in the NPI registry since March 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)
Vann Hauser is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 18
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
INVERNESS, FL 34452
INVERNESS, FL 34452
INVERNESS, FL 34452
INVERNESS, FL 34452
INVERNESS, FL 34452
INVERNESS, FL 34452
INVERNESS, FL 34452
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 Vann Hauser's NPI number?
The NPI number for Vann Hauser is 1053112359. It was assigned to this individual provider in the NPPES registry on March 22, 2025.
Where is Vann Hauser located?
Vann Hauser practices at 402 W Grace St, Inverness, FL 34452. The listed phone number is (352) 697-3581.
What is Vann Hauser's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Vann Hauser enrolled in Medicare?
Yes. Vann Hauser is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Vann Hauser was last updated on March 22, 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.