BOS — Behavioral Operating System

Your program has policies. Your staff need answers.

BOS turns the operational knowledge required to run a behavioral health program into an organized system staff can actually use.

Operations Academy Emergency Compliance People Systems

Preview of the BOS interface

The Problem

The answer exists. Nobody can find it.

Behavioral health programs rarely lack information. The information is simply scattered — and a staff member mid-shift has to guess which of a dozen places holds the answer.

  • Policy binders
  • Shared drives
  • Emails
  • EHR systems
  • Training documents
  • Group chats
  • Forms
  • Emergency plans
  • HR systems
  • Payroll platforms
  • Staff knowledge
  • Multiple technology systems

When the answer is hard to find, staff improvise. Practice drifts, documentation gets inconsistent, and the same questions get asked on every shift.

The Approach

BOS brings the operational layer together.

BOS is designed as an organized operational layer that sits across the program — connecting staff to the information, procedures, training, and systems they need, and pointing them to the right platform when the work belongs somewhere else.

It does not replace the tools a program already runs on. It makes them findable, and it holds the operational knowledge that currently lives in binders, inboxes, and people's heads.

  • BOS is not an EHR. Clinical charting stays in your electronic health record.
  • BOS is not an HR or payroll system. Those platforms remain the system of record for employment and pay.
  • BOS is not a medical record. It is an operational and workforce resource.

Designed to be PHI-free

BOS is designed to help staff know what to do and where to go — without becoming the client medical record.

BOS is being designed around operational and workforce information rather than client medical records. That boundary is deliberate: it keeps the platform useful to every staff member without turning it into another place identifiable client information can accumulate.

  • BOS can teach staff how to complete a workflow
  • BOS can direct staff to the appropriate EHR or operational platform
  • BOS can host training, procedures, emergency information, and staff guidance
  • BOS should not store identifiable client clinical information

This describes the design intent of the platform. It is not a legal opinion, a compliance certification, or a guarantee regarding HIPAA or any other regulatory requirement. Each organization remains responsible for its own privacy and security determinations.

Modules

How BOS is organized.

BOS is structured into modules that map to how a program actually operates. Modules are configured per program; not every module is enabled in every environment.

BOS

Operations

Daily workflows, procedures, staff guidance, schedules, systems, forms, and operational resources.

BOS

Academy

Orientation, training modules, system walkthroughs, role-specific education, and ongoing workforce development.

BOS

Emergency

Emergency Quick Cards, emergency contacts, evacuation information, disaster response, and critical staff instructions.

BOS

Compliance

Centralized access to program standards, regulatory resources, documentation expectations, and compliance guidance.

BOS

People

Staff onboarding, role expectations, announcements, contacts, and workforce resources.

BOS

Systems

An organized access point for the external technology and systems staff use to operate the program.

Preview of a BOS module view

BOS is an actively developing platform. Module availability and functionality vary by program and by stage of implementation.

The Habit

Check BOS first.

When staff have a question about how the program operates, where something is located, what procedure to follow, or what to do next, BOS is designed to be the first place they look.

  • Where’s the form?Check BOS.
  • What’s the procedure?Check BOS.
  • What do I do in an emergency?Check BOS.
  • Where’s the training?Check BOS.
  • What system do I use?Check BOS.

Spelled BOS Pronounced Boss

Architecture

One platform. Configured per facility.

BOS is built so the same operating structure can be deployed across different behavioral health programs, with the local details that make it specific to a site.

BOS Core

The reusable platform.

The structure that stays consistent from program to program.

  • Platform structure
  • Training
  • Workflows
  • Operational guidance
  • Resources
  • System framework

Facility Configuration

The local layer.

The information that makes a BOS environment specific to one site.

  • Facility name
  • Branding
  • Emergency contacts
  • Nearest hospital
  • Local police / fire
  • Utility providers
  • Evacuation locations
  • Evacuation maps
  • Staff roles
  • EHR
  • Payroll system
  • Internal platforms
  • Program-specific procedures

Core is developed once and improves for every program. Configuration is what makes a BOS environment belong to a specific facility — and it stays private to that program.

Deployments

BOS Programs

BOS environments can be configured around the workflows, procedures, systems, resources, and training needs of individual behavioral health programs.

Active Program

BOS | One Path

Residential Behavioral Health

A customized BOS environment supporting One Path’s residential operations, staff training, emergency response, program resources, and daily workflows.

Enter BOS | One Path

Private program access — portal not yet published.

Next Step

Interested in BOS for your program?

BOS is developed by SoCalMHS and configured program by program. If you are building, restructuring, or scaling a behavioral health program and want to talk through what a BOS environment would look like for it, start a conversation.