Multi-branch clinic software runs each branch in its own order
When a second branch opens, what you expect from software changes: each branch must work with its own calendar, cash desk and stock, yet the center must see all branches at a glance, and a patient's file must not get lost when they move from one branch to another. The HekimBis Clinic package meets these three needs on the same data model without breaking branch isolation.
What changes when the branch changes
The difficulty of multi-branch management is that the idea of a branch covers several things: permissions, prices, stock, cash desk and reports. If they do not all switch to the right context together, the smallest mistake grows. The flow shows what happens in order when a user changes branch.
The user sees only the branches they are a member of and selects one. The system checks the user's membership in that branch, their role and their care relationship with the patient concerned; no one is automatically given clinical access in all branches just because your package opens several branches, and permission is defined separately. Service prices can be separated by branch, physician or institution; when the branch changes, the valid list changes. Product quantity, lot and expiry date are read from that branch's warehouse; a transfer between branches is a separate action.
Each branch's cash desk has its own opening and closing; a cash difference is attributed to the branch. The user's reports are limited to that branch's data, while a central role opens the consolidated view. An authorized call-center employee can see availability and calendars across branches and direct the patient to the most suitable branch.
One branch of the flow is critical: a user without membership cannot reach another branch's data; access is denied and written to the audit trail. See Multi-branch and central management for details.
Call centre: cross-branch calendar view if authorised
- The process is complete here.
All steps
- 01 A branch is selected (User)
- 02 Membership and permission check (role, branch, care relationship) (Access)
- 03 The price list changes for the branch (Price)
- 04 Warehouse and stock context (Stock)
- 05 Cash session (Cash)
- 06 Report scope (Report)
- 07 Call centre: cross-branch calendar view if authorised (Report)
Alternative path from 02 Membership and permission check (role, branch, care relationship); the process ends on this path.
- 02a No membership: access refused + audit record (Access)
07 Call centre: cross-branch calendar view if authorised
How the Clinic package is built for several branches
Clinic is not merely a bigger Pro; it adds multiple branches and central management to all the capabilities of Pro. When a second branch opens, you move to Clinic.
The package includes one legal organization, three branches, fifteen physician and fifty staff seats and eight specialty profiles. Extra organizations, branches and seats are added as extra capacity; specialty profiles can grow up to thirty-four. All capacity comes from the versioned plan catalog, and technical capacity is protected separately.
What opens in Clinic: consolidated finance, stock and reporting; stock transfer between branches; branch cash desk and consolidation; central roles and advanced policies; AI policy and a central quota by organization; Hekimiz pages by institution and branch and consolidated analytics. See Pricing for current prices. For single-branch teams the clinic and polyclinic solution is enough.
What the center sees
Central call center
Requests from phone, messages and the web are handled in one place. The call-center employee, within their permission, sees the calendar across branches and books the right branch according to the patient's preference and availability. Missed calls are recorded as tasks and leads. See Switchboard connection and Appointments and calendar.
Consolidated report
The center compares the branches' occupancy, no-shows, revenue, collections, stock use and service-level performance. A branch manager sees only their own branch. Exporting a report depends on permission and is recorded. See Reporting.
Connector fleet
An Edge Connector runs on each branch's clinic network; connection health, queue status and certificate expiry are monitored from the center, and updates are signed. The center can diagnose a faulty branch remotely. See Edge Connector and Device connections.
In addition there are branch-level cash desk, earnings and profitability on the finance side; multi-warehouse and inter-branch transfer on the stock side; and branch-level shifts and tasks on the staff side. See Finance and payments and Stock and purchasing.
Everything the center sees is recorded independently of the branch. Price and service changes have validity dates; when a price is updated in a branch, past accruals stay at the old price and new procedures are calculated at the new price. In the consolidated report, periods are then not mixed up.
Branch isolation and cross-branch permission
The question multi-branch clinics ask most is this: when a patient goes to another branch, they should be able to find their file, but branch staff should not see everything of each other. HekimBis balances these two needs with one rule.
Patient identity is organization-wide. The same patient is one identity across the branches of a legal organization, and no duplicate file arises. Access to the clinical record opens separately: to see an exam note in another branch, a user needs open membership, a duty or a care relationship, and permission suited to the sensitivity of the data. Sensitive notes can carry an extra segment. If access without a care relationship is needed, temporary access opens with a reason, a time limit and extra verification and leaves a separate audit record.
Between different legal organizations, patient or clinical access is not automatic; each extra organization is defined as a separate institution. This matters for groups that run several legal entities under one roof.
The branch manager manages their branch's calendar, staff, cash desk and report. Central roles provide the consolidated view and policy management. When a branch employee leaves, access closes immediately. See Roles and permissions and Security for role and permission details.
The checklist for opening a new branch is short but the order matters. First the branch record and working hours are defined; then the branch manager and staff are invited and their memberships and roles assigned; the price list is assigned to the branch; warehouse and minimum stock levels are set up; the cash desk officer and opening procedure are decided; if there is one, the Edge Connector and device connections are installed; the branch is made visible to the call center; and finally the branch's reporting scope and central consolidation are checked. Because every step is recorded, the question of when, by whom and with which settings this branch was opened never goes unanswered. See Multi-branch and central management.
Frequently asked questions
Why is the Clinic package needed for multi-branch clinic software?
Multiple branches, the central call center, consolidated reporting and branch isolation open in the Clinic package. A single-branch structure works with Pro; when a second branch opens, you move to Clinic.
Can we grow beyond three branches?
Yes; each extra branch is added as extra capacity. Capacity comes from the plan catalog, and technical capacity is protected separately.
If a patient moves from one branch to another, is the file moved?
It is not moved; identity is one across the organization. Access to the clinical record opens by the user's permission and care relationship.
Can branches have different price lists?
Yes; a price list can be separated by branch, physician or institution, and a validity date is defined.
Does moving from one branch to Clinic need a data migration?
No. An upgrade is a change of permissions and capacity on the same data. See How it works.
Can the center see the branches' cash desks?
The central role opens the consolidated finance and cash desk view; a branch manager sees only their own branch's cash desk. Each branch's cash desk has its own opening and closing.
How does stock transfer between branches work?
A transfer between branches is a separate action; the sending and receiving warehouses are recorded and the quantity is updated in both.
Related pages
Features
- Multi-branchBranch-level permissions, prices, stock, and cash with central call handling.
- Staff and operationsShifts, leave, tasks, device maintenance, calibration, and incident management.
- Reporting and analyticsOperations, clinical quality, finance, inventory, diagnostics, and messaging reports.
- Roles and permissionsRole families, branch and sensitivity context, break-glass access, full audit trail.
Solutions and process
Software guides
Guides
- Multi-Branch Clinic Management with Central Control and Local FlexibilityRunning several branches as one operation: shared patient records, branch-level cash and stock, role boundaries and consolidated reporting in a practical framework.
- Physician Revenue Share Calculation Guide on Rate, Basis and ReconciliationPhysician pay should be a calculation, not a debate. Collection or charge basis, cost deductions, and what happens with cancellations and refunds.