GEM CITY BEHAVIORAL SOLUTIONS, LLC
NPI 1821801341
Community/Behavioral Health in Dayton, OH
About Gem City Behavioral Solutions, Llc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
GEM CITY BEHAVIORAL SOLUTIONS, LLC (NPI 1821801341) is a healthcare organization registered as a community/behavioral health in Dayton, Ohio and active in the NPI registry since January 2025. The organization lists William Slusser, Owner, as its authorized official.
NPPES Registry Identity
Specialties & Licenses 9
Accepted Insurance
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 Gem City Behavioral Solutions, LLC's NPI number?
The NPI number for Gem City Behavioral Solutions, LLC is 1821801341. It was assigned to this organization in the NPPES registry on January 29, 2025.
Where is Gem City Behavioral Solutions, LLC located?
Gem City Behavioral Solutions, LLC is located at 4134 Linden Ave, Dayton, OH 45432. The listed phone number is (937) 365-7455.
What is Gem City Behavioral Solutions, LLC's specialty?
The primary specialty registered for this NPI is Community/Behavioral Health with taxonomy code 251S00000X.
What insurance does Gem City Behavioral Solutions, LLC accept?
Health plans from Molina Healthcare list Gem City Behavioral Solutions, LLC as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Gem City Behavioral Solutions, LLC was last updated on May 26, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.