Skip to content
Gulf Cooperation Council

Hospital information systems for the GCC

We offer HIS software for Gulf care teams to link patient and business records, with each country’s rules and rollout needs reviewed on their own terms.

The Gulf Six member states

Best fit: a group working across Gulf countries

A healthcare group that wants consistent clinical and business workflows across the Gulf, but whose facilities do not operate under one regional rulebook. The GCC comprises the UAE, Saudi Arabia, Oman, Qatar, Kuwait and Bahrain. Licensing, coding, payer arrangements, data rules and national-platform onboarding are assessed country by country. This page is a regional overview, and each country has its own page.

Common foundation, and what stays local

  • No single configuration: No single GCC-wide configuration is offered. The common product foundation is Care for clinical and billing work, Engage for patient relationships and Flow for operational evidence. NXH One connects their shared patient, staff, facility and encounter records when products are combined. That shared model does not mean unrestricted movement of patient data between countries.
  • Confirmed connectivity: Care supports Malaffi and NABIDH connectivity within agreed scope. Other named national routes require specific confirmation of the proposed connection, transactions and facility activation.
  • Hosting: UAE hosting is confirmed. Other markets use an in-country cloud region wherever regulation requires it, with scope agreed per market.
  • Interface language: The current product interface is English. An Arabic interface is not claimed.

The local workflow

The platform names shown on the country pages describe the market environment, not a list of confirmed live NextHealth connections. General HL7, FHIR or ICD-10 support does not establish every national profile or coding variant.

NextHealth Technologies is the software division of Alpha Health Group, a healthcare operator based in Abu Dhabi and Dubai. Experience running facilities and consulting on accreditation informs the questions we bring to implementation: who records the work, who reviews it and what evidence remains.

Compare the main readiness questions by country

  • UAE: which emirate and regulator, which clinical exchange (Malaffi, NABIDH, Riayati) and which claims route (DHPO/eClaimLink, Shafafiya)?
  • Saudi Arabia: which NPHIES transactions and coding sets, and which in-Kingdom hosting arrangement?
  • Oman: is Dhamani in scope, separately from Al Shifa and NEHR, and which data processing permit applies?
  • Qatar: which QHIS requirement and coding variant apply for an insured clinic or a hospital?
  • Kuwait: a planned market. Which insurer or TPA process applies, and which data must be exchanged?
  • Bahrain: part of the regional context. A dedicated Bahrain implementation requires separate scoping.

Where the products fit

Care Clinics supports outpatient documentation and billing. Care Clinics Pro adds laboratory, radiology and claims records. Care Hospitals adds inpatient and nursing work. Engage supports booking, packages, memberships and patient relationships for private clinics. Flow provides document control, policy approvals, credentials, incidents, complaints and risk actions. National reporting and accreditation requirements still need their own evidence review. Choose the scope around your facility’s actual services.

Flow Quality indicators is still being completed. Review its availability separately before a rollout depends on it.

Define a rollout for each country

Choose one facility and a representative patient, payer and quality workflow. Agree the hosting region, access, backups and any transfer arrangements for each deployment, then define the additional configuration and assessment needed before extending the approach to another country. Start with the UAE, Saudi Arabia, Oman or Qatar page for the local discussion.

Bring three things to your GCC demo

A useful first conversation starts with your own work, not a feature list.

Book a demo
  1. A patient encounter

    One representative visit, from registration to the signed clinical record.

  2. A payer or payment workflow

    The claim, invoice or package your team handles most, and the response it needs.

  3. An evidence question

    One licensing, quality or inspection requirement you need to be able to show.

What your teams can run in the GCC

Each product is selected and scoped on its own. These are the modules most relevant to the GCC, with how each one is bought.

NextHealth Care

Keep registration, clinical notes, prescriptions and billing on one patient record, with plans for outpatient clinics and hospitals.

5 modules most relevant to the GCC

NextHealth Flow

Keep documents, workforce records, incidents and quality work organised across your facilities, starting with the modules you need.

4 modules most relevant to the GCC

Running more than one product? NXH One connects their shared patient, staff and facility records. Explore NXH One

Common questions

  • No single regional configuration establishes every country’s requirements. NextHealth offers a shared product foundation, while licensing, coding, claims, hosting and national-platform onboarding need separate assessment for each facility and country.

  • No unrestricted cross-border access is implied. Agree each deployment’s hosting, permissions, processing purposes and transfer conditions before enabling any group workflow that involves patient information across countries.

  • Care supports Malaffi and NABIDH connectivity within agreed scope, with facility activation still reviewed. Other named national routes require specific confirmation. General exchange capability does not establish every country’s profile or operational connection.

  • NextHealth is the software division of UAE-based Alpha Health Group. This page does not claim offices, partners or customers in every GCC country. Discuss the actual implementation and support arrangements for your project.

  • The current product interface is English. An Arabic interface is not claimed. Staff language, patient documents and training requirements should be reviewed before agreeing a regional or country rollout.

  • Choose one facility and a representative patient, payer and quality workflow. Review the available modules and local requirements, then define the additional configuration and assessment needed before extending the approach to another country.

Regulatory references 4

Not answered here? Contact the team

Our clients

See every client

Bone Care One Day Surgery Center

Review your GCC implementation scope

Bring one patient journey, one payer workflow and one evidence question. We will review the scope your facility needs in the GCC.