Hospital Management System
for Saudi Arabia
NPHIES is mandatory across every facility in the Kingdom, and CBAHI accreditation has been compulsory since 2013. careup.ai is NPHIES integrated, CBAHI-ready and Arabic-first — running today across four countries and five national health platforms.
What the Kingdom Actually Requires
Four bodies shape what your hospital information system has to do in Saudi Arabia. A vendor who cannot name all four has not sold here.
NPHIES
National Platform for Healthcare Information Exchange Services
Saudi Arabia's national exchange, formed by merging the SeHE clinical and SHIB financial programmes. It is mandatory across every government and private facility in the Kingdom — eligibility checks, prior authorisation and claims all flow through it in HL7 FHIR R4.
CBAHI
Central Board for Accreditation of Healthcare Institutions
Accreditation has been mandatory for every healthcare facility in the Kingdom since Cabinet Decree No. 371 of 2013. CBAHI standards reach deep into documentation, medication safety, infection control and patient rights — all of which your HMS either supports or obstructs.
CHI
Council of Health Insurance — formerly CCHI
The insurance regulator. Private facilities treating insured patients are licensed by the MOH and then accredited by CHI. Your claim workflows, pre-authorisation and payer rules live under its rules.
Wasfaty
National e-prescribing service
The MOH's national e-prescribing platform, launched in 2019 and mandatory for prescribers and pharmacies. Exposure differs between public primary care and private hospitals — worth scoping explicitly for your facility rather than assuming.
Six Questions to Ask Any NPHIES Vendor
“NPHIES ready” is a marketing phrase. These are the things that actually have to be true.
MOH conformance certification
Production connectivity is gated behind MOH conformance testing. No vendor connects a live facility without passing it — ask for evidence, not a claim.
HL7 FHIR R4 to NPHIES Implementation Guides
Not generic FHIR. NPHIES publishes its own profiles, and conformance is measured against those specific guides.
National ID and Iqama identity matching
Patient identity resolves against Saudi National ID for citizens and Iqama for residents. Registration workflow has to enforce it at the front desk.
Electronic claims and prior authorisation
Eligibility checks, pre-authorisation requests and claim submission all run through NPHIES rather than payer-by-payer portals.
Drug and formulary coding
Medication data must be coded to national standards for claims to adjudicate rather than reject.
Arabic clinical documentation
Arabic-first records, not an English system with Arabic labels bolted on. It shows immediately in a demo, and Saudi evaluators look for it.
Typical timeline. NPHIES implementation runs 8–12 weeks for a new Saudi facility, including regulator testing. We handle claims format mapping, conformance testing and go-live support alongside workflow configuration.
Four Regulators, One System
Saudi Arabia is the largest healthcare market in the GCC and the most actively restructured. The Health Sector Transformation Programme under Vision 2030 is moving the Ministry of Health out of direct service delivery and into a purchaser-regulator role, with care delivered through accountable clusters and an expanding private sector. For hospital operators, the practical consequence is that the regulatory surface has grown rather than shrunk: you now answer to the MOH for licensing, CBAHI for accreditation, CHI for insurance practice, and NPHIES for every claim you submit.
That fragmentation is the core difference from Qatar. In Doha a facility maintains one primary regulatory relationship; in Riyadh it maintains four, each with its own standards, audit cycle and evidence requirements. A hospital information system that satisfies one and obstructs another creates real operational cost — most visibly when CBAHI documentation standards and NPHIES claim requirements pull clinical staff in different directions at the point of care.
NPHIES is the unavoidable one. It is mandatory across government and private facilities, it is the sole route for eligibility checks, pre-authorisation and claims, and conformance is measured against its own published FHIR implementation guides rather than generic HL7. A system that cannot demonstrate live NPHIES conformance is not a weaker option in Saudi Arabia — it is not an option.
What a Saudi Deployment Involves
Typically 8 to 12 weeks for a new facility including regulator testing. Migration and broad specialty mixes extend that, and we scope both before quoting a date.
Regulatory position and scope assessment
We map your MOH licensing scope, CBAHI accreditation cycle and CHI standing against what the system has to support, and identify the gaps. Facilities mid-way through an accreditation cycle have different sequencing constraints than new builds, and that changes the plan.
NPHIES conformance and payer configuration
Claims and pre-authorisation are mapped to the NPHIES FHIR R4 implementation guides, patient identity is wired to National ID and Iqama matching, and your payer mix and benefit rules are configured. CHI testing runs inside this phase rather than after it.
Clinical configuration against CBAHI standards
Documentation templates, medication safety checks, infection-control recording and patient-rights workflows are configured so that CBAHI evidence is a by-product of normal clinical work rather than a separate exercise before each survey.
Arabic-first rollout and data migration
Clinical documentation, patient communication and printed output are configured in Arabic with English alongside. Historical records, open encounters and outstanding claims are migrated and reconciled in the same pass.
Parallel run, conformance testing and cutover
Both systems run in parallel over an agreed window with claims reconciliation against NPHIES responses, so revenue exposure is visible before cutover rather than discovered after it.
What We Claim — and What We Don't
Saudi tenders attract a lot of claimed NPHIES integration. Here is exactly where careup.ai stands, including the line we do not cross.
Five National Platforms, Four Countries
If your group operates in more than one GCC market, this is the argument that matters. One platform, each facility against its own regulator.
NPHIES
Saudi ArabiaDirect integration for electronic claims and pre-authorisation, with CHI testing handled as part of implementation.
QHIE-Hub
QatarIntegrated with Qatar's national health information exchange over HL7 FHIR, with Qatar national coding standards applied.
Malaffi HIE
Abu DhabiLive integration with Abu Dhabi's health information exchange, including UMRN support.
Nabidh HIE
DubaiLive integration with Dubai Health Authority's exchange platform.
ABDM — M1, M2, M3
IndiaCertified across all three milestones by the National Health Authority.
The multi-country question. Most groups running facilities in Riyadh and Doha, or Jeddah and Dubai, operate separate systems per market — or force one system to approximate compliance in the others. careup.ai runs all of them from a single multi-location command centre, each configured to its own regulatory profile.
Saudi Questions, Answered
Is careup.ai NPHIES integrated?
Yes. careup.ai submits electronic claims and pre-authorisation requests through NPHIES in HL7 FHIR R4, with patient identity matched against Saudi National ID and Iqama. CHI testing is handled as part of implementation. NPHIES is mandatory across every government and private facility in the Kingdom, so this is a threshold requirement rather than a differentiator — but plenty of vendors bidding in Saudi Arabia still cannot demonstrate it.
How long does a Saudi implementation take?
Typical NPHIES implementation runs 8 to 12 weeks for a new facility, including regulator testing. That covers claims format mapping, conformance testing and go-live support alongside configuration of your clinical and billing workflows. Timelines extend where a facility is migrating historical data or running an unusually broad specialty mix.
Does careup.ai support CBAHI accreditation?
Yes. CBAHI accreditation has been mandatory for all Saudi healthcare facilities since Cabinet Decree No. 371 of 2013, and careup.ai supports the documentation requirements — quality indicator tracking, complete audit trails, medication error and adverse event reporting, infection control surveillance, patient rights documentation and staff credentialing records. The accreditation is yours to earn; the evidence trail is what we provide.
Is the system genuinely Arabic, or English with Arabic labels?
Arabic-first clinical documentation runs in production across our GCC deployments — clinical records, patient communication and printed documentation, alongside English and additional languages. Ask for a live Arabic demo rather than screenshots; the difference between a genuinely bilingual system and a translated interface becomes obvious within a minute.
What about Wasfaty e-prescribing?
Wasfaty is the MOH's national e-prescribing service, mandatory for prescribers and pharmacies since its 2019 rollout. Exposure differs meaningfully between public primary care facilities and private hospitals, so we scope it explicitly per facility rather than assuming a single answer. Raise it early in your evaluation — with us and with every other vendor.
Can careup.ai replace an existing HIS in a Saudi facility mid-accreditation?
It can, but the sequencing matters and we will tell you if the timing is wrong. CBAHI surveys assess evidence generated over a period, so a cutover shortly before a survey creates a documentation discontinuity that is avoidable by waiting. Where a facility is close to a survey date, we usually recommend running the migration immediately after it rather than before, even though that defers the project.
What actually breaks when NPHIES conformance is wrong?
Claims reject, and they reject silently in ways that surface weeks later as revenue gaps. The common failure modes are profile non-conformance against the NPHIES implementation guides, identity mismatches between National ID and Iqama records, and benefit or eligibility data that is stale at the point of pre-authorisation. This is why we reconcile claims against live NPHIES responses during parallel running rather than testing conformance in isolation and assuming production will behave the same way.
How does this work for a group operating in both Saudi Arabia and the UAE?
Each facility runs against its own regulatory profile — NPHIES in the Kingdom, Nabidh in Dubai, Malaffi in Abu Dhabi, QHIE-Hub in Qatar — while the group sees one consolidated operational and financial picture across all of them. That is the case careup.ai is genuinely built for, and it is a materially different proposition from running four separate systems and reconciling them in a data warehouse afterwards.
What does the Kingdom require on data residency?
Health data handling in Saudi Arabia is governed by the Personal Data Protection Law alongside sector guidance, and the practical expectation for patient data is in-Kingdom residency. We confirm the residency arrangement per deployment as part of contracting rather than making a blanket claim here, because the answer depends on your facility type, your payer relationships and the deployment model you choose.
Can one platform run our Saudi and other GCC facilities?
Yes, and it is where careup.ai is genuinely differentiated. We are integrated with NPHIES in Saudi Arabia, QHIE-Hub in Qatar, Nabidh in Dubai and Malaffi in Abu Dhabi. A group operating across those markets runs each facility against its own regulatory profile from a single multi-location command centre — one platform, not four systems stitched together.
More across the GCC
HMS for Qatar
QHIE-Hub integration, MOPH licensing and Qatar's national coding standards.
ReadHMS for Qatar
QHIE-Hub integrated and MOPH compliant — the neighbouring GCC market, on the same platform.
ReadCompliance & certifications
NPHIES, QHIE-Hub, DHA, DoH, ABDM, NABH and JCI — every market we serve.
ReadEvaluating an HMS in the Kingdom?
Our GCC team will walk through NPHIES onboarding for your facility, CBAHI evidence requirements, and a live demo in Arabic — not a translated deck.