Healthcare & Life Sciences

Yes. NPHIES is the standard interoperability surface for clinical data, claims, and provider-payer exchange in Saudi Arabia, built on HL7 FHIR R4. We build NPHIES-compliant integrations for hospitals and digital-health providers — eligibility checks, pre-authorisation, claim submission, and clinical-data exchange. The same FHIR foundation lets the system play with bedside monitors and EHR systems already deployed in the facility.

Triage models ingest vital signs, chief complaints in Arabic and English, EHR history, ED occupancy, and labs — predicting acuity, admission likelihood, and deterioration risk. Arabic NLU tuned to clinical terminology is mandatory in the Saudi setting; we test on real Saudi chief-complaint phrasing with native clinical reviewers, not Google-translated baselines. See our AI patient triage guide for the integration patterns.

If the software influences a clinical decision — diagnosis, triage acuity, treatment recommendation, drug dosing, patient risk scoring — it almost certainly qualifies as Software as a Medical Device (SaMD) and needs SFDA registration before clinical use. Pure administrative surfaces (scheduling, billing, claims aggregation) usually don't. We make the classification call up front during discovery so the regulatory path is decided before build, not after.

By default, in-Kingdom — on Saudi-hosted cloud infrastructure where it's permitted, with sovereign-cloud or on-premise options for higher-classification workloads. Cross-border data flows are opt-in, scoped against SDAIA PDPL Article 29, and documented in the patient privacy notice. Audit trails are tamper-evident and feed CBAHI documentation reviews without manual aggregation.

No — Mantiqi is an engineering partner, not a licensed healthcare provider or medical-device manufacturer. Our model is to build and operate the technical surface (EHR, triage AI, telemedicine, NPHIES integrations, audit logging) while you carry the MOH licence as the hospital or pharmacy, and we coordinate directly with the SFDA where SaMD registration applies and with CBAHI on accredited workflows.

Plan on 10–16 weeks end-to-end for a typical engagement: 2 weeks of regulatory scoping and clinical-workflow mapping, 6–10 weeks of build (with two-week iterations), and 2–4 weeks of clinical pilot, penetration testing, and CBAHI mapping before go-live. AI surfaces requiring SFDA registration add 4–8 weeks for the submission cycle in parallel.

Common patterns: EHR implementation and migration off paper or legacy systems, AI-assisted triage and clinical-decision-support surfaces (scoped against SFDA SaMD classification), Arabic-first telemedicine platforms with Nafath identity, pharmacy and lab interoperability layers, NPHIES connectors for claims and clinical exchange, and CBAHI documentation workflows. Engagement scope is set during discovery based on which authorities apply.