MEGAN WELLS NP
NPI 1598685067
Nurse Practitioner in Baker, WV
About Megan Wells Np NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MEGAN WELLS NP (NPI 1598685067) is an individual nurse practitioner in Baker, West Virginia, licensed in West Virginia (113286) and active in the NPI registry since July 2026. She 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)
Megan Wells Np is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 26801 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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.
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 Megan Wells's NPI number?
The NPI number for Megan Wells is 1598685067. It was assigned to this individual provider in the NPPES registry on July 16, 2026.
Where is Megan Wells located?
Megan Wells practices at 17978 Sr 55, Baker, WV 26801. The listed phone number is (304) 897-5915.
What is Megan Wells's specialty?
The primary specialty registered for this NPI is Nurse Practitioner with taxonomy code 363L00000X.
Is Megan Wells enrolled in Medicare?
Yes. Megan Wells is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Megan Wells was last updated on July 16, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 39 days 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.