Skip to content

Create an account

HekimBis home

Central management for multi-branch clinics

Your branches are not separate programs but parts of one organization. When you move from one branch to another, permissions, price list, stock warehouse, till and report scope move with you. The center sees the call center, finance and stock for all branches together.

Night in a central clinic office: a manager pins blank markers to a wall map
A headset-wearing agent in a central call center routing a patient while checking several branch calendars

The center manages the branches together with four tools

Clinic adds multi-branch and central operations on top of everything in Pro.

Appointments and calendarReporting and analytics

Central call center
The call center sees the calendars of the branches it is authorized for on one screen, directs the patient to the most suitable branch and books the appointment there. Which branch calendars it can reach is set by permission.
Consolidated finance and stock
Revenue, collections, debt and stock are kept per branch and seen combined at the center. Each branch has its own till, and stock transfers between branches are recorded.
Organization policy
Price lists, automation rules and permission policy are defined at the center and applied to the branches.
Branch connection fleet
The device connection (Edge Connector) at every branch is monitored for health from the center; you can see which connection at which branch has a problem.

What changes when you switch branch?

Choosing a branch is more than a filter; it changes the whole working context. Your membership and permissions are checked first; then that branch's price list, stock warehouse, till session and report scope open. If you have no membership, access does not open and the attempt is written to the audit log.

User07End

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.
See Appointments and calendar
7 / 9

All steps

  1. 01 Branch selected (User) The user picks another branch from the branch switcher.
  2. 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.
  3. 03 Price list switches (Price) The effective price list of that branch (or physician, or institution) opens.
  4. 04 Warehouse and stock context (Stock) Procedures draw from that branch's warehouse; cross-branch transfers are on record.
  5. 05 Cash session (Cash desk) Collections are written to that branch's open cash session.
  6. 06 Report scope (Report) Reports open for the branch scope within your authority.
  7. 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.

  1. 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

Access to another branch's patient needs explicit membership

In a multi-branch organization the patient record is organization-wide, so a patient's file is not opened again when they move from one branch to another. That does not mean every employee can reach every patient at every branch. Patient and clinical access between different organizations does not open without explicit permission.

Roles and permissions
Organization-wide patient
A patient is recognized across the organization with one identity; no duplicate file is opened, and when the patient visits another branch the appointment is booked on the same record.
Branch membership and role
Each employee's branch membership and role are defined separately; the Clinic plan does not automatically give anyone clinical authority at all branches.
Access across branches
Access to a patient at another branch opens by explicit membership, assignment or care relationship, and a rule that looks at data sensitivity.
Rejected attempts
A rejected access attempt is written to the audit log; in consolidated reports, small groups are not shown on screen.

Adding a branch means growing inside the same organization

An organization that starts with one physician continues with Lite, with a second physician and a team with Pro, and with a second branch with Clinic. Clinic includes three branches; more are opened as additional branches. An upgrade changes the permission and capacity set on the same organization; existing patient, clinical, finance and audit data stays in place.

A price list can be defined by branch, physician or institution, and when you switch branch the valid list changes by itself; each branch's till session is separate. The opening of a branch and the setup plan are prepared together in the demo, according to your clinic's structure.

Multi-branch clinicPricing

A clinic owner and an architect discussing a new branch's reception area

Frequently asked questions

See all questions
Can branches have different price lists?

Yes. A price list can be defined by branch, physician or institution and has a validity date. When you switch branch, the valid list changes automatically.

Is each branch's till separate?

Yes. A till session is tied to a branch; the consolidated view is combined at the center.

Can stock be moved between branches?

Yes. The Clinic plan has multiple warehouses and transfers between branches; a transfer is made as a recorded movement.

Which branches' calendars does the call center see?

Only the branches it is authorized for. Permissions are defined at the center, and an unauthorized branch's calendar is not visible.

How long does it take to add a new branch?

The Clinic plan includes three branches; more are opened as additional branches. Because opening a branch and setup time depend on the clinic's structure, they are planned together in the demo.

If I move from Pro to Clinic, is my data migrated?

No migration is needed. An upgrade changes the permission and capacity set on the same organization; existing patient, clinical, finance and audit data stays in place.

If a patient moves from one branch to another, is their file opened again?

In a multi-branch setup the patient record is organization-wide; when a patient visits another branch, the appointment is booked on the same record and no duplicate file is opened. An employee at another branch has their access to that patient checked separately by membership, assignment or care relationship, and the data sensitivity rule.

Who can see consolidated reports?

The consolidated branch comparison is part of the Clinic plan. A user sees combined figures only for the branches they are authorized for; small groups that risk re-identification are not shown on screen.