Opening a second branch does not mean running the first branch twice. When patient records, cash, stock, physician calendars and permissions begin to work in several places at once, many things that ran on instinct in one branch turn into an invisible mess. This article explains which decisions should be made up front to run a multi-branch clinic in an orderly way.
The real problem: what is shared and what is separate
A multi-branch business faces two separate questions, and most software confuses them. First, which information is shared across all branches? Second, which information belongs to one branch? A workable split looks like this:
| Shared (organization level) | Branch-specific |
|---|---|
| Patient identity and core record | Appointment calendar and room or device use |
| Service and price catalog framework | Application of the price list at the branch |
| Role definitions | Which branch a user works in |
| Physician and staff identities | Cash session and daily close |
| Consolidated reports | Warehouse and stock count |
A file opened for a patient at one branch should not be reopened when the patient visits the second branch. But a front-desk employee at the second branch should not automatically see that patient's whole clinical history. "The same patient" and "the same permission" are separate concepts. Without this split, either the same patient lives in three branches with three separate records, or everyone sees everything.
Branch context: on whose behalf is each screen working?
The most critical concept in a multi-branch setup is branch context. When a user switches branches, several things on screen should change together:
- The user's membership and role at that branch are checked; if there is no membership, access is denied and the attempt is recorded.
- The price list returns to that branch's valid list.
- The warehouse and stock view switches to that branch's warehouse.
- The cash session opens with that branch's register.
- Reports are calculated within that branch's scope.
In HekimBis this is described as a branch-switching flow: membership and permission check first, then price, stock, cash and report context change. In central roles such as a call center, an authorized user can use a cross-branch calendar view, which is still permission-bound.
Call-center view
An authorized call center sees the cross-branch calendar on one screen and books the appointment at the most suitable branch.
- The process is complete here.
All steps
- 01 Branch selected (User) The user picks another branch from the branch switcher.
- 02 Membership and authority check (Authority) Is there explicit membership and role authority in this branch? For a patient at another branch, a task or care relationship is also required.
- 03 Price list switches (Price) The effective price list of that branch (or physician, or institution) opens.
- 04 Warehouse and stock context (Stock) Procedures draw from that branch's warehouse; cross-branch transfers are on record.
- 05 Cash session (Cash desk) Collections are written to that branch's open cash session.
- 06 Report scope (Report) Reports open for the branch scope within your authority.
- 07 Call-center view (User) An authorized call center sees the cross-branch calendar on one screen and books the appointment at the most suitable branch.
Alternative path from 02 Membership and authority check; the process ends on this path.
- 02a No membership: access denied (Authority) Without membership for the branch or patient, access does not open; the attempt is written to the audit log.
07 Call-center view
Making the context visible matters too. Users should see which branch they are working in at every moment. Entering a payment into the wrong branch's register is a common error in multi-branch businesses, and fixing it later is laborious.
Central booking and the call center
In businesses with several branches, a patient often does not ask "which branch has an opening?" but "is there a suitable time this week?" Being able to see every branch's calendar on one screen helps the call center fill freed-up slots. Two points need attention:
- Permission: A call center employee can book appointments but should not see the examination record. Appointment visibility and clinical record visibility are separate permissions.
- Resource conflicts: If the same physician works in two branches, the calendar must be one. Otherwise the same physician gets two appointments at the same time from two branches. The "single calendar" principle also covers the physician's working days across branches.
Mechanisms such as reminders and waitlists are described in the appointments and calendar feature. For practices that reduce no-shows, read our appointment management article.
Cash, stock and physician revenue share
Cash
Each branch's cash needs its own session and its own close. At the head office you need a consolidated view of these registers. In a good setup the branch register closes its own day, and the center sees the totals and differences of all branches on one screen. Collections and accounts are covered on the finance and collections page.
Stock
Transfers between branches are a recurring need: a consumable that ran out at branch A may be sitting at branch B. A transfer should leave a trace in both warehouses with an outgoing and an incoming entry, and lot and expiry tracking should travel with the transfer. If consumables are tied to procedure kits, consumption is deducted automatically with the procedure.
Physician revenue share
The same physician may work at different branches at different rates. The calculation should be separable by branch, service and collection. For details, see our physician revenue share guide.
Permission design: "a bigger plan does not make everyone authorized everywhere"
In a multi-branch structure, permission is thought of on two axes: the person's role (front desk, physician, accounting, manager) and the branches the person is a member of. The two are evaluated together. In addition, contexts such as data sensitivity and care relationship come into play. A physician normally cannot open the file of a patient they are not caring for. In an urgent situation there is an exception path that is recorded with a reason and a time limit and written separately to the audit trail.
A practical rule: buying a plan does not create permission. Buying a larger plan does not automatically give a user clinical access at every branch. Access is always defined separately through membership and role. See the roles and permissions page for the role structure.
Consolidated reporting
Head-office management wants to see comparative answers across branches: which branch has low occupancy, where do cancellations and no-shows run high, which service is in demand at which branch, where do collection delays pile up? These reports are comparable only if branches work with the same data dictionary. If branch A says "examination" and branch B says "follow-up," a consolidated report becomes meaningless. So the first job is to standardize the service and payment-type dictionary at the organization level. Report details are in the reporting feature.
The first thirty days of a new branch
When a new branch opens, most of the software work should be finished before the opening. Otherwise the branch starts out with old habits. A practical order:
- Branch record and memberships: Define the branch and add employees with their memberships and roles. A departing employee's old membership remains until they leave.
- Calendar and resources: Enter physician working days, rooms and devices; mark shared physicians' days at other branches so they do not overlap.
- Price list: Apply the central price framework to the branch; record any branch-specific difference openly.
- Cash and warehouse: Open the cash session and do the opening count; stock the warehouse with consumables.
- Communication channels: Make sure the branch's address and phone number flow into patient messages correctly; otherwise patients go to the wrong address.
- Trial day: Before opening, play a full day with fake appointments.
So you do not repeat this list for every branch, the definitions you make for the first branch should be reusable as a template. Remember, though, that each branch has its own cash and warehouse; a template applies to definitions, not balances.
Common mistakes in multi-branch setups
Duplicate records for the same patient across branches. A patient is opened at branch A as "Ayşe Yılmaz" and at branch B as "Ayşe Yilmaz." Both records point to the same person, but the history splits in two. A duplicate warning should match on fields such as ID number and date of birth, and merging should be done with human approval and be reversible rather than automatic.
Branch cash mixed with the center. If branch cash and head-office accounting live in the same ledger, finding the source of a difference at daily close becomes hard. Each branch should complete its own close, and the center should add these closes together.
Unclear physician pay across branches. If a physician works at two branches, it must be written down from the start which branch's collections the revenue share is calculated from and at what rate.
Permissions not set by branch. If a branch manager can see another branch's report, that is a permission error. Report scope should be limited to the branches the user belongs to.
Central management, local flexibility
The balance between central control and local flexibility is the real craft of multi-branch management. The center decides the service catalog, role definitions, privacy notice and consent texts, the report dictionary and security policies. The branch manages the daily appointment plan, shift schedule, local stock orders and cash close. When this split is drawn well, the branch manager decides quickly and the center can compare branches. Drawn badly, either the center interferes in every small task or every branch invents its own language and rules.
Checklist for multi-branch businesses
- Is the patient record one at organization level, and are duplicates across branches being created?
- Is the physician's calendar single across branches?
- Does each branch's cash have a separate session and close?
- Does a stock transfer leave a trace in both branches?
- Does the user see which branch they work in on screen?
- Are role and branch membership defined separately?
- Are center reports calculated with a shared dictionary?
- When an employee leaves, does access close in a single step?
Every "no" in this list is a cost that grows with the number of branches. For the broader framework see clinic management software, and for which plan covers which branch capacity, see the pricing page. The growth path is covered on the multi-branch clinic solution page, and the feature detail is on the multi-branch management page.
