Why this, why now, why us.
The UAE is the only GCC market with four operational HIE systems, a national digital identity, and a mandate for electronic claims. The software layer to tie them together has not yet been built.
- The only platform running self-hosted clinical AI inside the UAECloud LLMs (Bedrock, Azure OpenAI) can’t legally process UAE clinical text. We self-host Qwen 2.5 72B and Whisper in a private VPC inside UAE-resident infrastructure. It was hard to do. That’s the moat.
- Four-authority integration is a multi-year projectNABIDH SIT alone takes 4-6 weeks per facility. Malaffi onboarding takes 2+ months and needs SD-WAN. Riayati has its own cadence. We have built every adapter to production spec in the same codebase.
- eClaims automation compounds dailyDDC codes update twice a week from DHA. Payer codes shift. Claim formats drift. Maintaining correctness for DHPO and Shafafiya is continuous engineering work the incumbents haven’t absorbed.
- Bilingual-first gets harder to copy the longer it runsEvery string, every form, every PDF, every WhatsApp template: EN and AR, RTL and LTR, Latin and Eastern numerals. Catching up requires a rewrite, not a translation pass.
- Offline-first desktop protects ADHICS-isolated networksHospitals on isolated LANs, the highest-value segment, can’t use SaaS-only platforms. The desktop app with a local cache makes Sehtak the only option that works where they actually operate.
Not a global platform with UAE plugins.
Sehtak was designed from first principles against UAE federal law, four health authorities, two eClaims regulators, and the Arabic language. It could only have been built here.
PHI never leaves UAE infrastructure
PostgreSQL, Redis, object storage, the LLM, the speech-to-text: all on UAE-resident infrastructure. We self-host Qwen 2.5 72B and Whisper in a private network. No clinical text ever touches an endpoint outside the UAE.
All four UAE health authorities covered
DHA (Dubai), DoH (Abu Dhabi), SHA (Sharjah), and MOHAP (Northern Emirates). NABIDH via HL7 v2.5.1, Malaffi via FHIR R4 over SD-WAN, Riayati over HTTPS. One codebase, four regulators, one install.
Every pipeline separate, per regulator
eClaims and HIE are different pipelines. DHPO wants XML over SOAP, NABIDH wants HL7 v2.5.1, Malaffi wants FHIR R4. DHA itself confirms: no convergence. We ship separate queues, separate endpoints, separate audit trails by design.
RTL-first. Arabic as the primary language.
Every UAE competitor is English-first with Arabic added on. We do it the other way. Components built for RTL, adapted for LTR. Eastern Arabic numerals for clinical values. Proper Arabic typography at every layer.
Federal Decree-Law No. 38 of 2024 guardrails
Controlled-drug prescribing over telehealth is illegal in the UAE. Most EMRs let you do it anyway. We block it at prescription creation. The check is wired into the data model, not a policy banner.