Industries · Behavioral health & recovery
Built around the reality of community-based behavioral health operations.
The work doesn’t happen only in the EHR. It happens in homes, vehicles, community spaces, offices, treatment environments and everywhere in between. Phibian helps organizations coordinate the operation surrounding that work.
Why this is hard
The clinical record is complete. The operational picture isn’t.
Community-based organizations run a genuinely difficult operation: staff distributed across a service area, caseloads that change weekly, documentation requirements that arrive from several directions at once, and funding that depends on being able to demonstrate what happened.
The EHR does its job well — it documents the service after charting. Payroll does its job after the period closes. Scheduling holds the plan. Messaging holds the conversation. Each one is authoritative about its fragment, and the organization is left assembling the operational picture by hand, usually by asking people to re-report things another system already knows.
That assembly work falls on supervisors and program directors — the people whose actual job is supporting staff and clients. It is expensive, it is error-prone, and it means the honest answer to “is anyone falling through today?” arrives late.
Eight operational problems
What Phibian does about each one.
Stated against actual product status. Where a capability is still being built, this table says so rather than implying otherwise.
| Operational problem | What it looks like | How Phibian handles it |
|---|---|---|
| Scheduling distributed teams | Peer support, case management and outreach staff work across homes, community spaces and offices. The published schedule stops describing the day by mid-morning. | Scheduling connected to what actually happened, with coverage visible during the day. |
| Understanding field activity | A visit happens in a living room or a car. It reaches a system hours later, filtered through a phone and a memory. | Location-aware timekeeping with honest verification states, captured where the work happens. |
| Time and attendance | Hours are reconstructed at week’s end, and corrections overwrite whatever was first recorded. | Immutable punches, structured adjustments that supersede rather than erase, and weekly approval that locks a snapshot. |
| Mileage | Staff drive constantly between clients and sites, then rebuild the week from memory for reimbursement. | Being built on the authorized movement record so travel derives from the operation. In development — not available today. |
| Supervision workflows | Supervisors spend the day chasing status by text and phone, with no shared view of who needs support. | A ranked attention queue with the evidence attached, scoped to the programs a supervisor is responsible for. |
| Documentation visibility | Whether a service was documented is knowable only inside the system of record, long after the fact. | Reconciliation between scheduled work and observed activity, so unmatched records surface as operational exceptions. |
| Operational alerts | Problems are discovered at period close — an unstaffed shift, a missing clock-out, a week that does not add up. | Configurable rules evaluated against the live record, raising what deserves review while it can still be fixed. |
| System fragmentation | The EHR, payroll, scheduling, messaging and mileage tools each hold a fragment and none of them agree about today. | A connector framework with per-tenant credentials and honest degradation states, treating the EHR as a connector rather than the centre. |
In the product
What a Tuesday looks like.
A supervisor opens Phibian to see the operation. A peer support specialist opens it to see their day. Both are looking at the same record.
Program supervisor
Coverage across programs, check-ins that could not be confirmed, missing clock-outs, and visits with no matching time record — ranked, with the evidence attached and scoped to the programs they are responsible for.
Community-based staff
Today’s visits in order, clock in at the door, and a record that keeps working in a basement with no reception — uploading later with the real time, never the upload time.
Privacy in this environment
Built for a setting where privacy is not negotiable.
These are product defaults in Phibian, not configuration options an organization has to discover and switch on.
Clients appear by initials
Client identity is initials by default across the product. Opening a full name is a distinct permission, and doing so writes an audit event.
Client residences are not geofences
Work-site geofences are organizational sites. The product deliberately does not turn the places people live into monitored locations.
Location never travels in messages
Coordinates, addresses and geofence names are never placed into message, notification or SMS text, or into general logs.
Sensitive access is separately granted
Viewing raw location history is its own permission, granted to no role by default, and every view is recorded.
Phibian does not currently hold SOC 2, HITRUST or any other third-party security certification, and does not describe itself as “HIPAA compliant”. What we do have is described precisely on the security page, and the obligations that would sit in a business associate agreement are a conversation we are glad to have directly.
Worker trust
Peer and community staff will use this — or quietly won’t.
In this field, many staff have lived experience of systems that watched them. A product that feels like surveillance does not get adopted; it gets worked around, and the operational record degrades to match.
Collected while clocked in — never after
Location capture is bounded by the work session as a structural property of the system, not a setting somebody has to remember.
Gaps are questions, not accusations
Basements, weather and battery savers interrupt phones. A coverage gap opens a reviewable exception — never an automatic finding of misconduct.
Records are correctable
Staff can see their record and ask for a fix. The original is kept, so a correction never looks like a cover-up.
Keep exploring
Human services
The same operational foundation across community-based and social service organizations.
Explore Human servicesIntegrations
How Phibian is designed to connect around your system of record rather than replace it.
Explore IntegrationsField
Location-aware timekeeping, honest states and offline capture in detail.
Explore Field