Know where your healthcare data will live
NextHealth hosts data in the UAE. For other markets, the hosting approach uses a country’s own cloud region where required, with deployment details, continuity arrangements and exit scope reviewed before agreement.
Confirm location before agreeing the deployment
NextHealth’s hosting approach is UAE data hosting, with a local cloud region used in other countries where required. For Saudi Arabia the proposed approach is in-Kingdom hosting. This is the approach we review with you for a project. It is not a statement that every market already has an active customer deployment, and a country’s hosting is committed only once a deliverable configuration is agreed.
Region, cloud provider, environments, backups, support access and external services are each decided for your deployment and recorded in the agreement. The location of the production database does not answer every residency question, so review every supporting copy and service together.
The uptime commitment is 99.9%. It is a stated service commitment, not a measured historical availability result. Agree how it is measured, the exclusions and any service credits in the contract, alongside the continuity and exit terms your organisation needs.
Hosting by market
Use this as the starting point, then agree the exact arrangement for your facility and the services it will use.
- United Arab Emirates
- UAE hosting is the starting position for UAE deployments. Agree the exact region and provider, including backups and supporting services, in the deployment scope.
- Saudi Arabia
- The proposed approach is in-Kingdom hosting. It is confirmed for a project only when a deliverable configuration is agreed, so this page makes no country-specific commitment.
- Other markets
- A country’s own cloud region is proposed where required. Review each market individually. Hosting in a country is committed only once a deliverable configuration exists for it.
- Cross-border operations
- Shared product architecture does not imply unrestricted movement of patient data. Confirm permitted access and information flows separately for each organisation, country and external service.
Decisions to settle before go-live
Each item shows what NextHealth states now and where the answer is fixed. Open items are decisions for the deployment agreement. Nothing here is assumed.
- Region
- Stated now: UAE hosting for UAE deployments, with the proposed approaches above for other countries. Settled in: the deployment scope, before agreement.
- Cloud provider
- Stated now: this page names no provider. Settled in: confirm the cloud provider, region and supporting services for your proposed deployment with our team before agreement.
- Subprocessors and external services
- Stated now: not listed on this page. Settled in: ask our team for the subprocessors and external services in your proposed deployment, including any with support access, and record them in the agreement.
- Backups
- Stated now: no backup schedule is published. Settled in: the deployment scope, which sets frequency, retention and where each backup copy is held.
- Recovery objectives
- Stated now: none is published. The 99.9% uptime commitment is not a substitute for them. Settled in: the recovery point and recovery time objectives agreed with the recovery arrangements.
- Data export and deletion
- Stated now: Flow offers Excel and PDF exports for described workflows, and no full exit dataset or deletion timetable is published. Settled in: the contract, which sets export formats, attachments, data return, notice and deletion.
Common questions
-
UAE hosting is confirmed. In other markets, the stated approach uses local cloud regions where required, including in-Kingdom arrangements for Saudi deployments. Confirm the exact project configuration before agreement.
-
Confirm the cloud provider, region and supporting services for your proposed deployment with our team before agreement.
-
It is our uptime commitment for the hosted service. How availability is measured, what is excluded and any service credits are set out in your agreement.
-
Backup frequency, recovery point objective and recovery time objective remain to be confirmed. Agree them alongside retention, recovery arrangements and responsibilities before implementation.
-
Full exit scope must be agreed, including datasets, formats, attachments and assistance. Available operational exports do not by themselves establish complete platform migration or an open-format exit service.
Not answered here? Contact the team
NXH Flow