A hospital or clinic group is not buying several copies of the same software. It is buying the layer above the locations — one negotiated payer contract set applied everywhere, a consolidated leakage view with per-branch comparison, cross-branch patient records, and central administration.
The question only a group owner has
"Which of my six branches is losing the most, and why" is a question a single-site hospital never asks and no single-site system answers. It is also the question that decides where a group owner spends their attention this quarter.
Answering it requires the branches to classify deductions the same way. If branch three calls something a tariff mismatch and branch five calls the same thing a documentation issue, the comparison is noise. Shared taxonomy comes before shared reporting.
Negotiate once, apply everywhere
A group negotiating with a payer once and applying the result across six branches has real leverage. Six branches each negotiating separately have none, and typically end up on six slightly different rate cards — which then drift apart further at each revision.
This is the clearest commercial argument for the group layer, and it is measurable: compare your best branch rate against your worst for the same payer and the same procedure. The gap is what fragmented negotiation has cost you.
What breaks when two branches become six
| At two branches | At six |
|---|---|
| The owner sees every claim | Nobody sees every claim |
| One rate card, informally shared | Six rate cards, silently diverging |
| A patient is at one branch | A patient is at whichever is nearest today |
| Roles are informal | Roles need to be actual permissions |
| One consolidated view by memory | Consolidation requires a system |
The transition is usually felt at branch four or five, and it arrives as a general sense that things are slipping rather than as a specific failure. That is what makes it hard to act on in time.
One patient, six branches
Cross-branch records matter clinically and commercially. Clinically because a patient seen at three locations has one history, not three. Commercially because duplicate records inflate your patient count, break your recall lists, and make follow-up campaigns target people who already came back.
A single ABHA linkage per patient across branches solves most of this, and it is worth doing before the duplicates accumulate rather than after.
Central administration without central bottlenecks
The failure mode of group software is that everything routes through head office and every branch waits. The useful split: contracts, tariffs, roles and reporting centrally; clinical and billing operations locally.
A branch manager should not need permission to run their day. They should be unable to alter a payer contract.
What a group should measure
- Leakage per bed-day by branch, not absolute leakage — otherwise the biggest branch always looks worst.
- Rate-card divergence for the same payer and procedure across branches.
- Duplicate patient rate across the group.
- Time from contract revision to rate-card update, per branch. This is where tariff drift starts.
More in this cluster: Groups & multi-branch — every article we have on it.
Questions we get asked
Why does a group pay more than the same number of standalone sites?
Because it is buying the layer above the locations — one negotiated contract set, consolidated leakage comparison, cross-branch records and central administration. Per-location rates fall as branches are added; the platform fee covers the layer.
What is the strongest argument for group software?
Per-branch leakage comparison. Which branch is losing the most and why is a question only a group owner has, and one nobody else currently answers.
When does a growing group need this?
Usually at branch four or five, when nobody can see every claim any more and rate cards start diverging silently.
Read next
See it against your own settled claims
Twenty claims you have already settled, showing what was disallowed, how much was predictable, and how much the payer never explained. About an hour of your team’s time.