UAE healthcare software is failing doctors, clinics, and patients.
Designed around the doctor's day — not the billing report.
Every screen answers a single question: what does the doctor need right now? Clinical flow first. Compliance — NABIDH, DHPO, ADHICS — happens underneath.
AI ambient scribe
The doctor speaks. Sehtak drafts the SOAP note in Arabic or English, suggests ICD-10-CM codes, and populates the chart — one review, one click, done.
Claim auto-generation
When the encounter closes, Sehtak builds the DHPO or Shafafiya XML automatically — DDC-coded drugs, clinician license on every activity, ICD-10-CM diagnoses. Submitted in seconds.
HIE plumbed out of the box
NABIDH HL7 v2.5.1, Malaffi FHIR R4, Riayati gateway. Consent gates wired per regulator — opt-out for Dubai, opt-in for Abu Dhabi and Northern Emirates. Async, non-blocking, audited.
Offline-first desktop
Your clinic is on an ADHICS-isolated LAN? Sehtak keeps working. The Tauri desktop app caches appointments, patient lists, and prescriptions locally — syncs when the link returns.
Fill the script, not the form.
Dispensing software the pharmacist — not the billing team — actually wants to use. DDC-coded, DHPO-connected, barcode-native, bilingual.
E-prescription queue
Patients arrive with a QR code from the clinic. One scan and the full script — drug, strength, DDC code, doctor license — is ready to verify and dispense.
DDC catalog, always current
The Dubai Drug Code set updates twice a week. Sehtak syncs it twice a week. Every dispense on a DDC-coded item flows straight into the DHPO claim — no manual mapping.
POS built in
Barcode scanner, thermal receipt printer, cash drawer — all native. Sell, refund, and receipt in AED, without leaving the dispensing screen.
Eligibility at the counter
Real-time insurance eligibility against DHPO before dispensing. Co-pay amount displayed. Substitution suggested when the covered brand is cheaper.
Healthcare that feels like it was built for you.
Emirates ID photocopies, paper prescriptions, phone-tag booking — gone. A single mobile app for every clinic, pharmacy, and diagnostic centre on the network.
UAE Pass login
One tap. The government verifies who you are — SOP3 Emirates ID confirmed — and the clinic trusts it. No forms, no photocopies, no waiting.
Book with any clinic on the network
Search by speciality, language, insurer, or proximity. Hold your slot, confirm on the mobile app, arrive — no call, no back-and-forth.
WhatsApp-first reminders
Where you actually live. Appointment confirmations, prescription-ready alerts, refill nudges, lab-result releases — all on WhatsApp.
Arabic and English from day one
Not a translation layer. RTL-first design, Eastern Arabic numerals for clinical values, proper Arabic typography. Switch languages at any time.
One view, your whole family
Prescriptions, lab results, appointments, immunisations — you and your dependents, in one place. Managed consent, always revocable.
Not a global platform with UAE plugins.
Sehtak was designed from first principles against UAE Federal law, four different Health Authorities, two eClaims regulators, and the Arabic language. It could only have been built here.
PHI never leaves UAE infrastructure
PostgreSQL, Redis, S3, the LLM, the speech-to-text — all on AWS me-central-1 or UAE-resident providers. Amazon Bedrock only offers cross-region inference here, so we self-host Qwen 2.5 72B and Whisper inside a private VPC. No clinical text ever touches a non-UAE endpoint.
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 with mandatory SD-WAN, Riayati over HTTPS. One codebase, four regulators, one install.
Every pipeline separate, per regulator
eClaims and HIE are completely different pipelines — DHPO wants XML over SOAP, NABIDH wants HL7 v2.5.1, Malaffi wants FHIR R4. DHA itself confirms: no convergence. Sehtak ships separate queues, separate endpoints, separate audit trails — by design.
RTL-first, Arabic as primary language
Every UAE competitor is English-first with broken Arabic bolted on. Sehtak does 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. Sehtak blocks it at prescription creation — the check is wired into the data model, not a policy banner.
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.
- Only platform running self-hosted clinical AI inside UAEBedrock me-central-1 has no runtime APIs. UAE ICT Health Law forbids health data leaving UAE even de-identified. Our vLLM + Whisper deployment in a private VPC is the only fully compliant way to deliver AI scribing — and it took serious engineering to do it.
- Four-authority integration is a multi-year projectNABIDH SIT alone is 4–6 weeks per facility. Malaffi onboarding is 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 weekly from DHA. Payer codes shift. Claim formats drift. Maintaining correctness for DHPO + Shafafiya is a continuous engineering load — one the incumbents have not 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 — cannot use SaaS-only platforms. The Tauri native shell with local SQLite cache makes Sehtak the only option that works where they actually operate.