BRANDON SAVAGE DO
NPI 1063272607
Student in an Organized Health Care Education/Training Program in Norfolk, VA
About Brandon Savage Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRANDON SAVAGE DO (NPI 1063272607) is an individual student in an organized health care education/training program in Norfolk, Virginia and active in the NPI registry since March 2024. 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)
Brandon Savage Do is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 12
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
NORFOLK, VA 23507
NORFOLK, VA 23507
NORFOLK, VA 23507
NORFOLK, VA 23507
NORFOLK, VA 23507
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 Brandon Savage's NPI number?
The NPI number for Brandon Savage is 1063272607. It was assigned to this individual provider in the NPPES registry on March 20, 2024.
Where is Brandon Savage located?
Brandon Savage practices at 825 Fairfax Ave Ste 563, Norfolk, VA 23507. The listed phone number is (757) 446-7934.
What is Brandon Savage's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Brandon Savage enrolled in Medicare?
Yes. Brandon Savage is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Brandon Savage was last updated on March 20, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 years 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.