Walk into any busy polyclinic in Jeddah, Riyadh, or Dammam, and you will hear medicine practiced in two languages simultaneously. A Saudi internist takes a history in Khaleeji Arabic, the patient responds in a regional dialect, the nurse documents in English on the EMR, and the referral letter is written in formal Medical Arabic. This is not unusual — it is standard.
Yet most clinical documentation tools — and nearly all AI scribes — were built for monolingual English environments. The result: physicians either skip documentation, use awkward transliterations, or maintain parallel workflows for Arabic and English notes. None of these are acceptable for a Kingdom upgrading its health infrastructure while protecting patient rights under PDPL.
What a Proper Bilingual SOAP Note Looks Like
A bilingual SOAP note is not a translation — it is a parallel, culturally competent document. The Subjective section captures the patient's complaint in the language they used, with the clinical summary in the documentation language. Assessment and Plan are in the facility's primary documentation language (often English for NPHIES compatibility) with a patient-facing summary in Arabic.
Example: Subjective Section
Weak: "Patient says head hurts." Strong: "Chief complaint: headache — 3-day history of bilateral frontal throbbing headache, 7/10, worsens with light (Arabic: حساسية للضوء), no preceding aura, associated mild nausea. Denies vomiting, visual changes, neck stiffness."
Why Dialect Awareness Matters
Saudi patients use at least six major regional dialects (Najdi, Hijazi, Eastern, Southern, Tabuk/Northern, and Medina variants), plus significant numbers of expat patients communicating in Urdu, Tagalog, and Egyptian Arabic. A clinical AI trained only on Modern Standard Arabic will misinterpret common expressions — for example, the Najdi word وجع (waja') spans a wide pain spectrum that an MSA-only model may map incorrectly to a single ICD-10 code.
NPHIES and the Language of Claims
NPHIES requires claims submitted in a specific structured format. Diagnosis codes must follow ICD-10-AM, and clinical notes attached to complex claims must be in English. A physician documenting in Arabic must either translate manually before submission or rely on a tool that handles the mapping automatically.
Sina generates NPHIES-compatible outputs by default: the clinical note is produced in both languages, with the English version structured to map directly to claim fields. This eliminates the translation step that consumes 15–20 minutes per complex claim in most facilities today.
The ROI of Getting Language Right
- Claim rejection rates drop when documentation language matches NPHIES requirements — some facilities report 18–22% fewer rejections.
- Patient satisfaction improves when discharge summaries are provided in Arabic.
- Physician documentation time decreases when the tool matches how they actually think and speak.
- Medical error rates linked to translation ambiguity decrease with standardized bilingual documentation.
Building for Saudi, Not Adapting for Saudi
There is a meaningful difference between a global tool adapted for Arabic markets and a tool built from the ground up for Saudi clinical practice. Sina was trained on Saudi clinical data, designed by a team that includes Saudi physicians, and tested in KSA facilities. The bilingual capability is not a feature — it is the foundation.