BRENNEN BOSEMAN SEED LPC
NPI 1376979914
Counselor - Professional in Lovingston, VA
About Brennen Boseman Seed Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BRENNEN BOSEMAN SEED LPC (NPI 1376979914) is an individual professional provider in Lovingston, Virginia, licensed in Virginia (0701010703) and active in the NPI registry since September 2013. She is enrolled in Medicare PECOS and is a graduate of Other (2006).
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare and accepts Medicare assignment
Brennen Boseman Seed Lpc is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Brennen Seed's NPI number?
The NPI number for Brennen Seed is 1376979914. It was assigned to this individual provider in the NPPES registry on September 14, 2013. The provider is also known as Bren Boseman Seed Lpc.
Where is Brennen Seed located?
Brennen Seed practices at 14398 James River Rd, Lovingston, VA 22949. The listed phone number is (503) 317-5153.
What is Brennen Seed's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Brennen Seed enrolled in Medicare?
Yes. Brennen Seed is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Brennen Seed was last updated on August 15, 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.