GIANNA BROWN
NPI 1720807688
Counselor in Scranton, PA
About Gianna Brown NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
GIANNA BROWN (NPI 1720807688) is an individual counselor in Scranton, Pennsylvania and active in the NPI registry since October 2024. She is enrolled in Medicare PECOS and is a graduate of Other (2023).
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 and accepts Medicare assignment
Gianna Brown 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.
Other Providers at the Same Location NPPES 17
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
SCRANTON, PA 18503
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 Gianna Brown's NPI number?
The NPI number for Gianna Brown is 1720807688. It was assigned to this individual provider in the NPPES registry on October 8, 2024.
Where is Gianna Brown located?
Gianna Brown practices at 300 Mulberry St, Scranton, PA 18503. The listed phone number is (570) 955-5479.
What is Gianna Brown's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
Is Gianna Brown enrolled in Medicare?
Yes. Gianna Brown 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 Gianna Brown was last updated on October 8, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 22 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.