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
The owner-confirmed hosting position is UAE data hosting, with local cloud regions used in other countries where required. Saudi deployments are described on an in-Kingdom basis. This is the hosting approach to review for your project, not a claim that every proposed market already has an active customer deployment.
Confirm the exact region, cloud provider and environments covered by the agreement. Include backups, support access and any external services in that discussion rather than assuming the production database location answers every residency question. The brief does not identify a provider or establish the locations of every supporting copy and service.
The uptime commitment is 99.9%. It is a stated service commitment, not a measured historical availability result. Agree how it is measured, the applicable exclusions and any service credits in the contract, alongside the continuity and exit terms needed by your organisation.
Hosting scope by deployment
Use the confirmed hosting approach as the starting point, then agree the exact arrangement for the facility and the services it will use.
- United Arab Emirates
- UAE hosting is confirmed by the owner. Agree the exact region and provider, including the treatment of backups and supporting services, in the deployment scope.
- Saudi Arabia
- The stated approach for Saudi deployments is in-Kingdom hosting. Confirm the region, provider and service arrangements for the project before making a country-specific contractual commitment.
- Other markets
- The approach uses a country’s own cloud region wherever required. Review each proposed market individually rather than assuming an existing deployment or universally available regional footprint.
- 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.
Agree continuity and exit before go-live
These are matters for the deployment agreement. No backup schedule, recovery target, open-format migration service or notice period is invented.
- Backup arrangements
- Confirm the backup frequency, retention and storage location for the deployment. The supplied brief does not establish these details or prove a particular backup configuration.
- Recovery objectives
- Agree recovery point and recovery time objectives with the supporting recovery arrangements. The 99.9% uptime commitment is not a substitute for those separate targets.
- Data export and handover
- Flow provides Excel and PDF exports for described workflows. Confirm a full exit dataset, formats, attachments and migration assistance separately rather than assuming complete platform portability.
- Contractual exit terms
- Agree notice, access during transition, data return and deletion arrangements in the contract. No fixed notice period or automatic deletion timetable is stated here.
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.
-
The cloud provider is not identified in the supplied brief. Ask the team to confirm the provider, region and supporting services for the proposed deployment.
-
It is the owner-confirmed uptime commitment, not a published historical performance result. Measurement, exclusions and service credits must be established in the applicable 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.
Review the hosting and continuity scope
Bring your residency, recovery and exit requirements. Confirm the proposed deployment and contractual terms before your organisation relies on them.