MRS. BRIANNA WOLFE CRNP
NPI 1992530174
Nurse Practitioner - Family in Kintnersville, PA
About Mrs. Brianna Wolfe Crnp NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MRS. BRIANNA WOLFE CRNP (NPI 1992530174) is an individual family provider in Kintnersville, Pennsylvania, licensed in Pennsylvania (SP030552) and active in the NPI registry since September 2024. She is enrolled in Medicare PECOS and is a graduate of Other (2024).
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)
Mrs. Brianna Wolfe Crnp 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 18930 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 Brianna Wolfe's NPI number?
The NPI number for Brianna Wolfe is 1992530174. It was assigned to this individual provider in the NPPES registry on September 5, 2024.
Where is Brianna Wolfe located?
Brianna Wolfe practices at 385 Frogtown Rd, Kintnersville, PA 18930. The listed phone number is (215) 839-4223.
What is Brianna Wolfe's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
Is Brianna Wolfe enrolled in Medicare?
Yes. Brianna Wolfe is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Brianna Wolfe was last updated on September 5, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 23 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.