The AI-native operating system for cash-pay wellness clinics
Patient record, patient flow, and marketing on one governed kernel — with AI agents that draft the work and humans who approve every clinical, patient-facing, and financial action.
Built for owner-operated GLP-1 and weight-loss clinics, proven first in a real practice.
Three systems your clinic runs on. One place they finally live.
Today the record lives in an EHR, the pipeline lives in a CRM, and the schedule lives somewhere else. Oben fuses them on one kernel — one identity model, one permission system, one audit trail.
Patient record
A canonical, governed record: charting with sign-and-lock notes, medical alerts, consents, and minimum-necessary access for every role.
Patient flow
Scheduling, intake, tasks, and payments in one operational surface — the front desk and the provider work from the same truth.
Growth engine
Lead capture, pipelines, conversations, recalls, and reviews — marketing bound to the record instead of bolted on beside it.
AI does the heavy lift. Humans keep the pen.
Oben’s agents structure intake, flag contraindications, draft the visit note, and suggest the follow-up — inside the kernel’s governance, never around it.
Nothing clinical, patient-facing, or financial happens without a visible human approval. Every suggestion is labeled as AI and shows the record fields it came from.
- Every AI suggestion is labeled and source-linked
- Approve, edit, or reject — one deliberate action
- A first-class approval queue and audit trail
- Role-scoped access: staff see only what their job needs
The provider’s value moment
Open a new GLP-1 patient and the decision is already prepped: intake structured, flags raised, a drafted note waiting, a suggested titration on the side. Read, edit, approve — and the Rx is on its way to the pharmacy from the same record. Minutes, not an evening of charting.
Trust is a feature, not a promise
Wrong-patient guards, confirm-on-sign, append-only addenda, two-tier alerts, and a replayable audit log — safety patterns designed in from the first line of the kernel.
One visit, closed end-to-end
Lead becomes patient
A lead is captured, nurtured in the pipeline, and booked — the same identity from first click to first visit.
AI preps the visit
Intake is structured, eligibility and contraindications are flagged, and a lean note is drafted before the provider walks in.
The provider approves
The decision-ready packet on one screen: review, edit, approve the note, approve the Rx. Every approval is explicit and audited.
The loop closes
The Rx goes to the pharmacy, status writes back to the record, and follow-ups queue for approval — nothing falls through.
Cloud-native on AWS, from day one
Oben runs on an AWS foundation designed for healthcare workloads: HIPAA-eligible services under a Business Associate Agreement, encrypted at rest and in transit, with organization-wide audit logging and guardrails applied before the first feature shipped.
The AI layer is Bedrock-native, so patient data stays inside the same governed AWS boundary as the record itself.
- AWS-native architecture: RDS Postgres, App Runner, Amplify
- Bedrock-native AI — agents run inside the compliance boundary
- Multi-account AWS organization with HIPAA guardrails
- Encryption, audit trails, and least-privilege by default
Proven in a real clinic, not a whiteboard
Oben’s first customer is Wellform MD — the founder’s own cash-pay weight-loss and wellness practice. Every workflow is tested against a real front desk, real providers, and real patients before it ships to anyone else.
Why cash-pay GLP-1 clinics?
GLP-1 care is protocol-driven, recurring, and growing fast — and the clinics delivering it are run by owner-operators stitching together an EHR, a CRM, and a pile of spreadsheets. They deserve software that runs the whole practice, built by someone who runs one.
Run your clinic on one governed system
Oben is onboarding early clinics now. Tell us about your practice and we’ll be in touch.
Request early access