AI Scribe, Arabic and English, UAE-resident.
Doctor speaks. Sehtak listens. A bilingual SOAP note appears, ready for one-click approval. Self-hosted Qwen 2.5 on Azure UAE North. Your audio never leaves the country.
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.
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.
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.
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.
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.
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.