A country is a configuration, not a release.
Identifiers, regulators, registers, coding systems, data-protection law, statutory clocks and currency — all read from a governed record.
One platform, configured per country
A country is a configuration: identifiers with their check-digit rules, the regulator and its inspection framework, professional registers, national coding systems, data-protection law and its supervisory authority, statutory clocks with their working-or-calendar-day basis, and currency.
Sovereign deployment keeps the data inside the country’s own boundary, with residency recorded in the jurisdiction profile.
Sovereign hosting
A national deployment inside the country’s own boundary, running the same images we run.
Data residency
Recorded per jurisdiction and surfaced in the API — which also states plainly that recording is not the same as enforcing.
Multilingual
Language is a configuration value, and a jurisdiction may carry more than one.
Open standards
The exit is designed in. A ministry should be able to leave a supplier without leaving its data.
Middle East
National health transformation programmes, regional cluster structures and bilingual deployment.
Africa
Public health delivery, national registries and aggregate reporting, on infrastructure that is sometimes intermittent.
Caribbean
Ministry-scale platforms for small island systems, where off-island referral is a first-class pathway rather than an exception.
What is configured, and what is deployed
Several international jurisdictions are configured and demonstrable in the product today. That is not the same as deployed, and this page does not claim a live national deployment anywhere in these regions.
The distinction matters to a ministry evaluating risk, and blurring it is the fastest way to lose a procurement on the second question.