EVAN MUSMAN D.O.
NPI 1467598441
Anesthesiology - Pain Medicine in South Burlington, VT
About Evan Musman D.o. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
EVAN MUSMAN D.O. (NPI 1467598441) is an individual pain medicine provider in South Burlington, Vermont, licensed in Vermont (032-0000427) and active in the NPI registry since January 2007. He has opted out of Medicare through July 1, 2027.
NPPES Registry Identity
Specialties & Licenses 2
Other Identifiers 5
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Opted out of Medicare
Evan Musman D.o. has filed a Medicare opt-out affidavit. Services are provided under private contract between the provider and the patient, and are not billed to or reimbursed by Medicare. The opt-out is on file from July 1, 2023 through July 1, 2027.
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 Evan Musman's NPI number?
The NPI number for Evan Musman is 1467598441. It was assigned to this individual provider in the NPPES registry on January 29, 2007.
Where is Evan Musman located?
Evan Musman practices at One Kennedy Drive, Suite U-1, South Burlington, VT 05403. The listed phone number is (802) 861-6100.
What is Evan Musman's specialty?
The primary specialty registered for this NPI is Anesthesiology, specializing in Pain Medicine, with taxonomy code 207LP2900X.
Is Evan Musman enrolled in Medicare?
No. Evan Musman has opted out of Medicare through July 1, 2027. Care is provided under private contracts, and Medicare does not pay for services furnished by providers who have opted out.
When was this NPI record last updated?
The NPPES record for Evan Musman was last updated on March 5, 2008. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 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.