The practice's rules in its ERP, clinical records in a system of their own

The Business Problem

Any organization that runs several sites from one system faces the same five questions. Behavioral-health care sharpens each one, because treatment runs for months.

1. Can bookings be trusted? Patients book weekly or fortnightly sessions far into the future, across doctors, session types and branches. A slot shown online has to be a slot that really exists, and a calendar that runs about ten months ahead still has to open quickly for the receptionist and the patient.
2. Who is at the keyboard? Reception desks and consulting rooms share workstations. Being signed in is not enough to open clinical screens in the ERP: each doctor also enters a personal PIN, which must be re-entered after a set time. Managers need a record of every attempt.
3. Who has quietly stopped coming? Patients drift away after a few sessions or after a change of therapist. Unless the system notices, follow-up depends on someone remembering.
4. What is each clinician owed? Monthly payouts depend on doctor, session type and branch. Working them out by hand is slow and invites error.
5. Who should see clinical notes at all? Reception and finance need to know that a plan exists and how many sessions remain, not the clinical notes themselves.

Our Approach

We started from how the practice actually runs: how sessions are booked and moved, who sits at which screen, how care coordinators work, and how clinicians are paid. For each question we asked whether the standard set-up could express the rule. Where it could, we extended it. Where it could not, we built the logic the practice needed: inside the ERP for scheduling, follow-up and finance, which work from one set of records, and, for clinical records, in a dedicated system linked to the ERP.

Delivered Solution

1. Bookings that match real availability, on a calendar that opens fast. Every online booking is re-checked on the server against real doctor, time and branch availability before it is accepted. Live in production. On the calendar, since a September 2026 release, the first 45 days of a booking horizon of about ten months appear in under a second instead of about five. The rest loads in the background and stays bookable.

2. A second key for clinical screens on shared workstations. Clinical screens in the ERP are protected by a second, per-doctor PIN for shared workstations, and every check, failure and lockout is written to an audit trail. Live in production.

3. Continuity of care, made systematic. Treatment is organized as assessment-driven, multi-phase therapy plans. Each booked session is linked to the right phase of the plan, and the link holds when sessions are rescheduled or cancelled. Live in production. Alongside the plans, a daily five-rule check flags patients who may be dropping out of care or who are due a follow-up call, for example no return within 21 days, a sudden stop after regular attendance, or a first session with a new therapist. It creates follow-up tasks for coordinators without duplicates, so each case appears once rather than as repeated alerts. By mid-October 2026 it had raised 3,544 follow-up tasks.

4. Clinician payout calculation, built in. We built automatic calculation of monthly clinician commissions across doctors, session types and branches, which generates the vendor bills for finance. This is deployed in the production system.

5. A dedicated clinical system, linked to the ERP. On the strength of the first phase, the practice asked us back to build a separate system for clinical records. Clinicians record assessments and therapy plans there, each signing in with the personal ERP account they already have. Patients appear in it only as a random code; names and contact details stay in the ERP. Each clinician sees only their own patients, and a confirmed assessment is locked: reopening it needs a recorded reason. When a plan is confirmed, only the details needed for booking pass to the ERP, so reception can schedule sessions against the plan without seeing clinical notes. If the link is interrupted, the booking screen says so instead of showing that the patient has no plan. Because it is built on Odoo 19's open-source edition, clinicians will record there with full rights while keeping only portal access in the ERP, so about 30 clinicians, and any the practice adds, need no full ERP user subscription. Built and trialled; the clinicians move over when development is complete.

Evidence-Backed Value

• Live in production: server-side re-checking of every online booking; therapy plans with sessions linked to the right phase through reschedules and cancellations; and per-doctor PIN protection of clinical screens in the ERP, with an audit trail.
• Faster first view: since a September 2026 release, the first 45 days of the calendar appear in under a second instead of about five, with the full horizon still bookable.
• Follow-up at scale: 3,544 follow-up tasks raised for coordinators by mid-October 2026. This is a count of tasks, not a retention result.
• Payout calculation: automatic commission calculation, which generates the vendor bills for finance, is deployed in the production system.
• We designed the clinical system following HIPAA safeguard recommendations: a personal sign-in for every clinician, access limited to each clinician's own patients, patients identified only by a code, assessments that lock once confirmed, and a history of who created, confirmed or reopened each record.
• At least 30 full ERP user subscriptions a year, not needed (by design): clinicians will work in the clinical system with full rights and keep only portal access in the ERP; the number grows with every clinician the practice adds.
• Expected benefits: the follow-up queue is designed to help coordinators reach patients before they drop out of care. Automated commissions are designed to shorten the monthly payout close and remove manual recalculation.

What This Means for Your Organization

If you run several branches, sites or teams from one system, the same controls apply to you: availability the system checks for itself, access tied to the person rather than the workstation, a queue that brings forward the cases that need attention, and staff payouts calculated from the work recorded. If some of your records need tighter handling than the rest, they can sit in a dedicated system linked to your ERP, so the people who book and bill see what they need, not the sensitive detail, and everyone signs in as themselves. We build those rules into your ERP, or beside it where that is safer, and we tell you plainly which parts are live.

All case studies