MRS. LORIE LIPSCOMB FNP-BC
NPI 1811275852
Nurse Practitioner - Family in Charleston, WV
About Mrs. Lorie Lipscomb Fnp-bc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MRS. LORIE LIPSCOMB FNP-BC (NPI 1811275852) is an individual family provider in Charleston, West Virginia, licensed in West Virginia (50517) and active in the NPI registry since July 2011. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Mrs. Lorie Lipscomb Fnp-bc 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 25301 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Lorie Lipscomb's NPI number?
The NPI number for Lorie Lipscomb is 1811275852. It was assigned to this individual provider in the NPPES registry on July 25, 2011.
Where is Lorie Lipscomb located?
Lorie Lipscomb practices at 1201 Washington St E Ste 100, Charleston, WV 25301. The listed phone number is (304) 388-6370.
What is Lorie Lipscomb's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Lorie Lipscomb enrolled in Medicare?
Yes. Lorie Lipscomb is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Lorie Lipscomb was last updated on July 19, 2016. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 10 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.