The whole clinic, on one governed kernel
Oben is one role-based workspace for the front desk, the provider, and the owner — every module inherits the same identity model, permissions, audit trail, and AI governance.
Dashboard
A calm landing for each role: today’s arrivals, pending approvals, and the next thing that needs a human — nothing else.
Schedule
A clean clinical calendar with semantic statuses — booked, arrived, no-show — always paired with icons and labels, never color alone.
Clients
The canonical record: overview, appointments, payments, tasks, and a chart-review timeline of signed notes with append-only addenda.
Connect
All client communication in one governed inbox, plus live video consults and async video messages — delivered securely, never a public link.
Payments
Cash-pay charges, plans, and payment links — money and the medical record finally reconcile because they share one system.
Marketing
Pipelines, opportunities, and reviews bound to the record — growth work that knows who is already a patient, and outbound that waits for approval.
The provider encounter, decision-ready
The visit that matters most — a GLP-1 encounter — lands on one screen: patient context, eligibility and contraindication flags, the AI-drafted note, and the suggested Rx, each linked to its source in the record.
The provider reads, edits, approves the note, approves the Rx — and it’s sent to the pharmacy from the same record. A persistent patient-context banner and confirm-on-sign guard against wrong-chart mistakes.
- Decision-ready packet: context, flags, note, and Rx together
- Every AI draft is editable — approve is always a human act
- Wrong-patient guards and confirm-on-sign, by design
- Sign-and-lock notes; corrections are dated, signed addenda
Everything the AI does — and everything you control about it
One first-class surface shows the AI’s activity feed, the approval queue, and a replayable audit of who did what — staff, patient, or agent — and why.
Owners manage which agents run, what they’re permitted to do, and how much autonomy they get. Governance isn’t a settings page — it’s the product.
- Approval queue — clinical, patient-facing, and financial actions wait for a human
- Activity feed — every suggestion, action, and outcome, in the open
- Audit replay — trace any decision back to its evidence
- Agent controls — permissions and autonomy per agent, per clinic
Designed for healthcare from the first commit
Oben is built AWS-native on HIPAA-eligible services under a Business Associate Agreement — a multi-account organization with encryption, organization-wide audit logging, and least-privilege guardrails applied before the first feature. Minimum-necessary access is enforced in the product: each role sees only the data its job requires, and the full record is one explicit, audited action away.
See Oben on your clinic’s workflows
We’re onboarding a small group of early clinics alongside our client-zero practice.
Request early access