How do I connect two or more branches on one system? — answered by Engineer Saeed Baatiah
The first decision is where the data lives: on a server in one branch, or in the cloud. Cloud suits most multi-branch facilities, because each branch connects to it directly, whereas a local server makes the other branch hostage to the first branch’s connection and power. And what gets settled before connecting: whether a branch sees other branches’ data or only its own — a permissions decision rather than a network one.
The data-location decision precedes everything and is hard to reverse. A local server in one branch means the second branch stops when the first branch’s internet or power fails — one site’s outage taking down two. The cloud solves that because each branch connects independently, and in exchange a branch’s internet loss disables only that branch, a smaller harm mitigated by a backup line.
And what gets settled before connecting is a permissions decision rather than a network one: does a branch employee see other branches’ patient data? The default answer should be no, with an explicit exception for a patient visiting another branch. Its counterpart is a management question: does the manager see all branches in one dashboard? Yes — and that is the real benefit of unification.
And three things are forgotten in branch-linking projects: patient numbers must not collide between branches (two branches both starting at 1 produce a conflict that is painful to unpick later), stock is managed per branch with a unified view, and reports need a branch filter or the aggregated figures carry no operational meaning.
- Cloud stops one branch’s outage from disabling the others
- Default: a branch does not see other branches’ patient data
- Unify patient numbering upfront — collisions are painful to unpick