SECTOR / 03 Industry

Healthcare, built around the clinician.

Clinical AI, hospital operations, and population-health platforms aligned to the Health Sector Transformation Program. We build alongside MoH, CCHI, NUPCO, and the cluster operators — designed so the clinician spends less time documenting and more time with patients.

Beds under coverage
8,400+
Active programs
17
Clinician hours saved / wk
11.4
Avg. ED throughput lift
+22%
الصحةHEALTHCARE · KSA
STEWARDSMoH · CCHI · NUPCO
OPERATING MODELCluster-based
HSTP TARGETPrivatization · clusters
POSTUREHIPAA + PDPL
01 / The brief

What healthcare actually feels like in the Kingdom.

Six pressures we hear from CMOs, cluster CEOs, and CIOs on every first call.

01 /

HSTP cluster transition

The Health Sector Transformation Program is reshaping public healthcare into independent clusters. The IT, data, and revenue-cycle stack inherited from the Ministry was never designed for this operating model.

→ Cluster-native architecture
02 /

Clinician burnout

Saudi clinicians spend 38–52% of their day on documentation. Ambient scribing, structured-note generation, and order-entry copilots are the highest-ROI AI investment a hospital can make.

→ ~11 hrs / wk reclaimed
03 /

ED & throughput

Tertiary EDs run at 110%+ of design capacity. Predictive triage, bed-management, and discharge-planning AI move the throughput needle in a way new buildings cannot.

→ +22% throughput lift
04 /

Imaging volume

Radiology and pathology volumes outpace specialist supply. Computer-vision triage for chest X-ray, CT, mammography, and dermatology is now standard of care, not a research project.

→ Triage-grade CV
05 /

PHI & PDPL

Patient-health data is the most sensitive class under PDPL. Models trained on Saudi cohorts, governed under NDMO classification, and audited per MoH protocols — not models trained on Boston EHRs and rebadged.

→ Saudi-trained · in-Kingdom
06 /

Population health

Diabetes, cardiovascular, and obesity prevalence in Saudi cohorts demand population-level analytics, not just episodic care. Risk-stratification has to feed primary care, not radiology dashboards.

→ Risk-strat → primary care
02 / Service mapping

How our service lines land in healthcare.

Six disciplines, sector-tuned around the clinical workflow and the cluster operating model.

03 / Flagship deployments

Where it has actually shipped.

Two engagements that anchor our healthcare practice. Names redacted under MNDA — the cluster CEOs know the work.

CASE / 01 · TIER-1 CLUSTER

Bilingual ambient scribe

8 hospitals · 3,200 active clinicians · live Q4 2025

Ambient documentation that listens to the clinical encounter in mixed Arabic-English code-switching, drafts a structured note in seconds, and posts it to the EMR with order-entry suggestions. Built on a Saudi clinical-language corpus we trained ourselves; clinician retains the pen at every step.

11.4hRECLAIMED / WK
97%NOTE ACCEPTANCE
2.1sDRAFT LATENCY
4.6★CLINICIAN NPS
CASE / 02 · TERTIARY ED

Predictive ED throughput

580-bed tertiary · live since Q2 2025 · scaled across cluster

An ED operations platform with live arrival forecasting, acuity-aware triage decision support, and discharge-readiness scoring. Bed-management is no longer a whiteboard exercise — it is a 15-minute-horizon model the charge nurse trusts.

+22%THROUGHPUT
−31%LWBS RATE
−47minDOOR-TO-DOC
0SAFETY EVENTS
04 / Compliance posture

The frameworks we operate inside.

MoH Standards
CCHI
CBAHI
NUPCO Integration
PDPL
NDMO Classification
HIPAA-equivalent
HL7 FHIR R4
DICOM
ISO 27001
ISO 13485
IEC 62304
05 / Ecosystem

Who we work alongside.

Authorities, EMR vendors, and the partners we integrate with at the cluster level.

AuthorityMoH
AuthorityCCHI
AuthorityNUPCO
EMREpic
EMROracle Cerner
EMRInterSystems
PACSSectra · Agfa
Sovereign Cloudstc cloud
06 / FAQ

Common questions.

Are your models trained on Saudi cohorts?

Yes — and we say so explicitly. Models trained on Boston or London EHRs perform poorly on Saudi clinical reality. Our clinical AI is fine-tuned on Saudi-cohort data with explicit cohort sign-off from the partner cluster.

Where does PHI live?

In-Kingdom, at every step. Sovereign cloud or on-prem depending on the cluster's posture. Cross-border PHI movement is not part of our delivery model.

How do you integrate with Epic / Cerner?

FHIR-first. Read-side via FHIR R4, write-side through whatever interface engine the cluster has standardized on. We do not displace the EMR — we operate alongside it.

What about regulatory clearance for clinical AI?

Anything that influences a clinical decision is documented to MoH, CCHI, and CBAHI standards. Where appropriate, we follow IEC 62304 software-lifecycle and submit through the SFDA medical-device pathway.

Do clinicians actually use this?

97% acceptance on the ambient scribe in our flagship cluster — measured weekly. Adoption is the only metric that matters. We design for the clinician first, the dashboard second.

Can you operate at the cluster scale?

Yes. Our flagship deployments cover 8 hospitals, 8,400+ beds, and 3,200+ active clinicians under a single platform. The architecture is cluster-native, not single-site.

The clinician's hour is the asset.

ساعة الطبيب هي الأصل.

Sixty-minute working session with our Healthcare lead and a clinical informaticist. Bring the workflow that hurts — documentation, ED throughput, imaging backlog — and we'll come back with a one-page roadmap.