One product, six jurisdictions, and data that is not allowed to leave the country.
At this scale the hard constraints are legal, not clinical. A group operating in the UAE, Saudi Arabia, India, the EU and Canada must satisfy five residency regimes, five regulators and five clinical coding conventions — without running five systems.
Every country adds a system, and consolidation stops being possible.
Acquisition by acquisition, the group inherits a scheduler here, a rehab system there and a spreadsheet somewhere else. Group reporting becomes a monthly reconciliation exercise, always six weeks late and never trusted enough to act on.
The naive fix — one global database — fails on residency the day a regulator asks where the personal data physically sits.
- —Residency rules blocking a single consolidated instance
- —Group KPIs assembled by hand from incompatible exports
- —Every country with its own identity provider and role model
- —Clinical terminology and outcome measures not comparable across regions
Three areas of the platform carry this.
The rest of the product is present and dormant. These three are the reason you would move.
Region-pinned data with federated reporting
Patient-identifying data stays in its jurisdiction. Aggregate operational metrics federate upward without moving personal data across a border — one group view, no residency breach.
Multi-currency, language and regulatory profiles
Currency, language, calendar, working week, terminology set and regulatory profile are facility-level configuration. A Riyadh site and a Toronto site run the same build with different rules.
Deployment topology by jurisdiction
SaaS multi-tenant, dedicated tenant, single-tenant private cloud, sovereign or air-gapped on-premise — chosen per region, managed as one estate, upgraded on one release train.
What your tenant hierarchy looks like.
Region is a residency boundary first and a reporting tier second. Nothing crosses it that is not aggregate.
Numbers, with the assumptions attached.
Modelled on a group operating 214 facilities across five residency regimes, consolidating from eleven inherited scheduling systems.
- One product, per-region topology
- Federated KPIs at T+1
- SSO federation, one role model
- Residency solved by design
These are modelled figures, not a named customer result. Every input is stated so you can substitute your own; where a range is meaningful we publish the sensitivity rather than a single confident number.
Bring one week of real demand to a demo and we will rerun the model live on your data.
See what it costs →The questions this room always asks.
Only where that region's law and your policy allow it. By default the group tier sees aggregate operational metrics; patient-level access is granted within a region, logged, and reviewable.
You may be more than one of these.
Map your estate against residency.
Bring your country list and your regulators. We will draw the topology and the reporting boundaries with you.