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 set of settings. ID numbers and the rules that check them. The regulator and how it inspects. Professional registers, national coding systems, data protection law and the body that enforces it. Legal deadlines, counted in working days or calendar days. And the currency.
A national deployment keeps the data inside the country’s own borders, and the country profile records where it lives.
Sovereign hosting
A national deployment inside the country’s own boundary, running the same images we run.
Data residency
Recorded for each country and available through the API — which also says plainly that recording a rule is not the same as enforcing it.
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 services, national registers and summary reporting, on connections that are not always reliable.
Caribbean
Ministry-scale platforms for small island systems, where referring someone off the island is a normal route, not 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.